Define what is actually being decided
A meeting can spend an hour discussing a problem without identifying the decision it needs to make. Begin with a sentence that contains a choice and a deadline. “We need to improve onboarding” describes an ambition. “We need to choose which onboarding change to trial next month” establishes a manageable decision.
Next, identify who decides, who contributes and who implements. These roles may overlap, but they should not be assumed. When everyone believes someone else has the final word, more discussion rarely resolves the delay.
Set criteria before defending an option
Agree the criteria before comparing proposals. For an onboarding change, these might include the effort required from managers, the experience of new colleagues and the time needed to run a trial. Keep the list short enough to expose real trade-offs.
- Write down the outcome the decision should improve.
- Separate essential constraints from preferences.
- Compare at least one alternative to the favoured option.
- Include the cost of delaying or doing nothing.
- Ask what information could realistically change the choice.
Suppose one proposal is faster to launch but requires more manual coordination. Naming that trade-off is more useful than calling the proposal “better”. The team can then decide whether speed is worth the additional workload and who would absorb it.
Keep a short decision record
Record the selected option, the main reasons, the assumptions and the review date. This need not become a lengthy report. A few clear lines can prevent later arguments about what the team intended or what evidence was available at the time.
Distinguish reversible decisions from commitments that are difficult to undo. A small trial can justify moving with incomplete information. A larger commitment may require additional checks before action. The point is to match the depth of review to the consequences, not to make every decision at the same speed.
At the next review, ask whether the process was sound as well as whether the outcome was favourable. A good outcome can conceal weak reasoning, while an unwelcome result can still provide useful learning. Make one adjustment to the next decision rather than creating a new procedure for every surprise.
