Complexity Management in Systems Projects

🏗 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! 🎉🥳

Understanding complex systems changed how I think about design, strategy and futures work. It’s also the fourth and final ellipse in my strategic design model. Complex systems have some unique qualities: - Cause and effect aren’t linear - Even observing the system changes its nature - You can only really make sense of what happened in hindsight Those properties matter more than most design models acknowledge. A lot of design and strategy work assumes that if we can define a future state clearly enough, we can plan our way towards it. That can work when a problem is complicated. It doesn’t hold in a complex environment. If you’ve ever worked in a situation where: - People disagree on what the problem actually is - Interventions create unexpected side effects - The same “solution” works in one place and fails in another - Progress feels real, but hard to explain or predict you’re probably dealing with complexity. This is the work of Dave Snowden and The Cynefin Company, particularly through the Cynefin framework and Snowden’s work on anthrocomplexity. Complex adaptive systems shaped by human sense-making, not just behaviour. In that context, the approach changes. Rather than defining an end state and working backwards, we: - Understand and start from where we are - Run multiple safe-to-fail experiments - Amplify what seems to work - Dampen what doesn’t - Watch for what else emerges Importantly, we run these experiments in parallel. This is where complexity challenges design habits. Design often pushes us toward convergence — finding the best answer as efficiently as possible. In complexity, diversity matters more than optimisation. We might deliberately run experiments we think might fail, as we can’t be certain of the results. And because cause and effect are only clear in the rear view mirror we should expect surprises. I’m barely touching on the depth and breadth of anthrocomplexity here. There’s a substantial body of work behind it. In my practice it doesn’t replace design, strategy or futures thinking. It reframes how and when they’re useful. It’s also a reminder to be careful with familiar models, especially when the system itself is adaptive, complex and uncertain. As Col. John Boyd put it: “If you don’t challenge assumptions, what is doctrine on day one becomes dogma forever after.” For me, complex adaptive systems thinking is one way of keeping that challenge alive. #StrategicDesign #FuturesThinking #Strategy #DesignThinking #ComplexAdaptiveSystems

Healthcare has a habit of treating complexity as evidence of seriousness. A workflow with 14 approvals, 6 workarounds, 3 disconnected systems, and a team of people quietly repairing what the technology failed to do can easily acquire an undeserved aura of legitimacy, as if complexity itself were proof that the process is rigorous, compliant, or somehow necessary. It usually is not. What it often represents is accumulation: accumulated policy, accumulated caution, accumulated exceptions, accumulated handoffs, accumulated decisions nobody has had the time or appetite to revisit. That is why simplification is difficult. It demands more judgment than adding another layer, because adding feels productive while simplification forces a more uncomfortable reckoning. Which steps in this workflow are truly essential, and which ones survived simply because nobody removed them? That question matters enormously in healthcare. Complexity shapes labor cost, throughput, adoption, patient experience, and the real-world usability of any system we claim is improving operations. A process can look comprehensive on paper and still be structurally wasteful in practice. Before adding another automation layer, another Artificial Intelligence tool, or another vendor into the stack, it is worth asking whether the underlying workflow deserves to survive in its current form at all. A surprising amount of operational drag comes from old decisions still running long after their logic has expired. P.S. This reflection was inspired by Jon McNeill’s keynote at #HIMSS26.

In the lively debate of "Which agile method reigns supreme?" the truth is that no one is right. But clients often come to us inquiring, "What's the optimal approach for my business?" Drawing from my extensive background spanning over two decades in agile methodologies and project management, I've embarked on a journey to demystify the myriad of agile practices through a unique, albeit imperfect, classification scheme. Envisioning agile methodologies in a 2.5-dimensional framework, I've mapped them against two principal axes. The vertical (y-axis) represents the complexity of the system at hand, viewing it through the lens of subsystem interactions. Complexity scales from single teams or processes, which are relatively straightforward, to intricate networks involving multiple stakeholders and initiatives, each layer adding a degree of sophistication. On the horizontal (x-axis), we measure efficiency, defined here in the classical sense of outcome over effort. This dimension introduces us to various management strategies, from the basic cadence-bound methods, which, despite their simplicity, often result in significant downtime and necessitate frequent coordination, to the more advanced constraint-based approaches. These aim to optimize the key bottlenecks within a system, minimizing work-in-progress and lead times while maximizing output. Between these extremes lie replenishment-based methods, which improve upon cadence-bound strategies by eliminating unnecessary idle time and allowing for more flexible work allocation. Yet, there's a third aspect to consider, not fully dimensional but crucial — the nature of the work being executed. This divides into two categories: production-oriented tasks, characterized by a low touch-time to lead-time ratio, and project-oriented tasks, which have a higher ratio and numerous dependencies. This distinction is vital, especially in environments where innovation and time sensitivity are paramount. By pondering three critical questions regarding your system's complexity, your management simplicity tolerance, and the character of your work, you can navigate this framework to identify or tailor an agile methodology that aligns with your unique needs. In essence, this exploration doesn't champion one agile method over another; instead, it offers a lens through which to evaluate and select the most fitting approach for your specific circumstances. Through this matrix, the path to optimizing your project management strategy becomes clearer, encouraging a more informed and nuanced discussion on agile methodologies. What do you think - does this make sense? Wolfram

