If Everything Depends on You, How Does Your Company Grow？
"I'll just do it myself."
After 25 years in global sales and 15 years building a business, I know that sentence well. A customer has a problem. A product is running late. The team cannot make a decision. You step in. Early on, this can save the company. Over time, it can become the reason the company cannot grow beyond you.
A recent discussion about work left me thinking about two responsibilities of leadership: cultivating what could grow, and caring for what already exists.
We celebrate the first. We often overlook the second. And founders pay a price for that imbalance.
Who gets rewarded for keeping things healthy?
New products, new markets, new funding. These are visible achievements. They make good announcements and strong promotion cases.
Maintaining an aging system is less exciting. So is protecting customer trust, developing a successor, or making sure a reliable employee does not burn out.
When that work goes well, the report is often simply: "Nothing went wrong."
One observation from our discussion stayed with me: Builders get rewarded for releasing new things. Far fewer people get promoted for maintaining what they have already built.
Someone connected this to —— technical debt. A prototype becomes a permanent product. Code built for one purpose gets stretched to serve another. A system that works for a thousand users struggles under a million.
Each decision may have sounded reasonable at the time: "Ship it now. We'll fix it later." But "later" needs an owner, time, and a budget.
As AI helps teams produce code faster, I want leaders to ask more than, "How much faster can we ship?" Who will validate it? Who will maintain it? Who will be accountable when it fails?
When launches earn recognition and maintenance keeps getting postponed, technical debt also becomes management debt.
The strength that made you successful can become a constraint
Founders often earn trust by delivering when others cannot. You solve the problem. You stay late. You take responsibility.
People learn to rely on you. You learn to feel safest when the work is in your hands. That is understandable. I have felt it myself. But each time you take the work back, someone else loses an opportunity to develop judgment and ownership. Eventually, you may find yourself asking, "Why doesn't my team take more ownership?"
As a CEO coach, I want to slow that conversation down.
What happens when someone makes a decision differently from you?
How much room do they have to learn?
When pressure rises, do you keep their authority intact—or quietly take it back?
There is also a more personal question: Does the business need you to be indispensable, or have you come to need that feeling yourself?
That question deserves care. A founder may be carrying real financial pressure, responsibility for employees, and years of personal sacrifice.
Still, the answer matters. It shapes how much room other people have to grow.
Under pressure, "just delegate" is not enough
Consider a composite case from the learning material.
An engineering leader built much of his startup's original platform. The company is fundraising, and the CEO wants a live demonstration of a new AI feature at Thursday's investor meeting. The feature is roughly three months away from being reliable. He could work nights, build a demo that succeeds under carefully controlled conditions, and address the weaknesses afterward. Meanwhile, a senior engineer he recruited has been waiting six months to take ownership of the platform. An older billing system is also deteriorating. Last month, a customer was overcharged.
There are real costs on every side.
A disappointing investor meeting could threaten funding. A misleading demonstration could damage trust. Another heroic effort could postpone the senior engineer's development and leave existing customers exposed. This is why I hesitate to tell an overwhelmed founder simply to "let it go."
The conversation needs to become more concrete:
What can the demo honestly demonstrate?
Which limitations need to be disclosed?
Who will address the billing error?
What responsibility can the senior engineer take now, with appropriate support?
The leader may still need to step in. But that intervention should leave the organization better able to handle the next challenge.
A rescue that repeatedly postpones an organizational problem can become part of the problem.
What is your organization teaching people to do?
Leaders often describe problems in terms of individual character. Like "They lack ownership." "They don't collaborate." "They never tell me the bad news early enough."
Sometimes those observations are fair. But I also want to understand what the organization rewards. If the person who saves a failing launch gets celebrated, while the person who prevented five failures goes unnoticed, people learn. If raising concerns brings criticism, while a confident story earns approval, people learn. If every important decision returns to the founder, people learn that too.
Three questions from the discussion are worth bringing into a leadership meeting:
What am I doing—or avoiding—that helps this problem continue?
Where do blame, rivalry, or working alone show up between us?
What gets rewarded here, and what gets ignored?
The third question often reveals something the company's stated values.
Look at who receives recognition, authority, and advancement. That is where people learn what matters.
Caring for people includes allowing them to hand over
Another part of the discussion concerned long-serving volunteers who felt embarrassed after changing roles. They had contributed for years. Yet stepping back seemed to carry a sense of failure.
That stayed with me because I have seen a similar pattern in business.
A dependable person becomes the permanent owner of a difficult responsibility. They are praised for carrying it, but no one plans for a handover. Over time, their commitment becomes something they feel unable to leave.
We need better conversations about the full life of a responsibility: accepting it, growing into it, maintaining it, and eventually passing it on. That means discussing review points, succession, documentation, and transitions before someone is exhausted. It also means thanking people for a completed contribution without making them feel guilty for needing a different chapter.
An organization becomes more durable when knowledge and responsibility can move between people.
Remember who made your work possible
One question from the discussion brought all of this back to something very ordinary: "Whose work supported you this morning?"
Someone made breakfast. Someone taught an early class. A colleague resolved a technical problem. Open-source contributors built tools we use every day. Before we begin our own work, we have already benefited from the work of others.
Looking back at my years as a startup founder, I find it harder to describe even my modest successes as mine alone. I worked hard. I also received opportunities, trust, help, and the benefit of circumstances I did not control.
Remembering that changes how I see a team. People are placing their time, ability, and trust in our hands. Leadership includes taking care of that trust.
Before your next task, try two questions:
What needs to grow through my work today?
What already exists that needs my care?
And the next time you hear yourself say, "I'll just do it myself," pause.
Perhaps the most useful work you can do is help someone else become ready to carry it.