The MasterMind Mentors Club Series
There is a certain kind of silence that only occurs when the
truth enters the room, and no one wants to be the first to acknowledge it. It’s
not the silence of peace or rest; it’s the silence of recognition. The silence
that says, "This thing being spoken about is me, and sadly, I can no
longer pretend I don’t know it.”
That is the kind of silence that fell over the three of them
in the Aberdare Ranges.
James. Jacob. Martha.
Three founders. Three distinct journeys. Three unique
temperaments. Three different ways of handling pressure. Yet, beneath the
surface, they were wrestling with the same uncomfortable reality: their
businesses relied too heavily on them. More than that, they had quietly become
the system.
It is a strange thing, really, how easy it is for a founder
to admire the very thing that suffocates them. We praise the hustle. We praise
the sacrifices. We praise the one who is “always on.”
We admire the person who can carry everything in their head:
closing deals, solving crises, approving payments, managing staff, calming
clients, reviewing branding, fixing operations, and somehow still being
mistaken for a visionary rather than a very exhausted bottleneck.
And for a while, that kind of life can even seem glamorous.
Until it doesn’t. Until the body starts telling the truth. Until the business
begins revealing the gaps. Until your team keeps waiting for your decision on
everything from strategy to toilet paper. Until a two-day sickness feels like a
hostile takeover. Until you realize that what you thought was leadership might
actually be a highly refined addiction to control.
That was what sat before them that day, along with the
beautiful winding Aberdare ranges, to qualify the R&R.
James appeared successful from afar. At 27, he had already
achieved what many men spend decades talking about but never realize. Money,
assets, businesses, a visible life. He had risen from a servant’s quarter to
his own mansion, largely through wit, determination, and an exceptional ability
to get things done. Calling him gifted would seem lazy. He was more than
gifted. He was relentless. He was the kind of young man who made others feel
both inspired and insecure. He could close deals, organize, lead, fix, and
execute. Because he could excel at many things, he trusted very few people to
do anything well.
That is how a founder often starts to turn into the system.
First through excellence, then impatience, followed by suspicion, then control,
and finally exhaustion.
James often hired and fired. He was quick to judge what he
called incompetence and was strongly attached to his own standards. It's easy
to admire such people when everything is running smoothly. More difficult to
recognize that the system relies on just one main energy source. Even harder to
accept that if that source weakens, everything begins to flicker.
Jacob was a different kind of founder, but no less trapped.
He had spent five years building a consulting practice that somehow still
behaved like a side hustle in a trench coat. It rose and fell with his moods,
energy, social confidence, and whatever was happening in his life at the time.
When he was energized, things moved. When he withdrew, the business followed
him into the cave. He had money sometimes. Big payouts sometimes. Hope often.
Stability rarely. His business did not run on structure. It ran on chemistry.
On adrenaline. On chance encounters. On his personal social weather.
And then there was Martha.
Martha owned what many would call a “real business.” A
physical location, a recognizable product, staff, and clients who loved her
work. She had documented some of her baking processes and maintained certain
operational standards. From the outside, she appeared more organized than the
other two. But upon closer inspection, you could see the same trap beneath a
more respectable appearance. Her business still revolved around her. The major
decisions, daily choices, marketing efforts, client interactions, and emotional
core all depended on her. Even with five employees, she couldn’t truly step
back. Her team functioned, yes, but their confidence and decisiveness still
relied heavily on her presence. She set standards, but not freedom. She built a
team but not complete trust. She created a business, but not an escape route.
That is the problem with founder dependency.
It does not always appear chaotic. Sometimes it looks organized, and sometimes
it even looks successful. Sometimes it bakes beautiful cakes. And still
imprisons the founder.
At one point in their conversation, someone clearly stated
the truth: if any of them were to step away for any serious length of time,
their businesses would slow down, struggle, or even collapse. Not because
the market had changed. Not because the opportunity was gone. But because
approvals, relationships, decisions, and momentum still relied too heavily on
them. That was the point when the conversation shifted from business mechanics
to identity. Because once you realize you are the center of everything, you
have to ask a tougher question: Why?
Why is everything still flowing through you?
Why haven’t you built beyond yourself?
Why do you keep staying in operations?
Why is there always one more reason you need to remain
needed?
And that is where the lessons deepen.
The first lesson is that many founders do not become
the bottleneck because they are weak. They become the bottleneck
because they are strong in the wrong way. Competence can be a dangerous
thing when it is not balanced with trust, patience, and structure. If you
can sell better than your team, you keep taking the calls. If you understand
the finances better, you keep holding the approvals. If you know operations
deeply, you keep intervening. If your standards are high, you start to prefer
your own hands over everyone else’s. And gradually, without making it obvious,
excellence can turn into centralization.
That is what had happened to James. He did not become the
bottleneck because of a lack of capacity. He became one because his capacity
exceeded his willingness to develop others. He trusted his own talent more than
any system that could outlast him. He prioritized speed, competence, execution,
and results. But beneath that was something he was reluctant to admit: he did
not trust people. And trust, unfortunately, is not just a virtue in
business; it is the foundation.
Jacob’s trap was different. It was less about striving for
excellence and more about mere survival. He saw himself almost like a highly
skilled worker leasing his freedom on uncertain terms. He could do the work;
clients hired him for his intellect. But because his business identity hadn’t
fully developed, he stayed reactive rather than strategic. He documented
extensively, yes, but even he admitted that much of the documentation felt
useless because no one else was there to use it. His core logic revealed the
real issue: "They hire me for my skill." In other words, he
still viewed himself mainly as the talent, not as the creator of a repeatable
system. That’s a self-concept issue before it’s a business problem.
Martha’s trap was more emotionally subtle. She loved her
team, had operational documents, and cared about quality. But somewhere along
the way, the business had shifted from just a livelihood to a place of
psychological occupation. It became a way to stay busy, cope, and find comfort
through control. Nothing is more dangerous than comfort disguised as
responsibility. Once being needed starts to soothe you, you will resist the
very systems that could set you free. You’ll tell yourself you’re preserving
quality, that your standards are high, and that the team isn’t ready yet. Maybe
all of that is partly true. But beneath it, there may also be grief, fear, a
sense of identity, and the quiet terror of feeling irrelevant.
This is why I often say that many business problems are not
just structural. They are psychological, behavioral, and identity-based. A
founder’s systems rarely go beyond the founder’s self-concept. If you see
yourself as the person who must always struggle, you will embed struggle into
your business model. If you believe you are the only competent one, you will
centralize decisions until your company functions like a nervous system with
one overworked brain. If you need to be needed, you will unconsciously keep
your team dependent on you. If you fear things might go wrong, you will stay
too close to operations and call it diligence. If your self-concept still
resembles that of an employee, you will ask, “How do I do this?” instead
of the more powerful founder question, “How should this be done?”
This is one of the strongest insights shared during the
Tuesday Mastermind Mentorship Club session. Let me emphasize it: founders
often struggle not just with weak systems, but also with a weak founder
identity.
They think like workers inside the business rather than
designers of the business. They are focused more on doing than on designing. More
on solving today than building repeatability. More on heroics than on
architecture. More on urgency than on discipline.
And because of that, they delay systems. They keep saying
later. They imagine systems are for bigger businesses, more stable businesses,
more mature seasons, or some future version of themselves that will finally
have enough space to be organized. Meanwhile, the business continues to run on
memory, urgency, personality, and heroes, which is to say, on unstable
electricity.
One of the funniest and saddest truths about founders is how
often we idolize business heroes without realizing that they are usually signs
that a system is weak. If one person is always saving the day, then the day is
clearly designed to go wrong too often. But because the rescue feels dramatic
and noble, we cheer for the hero and ignore the underlying flaw.
Martha clearly expressed this herself when Judy, a stellar
employee, once stepped up during Martha’s illness. Heroes are wonderful, yes.
But a business cannot rely on occasional angels dropping in from the
operational heavens. It needs consistency. It needs clarity. It needs
measurable delegation. It needs standard processes that are not just documented
but actively used, reinforced, measured, and improved.
That brings us to the second major lesson: systems
are not just software. Systems are agreements, measurements, roles, rhythms,
and documented ways of doing things that survive moods, absence, and fatigue.
This was beautifully implied in the conversation. James was
starting to realize that roles and responsibilities needed to be clearly
defined. What requires his approval? What doesn't? What is solely his
responsibility? What should no longer fall under his direct control?
Martha realized that her instruction manuals helped maintain
operational consistency, but the deeper challenge was to broaden systems
thinking beyond production to include sales, marketing, administration, and
leadership.
Jacob realized that his business depended too much on his
personality and lacked a repeatable commercial structure.
Together, they started to see the same truth from different
angles: the business needed to be removed from the core of their nervous
systems and placed into structures outside of themselves.
That is where the shift from operator to architect matters.
An operator asks, “What do I need to do next?” An architect asks, “What kind of
system should exist so this gets done consistently?” An operator is heroic. An
architect is scalable. An operator can be admired. An architect can be replaced
without the building collapsing.
And perhaps the deeper invitation of this conversation is to
stop measuring your worth by how indispensable you are. Many founders
secretly build businesses that validate their indispensability. They want
freedom, yes. But they also want to be needed. They seek scale, yes. But they
also desire control. They want teams, yes. But only teams that never challenge
them. They want systems, yes. But not systems that make their presence less
central. No wonder the process drags. No wonder growth feels heavy. No wonder
stepping away seems like treason.
The third lesson is this: if you want a business that
runs without you, you must become a founder willing to be less central.
That sounds noble until it involves ego. Until it involves trust. Until it
involves insecurity. Until it involves the hidden fear that if the business no
longer needs you in the same way, then who are you? This is why the work is not
just operational. It is personal.
James needed to confront his trust and control issues. Jacob
needed to confront his self-concept around struggle and skill-based identity. Martha
needed to confront her comfort in being needed and her closeness to operations.
And the fourth voice in this story, the observing voice—the
coaching voice—must convey the same message in different ways: your business
not only reveals your system gaps but also exposes your self-habits. It
highlights where your thinking is narrow, where your identity is
underdeveloped, where your tolerance for discomfort is low, where your
delegation is unclear, where your accountability is weak, where your standards
are unmeasured, and where your structure still relies too much on your physical
presence in the room.
That is not condemnation; it is an invitation, because once
you see it, you can change it.
The solution isn't to suddenly disappear for a month and
call it empowerment. That’s not delegation; it's abandonment or abdication in a
nice disguise. The real solution is to identify what only you should do, then delegate
everything else with clear expectations, defined results, measurements,
feedback loops, and consequences. If you can’t measure it, you can’t
truly delegate it. If it’s not clear, it’s not delegated. If there’s no routine
follow-up, it’s just wishful thinking. If everything still relies on you, you
haven’t built a system — you’ve built a backlog.
The challenge, of course, is that all this requires
disciplined review—weekly review, early decision-making, faster confrontation,
less avoidance, less emotional hiding, and no romantic attachment to old ways
of doing things. It demands that founders stabilize before scaling, build
systems before expanding, and insist on repeatability before seeking applause.
Growth without structure leads to self-destruction, and I suspect one reason
this line hits so hard is that every founder has, at some point, mistaken
expansion for maturity. But they are not the same.
So here is the tough truth at the heart of all this. Pause.
Separate yourself from the flattering story you've created
about how essential you are. Distance yourself from the performance. Detach
from the identity of always being the one who saves the day.
Ask yourself honestly:
If I stopped working in this business for 30 days, what
would happen?
Would the machine continue to breathe?
Would the team know what to do?
Would decisions still move?
Would standards hold?
Would clients still be served?
Or would everything pause at the altar of my absence?
Hence, if the business cannot operate without you, then the
issue is not just that you are hardworking. It may also be that you have not
yet built something beyond yourself. And that, perhaps, is the deepest work of
leadership. Not proving that you can do everything. But building something that
no longer depends on you at the center of everything. That is not abandonment.
That is maturity. That is architecture. That is trust. That is scale. And
maybe, just maybe, that is where a founder finally stops being the system
and starts building one.
If this message stirred something in you, don’t let it fade.
1. Join my LinkedIn
Habit Coaching Newsletter: https://www.linkedin.com/newsletters/habits-with-coach-edwin-7399067976420966400/
2. Join my Habit
WhatsApp Community at https://whatsapp.com/channel/0029VbAmKkOBvvsWOuBx5g3L
3. Ready to level up your
life? Join my 12-Month Personal Transformation Program and
let’s intentionally build the next version of you — with clarity, discipline,
and momentum. Call or WhatsApp me directly at +254 724 328059, and
let’s begin.
Great article.
ReplyDelete