The Hidden Commitments That Derail Founders
There’s a phenomenon I’ve observed in founders. When I say “phenomenon,” I’m talking about a repeated pattern of behavior. I’m not sharing this to blame or shame anyone, but so leaders can actually see what they’re doing and the downstream impact it creates.
Here’s the short version:
A founder walks into a meeting and casually says, “We should get some case studies from clients.” On its face, it’s a perfectly reasonable idea.
But inside an organization, something else happens.
Whoever hears that idea (no matter how many levels below the founder they sit) treats it as a directive, not an idea.
And that directive can collide with existing priorities, create confusion, and overload people with tasks that aren’t anchored in a clear problem or purpose.
The only real “why” behind it is: the CEO said so.
This erodes motivation fast.
So what’s really happening?
A founder comes across a single piece of information. Perhaps someone tells them something at a conference. It might even be something vague like, “People are talking shit about your company.”
Instead of slowing down and asking, “Which people? How often? What exactly did they say?” they treat the information as truth.
From there, everything accelerates.
Step 1: They jump to a conclusion.
“This is a problem.”
Step 2: They decide the problem requires action.
“This is something we need to deal with.”
Step 3: They decide on a solution.
“We need some case studies.”
Step 4: They decide who should do it and often task them directly.
All of this happens before anyone else is enrolled, before more data is gathered, and before the actual owner of the problem or solution has any say in defining it.
One data point becomes a full-blown directive with organizational weight behind it.
It isn’t malicious. In fact, it’s rooted in something pretty brilliant.
To understand why this happens (and what can be done about it), you have to begin by looking at how they see themselves, their role, and their identity.
If we treat their actions as a “bad habit to correct,” we miss the point entirely.
Behavior doesn’t change because someone is told to “slow down” or “stop giving solutions.” It changes when THEY see what’s driving the behavior in the first place.
Founders often have competing commitments running in the background:
A commitment to being useful
A commitment to being helpful
A commitment to ensuring their people succeed
A commitment to adding value
A commitment to being essential
These commitments got them where they are.
Early on, they were essential. They solved everything. They made things happen. They saved the day. And that identity doesn’t vanish just because the company grows.
So even if a founder says they want empowerment, autonomy, buy-in, and a team that owns problems end-to-end, their deeper commitment (the one they don’t consciously see) can still run the show.
Real change requires working at the level of identity, not behavior.
A founder must begin noticing the moment their legacy identity starts driving the bus. They need to recognize the impulse to be essential, the instinct to solve, and the desire to be the one who adds value.
And instead of suppressing it or “trying to behave differently,” they have to choose a new way of being and a different source of value for the company.
Only then does the possibility exist that they won’t repeat the same pattern.


Great perspectives here, Townsend. From my personal experience (more than once), the phenomenon you detail—where a founder's off-the-cuff idea becomes an instant, priority-shifting directive—is spot-on, and it all boils down to the founder's identity; they're still operating from the successful, early-days commitment of being the essential problem-solver, and until they recognize that impulse and intentionally find a new way to add value, they will keep derailing the organization's focus.