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.

When conducting manual "open coding" for AI evals, teams often get bogged down by trying to reach a consensus. Instead, appoint a single person with deep domain expertise (often the product manager) to be the "benevolent dictator," making the final judgment calls on error categorization. This makes the process tractable and fast.

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.

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.

To foster productive debate, teams must move beyond simply encouraging disagreement. Implement specific, pre-agreed rules of engagement, such as using a neutral mediator or applying a 'two-minute rule' that grants a person uninterrupted speaking time. These protocols transform potential fights into structured, truth-seeking conversations.

To avoid chaos in AI exploration, assign roles. Designate one person as the "pilot" to actively drive new tools for a set period. Others act as "passengers"—they are engaged and informed but follow the pilot's lead. This focuses team energy and prevents conflicting efforts.

Research shows power degrades empathy, making leaders less objective. A practical system to counteract this is to formally assign a team member the role of 'devil's advocate' for major decisions. This institutionalizes dissent as a process, removing the personal and career risk of challenging authority.

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.

Instead of asking employees what they do, map your core business processes (e.g., customer acquisition). Then, assign each step to a person. This bottom-up approach reveals who is truly driving value and who is overburdened, leading to more accurate role definitions based on business impact.