Decision Roles & Routines

Clarify who decides, who advises, and how decisions move forward—so teams spend less time debating and more time doing, learning, and improving.

Why this matters

Unclear decision ownership is one of the most common causes of slow execution, repeated arguments, and hidden blame. When teams name roles and pair them with repeatable routines—short meeting recipes, clear escalation paths, and a simple way to record decisions—they gain speed, reduce rework, and build institutional knowledge about why choices were made.

What you’ll understand and be able to do

After using this resource you will be able to:

• Define practical decision roles (decider, advisor, contributor) that fit your team’s size and culture.
• Choose lightweight meeting recipes for common decision types (tactical, cross-functional, strategic) that balance information sharing and closure.
• Design simple escalation paths so disagreements surface early and resolve predictably.
• Create a minimal decision record that captures options, trade-offs, owner, and review date so decisions become learnable assets.

Practical examples across settings

Small business: A restaurant manager clarifies that the floor manager is the decider for shift staffing, the head chef is an advisor on menu constraints, and servers are contributors who report customer flow data.

Healthcare unit: A ward adopts a 10‑minute huddle recipe for equipment allocation, names a clinical lead as decider for day shifts, and routes unresolved conflicts to a staffing coordinator via a defined escalation.

Manufacturing team: Engineers and operators use a pre-shift decision checklist to resolve maintenance priorities; the plant manager has final sign-off for capital requests following the documented routine.

How this fits into the Organizational Intelligence ecosystem

This resource is a practical component of the Decision Quality Playbook and the broader Organizational Intelligence domain: it turns decision theory into repeatable team practices that accumulate learning across projects, locations, and time. Use these role definitions and routines alongside decision templates, decision records, and retrospectives to make choices more transparent and improvable.

Ways to use and adapt these routines

Teams may copy and tailor these role templates to their own Hunger Engine—defining local escalation paths, turning meeting recipes into checklists, or capturing decision records in simple forms. Where appropriate, convert checklists into interactive forms or include decision records in collections so they can be audited, searched, and learned from later.