I have noticed that the hardest stretch of work often appears just before I am ready to operate at a higher level.
The calendar fills up. A familiar process stops working. A client asks a question I cannot answer immediately. A decision I have postponed suddenly needs to be made. It can feel as though everything has become more difficult at precisely the wrong moment.
My first instinct used to be to treat that pressure as evidence that something had gone wrong. Now I see it differently. Often, the old way of working has simply reached its limit.
Growth exposes the weak spots
When my responsibilities increase, the cracks in my habits become easier to see. An inbox managed by memory works until the volume doubles. Informal notes are fine until several people need the same information. Keeping every decision in my head feels efficient until I become the bottleneck.
That discomfort is useful. It shows me what can no longer come with me.
I see this regularly with Microsoft 365 Copilot adoption. Someone starts by asking Copilot in Outlook to draft a reply or summarise a long email thread. That is helpful, but the real test arrives later. They discover that the source material is scattered, meeting decisions were never recorded, and important documents live in places nobody else can find.
Copilot has not created the problem. It has made the existing problem visible.
That is the moment where progress can stall. It is tempting to blame the tool, go back to the old approach, or decide that the organisation is not ready. I think the better response is to improve the system around the work. Capture decisions in Teams. Store the current document in SharePoint. Give files useful names. Make ownership clear.
A better result often requires a better foundation.
The next level asks for different behaviour
I cannot solve every new challenge by working longer or pushing harder. Sometimes the answer is a new skill. Sometimes it is a clearer boundary. Sometimes it is trusting another person with work I would normally keep for myself.
This is where the pressure becomes personal. A technical obstacle is often easier than changing a habit that has been rewarded for years. Being the person who knows everything can feel valuable. Becoming the person who builds a system others can use requires a different kind of confidence.
Copilot can assist with that transition, but it cannot make the decision for me. I can use it in Teams to pull together the actions from a meeting, turn rough notes into a first draft in Word, or identify unanswered questions across a discussion. The bigger change is that I must stop treating structure as administration and start treating it as capacity.
Friction is information
I try not to romanticise difficult periods. Not every setback is a sign of an imminent breakthrough. Some problems are simply problems, and they need practical attention.
But I no longer assume that resistance means I should retreat. I ask what the situation is revealing. Which process is too dependent on me? What have I avoided learning? Where am I relying on effort because I have not built a repeatable method?
Those questions turn pressure into information.
The move to a higher level rarely begins with a grand announcement. More often, it begins with an uncomfortable week, an overloaded inbox, and the realisation that yesterday’s habits cannot carry tomorrow’s responsibilities.
I have learned to pay attention when that happens. The strain may not mean I am failing. It may mean the work is asking me to become more deliberate, more structured, and more capable than I was before.
