That chaotic, ambiguous feeling as a company scales isn't a sign of agile culture; it's the smell of burnout. It represents a compounding debt of stress, heroic efforts, and invisible, unowned work. Ambiguity that feels like magic at 10 people becomes pure chaos at 100.
Regardless of title, the individual who owns the Profit & Loss (P&L) statement for a product is its true manager. A Product Manager without P&L authority is effectively a proxy whose roadmap and decisions can be legitimately overridden by the P&L owner. This is the root of many roadmap conflicts.
Instead of immediately diving into documenting roles with tools like RACI, the first step should be to identify and name a "referee." This is an individual or body with the explicit, recognized authority to arbitrate and settle role-based disputes when they inevitably arise.
Hiring documents often swing between demanding a "product unicorn" with an impossible mix of skills and a watered-down description so vague it attracts completely unqualified applicants. Both extremes fail to define the role effectively and create noise in the hiring process.
Leaders often try to emulate military-style delegation, like moving authority to the information. This fails because corporations neglect the massive prerequisite investment in training and building shared context that makes such empowerment possible in the military. It's a cargo-cult approach to leadership.
Unpredictable intrusions by senior leaders (the "Hippo") hollow out authority and train the entire organization to stop making decisions. Instead, everyone learns to wait for the Hippo's opinion, creating systemic decision latency. The unpredictability, not the intrusion itself, is the primary source of chaos.
The process of clarifying roles is itself a decision-rights question that is typically unowned. This creates a paradox where the organization is stuck in turf wars because the very authority required to solve the problem is what's in dispute. The system lacks a mechanism to fix itself.
The RACI matrix is frequently a fictitious document, created once by a project manager and then filed away. It doesn't reflect the reality of how decisions are made and is typically only referenced after something has gone wrong to assign blame, rather than to provide proactive clarity.
Job descriptions are written to attract candidates, not to guide daily decision-making. Relying on them for operational clarity creates a gap between what's on paper and who actually decides, leading to career-killing confusion. They are the wrong artifact for clarifying real-time roles and responsibilities.
The perceived magic of early-stage startups isn't role ambiguity, but the rapid feedback and high trust that small teams enable. Founders who try to preserve ambiguity as "culture" during scaling are misdiagnosing their own success. This leads to chaos and burnout rather than maintaining the initial energy.
Don't assume Human Resources owns the solution to role confusion. Modern HR departments are often not trained in organizational design and lack the expertise to address these deep-seated structural problems. The responsibility ultimately falls to senior leadership to define the operating model.