| Case element | Description |
|---|---|
| Company | PE-backed robotics components company |
| Situation | Preparing to scale internationally |
| Business condition | Strong business, clear strategy, capable people, investor backing |
| Critical decision | Whether to accelerate from project-led delivery into a repeatable platform model |
| Felt weight | More interpretation, coordination, exception handling, and leadership energy than expected |
| Four Books question | Does the platform decision still hold under the conditions it now faces? |
| Leadership question | What may be underneath |
|---|---|
| Why does this decision need so much interpretation across teams? | Decision language may be fragmenting |
| Why do customer commitments differ across regions? | Commercial logic may not fully match repeatability |
| Why is product standardisation harder in delivery? | Product intent may not yet carry through operations |
| Why is finance unsure where coordination cost will appear? | Margin logic may not reflect real execution cost |
| Why does alignment at the top lose precision in execution? | Transmission may be weakening |
| Why does every scaling step create more exceptions? | The platform model may not yet be stable enough to scale |
| Dimension | What Four Books looks for |
|---|---|
| Strategic logic | Does the platform decision still support the company’s ambition? |
| Commercial reality | Are customer commitments aligned with repeatability? |
| Product direction | Is the intended platform logic clear enough to carry across markets? |
| Engineering | Are technical dependencies visible and stable enough? |
| Operations | Are exceptions still manageable or becoming structural? |
| Supply chain | Can the model carry across geographies and delivery conditions? |
| Finance | Does the margin logic still hold once coordination cost is included? |
| Ownership | Are decision rights and accountability clear enough? |
| Time | Is reversibility still available before further scale is added? |
| From | To |
|---|---|
| “This feels heavier than expected.” | “We can now see where it holds, where it weakens, how much, and why.” |
| “The decision is broadly aligned.” | “We know where alignment carries and where it loses precision.” |
| “The platform direction is right.” | “We know what must be stabilised before more scale is added.” |
| “Finance sees the ambition.” | “Finance can see which assumptions still hold.” |
| “Leadership is compensating.” | “Accountability is explicit.” |
| Continue | Stabilise | Do not yet scale further |
|---|---|---|
| What already holds | What weakens but can be corrected | What would compound unnecessarily |
| What is strong enough to carry | What needs clearer ownership, assumptions, or coordination | What should wait until the weak part is visible and contained |
| What should be left alone | What should be adjusted | What should not receive more capital, coordination, or time yet |
| Case element | Description |
|---|---|
| Company | Same PE-backed robotics components company |
| Situation | Further into execution |
| Business condition | Strategy still valid, ambition strong, market opportunity real |
| Felt weight | Execution requires more effort, coordination, and leadership energy |
| Core truth | The old way was not wrong. The weight has changed. |
| CP question | Where is execution carrying more than expected, and what must be stabilised so more carries through? |
| Leadership Question | What may be underneath |
|---|---|
| Why do commercial promises create operational drag? | Customer commitments may not carry cleanly into delivery |
| Why do product decisions not fully carry through? | Product-to-execution translation may be weak |
| Why are engineering priorities clear locally but not across functions? | Cross-functional carry may be fragmenting |
| Why does production planning depend on individual knowledge? | Repeatability may not yet be strong enough |
| Why does finance see growth but not enough repeatability? | Cost-to-serve assumptions may be unstable |
| Why are meetings solving too many exceptions? | Execution may be scaling exceptions instead of patterns |
| Continue | Stabilise | Stop scaling as-is |
|---|---|---|
| What already works | What is almost right but needs support | What depends too much on exceptions |
| What carries through cleanly | What needs clearer ownership | What creates repeated drag |
| What should be left intact | What must be adjusted so more carries through | What risks becoming structural weight |