Skills Drift: Is Your Learning Forming Anything?

You are probably learning more than ever. The question is whether it is compounding.

Skills drift is not the absence of learning. Often, there is plenty of evidence of learning, but the skills do not connect into a clear professional strength. It looks like this: certifications that do not connect. Courses that cover what is urgent rather than what is strategic. A growing list of tools you have touched, but no clear answer to what capability you are building.

In IT, the pressure to keep learning is constant. Cloud certifications, security frameworks, new platforms, and emerging tooling. The list never ends, and the pressure to stay current never stops.

But staying current is not the same as building a coherent capability stack.

A capability stack is not a list of tools. It is a set of skills: one core skill, several supporting skills, and one strategic skill, that together combine to make you distinctively useful for a specific class of problems and move you closer to the professional identity you are building.

That is the shift from collecting skills to architecting capability.

The question is not “are you learning?” It is: is what you are learning forming anything coherent?

Random learning keeps you busy. Coherent learning earns you the trust to tackle larger problems.

There is a difference between an IT professional who has completed twelve certifications and one who can say: “I am working toward becoming the kind of IT professional organisations trust to design and manage their identity systems at scale.”

The first has volume. The second has direction.

Cloud, cybersecurity, data, service delivery, and platform roles tend to reward coherent capability stacks because the problems are too complex for isolated skills.

Decision-makers can more easily trust people whose learning trajectory is legible, not just people who are constantly staying current.

When your learning is scattered, it becomes harder for the market to understand which problems to trust you with. When your learning is coherent, your capability becomes easier to recognise.

That makes you easier to trust. And easier to invest in.

The difference is not only how much you have learned. It is whether what you have learned points to anything specific.

The skills drift test most IT professionals have never taken

List your last five learning investments. Certifications, courses, labs, structured self-study, or anything you have deliberately spent time learning in the past twelve months.

For each one, write one sentence, not what the course covered, but what specific professional problem it equips you to solve.

Then look at the five sentences together.

If three or more of your learning investments point in the same direction: a specific problem space, a type of environment, or a class of challenge, then your learning may be becoming architectural.

If they point in five different directions, mostly shaped by urgency, trends, recommendations, or whatever your current role demanded at the time, then your skills may be drifting.

This is not a judgment on your discipline. It is a structural observation. The IT environment creates enormous learning pressure, such that without a named direction from layer one, that pressure will fill the space randomly. Identity gives skills somewhere to point. Without it, the learning keeps happening, but the compounding does not.

What a coherent capability stack actually looks like

It has a specific structure.

• One core capability: the thing you are becoming most trusted to do well.
• Two to four supporting capabilities that make the core stronger, broader, or more useful in real environments.
• One strategic capability that expands your future range.

For example, a cloud infrastructure professional might have cloud infrastructure design and operations as the core. Security hardening, cost governance, monitoring, and automation could sit around it as supporting capabilities.

Data platform integration might become a strategic capability because it helps them move beyond infrastructure and become useful in wider platform work.

Every learning decision can then be tested against the stack: does this strengthen something already in it, does it support the direction I am building, or does it pull my attention away from the capability stack I am trying to build?

Many IT professionals have never explicitly built this.

They have accumulated skills in response to projects, team needs, manager requests, job descriptions, incidents, and whatever felt urgent at the time.

Those are all legitimate sources of learning, but by themselves, they do not build career architecture.