Project Management

Stuck in an endless loop of client changes? Lost track of what revision this constitutes? Yeah. Been there. Done that. The secret? It's not about saying no. It's about saying yes to the right things upfront. Every project that goes sideways starts the same way: Vague agreements. Fuzzy boundaries. Good intentions. Six weeks later you're bleeding money and everyone's frustrated. Here's my framework after 30 years of running two 8-figure businesses: The SOW is your salvation. Not some boilerplate template. A real document that covers: • Exact deliverables (not "design work" but "3 homepage concepts, 2 rounds of revisions") • Hours of operation ("We respond M-F, 9-5 PST. Weekend requests get Monday responses") • Revision rounds spelled out ("Round 1 includes up to 5 changes. Round 2 includes 3.") • Feedback cycles defined ("48-hour turnaround for client feedback or the project may be delayed or additional fees may be incurred") But here's what most people miss— Don't work on client notes immediately. Client sends 37 pieces of feedback at 11pm Friday? Producer sends conflicting notes from the CEO? Marketing wants one thing, sales wants another? Stop. Collect everything first. Resolve the conflicts. Get on the phone and discuss it with your client to get alignment. Separate the "have to haves" from the "nice to haves". Then present unified changes. "Based on all feedback received, here are the 8 changes we'll implement. This constitutes revision round 2 of 3." Watch how fast the random requests stop. No extra work that goes unappreciated. No more feelings of being taken advantage of. Communicate before the crisis, prevents the crisis from happening. "Just so you know, we're entering round 2. You have one more included. After that, it's $X per additional round." No surprises. No awkward money conversations. No resentment. Scope creep isn't a them problem. It's a you problem. And that's good news, because that means you are in control. They're not trying to take advantage. They just don't know where the boundaries are because you never drew them. Draw the lines early. Communicate them clearly. Everyone wins. What's your most painful scope creep story? What boundary would've prevented it? Small Business Builders #projectmanagement #clientmanagement #businessgrowth

Last week, I described four design patterns for AI agentic workflows that I believe will drive significant progress: Reflection, Tool use, Planning and Multi-agent collaboration. Instead of having an LLM generate its final output directly, an agentic workflow prompts the LLM multiple times, giving it opportunities to build step by step to higher-quality output. Here, I'd like to discuss Reflection. It's relatively quick to implement, and I've seen it lead to surprising performance gains. You may have had the experience of prompting ChatGPT/Claude/Gemini, receiving unsatisfactory output, delivering critical feedback to help the LLM improve its response, and then getting a better response. What if you automate the step of delivering critical feedback, so the model automatically criticizes its own output and improves its response? This is the crux of Reflection. Take the task of asking an LLM to write code. We can prompt it to generate the desired code directly to carry out some task X. Then, we can prompt it to reflect on its own output, perhaps as follows: Here’s code intended for task X: [previously generated code] Check the code carefully for correctness, style, and efficiency, and give constructive criticism for how to improve it. Sometimes this causes the LLM to spot problems and come up with constructive suggestions. Next, we can prompt the LLM with context including (i) the previously generated code and (ii) the constructive feedback, and ask it to use the feedback to rewrite the code. This can lead to a better response. Repeating the criticism/rewrite process might yield further improvements. This self-reflection process allows the LLM to spot gaps and improve its output on a variety of tasks including producing code, writing text, and answering questions. And we can go beyond self-reflection by giving the LLM tools that help evaluate its output; for example, running its code through a few unit tests to check whether it generates correct results on test cases or searching the web to double-check text output. Then it can reflect on any errors it found and come up with ideas for improvement. Further, we can implement Reflection using a multi-agent framework. I've found it convenient to create two agents, one prompted to generate good outputs and the other prompted to give constructive criticism of the first agent's output. The resulting discussion between the two agents leads to improved responses. Reflection is a relatively basic type of agentic workflow, but I've been delighted by how much it improved my applications’ results. If you’re interested in learning more about reflection, I recommend: - Self-Refine: Iterative Refinement with Self-Feedback, by Madaan et al. (2023) - Reflexion: Language Agents with Verbal Reinforcement Learning, by Shinn et al. (2023) - CRITIC: Large Language Models Can Self-Correct with Tool-Interactive Critiquing, by Gou et al. (2024) [Original text: https://lnkd.in/g4bTuWtU ]

The C.A.S.H Framework How do you improve CASH? Follow my framework: C - Collections Efficiency Quickly collecting receivables allows for immediate use of funds in operations, investments, or debt payment. How? • Implement an automated invoicing system. • Systematically follow up overdue payments. • Encourage shorter payment terms or early payments. A - Accurate Forecasting Forecasting helps anticipate liquidity needs and prepares you for situations that could strain cash reserves. How? • Use financial forecasting software. • Regularly adjust forecasts based on actuals. • Collaborate with sales, operations, and procurement for their insights. S - Streamlined Expenses Optimizing operational costs increases the available cash in your business. How? • Regularly audit expenses to identify inefficiencies. • Negotiate better rates or terms with suppliers. • Use cost-saving technologies or automation. H - Healthy Investment Wise investments contribute to future cash flow, and efficient inventory management frees tied-up cash. How? • Develop a process for evaluating investments. • Use just-in-time inventory management. • Regularly review and dispose of underperforming assets. 👉 Which framework or tactics do you use to improve your Cash? Save this post for later and share it around ;)

