Intellectual Frontiers

Research program

AI Workforce™, Native Alpha™, and Recomposition

Native Alpha™ is the unusual capability of a person or organisation that materially changes an accepted outcome, and that ordinary peers with ordinary tools and AI cannot reproduce. Recomposition is dividing work again so that capability is spent where it matters. The goal is a working operation in which people, machines, software, and outside services each carry the work they can perform well and lawfully.

What division of work preserves scarce human capability, keeps authority clear, and improves the whole outcome rather than one task?

Build the workforce from the outcome

An AI Workforce™ includes people, AI workers, deterministic automation, applications, source systems, data stores, devices, outside services, and governance. It is not a list of agents.

Start with the accepted outcome. Then assign work according to judgment, authority, trust, repeatability, observability, reversibility, physical presence, and the cost of error.

Figure: One workforce, many worker types The accepted outcome is produced by people, AI workers, rules, applications, systems, devices, services, and governance.

Recompose instead of substitute

Replacing one box on an organization chart preserves the assumptions that created the old role. Recomposition rebuilds the operation from work units, decisions, evidence, authority, handoffs, exceptions, and outcomes.

A cheaper task can create more review, delay, and correction elsewhere. Measure the complete operation.

Figure: Recompose around the work Preserving an org chart and swapping workers is contrasted with rebuilding the operation around outcomes, tasks, decisions, authority, evidence, and exceptions.

Protect the work that is truly scarce

A title, credential, seniority, or salary does not prove Native Alpha™. Look for unusual judgment, trust, knowledge, relationships, access, data, rights, workflow position, or execution that changes the result.

For each human activity choose preserve, amplify, encode, or reject. Some technically automatable work should stay human because it creates trust, learning, relationships, or knowledge that compounds.

Figure: Disposition of human capability A claimed differentiated capability is preserved, amplified, encoded, or rejected after its effect on outcomes is tested.

Use two measures together

Credential exposure asks how much licensed authority and liability the outcome consumes. Native Alpha™ density asks how much scarce capacity is spent where unusual capability changes the result.

A sound redesign can lower unnecessary credential exposure while giving differentiated people more time for difficult cases and consequential decisions. Neither measure should be optimized alone.

Figure: Two measures, one redesign Credential exposure and Native Alpha density are examined together so less professional burden does not mean less valuable judgment.

Manage review and exceptions

Execution can become cheap while attention remains scarce. Count review minutes, override rate, disagreement, escalation quality, exception backlog, and cognitive intensity.

A supervisor who nominally owns too many machine workers may own none of them in practice. Review must shrink through evidence, not hope.

Preserve the path to expertise

Routine work can be waste, but it can also teach pattern recognition, ordinary cases, failure modes, and professional judgment. Before removing it, identify what capability it forms and at which career stage.

Replace useful exposure with simulation, deliberate practice, sampled execution, independent decisions before machine advice, error review, and graded authority. Zero Meaningless Work must not become zero apprenticeship.

Figure: The apprenticeship trap Removing repetitive work can remove needless burden or remove the cases and feedback from which future judgment develops.

Move through the brownfield

Most operations cannot switch at once. Observe the current work, replay old cases, run in shadow mode, compare outputs, use packets, grant narrow actions, and retire duplicated work only after the evidence holds.

Count parallel labor, integration, policy change, training, temporary slowdown, anxiety, exceptions, contracts, retirement, and rollback. Time to net positive value matters more than a steady state estimate.

Figure: Brownfield migration Current work is observed and replayed before shadow use, packet preparation, narrow action, and retirement of duplicated work.

Test whether the advantage compounds

A durable recomposition can improve lawful data, decision history, workflow position, trust, distribution, operating know-how, rights, and future products. A one-time labor saving is easier to copy.

Keep rights clear before encoding a person's or organization's unusual capability. A vendor contract or unclear ownership can turn knowledge capture into knowledge loss.

Research notes

  • Capability Formation map

    Identify which repeated work creates future judgment and replace that learning path before automation removes it. This map matters because automating routine work can strip future workers of the cases and feedback they need to become competent. It preserves the learning, not the burden.

  • From human work to AI workforce

    Automation follows understanding. Work becomes explicit, then observable, then repeatable, and only then is it a candidate for AI execution with human exception handling. Skipping a stage does not speed the sequence; it moves the failure later, where it costs more.

  • Native Alpha Capability map

    Find where a person's or organization's unusual capability materially changes an accepted outcome. The map tests whether the difference survives comparison with peers, tools, and AI, so the firm rejects the claim when ordinary peers reproduce the result. Native Alpha™ is a hypothesis, not praise.

  • Native Alpha density review for work

    This note gives a review for judging whether a redesign of work raised Native Alpha™ density and improved the outcome. It is a qualified view, not a universal numerical score, and the redesign is rejected when density rises on paper but outcomes, learning, trust or resilience worsen. Test whether scarce capacity is moving toward work where unusual capability changes or compounds the result.

  • Patient and Caregiver Labor map

    This note gives a before and after map of the unpaid work patients and caregivers do, so it counts in the economic and human result. A workflow improvement that merely exports more work to patients or caregivers than it removes is rejected. Count unpaid calls, forms, portals, travel, record gathering, repeated explanations, and home work around care.

  • Preserve, Amplify, Encode, or Reject

    Choose how to handle a claimed differentiated capability after testing what makes it valuable. The four choices are preserve, amplify, encode, or reject, and they can coexist across parts of one capability. Encoding stops when it weakens trust, learning, control, portability, or the advantage itself.

  • Recomposition, not replacement

    The realistic outcome is not fewer credentialed people. It is credentialed people supervising a distributed set of workers, human and otherwise. The role is recomposed, not deleted, and how many workers one person can oversee is the unknown that decides whether the economics work.

  • Transition and Cutover plan

    Move from the current operation through shadow work and narrow authority while keeping rollback available. The plan stages the move with gates, costs, owners, and fallback, and reports time to net positive value, because steady state savings do not erase transition cost or temporary risk.

  • Workforce Composition map

    Assign work across people, AI, rules, software, systems, devices, services, and governance as one operation. The map gives every Work Unit an owner and every handoff in writing, and it stops when a task saving raises end to end cost, delay, risk, or review burden.

Related

Next