We scan new podcasts and send you the top 5 insights daily.
Coordination work does not disappear when roles like project coordinators or scrum masters are eliminated. Instead, a 'coordination vacuum' is created where essential tasks are either dropped or haphazardly absorbed by unprepared team members, leading to widespread inefficiency and chaos.
If two people are responsible for watering a plant, it dies from either overwatering or neglect. This is why scaling companies must be zealous about assigning a single Directly Responsible Individual (DRI) for every key initiative. Shared ownership means no ownership, especially for cross-functional projects.
Effective delegation of decision-making authority is impossible without first ensuring leaders are deeply aligned on organizational objectives. When individuals are empowered to make choices but pull in different directions, the result is a quagmire, not progress. Alignment must precede autonomy.
Intentionally assigning fewer people to a project than seems necessary forces extreme focus on the highest priorities. Overstaffing is "poison" because it breeds politics, encourages work on non-essential tasks, and creates cruft that slows the entire company down.
A successful reorg simplifies work, but delayering often does the opposite. Pushing management, QA, and coordination tasks onto developers dramatically increases their cognitive load, harming their primary function and leading to burnout. This is a key failure metric for any flattening initiative.
Highly skilled teams will repeatedly fail if the surrounding organizational structure—decision-making, governance, silos—is dysfunctional. The root cause of failure is often not the team's ability but systemic issues that must be addressed at a leadership level for anyone to succeed.
Companies like Amazon and Meta that cut middle management are not necessarily wrong to flatten their organization, but they err by doing so without first redesigning the underlying system. The true mistake is removing the people responsible for coordination and decision-making without fixing the processes they managed, leading to chaos.
As teams grow, ambiguity over ownership increases, causing key tasks to be dropped. The RACI model (Responsible, Accountable, Consulted, Informed) combats this by clarifying roles upfront for any project, ensuring clear ownership and preventing the diffusion of responsibility that paralyzes larger groups.
The primary source of friction between product and project functions isn't a lack of skills but rather unclear ownership, siloed planning, and conflicting success metrics. The solution is proactive, early alignment on roles, tools, and a shared definition of success.
An event manager, solely responsible for all logistics for 30 events in three weeks, made a major booking error. This demonstrates that assigning high-volume, complex projects to a single person without support turns them into a single point of failure, making critical mistakes almost unavoidable.
The Waterline Model suggests 80% of team dysfunctions are rooted in structural problems (unclear goals, roles), not interpersonal issues. Before you 'scuba dive' into individual conflicts, 'snorkel' at the surface by clarifying roles and expectations. This simple act solves the majority of problems.