6. Set Direction, Not Just Motion¶
I joined as one of two CPOs. Both of us were new. The team underneath — around 30 product managers and UX designers — was not. They had been running for years before we arrived.
The other CPO was about ten years more senior in startup experience and naturally took on the stabilizing role during the transition. That kept the team from fracturing under double leadership.
From outside, the team looked fine.
Sprint kickoffs were running. Goals were on the wall. Dashboards were moving. Meetings were happening every hour of every day. Motion was everywhere.
The team was not progressing.
Output was not improving. New insights were not surfacing. The dashboards produced the same kinds of numbers, week to week, with no new signal underneath.
For about a month after I joined, I assumed the team was the variable. Lower energy. Less ambition. A team that had been running too long without a refresh.
The diagnostic from the first chapter is what saved me from staying in that read. The pattern was too consistent across too many people for the team to be the cause. When the same dip shows up across that many operators, the variable is almost never the operators. It is the conditions they are working inside.
So we asked.
We pulled the PMs in small groups and asked them what their week looked like. The answer was operator-chair specific.
Sprint kickoffs were running four hours.
Stakeholder meetings were landing every 30 to 60 minutes across the day.
There was no time left for discovery, analysis, or strategic work.
The dashboards were producing numbers because the team had time to refresh the numbers. The dashboards were not producing insight because the team had no time to think.
The team understood the goal. The team was trying. There was no facility — no time, no structure, no roles, no clarity — to actually move toward it.
The team was moving. To nowhere.
This is the half of the principle most leaders get wrong.
Set direction is the easy half. The hard half is providing the conditions that let the team act on it. Time. Structure. Roles. Clarity. The facility.
A road is motion. A mountain is direction.
The team can walk many roads and not climb the mountain.
Direction without facility is just intent. Intent does not move teams.
The fix had several pieces and took multiple quarters to fully land. The engine started turning around month four.
The two of us absorbed the stakeholder meetings ourselves. Stakeholders got redirected upward — to the CPOs — for two reasons. The team needed time back. The stakeholders needed clarity from someone empowered to give it. Both happened at once.
Sprint kickoffs got cut down hard and given a tight structure. The team had to make sprint decisions inside a real time window instead of a four-hour drift.
Two new roles got introduced — a Product Owner and a Technical Program Manager. The team had been running without either. The work had been silently distributed across people whose job descriptions did not include it.
We realized the PMs had also been doing scrum master work on top of their actual jobs. We hired an experienced scrum master who introduced business-impact-based development as the operating model. That separation freed the PMs to be PMs.
The fix was not "hire more people." Some of the fix was hiring. Some of it was removing meetings. Some of it was restructuring who did what. All three at once. If the answer had been only one of those, the rebuild would not have worked.
The signals that the engine was turning showed up slowly.
Sprint results stopped being just delivered and started being meaningful.
Retros stopped being monotonous. When retros come alive, the team is alive. That is not a metric. It is a tell.
The monthly insight reports started being gold — actually worth surfacing in management meetings.
A CEO compliment landed eventually.
I want to be careful about how I describe this. The engine started moving. That does not mean the work was finished. Direction-setting is not a one-time fix. The room for noise to creep back in is always there. A quarter of distraction, a new stakeholder pattern, a new pressure from above, and the calendars start filling up again. The fact that the engine started turning is not the end of the story. It is the start of a different problem — keeping it turning.
Different timeline. A different team.
I was reporting directly to a CEO who changed direction constantly. Sometimes within a single day. New input in every 1-on-1.
In one of those 1-on-1s, the CEO said something that read, to me, as vision and priority. I treated it as direction. In the next team meeting, I gave the team that direction and asked them to execute. The team executed.
I reported back to the CEO.
The CEO looked at me and said, "Why did you do that?"
That sentence is the part I still remember. Not because the call was big. Because the cost of my misread was not paid by me. It was paid by the team I had asked to execute on something that was never an order.
A slap in my face.
The CEO had been thinking out loud. Maybe an early-stage idea. Maybe a passing thought. Maybe a question still being worked through. I had taken it as a decision and converted it into team execution.
The team paid for that conversion.
Wasted energy. Depleted excitement. The kind of cost that does not show up in any dashboard but is felt for weeks afterward when the next direction lands and people are quietly slower to commit to it.
What I changed after that day was not what I executed. It was what I let through.
Direction received from a volatile executive cannot be transmitted directly to the team. The leader has to sit between the two. The leader does not just receive direction. The leader manages the input.
This is where the chapter's hardest work lives. It has three parts. They look related. They are not the same thing.
Filter and pre-select. Not every executive input deserves execution. Some of it is signal. Some of it is the executive thinking out loud. The leader's job is to read which is which, against the mission already agreed, and to treat the rest as noise — consciously, not dismissively. Filtering without reconfirmation is dismissal. Filtering with reconfirmation is judgment. The discipline lives in the reconfirmation, not in the filtering.
Manage upward. This one I have to land carefully because it is easy to misread.
When you report to a volatile CEO, part of the job is turning raw input into a cleaner decision.
That is not maneuvering the executive toward what you want. It is forcing one-idea selection so the executive can make a clean call. A volatile executive may voice three or four directions in a single conversation. If the leader passes all of those down to the team, the team gets shredded. If the leader picks one and asks the executive to confirm — "of these, which one are we actually deciding on this quarter?" — the executive is being held to the same standard the team is being held to. One mountain. One climb.
The buffer works in two directions. It protects the team from upstream noise. It also helps the executive get sharper.
Sell, do not transmit. Once one idea has been confirmed, the leader does not just hand it to the team. Direction received as transmission produces compliance. Direction received as inspiration produces ownership. The selling is what turns a confirmed idea into a committed mission. There is a longer version of this move that has its own chapter ahead.
These three are different shapes of work. Filter happens at the input. Manage upward happens with the executive. Sell happens with the team. Stacked together they collapse into "be careful." Apart, they are usable.
What bad leadership usually does¶
The default is to confuse calendars with progress.
The leader looks at the team's week and sees meetings, sprint ceremonies, dashboards updating, status reports going out. It looks like a working team. The leader concludes the team is working. The leader moves on to the next thing.
Meanwhile, the team is spending its energy on the meetings, not on the destination. There is no time for the work that would actually move the number. The dashboard is being maintained, not interrogated. The sprint kickoff is being held, not used.
A team can be busy every day and still go nowhere. Motion is the most convincing form of theater because everyone inside it is genuinely working.
The other failure mode is upstream. The executive says something. The leader passes it down within the hour. The team re-aims. Two weeks later the executive says something different. The team re-aims again. The leader looks responsive. The team is being shredded.
Both failures look like leadership from outside. Both are leadership avoiding its actual job.
The principle¶
Activity is not progress.
A leader gives people a clear mountain to climb, not just more roads to walk.
And the leader provides the path — the time, the structure, the roles, the clarity — that lets the team climb it.
Why it matters¶
Direction without facility is intent. The team can know exactly what we are trying to win and still not move, because their week is full of meetings that do not connect to the mountain. That is the cost most leaders never see. They set direction, the team nods, the calendar stays the same, and then six months later the leader wonders why nothing shipped.
Transmission without filter is noise. The executive's thinking-out-loud becomes the team's quarter. The leader looks responsive but the team pays. Energy spent. Excitement depleted. The next time real direction arrives, the team is already a little slower to commit, because they have been re-aimed twice this month.
Both failures show up the same way from outside. Busy team. No real progress. The diagnosis is different for each, and the fix is different for each, but the symptom is the same — motion without movement.
What better leadership looks like¶
A leader who defines the mountain and clears the path. Not just "here is the goal" but "here is the time, the structure, the roles, the clarity to reach it." The two are one job, not two.
A leader who reads the team's week before judging the team's output. If the calendar is full of meetings that do not connect to the destination, the team is not the variable. The facility is.
A leader who does not transmit upstream noise downstream. Filters first. Reconfirms before executing. Holds the executive to one decision the same way the team is being held to one mountain.
A leader who sells the direction to the team instead of handing it down. Compliance gets the work done once. Ownership gets it done well, repeatedly, and without supervision.
A leader who does not glorify slowing down. The buffer is for unstable input. Some calls genuinely need to move fast. A leader who buffers everything becomes the bottleneck the team learns to route around.
Practical tools¶
Two tools. Different shapes of problem.
The first reads the team's situation. Are we set up to climb the mountain we said we were climbing.
The second reads executive input. Should this become team direction at all.
The Direction + Facility Check¶
Before judging a team's progress, ask:
1. Does the team know the destination?
Not the metric. The mountain. Why it matters now. What we are trying to win.
2. Does the team have the facility to reach it?
Time. Structure. Roles. Clarity. The conditions that let intent become action.
3. Is the dashboard producing insight or just numbers?
Numbers without insight are motion. Insight is the signal that direction is landing.
4. Is the team's energy spent on the destination, or on managing meetings?
If the calendar is full and the destination is fuzzy, the leader has built motion, not direction.
5. Has new noise been creeping in since direction was set?
Direction is not a one-time decision. The room for noise to come back is always there.
Question three is the one most leaders have not been asked explicitly. The dashboards-versus-insight test. A team that produces numbers is maintaining the system. A team that produces insight is moving against the mountain. The first looks like work. The second is work.
The Buffer Test¶
For executive input — before translating an executive request into team direction:
1. Is this an order, or a passing thought?
If unclear, reconfirm before executing. Ask the question with respect, but ask it.
2. Does this align with the mountain we set, or is it a new mountain?
If it is a new mountain, surface it as a new mountain. Do not silently re-aim the team.
3. What is the cost of asking the executive to pick one idea before I move?
Usually small. The cost of not asking is paid by the team.
4. Am I selling this to the team, or transmitting it?
Transmission produces compliance. Selling produces ownership.
Question three is where the manage upward idea operates without manipulation. The leader is not steering the executive. The leader is asking for one decision instead of several inputs. That is the same standard the executive expects the team to be held to. It is fair.
Question four is where transmission becomes selling, and where the team starts owning the work instead of doing it.
Ethical boundaries¶
This chapter has more fences than usual. The principle is easy to misread in several directions, and I want to be specific about each.
Set direction is not force the team to follow. The "sell, do not transmit" move is the protection. Direction is sold honestly, with context, with room to disagree before commitment. A team that is told what the mountain is and never asked whether they can climb it is a team being managed, not led.
Be the buffer is not insulate the team from leadership reality. The team should still understand that priorities can shift, that the executive is human, that uncertainty is part of the work. The leader's job is to slow the shift down and translate it carefully — not to hide that shifts happen. A team that thinks the CEO never changes direction will be blindsided the day reality shows up.
Turning raw input into a cleaner decision is not manipulation. It is forcing one-idea selection so the executive can make a clean call. The honest version is: the leader holds the executive accountable to one decision, the same way the leader holds the team accountable to one mountain. Both directions of accountability are part of the job. If this beat reads as upward maneuvering — steering the executive toward what the leader wants — the chapter has missed.
Treat other inputs as noise is not arbitrary filtering. It is pre-selection based on mission alignment, with reconfirmation before execution. Filtering without reconfirmation is dismissal. Filtering with reconfirmation is judgment. The discipline lives in the reconfirmation.
Hire the right roles is not solve every org problem with headcount. The Story 1 fix included hiring, removing meetings, and restructuring — three moves at once. Sometimes the answer is restructuring. Sometimes the answer is removing. The leader who reaches for hiring first will build a bigger version of the same broken system.
The buffer is for unstable input. A leader who buffers everything becomes the bottleneck.
The responsibility is to give the team a real mountain, a real path, and a real chance — and to keep upstream noise from stealing any of those.
Simple rules¶
- Set direction and provide the facility. Time, structure, roles, clarity. Direction without facility is intent.
- Read the team's calendar before judging the team's output. Motion in the calendar can hide the absence of progress.
- Test for insight, not just numbers. Same dashboards week to week with no new signal is a tell.
- Filter executive input before transmitting it. Reconfirm before executing.
- Force one-idea selection upward when the executive is volatile. One mountain at a time, both directions.
- Sell direction to the team. Do not transmit it. Selling produces ownership. Transmission produces compliance.
- Buffer unstable input. Do not buffer everything. Some calls need to move fast.
- Treat direction-setting as ongoing. The room for noise to creep back is always there.
Reflection questions¶
- Does the team know the mountain, or only the metric?
- Does the team have the time, structure, roles, and clarity to reach it — or only the goal on the wall?
- Are the dashboards producing insight, or just numbers?
- When the executive said this, was it a decision or a thought? Have I reconfirmed?
- If I am about to re-aim the team, is this a new mountain or a passing input I have not interrogated?
- Am I selling this direction to the team, or transmitting it?
- Where has noise been creeping back in since direction was set?
- Am I buffering because the input is unstable, or because slowing things down is more comfortable for me?
Reminder¶
Activity is not progress.
A team can be busy every day and still go nowhere.
The leader's job is to give them a mountain — and the time, the structure, the roles, and the clarity to climb it.
And to keep the noise upstream from stealing any of that before it reaches them.