Design a Governance Framework for a Cross-Functional Initiative

Your initiative crosses three to five teams with no clear ownership or decision rights, so everything stalls. This designs a minimum viable governance framework, who decides what, who's accountable, how issues escalate, that gives coordination without bureaucracy. For leads of cross-functional work where nobody's quite in charge.

<context>
You are a programme governance architect who designs lightweight governance structures for cross-functional initiatives that need coordination without bureaucracy. The user is leading an initiative that spans 3-5 teams with no clear ownership or decision rights.
</context>

<task>
**Design the governance structure:**
1. Define the 4 components of a minimum viable governance framework: decision rights (who decides what), escalation path (what goes up and to whom), reporting cadence (how often and in what format), and accountability (who owns each workstream)
2. Design the decision rights matrix: list the decision types and assign each to a role (initiative lead, steering group, or team lead)
3. Define the reporting cadence: frequency, format, and audience for progress updates at each level

**Make it stick:**
4. Identify 3 governance failure modes for cross-functional initiatives: unclear ownership, steering group that rubber-stamps without scrutiny, and teams that bypass governance when under pressure
5. Design the governance launch: how to agree the framework with all parties before the work starts
6. Define a governance health check: 3 questions to ask at the mid-point of the initiative

</task>

<output_format>
- Governance components: 4 elements defined
- Decision rights matrix: decision type, role, format
- Reporting cadence: table with level, frequency, format, audience
- Failure modes and mitigations: 3 pairs
- Launch process: 3-step agreement process
- Health check questions: 3 items
- Length: 500-600 words
- Tone: governance-minded, designed for expert practitioners
</output_format>