Insights · The Growth Coach HK
How to Build a Team That Leads When You're Not in the Room
14 August 2025
Introduction
The real test of leadership is not what happens when you are present.
It is what happens when you are not.
I have asked this question to dozens of founders and senior leaders across Asia, and the honest answers are usually revealing. Some describe teams that have strong ownership, that make decisions confidently, solve problems before they escalate, and maintain standards without needing constant oversight. Others describe something closer to a pause state, things slow, or stop, or wait, until the leader is available again.
Both of these outcomes are designed. Not always deliberately, but designed nonetheless. The team that leads in your absence was built that way. So was the team that does not.
This article is about how to build the first kind deliberately.
Main Insight
The waiting team is not a team of weak people. In my experience, it is usually a team of capable people who have learned, accurately, what the organization rewards.
Here is what they have learned: decisions made without the leader’s involvement get revisited, modified, or sometimes overridden. Stepping up decisively and being wrong is more visible, and more costly, than waiting and being safe. The leader moves fastest, so following their lead produces the best near-term outcome even when it produces a worse long-term one.
None of this is irrational. It is a completely logical response to the environment. The problem is the environment.
The team that waits was not born that way. It was trained by the system around it.
When leaders step in consistently, when they are available for every question, solve every problem that reaches them, and hold final say on most decisions, they inadvertently create a culture of deference. Not because they wanted to, but because they are reliably the best option the team has. Why exercise your own judgment when better judgment is available on demand?
Building a team that leads when you are not in the room requires changing that environment before changing the people.
Common Mistakes
Across the teams I have worked with that genuinely operate well without constant leader involvement, four conditions tend to be in place. When these are missing, the team waits. When they are present, the team moves.
Condition One: People know what they own.
Not generally, not as part of a team, but specifically. This account is mine to manage. This decision is mine to make. These outcomes are mine to deliver. When ownership is diffuse, “we all own the client relationship,” accountability dissolves equally across everyone. Nothing belongs to anyone, so nobody drives it.
The work of building clear ownership is not complicated but it is deliberate. It means going through the significant things your team does and naming a single person responsible for each. Not the person who will do everything, the person who is accountable for the outcome and will make the calls required to achieve it. This often means having some uncomfortable conversations about what changes when ownership shifts.
Condition Two: People know what good looks like.
Most leaders have standards that live inside their heads, an intuitive sense of quality, of what a strong proposal looks like, of how client communication should sound, of what a good hire needs to demonstrate. The problem with standards that live only in someone’s head is that they cannot be accessed by anyone else.
When your team does not know your standards, they cannot meet them without asking you. So they ask you, and you become the quality checkpoint, and the bottleneck deepens.
Making standards visible, writing down what good looks like in concrete, usable terms, is one of the most high-leverage things a leader can do. It is unglamorous work. It feels like documentation, not leadership. But it is what allows your team to make good decisions when you are not there.
Condition Three: People have real authority within their scope.
Ownership without authority is just blame waiting to happen. If someone “owns” a decision but every significant call gets reviewed and potentially overridden, the ownership is not real and the person learns not to invest in it.
This does not mean authority is unlimited. It means that within a clearly defined scope, a person has genuine decision-making power and is trusted to exercise it. The leader’s role is to set the scope clearly, establish the standards, and then stay out of the process unless genuinely needed.
The boundary between “genuine need” and “habit of involvement” is worth examining honestly. For most leaders I work with, a significant proportion of the decisions they are involved in do not genuinely need them. They are involved because it has become the default pattern, not because their involvement is actually necessary.
Condition Four: People have a rhythm that maintains clarity.
Even a team with clear ownership, visible standards, and real authority needs a rhythm that keeps them oriented. Markets change. Priorities shift. New information arrives. Without a regular mechanism to stay aligned, to surface what has changed, to recalibrate expectations, to make decisions together about direction, even well-functioning teams drift.
The rhythm does not need to be elaborate. A well-run weekly touchpoint of thirty to forty minutes is usually sufficient. But the meeting needs to be designed for alignment and decision-making, not just updates. The difference matters enormously in practice.
Framework: Building Independent Leadership
One thing I want to address specifically, because it comes up consistently in the organizations I work with across Hong Kong and Singapore: the cultural dynamics that can make building independent leadership harder in Asian business environments.
In many Asian organizational cultures, deference to authority is deeply embedded. Questioning the leader’s direction, proposing alternatives, or making decisions that the leader did not explicitly sanction can feel presumptuous or disrespectful. This is not weakness. It is a cultural norm that has its own logic and value. But it can also make it harder to build the kind of independent leadership we are talking about here.
The leaders I have seen navigate this effectively do not try to eliminate hierarchy or pretend cultural norms do not exist. They work explicitly within them while creating deliberate space for different behavior. This often means being very clear and direct about what they want: “I need you to make this call. I am not going to step in. Your judgment here is what matters.” The explicitness removes the ambiguity that cultural deference fills.
It also means responding well when people do step up, especially when they step up and make a call that does not go perfectly. How a leader responds to an imperfect but well-reasoned decision tells the team everything about whether stepping up is actually safe. If the response is critical and public, the next person who was considering stepping up will wait instead. If the response is coaching and learning-focused, the culture shifts.
Practical Lessons
This is the hardest part, and I want to be honest about that.
When you have built something with your own judgment and taste, watching it be done differently, even competently differently, can feel wrong. The proposal does not have quite the structure you would have used. The client communication sounds a bit less polished than yours. The approach to a hiring decision diverges from how you would have framed it.
None of this is failure. But it can feel like it.
The discipline of distinguishing between “done badly” and “done differently than I would” is one of the most important practices a leader can develop. If an outcome meets the standard, the method is secondary. If the standard itself is being compromised, that is worth addressing. But conflating the two, stepping in to change things that are just different from your preference, teaches the team that their judgment is not trusted. And teams whose judgment is not trusted stop exercising it.
This does not mean accepting low quality. It means being honest about where the line actually is between quality and preference, and only intervening on one side of it.
When these conditions are in place and the team genuinely leads independently, the change is felt on both sides.
The leader gets cognitive bandwidth back. Not free time necessarily, but the ability to focus on the things that genuinely need them, strategy, relationships, the next stage of the business, rather than being constantly pulled into operational decisions. This is where leaders start adding the most value, because it is where their experience and perspective is genuinely scarce.
The team gets something more valuable than direction: capability. They develop judgment through practice, confidence through being trusted, and pride through genuinely owning outcomes. These things do not come from being managed well. They come from being led in a way that requires them to grow.
And the business gets something it cannot get any other way: the ability to move in multiple directions simultaneously, to make good decisions faster than the leader’s bandwidth would otherwise allow, to scale beyond the ceiling that any single person’s involvement creates.
Conclusion
If you want to assess where your team currently sits, here is a simple exercise. Without asking anyone or prompting anything, take a day off from your normal communication channels. No Slack, no email, no WhatsApp. See what surfaces. See what gets resolved without you and what waits. See what decisions get made and which ones get parked.
What you observe will tell you more about the current state of your team’s independence than any assessment or conversation. And it will show you exactly which areas to prioritize as you start building the conditions that allow real independent leadership to develop.
This article is part of the Leadership Systems series. The pillar piece, Why Execution Breaks When the Leader Is Still the System, covers the foundational framework. Other articles in the series address the founder bottleneck, the manager-to-leader shift, alignment, and what 360 feedback reveals.
To talk through where your team is now and what would move it forward, book a direct conversation.
FAQs
What does it mean for a team to lead when the leader is not in the room?
It means the team can make decisions, solve problems, maintain standards, and move work forward without waiting for constant direction or approval. The leader still matters, but the team is not dependent on their presence for every important call.
Why do capable teams still wait for the leader?
Capable teams wait when the system rewards waiting. If decisions are regularly revisited, corrected, or overridden, people learn that deference is safer than judgment. The issue is often not ability. It is unclear ownership, invisible standards, or authority that is not actually real.
How can leaders start building more independent teams?
Start by clarifying ownership, making standards visible, and giving people real authority within a defined scope. Then create a regular rhythm that maintains alignment without pulling every decision back to the leader. Independent leadership develops when people are trusted to practice judgment, not just execute instructions.
This site requires JavaScript for the full experience. Email us or enable JavaScript to continue.