𝐘𝐨𝐮𝐫 𝐫𝐨𝐚𝐝𝐦𝐚𝐩 𝐢𝐬𝐧'𝐭 𝐝𝐞𝐥𝐚𝐲𝐞𝐝 𝐛𝐲 𝐜𝐨𝐦𝐩𝐥𝐞𝐱𝐢𝐭𝐲. 𝐈𝐭'𝐬 𝐝𝐞𝐥𝐚𝐲𝐞𝐝 𝐛𝐞𝐜𝐚𝐮𝐬𝐞 𝐨𝐟 𝐜𝐨𝐮𝐩𝐥𝐢𝐧𝐠. Shared services seem efficient. Centralized platforms ensure consistency. Reusable components help cut duplication. Then reality hits. One team waits for another. A simple feature requires three approvals. Your fastest engineers spend their time in coordination meetings instead of delivering code. Dependencies not only create technical constraints but also cause organizational bottlenecks. Each shared service turns into a queue. Each integration point becomes a negotiation. Every coupling requires synchronization—and synchronization leads to waiting. Teams optimize locally while the system degrades globally. They build workarounds. They duplicate secretly. They stop asking for help because asking takes longer than hacking. Autonomy isn't about creating silos. It's about removing the structural barriers that prevent teams from working together. The best architectures are not judged by elegance or reuse. They're judged by how quickly independent teams can deliver without approval. 𝐖𝐡𝐚𝐭 𝐰𝐨𝐮𝐥𝐝 𝐜𝐡𝐚𝐧𝐠𝐞 𝐢𝐟 𝐲𝐨𝐮𝐫 𝐭𝐞𝐚𝐦𝐬 𝐜𝐨𝐮𝐥𝐝 𝐬𝐡𝐢𝐩 𝐰𝐢𝐭𝐡𝐨𝐮𝐭 𝐜𝐫𝐨𝐬𝐬-𝐭𝐞𝐚𝐦 𝐝𝐞𝐩𝐞𝐧𝐝𝐞𝐧𝐜𝐢𝐞𝐬?

What broke my projects wasn’t complexity. It was control. I learned this the hard way managing a 300-person project team. Every approval through me.  Every decision waiting on my calendar. Projects stalled.  Teams frustrated.  I became the bottleneck. 𝗧𝗵𝗲 𝗿𝗲𝗮𝗹𝗶𝘁𝘆: You can't scale yourself.  But you can scale your systems. 𝗧𝗵𝗲 𝘀𝗵𝗶𝗳𝘁: From control to guardrails. Instead of managing people, I built systems that managed 𝘰𝘶𝘵𝘤𝘰𝘮𝘦𝘴: 𝗥𝗔𝗖𝗜 𝗺𝗮𝘁𝗿𝗶𝗰𝗲𝘀 𝗳𝗼𝗿 𝗲𝘃𝗲𝗿𝘆 𝘄𝗼𝗿𝗸𝘀𝘁𝗿𝗲𝗮𝗺 ↳ No more "who's responsible for this?" 𝗔𝘂𝘁𝗼𝗺𝗮𝘁𝗲𝗱 𝗿𝗲𝗱/𝘆𝗲𝗹𝗹𝗼𝘄/𝗴𝗿𝗲𝗲𝗻 𝗱𝗮𝘀𝗵𝗯𝗼𝗮𝗿𝗱𝘀 ↳ Issues surfaced before they became crises 𝗦𝘁𝗮𝗻𝗱𝗮𝗿𝗱 𝗲𝘀𝗰𝗮𝗹𝗮𝘁𝗶𝗼𝗻 𝘁𝗵𝗿𝗲𝘀𝗵𝗼𝗹𝗱𝘀 ↳ Teams knew exactly when to involve leadership 𝗪𝗲𝗲𝗸𝗹𝘆 𝗽𝘂𝗹𝘀𝗲 𝘀𝘂𝗿𝘃𝗲𝘆𝘀 ↳ Real-time team health without micromanaging mood 𝗞𝗲𝘆 𝗯𝗿𝗲𝗮𝗸𝘁𝗵𝗿𝗼𝘂𝗴𝗵: Decision authority maps.  Every team member knew their $30K, $100K, and $250K boundaries. Below their threshold? Move fast. Above it? Escalate with context, not questions. 𝗧𝗵𝗲 𝗿𝗲𝘀𝘂𝗹𝘁𝘀: Projects delivered faster. Team morale scores soared. My meetings dropped by half. But here's what surprised me: Teams felt 𝘮𝘰𝘳𝘦 supported, not less managed. Clear boundaries created the confidence to act. 𝗦𝘆𝘀𝘁𝗲𝗺𝘀 𝗱𝗼𝗻'𝘁 𝗿𝗲𝗽𝗹𝗮𝗰𝗲 𝘁𝗿𝘂𝘀𝘁. They enable trust to scale. 💬 What's one management task you could systematize this week? ♻️ Share if you've hit the micromanagement wall. Image by Roberto Ferraro