𝗧𝗼𝗱𝗮𝘆, 𝗣𝗠𝗜 𝗿𝗲𝗹𝗲𝗮𝘀𝗲𝘀 𝘁𝗵𝗲 𝗳𝗶𝗿𝘀𝘁 𝗿𝗲𝘀𝘂𝗹𝘁𝘀 𝗳𝗿𝗼𝗺 𝘁𝗵𝗲 𝗹𝗮𝗿𝗴𝗲𝘀𝘁 𝘀𝘁𝘂𝗱𝘆 𝘄𝗲’𝘃𝗲 𝗲𝘃𝗲𝗿 𝗰𝗼𝗻𝗱𝘂𝗰𝘁𝗲𝗱 - 𝗼𝗻 𝗮 𝘁𝗼𝗽𝗶𝗰 𝘁𝗵𝗮𝘁 𝗶𝘀 𝗰𝗿𝗶𝘁𝗶𝗰𝗮𝗹 𝘁𝗼 𝗼𝘂𝗿 𝗽𝗿𝗼𝗳𝗲𝘀𝘀𝗶𝗼𝗻: 𝗣𝗿𝗼𝗷𝗲𝗰𝘁 𝗦𝘂𝗰𝗰𝗲𝘀𝘀. 📚 Read the report: https://lnkd.in/ekRmSj_h With this report, we are introducing a simple and scalable way to measure project success. A successful project is one that 𝗱𝗲𝗹𝗶𝘃𝗲𝗿𝘀 𝘃𝗮𝗹𝘂𝗲 𝘄𝗼𝗿𝘁𝗵 𝘁𝗵𝗲 𝗲𝗳𝗳𝗼𝗿𝘁 𝗮𝗻𝗱 𝗲𝘅𝗽𝗲𝗻𝘀𝗲, as perceived by key stakeholders. This clearly represents a shift for our profession, where beyond execution excellence we also feel accountable for doing anything in our power to improve the impact of our work and the value it generates at large. The implications for project professionals can be summarized in a framework for delivering 𝗠𝗢𝗥𝗘 success: 📚𝗠anage Perceptions For a project to be considered successful, the key stakeholders - customers, executives, or others - must perceive that the project’s outcomes provide sufficient value relative to the perceived investment of resources. 📚𝗢wn Project Success beyond Project Management Success Project professionals need to take any opportunity to move beyond literal mandates and feel accountable for improving outcomes while minimizing waste. 📚𝗥elentlessly Reassess Project Parameters Project professionals need to recognize the reality of inevitable and ongoing change, and continuously, in collaboration with stakeholders, reassess the perception of value and adjust plans. 📚𝗘xpand Perspective All projects have impacts beyond just the scope of the project itself. Even if we do not control all parameters, we must consider the broader picture and how the project fits within the larger business, goals, or objectives of the enterprise, and ultimately, our world. I believe executives will be excited about this work. It highlights the value project professionals can bring to their organizations and clarifies the vital role they play in driving transformation, delivering business results, and positively impacting the world. The shift in mindset will encourage project professionals to consider the perceptions of all stakeholders- not just the c-suite, but also customers and communities. To deliver more successful projects, business leaders must create environments that empower project professionals. They need to involve them in defining - and continuously reassessing and challenging - project value. Leverage their expertise. Invest in their work. And hold them accountable for contributing to maximize the perception of project value at all phases of the project - beyond excellence in execution. 📚 Please read the report, reflect on its findings, and share it broadly. And comment! Project Management Institute #ProjectSuccess #PMI #Leadership #ProjectManagementToday

