Over time, I started noticing a pattern across the people who reached out to me.
On the surface, they came with different problems.
One did not know what direction to take. Another knew exactly what they wanted but could not break into it. Another was already doing well, but was not progressing or being recognised.
Different situations. Different roles. Different industries.
But the more I listened, the more it became clear that they were not dealing with completely different problems.
The First Conversation
One client was working as a data analyst.
He was doing well. Delivering consistently. No major issues on paper.
But he kept saying the same thing:
"I don't think this is enough. I want to be closer to how the data is actually built."
At first, it sounded like a typical progression conversation. Move from analysis into engineering. Upskill. Take a course.
But when I asked him what frustrated him day-to-day, the answer was clearer.
He was not struggling because he lacked direction. He was frustrated because he was working at the surface of something he wanted to build.
The Second Conversation
Another client had moved from a project role into a delivery management position.
In her previous role, she described herself as average. Capable, but not outstanding.
In her current role, the language changed completely. She was leading, structuring work, driving outcomes. Her performance had shifted significantly.
Nothing about her ability had suddenly changed.
What changed was the nature of the work she was doing. She was no longer executing tasks. She was coordinating and directing them.
The Third Conversation
A third client came in with a different concern.
She enjoyed her work. She was solving problems, thinking critically, contributing meaningfully.
But she felt constrained. She wanted to explore more, take on more complex problems, and expand her capabilities. At the same time, she was frustrated by internal politics, communication gaps, and lack of visibility.
She was not confused about what she wanted. She just felt like her environment was not allowing her to operate fully.
Where It Started to Make Sense
After enough of these conversations, I arrived at a simple way of understanding it, which I call the four levels of work.
The issue was not always lack of clarity, wrong career choice, or lack of ability. It was more structural than that.
People were operating at different levels of work, and frustration appeared when there was a mismatch between how they naturally operated and what their role required.
The Four Levels of Work
Across different industries and roles, work tends to fall into four broad levels.
Execution
This is where work is delivered. Tasks are completed. Outputs are produced. Instructions are followed. There is clarity here, but limited control. Some people thrive in this. Others feel restricted very quickly.
Coordination
This is where work is organised. Timelines are managed. Teams are aligned. Work is structured. The focus shifts from doing the work to making sure the work happens. Some people move into this naturally, even when it is not formally their role.
System
This is where work is built at a deeper level. Systems, processes and underlying structures are designed, improved or fixed. These are the people who ask: "Why does this work like this?" They are not satisfied using something. They want to understand and shape it.
Strategy
This is where direction is set. Decisions are made about priorities, focus and long-term direction. The work becomes less about execution and more about defining what should happen.
But Level Alone Was Not Enough
Knowing someone's natural level of work explained part of the problem, but not all of it.
Two people could both be suited to the same level and still experience completely different forms of friction. That is where the second part of the model came in.
The Patterns I Kept Seeing
Capability
In some cases, the issue was capability. The person was aiming for a higher level of work, but had not yet built the skills, exposure or experience required to operate there consistently. This is not a flaw. It is a gap that needs to be closed.
Access
In other cases, the person had the capability, but not the access. They were in roles or environments that did not allow them to operate at the level they were naturally moving toward. They were thinking at a higher level, but structurally confined to a lower one.
Translation
And then there were people who were already doing the right kind of work, but it was not translating. Their contribution was not visible. Their role was not positioned well. Their value was not being recognised in pay, progression or opportunity. They were not blocked by ability. They were blocked by how their work was being understood.
What About a Complete Career Change?
There are situations where someone genuinely needs to change careers. For example, a care worker who wants to become a developer.
On the surface, that looks like a straightforward decision. They feel something is off, so they decide to move into a completely different field. But this is where most people move too quickly.
They jump from "I feel stuck" to "I need a new career" without understanding what that feeling actually means.
Using this model, the question becomes more precise. What is pulling them toward development?
Is it a genuine pull toward system-level work, building and understanding how things work underneath? Is it frustration from being limited to execution-level work in their current role? Is it driven by income and recognition rather than the nature of the work itself?
Each of these leads to a different conclusion.
If it is a capability gap, then the transition is real, and the focus should be on building the foundation required. If it is an access problem, they may already be thinking at a different level, but their current field does not give them room to express it. If it is a translation problem, the issue may not be the type of work, but how their current work is valued and positioned.
The outcome might still be a career change. But now it is an informed one, not a reactive one.
What This Changed
Once I saw both parts together, things became clearer.
The levels explain where someone naturally operates. The patterns explain what is getting in the way.
That shifted how I thought about career decisions entirely. Instead of asking "what career should I move into?" the question became "what level do I naturally operate at, and what is actually blocking that from translating into progress?"
That question is more precise. And in most cases, it gets much closer to the real issue.
Final Thought
Not all dissatisfaction means you are on the wrong path.
In many cases, it is a signal. A signal that something about your current role, level or environment does not match how you naturally think and operate.
But more importantly, it is a signal that should be understood before it is acted on. You do not switch careers because something feels off. You do not take expensive courses because someone suggested it, or because a trend is gaining attention.
You make informed decisions. Sometimes that leads to a complete career change. But when it does, it is deliberate. You understand why you are making the move, what it requires, and how it aligns with how you actually operate.
That is what ensures that whatever decision you make, your direction remains intact.