Taming the Complexity Beast: Why LLMs are the Future of Requirements Management Developing complex mechatronic systems today is a massive challenge. We are often dealing with several hundred thousand requirements that must be structured, quality-assured, and rigorously monitored for coverage. For human teams alone, maintaining this level of oversight is becoming nearly impossible. However, because Requirements Management is inherently text-heavy, the barrier to entry for applying Large Language Models (LLMs) is surprisingly moderate and the potential impact is huge. In our recently published White Paper (https://lnkd.in/ez6eQCM9), we analyzed the current landscape and identified three distinct classes of AI applications in RM that are already proving their worth in both academia and industrial practice: 1️⃣ Requirement Generation: Translating vague and heterogeneous stakeholder needs into technically precise specifications is a challenge. LLMs act as a bridge here. They can sift through vast amounts of unstructured text to extract key information, translate inputs into technically valid requirements, and integrate them directly into structured requirement models. 2️⃣ Requirement Optimization: Writing the requirement is just step one. In highly complex systems, requirements change over time. AI agents can continuously monitor the database to check for ambiguity, consistency, completeness, conflicts, and regulatory compliance. This allows organizations to maintain healthy requirement ecosystems with manageable human resource efforts. 3️⃣ Traceability Creation: Perhaps the most critical aspect is establishing traceability along the entire product development process, specifically across RFLPT (Requirements, Functional, Logical, Physical, Test) artifacts. LLMs can significantly accelerate this by predicting link candidates and rigorously monitoring the coverage of requirements against test cases. The synergy between LLMs and Requirements Management is not just a trend. It is a necessity for handling modern system complexity. We are moving from static databases to intelligent, AI-assisted engineering. Vlad Larichev | Timo Altmann | Yannik Dahmann | Garrett Graham | Rick Bouter #SystemsEngineering #RequirementsManagement #ArtificialIntelligence

🤔 How can large, complex projects navigate the complexities of systems integration? We introduce the concept of "disciplined flexibility" as a strategic approach to maintain stability while adapting to evolving challenges throughout the project lifecycle in "The dynamics of systems integration: Balancing stability and change on London's Crossrail project", coauthored with Kesavan Muruganandan Andrew Davies and Juliano Denicol in International Journal of Project Management 🔗 Read the full article https://lnkd.in/gVw8spkk (CC BY license) Key Insights: 🔹 "Disciplined flexibility" as a dynamic process of maintaining stability, while responding flexibly to changing conditions 🔹 Challenge of complex systems with interdependent systems at different degrees of maturity. 🔹 Strategies for ongoing monitoring and control to ensure successful integration. 🔹 Reciprocal interdependencies at both system and system-of-systems levels. Abstract Systems integration is essential for the design and execution of large, complex projects, but relatively little is known about how this task develops over time during the life cycle of a project. This paper builds on the concept of “disciplined flexibility” to describe how systems integration can be conceived as a dynamic process of maintaining stability, while responding flexibly to changing conditions. We examine the dynamics of systems integration through a case-study of Crossrail, the construction of London’s new urban railway system, which will be called the Elizabeth Line when it opens for service. The balancing act of stability and change manifests during critical periods of the project life cycle as various interdependent systems evolve with different degrees of maturity. We identify how various types of reciprocal interdependencies in complex projects such as Crossrail – at the system and system of systems levels – require ongoing monitoring and control, and the mutual adjustment of tasks.  Reference as: Muruganandan, K., Davies, A., Denicol, J., & Whyte, J. (2022). The dynamics of systems integration: Balancing stability and change on London's Crossrail project. International Journal of Project Management, 40(6), 608-623. I would love to hear from you if you're interested in complex projects and systems integration. This is an invitation to explore our findings and consider how they might inform your own work. Your feedback and discussions are always welcome! #SystemsIntegration #Infrastructure #Megaprojects #ProjectManagement #Research #OpenAccess #IJPM

When I first started consulting, behavioural science was easy. Identify drivers and barriers. Design clever nudges. Evaluate impact. But something was missing in my toolkit. As a behavioural scientist, I was trained on spending time and effort irrespective of whether it was the right or wrong problem to solve. This 'Cake Rocket Child' tool (goes by many names) can help you consider the nature of the problem and whether your approach is appropriate for that kind of problem. Ask yourself: What kind of problem am I actually trying to solve? 🍰 Simple (baking a cake): Follow a recipe and you get predictable results. 🚀 Complicated (sending a rocket to space): Requires expertise and coordination, but still solvable with the right process. 👶 Child (e.g raising a child): Every situation is different. Relationships matter. No formula guarantees success. 🌪 Wicked problems (e.g. preventing biodiversity loss): Multi-causal, contested, and constantly evolving. No single organisation can solve them. This is from the Systems Practice Toolkit by NPC (New Philanthropy Capital) a practical guide for people working with complexity. Alongside this tool, the guide introduces other helpful lenses and canvases for your systems practice: • Iceberg Model — events → patterns → structures → mental models • Complexity Canvas — understanding how complex systems behave • Systems Mapping — visualising relationships and feedback loops • A learning cycle of Understand → Design → Act → Learn Personally, the shift to thinking in systems is a massive confidence boost to solving our most pressing social challenges (e.g. sustainable transport, financial wellbeing, tackling fake news & misinformation). Before designing nudges, locate the nature of the problem. ♻️ Share this with purpose-driven leaders working on wicked problems.

The Fab Whisperer: Cost of Fab Complexity Across fabs today, performance rarely degrades because something breaks. It degrades because complexity quietly outpaces the fab’s ability to manage it. Not the visible kind of complexity. The hidden, compounding kind. More products. More routes. More recipes. More scheduling priority classes. More scheduling exceptions - fraction of lots with 1 or more rule override. More local optimizations. Each addition makes sense on its own. Together, they change how the system behaves. The cost doesn’t show up as a single failure or a red KPI. It shows up as slower decisions, fragile schedules, more escalations to keep flow moving, and growing dependence on heroics. Throughput doesn’t collapse. It leaks. One thing I see repeatedly is that fabs feel complexity — but struggle to quantify it and make complexity visible. Here, I will suggest two concepts that may help. 1. The Complexity Index A simple way to describe the structural load placed on the fab. Think of it as a function of product or technology counts, route variants, recipe/configuration variants, priority classes, and exception rate compared with baseline complexity. This index would be computed as a product of listed complexity factors. If we define Complexity Index = products × routes × recipe variants × priority classes × exception rate. Then, complexity ratio will be: Current complexity Index ÷ baseline complexity index. As this index grows, coordination effort, dispatch instability, and decision latency grow non-linearly — even if tools, headcount, and nominal KPIs stay flat. 2. The Complexity Cost Ratio (CCR) This is where complexity becomes an investment conversation. CCR = tools (or capacity in WSPM) required at current complexity index ÷ tools required at baseline complexity index A CCR > 1.0 means the fab effectively needs more equipment capacity to deliver the same output because complexity is consuming capacity. That usually hides in lost effective throughput, longer cycle time and higher WIP, extra coordination and management effort, and more frequent recoveries and overrides. Most fabs I engage with still treat complexity as “the cost of doing business” and struggle with quantifying it as a capacity tax — something to be engineered, constrained, and actively managed. That paradigm shift changes investment logic. Complexity reduction becomes a capacity investment, decision automation becomes a throughput lever, and process simplification pays back with CAPEX avoidance. The fabs that win will be the ones that learn how to operate with complexity — without letting it quietly consume throughput, cycle time, and focus. Which factor do you see causing your Complexity Index to rise fastest today? #TheFabWhisperer #Semiconductor #FabOperations #ManufacturingSystems #Complexity #Capacity #OperationalExcellence