Most projects fail. But there’s a simple technique to give yours a fighting chance. It’s not a to-do list. It’s not a fancy tool. It’s not a 12-step system. It’s a single question that flips the way you think. Here’s how it works: It’s called a “premortem.” You’ve heard of a postmortem what went wrong after a project dies. A premortem asks: What if we ran that analysis now? Before anything dies. Before the first misstep. Before failure sets in. The premortem comes from psychologist Gary Klein. Here’s how to run one: → Gather your team. → Imagine it’s 2 years in the future. → The project has completely failed. → Ask: What went wrong? No sugarcoating. No happy talk. Start listing the causes of failure. Budget misfire? Wrong team? Lack of buy-in? Scope creep? Missed deadlines? You’ll be shocked how quickly people identify risks—once they feel safe predicting failure. Why this works: It defeats irrational optimism. • It turns hindsight into foresight. • It makes risk visible. • It aligns the team before chaos hits. Because the best time to fix a problem… is before it happens. Pre-mortems don’t require special skills. Just a shift in mindset: Don’t assume success. Assume failure—and reverse-engineer your way out. Ask: What will future-you wish you had done? Then… do that now. I run a premortem for every big project I take on. Writing a book? Premortem. Launching a podcast? Premortem. Planning an event? Premortem. It never guarantees success—but it always makes success more likely. Summary: The Premortem Playbook → Imagine future failure. → List the causes. → Turn those risks into action steps. → Adjust your plan today. It’s one of the most underrated tools in your productivity toolkit. Try it before your next project. You won’t regret it.

As head of our product organization at Chase, I often think about how and what we’re delivering to customers, but I recently reflected on the vital role of product managers. While some may view it as merely administrative, in my opinion this couldn't be further from the truth. Product managers are the driving force behind strategy and exceptional experiences, whether for external customers or internal users. Our role demands a deep connection to both the product and its users. Three essential qualities we all have: Customer Obsession: Go beyond empathy by diving into data and insights to understand user behavior, pain points, and opportunities. Decisions should be data-driven, ensuring the product evolves with user needs. Strategic Leadership: Product managers must define and drive the product vision, setting strategies that align with company goals. This involves fostering alignment across cross-functional teams and building strong relationships with stakeholders to ensure everyone is working toward a shared vision. Accountability: Own the outcomes, whether good or bad. Exceptional product managers embrace challenges, learn from mistakes, and continuously iterate to improve. They step into gray areas, connecting the dots to drive cohesive and successful outcomes. This role is strategic and high-impact, requiring us to lead with intention, push boundaries, and always advocate for the user. #productmanagers #productdevelopment

