Five Leadership Moves That Unlock Team Performance

I think about this often. I feel like our teams are not underperforming because they lack talent, tooling, or process. In most of the organizations I work with, the ceiling on performance is set much higher up the org chart. Yes, you might be the problem!

Current studies suggest that the strongest predictors of both delivery speed and team well-being were stable priorities. Not better deployment pipelines. No more retrospectives. Stable priorities.

Teams with frequent re-prioritization delivered more slowly, experienced higher change-failure rates, and reported significantly worse burnout. The mechanism is straightforward. When priorities shift constantly, work in progress climbs, context-switching compounds, and your most experienced people quietly stop making full commitments. They have learned that the target moves. So they hedge.

Every time you add a priority without removing one, you have not made a decision. You have made an addition. That inventory sits in your system, incurring a carrying cost that compounds every day it remains active.

The five suggestions below are not a named framework. They are the behaviors I consistently see separate leaders who build high-throughput teams from leaders who build high-theater teams. The difference is usually not intelligence or effort. It is a handful of repeatable choices.

Decide what you are NOT doing

Most leaders are genuinely good at prioritizing. Very few are good at de-prioritizing. Before you add anything to your team's active work, name aloud in the meeting what comes off the list.

If you cannot name what stops, you have not made a priority decision. You have made an addition.

What leaders say differently: Instead of "we need to add this to the sprint," try "I want to add this, which means we need to decide what we are pausing. Let's do that now before we leave this room."

And when something gets parked, say so explicitly. "This is not cancelled. It is waiting for capacity." Without that statement, people will keep working on it in the background. You still carry all the WIP, with none of the visibility.

Sell the why before you sell the what

People do not resist change. They resist change they had no part in shaping, change where nobody can explain what success looks like, and change led by someone who announced it and then moved on to the next thing.

John Kotter identified this as one of the most consistent failure points in change efforts. 

A vision that cannot survive a short hallway conversation is not ready to execute against.

Before you announce a change, answer three questions in plain language. What is happening in our environment that makes the current approach unsustainable? What does success look like in specific, observable terms? What is the cost of staying where we are?

If you cannot answer all three in under two minutes, you are not ready to lead that change yet.

What leaders say differently: Instead of "we are shifting to a platform-first model starting next quarter," try "our last three product launches took over six months to reach customers. The platform model is how we change that, and here is what it looks like when it is working."

Stay in the work, not just the launch

Change does not die at the announcement. It dies three months later, when daily delivery pressure crowds out the new behavior and the leader is nowhere to be seen in that friction.

There is a meaningful difference between a change sponsor and a change catalyst. A sponsor funds the initiative and approves the charter. A catalyst shows up in the retrospective. Removes a structural blocker publicly, so the team can see it happen. Changes their own behavior first, before asking anyone else to do so.

Joiner and Josephs, in their research on leadership agility, found that the leaders who navigate change well hold complexity without reflexively asserting a faster, louder directive. They stabilize what they can, create space for the team to learn, and adjust based on evidence rather than anxiety.

Leadership Agility by Joiner and Josephs: https://www.changewise.biz

What leaders say differently: Instead of checking in on status, ask "what is the one thing I could remove or decide right now that would make the next two weeks faster for your team?" Then do it. Visibly.

Create a clarity interval, not a constant stream

Every new signal that hits your inbox does not need to go straight to the team. When you forward every piece of strategic noise as soon as it arrives, you are not being responsive. You are flooding the queue.

Instead, batch your strategic inputs. Collect new information through the week, hold it for 48 hours, and bring it to a regular planning cadence. If it still feels urgent by then, bring it forward. If it does not, it was noise. You just protected your team's focus for free.

This is not about hiding information. It is about being a responsible filter. Leaders who understand flow work on queue depth recognize that the cumulative effect of a constant stream of information is as damaging to throughput as any single bad decision.

What leaders say differently: Instead of "just looping you in on what came out of the exec meeting today," try "I have a few updates from the week. Let me bring them to Thursday's planning conversation so we can look at them together in context."

Make your reasoning visible

When you change direction, explain the evidence behind it. Not just what you decided. Why, based on what you learned?

"We are refocusing on enterprise customers because our last two experiments showed activation rates under five percent. The unit economics do not support continuing on the current path." That sentence takes fifteen seconds to say. It saves hours of hallway confusion.

When people understand your reasoning, they can apply judgment to their own decisions. When they only receive the output, they can only comply. And compliance is slow. Judgment is fast.

This is why the Scrum framework builds inspection and adaptation into the operating rhythm. Sprint reviews, retrospectives, and the sprint cadence itself are not optional ceremonies. They are the mechanism by which your organization actually gets smarter. 

The leader's job is to protect them, show up for them, and use what they surface to change behavior, not just update the slide deck.

What leaders say differently: Instead of "we are going in a different direction on this," try "the data from last sprint showed us that our assumption about user behavior was wrong. Here is what we learned, and here is what we are changing because of it."

Do this next week

Before your first meeting, write down every initiative your team is actively carrying out right now. Not the roadmap. The live work. The things people are in meetings about are designing, building, and coordinating.

Count them. If it is more than three, you have a WIP problem, and it almost certainly did not happen on purpose.

Then do one more thing. Take your top priority change and ask yourself: could my most skeptical team member explain in two sentences why this matters and why it matters right now?

If the answer is no, you do not have an execution problem. You have a clarity problem. Write the two sentences. Say them out loud. If they do not feel honest and urgent when you say them, keep working on them before you ask anyone else to commit.

Your teams are not waiting for a better process. They are waiting to see if this time the direction actually holds. These five moves will not fix that overnight. But they are how you start building the signal worth trusting.

Want to go deeper?

If this resonates with something you are navigating right now, there are a few ways to keep going. 

This week's Tuesday premium newsletter went further into the weekly operating rhythm, with a copy-ready agenda you can run starting next week. And on Friday, the LinkedIn newsletter gets into a question that trips up a lot of leaders: when your team looks disengaged, is it a motivation problem or a clarity problem? Those require very different responses.