Ownership models that survive handovers

Blueprints die when “QA owns everything” is the only line under ownership. QA cannot review every product fixture change across squads. Planning sessions spend real time naming owners by layer.

Patterns that hold

• Platform fixtures owned by a platform or quality enablement pair
• Domain checks owned by the squad that ships the domain
• Merge rules that require a domain reviewer when a check touches that domain’s journeys

Review gates without theatre

A gate that only checks “file exists” teaches nothing. Prefer a short checklist: naming, isolation, and whether the assertion matches the risk card from strategy work. We write that checklist into the blueprint so it is not tribal knowledge.

After we leave

Ask who will update the blueprint when a layer changes. If the answer is silence, schedule a 60-minute internal review each quarter—even without us in the room.