Attention Follows Accountability

A manager left one of our projects.

Like many organizations, we did what organizations often do. We redistributed the work.

The obvious choice was someone already on the team. They knew the project well, had the trust of the client, and had been growing into broader responsibilities for some time.

On paper, it was a sensible decision.

What we overlooked was that nothing else had changed.

The client was still demanding. Their existing responsibilities hadn’t gone anywhere. We had simply added another role without taking anything away.

A few days later, I got on a call with them.

They were clearly under pressure. Their thoughts were scattered. Every sentence jumped to a different concern. Deliverables. Team issues. Stakeholders. The client. Timelines. The new responsibilities. What might go wrong next.

At one point, they missed something I knew they would normally catch almost automatically. It wasn’t a lack of experience. I’d seen them handle similar situations before.

That conversation left me with a very different understanding of what was happening.

Attention follows accountability.

The work itself hadn’t become more difficult. They already understood the project. They knew the client. They had the judgment for the role.

What had changed was what they now felt responsible for.

The moment they became accountable for deliverables, team handling, stakeholder expectations, timelines, and everything that could go wrong, those concerns naturally occupied most of their thinking.

The quality work hadn’t become harder.

It had simply lost the focus it needed.

Once I understood that, it became clear this was not just about helping them handle the situation better.

They didn’t need different skills.

They needed different conditions.

So instead of asking them to absorb more, I started looking for pressure that could simply be removed.

The first step was not removing all the responsibility.

That wasn’t realistic. The role still needed someone to step up. The project still had commitments. The client still had expectations.

The question was different.

What actually needed their attention right now?

I spoke with the project leadership and examined their workload. We identified what genuinely mattered, moved a few things away, and gave them room to focus on the areas where their judgment mattered most.

Looking back, I think the difficult part of transitions is that responsibilities usually move immediately, but understanding what a person can realistically absorb takes more time.

In this case, we had added new expectations without taking a closer look at everything they were already carrying.

Reducing the pressure was only one part of the conversation.

The other part was helping them adjust to the role they were stepping into.

When people move into broader responsibilities, there is often an instinct to hold on to everything. Every issue feels urgent. Every escalation feels like something they need to personally solve.

We spent time separating what was truly important from what only felt urgent in that moment.

Some things genuinely needed their attention. Some things needed their guidance. Some things simply needed to be delegated.

The shift was from trying to personally solve every problem to deciding where their involvement mattered most.

The goal was not to lower the bar or reduce ownership. It was to help them understand where their involvement created the most value.

That distinction is easy to miss when you are in the middle of the pressure.

Over the next few weeks, the change was visible.

The pressure did not disappear. The role was still demanding. The client still had expectations, and the team still needed direction.

But the nature of the conversations changed.

The scattered thinking from those early conversations was gone. There was more clarity around what needed immediate attention, what could wait, and where their involvement would make the biggest difference.

The role had not become easier. The expectations had not reduced.

But they were no longer trying to personally carry everything. They had started operating from a place of ownership rather than constant reaction.

They had the clarity to use the judgment and experience they already had.

This experience made me think about how the role of a senior leader changes over time.

Earlier in my career, my value came mostly from solving problems myself. Having the right answer, jumping into difficult situations, and helping move things forward.

With more responsibility, the role changes.

It is no longer only about solving problems. It is also about noticing when someone has the capability to solve them, but the weight of everything they are carrying is getting in the way.

As people take on broader roles, their accountability naturally expands. They start carrying deliverables, teams, stakeholders, timelines, and risks. That is part of growth.

But accountability has a cost. It consumes attention.

The challenge is that the same attention that gets consumed by managing the responsibility is often the attention needed to make the right decisions within that responsibility.

In this case, the answer was not reducing the accountability. It was creating enough clarity for that accountability to be carried well.

The pressure did not disappear. The responsibility did not reduce. But they had the clarity to use the judgment they already had.