People problems feel personal. They have faces attached to them. A manager who cannot seem to execute. A team that keeps missing the point. A senior hire who came in with strong credentials and is not performing the way the founder expected. When these patterns emerge, the natural response is to address the person: coach them, manage them more closely, or replace them.
The problem with that response is not that it is wrong about the person. It is that it is asking the wrong diagnostic question. The question most founders are asking is: what is wrong with this person? The more useful question is: what structural condition is producing this pattern in otherwise capable people?
Three patterns in particular account for the majority of what founders classify as people problems in companies between 10 and 75 employees. In each case, the structural condition producing the pattern is identifiable, architectural, and resolvable — without replacing the people involved.
One. The manager who cannot seem to execute independently
The founder hired an operations manager, a director of sales, or a functional lead with the explicit expectation that this person would take ownership of their domain and run it. Three months later the founder is still deeply involved in every significant decision in that domain. The manager escalates constantly. The founder interprets this as a confidence problem, a capability gap, or a failure to take initiative.
In most cases it is none of those things. It is a decision authority problem. The manager cannot execute independently because independent execution requires knowing what you are authorized to decide, at what threshold, through what process, and what happens when a decision exceeds that threshold. In the absence of that architecture — a decision authority map that defines the boundaries clearly — the rational behavior for any competent manager is to escalate. They are not failing to take initiative. They are correctly reading a structure that has not given them the backing to decide.
The diagnostic test: can the manager articulate, without asking the founder, what decisions are within their authority and what decisions require escalation? If the answer is no — if the authority boundaries are unclear or undefined — the execution problem is not in the person. It is in the architecture.
This is not a mindset challenge. It is a structural one.
Two. The team that keeps missing the point
The founder communicates a strategic direction. Clearly, directly, more than once. And then watches as different parts of the team execute different versions of it. The marketing team heard one thing. The operations team heard another. The sales team is still executing last quarter’s direction because no one formally told them it had changed. The founder concludes that the team does not listen, cannot think strategically, or lacks the organizational IQ to translate direction into action.
The structural diagnosis is different. The team is not missing the point. The organization has no mechanism for ensuring that the point lands consistently. There is no defined process for converting strategic direction into operational meaning — no translation layer, no version control for organizational priorities, no distribution system that gets the same interpretation of the same direction to every function simultaneously. Different people heard different things because they were in different conversations, absorbed the direction through different filters, and had no common reference point for what the direction meant for their specific work.
This is the Vision-Capture bottleneck described in The Bottleneck Files series. The team’s divergent execution is not evidence of their failure to understand. It is evidence of a translation architecture that does not exist. The diagnostic test: if the founder asks three different team members to describe the current strategic priority, do the answers align? If they do not, the problem is not comprehension. It is architecture.
Three. The strong hire who is not delivering
The founder recruited carefully. The candidate had relevant experience and performed well in the interview process. Six months in, the results are not matching the expectation. The founder is disappointed, the hire is frustrated, and the relationship is deteriorating.
Before concluding that the person is wrong for the role, the structural diagnosis requires three questions. First: has the role been defined clearly enough that the person knows what success looks like and how it is measured? Senior roles in founder-led companies are frequently defined by title and general responsibility without outcome ownership or decision authority — which means a capable person may have no reliable way to know whether they are performing well. Second: does the person have the information they need to make the decisions their role requires? Information in founder-led organizations is frequently founder-gated, which means that a capable person may be deciding with systematically incomplete inputs. Third: are there structural conditions — competing authority, undefined accountability, founder override patterns — that are preventing effective performance regardless of capability?
The strong hire who is not delivering is one of the most expensive misdiagnoses in founder-led company development. Replacing a capable person who is operating inside a structural failure does not fix the structure. The next person hired into the same role will encounter the same conditions and produce similar results.
The underlying pattern
Not every performance issue is structural. But recurring patterns across otherwise capable people almost always warrant structural investigation before personnel decisions are made.
These three patterns share a common structural logic. In each case, the founder is observing a behavioral outcome — escalation, divergent execution, underperformance — and attributing it to the individual. The structural diagnosis reveals that the behavior is a rational response to an architectural condition: undefined authority, absent translation mechanisms, role design that cannot support independent performance.
This distinction matters because the interventions are entirely different. People interventions address the individual: coaching, performance management, replacement. Structural interventions address the architecture: decision authority maps, translation systems, role clarity frameworks, information flow design. People interventions applied to structural problems produce temporary improvement at best and accelerating frustration at worst, because the structure that is generating the behavior remains intact.
If the same type of problem reappears with different people in the same role or the same function, the problem is not in the people. It is in the structure those people are operating inside.
Structural conditions produce behavioral patterns. The patterns feel personal because they are expressed through people. But the condition generating them is architectural — and architectural conditions do not resolve through people interventions.
Before the next performance conversation, the next hiring decision, or the next reorganization, the more useful question is not: what is wrong with this person? It is: what structural condition is this person operating inside, and is that condition designed to allow them to succeed?
References
Galbraith, J. R. (1973). Designing Complex Organizations. Addison-Wesley.
Mintzberg, H. (1979). The Structuring of Organizations. Prentice-Hall.
Wasserman, N. (2012). The Founder’s Dilemmas: Anticipating and Avoiding the Pitfalls That Can Sink a Startup. Princeton University Press.
Legacy Line Operations works exclusively with founder-led companies between 10 and 75 employees.
This post is part of the Signals & Symptoms Series — observable patterns that precede operational breakdown in founder-led companies.
legacylineoperations.com