''' Cross-functional projects are where momentum goes to die. A new feature, a marketing campaign, a system upgrade—everyone agrees it’s a priority. The project kicks off with enthusiasm, but soon it stalls. Marketing is waiting on Engineering, who is waiting for feedback from Product. Deadlines are missed. Frustration mounts. In the retrospective, everyone points fingers. Sound familiar?
The common response is a call for “more collaboration” or “better communication.” These are not solutions; they are platitudes. The root cause of failure in cross-functional work is not a lack of willingness to collaborate. It’s a lack of a clear system for accountability.
The Real Cost of Vague Ownership
When no single person is accountable for an outcome, everyone is accountable. And when everyone is accountable, no one is. This ambiguity doesn’t just delay projects; it has a corrosive effect on the entire organization.
First, it creates decision-making bottlenecks. When a group is collectively responsible, every minor decision can require a meeting to achieve consensus. This slows progress to a crawl. Second, it erodes morale. Team members become frustrated when they can’t get the answers or resources they need because it’s unclear who has the authority to provide them. Finally, it breeds a culture of blame. It’s human nature to deflect responsibility when outcomes are poor. Without a clear owner, it is nearly impossible to diagnose *why* a project failed, dooming you to repeat the same mistakes.
The Myth of "Shared Ownership"
Many leaders champion the idea of “shared ownership.” It sounds collaborative and egalitarian. In practice, it is often a recipe for inaction and mediocrity. True accountability is not a group activity.
Imagine a ship with two captains. When a storm hits, who has the final say on which direction to turn? If they disagree, the ship is dead in the water. Shared ownership creates the same paralysis. For any given initiative, there must be a single person who is ultimately answerable for the result. This person is not expected to do all the work, but they are responsible for ensuring the work gets done. They are the final point of escalation and the ultimate decision-maker in a deadlock.
A Simple Framework: The DRI
To solve this, implement the concept of the Directly Responsible Individual, or DRI. The DRI is the one person who is accountable for the success of a project or initiative. They are the single source of truth and the owner of the outcome.
Here’s how it works:
- One DRI per Initiative: Every significant cross-functional project has a single, named DRI. This is non-negotiable.
- The DRI is the Shepherd, Not the Entire Flock: The DRI is responsible for creating a plan, securing resources, tracking progress, and unblocking issues. They coordinate the work of others, but they don’t do it all themselves.
- Define Supporting Roles: While there is only one DRI, others have clearly defined roles. The most common are “Consulted” (must provide input) and “Informed” (must be kept in the loop). The DRI is responsible for ensuring these stakeholders are properly engaged.
For example, for a new website launch, the Head of Marketing might be the DRI. They are accountable for the on-time launch. A designer is consulted on the visual identity. The Head of Engineering is informed of the launch timeline to ensure server readiness.
Putting the DRI Model into Practice
Adopting this model requires discipline, not new software or expensive consultants.
1. Start at the Top: For any new initiative, the leadership team must explicitly name the DRI as the first order of business. 2. Document and Communicate: The DRI’s name should be documented in the project plan, kickoff meeting notes, and any relevant communications. There should be zero ambiguity about who owns the project. 3. Empower the DRI: The DRI must have the authority to make decisions to move the project forward. If stakeholders disagree, the DRI listens to all input and makes the final call. Micromanaging a DRI defeats the entire purpose of having one.
Stop accepting ambiguity as a cost of doing business. True cross-functional accountability is not a mystery. It is the direct result of a clear, simple system. Appoint a DRI for every important project, empower them to succeed, and watch the blame game disappear. '''