Create a Consulting Decision Map Before Work Stalls

A project can have a full calendar, an active team, and a clear plan while still losing days to one unanswered question. The issue is often not a lack of effort. Nobody knows who has the authority to decide.

A consulting decision map makes that authority visible before the project reaches a deadline. It names the decisions the work will require, the person who owns each answer, the people who should advise, and the date the team needs a response.

Map decisions, not every task

Start with choices that could change scope, timing, cost, or the final recommendation. Do not turn the map into another project plan.

Useful entries might include:

• Which customer segment the analysis will prioritize
• Whether a policy exception is acceptable
• Which option moves into detailed design
• Whether new information justifies a timeline change

Write each entry as a question that someone can answer. “Data approach” is a topic. “Will the team use the full data set or the validated sample?” is a decision.

Assign one decision owner

Every decision needs one person with the authority to give the final answer. Several people may provide evidence or advice, but shared accountability often becomes no accountability.

Use roles instead of names when the project will run long enough for people to change. “Client program sponsor” is usually more durable than a person’s name. Add the current name in a separate field if it helps the team route the request.

Confirm that the owner accepts the role. A consultant should not quietly assign decision authority to someone who does not have it.

Separate advice from approval

List the few people whose input is required before the owner decides. Be specific about why their advice matters.

Keep the adviser list short. If twelve people must be consulted for every choice, the map has documented the delay instead of solving it.

People who only need the outcome belong in the communication plan. They do not need to sit inside the decision process.

Set a date tied to the work

“As soon as possible” does not help a client choose between competing priorities. Set the answer date by working backward from the task that depends on it.

If analysis begins on Monday, the data choice may be due Thursday so the team can prepare on Friday. Record the consequence beside the date: “A later answer moves the analysis start.”

That consequence should be factual, not threatening. It helps the owner understand what the project can and cannot do while the question remains open.

Define the escalation path early

Escalation works best when it is an agreed process, not a surprise message sent after a deadline passes.

For each important decision, record what happens if the owner cannot answer:

1. Remind the owner one business day before the due date.

2. Surface the dependency in the next project update.

3. Ask the named sponsor to resolve ownership or choose a temporary path.

Escalate the decision, its consequence, and the requested action. Avoid escalating frustration or assigning blame.

Keep the map connected to the decision log

The decision map shows who will decide. The decision log records what they chose and why. Use both for consequential choices.

When an answer arrives, record the date, outcome, and any conditions. Link it to the affected plan or deliverable. Then close the open item on the map.

Review the map at phase changes and before major client meetings. Add newly discovered decisions, remove choices that no longer matter, and confirm ownership when the client team changes.

A decision map will not make every answer immediate. It will make delay visible while the project still has options. That gives you and your client a fair way to protect the schedule, involve the right expertise, and keep authority where it belongs.

[Keep consulting projects moving with clearer client decisions](https://getconsultkit.com)