Framework: The 'Waterline Model' for Debugging Teams

A new essay details the 'Waterline Model' for diagnosing team dysfunction. It reframes issues like missed deadlines not as people problems, but as symptoms of hidden structural factors like unclear ownership or misaligned incentives. The model urges leaders to 'debug the system' before reshuffling staff.

The Waterline Model was developed by Molly Graham, who shaped people systems and mobile strategy during periods of hyper-growth at companies like Facebook, Google, and Quip. The framework emerged from her experience leading teams where the instinct is to blame individuals, rather than investigating underlying systemic issues. The model's core principle is to "snorkel before you scuba," asserting that roughly 80% of team problems are caused by issues at the surface—structure and dynamics—not by the individuals deep below. Before examining interpersonal conflicts or individual performance, a leader should first investigate whether goals, roles, and expectations are clear for everyone on the team. For engineering teams, these structural problems manifest as unclear project requirements, shifting priorities, inefficient code reviews, or a theoretical release process. These issues directly impact key DevOps Research and Assessment (DORA) metrics by increasing lead time for changes and change failure rates while decreasing deployment frequency. The four layers of the model, in order of investigation, are Structure (clarity of goals and roles), Dynamics (how decisions are made and meetings are run), Interpersonal (tensions between team members), and Individual (skill gaps or personal issues). What often appears as interpersonal conflict is frequently a symptom of structural flaws, such as two engineers having overlapping ownership because their roles were never clearly defined. Ignoring these structural dysfunctions creates significant financial drain through high employee turnover. The cost to replace a single software engineer can range from 6-9 months of their salary, with some estimates putting the total impact, including lost productivity and recruitment fees, at 100-150% of their annual salary. This high attrition imposes hidden taxes on an organization. A "Knowledge Transfer Tax" is paid as senior engineers spend billable hours retraining new hires, a "Recruitment Amortization" cost is incurred when short tenures prevent a return on the initial $20,000 to $40,000 spent on hiring, and a "Defect Remediation" tax is paid as inexperienced developers are more likely to ship bugs. The Waterline Model shares philosophical ground with W. Edwards Deming's principle that most organizational problems are systemic. It serves as a diagnostic tool that complements other frameworks like Patrick Lencioni's "The Five Dysfunctions of a Team," but with a stronger initial focus on organizational design over interpersonal behaviors. The essay detailing this model comes from Lenny Rachitsky, who previously led product and growth teams at Airbnb after his own startup was acquired by the company. His newsletter has become a significant resource for product and engineering leaders by translating operational experience from high-growth tech environments into actionable frameworks.

Get your own daily briefing

Scout delivers personalized news, insights, and conversations tailored to your role and industry.

Download on the App Store

Shared from Scout - Be the smartest in the room.