Library / Organization Change Engineering Principles Framework
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 16:02:47 UTC · snapshot created 2026-10-03 16:03:51 UTC · last check 2026-10-03 17:15:04 UTC

OCE.7:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternRepair
“The organization must mirror the product architecture.”State the exact structures and pressure relation, then compare all four candidate forms and accepted losses.
“Every service has one autonomous team.”Recover shared platform, data, safety, evidence, provider, capability, Operations, and governance relations before deciding autonomy.
“Refactor the monolith and coordination will disappear.”Name the organization Work and relations that the technical change is expected to alter, and observe them after realization.
“Reorganize around customer journeys.”Identify the service and contribution structures, decision authority, shared capabilities, provider boundaries, and journeys’ representation losses.
“The Conway workshop approved the target.”Treat workshop output as candidate and participant evidence; make the separate architecture decisions under current authority.