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

Anti-pattern	Repair
“Create product teams and define interfaces.”	Name the contribution and Work basis for each boundary, then write separate possible-future specifications for supplied-result, decision, information-use, access, service, and coordination relations.
“One owner per deliverable.”	Recover the result, receiver, acceptance decision, contributing Systems, authority, and exception path; choose an ownership predicate only when it is actually governed.
“Put everyone involved in one team.”	Select the smallest contribution-bearing boundaries and preserve scarce capability homes, independent acceptance, providers, and continuing service where they change the decision.
“The matrix has two reporting lines.”	State which contribution, decision, authority, access, or coordination relation each line is intended to represent.
“The architecture is now implemented.”	Compare actual Work and obtaining relations after change; retain the current item as decision and possible-future description until then.