I have met plenty of capable people who have accidentally built a career around work they cannot stand. They became dependable, then efficient, then indispensable. Because they were good at fixing a particular problem, that problem kept finding its way back to their desk.
Competence is valuable, but it is not always a compass. Sometimes it simply tells other people what they can safely hand to you.
Efficiency can take you in the wrong direction
I see this often in small businesses and MSPs. The owner starts by handling invoicing because nobody else is available. They build a spreadsheet and chase overdue accounts. Before long, they are spending Friday afternoon doing work that drains them, while the work that originally drew them into the business is pushed into spare time.
The usual response is to optimise the task again. Add another formula. Create another rule. Work through the backlog on Saturday morning.
I think that misses the real question. Should I be doing this work at all?
Microsoft 365 Copilot can help expose the pattern. I can ask Copilot in Outlook to summarise the types of requests that consumed my week, or use Copilot in Excel to help me examine where time and effort are accumulating. I am not looking for an artificial verdict about what I should enjoy. I am looking for evidence about where my attention is going.
Once I can see the pattern, I can decide whether to automate it, document it, delegate it or stop doing it.
Invest deeply where the work matters
I do not believe every unpleasant task should be avoided. Every worthwhile role contains repetition and difficult conversations. The distinction is whether those tasks support work I care about or have quietly become the work itself.
When I find an activity that holds my attention, uses my strengths and creates real value for clients, I want to go deeper. I want to practise it and become known for it. That might be designing a security strategy, teaching a technical concept, improving a client conversation or building a better service.
That depth creates options. Strong capability in valuable work can produce the margin needed to bring in someone who is better suited to the tasks I keep postponing. Delegation then becomes more than dumping unwanted work. It becomes an exchange of strengths.
Hand over outcomes, not confusion
Paying someone else does not remove my responsibility to make the work clear. If I delegate a messy process with no context, I have simply transferred frustration.
Before handing over a recurring task, I can capture the process in Word, keep the working material in SharePoint and use Copilot to turn rough notes into clear instructions. I still need to check the detail. It is to give another person the context, boundaries and definition of a good result.
That person may also improve the process in ways I never would, because the work fits how they think. What felt heavy to me may be the kind of order, rhythm or detail they genuinely enjoy.
I am increasingly careful about what I choose to become excellent at. Skill compounds, but so does direction. If I keep sharpening an ability that makes me miserable, I may only earn a more permanent seat in the wrong job.
I would rather build uncommon strength around work I find meaningful, use technology to reduce friction, and create room for other people to contribute where they are strongest. The aim is not to avoid work. It is to make sure my best effort is pointed somewhere worth going.
