Methodologies

Redesign the work, not just the technology.

Turn an AI-enabled workflow into a clear operating agreement between people and agents—who owns the outcome, who may decide, how handovers work and what proves the model is taking hold.

Coral and violet forms converge at a shared decision point within ivory and deep navy architecture, representing human–AI collaboration.
Human-Agent Operating Model PlaybookCollaboration without shadow coordination.

Decision

How must roles, rights and handovers change when AI enters real work?

Output

A role and handover design, decision-rights map, capability plan, incentive changes, and adoption measures.
Method Boundary & Connections

Start here when

An AI capability is entering live work, requiring changes to roles, rights, handovers, incentives, and operational measures.

Does not decide

If the underlying workflow is stable enough to automate (use Agentic Operations Readiness).

Reassess when

Agents gain new capabilities, exception volume overwhelms human supervisors, or business incentives drift away from the workflow's purpose.

Connection to IDAO

Shapes roles, handovers, capabilities, incentives and measures throughout Innovate, Demonstrate, Activate and Operate. Live evidence can return weak assumptions to the responsible stage.
See the IDAO methodology

Connection to Agent Authority

Converts identified handovers into explicit propose, approve, act, intervene and demotion rights. Uses the Agent Authority Model calculation to bound the autonomy of those rights.
See the Agent Authority Model
The Boundary

A rollout installs a tool. An operating model changes how work runs.

Technology rollout
  • Configures access and integrations
  • Explains features and prompts
  • Tracks attendance, licences and usage
  • Supports initial technical adoption
Operating-model change
  • Changes roles, accountabilities and spans
  • Reallocates decision and intervention rights
  • Redesigns handovers, controls and incentives
  • Proves outcomes persist in live operation
Five design moves

Start with one real workflow. Finish with an operable design.

  1. 01

    Trace the live work

    Map the work as it happens: demand, decisions, exceptions, queues, evidence and the people who carry hidden coordination.

    OutputWork and handover baseline
  2. 02

    Redesign roles and handovers

    Decide what people lead, what agents support or execute, and how ownership moves without losing context or accountability.

    OutputRole and handover design
  3. 03

    Set decision rights

    Name who proposes, approves, acts, intervenes and remains accountable for each consequential decision and handover.

    OutputDecision-rights map
  4. 04

    Build operating capability

    Define the judgement, supervision, exception handling, evidence literacy and improvement routines each role needs.

    OutputCapability and enablement plan
  5. 05

    Align incentives and measures

    Remove targets that reward unsafe automation or hidden rework. Measure confident use, intervention, quality and sustained outcomes.

    OutputAdoption measures and incentive changes

Handover Choreography across IDAO

Innovate

Identify roles and constraints.

Demonstrate

Test handover logic safely.

Activate

Install explicit rights pointing to Agent Authority.

Operate

Measure and loop back.

Decision-rights map

Make authority visible at every move.

A role title is not a control. The map records what the person and agent may do at each point, the evidence they need and the condition that moves authority back to a person.

RightPersonAgent
FrameSets the outcome, boundaries and evidence requiredContributes options and operating evidence
RecommendChallenges assumptions and interprets contextProduces traceable analysis or a proposed next action
ApproveRetains authority where exposure requires itWaits at the defined gate and preserves the approval record
ActHandles exceptions and actions reserved for peopleExecutes only within its permitted authority and constraints
IntervenePauses, overrides, escalates or demotes authoritySurfaces thresholds, uncertainty and control breaches

Consequential handovers need an authority ceiling.

For every explicit propose, approve, act, intervene, and demotion right that can materially affect a person, record, system or service, point to the Agent Authority Model calculation to set permitted autonomy.

Set the authority
Capability, not attendance

Prepare people to operate, challenge and improve the system.

The capability plan is role-specific. It combines practice in live scenarios, observed proficiency and support at the moment of work—not a generic course-completion target.

Role practice

Rehearse the normal route, exceptions and fallback with the people who will own them.

Control fluency

Recognise uncertainty, challenge evidence, intervene and document why authority changed.

Handover discipline

Pass context, state and accountability without creating shadow coordination.

Improvement ownership

Use operating evidence to adjust roles, controls and workflow—not only the model.

Adoption and sustained operation

Measure behaviour, control and outcomes—not logins alone.

Activation begins when the redesigned route can run safely in live work. Sustained operation begins when the client team owns the routines, evidence and improvement cycle.

Use

  • Eligible work using the new route
  • Active use by role and team
  • Fallback to the old process

Control

  • Interventions made in time
  • Exceptions resolved by the named owner
  • Authority demotions and control breaches

Capability

  • Observed proficiency in live work
  • Confidence to challenge an agent output
  • Time to independent operation

Outcome

  • Quality and cycle-time movement
  • Rework displaced rather than hidden
  • Value sustained after handover
Connection to IDAO

Design before launch. Learn after it.

Activate uses the role, rights, capability and measure designs to prepare the live workflow, rehearse exceptions and confirm ownership.

Operate uses real performance, interventions and workforce evidence to improve the model and return weak assumptions to the right IDAO stage.

Explore the IDAO lifecycle
Start with live work

Bring one workflow where people and agents must work together.

We will identify the first operating-model decision, the evidence it needs and the right IDAO entry point.

Book a Value Scan