Decision-making glossary

Decision owner

A decision owner is the one person accountable for a decision or for a whole area of decisions: they make the call when no rule exists, answer questions about it and are the one asked whether it still holds. Frameworks such as DACI and RAPID call this role the Approver or the Decider, and insist there is only one.

Atlassian’s DACI framework names a single Approver, and Bain’s RAPID framework a single person who decides. The point is the same: if two people can make the call, either can reopen it, and nobody knows whom to ask. Contributors and people who must be informed are different roles; they do not own the decision.

An owner for a single decision is useful, but a rulebook needs owners for areas. When someone asks what the rule on overtime is and there is none, the question should go to one named person, not to a channel. An area with no owner leaves that question with whoever happens to answer it.

Ownership is about accountability, not seniority. The owner decides after hearing the people affected, writes the decision down in their own words and is the person asked later whether it worked. The common mistakes are naming a committee, naming nobody, and naming an owner who was never told.

In Decize: In Decize an area can have one owner, who answers requests for a rule that does not exist yet. A request goes to that owner with a due date, by a link that needs no login, and their answer becomes the rule. An area with no owner sends requests to the managers. See how →

Sources: Atlassian Team Playbook, “DACI: A Decision-Making Framework” · Bain & Company, “RAPID Decision Making”

Your team's rules, always current

Keep one rulebook your team can ask.

Decize keeps the rules your team has decided, with who owns each one, when it was decided and what it replaced. Cc an email or tag it in Slack to record a decision, then ask what the rule is. Ten decisions a month are free, with unlimited people.