06 July 2026

Last time, this series watched L&D reinvent itself as the steward of the capability picture the whole business now runs on. That closed a loop this series has been drawing since April — managers, taxonomies, measurement, content, practice, feedback, the business case, the organisation, the function itself. Read the list back and something stands out: every one of those posts looked at skills-based L&D from above. The one perspective the series has never taken is the one belonging to the person whose skills are actually in the data.

That gap matters more than it looks, because in 2026 the success of a skills-based organisation is not decided in the boardroom that approved it. It is decided at thousands of individual desks, where people quietly choose whether to keep their profile honest, whether to engage with the feedback, and whether to believe that any of this is being done for them rather than to them. This week, the series changes seats.

The View From the Other Side of the Skills Profile

To the organisation, a skills profile is infrastructure — a row in the dataset that feeds planning, staffing, and development decisions. To the employee, it is something far more personal: a standing claim about who they are and what they are worth, held and read by their employer. Whether that claim feels like an asset or an exposure is not a soft question about sentiment. It is the single biggest determinant of whether the data underneath the whole strategy can be trusted.

The mechanism is simple. Skills data is only as good as people’s willingness to be honest in it, and honesty follows consequences. In an organisation where admitting a gap reliably produces support — a course, a stretch assignment, a coaching conversation — people tell the truth. In one where a visible gap quietly costs you the interesting project or the promotion shortlist, people polish. No taxonomy, platform, or dashboard survives a workforce that has learned to polish.

From Being Sent on Courses to Owning a Direction

The old deal was passive: learning was something the organisation did to you. You were enrolled, you completed, you were certified, and the record of it belonged to a system you never looked at. The skills-based deal is different in kind, not just degree. A living profile shows you where you stand; visible gaps show you what is between you and the role you want; and clear training goals turn that distance into something you can actually walk.

The best implementations go a step further and ask the person where they want to go before deciding what they should learn, capturing career aspirations alongside skill and will so that development is negotiated rather than assigned. That single change — from consumer of a curriculum to owner of a direction — is what employees mean when they say skills-based working finally feels different from the annual training calendar it replaced.

The Trust Question Nobody Puts on the Roadmap

There is a harder edge to all this, and pretending otherwise is how programmes lose the room. The same data that powers development can, from the employee’s seat, look like surveillance. Who sees my gaps? Does this number follow me into pay conversations? Was I passed over because of something in a system I have never been shown? These questions rarely appear on an implementation roadmap, and they are the ones the workforce is actually asking.

The organisations that answer them well do it with transparency rather than reassurance. They put plain rules around who sees what and what it is used for, and — crucially — they make the data flow back to the person, not just upward. When evaluations and feedback reach the employee as insight they can act on, and the analytics visibly serve their development rather than only management reporting, measurement starts to read as investment. Opacity, not measurement, is what people distrust.

When the Data Starts Working for the Employee

Get the trust question right and the payoff lands squarely on the employee’s side of the table. Career conversations stop being exercises in advocacy — who noticed you, who will vouch for you — and start being grounded in shared evidence. A development review built on a skills profile is a conversation two people can actually have, because both are looking at the same picture rather than trading impressions.

There is a fairness dividend here that deserves more airtime than it gets. When capability is the currency, the quiet performer in the regional office competes on the same terms as the confident voice in head office. Internal moves stop depending on being in the right meeting. That is not a soft benefit; it is the employee-side answer to why any of this is worth the discomfort of being measured at all.

The Catch: Ownership Cuts Both Ways

The honest catch is that handing employees ownership means asking them to do something with it. A profile only stays true if the person keeps it true; feedback only compounds if it is engaged with; a visible gap only closes if somebody chooses to close it. Organisations that frame skills-based working as pure empowerment set themselves up for the quiet disappointment of profiles that were filled in once, enthusiastically, and never touched again.

Nor can the organisation use ownership as an exit. “It’s your career” is a partnership when it comes with time, support, and honest data — and an abdication when it does not. The test worth applying in 2026 is disarmingly simple: would the person being measured choose this system for themselves if it were optional? Everything this series has covered — the taxonomy, the measurement, the manager conversations, the business case — ultimately exists to make the answer yes. Build it so that it is.