by Brent Voelker
May 26, 2026
Without explicitly saying so, in recent posts we have been exploring some of the hallmarks of a High Reliability Organization (HRO). One hallmark we previously discussed was Vigilance for Failure. In this post, we will consider another: Command of Complexity.
But first, what is an HRO? These are organizations that operate in complex, high-risk environments but consistently maintain a very low rate of errors, defects, or accidents. High reliability companies and institutions consistently achieve positive results despite the high potential for negative outcomes inherent in the environment in which they operate.
In the context of new product development, an HRO is a team engaged in the development of complex, high-risk products that consistently maintains a very low rate of errors or defects. In other words, an HRO can be counted on to deliver high-quality, high-performance and reliable products – on time and under budget.
In Managing the Unexpected, Karl Weick and Kathleen Sutcliffe identify a “reluctance to simplify” as a core principle of HROs, emphasizing the importance of preserving complexity rather than reducing it prematurely. They argue that simplifying interpretations can obscure critical nuances, mask early warning signs, and lead to flawed decision-making. In complex, tightly coupled systems, small details often matter, so oversimplified explanations increase the risk of overlooking subtle interactions that can escalate into major failures.
By resisting the urge to reduce complexity into overly neat or convenient narratives, teams remain alert to weak signals, unexpected interactions, and hidden dependencies. In practice, this means encouraging diverse perspectives, questioning assumptions, and deliberately exploring alternative explanations, even when a problem appears straightforward on the surface.
But engineering requires us to break down complex systems into simpler, real-world components, to break apart multi-dimensional problems into ones we can actually solve. Further, we can’t afford to dwell without end, wringing our hands and talking about the dozens of ways complicated interactions may yield poor results. How can we operationalize this concept through processes and tools we can actually manage?
Novellum Partners reframes this idea with the phrase “Command of Complexity,” shifting the mindset from passive mindfulness to active mastery. Rather than simply avoiding oversimplification, organizations take command of complexity by deliberately equipping themselves to track, understand, navigate, and manage it. This framing emphasizes capability: developing tools, processes, and the discipline necessary to allow teams to confidently operate within intricate systems. It highlights that complexity is not merely a hazard to be minimized, but a reality to be managed with rigor, insight, and structured approaches that maintain clarity without sacrificing fidelity.
System engineering practices provide the foundation for achieving this command. Through disciplined decomposition, engineers break large, complex systems into manageable subsystems, components, and interfaces. This process enables teams to focus on smaller, well-defined problem sets without losing sight of the broader system context. Techniques such as functional decomposition, interface definition, and model-based design (MBD) ensure that each piece of the system is understood both independently and as part of the whole. Critically, this structured breakdown avoids the trap of oversimplification because it preserves the relationships and dependencies that give rise to system behavior.
At the core of this capability is traceability within requirements management, which acts as the connective tissue across all levels of system design. Traceability connects detailed subsystem requirements, design elements, and verification activities upward to high-level mission objectives and stakeholder needs. This linking ensures that every component can be traced back to its purpose – which provides the criteria for validation – while also revealing how changes or failures in one area may propagate across the system. By maintaining these connections, teams can simplify work into actionable segments while retaining full visibility into system-wide impacts. Traceability operationalizes command of complexity: it allows organizations to manage complexity pragmatically, breaking it down enough to act effectively yet preserving the intricate web of relationships that must be mastered to obtain high reliability and performance.
Novellum Partners can help your company seize command of complexity and leverage it to competitive advantage. Call us today.