Cross-functional projects are notorious for stalls and failures. The reason is rarely a lack of effort. It's a lack of clear ownership. When everyone is responsible, no one is. The "matrix" structure that makes companies agile can also create accountability gaps where key decisions languish and deadlines slip.
This isn't a people problem; it's a structural one. Without a clear owner, a project lacks a final decision-maker. Team members get conflicting instructions. Priorities diverge. The project loses momentum and eventually gets deprioritized. The solution is to assign ownership before the work begins.
The Single, Accountable Owner
Every cross-functional project needs one—and only one—accountable owner. This person is the project's "CEO." They are responsible for the project's success or failure. This doesn't mean they do all the work, but they are on the hook for the outcome.
The owner is responsible for:
- Defining success: What does "done" look like? What are the specific, measurable outcomes?
- Securing resources: Are the right people and budget allocated?
- Making final decisions: When the team is at an impasse, the owner makes the call.
- Communicating status: Keeping stakeholders informed of progress, risks, and changes.
The accountable owner is not a project manager. A project manager tracks tasks and timelines. The owner is responsible for the *result*. This is often a Director or VP-level individual who has the authority to unblock issues and make binding decisions.
The Directly Responsible Individual (DRI)
While the owner is accountable for the *what*, each workstream within the project needs a Directly Responsible Individual (DRI). The DRI is accountable for the *how*.
For example, in a new feature launch, you might have:
- Accountable Owner: VP of Product
- DRIs:
- * Engineering Lead (for the build)
- * Marketing Manager (for the launch campaign)
- * Sales Director (for sales enablement)
Each DRI has full ownership over their workstream. They manage the tasks, the timeline, and the deliverables for their part of the project. They report progress and escalate roadblocks to the accountable owner. This structure ensures that every component of the project has a clear leader responsible for its execution.
The Accountability Framework in Practice
How do you implement this?
- Kickoff Charter: Before any work starts, create a simple project charter. This document should name the single, accountable owner and each DRI for the major workstreams. It should also define the project's goal and key metrics.
- Define Communication: The charter should specify the communication rhythm. A weekly status update from DRIs to the owner is a good starting point. This isn't a detailed report; it's a quick summary of progress, risks, and needs.
- Empower Decision-Making: The accountable owner must trust their DRIs. DRIs should have the autonomy to make decisions within their workstream. The owner only steps in to resolve conflicts between workstreams or to make a final call when a DRI escalates an issue they cannot solve.
This isn't about adding bureaucracy. It's about creating clarity. By defining a single, accountable owner and a clear set of DRIs, you eliminate the ambiguity that kills cross-functional initiatives. You replace confusion with clear lines of responsibility, ensuring that projects move forward and deliver results.