Project Complexity Reduction Tactics

🏗 How To Tackle Large, Complex Projects. With practical techniques to meet the desired outcome, without being disrupted or derailed along the way ↓ 🤔 99% of large projects don’t finish on budget and on time. 🤔 Projects rarely fail because of poor skills or execution. ✅ They fail because of optimism and insufficient planning. ✅ Also because of poor risk assessment, discovery, politics. 🎯 Best strategy: Think Slow (detailed planning) + Act Fast. ✅ Allocate 20–45% of total project effort for planning. ✅ Riskier and larger projects always require more planning. ✅ Think Right → Left: start from end goal, work backwards. ✅ For each goal, consider immediate previous steps/events. ✅ Set up milestones, prioritize key components for each. ✅ Consider stakeholders, users, risks, constraints, metrics. 🚫 Don’t underestimate unknown domain, blockers, deps. ✅ Compare vs. similar projects (reference class forecasting). ✅ Set up an “execution mode” to defer/minimize disruptions. 🚫 Nothing hurts productivity more than unplanned work. Over the last few years, I've been using the technique called “Event Storming” suggested by Matteo Cavucci to capture user’s experience moments through the lens of business needs. With it, we focus on the desired business outcome, and then use research insights to project events that users will be going through towards that outcome. On that journey, we identify key milestones and break user’s events into 2 main buckets: user’s success moments (which we want to dial up) and user’s pain points or frustrations (which we want to dial down). We then break out into groups of 3–4 people to separately prioritize these events and estimate their impact and effort on Effort vs. Value curves (https://lnkd.in/evrKJUEy). The next step is identifying key stakeholders to engage with, risks to consider (e.g. legacy systems, 3rd-party dependency etc.), resources and tooling. We reserve special timing to identify key blockers and constraints that endanger successful outcome or slow us down. If possible, we also set up UX metrics to track how successful we actually are in improving the current state of UX. When speaking to business, usually I speak about better discovery and scoping as the best way to mitigate risk. We can of course throw ideas into the market and run endless experiments. But not for critical projects that get a lot of visibility — e.g. replacing legacy systems or launching a new product. They require thorough planning to prevent big disasters and urgent rollbacks. If you’d like to learn more, I can only highly recommend "How Big Things Get Done" (https://lnkd.in/erhcBuxE), a wonderful book by Prof. Bent Flyvbjerg and Dan Gardner who have conducted a vast amount of research on when big projects fail and succeed. A wonderful book worth reading! Happy planning, everyone! 🎉🥳

Have you ever spent endless hours on a project just to end up realising that a more straightforward method would have been more effective? This common mistake, referred to as over-engineering, can cause needless complexity and inefficiency when developing new products. Understanding Over-engineering > Over-engineering happens when a solution gets more difficult than it needs to be, usually by adding features or functionalities that do not directly meet the needs of customers. > This can lead to higher costs, longer development cycles, and less user-friendly products. Real-World Example: The Juicero The Juicero, a high-tech juicing machine, was released in 2016. It cost $700 and was designed to squeeze proprietary juice packets with considerable force. Later on, though, it was found that the costly machine was not essential because the same juice bags could be squeezed by hand. The company was eventually shut down as a result of the public outcry following this disclosure. My Own Story: The Overly Complex Website I was in a team early in my career that was assigned with creating a company website. We included the newest interactive elements and design trends in an effort to wow. Feedback received after the launch, however, indicated that visitors found the website overwhelming and challenging to use. In our pursuit of innovation, we had failed to realise the website's main purpose, which is to provide easily comprehensible information. I learnt the importance of simplicity and user-centred design from this experience. Useful Tips to Prevent Over-Engineering 1. Pay attention to the essential needs: Focus on key features that meet user needs and clearly explain the issue you're trying to solve. Don't include features that aren't directly useful. 2. Adopt Incremental Development: Begin with an MVP that satisfies the fundamental specifications. By using this method, you may get user input and decide on new features with knowledge. 3. Put Simplicity First: Use the KISS philosophy, which stands for "Keep It Simple, Stupid." Simpler designs are frequently easier to use and more efficient. 4. Verify Assumptions: Talk to users to learn about their wants and needs. This guarantees that the things you create will actually be useful to them. 5. Promote Open Communication: Create an environment where team members are at ease sharing thoughts and possible difficulties. Over-engineering tendencies can be recognised and avoided with the support of this collaborative environment. Have any of your initiatives involved over-engineering? How did you respond to it? Post your thoughts and experiences in the comments section below!

