The Waterline Model: Why Blaming People is an Architectural Error
Most leaders react to a failing team by focusing on the people. They assume “the vibe is off,” “there’s a lack of talent,” or “those two don’t get along.” This is a high-latency, high-bias protocol. It treats the symptoms while ignoring the transmission mechanism of the failure.
In the latest Lenny’s Newsletter, Molly Graham (formerly of Google, FB, and CZI) performs an autopsy on this management trap. She introduces the Waterline Model: a diagnostic framework that forces you to “snorkel before you scuba.”
If your team is underperforming, the problem is likely structural, not personal. Blaming the individual before fixing the system is an architectural error that creates a permanent “Clarity Tax” on your organization.
The Autopsy of the “Vibe” Problem
When a team misses goals or timelines slip, the social instinct is to look at the bottom of the waterline: the individual. We assume a skill gap or a lack of motivation.
The Waterline Model re-indexes this search. It defines four layers of system failure, in order of impact:
1. Structure: Vision, goals, and role clarity.
2. Dynamics: How decisions are made and how conflict is resolved.
3. Interpersonal: Trust and tension between specific nodes.
4. Individual: Skill gaps, stress, or values.
The “Snorkel before you Scuba” rule means you must rule out structural and dynamic failures before you ever touch an individual’s performance plan. In most cases, people are behaving rationally inside a broken system. If they are “rowing in different directions,” it is usually because the structure hasn’t defined the destination.
Structure: The Most Common System Failure
A team without structural clarity is running a lossy protocol.
Graham notes that most “performance issues” disappear once you re-clarify the mandate and individual role definitions. When roles overlap or incentives are misaligned, two people stepping on each other’s toes isn’t “interpersonal friction.” It is a structural overlap wearing a human face.
The “System Steward” realizes that people are generally smart and motivated. If they aren’t shipping, do not look at their “attitude.” Look at the Coordination Tax of their ambiguity. If success isn’t defined, every action is a guess.
Dynamics and the “Rational Slowdown”
Dynamics are the cultural norms of how a team works day-to-day. This is where the most dangerous feedback loops live.
Consider a team that moves slowly despite having clear goals. If a founder or leader consistently “swoops in” and unmakes decisions at the last minute, the team will adapt in a very rational way: They will slow down. They will escalate every minor choice to avoid being wrong.
This isn’t a lack of speed. It is self-protection. The “Dynamics Tax” here is the cost of navigating an unstable decision-making environment. You cannot fix this with a new project management tool. You fix it by changing the leader’s behavior and normalizing a “low-latency” decision protocol.
Only Scuba When Necessary
The ultimate goal of the Waterline Model is to prevent “Relitigation” of people’s worth.
When the system is sound—the goals are clear, the roles are clean, and the dynamics are stable—then, and only then, does an individual’s failure become a decision point. At that layer, management is no longer a diagnostic; it is a verification of fit.
Decisiveness at the individual level is kinder than lingering in a broken system. But that decisiveness is only valid if you have cleared the water above it.
The Path to High-Signal Management
The lesson of the Waterline Model is that Management is a Debugging Process.
If you are building a high-velocity product team, you cannot afford to waste time “scuba diving” into personalities while your structural hull is leaking. You must push clarity and decision-rights as close to the point of action as possible.
Stop optimizing for “Team Vibes.” Optimize for the Flow of Truth through the structure. When the boat is rigged correctly, the crew will almost always find the way.