You can explain a strategy clearly and still discover that people understood different things. Leaders talk about customer focus, faster execution, ownership, innovation, growth, or operational excellence. The presentation is polished, the graphs are accurate, and everyone seems to agree. Then people return to work and make many of the same choices they made before.
Sometimes they do not need another definition or another slide. They need to see what the idea looks like when it touches real work.
An anecdote is a short account of a specific moment used to make an idea easier to see. It may take less than a minute to tell. It does not need an elaborate plot, dramatic characters, or a clever ending. It needs a job: help people picture something that would otherwise remain abstract.
Years ago, I entered an elevator with several managers who were about to attend a time-management seminar I was facilitating. Someone mentioned that they had already attended a similar program led by a well-known Filipino speaker. The organization had reportedly spent around ₱350,000 on the earlier session. The managers said the speaker had been excellent—entertaining, impressive, memorable.
Then the HR manager asked what had changed.
“Same, same,” they said. “We are still busy.”
That exchange carries a larger idea: a successful learning event and changed work are not necessarily the same thing. I could explain that distinction through several slides about attendance, learning, application, and impact. Those measures may be useful. But the elevator gives the idea a scene people can remember.
That is what a good anecdote does.
Give Strategy Something People Can See
Strategy is full of words that appear clear until people have to make a decision. Suppose a company says, “We will win through faster customer resolution.” Everyone can agree with the statement, but the agreement does not yet tell us what must change on Monday.
A graph might show that customers wait an average of 2.7 days for resolution. That number matters. Now imagine hearing about one customer whose billing error could have been corrected in ten minutes, except the frontline employee had to send the request through two approvals. The employee could see the problem and knew the correction, but the customer still waited three days.
The number tells us how much. The anecdote helps us see what happened.
Now the strategic choice has entered the work. If faster resolution is genuinely part of how the organization intends to win, then moments like this cannot remain normal. The anecdote has given people something concrete to discuss: Why were two approvals necessary? What risk were they protecting against? Which decisions could responsibly move closer to the frontline? What would the customer experience if the strategy were really operating?
This is one reason anecdotes can help make strategy clear. They do not replace strategic choices, data, or analysis. They help people see what a choice changes, protects, or refuses to tolerate.
If people cannot picture the strategy, they will struggle to practise it.
Use the Moment to Show Where Execution Happens
The same principle applies to execution. Leaders frequently say that people need more accountability, stronger ownership, better communication, or greater initiative. These words may be correct, but execution happens somewhere more specific: during an approval, a handoff, a customer conversation, a team huddle, a coaching conversation, or a decision under pressure.
At one resort where I worked, the morning briefing was supposed to prepare employees for the day. Instead, many people had learned to fear it. When someone made a mistake, the general manager could make that failure the focus of the briefing. Over time, employees learned that reporting a problem might make them the problem. Some became quieter, some delayed bad news, and some tried to repair problems before the manager discovered them.
I eventually asked him, “What do you want people to do after these sessions—hide or help?”
I could simply say that leaders should create psychological safety, but the anecdote gives us more to work with. We can locate the recurring moment—the morning briefing. We can see the familiar response—publicly concentrating on failure. We can see what people learned from that response and how it might affect the work.
Then a better execution question appears: If we want people to surface problems early, what should leaders do when someone actually brings one?
That question takes us directly into making execution daily. Instead of discussing accountability as a general value, we can examine the moment where accountability either becomes easier to practise or more dangerous to demonstrate.
An anecdote gives execution a location.
Let Stories Carry Meaning Through the Organization
A strategy presentation often loses meaning as it travels. Senior leaders understand why a choice was made because they spent hours debating it. Managers receive the presentation. Supervisors receive talking points. Frontline employees eventually receive instructions. At each transfer, some of the reasoning can disappear.
Stories can travel differently because people can retell them.
The customer who waited three days can become shorthand for unnecessary approval. The morning briefing can become shorthand for the unintended consequences of punishing the person who surfaces a problem. The elevator story can make “same-same program” a quick way of asking whether an intervention changed anything beyond the event.
A useful anecdote is concrete enough to remember, short enough to retell, and meaningful enough to guide a choice. That makes it valuable to leaders who need to communicate strategy not once, but repeatedly—in meetings, coaching conversations, huddles, onboarding, feedback, reviews, and informal discussions.
This is also where anecdotes connect naturally to Build Leaders Who Move Work. Leaders do not communicate strategy only through formal presentations. They make it clearer every time they use a real moment to help people understand what matters, why a choice matters, and what should happen differently next time.
But stories should not travel only downward. They should travel upward too.
A frontline employee can tell the story of a customer who waited because nobody knew who had authority to decide. A supervisor can describe a handoff that repeatedly creates rework. A salesperson can tell what a prospect said immediately before choosing a competitor. A manager can bring one of those moments into the next strategy review.
Now anecdotes become more than communication tools. They become sensing tools.
Strategy gives meaning to work. Stories from work can give information back to strategy.
Bring Real Work Into the Strategy Workshop
This is why anecdotes can be especially useful when you run strategy workshops that move work.
A strategy workshop can easily become dominated by slides, financial reports, SWOT tables, market analysis, targets, and frameworks. All of those can contribute something important, but a leadership team can spend hours discussing them while remaining surprisingly far from what employees and customers actually experience.
A simple prompt can change the conversation:
Tell us about a recent moment when the way we currently work either helped or got in the way of what we are trying to achieve.
If the issue is customer focus, ask for a recent customer moment. If the concern is ownership, ask for a recent decision that nobody seemed willing to own. If execution feels slow, ask where work waited last week and why.
Different departments may bring very different anecdotes. That is useful. Sales may see something Operations does not. Finance may notice a risk Customer Service barely encounters. Frontline employees may see friction senior leaders rarely experience. The differences can expose assumptions that a strategic statement alone would never reveal.
I saw something similar with a BPO team that had missed three campaigns in four months. The team believed it needed better task-management software and was considering tools such as ClickUp or Notion. When I observed the planning meeting, another pattern became visible: deadlines were not confirmed aloud, actions were not clearly assigned, and discussions could end with something like, “OK na? Sige, good luck.”
They thought they had a software problem. The moment suggested an ownership problem.
The anecdote did not prove that software was unnecessary. It gave us a better place to investigate.
That is a useful movement inside a strategy workshop:
Story → critical moment → strategic choice → possible play
Start with what happened. Ask why that moment matters to the strategy. Examine the familiar response that produced the result. Then ask what people might do differently when the moment returns.
The story has now moved the workshop from abstraction toward execution.
Stories Help Us See. They Do Not Give Us Permission to Stop Investigating.
Anecdotes are powerful partly because they are vivid, and that is also what makes them dangerous. One angry customer can make a problem feel widespread when it may be unusual. One remarkable employee can make a practice look reliable when it depends on one person. One success after a workshop can tempt leaders to claim that an intervention transformed the organization.
So it helps to distinguish an example, an anecdote, and evidence.
An example helps people understand what could happen. An anecdote gives us a specific moment that happened, or a clearly identified anonymized or composite moment that represents a pattern worth examining. Evidence helps us determine whether that pattern is repeated, consequential, and strong enough to influence a decision.
The anecdote opens the question. Evidence helps us decide how often it is true and whether it matters enough to act on.
Suppose a supervisor begins asking employees, “What do you recommend?” rather than immediately solving every problem they bring. A month later, she tells you that one employee now arrives with two options, explains the trade-offs, recommends one, and decides within the agreed boundary. That anecdote helps you see the behavior you hoped would emerge.
Now follow the proof. Are routine escalations falling? Are decisions happening closer to the work? Are supervisors spending less time answering questions other people can responsibly decide? Are those decisions producing acceptable results?
This is where anecdote connects with Build Learning Systems and Proof. Stories can show us what to notice. They can help us recognize an emerging shift. But learning becomes stronger when we follow the story back into the work and see whether the pattern holds.
Stories help us see. Evidence helps us decide.
Build the Anecdote Around What People Need to See
You do not need to become a professional storyteller to use anecdotes well. In fact, trying too hard to make a story entertaining can make it less useful.
Begin with the people listening. What do they need to understand that remains abstract? What decision, tension, or pattern do they need to see more clearly?
Then find a moment that carries the idea.
A useful anecdote usually needs only three things: the moment, or what happened; the tension, or why it mattered; and the meaning, or what people should see differently because of it.
Look again at the elevator. The moment is simple: managers are discussing an earlier time-management seminar. The tension is that the program was impressive and expensive, yet the original problem remained. The meaning is that we should not confuse a successful learning event with changed work.
Everything else is optional.
Remove details that do not help the listener see the point. Then apply one more test:
Could someone else retell this tomorrow without your slides and still carry the meaning?
If the answer is yes, you have made the idea portable.
Give Strategy a Moment People Can Remember
Strategy still needs analysis. Leaders still need data, graphs, measures, financial information, and careful thinking. Anecdotes should not replace any of these things.
They have another job.
They show the customer waiting. They show the decision nobody owned. They show the employee who stayed silent because speaking had become dangerous. They show what happened before a different play was introduced and what happened when people began responding differently.
They give people a concrete moment they can examine, remember, retell, and bring back into the work.
The next time you need to communicate an important strategic idea, do not begin by asking what slide should come next. Begin with the people who need to understand it. Ask what they need to see, then find the moment that makes the idea visible.
Tell only enough of the story to carry the meaning. Then use that story to examine the work.
Because strategy becomes easier to understand when people can picture it, easier to discuss when they can point to it, and easier to carry when they can retell it.
Give the strategy a moment people can remember.
