A manager sends a proposal to six people and asks for thoughts. One person assumes they are approving it. Another treats their comment as optional. A third waits for unanimous agreement. The delay begins with an unclear request, not necessarily with disagreement.
Before sharing the proposal, identify the decision owner and the reason each person is involved. Expertise, delivery responsibility and formal approval authority are different contributions.
Put the role in the request
Instead of “Please review,” try a more precise instruction: “I will decide the pilot scope on Thursday. Please identify operational risks by Tuesday; budget approval remains with the department lead.” The dates and roles are illustrative, but the distinction is practical.
Someone advising on technical feasibility should know whether they are being asked for a recommendation, a mandatory sign-off or a list of unresolved questions. If a safety, legal or other required approval applies, name it explicitly rather than treating it as ordinary feedback.
- What decision is being made?
- Who has authority to make it?
- Whose approval is required before action?
- Who should be consulted, and on which question?
- Who needs to be informed afterwards?
Keep the arrangement small enough to use. A complex role chart that nobody reads is less helpful than a clear paragraph attached to the proposal.
A small pilot with three different roles
Imagine a team testing a new booking process. The operations lead owns the decision about the trial workflow. The finance manager must approve any spending. Front-desk staff advise on the steps that are likely to confuse visitors. Asking all three to “approve the plan” blurs the arrangement.
A clearer request lets staff identify a practical problem without making them responsible for the budget. It also prevents the operations lead from treating a favourable staff response as financial authorisation. Write down the unresolved issue and its owner, then return the question to the person with the relevant role.
Close the consultation honestly
After deciding, explain the outcome and how significant concerns were handled. Consultation does not promise that every suggestion will be adopted, but it should not be a performance after the decision has already been made.
If new evidence changes the authority or scope, update the group. Do not let a deadline silently override an approval that is genuinely required.
The aim is not to reduce useful disagreement. It is to give disagreement a route into a decision without making every participant guess whether they are advising, authorising or merely being kept informed.