💵 “What’s the ROI of your UX project?” How to be better prepared to make a strong case for UX, design, research and accessibility ↓ 🤔 Return on Investment (ROI) is all about the value of a project. 🤔 Most managers want to see investments with ROI > 15%. ✅ Businesses must see what they’ll get + what it costs them. ✅ Return is revenue, but also fewer costs, expenses, risks. 🚫 Most designers aren’t prepared for ROI conversations. ✅ ROI isn’t always money, but degree of impact/success. ✅ First, we must identify the problem, its costs and impact. ✅ Then, we set up goals/targets that we want to reach. ✅ We project changes: time savings ↑, drop-offs ↓, etc. ✅ We gather costs/expenses: team hours, tools, prep work. ✅ ROI = ( Projected Benefits – Cost) ÷ Cost ) × 100. ✅ Projected benefits must be realistic but conservative. ✅ Research how many users are affected by your changes. ✅ Track impact: adoption, retention, user satisfaction (TARS). For a given project, most businesses want to understand what they'll get, when they'll get it and how much it will cost them. Ironically, most signed-off projects are tremendously expensive and risky — they are big bets with large engineering efforts. To the contrast, UX is often much easier and much more cost-effective, yet often it’s perceived as unnecessary, expensive and time-consuming. The reason for that is almost always wrong expectations, poor assumptions and little understanding of the project’s impact on business. Senior management wants: 1. More things that worked in the past 2. Reliable outcomes of the work done 3. Effective solutions to existing problems 4. Clear initiatives with meaningful goals 5. More influence and better standing And in terms of strategic priorities (as noted by Jared Spool): 1. Increased revenue → UX fit ✅ 2. Decreased costs → UX fit ✅ 3. Increased new business → UX fit ✅ 4. Increased existing business → UX fit ✅ 5. Increased shareholder value → hard to show 🚫 (6. Reduced and mitigated risks) → UX fit ✅ We have to frame our work in terms of business value that fits in these areas to make a strong case for our projects. When I hear about “ROI of design”, I always get reminded of Erika Hall's point about how strange that concept actually is. How would you calculate ROI of HR? Or ROI of engineering? Most companies are looking for ROI of specific projects, not functions. Personally, when I argue about the impact of UX work, I always highlight the cost of working on a wrong solution for a wrong problem that has barely any impact on business. We want to work on impactful projects, and to find them, we need to do research, iterations, testing and then measure outcomes. As Erika said, “design is just systematic, intentional decisions. You need to know which decisions to focus on, which may not look like “design”. And that’s an incredible value of UX — often with much less effort and much more impact on the bottom line. [Examples and tools in the comments below ↓]

Wheel for Sustainable Business Innovation 🌎 The sustainability landscape is evolving rapidly, and businesses are increasingly expected to integrate environmental and social considerations into their innovation processes. However, traditional innovation frameworks often fall short by focusing solely on customer needs, financial returns, and technical feasibility, leaving critical planetary challenges unaddressed. A more comprehensive approach is needed—one that embeds sustainability at the core of value creation. The 130+ Value Proposition Types Wheel is a practical tool that helps organizations frame innovation efforts across four key dimensions: People, Planet, Profit, and Progress. It provides over 130 value types that businesses can leverage to ensure their projects contribute meaningful solutions to global challenges such as climate action, resource efficiency, social inclusion, and technological advancement. This approach shifts the focus beyond immediate customer needs to include long-term sustainability impacts across entire ecosystems. By using structured frameworks like this, companies can link their innovation projects directly to UN Sustainable Development Goals (SDGs), addressing critical issues such as climate resilience, biodiversity, and social equity. The tool also encourages the use of metrics to track progress, making sustainability-driven innovation more actionable and measurable across industries. It helps businesses unlock new forms of value while addressing both environmental risks and opportunities. The tool is adaptable to different phases of the innovation process, from identifying unmet needs to scaling solutions in the market. It guides organizations in understanding how their innovations create value in areas such as climate action, circularity, supply chain management, and stakeholder engagement. This makes it relevant for both B2B and B2C companies aiming to enhance their impact while future-proofing their operations. Originally developed by Explorer Labs, this tool has been referenced in the past and continues to remain highly useful as businesses advance their sustainability journeys. As 2025 begins, leveraging tools like this can help organizations move from incremental improvements to transformative solutions, embedding sustainability into innovation processes that deliver lasting value. #sustainability #sustainable #business #esg #climatechange #innovation #SDGs

