Capability Intelligence After 50 CapabilityPrints™

What fifty real jobs taught me about the future of work.

When I published the first CapabilityPrint™, I expected to learn about individual jobs.

Fifty CapabilityPrints™ later, I realized I was learning something much bigger.

Across Microsoft, Deloitte, Nike, Shell, American Express, IBM, McDonald's, FedEx, LEGO, Zoom, Caterpillar, Oxfam, Toyota, Canva, L'Oréal, Unilever and dozens of others, one pattern kept repeating:

The work was rarely what the job title suggested.

The capabilities that actually create value were often hidden beneath the surface.

We consistently underestimate modern work

Most organizations still describe roles in terms of activities.

Write code.

Sell products.

Manage projects.

Investigate fraud.

Train staff.

Repair equipment.

But CapabilityPrint™ asks a different question:

What capabilities must this role possess to consistently create value?

The answers are often surprising.

A Package Handler isn't simply moving freight: they're protecting the integrity of a global tracking network.

A McDonald's Crew Member isn't simply serving customers: they're operating within a tightly controlled real-time information system.

A UX Writer isn't simply writing copy: they're reducing cognitive load while balancing safety, regulation, accessibility and product constraints.

Once you look through a capability lens, the work changes completely.

Data literacy isn't a specialist skill

Perhaps the biggest surprise from the first fifty roles has been this:

There isn't a "data job."

Data capabilities appear everywhere.

In logistics.

In hospitality.

In healthcare.

In retail.

In engineering.

In law.

In manufacturing.

In humanitarian aid.

Some collect it.

Some interpret it.

Some govern it.

Some communicate it.

Some make decisions from it.

The combination changes by role, but the pattern never disappears.

Seniority changes the capability mix, not the importance

Operational roles are often dismissed as "execution."

The evidence suggests otherwise.

Operational roles frequently depend on precise data collection, quality assurance, governance and ethical decision making.

Strategic roles don't replace these capabilities.

They add synthesis.

Influence.

Judgment.

Ambiguity management.

The work becomes more complex, but it doesn't become "more data-driven."

It becomes differently data-driven.

Capability belongs to the work

Perhaps the strongest finding after fifty CapabilityPrints is one I've come back to repeatedly.

Capability doesn't begin with people.

It begins with work.

Every role creates its own capability demand.

Only then do we ask whether people can meet it.

This sounds like a subtle distinction.

It isn't.

It's the difference between designing organizations around evidence instead of assumptions.

The invisible pattern

Across fifty organizations and industries, one observation has become impossible to ignore.

The highest-performing roles rarely rely on technical expertise alone.

They combine domain expertise with capabilities such as:

• Making evidence-based decisions.

• Identifying meaningful patterns.

• Ensuring data quality.

• Applying governance consistently.

• Communicating complex information clearly.

These capabilities appear again and again, regardless of industry.

They're becoming part of modern work itself.

The next fifty

The first fifty CapabilityPrints weren't intended to prove a theory.

They were intended to test one.

Instead, they've uncovered something more interesting.

Organizations don't lack talented people.

They often lack visibility into the capabilities their work actually depends on.

That's the gap Capability Intelligence is designed to close.

And we're only halfway to one hundred.

I'm looking forward to seeing what the next fifty reveal.