Being Good at a Role Doesn’t Mean You Want More of It

When “you’re good at this” starts deciding your role

Imagine a project with several teams involved.

Someone needs to collect updates before the meeting. Someone has to notice that one team is waiting for another. Someone needs to follow up afterward so the same question does not appear again next week.

You are good at this.

So people ask you to handle it again.

Then again.

A few months later, your calendar is full of progress meetings and follow-up calls. Messages come to you because you usually know who is waiting for what.

Meanwhile, the technical work you wanted to spend the afternoon on is still open on your screen.

There may be nothing unreasonable about how this happened. Your coworkers may simply have noticed a real strength.

The important distinction is what comes next:

“I am good at coordinating” does not mean “I want coordination to become more of my job.”

One describes your ability. The other describes the direction you want your work to take.

A strength can become a role almost by accident

Suppose you are a network engineer who is good at explaining problems clearly.

During one project, you start translating technical details between engineers, managers, and another team. You keep conversations organized, so the project benefits from having you in the middle.

That is useful work.

The trouble is not that you did it.

The trouble comes if yesterday’s usefulness quietly becomes tomorrow’s job description without you ever deciding whether that is what you want.

You might eventually find yourself comparing two very different afternoons:

Afternoon A

• one hour checking a network design
• two hours testing a configuration
• one hour investigating a technical problem

Afternoon B

• one hour collecting progress updates
• one hour preparing a meeting
• one hour in the meeting
• one hour following up with different teams

You might be capable of both.

But if Afternoon A is the kind of work you want to deepen, that preference matters.

You do not need to prove that Afternoon B is bad work before saying so.

“I can do it” and “I want more of it” answer different questions

This is where the distinction becomes useful.

Consider these three statements:

I’m good at: keeping several teams aligned.

I’m willing to keep doing: the coordination that genuinely benefits from my technical knowledge.

I want more of: design, configuration, testing, and technical problem-solving.

Those statements can all be true at the same time.

That is a more accurate description than either extreme:

“I hate coordination.”

or:

“People depend on me for coordination, so I suppose this is the role I should keep moving toward.”

The first may reject a genuine strength.

The second can turn a strength into an obligation.

A better question is not simply, “What am I good at?”

It is:

“What mix of this work do I want to keep?”

Perhaps you are happy to run one technical handoff each week because your knowledge helps the teams understand one another. What you do not want is to become the default person for scheduling, collecting every status update, and chasing every unanswered message.

Now the issue is no longer vague.

You are not trying to escape “coordination.” You are deciding which coordination still belongs in the role you want.

Explain the mix you want, not just what you want to remove

That distinction also makes the conversation with a manager more concrete.

Compare these two versions:

“I want to do less coordination.”

and:

“I’m happy to keep owning the weekly technical handoff because my technical knowledge is useful there. I’d like to reduce some of the general scheduling and status follow-up, though, so I can spend more time on design and implementation.”

The second version gives the other person something they can actually discuss.

It recognizes why you have been trusted with the work.

It identifies what you are still willing to contribute.

And it makes the direction you want visible.

A simple structure is:

“I’m good at ___, and I’m happy to keep contributing to ___. I’d like more of my role to move toward ___.”

For example:

“I’m good at coordinating across teams, and I’m happy to keep handling the technical handoff. I’d like more of my role to move toward network design and implementation.”

That is different from rejecting your current role.

You are describing a preferred allocation of your time.

Sometimes the role really does require the work you want to reduce

There is an important limit.

Not every responsibility can be redistributed simply because you would prefer a different mix.

A senior specialist may genuinely need to coordinate with other teams. A technical lead may spend less time doing hands-on work because communication and decision-making are part of the role. A small team may not have another person who can take over the work.

In that case, the conversation gives you useful information even if the answer is no.

You can ask a more precise question:

Is this coordination a temporary consequence of the current project, or is it an essential part of the role I am moving toward?

If it is temporary, you may decide that the current imbalance is acceptable.

If it is fundamental to the role, you have learned something more important: progressing further in that direction may mean doing more of the very work you want less of.

That is not a reason to make an immediate career decision. It is a reason to stop treating promotion, expertise, and role preference as if they always point in the same direction.

Your strengths do not have to choose your direction for you

Being repeatedly trusted with something is useful information.

It tells you:

“I can contribute here.”

It does not, by itself, answer:

“Do I want more of my working life to look like this?”

You can respect the first answer without surrendering the second.

Before your next conversation about responsibilities, try completing just one sentence:

I’m good at ___, I want to keep ___, and I want more time for ___.

You do not have to deny what you are good at.

You only need to become more precise about what you want that strength to mean for your future.