DecisionOS — Build · module

Talent

Whether we can staff and supervise what we have decided to do — and whether we still will be able to when the people who can catch the machine's mistakes have moved on.

When you reach for it

During planning, when a date has to be committed. During budget, when an HR business partner asks what roles to open. And when a CHRO or a function head asks the harder question about what happens to the bench.

What it asks you

4 blocks, in this order. Each one exists for a stated reason, and the run tells you that reason as you answer it.

01
The roles this agenda implies
Three to eight roles, named as you name them. Not a skills matrix: a skills inventory across a hundred competencies is an HR artefact that nobody finishes and nobody reads, and the question here is only whether the roles this work implies exist, when they could, and what the lead time is.
02
Four facts per role
Every one of these is a recognition judgement a manager can actually make. None of them is a skill level, because a skill level of 3 out of 5 is not a thing anybody knows and 'could do it now, without training' is.
03
The supervised steps
The steps where a human reviews an agent's output. This is the second axis, and it is the one that matters here: an organisation can be perfectly capable of building a system and structurally incapable of noticing when it is wrong.
04
Supervisory capability, per step
Three questions about who can tell that an output is wrong, how they came to be able to, and whether anybody else is on the way. The third is the one no comparable product asks, and it is the one that decides whether this still works in three years.

The method

How the result is produced

Each role's gap is need minus availability, read as bands rather than as headcount, and every gap resolves to one of four named routes by an ordered rule set evaluated top to bottom, first match wins: redesign, build, contract, hire. The longest lead time across the unresolved gaps sets the agenda's earliest credible start, stated as a duration from the day the decision is taken rather than as a calendar date — derivation carries no clock, and a saved run reopened in a year must not have moved its own date. Supervision is assessed separately from delivery. A step reviewed only by the vendor, or by nobody, is recorded as unsupervised whatever the operating model says. Review load is divided by the supervisor population read at the low end of the band given. Deskilling exposure is reported where three answers coincide on one step: the judgement came from doing the work, that work is now the agent's, and nobody is acquiring it.

What this is not

This produces no headcount-reduction output. There is no field for it, no figure computed from it, and no view expressed on it. Reductions are a consequence of decisions taken elsewhere; this module's only question is whether the work can be staffed and supervised.

This has not assessed any individual. Nothing here is an input to any personnel decision, and the module holds no information about a named person.

This is not a skills assessment or a competency framework. It asks whether roles exist and whether somebody could tell that an output was wrong. It does not measure anybody against anything.

This asserts no hiring benchmark. Every lead time in this report is yours, and there is no market data behind any of it.

Deskilling exposure is a structural inference from three answers, not a prediction. It says a route to future supervisory judgement has not been established. It does not say anybody will lose a skill.

Where it stops

Everything here is what you told us. Nothing was read, inspected, profiled or connected to.

There is no peer comparison behind any statement in this report, and none is implied. We will not show one until there is enough real data to state an n.

This run reflects the answers of whoever completed it. A second respondent answering the same questions frequently disagrees, and that disagreement is usually the finding.

The role list is whatever was entered. Whether a role is missing cannot be established from inside this run, and the reviewer role is the one most often left off.

Lead times are one person's read of one market at one moment. The critical path is shown against the next band up for exactly that reason.

Availability answers the question 'could do this now'. It does not establish that those people have capacity, only that they have capability, and the two are routinely confused when a plan is assembled.

The reviewable-hours threshold is ours and is drafted rather than signed off. Where reviewing genuinely is somebody's job, it is wrong for them by design.

What it connects to

Answers established elsewhere are carried in with their age shown, so a stale answer reads as stale rather than being silently reused.

Reads saved results from

The rest of the Build line

Readiness

Given what we have decided to do, the one thing that stops us — and what becomes the next constraint after we fix it.

Open

Operating Model

Who does what in this workflow, who approves what, what it costs to supervise, and who is accountable when the agent is wrong.

Open

Data Foundation

Whether the data this initiative needs can be reached, is right enough, is permitted, and is fresh enough for the decision it feeds.

Open

Architecture

What has already been decided about how AI runs here, which of those decisions nobody actually made, and which will be expensive to reverse.

Open

See what it costs All twelve modules