Dr-David-C.Com

In the world of software, no one releases a product without a Beta version. In the world of architecture, no one builds a skyscraper without a scale model. Yet, in organizational design, leaders often spend six months in a dark room and then “go live” with a 5,000-person re-org on a Monday morning.

This is a recipe for a catastrophic system crash. Episode 3 is about Prototyping—running “Safe-to-Fail” experiments to see if your theoretical “Future State” can survive a Tuesday morning in the real world.

The Core Concept: The “Organizational Sandbox”

A prototype is a contained version of your new design. You aren’t changing the whole company; you are changing one department, one product squad, or one specific process. The goal isn’t to be “perfect”; the goal is to break the design early so you can fix it before the stakes are high.

The Framework: The “Pilot” Design Canvas

Before you run a prototype, you must define the boundaries of the “Sandbox.”

1. Scope: Which specific “Box” or “Process” are we testing? (e.g., The “New Product Development” squad).
2. Hypothesis: “If we move decision rights to the squad leader, our speed-to-market will increase by 20%.”
3. Duration: Run the test for 30–90 days. Anything shorter isn’t a test; it’s a distraction.
4. The “Kill Switch”: What is the one metric that, if it drops, means we stop the experiment immediately? (e.g., Customer churn).

Three Ways to Prototype Without a Re-org

• The Shadow Team: Keep the formal structure as-is, but create a temporary “Strike Team” that operates under the new rules (e.g., new reporting lines, new RAPID matrix).
• The “Zero-Meeting” Week: Test your Process point on the Star Model. For one week, ban all internal coordination meetings and force the team to use the new asynchronous tools you planned for the redesign.
• The Decision Proxy: Give a junior manager the “Decide” (D) right on a mid-level project. Observe where the friction occurs. Does the senior leader struggle to let go? Does the junior leader lack the data?

The Actionable Insight: The “Retrospective” Ritual

At the end of the prototype, you don’t ask “Did it work?” You ask: “Where did the design leak?”

• Where did people go back to their “old” habits?
• Which new “reporting line” felt confusing?
• Which tool was ignored?

The Design Fix: Use the data from your prototype to refine the “To-Be” map. It is much easier to move a line on a PowerPoint slide after a failed pilot than it is to undo a global announcement.

Tomorrow’s Preview

In Episode 4, we do the “Clean Sheet” Exercise. We’ll strip away the baggage of your history and ask the most important question in design: If you were starting this company today, what would it look like?