Most managers have sat through a strategy presentation.
The CEO or the MD stands at the front of the room. There are slides. There is a direction. There is language about priorities and focus and where the company is going. People nod. Someone asks a question. The meeting ends.
And then everyone goes back to their desks and does roughly what they were doing before.
Not because the strategy was wrong. Not because the people in the room stopped caring. But because nobody told them what any of it had to do with them specifically — with their team, their decisions, their work on a given Tuesday.
That gap is not the CEO’s fault. And it is not yours.
But it is your problem.
Strategy is not a destination. It is a map.
Here is the version of strategy most managers carry around in their heads.
Strategy is the big plan. It lives at the top of the organisation. It is set once a year, usually in a room they were not invited to, and it concerns things like market position and five-year projections and decisions made at a level above their pay grade. It is important, certainly. But it is not theirs.
That version is wrong. Not just incomplete — wrong in a way that costs.
A strategy is not a destination. It is a map. And a map is only useful to the person holding it.
Think about a road trip. A group of eight people, two weeks, across a country they have never driven through. Someone planned the route — where they are starting from, where they want to end up, the milestones along the way, the decision not to use motorways because the smaller roads are more interesting and the campervan cannot keep up above ninety kilometres per hour. That is the strategy. It sets the shape of the whole journey.
But say you are in charge of days one through five. The first leg. You have been told where the group needs to be by six o’clock on day five, and you know the parameters — eight hours of driving per day maximum, no motorways, everyone needs to eat. Within those constraints, the route for your five days is yours to plan. Your decisions, your trade-offs, your judgment about what matters.
You are not waiting for the person who planned the whole route to tell you where to stop for lunch. You are leading your leg. And the quality of your leg depends on whether you understood the overall plan clearly enough to make good decisions within it.
That is what strategy means for a manager.
Not: follow the slides.
Not: wait for instructions.
Understand the direction well enough to lead your part of the journey without someone standing over you.
The question that changes your value
Here is something most managers never do.
They never go to their manager and ask: what does success look like for my team this quarter, and how does that connect to where the company is going?
That question feels presumptuous. It feels like stepping above your level. In some organisations it might even feel risky — like admitting you do not already know.
It is none of those things. It is the question that separates the managers who get promoted from the managers who stay where they are.
Think about what that question communicates. It communicates that you understand your job is not just to keep your team running — it is to move the organisation in a direction. That you are not waiting to be told what to do, but are actively trying to understand the logic so you can make better decisions. That you are thinking about your team’s work in the context of the whole company, not just the context of your own desk.
That is not what most managers do. Most managers manage downward — they focus on their team, their deliverables, their own results. Which is important. But it is half the job.
The other half is managing upward. Understanding the direction above you well enough that you can translate it, make it concrete, and give your team something they can actually act on.
A manager who does both is twice as useful as a manager who does one.
The fractal in practice
There is a word for what you are doing when you take the company’s strategy and make it real for your team.
You are making strategy fractal.
A fractal is a pattern that repeats at different scales. Zoom out and you see the whole shape. Zoom in and you see the same shape repeated at a smaller level. And again at a smaller level. The structure is self-similar across scales.
That is how strategy works in a healthy organisation. The board or the CEO has set the overall direction. The business unit head has translated that into what it means for their unit. The department manager has translated that into what it means for their team. The team lead has translated that into what it means for this week.
Each layer holds the same structure — where are we now, where are we going, what matters most right now, what are we choosing not to do, how do we communicate what is real. The scale changes. The logic is the same.
When a manager does this deliberately — when they understand the direction above them and convert it into a usable map for their team — they are not doing strategy instead of leadership. They are doing strategy as leadership. The two are the same act at different scales.
When they do not do this — when they receive the company strategy as a presentation and hand their team a list of tasks — the fractal breaks. The team operates from their manager’s to-do list instead of a direction they understand. Every ambiguous situation gets resolved by instinct rather than by principle. The work may be completed. The direction may be lost.
What your team actually needs from you
Your team does not need you to motivate them. Motivation is the wrong category.
They need to know where they are going. Not in the corporate-vision-statement sense. In the practical sense: what is this team trying to achieve in the next 90 days, and why does that matter?
They need to know what matters most right now. Not everything. The one thing that, if it gets done well this quarter, moves everything else forward.
They need to know what you will not do. Strategy is not the list of priorities. It is also the list of things the team is explicitly not pursuing right now — the clients you are not taking, the work you are deprioritising, the meetings you are declining. Without that list, everything urgent becomes equally important, and the team has no way to make consistent decisions when you are not in the room.
They need to understand the current reality, not the polished version of it. What is working, what is not, what constraints are real. A team that operates from an accurate picture of where they are makes better decisions than one operating from the picture management hoped to be presenting by now.
And they need to see you correct course when you were wrong. Not apologise for it. Correct it. The team that sees their manager update direction based on what the last quarter revealed learns something important: decisions are based on evidence, not ego. That is the foundation for a team that can learn.
None of this is complicated. All of it is deliberate.
What ownership actually requires
There is a phrase that travels around most organisations without anyone stopping to define it.
Take ownership.
It gets said to managers who are not deciding. To teams that are waiting for permission. To individuals who keep escalating instead of resolving. The instruction sounds clear. Act like it is yours. Own it.
But ownership is not a mindset. It is a structural condition. And you either create it or you do not.
A person can only take ownership of something when three things are true. They understand the destination, why it was chosen, and the parameters that govern how to get there — deeply enough that when the unexpected arrives, they can navigate without asking. They have the authority to make decisions within a defined space without asking permission for each one. And they have cover: the structural assurance that a decision made in good faith, within the authority they were given, will be judged by the quality of the thinking at the time — not by what became clear afterwards.
Those three things are not character traits. They are information and structure. A manager who provides them creates a team that owns its work. A manager who does not provides a team that waits — and then gets told they are not taking ownership.
This is where the fractal becomes important beyond the strategy conversation.
When you translate the company’s direction into your team’s context — when you give them a clear picture of where you are going, what matters most right now, what you will not do, and what the current reality actually is — you are not just communicating a plan. You are building the conditions under which ownership becomes possible.
Your team cannot own what they do not understand. They cannot decide well within boundaries they cannot see. They cannot act with confidence when the stakes have not been named.
Translation is not a communication task. It is the structural act that makes ownership available.
If your team is not taking ownership, the first question is not what is wrong with them.
It is what they are missing.
The conversation worth having
Before your next one-to-one with your own manager, there is a question worth preparing.
Not: what do you need from me this quarter?
That is a question about tasks.
This one: what does this team need to have achieved in the next 90 days for you to consider it a strong quarter — and how does that connect to where the company is going?
That question opens a different conversation. It might be slightly uncomfortable. Your manager may not have a clear answer ready, which is itself information.
But ask it, and something changes in how you are perceived. You are no longer the person managing their team. You are the person who wants to understand the direction well enough to manage it.
Those are not the same person. And over time, organisations do not treat them the same way.
The ideas in this essay are at the centre of Fractal Strategy: Leadership at Every Level — a half-day workshop designed for managers at every level who want to lead their team with the company’s strategy, not around it. If your organisation would benefit from running this workshop, the details are here.