Decision Rights
Clarify who has authority to make which decisions.
Explanation
Unclear decision-making authority kills team speed and creates frustration. People either make decisions they shouldn't or avoid making decisions they should. Clear decision rights eliminate this confusion by explicitly stating who owns what types of decisions and what input they need before deciding.
Real-World Example
Team lead can make hiring decisions up to certain level with input from team. Budget decisions over $X require manager approval. Technical architecture decisions belong to senior engineer with consultation from team. Customer policy changes require product manager approval with legal review. Clear boundaries eliminate guesswork.
How to Apply
List all recurring decisions your team makes. For each, specify: Who makes the final call? Who must be consulted? Who should be informed? What's the escalation path? Document and share widely. When new decisions arise, quickly clarify who owns it. Review and update quarterly as team and responsibilities evolve.