Governance

Documents an architecture decision with context, alternatives, and consequences so later reviews remain traceable.

Core question: Which architecture decision are we making in this context, why choose it and which consequences does it carry?

• 15-45 min
• 1-3

Clarifies responsibility for tasks and deliverables, exposes gaps or overload, and improves alignment.

Core question: Which role performs each activity, owns the outcome, is consulted, or is informed?

• 45-90 min
• 2-8

Describes the preferred default path for common use cases and adds templates, checks, and exceptions.

Core question: How does a team reliably move from entry to an operable result in the supported standard case?

• 1-3 Tage Setup, laufend
• 2-8

Clarifies roles for driver, approver, contributors, and informed and records the decision in a solid matrix.

Core question: Who drives this decision, who decides, who provides input and who needs to know the result?

• 30-60 min
• 2-10

Arranges decision responsibility across five roles and makes recommendation, input, and follow-up unambiguous.

Core question: Who recommends, must agree, provides input, decides and executes the decision?

• 45-90 min
• 3-12

Moves scope, sequence, and delivery flow toward a concrete result through "create a table for Risks, Assumptions, Issues, and Dependencies", "carry over initial entries from discovery and kickoff", and "archive resolved items instead of deleting them".

Core question: Which open Risks, Assumptions, Issues, and Dependencies threaten the next commitment, and who will do what by when?

• 30 min Setup, dann laufend
• 1-3 maintaining, briefing for everyone

Moves group input, selection, and decision toward a concrete result through "prepare the stakeholder list", "define power, legitimacy, and urgency", and "derive strategy by class".

Core question: Which stakeholder claims possess power, legitimacy, and urgency in this decision, and what attention follows?

• 60-90 min
• 3-6

Moves options, criteria, and risks toward a concrete result through "identify key decision types", "collect roles", and "document and communicate the agreement".

Core question: Who recommends, provides input, must agree, decides once, and performs this specific decision?

• 90-180 min
• 4-12

Uses a structured proposal and review process to make non-trivial technical or product changes discussable and decidable.

Core question: Is the proposal decision-ready with alternatives, consequences, and a migration path?

• 1-3 Wochen vom Draft bis zur Entscheidung
• 3-20 Reviewer

Connects strategy development, translation, operational planning, monitoring, and adjustment into a repeatable leadership cycle.

Core question: How do we close the loop from strategy through operations to learning and adaptation?

• Initial 3-6 h, then monthly or quarterly reviews
• 5-12

Separates planning levels by time horizon, decision type, and control logic, so strategy does not get mixed up with day-to-day business.

Core question: How is strategic direction translated into tactical capabilities and operational work without losing feedback?

• 90-180 min
• 4-12