Insights · The Growth Coach HK
Why Execution Breaks When the Leader Is Still the System
1 May 2025
Introduction
There is a moment most founders in Asia recognize, even if they have never said it out loud.
The business is growing. Revenue is there. The team is capable. And yet every important decision still somehow ends up on your desk. Not because you have asked for it. Not because you are a control freak. But because somewhere along the way, the business quietly learned that you are the answer.
You are the one who knows the context. You move fastest. You care most. So when something needs to happen, it runs through you.
It works until it does not.
I spent nearly thirteen years at Google, running sales teams across Southeast Asia and eventually overseeing country-level revenue operations. One thing I saw repeatedly, in high-growth markets from Singapore to Hong Kong to Manila: the businesses that stalled were rarely short on talent or ambition. What they were short on was structure. The leader had become the system. And systems that depend on one person do not scale.
This piece is about what that actually looks like, why it happens to good leaders, and what to do about it.
Main Insight
Nobody builds a business intending to become its biggest constraint.
In the early stages, founder-led everything makes sense. You are lean. Speed matters more than process. Your instincts are the competitive advantage because you understand the customer, the market, and the problem better than anyone on your team. You make twenty decisions a day and most of them are right.
So the team adapts. They learn to bring things to you. They learn that decisions get made faster when you are involved. They learn, without anyone saying it, that waiting for your input is safer than acting without it.
That is not a trust problem. It is a design problem.
The same behavior that made you effective in year one becomes the ceiling in year three.
The issue is that what works at ten people starts to crack at thirty. At fifty, it is painful. At a hundred, it breaks. The same behavior that made you effective in year one becomes the ceiling in year three.
I have sat with founders across Hong Kong and Singapore who are exhausted by this. They tell me they feel like they are always behind. That weekends do not exist. That their team is talented but somehow still dependent. What they are describing is not a people problem. It is what happens when a business grows past its leadership infrastructure.
Common Mistakes
The bottleneck does not announce itself. It creeps in through patterns that look, on the surface, like commitment.
You are in every key client meeting because “you know the relationship best.” You review the proposal before it goes out because the standard matters. You join the operations call because things tend to get resolved faster when you are there. You approve the hire because you have a feel for culture fit that is hard to explain.
None of these things are wrong. The problem is when they are all true at the same time, every week, indefinitely.
Here is a useful test. Think about the last ten significant decisions in your business. How many of them required your direct input before they could move? If the answer is most of them, the system is running on you rather than on structure.
The consequences show up in predictable ways. Your calendar fills with things that should not need you. Your team waits rather than acts. Decisions pile up during the times you are traveling or unavailable. Good people get frustrated because they have responsibility without real authority. And you start to wonder why, despite how hard you are working, it still feels like the business is not quite running properly.
This matters: it is not a character flaw. The leaders who end up as the bottleneck are usually the ones who care most. They are involved because they want things done well. They stay close because they understand the consequences of getting it wrong.
Three patterns drive it more than anything else.
Competence as a trap. You are often the best person in the room for many decisions. You have context that takes months to develop. Acting yourself is genuinely faster than explaining, coaching, and waiting. So you do it. The team delivers less over time not because they are growing worse, but because they are practicing less. Capability atrophies without use.
Fear of the wrong call. In markets like Hong Kong where relationships are everything and reputation matters deeply, a misstep can cost more than just a deal. Leaders who have built something valuable are understandably protective. The instinct to stay close to decisions is rooted in real experience. But protection through involvement has a ceiling.
Identity wrapped around being needed. This is the hardest one to say out loud. For many founders, being the one who holds it all together is not just a function. It is who they are. The business is an extension of their judgment, their taste, their standards. The idea of stepping back feels not just risky but somehow like a diminishment.
All of these are understandable. None of them are sustainable.
Framework: From Running the System to Designing It
The transition that changes everything is not about doing less. It is about changing what you do.
Running a system means you are in the middle of it, making calls, resolving conflicts, holding context that nobody else has. Designing a system means you build the conditions in which others can do those things consistently, without you in the loop.
That shift is harder than it sounds because it requires giving up control before you feel safe doing so. Trust is a decision, not a feeling. You do not wait until stepping back feels comfortable. You build the structure that makes it less risky, and then you move.
What does that structure actually look like?
- Clear decision ownership: Every significant decision in your business should have one person who owns it, not a committee, not “the team,” one named person who is accountable for the outcome. Where decisions currently default to you, ask: should this actually live with someone else? If yes, make that explicit. Write it down. Communicate it.
- Explicit standards: Most leaders stay involved in decisions because they are the keeper of quality. They know what “good” looks like and they do not trust that others do. The fix is not to lower standards. It is to make them visible. What does a good client proposal look like? What makes a hire right for this culture? When those answers exist in a form others can reference, you stop being the necessary checkpoint.
- Operating rhythms: A lot of escalations happen because people do not know where the business is heading well enough to make decisions without checking. Regular, structured communication, a clear weekly rhythm, visible priorities, honest updates on what has changed, reduces the uncertainty that drives people back to you.
- Coaching instead of answering: When someone brings you a problem, the reflex is to solve it. The better move, most of the time, is to ask: what do you think? What options have you considered? What would you do if I were not available? This feels slower. It is slower, initially. But it is the only way capability actually transfers.
Practical Lessons
I worked with a business owner in Singapore, financial services, around sixty people, who felt like he was being copied on everything. Not because people were lazy but because the stakes felt high and nobody wanted to get it wrong without cover.
We did not start with a big restructure. We started by mapping, for four weeks, every decision he was involved in and asking one question about each: does this actually need me?
About sixty percent of them did not. They needed either a clearer standard or a named owner, not him. We documented the standards, named the owners, and changed one meeting so that it became a decision-making forum rather than an update session.
Three months later, he was no longer being copied on client proposals. The team was making calls they had previously escalated. He had time, actual unscheduled time, to think about where the business was going rather than what it was doing right now.
Nothing dramatic changed. The infrastructure changed.
There is a question most founders do not want to ask themselves honestly.
If I stepped away for a month, what would happen?
Not a vacation where you are still on WhatsApp. A real absence. Would the business continue to move? Would decisions get made? Would clients be looked after?
If the answer is “it would struggle,” that is important information. Not shameful, important. It means the business is dependent on your presence in a way that limits both your freedom and its ceiling.
The leaders I have seen break through this are not the ones who work harder. They are the ones who get serious about building infrastructure, decision rights, standards, rhythms, ownership, that does not require them to be physically present for things to work.
That infrastructure takes time to build. But the cost of not building it compounds quietly, year after year, until you are working harder than ever and wondering why the business still does not feel like it is fully running.
If you are reading this and recognizing the pattern, here is where to begin.
Pick one area, just one, where decisions consistently come back to you that probably should not. It might be client communications, hiring, content approval, operations, finance. One area.
For that area, ask three questions. Who should own these decisions? What does “good” look like that I have never written down? What would I need to put in place for that person to make these calls without me?
The answers to those three questions are your first piece of leadership infrastructure. Build it. Test it. Adjust it. Then do the same thing in the next area.
This is the work. Not a single big change, a series of deliberate, small redesigns that move ownership downward and outward until the system runs on structure rather than on you.
Conclusion
The rest of the articles in this series go deeper on the specific pieces:
- Why the founder bottleneck is a design problem, not a trust problem
- How to shift from managing people to actually leading them
- Why your strategy keeps losing alignment after every planning session
- How to build a team that leads when you are not in the room
- What 360 feedback reveals that no dashboard ever will
The thread through all of them is the same. Businesses that scale are not led by people who do more. They are led by people who build better.
Jerald Lee is the founder of Curiosity At Work and operating partner of The Growth Coach Hong Kong. He works with founders and commercial leaders across Asia to build the leadership systems that let their businesses grow without depending on them for everything.
If this resonated, the best next step is a direct conversation about how your business is currently operating. Book a call here.
FAQs
Why do founders become bottlenecks as the business grows?
Founders often become bottlenecks because they hold the most context, make decisions quickly, and care deeply about standards. In the early stage, that involvement helps the business move. Over time, the same involvement can stop others from building the judgment and authority needed to operate independently.
Is this mainly a delegation problem?
Not entirely. Delegation is part of it, but the deeper issue is structure. If people do not know who owns decisions, what good looks like, or how priorities should be interpreted, work will keep coming back to the founder. The fix is not just to hand off tasks. It is to build the operating infrastructure that allows others to make good decisions without constant approval.
What is the first step to reducing founder dependency?
Start with one area where decisions keep coming back to you. Map the decisions, identify which ones truly need your input, and clarify who should own the rest. Then document the standard that person should use. Reducing founder dependency starts with making ownership and quality visible.
This site requires JavaScript for the full experience. Email us or enable JavaScript to continue.