Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.
Decision pain inventory from the last quarter
This is a team plan, best installed into a shared workspace so everyone with a role in it can see and own their tasks. Before drawing any matrix, find out where decisions actually hurt: the pricing call that took nine weeks, the hire approved twice by different people, the launch nobody knew had been cancelled.
First tasks
- Write the three questions you will ask in every decision pain conversation
- Book twenty-minute conversations with twelve people across four functions
- Log each stuck, duplicated or reversed decision with its rough cost
- Group the cases into patterns and draft the one-page summary
Map of the twenty decisions that matter most
Organisations make thousands of decisions, but perhaps twenty recurring ones decide most of the value: budgets, senior hires, pricing, product scope, major contracts, market entry. Naming those twenty, with how often each comes up and who makes it today, keeps the decision rights work focused on what moves the business instead of on every expense claim.
First tasks
- Pull the approval types configured in the finance and HR systems
- List every recurring decision mentioned in the pain inventory
- Score each decision for money, risk and customer impact
- Ask two senior leaders to challenge the final twenty
Choosing a decision rights framework
RACI, RAPID, DACI and the advice process all describe roles in a decision, but they suit different cultures and mixing them causes confusion. Picking one vocabulary for the whole organisation, and writing down what each role means in your words, stops arguments about whether "consulted" means a veto.
First tasks
- Summarise RACI, RAPID and DACI on a single comparison page
- Map two recent real decisions in each framework
- Agree the choice with the sponsor and record the reason
- Write plain-language definitions of every role in the chosen framework