Some nights, my daughter asks for a bedtime story when I have very little imagination left. The requested characters can be ambitious: a unicorn who is also a firefighter and a chef.
When I lose the thread, her attention drifts. When the character has a clear problem and something worth trying, we have a story we can follow together.
I think about that when explaining a plan at work. People need enough context to understand why the work matters, what they are being asked to do and how they will know whether it helped.
Explain the situation before the task list
A list of actions is easier to follow when people understand the problem behind it. Start with what is happening now and who it affects.
Here is a hypothetical example for a local service business: enquiries are arriving through several channels, and some customers are waiting because nobody is sure who should reply. The proposed change is to give each enquiry an owner and a confirmed next step.
That explanation gives the team a reason for the work. “We are introducing a new workflow” tells them much less.
Use actual observations where you have them. If you do not know how often an enquiry is missed, say that you need to establish a baseline. A story should make the evidence easier to follow; it should not supply evidence you do not have.
Show what will happen and where it may get difficult
Next, explain the work. In the enquiry example, one person checks the incoming requests, assigns them and confirms that someone has accepted the handoff. The office records what happened after the customer was contacted.
Then name the likely difficulties. What happens outside office hours? Who covers an absence? Where does a request go if the usual person cannot take it?
These details give people a chance to improve the plan before they are expected to use it. Leave space for the people doing the work to point out what you missed.
You can keep this explanation short. A page showing the current problem, proposed change, responsibilities and open questions may be more useful than a presentation full of ambitions.
Describe a result people can recognise
A plan needs a way to judge progress. In our example, the team could check whether each enquiry has an owner and whether the promised follow-up happened. A booked job is a later outcome and should be recorded separately.
Avoid writing a guaranteed happy ending into the plan. Customers may decline a quote, the new process may need adjustment or the evidence may remain inconclusive. Agree what you will observe and when you will review it.
The business story is useful when it helps people make a decision. It becomes a distraction when the presentation makes an uncertain result sound inevitable.
Try a short version before the next meeting
Write four sentences:
- Here is the situation we need to address.
- Here is the change we propose and why.
- Here is who will do the work, including the difficult cases.
- Here is what we will check before deciding what happens next.
Read them to someone who has not been involved. Ask which part needs explanation and what decision they think you are asking for.
You can use the same approach when introducing a new colleague to a task. Explain why the work exists, show how it happens and give them a clear place to ask for help. Keep the detailed instructions available alongside that explanation.
A bedtime story can wander into an unlikely adventure. A working plan needs to bring people back to a practical next step. The common skill is helping someone follow what happens next.
