.jpg)
There is a pattern that shows up in nearly every founder-led company that hits the 15 to 40 person stage.
A department head who was strong in the early days starts to slip. Goals get missed. Updates get vague. The founder starts checking in more, which creates friction. The department head starts to feel micromanaged. The founder starts to wonder if they hired the wrong person.
Sometimes the diagnosis is right and the person is genuinely not suited for the role. But more often, what looks like a people problem is a system problem wearing a people problem's clothes. The department head is not underperforming because they stopped caring or stopped trying. They are underperforming because the conditions required for accountability were never actually installed.
Understanding why this happens is the first step to fixing it without burning through your leadership team.
Accountability requires something precise to be accountable to. When quarterly goals are defined at the level of themes or initiatives rather than measurable outcomes, the department head has no clear target to aim at and no clear standard against which their performance can be evaluated.
"Improve customer retention" is not a goal. "Reduce monthly churn from 4.2% to 2.8% by March 31" is a goal. The difference is not just semantic. The first version gives the department head room to report progress indefinitely without the needle actually moving. The second version makes underperformance visible and undeniable, which is uncomfortable but necessary for real accountability to function.
When founders complain that department heads are not hitting their numbers, it is worth asking first: were there numbers to hit? In many cases, the answer reveals that the goals set at the last planning session were directional at best. Accountability cannot be enforced against a direction. It can only be enforced against a commitment.
Cross-functional goals are genuinely hard to assign. A pipeline growth goal involves both marketing and sales. A product adoption goal involves both product and customer success. The temptation is to list both departments as owners, which feels fair and collaborative but functionally destroys accountability.
When two people own a goal, each has a natural exit. If the goal is missed, marketing points to what sales did not do. Sales points to the leads marketing generated. Both are partially right, which means neither is fully accountable, which means nobody is.
Single ownership does not mean the other departments are uninvolved. It means one person is the accountable party who drives the work, coordinates across functions, and answers for the result. The other departments support. One person owns.
Department heads who have never had single, unambiguous ownership of a goal have never had a real experience of accountability. They have had shared responsibility for outcomes that were always someone else's fault when they were missed. Expecting them to suddenly perform differently without changing the ownership structure is not a leadership problem. It is a planning problem.
Accountability without visibility is accountability in name only.
If a department head knows that their goal progress will not be reviewed until the end of the quarter, they face a behavioral dynamic that works directly against execution. The goal is real but distant. Other work is immediate and pressing. The rational response, from the brain's perspective, is to defer the goal-related work in favor of whatever is in front of them today. Weeks pass. The quarter is suddenly half over. Recovery becomes the plan.
This is not a willpower problem. It is what happens when goals live in a document nobody looks at between the planning session and the QBR. The structural fix is continuous visibility: a centralized dashboard where goal progress is updated and visible to the whole leadership team at all times.
When every department head can see every other department's progress in real time, the social dynamic shifts. Falling behind is no longer invisible until it is too late to address. It is visible the week it starts to happen. That visibility creates the ambient accountability that most founders try to create through check-ins and status updates, but with a fraction of the friction.
Department heads often stop hitting numbers not because they stopped working but because they hit a wall and had no clear path to surface it.
A blocker might be a dependency on another department that has not moved. It might be a resourcing constraint the founder does not know about. It might be an assumption in the original goal that turned out to be wrong and needs to be renegotiated. In a company without a structured meeting cadence, these blockers sit. The department head either tries to solve them alone, drags the founder into an ad hoc conversation, or quietly adjusts their expectations for the goal without anyone formally agreeing to the change.
None of these are good outcomes. The first creates bottlenecks. The second creates chaos. The third creates the illusion of accountability without the substance of it.
A bi-weekly leadership meeting that explicitly surfaces blockers gives department heads a structured, expected place to raise what is in the way. The meeting is not a status report. It is a decision-making forum. Blockers get named, owners get assigned, and the founder is not the one who has to initiate every problem-solving conversation.
When department heads have that forum, the nature of the conversation changes. Raising a blocker is no longer an admission of failure. It is what the meeting is for. That shift alone meaningfully reduces the amount of silent underperformance that builds up between planning sessions.
In many founder-led companies, the founder is the entire accountability infrastructure. They remember what was agreed. They follow up when things go quiet. They push when progress stalls. They are the reason goals get hit at all.
This arrangement works until it does not. It does not scale beyond a certain team size because the founder runs out of bandwidth. It also creates a dependency that works against the department heads developing genuine ownership instincts. When accountability is something the founder enforces rather than something the system produces, department heads learn to respond to founder pressure rather than to internalize accountability as a value of their role.
The result is a leadership team that performs when the founder is watching and drifts when the founder is not. The founder experiences this as a people problem. The real problem is that they built a system where their presence is a load-bearing wall.
Removing the founder from the accountability role requires replacing them with something structural: visible goal tracking, a regular review cadence, and single ownership that is public enough to carry social weight. When those three things exist, accountability stops being something the founder provides and starts being something the system produces.
The clearest signal that accountability has become structural rather than founder-dependent is when department heads start holding each other accountable without the founder prompting it.
That happens when goals are specific enough to be evaluated objectively, ownership is clear enough that everyone knows who answers for each outcome, visibility is high enough that drift is noticed early, and the meeting cadence creates a regular, expected forum for surfacing what is in the way.
None of this requires replacing your department heads. In most cases, the people who appeared to be the problem perform significantly differently when the structure around them changes. The ones who still underperform after the structure is in place are the ones worth having a harder conversation about.
The sequence matters. Structure first. Evaluation second.
FounderMove installs the execution structure that makes department-level accountability structural rather than founder-dependent, through quarterly planning, centralized goal tracking, and bi-weekly facilitated leadership sessions.