Complexity used to be the cost of scale. Now, it’s the tax on speed. For leaders of my generation, complexity has been our conditioning because we were taught that it equals competence. Dense slide decks made me feel credible. Multilayered strategies made me feel indispensable. Overpacked calendars gave me the illusion of control. Over time, I saw what complexity actually does: it slows decisions, dilutes focus, and distances leaders from outcomes. What I once thought made me look smart was actually keeping me stuck. We are no longer rewarded for how much we manage, how long we work, or how complex we sound. We are rewarded for how clearly we lead, how quickly we decide, and how efficiently we execute. Yet, reduction is deceptively hard for senior executives because reduction challenges identity. It confronts ego. Senior leaders don’t need to do more. We need to do fewer things faster and better with tools and thinking that match the velocity of this new era. STRATEGIC COMPLEXITY 🚫 Long decks. Vague goals. Annual cycles that feel irrelevant after six weeks. 👉 The shift: Move to lean, AI-assisted strategy cycles. Think quarterly focus, not yearly sprawl. OPERATIONAL COMPLEXITY 🚫 Bloated workflows. Too many approvals. Manual check-ins across disconnected tools. 👉 The shift: Cut, automate, or reassign. Simpler systems lead to faster movement. COMMUNICATION COMPLEXITY 🚫 Email chaos. Unclear messaging. Meetings that go nowhere. 👉 The shift: Move to asynchronous clarity with AI-generated briefs. The next era will be led by those who simplify the fastest. That's the new currency of high-performance leadership. Outcomes improve not by layering more controls but by returning to the essential. As John Maeda says: “Simplicity is about subtracting the obvious and adding the meaningful.” Where are you mistaking complexity for value and what can you strip away? #leadership #transformation #change

Big 4 Sell Complexity. We Cut 47 Initiatives to 3. The “18‑month roadmap” down to 90 days. How? I once watched a factory manager nearly lose his job because he refused to follow the Big 4 playbook. His name was Marco. One of his plants was struggling Late deliveries, high costs, frustrated teams. The board brought in a top-tier consulting firm. Their solution? A 12-month "digital transformation roadmap" with 47 initiatives, 9 new software systems, and a 200-slide deck. Marco pushed back. He said: "This is too slow. Too complicated. We need to fix the basics first." They ignored him. Six months in, the consultants were gone, the project was over budget, and nothing had improved. So Marco did something radical. He called me ; ) Then: He scrapped the plan. Instead, he focused on three things: 1. Fix the bottlenecks first: no tech, no fancy tools, just clear the logjams slowing production. 2. Train the team in simple problem-solving: no six-sigma black belts, just daily 15-minute huddles to tackle issues. 3. Measure only what matters: no 50 KPIs, just delivery time, cost per unit, and defect rate. Within 90 days, output went up 30%. Costs dropped. Morale improved. The board was shocked. Here’s the problem: Big 4 consultants sell complexity because it justifies their fees. But in the real world, speed and simplicity win. Want to transform faster? Try this: - Start small: Pick one high-impact area, fix it fast, then scale. - Cut the jargon: If your team doesn’t understand it, it won’t work. - Ignore "best practices": What works for a Fortune 500 won’t fit your factory floor. The result? You’ll move faster, spend less, and actually see results, not just PowerPoints. So here’s my question: Have you ever seen a "perfect" plan fail because it was too complex? Drop a comment below. 👇 — ♺ Reshare to your network to someone who needs to hear this, they’ll thank you. ► Like this? Join my newsletter: https://lnkd.in/dMGaUj4p for more no-BS transformation wins.

Adding more people won't solve your problem. Odds are, it'll make things worse. Here's a pattern that hurts most teams: Problem → Add People → Create Complexity → Face Bigger Problems → Hire Even More People They chase capacity. And then drown in complexity. An overlooked paradox: • People scale linearly • Complexity scales exponentially Savvy teams take a different path: Problem → Diagnose Root Cause → Simplify or Automate → Focus & Execute → Scale What Works They know: Pruning enables growth. Complexity kills potential. Before you look to hire, Ask these questions: 1. What Should Stop? • Low-impact meetings • Redundant reporting • "Nice to have" projects 2. What's Overcomplicated? • Decision processes • Communication flows • Project handoffs 3. What Are We Avoiding? • Hard conversations • Tech improvements • Priority choices 4. How can we leverage AI? • Document processing • Standard responses • Data analysis • Routine tasks Remember: Success rarely comes from doing more. It comes from doing fewer things better. What complexity will you eliminate first? ♻️ Share to help someone 🔔 Follow Marsden Kline for more 📌 Save these questions to review before you add to your team -- We are sharing another practical way AI can help. Join our live lesson on building a AI-Powered Employee Dashboard: https://lnkd.in/eEZX-9Sq

The best project managers know how to make things simple. They deliver one-page summaries, not decks. They send 3-5 bulleted emails, not essays. They track what matters, not the extraneous. They communicate clearly, not with jargon. You can't distill your project to one page? You don't understand it well enough. You can't explain status in three sentences? You're making it more complex than it needs. You sent a phone book of updates nobody reads? You're wasting everyone's time. You create dashboards that look like an airplane cockpit? You're tracking noise, not what matters. Great project managers strip everything to the essentials, deliver information people can actually use, make the complex simple, and clearly communicate what matters most. Just doing this puts you in the top 10% of project managers. If your deliverables seem difficult... Simplify. Can you cut your status update to 5 sentences? Could you reduce your dashboard to 3 metrics? Should you condense your project plan to a single page? In this busy world, simplicity is hard to ignore.

