Before You Build a Skills Strategy, Decide What Problem You're Trying to Solve

It seems to me like every conversation about the future of Talent Management eventually comes back to skills.

Organizations are investing in skills frameworks, skills intelligence, AI-powered skills inference, and skills-based talent practices. HR technology vendors continue to expand their capabilities, and industry analysts regularly describe skills as the foundation of the future workforce.

I agree that skills are important.

But before investing significant time and effort into building a skills strategy, I think there is a more fundamental question to answer.

What business problem are you trying to solve?

Because building a skills strategy isn't the goal.

Improving Talent Management decisions is.

That's an important distinction.

Skills Are a Means, Not an End

Organizations don't create business value by collecting more skills data.

They create business value by making better Talent Management decisions.

Skills become valuable when they help answer questions that are difficult to answer today.

Questions like:

• Who could be ready for a future leadership role?

• What career opportunities should an employee consider next?

• Where do we have capability gaps that learning opportunities aren't addressing?

• How can we better match employees to the work they do today and the work they could do tomorrow?

• Which critical skills should we be developing to support our future business strategy?

If a skills strategy doesn't improve decisions, it's difficult to justify the investment required to build and maintain it.

One Skills Strategy Can Support Many Outcomes

Organizations rarely invest in skills intelligence to solve just one challenge.

A mature skills strategy might support succession planning, career development, internal mobility, learning, workforce planning, and talent acquisition.

That's exactly what makes it valuable.

The challenge is that those business outcomes don't all require the same information or place the same demands on a skills strategy.

An organization focused on internal mobility may prioritize helping employees discover new opportunities.

An organization focused on succession planning may need greater confidence in leadership capabilities and readiness.

Another organization may be focused on understanding future workforce capabilities to support strategic planning.

The underlying skills foundation may be shared.

But the business priorities should shape how that foundation is designed, governed, and used.

Start With the Decisions You Want to Improve

One of the first questions I ask is not:

What skills do we need to collect?

It's:

What decisions are we trying to improve?

That conversation often leads in a very different direction.

Instead of focusing immediately on technology, organizations begin discussing where managers struggle to make decisions, where employees lack visibility into opportunities, where talent processes create unnecessary friction, or where leaders simply don't have enough information to move forward with confidence.

Those conversations usually produce a much clearer picture of what the organization actually needs from a skills strategy.

Technology becomes much easier to evaluate once the desired business outcomes are well understood.

Start Simple, Then Build

Organizations make Talent Management decisions using many different types of information. Skills are only one part of that picture.

Experience, project work, certifications, learning, career interests, performance, and many other attributes all contribute to understanding an employee's capabilities.

But that doesn't mean organizations need to tackle everything at once.

For many organizations, skills are the right place to begin.

A well-designed skills strategy creates a strong foundation that can mature over time as the organization's Talent Management practices evolve.

Starting with one foundational capability often produces better results than trying to solve every Talent Management challenge in a single initiative.

Technology Should Support the Strategy

Today's HR technology platforms offer increasingly sophisticated ways to identify, infer, organize, and use skills.

Those capabilities are exciting, and they continue to improve.

But technology should support a well-defined strategy, not become the strategy itself.

When organizations begin with a clear understanding of the business decisions they want to improve, technology becomes an enabler rather than the starting point.

That's where the greatest value is created.

Looking Ahead

Organizations don't need a skills strategy simply because skills are receiving more attention.

They need one because better Talent Management decisions require better information.

The question isn't whether your organization should invest in skills.

The question is whether you've clearly defined what success looks like before you begin.

Because the strongest skills strategies aren't defined by the skills they collect.

They're defined by the decisions they help organizations make.

What Do You Think?

What business decisions is your organization hoping to improve through a skills strategy?

Are you building your skills strategy around technology capabilities, or around the Talent Management outcomes you want to achieve?

I'd love to hear how your organization is approaching this journey. I read every comment and genuinely enjoy hearing different perspectives.