Capability, read from the work itself.

The problem nobody is solving

The hardest thing to see is what people can already do.

Ask a capable professional what they are good at and you will get job titles and adjectives. Not because they are hiding anything — because the moment that would tell them, the one where they say I had not thought of that as something I did, only happens when somebody asks properly and with genuine interest, and almost no one ever does.

Ask an organization what it can do and you get an org chart and an inventory of declared departments and skills. The same gap, one floor up, with a larger budget behind it.

The cost of that is quiet, which is why it survives. Development budget aimed at capability that was already there. People hired from outside for work somebody inside had done twice. Projects not attempted because nobody knew the company could do them. Projects launched that do not move forward as expected. The explanation and possible fixes don’t seem to show anywhere, because the thing that would have made them visible has never existed.

The evidence exists — it is in what people did last quarter and the quarter before. It has simply never been captured consistently, so it could become an instrument that gives the guidance needed to match the intended direction, for professionals and organizations alike.

What Alaya does

Capability is cultivated, not counted.

It is not a stock sitting in a warehouse waiting to be inventoried. It grows through craft — practice done deliberately, repeatedly, under real conditions. Naming it does nothing for it. Scoring it does less.

Capability The living terrain.

Experience Where capability is developed and exercised.

Practice How capability is cultivated and renewed.

Contribution Capability expressed through work that creates value.

Knowledge Preserves and carries forward what is learned.

Curiosity Keeps the field developing.

How Alaya sees capability.

So Alaya reads accounts of work that was actually done, on two axes at once.

Practices are not job titles — a practice is classified by what the act changed. One piece of work usually belongs to several at once, and is allowed to. Dimensions are the same everywhere; what changes with the craft is the practice they show up in.

That intersection is what makes it usable. A score gives nobody anything to do. Knowing that someone's strength shows up in the reasoning and relational aspects of work that changes what is settled — and thins out where the work is about holding something steady — tells a person where to push next and tells an organization what to develop, where to deploy, and where it is exposed.

And every reading stays anchored to the exact sentence in the account that supports it. No sentence, no reading.

The gap, measured

The problem is documented. The market is aimed somewhere else.

None of what follows is our research. It is what the industry reports about itself — and read together it describes an organization that cannot see what it already has, and a person whose capability goes unread inside it.

Sources: Greenhouse, The Hire Standard: Hiring Benchmarks 2026 · Mercer, Skills Snapshot Survey 2025/26 (72 countries) · McKinsey, HR Monitor 2026 · Deloitte, 2026 Human Capital & TA Technology Trends · “The State of Learning and Development” First Annual 2026

The difference is not speed. It is where the instrument points.

Almost all the money and engineering of the last few years went to the front door — matching, screening, sorting, scheduling. That is a real problem and it is being worked on hard. It is also not the one the numbers above describe.

What an organization actually buys to see the people it already has is far older and far thinner: a skills inventory filled in by self-assessment, a competency matrix, a manager's recollection at a talent review. That is the shelf Alaya sits on.

No scores, no rankings, no personality words, no recommendation about a human being. Each one costs something obvious and buys something less obvious: a system that cannot be used against the people feeding it is a system people will tell the truth to. Everything downstream depends on that.

Why there is a market

The flood is the reason, not the obstacle.

Many funded companies claim to help fix this problem, for organizations and professionals both — automating the writing of résumés on one side, automating the parsing of them on the other, and matching skills matrices to job descriptions in between.

What almost none of them touch is the thing being written and parsed. AI is being applied, very fast and very well, to a faulty process and to three unusually thin representations: the résumé, the job description, and the skills matrix. Not one of those was ever a decent description of what a person can do. Automating them in both directions does not make them one — it makes the same thin thing arrive sooner, in greater quantity, from both sides at once.

When a signal becomes free to produce, it stops being a signal. The only thing that recovers is something more expensive to fake. Constructing a whole situation — what it was like before, who objected, what it cost — is not something anyone does by accident.

And the inward problem is larger than the hiring one and much less served. Organizations are building internal skills inventories at a serious rate, and the research behind that trend reports more libraries and more mapped jobs. It does not show the visibility gap closing: mapping to individuals still rests mostly on job roles (73%) and manager-validated self-assessment (71%), and 53% of organizations don’t manage proficiency at all. Cataloging declared skills faster does not tell a company who can actually do the work. It is the résumé problem again, indoors, with a bigger budget behind it.

Meanwhile the question do we already have someone who can do this has become expensive to get wrong. Hiring externally for capability that already exists inside is a cost nobody can see, because the thing that would make it visible has never existed.

The engine

CIE — the Capability Intelligence Engine.

CIE is the engine that allows this to be possible at scale, in the hands of an organization or a professional: it gathers accounts of work that was actually done, then recognizes the capability in them. It has two parts, shown below, and the line between them is the whole design.