Insights
Beyond the Skills-Based Organization
Sixty-one percent of organizations now deploy workers based on tasks, skills, and outcomes rather than job titles. Only a third still rely on traditional position-based models. This is the largest shift in organizational design in decades. And it’s genuine progress — organizations are finally acknowledging that people are more than their titles. I wonder whether it goes far enough.
The skills-based organization is better than the job-based organization. Instead of fitting people into rigid roles, it maps what they can actually do. More flexible. More honest. More responsive to the pace of change that AI demands.
Skills are still an execution lens
They describe capacity — what someone is able to do. They don’t describe contribution — what someone notices, questions, connects, or reimagines that no one asked them to. The hospital cleaner who times her work around patient recovery and notices emotional shifts in patients’ families has no skills taxonomy entry for any of that. The engineer who asks the question that prevents a catastrophic product decision isn’t deploying a cataloged capability. The analyst whose background in philosophy helps her see a strategic pattern everyone else missed — that doesn’t appear in a skills profile. Skills can be inventoried. Contribution can only be cultivated.
A three-stage evolution
Perhaps what we’re witnessing is a three-stage evolution:
- A job-based organization asks: What position does this person fill?
- A skills-based organization asks: What capabilities does this person have?
- A contribution-based organization asks: What does this person see, question, and create that no one else does?
The first two are legible. They fit in databases, talent platforms, work charts. They can be sorted, scored, optimized. Contribution resists that. It emerges from the intersection of someone’s experience, curiosity, values, and context. It changes daily. It defies taxonomy. That’s precisely why it’s becoming the most valuable thing in an organization. When AI can perform most cataloged skills, the scarce resource isn’t what people can do. It’s what they uniquely notice, uniquely question, uniquely imagine. No work chart maps it. No talent platform indexes it.
The skills-based organization is a necessary bridge
Eighty-eight percent of leaders say the ability to dynamically orchestrate people and capabilities is critically important. Only seven percent say they’re making real progress. I wonder whether that 81-point gap exists because they’re trying to orchestrate skills — when what they should be doing is creating conditions for contribution. The skills-based organization is a necessary bridge from the job-based organization. But a bridge is not a destination. The destination is an organization that doesn’t just catalog what people can do — but creates the environment for them to contribute what no system would ever think to request.