Reflecting on Agile Development with DevOps 2.0: A Flexible CI/CD Flow Last year, I shared a CI/CD process flow for Agile Development with DevOps 2.0, and it’s been amazing to see how much it resonated with the community! This framework isn’t about specific tools—it’s about creating a seamless, collaborative process that supports quality and agility at every step. ✅ 𝗣𝗹𝗮𝗻: Building a Strong Foundation with Clear Alignment The journey begins with planning—whether it's user stories, tasks, or broader product goals. Tools like JIRA or Asana (or any project management platform) help capture requirements and align the team with the Product Owner’s vision. This early alignment is essential to avoid misunderstandings and establish a shared understanding of success. Key Insight: Planning thoroughly and involving stakeholders from the start leads to a smoother process. When everyone’s on the same page, the entire pipeline benefits. ✅ 𝗖𝗼𝗱𝗲: Collaborative Development and Real-Time Feedback In the coding phase, developers work together, often pushing code to a version control platform like GitHub or Bitbucket and communicating via real-time collaboration tools like Slack or Teams. Open communication and continuous feedback help catch issues early and keep the team in sync. Key Insight: Real-time feedback is crucial for speed and quality. Regardless of the tools, creating a culture of continuous collaboration makes all the difference. ✅ 𝗕𝘂𝗶𝗹𝗱: Automating Quality and Security Checks As code is committed, it’s essential to automate quality and security checks. Tools like Jenkins, CircleCI, or any CI/CD platform can trigger builds and run automated tests, ensuring that quality checks are consistent and fast. This step helps prevent issues from creeping into production. Key Insight: Automated checks for quality and security are invaluable. Integrating these checks into the build process improves confidence in every deployment. ✅ 𝗧𝗲𝘀𝘁: Structured, Multi-Environment Testing Testing is layered across environments—whether it’s regression, unit, or user acceptance testing (UAT). Using frameworks like Selenium for automated testing or dedicated QA/UAT environments enables rigorous validation before production. Key Insight: Testing across environments is a safeguard for quality. Structured testing helps ensure that code is reliable and ready for release. ✅ 𝗥𝗲𝗹𝗲𝗮𝘀𝗲: Scalable, Reliable Deployments with Infrastructure as Code (IAC) Finally, using Infrastructure as Code (IAC) principles with tools like Terraform, Ansible, or other IAC solutions, deployments are made repeatable and scalable. IAC empowers teams to manage infrastructure more efficiently, ensuring consistent and controlled releases. Thank you to everyone who has engaged with this diagram and shared your insights! I’d love to hear how others approach CI/CD. Are there any tools or strategies that have worked well for you?

Enterprises want the speed and intelligence of AI agents and automation, but never at the expense of security or control. Auditability remains essential in making that possible. Organizations need to verify what happened, when it happened, and why, and this level of transparency has shaped how we’ve built trust with enterprises over many years. Protecting sensitive information is equally critical as AI models enter more workflows. Model governance helps safeguard PII, enforce regional and data-handling requirements, and log every model interaction so organizations can innovate without compromising the data they are responsible for. Underpinning all of this is that customers need to know they can trust the companies that platforms and tools they rely on to get work done across their businesses. Governance and security are what allow enterprises to move forward with confidence, and they remain the foundation of the trust we’ve earned and continue to protect as the landscape of agentic automation evolves.