On this page
Choose the conversation you need
The meeting ends well. Your stakeholder supports the rollout, the date stays in the plan, and everyone moves on. A week later, the promised input is still missing.
You could send another reminder. Before you do, check what that “yes” actually covered. Did they agree with the idea, accept a specific action, or promise time they do not control? Those are different conversations.
This is an interactive article, but choosing a path is optional. All three paths are shown by default, so you can read the complete article in order. Choose a situation to focus on that branch and the shared follow-up, or use “Show all paths” whenever you want the whole story back. The example and advice are complete here; no separate tool is needed.
Not sure? Start with the short example below. More than one explanation can apply. Choose based on what you can observe, and change your approach when you learn something new.
A yes worth checking
Imagine a small equipment-booking service rolling out a new scheduling tool. Alex, the PM, needs two operations advisers to test the booking and cancellation steps before staff training. Morgan, the operations manager, says, “Yes, we support it. We will help.”
By Tuesday, no advisers have been named. Training preparation depends on the test results, so waiting has a consequence.
Alex and Morgan are fictional. The rollout, dates and commitments below are teaching examples, not a real project or a recommended delivery timetable.
Alex starts privately:
“We agreed operations would help with testing, but I do not yet have the names. The results are needed before we finish the training material. What is getting in the way?”
Then Alex listens. The answer determines the next move. APM’s guidance makes the same useful starting distinction: communicating includes understanding the people involved, rather than only sending information to them. APM: Communicate
Three ways to move the conversation forward
They agree but miss commitments
Morgan replies, “Of course we will help. I thought someone would pick it up.” Alex has discovered an ownership gap. The earlier agreement never became a task that somebody accepted.
Say this:
“Can you confirm two advisers by 15:00 Thursday, with a one-hour test slot on Friday? I will send the test steps today. If that does not work, what can you commit to before we finalise training?”
Do this: check that the advisers have accepted the slot, know what to test and can access the tool. Record the owner, result and date in the action log. A name suggested by Morgan is still a proposal until the person and their manager have confirmed the arrangement.
If this was already a clear commitment, do not pretend it was merely a misunderstanding. Name the missed date without accusing Morgan of bad intent:
“The names were due on Tuesday and are still missing. Has the priority changed, or is there a blocker we have not resolved?”
A useful result: two confirmed people and a workable test slot. “We will try” leaves the action open.
If you want to practise a more delicate version of that conversation, use the People Field Guide’s polite-resistance situation. Treat it as one possible explanation, not a label for Morgan. If the specific situation does not open, search for “polite resistance” in the Field Guide.
Continue to the shared follow-up ↓Show all pathsThey raise a legitimate concern
In this version, Morgan says, “The cancellation process leaves equipment unavailable until the next morning. We cannot train people to use it that way.”
Another reminder would miss the point. There is a concrete operational concern to investigate.
Say this:
“Show me one cancellation where that happens. What would a workable result look like? Let us test it with the product owner before we decide whether training can proceed.”
Do this: capture the example and expected result. Ask the responsible team to reproduce it and assess the impact. Agree who decides whether the fix, an acceptable temporary procedure or a revised rollout is appropriate. Keep the concern visible until that decision and its conditions are recorded.
Suppose the test confirms the problem. Alex brings two assessed choices to the authorised decision-maker: correct it before training, or limit the initial rollout to a scenario that does not depend on cancellation. The operational owner must be involved in judging whether the limited route is workable. Alex cannot quietly accept the risk just to protect a date.
A useful result: a verified finding and a decision with conditions. If the test does not reproduce the issue, explain what was tested and ask whether it represents Morgan’s concern. Do not close it merely because one convenient example passed.
Continue to the shared follow-up ↓Show all pathsThey cannot commit resources
In the third version, Morgan says, “I support the rollout, but two advisers are covering absences. Releasing them means leaving the service desk short.”
The commitment competes with operational work. Repeating the project deadline will not create capacity.
Say this:
“What time can you release without leaving the service uncovered? We can assess a smaller test, move the session, or ask for temporary cover. Which is workable, and who can approve the trade-off?”
Do this: make the options concrete. Check what a smaller test would leave untested, whether another qualified adviser is available, and what moving the session does to training. Do not reduce essential coverage simply to claim testing is complete.
If Morgan cannot authorise the resource change, Alex prepares a short decision request for the person who can. The request states the competing needs and recommends a route. Until a choice is authorised, the resource action remains unconfirmed and the dependent date is a forecast at risk.
A useful result: an approved allocation or an explicit change to the plan. Willingness alone is not an allocation.
Continue to the shared follow-up ↓Show all pathsClose with a workable agreement
Whichever route fits, finish by checking what happens next:
“Let me check we mean the same thing. You will confirm the advisers by Thursday afternoon. I will send the test steps today. If the slot is no longer possible, we will review the training impact before changing the plan. Is that workable?”
Adjust the wording to the actual agreement. For a concern, the next action may be a test and decision. For capacity, it may be a resource decision rather than delivery of the work itself.
Keep a brief record: action, accepted owner, due date, dependency and current status. Link any decision or issue that explains the action. Share it with the people involved and invite corrections. APM also emphasises clarity about roles and expectations in stakeholder engagement. APM: Take responsibility
At the agreed checkpoint, check the result. If it is missing, establish what changed and update the forecast. Do not mark work complete because the meeting sounded positive.
When to ask for a decision above your authority
For an ordinary delivery issue, try the direct conversation while there is still time to recover. Escalate when the required decision is outside your authority, an agreed recovery has failed, or waiting will remove a realistic option. Follow your project’s escalation rules. Do not delay urgent safety, security, legal or regulatory concerns while working through these conversational steps.
Bring a decision, not a complaint:
“Operations has not confirmed test capacity. Training preparation depends on those results. We have checked a smaller test and a later slot; neither protects the current training date with the required coverage. Please decide by Thursday whether to provide cover or move training. I recommend moving training unless cover is confirmed.”
That is a fictional example, not a script to copy unchanged. Include the actual evidence, impact, available options and decision owner. Tell the stakeholder you are taking the issue forward where appropriate. Avoid surprising them with a senior-person copy-in when a direct explanation is possible.
Read the whole route
The complete approach is available above without making a choice:
- State the missing result and why it matters.
- Ask what is preventing it, without guessing the person’s motives.
- Clarify an incomplete commitment, investigate a concern, or resolve the resource trade-off. Read all three branches if the situation is mixed.
- Agree a next step that somebody can actually own.
- Check the result at the agreed time and raise the decision if it exceeds your authority or recovery window.
The aim is to find a credible next step, including changing the plan when that is the honest answer.
Put it into practice
Pick one overdue stakeholder action. Before sending the next reminder, write down what was actually agreed and the one question you still need answered.
Want to rehearse a conversation where support keeps turning into delay? Try the polite-resistance practice in the People Field Guide. It is optional. The scripts and next steps above work on their own. If the selected situation does not open, open the Field Guide and search for “polite resistance”.
If the change itself feels threatening, the SARAH article offers another conversation lens. Use it to prompt curiosity, not to diagnose a person or assume everyone passes through fixed stages. A genuine concern or lack of capacity still needs a practical response.
Sources and further reading
The three routes, fictional example and scripts are InsightSpotter editorial suggestions, not a validated diagnostic model or an APM-prescribed process. Adapt them to your project’s authority, controls and context.
- APM: Communicate, for understanding stakeholders and adapting communication.
- APM: Take responsibility, for roles and expectations.
- InsightSpotter: Stakeholder management, for the broader engagement process.
- InsightSpotter: People Field Guide, for preparing and practising a conversation.
