Inspire, develop, and guide a winning organization.
Create visible workflows to achieve well-architected software.
Understand and use meaningful data to measure success.
Integrate and automate quality, security, and compliance into daily work.
Understand the unique values and behaviors of a successful organization.
LLMs and Generative AI in the enterprise.
An on-demand learning experience from the people who brought you The Phoenix Project, Team Topologies, Accelerate, and more.
Learn how making work visible, value stream management, and flow metrics can affect change in your organization.
Clarify team interactions for fast flow using simple sense-making approaches and tools.
Multiple award-winning CTO, researcher, and bestselling author Gene Kim hosts enterprise technology and business leaders.
In the first part of this two-part episode of The Idealcast, Gene Kim speaks with Dr. Ron Westrum, Emeritus Professor of Sociology at Eastern Michigan University.
In the first episode of Season 2 of The Idealcast, Gene Kim speaks with Admiral John Richardson, who served as Chief of Naval Operations for four years.
New half-day virtual events with live watch parties worldwide!
DevOps best practices, case studies, organizational change, ways of working, and the latest thinking affecting business and technology leadership.
Is slowify a real word?
Could right fit help talent discover more meaning and satisfaction at work and help companies find lost productivity?
The values and philosophies that frame the processes, procedures, and practices of DevOps.
This post presents the four key metrics to measure software delivery performance.
November 15, 2023
This post is adapted from Wiring the Winning Organization: Liberating Our Collective Greatness Through Slowification, Simplification, and Amplification.
In our previous post, we presented a vignette of Gene and Steve renovating an old Victorian hotel. The problems that Gene and Steve grappled with are likely familiar to anyone who has ever worked in a functionally oriented organization—where people are divided based on their specialties. Leaders in these organizations often assume things will naturally self-organize or that schedules can always integrate those specialties toward a common purpose. They often neglect, as Gene and Steve did, the careful design of their organizational wiring (Layer 3).
Before we explain what Gene and Steve did to get things right, let’s first analyze and reflect on what they did to get things so badly wrong. How did they miswire their Layer 3 so dismally?
At first, Gene and Steve did not coordinate the efforts of the movers and painters at all, resulting in their starting at opposite ends of the building. Next, they tried to use a schedule as the coordination and integration mechanism but were still unable to get the movers and painters where they needed to be when they needed to be there.
What Gene and Steve did not appreciate is that scheduling a project of this complexity, let alone one of even greater complexity, is nearly impossible. They were unable to get sufficiently accurate forecasts of how much time the movers and painters needed to complete their work, nor were they ever able to get adequately complete and timely information from everyone in their system to tell people where to go.
But even if they had all that information, creating an accurate schedule is still hopeless. It was mathematically proven over fifty years ago that it is often impossible to compute a correct and optimal scheduling solution in finite time for schedules of any significant size. Gene and Steve created the best schedule they could in their spreadsheet, based on insufficient detail, guaranteeing a poor schedule and their dismal outcomes.
Gene and Steve also tried expediting, having movers and painters drop whatever they were doing to do something “more urgent.” The resulting chaos they experienced is not an exaggeration.
In settings where there is a daily production schedule, such as in manufacturing or IT operations, many of us have experienced morning production control meetings, daily review meetings, and so forth. After schedules have been released, managers start generating hot lists (the list of urgent schedule changes), super hot lists, and extra hot lists, all while shop floor supervisors are running about trying to expedite, firefight, and reroute workflows for “blocking” of upstream work by downstream work and “starving” of downstream work by upstream work.
Furthermore, notice how their system couples everyone to everyone else—if any mover or painter runs late, they quickly cause other rooms to become late, and the lateness spreads like a contagion. In this system, small problems quickly become large problems. As a result, expediting may provide some immediate gratification but actually makes matters worse.
As they did in scheduling, Gene and Steve ran into another theoretical limitation, this time for control systems. Their ability to see and solve problems was not able to keep up with the frequency, speed, or detail of the work of the movers and painters they were trying to coordinate and control. Gene and Steve created the best schedule they could in their spreadsheet, based on insufficient detail, guaranteeing a poor schedule and their dismal outcomes.
Note how any isolated performance measure, such as “number of pieces of furniture moved” or “number of walls painted,” did not improve overall performance—and may likely make things worse.
For instance, to meet the furniture-moving goals, movers may start moving rooms before they are needed, jeopardizing the rooms that actually need moving. One can even imagine a situation where they “over produce” and run out of space to store the furniture.
At this point, we have illustrated how Gene and Steve’s social circuitry (Layer 3) was profoundly unsuited for the work of the movers and painters (Layers 1 and 2). In mathematics, there is a term for this: isomorphism. Isomorphism is the quality of related items having similar structures. In the simplest case, the work of refurbishing a room requires movers to clear out the furniture, which signals the painters to begin their work, who, upon completion, signal the movers to bring the furniture back in when the paint is dry to the touch.
But consider how the information travels in Gene and Steve’s Layer 3 wiring, which did not flow in anything like this pattern. Instead, information traveled from painters and movers when they completed their work to Gene and Steve, who would determine what people should actually be doing rather than what they were doing. Then, they sent instructions (information) back to the movers and painters.
The work, in effect, was flowing linearly through time, whereas the information had to be moved (with great effort) vertically, up and down silos. The “structural” problem was that the people who really needed to be in direct communication with each other were not. All information had to be processed through Gene and Steve as opposed to flowing directly between the movers and painters. The resulting problem (dynamics) was as described: scheduling and expediting occurred with a frequency, speed, and detail completely inadequate for the frequency, speed, and detail with which work was being done.
It is clear that Gene and Steve created organizational wiring that was incongruent, or not isomorphic, to the work being done. (We will explore this in more detail in Part III: Simplification.)
Gene and Steve created Layer 3 wiring that resulted in a system where movers and painters were working in nothing remotely resembling a unified and coherent whole. The functional silos divided the people who needed to coordinate and collaborate frequently and intensely. The only mechanism their system gave them to coordinate was escalating to Steve and Gene.
Let us marvel for just a moment at how thoroughly we can screw up even this relatively simple system, placing Gene and Steve very much in the danger zone. Of course, the consequences are graver in situations that are more complex, across all the dimensions of frequency, complexity, variety, consequence, speed, information density, the number of functional specialties, and so forth.
In our next post, we’ll return to Gene and Steve’s story to see what they do to rewire the system to move them into the winning zone.
Learn more about Wiring the Winning Organization here.
Gene Kim is a best-selling author whose books have sold over 1 million copies. He authored the widely acclaimed book "The Unicorn Project," which became a Wall Street Journal bestseller. Additionally, he co-authored several other influential works, including "The Phoenix Project," "The DevOps Handbook," and the award-winning "Accelerate," which received the prestigious Shingo Publication Award. His latest book, “Wiring the Winning Organization,” co-authored with Dr. Steven Spear, was released in November 2023.
Dr. Steven J. Spear (DBA MS MS) is principal for HVE LLC, the award-winning author of The High-Velocity Edge, and patent holder for the See to Solve Real Time Alert System. A Senior Lecturer at MIT’s Sloan School and a Senior Fellow at the Institute, Dr. Spear’s work focuses on accelerating learning dynamics within organizations so that they know better and faster what to do and how to do it. This has been informed and tested in practice in multiple industries including heavy industry, high tech design, biopharm R&D, healthcare delivery and other social services, US Army rapid equipping, and US Navy readiness.
No comments found
Your email address will not be published.
First Name Last Name
Δ
You've been there before: standing in front of your team, announcing a major technological…
If you haven’t already read Unbundling the Enterprise: APIs, Optionality, and the Science of…
Organizations face critical decisions when selecting cloud service providers (CSPs). A recent paper titled…
We're thrilled to announce the release of The Phoenix Project: A Graphic Novel (Volume…