How I Make Complex Projects Feel Simple as a Program Manager at Amazon The work doesn’t need to get easier. It needs to get clearer. I don’t shy away from complex projects. Tight timelines. Messy org charts. Conflicting priorities. Unknowns on top of unknowns. That’s the job. But the secret isn’t working more hours… It’s building simplicity on the other side of complexity. Here’s how I do it: 1/ I create a one-sentence summary of the goal ↳ “This program exists to [do what] by [when] for [whom]” ↳ If I can’t write that clearly, no one knows what we’re doing 2/ I write a list of “what must be true” ↳ Not tasks…conditions for success ↳ Headcount approved, system stable, stakeholder signed off ↳ This becomes the spine of the plan 3/ I give every problem a container ↳ Timeline issues = blue ↳ Headcount issues = yellow ↳ Tech blockers = red ↳ Sorting beats solving…clarity before action 4/ I ruthlessly limit what we work on at once ↳ Multi-threading = multi-drifting ↳ I stack work sequentially and communicate why ↳ Simplicity isn’t less work…it’s fewer distractions 5/ I revisit the goal every Monday ↳ “Are we still solving the right problem?” ↳ If the answer is no, I reset the team ↳ Simplification is a weekly practice, not a one-time effort You don’t need a perfect plan. You need a simple narrative your team can run with under pressure. 📬 I share systems like this weekly in The Weekly Sync: 👉 https://lnkd.in/e6qAwEFc What’s your go-to move when things start getting complicated?

Only 0.5% of mega projects deliver the expected outcomes or better, on time or shorter, and on budget or cheaper. Megaproject Heuristics Checklist This checklist is based on Bent Flyvbjerg’s *How Big Things Get Done* and summarizes key heuristics that improve the odds of delivering large, complex projects on time and on budget. ● Think Slow, Act Fast – Spend time upfront in planning; execution should be rapid. ● Reference Class Forecasting – Compare against similar past projects to calibrate cost, schedule, and risk. ● Take the Outside View – Avoid optimism bias; ask what happened in comparable efforts. ● Keep It Simple & Modular – Favor repeatable, proven components over one-off complexity. ● Check Optimism & Misrepresentation – Guard against deliberate or unconscious underestimation. ● Align Incentives – Ensure contracts and governance tie outcomes to performance. ● Front-End Loading (FEL) – Lock in scope, design, and contingencies early. ● Use Probabilistic Planning – Model ranges and distributions, not single-point estimates. ● Learn from Failure & Success – Document, benchmark, and apply lessons systematically. ● Build for Real Users – Ensure design reflects actual needs and usage patterns.

Stop trying to describe the "flow" of a project with words. Draw it instead. ✍️ Some people are verbal learners, but many of your team members are visual. If you’re explaining a complex process or a new team structure using only paragraphs, you’re losing half your audience. A simple diagram, a flowchart, or even a well-placed icon can do the heavy lifting that three paragraphs of text can’t. You don't need to be a graphic designer. - Use a simple table for comparisons. - Use a timeline for project milestones. - Use a basic flowchart for "If this, then that" scenarios. When you show rather than just tell, the message sticks. Do you include visuals in your internal comms, or are you strictly a "text only" person? I’d love to hear what works for your teams. [Image description: Four blue tiles. (1) has black headline text that reads: 3 ways to use visuals to simplify complexity. (2) Black text that reads: 1. Use tables for comparisons. Below is a simple table with two columns headed 'current state' and 'future state'. (3) Black text that reads: 2. Use timelines or milestones. Below is a simplified version of a timeline graphic featuring five markers on a dotted line. (3) Reads: 3. Use icons as signposts. Below are three examples: an information icon, an action icon, and a share with your team icon.]

When we help companies get into FLOW, most managers stumble over the question of reducing work in progress! They always think it's very time-consuming. In practice, however, it's really easy if you know two things: 1. Any WIP reduction (and prioritization) is better than none – no matter how wrong it is, it always gets better. 2. If you accidentally pause something wrong, you can easily change it – one in = one out. In other words, no matter how bad it is, it always gets better. But you don't have to make yourself look stupid. In most cases, the order and the optimal WIP are easy to find. Here's just one way of how it can be done quickly: 1. Put all projects (or agile initiatives/releases) on a list and sort them by promised delivery date. 2. Start at the top and allocate the optimal resources to the top item on the list as if it were the only one – there is a list of names of the people with skills, which can simply be crossed off when they are assigned to a project. 3. Then continue with the next item on the list until no more people can be assigned to projects – this is the red line; no work may be done on projects below it. Finally, check whether there is anything critical below the red line. If so, then “one in, one out.” Even with hundreds of people, this usually takes 1-2 hours. Of course, there are more detailed and better options. For example, we have an Excel spreadsheet (SmartPipeliner) that is also used in large companies with thousands of employees. This usually takes 1-4 days, but you end up with a decision template that is suitable for the board. SmartPipeliner and support in filling it out are available free of charge in our community for hyperproductive knowledge work – simply register and search for SmartPipeliner in the Body of Knowledge: 🔗 https://lnkd.in/eQR_AgmM