Last time, I wrote about measurement.
We can send an email, deliver a presentation, publish a guide, or conduct training without knowing whether the communication actually produced the intended outcome.
Measuring what we produce is relatively straightforward. Understanding what changes because of our work is more difficult.
But that raises another question I've been thinking about: Who is responsible for what happens after the work is completed?
The difference between completing work and producing an outcome
Imagine a university notices that students are struggling to understand their degree requirements. An investigation identifies several problems.
Students don't always know which requirements apply to them. Information is distributed across multiple websites.
Some students misunderstand the relationship between course selection and degree progression.
The university decides to improve its communication. A communications specialist creates a guide. An academic advisor reviews the content. A designer produces a visual resource. A manager approves its distribution. Students receive the material.
Everyone completes their assigned work.
But several months later, students are still making the same mistakes.
Was the project successful?
The guide was produced. The information was distributed. The assigned tasks were completed. But the original problem may not have improved. Someone needs to investigate why. And someone needs to be responsible for deciding what happens next.
Responsibility extends beyond the intervention
Throughout these emails, I've been exploring different parts of making knowledge useful. We started with identifying problems and turning evidence into recommendations.
Then we examined priorities, ownership, handoffs, resources, delegation, feedback, and measurement.
Each of those capabilities matters. But they also have to work together.
An intervention can be well designed and poorly implemented. It can be implemented successfully but inadequately resourced.
It can be adequately resourced but poorly coordinated. It can produce measurable changes that don't solve the original problem. This is why I'm becoming interested in executive responsibility.
Not necessarily the job title; the type of ability it requires.
The ability to remain accountable for an outcome across the decisions, people, resources, and adjustments required to produce it.
Following the problem all the way through
Consider the student communication example again. If I were responsible for the outcome, I would need to follow a sequence.
1. Diagnosis: What problem are we solving?
Students are making avoidable academic planning errors. But why? Are requirements unclear? Are students using outdated information? Are they receiving conflicting advice? Are they struggling to apply information to their individual circumstances?
The diagnosis matters because different causes require different interventions.
2. Decision: What should we change?
Perhaps the evidence suggests students need a clearer explanation of how to interpret degree requirements. We decide to create a guide and introduce it at a particular point in their academic progression.
That's a proposed solution, not yet a demonstrated success.
3. Coordination: Who needs to contribute?
Advisors understand recurring student questions. Academic administrators understand requirements and policies. Communications staff understand how to structure and distribute information. Students can help us test whether the resource makes sense.
Someone has to coordinate those contributions.
4. Resources: What will the work require?
Staff time. Access to accurate information. Design capacity. A distribution channel. Time to test the resource.
Without those resources, the intervention may remain an intention.
5. Implementation: Did we do what we decided?
Was the guide produced? Was it reviewed? Did students receive it at the intended time? Were the people responsible for distributing it prepared?
Implementation matters, but it isn't the endpoint.
6. Evaluation: Did the problem improve?
Can students use the guide to interpret their requirements more accurately? Are they making fewer of the specific errors we identified? What questions remain? What evidence would justify changing the intervention?
This is where responsibility becomes especially important. Because the person accountable for the outcome cannot simply point to the completed guide and declare success.
Accountability isn't control over everything
There's a tension here that I'm trying to understand.
If I'm responsible for an outcome, I can't personally control every factor that influences it.
Students make their own decisions. Employees bring different capabilities and experiences. Customers respond unpredictably. Budgets change. Unexpected problems emerge.
So executive responsibility cannot mean guaranteeing a particular result regardless of circumstances. Nor can it mean personally completing every task.
I'm beginning to understand it as something more practical.
Taking responsibility for the quality of the decisions, coordination, monitoring, and corrective action within your authority.
That includes acknowledging when an intervention hasn't worked. It includes recognizing when the original diagnosis was incomplete. It includes changing direction when the evidence warrants it. And it includes being clear about what remains outside your control.
The ability I'm trying to develop
Much of my professional life has involved helping people understand complicated situations.
I teach. I advise. I research. I interpret evidence. I communicate recommendations.
Those are capabilities I've spent years developing.
But I'm increasingly interested in what happens beyond the recommendation. Can I organize the resources? Can I coordinate the people? Can I establish expectations? Can I support someone else's performance? Can I evaluate whether the intervention produced the intended outcome? And can I make the next decision when things don't go as planned?
These are different responsibilities from simply being knowledgeable. They're also important to the kind of life and business I'm trying to build.
I want to use the capabilities and resources I've accumulated to create income-producing assets and systems that don't require my continuous personal labour.
That means learning to work through people, processes, and resources without abandoning responsibility for results.
The goal isn't to make myself responsible for doing everything. It's to become capable of building and overseeing systems in which the necessary work can happen without me doing everything.
This is what I am doing
Think about a problem you've recently tried to solve.
Perhaps you made a recommendation, created a resource, assigned work, or introduced a new process.
Now ask:
What was the original problem?
What outcome did I want to produce?
What intervention did I choose?
Who was responsible for implementation?
What evidence do I have that the outcome improved?
Who is responsible for deciding what happens next?
Because when responsibility ends with task completion, problems can survive even after everyone has done their job. And when nobody owns the outcome, the system can continue producing activity without producing improvement.
From knowledge to responsibility
Over the past several emails, I've been exploring what it takes to move from understanding a problem to organizing an effective response.
I'm learning that producing knowledge is only one part of that process. We also need to make decisions.
Set priorities. Allocate resources. Coordinate people. Delegate responsibility. Provide feedback. Measure outcomes. And respond to what we discover.
These aren't simply management techniques. They're capabilities that help turn what we know into what we can accomplish. That's the direction I want to keep developing through Leverage.
Not just understanding complicated systems. Not just explaining them.
But learning how to make informed decisions within them, coordinate resources, and take responsibility for what happens next.
Because someone can own the task, someone can own the process, and someone can own the communication.
But someone still has to own the result.
— Greg Campbell
Leverage your experience.
