Jason A. Hoffman, PhD | May 5, 2026
There is a particular failure mode that plays out when a senior executive joins a company whose founder is still in the building, still engaged, still making the decisions that matter. The executive arrives with credentials, a playbook, a network, and a reflex. The reflex is to find what is broken and fix it. The reflex is wrong, and almost no one catches it in time.
The reflex is not malicious. It is structural. The day you accept the offer, you take on a problem: you need a thesis for your first ninety days, and “the place is already running well, I am here to learn” feels professionally fatal to most people. It does not justify the comp. It does not give you a platform. It does not generate the artifacts you need for your next role. So the thesis writes itself before you have read a single document. There is something broken. You were brought in to fix it. The evidence will be assembled to fit.
This would be a manageable problem if it did not collide with a second one. Most executives joining a founder-led company are coming from places that operate at a lower standard. Not lower in revenue or headcount. Lower in tolerance, lower in coupling between decisions, lower in the load each individual choice is asked to bear. The pattern library you bring with you, the playbooks you have rehearsed, the war stories you tell, the consultants you know, the vendors you trust, all of it is calibrated to that prior environment. When you arrive and see something built to a tighter tolerance than you have ever operated within, you do not read it as superior. You read it as strange. Over-engineered. Idiosyncratic. Founder-driven. Not best practice. The reflex is to normalize what you are looking at down to what you recognize, and you will call that normalization “fixing.”
In practice, you replace the proprietary internal tooling with the SaaS suite you know from your last three companies, because the proprietary system feels strange and the SaaS suite has wide adoption at peers. You replace the unusual go-to-market motion with the standard SDR-to-AE funnel, because the standard funnel is what your network operates and what consultants benchmark. You replace the founder’s idiosyncratic compensation philosophy with the public comp-bands approach you have administered before. You hire the firm that produced the report you saw at five other companies. Each replacement is defensible in isolation. Each replacement also removes a piece of what made the company different from its competitors. Best practice is, by definition, what the median company does. It is not what the company at the top of its market does.
Here is what you are actually doing. You are looking at a system in which most of the visible design choices are load-bearing. The founder did not pick any of them by accident. Not the operating model, not the vertical integration posture, not the IP strategy, not the customer concentration profile, not the organizational architecture. Those choices are wired into the moat. They do not look like best practice because best practice describes the median, and the company you joined is not at the median. The choices look strange precisely because they are the source of the advantage. Rationalizing them down to what you recognize is not maturity. It is the fastest available path to value destruction, and it will look like progress for about eighteen months before the consequences arrive.
The founder is the keeper of those choices. Not because the founder is infallible, and not because every decision they ever made was correct, but because the founder is the only person in the building who carries the full causal history of why the system looks the way it looks. They remember the version that did not work. They remember the customer who left because the team compromised on a thing that seemed minor. They remember which constraints are real and which are vestigial. You do not have access to that history. You have access to the present state, which looks to you like a list of things to question.
This is the part that almost no one gets right. Acknowledging that the place was built well by the people already there means accepting a subordinate intellectual position to the existing system and the people who designed it. Most executives at the senior level will not do that. The cheaper move is to assert that what exists is legacy, that the prior leadership was operationally naive or technically limited, and that real maturity arrives with you. The org chart rearrangement and the consultant engagement and the new framework rollout are the visible expression of that assertion. They are also the moment the moat starts to leak.
The disposition that works is not deferential. Deference is the wrong frame, and founders do not want it anyway. The disposition that works is curious. You ask why the thing is the way it is before you propose changing it, and you treat the answer as load-bearing data rather than as resistance. You assume that the strange design choice is correct until you have understood the constraint it solves. You earn the right to propose changes by first demonstrating that you understand what the existing system is doing and why. You put the burden of proof for changing a load-bearing element on yourself, not on the system that already works.
Even when the founders have done the work of making everything legible, with design documents, podcasts, talks, and engineering rationale for the choices that matter, the reflex still fires. “This isn’t how we did it at company X.” “Is this really ‘enterprise ready’?” Both questions sound reasonable. Both are normalization pressures dressed as evaluation. The first compares against a baseline that has nothing to do with whether the choice is right. The second asks whether the company conforms to the median enterprise’s expectations, which is the opposite of what makes the company different from the median enterprise. Founder articulation makes the curious posture cheaper. It does not make it automatic.
This is uncomfortable, because it inverts the implicit deal of the senior hire. You were hired to bring expertise. The expectation, internalized over a career, is that you arrive and apply the expertise. In a founder-led company at the top of its category, the deal is different. You arrive and you study. You apply expertise where the gap is real and you adopt the local standard where the gap runs the other direction. The expertise that matters most is the discrimination between the two cases, and that discrimination requires intellectual humility in a register that most senior careers do not train.
The selection problem on the company’s side is the mirror of this. You cannot hire for the absence of the fixing reflex, because almost everyone at that level has it. You hire for curiosity and for intellectual humility, you set an explicit early expectation that the burden of proof for changing a load-bearing element sits with the person proposing the change, and you watch what happens in the first ninety days. The executives who treat the existing system as a puzzle to understand are the keepers. The executives who treat it as a problem to fix are the leak.
The founder has a corresponding responsibility, and most founders underestimate it. You cannot expect a senior hire to recognize a load-bearing choice without articulating it. The choices are obvious to you because you made them under the constraint they solve. They are not obvious to anyone else. The founder who hires a senior executive and says “come in and figure out what to fix” is not delegating; they are setting the executive up to dismantle the thing the founder built. The minimum is to name the choices that are wired into the moat, explain the constraint each one solves, and make clear that those choices are not on the table. Anything not on that list is genuinely open.
The founder side of this is harder than it looks from the outside. Running the thing you built is one of the hardest things to do in a sustained way without losing yourself in it. The pressure to dilute the load-bearing choices comes from every direction at once. The new executive proposes the standard playbook. The board member who has seen ten other companies suggests benchmarking against them. The investor flags the unusual customer concentration as a risk. The HR consultant notes that the compensation structure is non-standard. Each individual challenge is reasonable on its own merits. The cumulative effect is to grind the company toward the median, choice by choice, while everyone involved believes they are professionalizing the operation.
Staying true to what you built is not a matter of stubbornness. It is a matter of articulation. The founders who lose the thing they created are not the ones who gave in to a single bad argument. They are the ones who never made the load-bearing choices explicit, even to themselves. When every choice is implicit, every choice is negotiable, and the negotiations happen one at a time, without the architect noticing that the cumulative trajectory is rebuilding the median company they started the company to avoid being. The minimum the founder owes themselves is the same thing they owe a senior hire: a written list of the choices that are wired into the moat, the constraint each one solves, and the conditions under which any of those choices would need to change. Not as a defensive document, but as a working artifact that lets the founder distinguish a real challenge from a normalization pressure dressed up as one. Without that artifact, the founder will negotiate against themselves and call it open-mindedness.
There is a separate failure mode where the founder gets this wrong from the other side. The founder who treats every challenge as an attack on the moat, who refuses to distinguish load-bearing from accidental, who confuses staying true to the company with refusing to let the company evolve, produces the same value destruction by a different path. The list of load-bearing choices is not the entire system. The parts not on the list are open, and a founder who cannot tell the difference is no longer functioning as the architect. They have become the obstacle. Board members who have watched a founder cross that line will recognize the moment it happened, often well before the founder does. The cure for the executive’s fixing reflex is curiosity about why the system looks the way it looks. The cure for the founder’s defending reflex is the same discipline applied inward: the list, the constraints, the conditions under which a choice is open.
The founder being in the building is not a constraint on your authority. It is the reason the company is worth joining in the first place. The mistake is treating the founder as a legacy figure to be managed, rather than as the architect of the thing you came to operate. Get that orientation right and the rest of the work becomes possible. Get it wrong and you will spend your tenure dismantling the moat that made the company attractive enough to bring you in.
Leave a Reply