RePerspective Labs

The autonomous enterprise

One enterprise.
Connected decisions.

An autonomous enterprise is a system of connected decisions. Explore how people, process and technology turn intent into accountable action—from the first worthwhile outcome to dependable operation.

63 leadership topics3 perspectives6 guided paths

Start with the whole. Explore the connections.

Open a branch as your question develops. Select a topic to see its leadership considerations and related reading.

An operating perspective

The interactive explorer loads here. The topic directory below is available for reading.

Select a topic label for details. Use + / − to open or close its branch. The branches are entry points; authority, evidence and responsibility connect across the whole operation.

Leadership topic directory

Read the questions, decisions and considerations below. Topic records are maintained in the RePerspective Labs CMS.

acceptance-evidence

acceptance-evidence

Acceptance evidence

handoff-readiness

process

1

What would justify accepting the handoff?

Acceptance is an operating decision supported by evidence. Define the evidence required for the next step without assuming every exception can be anticipated.

What leaders decide

Which facts and decisions justify acceptance, and who may accept an incomplete case?

Leadership considerations

  • Specify the minimum evidence. Identify the facts and decisions required for this particular transfer.
  • Preserve unresolved questions. Let the receiver challenge, return or explicitly accept an exception.
  • Learn from rejected handoffs. Use recurring omissions to improve the working agreement and its supporting context.

What to watch

Missing facts discovered after acceptance, recurring omissions and growing review effort.

Illustrative invoice example

Finance can identify the invoice discrepancy, verify receipt evidence and see the authorized resolution before accepting the case.

bp-operating

Connected Operating Blueprint dimension

Work & decisions

Explore this Operating Blueprint dimension

Reviewed on

October 9, 2026

Content edition

1.0

accountability

accountability

Accountability

people

people

1

Who owns the outcome when work crosses organizational boundaries?

Assign responsibility for the complete business capability and for its supporting knowledge, systems and controls. Give owners the authority and resources to act.

What leaders decide

Who accepts the end-to-end outcome and can resolve dependencies that cross organizational boundaries?

Leadership considerations

  • Name the outcome owner. Identify who accepts the service, commits resources and answers for its performance.
  • Allocate supporting responsibilities. Clarify who maintains sources, resolves exceptions, monitors operation and approves changes.
  • Make escalation real. Specify who decides when objectives conflict or a dependency cannot be met.

What to watch

A successful pilot without an operating owner, unfunded shared dependencies or alerts that no one is responsible for resolving.

Illustrative invoice example

Finance owns the invoice exception outcome. Procurement owns order clarification; Receiving owns confirmation of delivery.

bp-operating

Connected Operating Blueprint dimension

Work & decisions

Explore this Operating Blueprint dimension

Reviewed on

October 9, 2026

Content edition

1.0

Accountability

action-limits

action-limits

Action limits

task-scope

technology

1

Which limits must hold while the agent works?

Turn the assignment into explicit limits at the point of action. A system should not rely on the model alone to decide whether it has permission.

What leaders decide

What action, access, time and spending boundaries must hold throughout this task?

Leadership considerations

  • Constrain the action. Allow only the tools, records and operations needed for this task.
  • Limit the attempt. Set appropriate retry, elapsed-time, step and spending boundaries.
  • Route exceptions. Require an authorized decision when the next action would exceed the permitted scope.

What to watch

Repeated attempts, unexpected tool calls, boundary denials and activity with no useful progress.

Illustrative invoice example

After unsuccessful evidence retrieval, stop and route the case to its owner. Do not widen access to find another route.

bp-governance

Connected Operating Blueprint dimension

Authority & controls

Explore this Operating Blueprint dimension

Reviewed on

October 9, 2026

Content edition

1.0

adoption-incentives

adoption-incentives

Adoption and incentives

capability

people

3

Why would people choose the new way of working?

Adoption reflects the practical experience of the work. Examine whether the new route reduces friction, supports accountability and fits the incentives people are measured against.

What leaders decide

What must change in the workflow, support or incentives for the intended behavior to make sense?

Leadership considerations

  • Observe actual work. Look at duplicate effort, bypasses and the reasons people return to the old route.
  • Align the measures. Avoid rewarding local activity that undermines the end-to-end outcome.
  • Remove persistent friction. Adjust the process and support using evidence from the people doing the work.

What to watch

High login counts alongside continued manual processes, hidden checking and avoidance of the shared case record.

Illustrative invoice example

If staff must maintain both the new invoice case and a separate spreadsheet, resolve that duplication before interpreting low adoption as resistance.

bp-workforce

Connected Operating Blueprint dimension

People & capability

Explore this Operating Blueprint dimension

resistance change adoption workarounds

Reviewed on

October 9, 2026

Content edition

1.0

agents

agents

Agents & orchestration

technology

technology

2

Where does choosing the next step require contextual intelligence?

Use the simplest mechanism that can perform the work dependably. Agentic coordination is useful where the next step depends on evolving context and needs explicit limits.

What leaders decide

Where does flexible choice add value, and where is a controlled workflow sufficient?

Leadership considerations

  • Choose the mechanism. Use a fixed sequence where it is sufficient. Introduce agent choices where that flexibility has a clear purpose.
  • Keep state and handoffs explicit. Record what is known, what has been done, who acts next and when the work is complete.
  • Bound execution. Set tool permissions, step and spending limits, and conditions for stopping or escalating.

What to watch

Repeated retries, unnecessary tool use, unclear completion, lost context or actions outside the assigned scope.

Illustrative invoice example

An agent may identify missing invoice evidence and draft a request. A controlled workflow routes it to the responsible person.

bp-intelligence

Connected Operating Blueprint dimension

Knowledge & context

Explore this Operating Blueprint dimension

Reviewed on

October 9, 2026

Content edition

1.0

Agents & orchestration

approval-thresholds

approval-thresholds

Approval thresholds

decision-rights

people

1

When must a person review the proposed action?

Set approval conditions according to the consequence, uncertainty and reversibility of the action. Review the conditions as evidence and the operating context change.

What leaders decide

Which consequences or uncertainties require approval before action, and how is that condition enforced?

Leadership considerations

  • Use meaningful triggers. Consider changes in commitments, exceptions and insufficient evidence.
  • Make the rule enforceable. Place the approval check before the action and preserve the decision record.
  • Keep review workable. Account for reviewer capacity, escalation and the ability to stop.

What to watch

Rubber-stamping, delays caused by overloaded reviewers and action before an approval is recorded.

Illustrative invoice example

A payment-related exception reaches an authorized reviewer with evidence and unresolved questions before the consequential action.

bp-governance

Connected Operating Blueprint dimension

Authority & controls

Explore this Operating Blueprint dimension

Reviewed on

October 9, 2026

Content edition

1.0

authority

authority

Authority & boundaries

shared

0

How do we keep agents within their intended task and authority?

Combine clear intent, enforced permissions, observable behavior and a way to intervene. These controls reduce and expose deviations; they do not guarantee that an agent will never go off course.

What leaders decide

Which actions are permitted, which require approval, and who can restrict or stop the operation?

Leadership considerations

  • State the permitted task. Define the desired outcome, exclusions, completion criteria and decisions that remain human.
  • Enforce action limits. Restrict tools and system permissions. Validate consequential actions and require the appropriate approval.
  • Treat incoming content carefully. Documents and tool results are evidence to assess, not permission to change the assigned task or controls.
  • Test, stop and recover. Evaluate adverse cases, set step and spending limits, and provide a usable cancellation and recovery path.

What to watch

Unexpected tool calls, attempts to exceed permissions, repeated retries, unsupported conclusions or actions inconsistent with the stated outcome.

Illustrative invoice example

An invoice agent may gather evidence and draft a request. It cannot approve a payment, change bank details or expand its own access. Boundary attempts are recorded for review.

bp-governance

Connected Operating Blueprint dimension

Authority & controls

Explore this Operating Blueprint dimension

guardrails governance agent drift keep agents on task kill switch stop agent

Reviewed on

October 9, 2026

Content edition

1.0

Authority & boundaries

overview

overview

Autonomous Enterprise

overview

0

How do the parts work together?

An autonomous enterprise connects business intent, knowledge, decisions and action across organizational boundaries. People retain accountability; evidence determines what the operation may do and how it should change.

What leaders decide

Which business capability should change, what value should improve, and who will own its authority and performance?

Leadership considerations

  • Start with one outcome. Follow a business capability across the teams and systems needed to deliver it.
  • Connect the operating choices. Explore People, Process and Technology, then examine authority and monitoring across all three.
  • Apply the perspective. Use the Operating Blueprint for design choices and the Autonomy Map for a situation you want to explore.

What to watch

A local efficiency gain may create more checking, delay or risk elsewhere. Follow the whole outcome.

Illustrative invoice example

An invoice exception spans Procurement, Receiving and Finance. Its outcome depends on shared facts, coordinated work and clear authority.

bp-operating

Connected Operating Blueprint dimension

Work & decisions

Explore this Operating Blueprint dimension

Reviewed on

October 9, 2026

Content edition

1.0

Autonomous Enterprise

Autonomy is delegated authority inside an accountable operating system.

capability

capability

Capability & adoption

people

people

3

What must people be able to do as their work changes?

Develop the skills, roles and working routines needed for the intended operating model. Adoption depends on whether the new way makes the work more dependable and useful.

What leaders decide

What must each role learn, own and stop doing as the operating model changes?

Leadership considerations

  • Redesign the role. Clarify what people will judge, own and improve as routine work changes.
  • Practice real decisions. Use representative cases to build source evaluation, challenge and escalation skills.
  • Learn from actual use. Examine workarounds, friction and workload, then adapt the process and support.

What to watch

Parallel manual work, avoidance of the new process, poor confidence in the evidence and increased review effort.

Illustrative invoice example

Train reviewers to identify missing invoice evidence and explain an override. Use recurring difficulties to improve both the tool and the work.

bp-workforce

Connected Operating Blueprint dimension

People & capability

Explore this Operating Blueprint dimension

Reviewed on

October 9, 2026

Content edition

1.0

Capability & adoption

resilience-limits

resilience-limits

Capacity and limits

platform-reliability

technology

2

What happens when demand or repeated attempts exceed the planned capacity?

Bound resource use and design how the route behaves under pressure. Include technical capacity, dependency limits and the human workload created by retries or escalations.

What leaders decide

Which limits trigger waiting, reduced scope, fallback or intervention?

Leadership considerations

  • Bound consumption. Set appropriate execution, retry, time and spending limits for the task.
  • Plan degraded operation. Identify which work can wait and which commitments need an alternative route.
  • Observe the queue. Track accumulating work and the capacity of the people expected to intervene.

What to watch

Growing backlogs, repeated retries, sudden cost increases and more review requests than people can handle.

Illustrative invoice example

A temporary source outage pauses evidence collection after a bounded number of attempts instead of consuming resources indefinitely.

bp-learning

Connected Operating Blueprint dimension

Evidence & adaptation

Explore this Operating Blueprint dimension

rate limits scalability retry budget runaway cost

Reviewed on

October 9, 2026

Content edition

1.0

escalation-capacity

escalation-capacity

Capacity to intervene

judgment

people

3

Will a qualified person actually be available when the system needs help?

An escalation route is an operating commitment. It needs coverage, response expectations and a way to handle demand beyond the available capacity.

What leaders decide

Who responds, within what time, and what happens while the operation waits?

Leadership considerations

  • Plan for real demand. Include normal volume, peaks and correlated failures that create many exceptions at once.
  • Define waiting behavior. Specify whether work pauses, continues in a narrower mode or moves to an approved fallback.
  • Provide cover. Give backup roles the necessary access, context and authority.

What to watch

Unanswered requests, old exception queues and systems proceeding because a person did not respond.

Illustrative invoice example

If the authorized Finance reviewer is unavailable, the invoice case waits or follows an agreed backup route; silence does not authorize payment.

bp-workforce

Connected Operating Blueprint dimension

People & capability

Explore this Operating Blueprint dimension

on call human takeover approval queue

Reviewed on

October 9, 2026

Content edition

1.0

adverse-case-testing

adverse-case-testing

Challenge the boundaries

release-readiness

process

2

What happens when the operation receives misleading content or encounters a failure?

Challenge the permitted route deliberately. Observe whether inappropriate requests are refused, useful evidence is retained and a responsible owner can contain the resulting problem.

What leaders decide

Which boundary and failure scenarios must be demonstrated before this scope is allowed?

Leadership considerations

  • Test the action boundary. Attempt actions outside the assigned scope and approved permissions.
  • Test uncertainty and failure. Include conflicting evidence, unavailable tools and partially completed actions.
  • Check the response. Verify stopping, escalation, recorded state and the route back to an accepted operation.

What to watch

A control that works only on the expected path, repeated attempts after denial and failures that leave no usable case history.

Illustrative invoice example

A supplier attachment asks the agent to bypass approval. The test checks that the request cannot authorize a payment action.

bp-governance

Connected Operating Blueprint dimension

Authority & controls

Explore this Operating Blueprint dimension

adversarial testing red teaming prompt injection test

Reviewed on

October 9, 2026

Content edition

1.0

governed-change

governed-change

Change and improvement

readiness

process

4

How does operating evidence lead to a reviewed change?

Connect signals and feedback to a deliberate decision about the work. Changes to models, sources, instructions, tools or authority can alter the behavior of the whole route.

What leaders decide

Who approves a material change, what must be retested, and how can the previous mode be restored?

Leadership considerations

  • State the proposed improvement. Connect the change to a recurring problem and the expected effect.
  • Review the affected commitments. Consider outcomes, permissions, review burden and downstream dependencies.
  • Release with evidence. Retain versions, relevant evaluation and a practical rollback or recovery plan.

What to watch

Silent prompt or source changes, repeated fixes without outcome evidence and growing differences between documented and actual behavior.

Illustrative invoice example

Before changing the invoice agent’s retrieval instructions, test the affected case types and review any new escalation or permission behavior.

bp-learning

Connected Operating Blueprint dimension

Evidence & adaptation

Explore this Operating Blueprint dimension

change control continuous improvement versioning drift

Reviewed on

October 9, 2026

Content edition

1.0

workforce-transition

workforce-transition

Changing roles

capability

people

4

How will responsibilities and capacity change as routine work shifts?

Plan the transition from current work to the intended roles. Account for the judgment, stewardship, support and improvement effort that remains or is newly created.

What leaders decide

What work will each role retain, gain or stop doing, and how will released capacity be used?

Leadership considerations

  • Describe the future work. Name the decisions, exceptions and improvements people will own.
  • Fund the transition. Allow time for learning, dual running where necessary and knowledge transfer.
  • Validate the capacity claim. Measure recurring oversight and support before committing the expected capacity elsewhere.

What to watch

Role ambiguity, hidden overtime, permanent dual running and savings assumptions that ignore retained work.

Illustrative invoice example

Finance capacity shifts from gathering invoice facts toward resolving difficult exceptions and improving the causes of rework.

bp-workforce

Connected Operating Blueprint dimension

People & capability

Explore this Operating Blueprint dimension

workforce redeployment capacity release

Reviewed on

October 9, 2026

Content edition

1.0

completion-checks

completion-checks

Completion checks

task-scope

technology

2

What evidence shows that this task has actually finished?

Completion should describe an accepted operating result. A fluent response or a successful tool call may leave the business task unresolved.

What leaders decide

What observable result establishes completion, and who may accept it?

Leadership considerations

  • Define an observable result. Use a case state, accepted handoff or verified record as appropriate.
  • Keep unresolved facts visible. Distinguish completion from a blocked or partially completed task.

What to watch

Tasks marked complete despite unresolved evidence, failed writes or a missing acceptance decision.

Illustrative invoice example

Finding a receipt document is one step. Finance still needs an accepted case with the relevant discrepancy resolved.

bp-operating

Connected Operating Blueprint dimension

Work & decisions

Explore this Operating Blueprint dimension

Reviewed on

October 9, 2026

Content edition

1.0

context-assembly

context-assembly

Context at the decision

knowledge

technology

2

Will the decision receive the right facts at the right moment?

Assemble context for the particular task and its permitted scope. Include the current work state, relevant policy and unresolved facts so that a decision can be explained and challenged.

What leaders decide

What context is necessary for this decision, and what should be excluded?

Leadership considerations

  • Start from the decision. Identify the evidence and history that materially change the next action.
  • Preserve source meaning. Keep provenance, currency and relevant uncertainty with the retrieved information.
  • Limit unnecessary context. Avoid introducing unrelated or unauthorized records into the case.

What to watch

Relevant evidence omitted, large context bundles with unclear relevance and decisions based on an old work state.

Illustrative invoice example

The invoice reviewer receives the current purchase order, receipt evidence and open discrepancy, with source references.

bp-intelligence

Connected Operating Blueprint dimension

Knowledge & context

Explore this Operating Blueprint dimension

RAG retrieval context engineering

Reviewed on

October 9, 2026

Content edition

1.0

business-continuity

business-continuity

Continuity of service

recovery

process

3

How will essential work continue if the AI-enabled route is unavailable?

Specify the service that must be sustained and the mode that can sustain it. A fallback needs tested procedures, accessible information and people with enough capacity to use it.

What leaders decide

Which service commitments must hold during disruption, and what fallback will meet them?

Leadership considerations

  • Define the minimum service. Distinguish urgent work from cases that can safely wait.
  • Make fallback usable. Maintain the context, access and skills required to operate the alternative route.
  • Practice the transition. Test both entry into fallback and reconciliation when normal operation returns.

What to watch

Fallback instructions that have not been exercised, unavailable reviewers and backlogs that exceed the assumed recovery capacity.

Illustrative invoice example

During an invoice platform outage, authorized staff use an agreed queue and reconcile case state before automated handling resumes.

bp-learning

Connected Operating Blueprint dimension

Evidence & adaptation

Explore this Operating Blueprint dimension

business continuity disaster recovery fallback

Reviewed on

October 9, 2026

Content edition

1.0

tool-contracts

tool-contracts

Controlled tool use

systems

technology

2

What guarantees must the interface enforce before an action is accepted?

Define a clear contract for each tool: permitted inputs, authorization, state changes and failure behavior. Validate consequential actions at the interface where they take effect.

What leaders decide

Which checks must succeed before this tool may change the enterprise’s state?

Leadership considerations

  • Specify the action. Make the permitted operation and its input requirements precise.
  • Check authorization at execution. Validate the current actor, target, parameters and required approval.
  • Return usable results. Report the actual outcome and enough failure context for safe follow-up.

What to watch

Broad tools, ambiguous success responses and actions accepted on the basis of a model’s statement that approval exists.

Illustrative invoice example

A case-update tool validates the record and allowed fields. It cannot silently convert a draft request into a payment instruction.

bp-governance

Connected Operating Blueprint dimension

Authority & controls

Explore this Operating Blueprint dimension

MCP API tools function calling authorization

Reviewed on

October 9, 2026

Content edition

1.0

multi-agent-coordination

multi-agent-coordination

Coordinating agents

agents

technology

5

What justifies distributing the work across several agents?

Additional agents create additional boundaries, handoffs and failure conditions. Use distinct roles when they clarify responsibility or capability, and make coordination and final acceptance explicit.

What leaders decide

Which responsibilities should be separated, and who or what controls the combined result?

Leadership considerations

  • Give each role a bounded task. Specify its inputs, outputs, permissions and completion condition.
  • Preserve the shared case. Maintain the facts, work state and responsibility needed across handoffs.
  • Control disagreement and loops. Define how conflicts, repeated attempts and incomplete results reach an owner.

What to watch

Agents repeating or contradicting each other, authority inherited informally and a final result with no clear acceptance check.

Illustrative invoice example

Separate evidence gathering from case preparation only if the distinction improves the invoice route and preserves clear ownership.

bp-intelligence

Connected Operating Blueprint dimension

Knowledge & context

Explore this Operating Blueprint dimension

multi agent agent collaboration orchestration

Reviewed on

October 9, 2026

Content edition

1.0

coordination-checkpoints

coordination-checkpoints

Coordination checkpoints

agents

technology

2

Where should coordinated work pause, verify or hand over?

Make consequential transitions explicit so people and systems can tell what has happened, what remains uncertain and who owns the next step.

What leaders decide

Which transitions need a check before the next person or system proceeds?

Leadership considerations

  • Record the transition. Carry current case state, relevant evidence and unresolved questions.
  • Verify before proceeding. Check the required authorization and readiness at material transitions.

What to watch

Duplicated work, lost responsibility or a downstream action based on an assumed handoff.

Illustrative invoice example

Before the invoice case moves to Finance, verify that the receiving team has confirmed the relevant facts.

bp-operating

Connected Operating Blueprint dimension

Work & decisions

Explore this Operating Blueprint dimension

Reviewed on

October 9, 2026

Content edition

1.0

unit-economics

unit-economics

Cost per accepted outcome

value

process

3

Does the result justify the full cost of producing it?

Use the cost of an accepted outcome to connect technology activity with business value. Count recurring human review, correction, oversight and support alongside the technical running cost.

What leaders decide

What cost, quality and service conditions must hold for the capability to remain worthwhile?

Leadership considerations

  • Use a meaningful denominator. Count accepted results; include the cost of failed and repeated attempts in the total.
  • Include the whole operation. Account for integration, review, monitoring, support and recovery effort.
  • Explain the benefit. Distinguish cash savings, avoided cost, released capacity and improved service.

What to watch

Falling model cost alongside rising review burden, expensive retries and claimed savings that have no agreed use.

Illustrative invoice example

Compare full recurring handling cost per accepted invoice resolution, including the cases returned for more evidence.

bp-value

Connected Operating Blueprint dimension

Value & outcomes

Explore this Operating Blueprint dimension

ROI cost economics token costs FinOps

Reviewed on

October 9, 2026

Content edition

1.0

decision-rights

decision-rights

Decision rights

judgment

people

1

Who may decide when the work involves a consequential trade-off?

Connect each retained human decision to an authorized role, usable evidence and a practical escalation route.

What leaders decide

Which role may approve, decline or escalate each consequential decision?

Leadership considerations

  • Name the decision owner. Make authority explicit for approvals, exceptions and conflicting priorities.
  • Support the decision. Provide evidence, time and the ability to decline or pause the proposed action.

What to watch

Approval requests sent to unavailable people, ambiguous ownership and escalation by informal influence.

Illustrative invoice example

An authorized Finance role decides whether an invoice exception can proceed; the agent assembles the case.

bp-governance

Connected Operating Blueprint dimension

Authority & controls

Explore this Operating Blueprint dimension

Reviewed on

October 9, 2026

Content edition

1.0

progressive-autonomy

progressive-autonomy

Delegated authority

readiness

process

3

How much should this route be allowed to do on its own?

Choose authority for a specific task and consequence. Preparation, reviewed action and bounded execution are different operating choices; a capable design may deliberately retain human decisions.

What leaders decide

What authority is justified for this scope, and what evidence would expand, narrow or withdraw it?

Leadership considerations

  • Describe the permitted mode. Distinguish gathering information, drafting, proposing, executing and making commitments.
  • Match the evidence to consequence. Review capability, recoverability and oversight before changing authority.
  • Keep withdrawal practical. Ensure that the route can pause or return to a narrower mode without losing the work.

What to watch

Authority increasing because a pilot was popular, or permissions persisting after the supporting evidence changes.

Illustrative invoice example

Begin with invoice case drafts for review. Consider controlled record updates separately from decisions that authorize payment.

bp-governance

Connected Operating Blueprint dimension

Authority & controls

Explore this Operating Blueprint dimension

autonomy levels crawl walk run fly delegation

Reviewed on

October 9, 2026

Content edition

1.0

state-consistency

state-consistency

Dependable state changes

systems

technology

3

Can the operation tell which changes actually completed?

Make consequential writes traceable and reconcile uncertain results. Retries and partial failures should not create duplicate actions or contradictory records.

What leaders decide

How will the route verify completion, avoid duplicate effects and reconcile partial work?

Leadership considerations

  • Define the accepted transition. State what may change and which conditions must hold before and after it.
  • Handle retries deliberately. Identify repeated requests and prevent unintended duplicate effects.
  • Reconcile uncertainty. Check recorded state before deciding whether to retry, repair or escalate.

What to watch

Duplicate records, successful responses with missing updates and partially completed work treated as a clean failure.

Illustrative invoice example

After a timeout, verify whether the invoice case update was stored before submitting the same action again.

bp-operating

Connected Operating Blueprint dimension

Work & decisions

Explore this Operating Blueprint dimension

idempotency retries transactions state management

Reviewed on

October 9, 2026

Content edition

1.0

interoperability

interoperability

Enterprise integration

systems

technology

4

How will the capability work with the systems the enterprise already depends on?

Connect the operating design to supported interfaces and authoritative records. Avoid creating a parallel system of work that requires people to reconcile the same case repeatedly.

What leaders decide

Which systems remain authoritative, and which interfaces are needed to support the intended flow?

Leadership considerations

  • Name the record of authority. Make it clear where each fact, decision and case state belongs.
  • Understand interface limits. Account for latency, availability, access and supported operations.
  • Preserve the operating context. Carry the identifiers and evidence needed across system boundaries.

What to watch

Shadow trackers, fragile interface assumptions and multiple records that disagree about ownership or completion.

Illustrative invoice example

The invoice route connects the purchase order and receipt records to the existing case system instead of inventing another tracker.

bp-intelligence

Connected Operating Blueprint dimension

Knowledge & context

Explore this Operating Blueprint dimension

integration legacy systems APIs system of record

Reviewed on

October 9, 2026

Content edition

1.0

recovery

recovery

Exceptions & recovery

process

process

3

How does the operation continue when the system cannot proceed?

An exception needs a responsible owner, an understood fallback and evidence for safe resumption. Recovery is part of the operating design.

What leaders decide

What pauses the route, who takes over, and what evidence permits it to resume?

Leadership considerations

  • Name the stop conditions. Define which uncertainty, failure or boundary breach requires a pause or escalation.
  • Make takeover workable. Provide people with case history, current state and the authority and capacity to intervene.
  • Control the restart. Reconcile partial actions and verify that the conditions for resuming have been met.

What to watch

Unowned exception queues, repeated automated retries, incomplete recovery records and fallback routes that depend on unavailable people.

Illustrative invoice example

If the finance interface fails after a case update, check the recorded state before retrying. Avoid producing duplicate records or actions.

bp-learning

Connected Operating Blueprint dimension

Evidence & adaptation

Explore this Operating Blueprint dimension

Reviewed on

October 9, 2026

Content edition

1.0

Exceptions & recovery

pilot-to-operation

pilot-to-operation

From pilot to operation

readiness

process

2

Can the business run this capability after the project team steps away?

A durable operation needs an accepted owner, funding, support, maintained knowledge and a review rhythm. Establish these responsibilities as part of the release commitment.

What leaders decide

Who accepts the service, and which operating responsibilities must be in place before handover?

Leadership considerations

  • Agree the service commitment. Define scope, expected performance, support and escalation.
  • Transfer operational knowledge. Provide runbooks, known limitations, case history and dependency ownership.
  • Fund continuing work. Include source maintenance, review, support, measurement and improvement.

What to watch

Project specialists becoming permanent informal support, unowned knowledge changes and unfunded review or recovery work.

Illustrative invoice example

Finance accepts the invoice service with named source owners, exception coverage and a regular review of cost and quality.

bp-operating

Connected Operating Blueprint dimension

Work & decisions

Explore this Operating Blueprint dimension

production scale handover operating model

Reviewed on

October 9, 2026

Content edition

1.0

handoff-readiness

handoff-readiness

Handoff readiness

work

process

1

Can the receiving team proceed without reconstructing the case?

A usable handoff transfers the context needed for the next decision, including what is unresolved. Readiness should be agreed with the people receiving the work.

What leaders decide

What must the receiving team have before accepting the work?

Leadership considerations

  • Agree the acceptance condition. Define what the receiver needs and who can accept an exception.
  • Carry the context. Include the current state, material evidence, dependencies and open decisions.
  • Confirm the transfer. Make acceptance and ownership visible in the existing system of work.

What to watch

Repeated clarification, rejected handoffs and records marked done before another owner can proceed.

Illustrative invoice example

Finance receives the invoice, the discrepancy, the receipt evidence and the named owner of any unresolved question.

bp-operating

Connected Operating Blueprint dimension

Work & decisions

Explore this Operating Blueprint dimension

Reviewed on

October 9, 2026

Content edition

1.0

judgment

judgment

Human judgment

people

people

2

Which decisions require a person, and what makes that review effective?

Place human judgment where consequence, ambiguity or trade-offs require it. A review step needs usable evidence, time, expertise and real decision authority.

What leaders decide

Which decisions stay with people, and what must they receive to make those decisions well?

Leadership considerations

  • Define retained decisions. Name the commitments, exceptions and changes that require authorized human approval.
  • Support a challenge. Show source evidence, uncertainty and meaningful alternatives alongside recommendations.
  • Design review capacity. Plan for workload, escalation timing and the ability to pause or reject the proposed action.

What to watch

Rubber-stamping, unexplained overrides, review overload and recommendations presented without their evidence or limitations.

Illustrative invoice example

An authorized Finance reviewer decides the invoice exception. The agent provides a source-linked case and preserves unresolved receipt questions.

bp-workforce

Connected Operating Blueprint dimension

People & capability

Explore this Operating Blueprint dimension

Reviewed on

October 9, 2026

Content edition

1.0

Human judgment

identity-access

identity-access

Identity and permissions

systems

technology

1

Can the enterprise tell who or what is acting, and with what authority?

Tie access to an identifiable actor and a defined task. Separate the ability to read, draft, change records and authorize commitments, with a practical way to revoke access.

What leaders decide

Which identity receives which permissions, for which scope and duration?

Leadership considerations

  • Identify the actor. Distinguish the service or agent identity from the people approving its actions.
  • Scope the permission. Grant only the records and operations required for the assigned work.
  • Review and revoke. Change access when responsibilities, scope or confidence in the route changes.

What to watch

Shared credentials, permissions copied from broad human roles and access that survives the task or service that justified it.

Illustrative invoice example

The invoice assistant can read permitted case records and draft updates, while payment authority remains separately controlled.

bp-governance

Connected Operating Blueprint dimension

Authority & controls

Explore this Operating Blueprint dimension

IAM RBAC ABAC least privilege credentials

Reviewed on

October 9, 2026

Content edition

1.0

investment-gates

investment-gates

Investment decisions

value

process

4

What evidence justifies the next commitment?

Make investment decisions in increments that match the uncertainty. Agree the evidence for choosing Expand, Continue, Narrow, Redesign or Stop before a promising trial creates pressure to scale.

What leaders decide

What is the next bounded commitment, and which results would change that decision?

Leadership considerations

  • Bound the next step. Specify scope, resources, duration and the operating responsibilities accepted.
  • Agree the evidence. Define value, quality, authority and readiness conditions together.
  • Keep stopping possible. Preserve a practical exit or narrower operating mode when assumptions fail.

What to watch

Expansion justified by sunk cost, enthusiastic demonstrations or targets that ignore the operating burden.

Illustrative invoice example

Approve a limited invoice trial, then review accepted results and full effort before increasing volume or authority.

bp-value

Connected Operating Blueprint dimension

Value & outcomes

Explore this Operating Blueprint dimension

funding stage gate go no go

Reviewed on

October 9, 2026

Content edition

1.0

knowledge

knowledge

Knowledge & context

technology

technology

1

What must be known before a decision or action is justified?

A usable context connects facts, policy, meaning and the current state of the work. It also makes missing or conflicting information visible.

What leaders decide

Which sources may support this decision, who keeps them dependable, and when is the evidence insufficient?

Leadership considerations

  • Establish the source. Identify where each material fact comes from, who owns it and how current it must be.
  • Carry decision context. Preserve case history, dependencies and relevant rationale as work changes hands.
  • Handle uncertainty. Define what to do when sources are missing, stale or contradictory.

What to watch

Unsupported assertions, outdated policy, incomplete records and contradictory evidence.

Illustrative invoice example

An invoice match is insufficient if the receipt record is unreliable. Ask the receiving team to verify delivery before the payment decision.

bp-intelligence

Connected Operating Blueprint dimension

Knowledge & context

Explore this Operating Blueprint dimension

Reviewed on

October 9, 2026

Content edition

1.0

Knowledge & context

knowledge-stewardship

knowledge-stewardship

Knowledge stewardship

knowledge

technology

3

Who keeps operational knowledge dependable as the business changes?

Knowledge that supports action needs a continuing owner and maintenance route. Corrections from work should reach the responsible source and be reviewed before becoming a new operating assumption.

What leaders decide

Who owns each critical source, and how are changes, conflicts and corrections resolved?

Leadership considerations

  • Assign source responsibility. Name who can confirm meaning, resolve conflicts and approve material changes.
  • Connect feedback to maintenance. Route recurring gaps to the owner who can correct the underlying source.
  • Retire obsolete guidance. Make the current version identifiable and prevent superseded material from silently driving decisions.

What to watch

Unowned policy documents, repeated manual correction and different teams applying conflicting interpretations.

Illustrative invoice example

Recurring invoice discrepancies reveal that a purchasing policy reference is outdated; its owner corrects and reviews the source.

bp-intelligence

Connected Operating Blueprint dimension

Knowledge & context

Explore this Operating Blueprint dimension

knowledge owner data stewardship feedback learning

Reviewed on

October 9, 2026

Content edition

1.0

leadership-change

leadership-change

Leading the change

people

people

4

What must leaders do differently for the operating model to change?

Leadership connects ambition to choices about value, authority, resources and human contribution. Sustained sponsorship resolves the conflicts that a project team cannot settle alone.

What leaders decide

Which principles and operating commitments will guide the change across functions?

Leadership considerations

  • Set a coherent direction. Connect the desired business outcome with the changes in work and accountability.
  • Make trade-offs visible. Resolve competing objectives and resource commitments explicitly.
  • Stay involved in evidence. Review what is working and narrow, stop or redirect commitments when the case changes.

What to watch

A broad AI ambition with no shared priorities, unfunded dependencies or a technology team carrying every unresolved business decision.

Illustrative invoice example

Leaders agree that dependable invoice resolution matters more than maximizing the number of automated steps.

bp-value

Connected Operating Blueprint dimension

Value & outcomes

Explore this Operating Blueprint dimension

executive leadership transformation sponsorship

Reviewed on

October 9, 2026

Content edition

1.0

model-selection

model-selection

Model choice

agents

technology

4

Which model is suitable for this task and operating context?

Choose a model using evidence from the actual task and constraints. Consider accepted quality, latency, cost, information handling and the ability to sustain the service as versions change.

What leaders decide

Which model meets the required outcome and constraints with an acceptable operating burden?

Leadership considerations

  • Evaluate the task. Use representative cases and the criteria the business will apply.
  • Include operational constraints. Consider response time, context needs, access conditions and support.
  • Retest material changes. Treat a model or routing change as a change to the capability’s behavior.

What to watch

Selection driven only by general benchmarks, a powerful model used indiscriminately and performance changes after a version update.

Illustrative invoice example

Compare models on accepted invoice-case preparation, including missing evidence and review effort, before selecting a route.

bp-intelligence

Connected Operating Blueprint dimension

Knowledge & context

Explore this Operating Blueprint dimension

LLM model routing model evaluation latency

Reviewed on

October 9, 2026

Content edition

1.0

monitoring

monitoring

Monitoring & adaptation

shared

0

How do we know the operation is working, and when should someone intervene?

Observe business outcomes and execution behavior together. Connect signals to a responsible owner, an intervention threshold and a reviewed improvement decision.

What leaders decide

Which signals trigger review, restriction or suspension—and who has authority to respond?

Leadership considerations

  • Measure the operating result. Track accepted quality, elapsed time, full cost, exceptions and human review effort against a baseline.
  • Trace decisions and actions. Retain the relevant input context, tool actions, permissions, results and escalations with appropriate access controls.
  • Watch for departures. Look for unexpected action patterns, source-quality problems, repeated retries and attempts to cross boundaries.
  • Close the loop. Assign responses to alerts. Pause or narrow the affected route, investigate and review changes before expanding authority.

What to watch

Outcome deterioration, rising cost per accepted outcome, missed escalations, accumulating exceptions and alerts with no accountable response.

Illustrative invoice example

Watch invoice resolution time, review minutes, repeat exceptions and payment accuracy. Investigate any attempt to invoke an unapproved payment action.

bp-learning

Connected Operating Blueprint dimension

Evidence & adaptation

Explore this Operating Blueprint dimension

monitor metrics drift alerts operational monitoring

Reviewed on

October 9, 2026

Content edition

1.0

Monitoring & adaptation

outcome-baseline

outcome-baseline

Outcome and baseline

value

process

1

What should improve, and how does the work perform today?

Define the result for its intended stakeholder and establish a usable starting point. Include the full journey so that a local improvement does not conceal work moved elsewhere.

What leaders decide

Which outcome and baseline will distinguish a useful change from activity?

Leadership considerations

  • Define acceptance. State what counts as a successful result and which quality conditions must hold.
  • Measure the current journey. Include elapsed time, human effort, exceptions and stakeholder experience.
  • Record uncertainty. Separate measured evidence from estimates and impressions that still need validation.

What to watch

Success measures chosen after the trial, averages hiding difficult cases and claimed improvements without a comparable baseline.

Illustrative invoice example

Before changing invoice handling, measure time to accepted resolution, repeated clarification and full review effort on comparable cases.

bp-value

Connected Operating Blueprint dimension

Value & outcomes

Explore this Operating Blueprint dimension

baseline KPI success metrics

Reviewed on

October 9, 2026

Content edition

1.0

outcome-ownership

outcome-ownership

Outcome ownership

accountability

people

1

Who answers for the complete result?

A business capability needs an owner who can accept performance, commit resources and change the way work runs. Technical ownership supports that responsibility but does not replace it.

What leaders decide

Who accepts the service outcome and has the authority and funding to improve it?

Leadership considerations

  • Name the accountable role. Give one role responsibility for the end-to-end result and its operating commitments.
  • Connect supporting owners. Agree responsibilities for knowledge, interfaces, controls and exceptions.
  • Review the whole result. Include customer impact, quality, full effort and unresolved dependencies.

What to watch

Local teams meet their targets while the overall case slows down or its cost rises.

Illustrative invoice example

Finance owns accepted invoice resolution, while Procurement and Receiving remain responsible for the facts and decisions they contribute.

bp-operating

Connected Operating Blueprint dimension

Work & decisions

Explore this Operating Blueprint dimension

business owner service owner

Reviewed on

October 9, 2026

Content edition

1.0

people

people

People

overview

people

1

Who owns the outcome, exercises judgment and improves the operation?

Human contribution needs an explicit design: authority to decide, context to challenge, capacity to handle exceptions and responsibility for improvement.

What leaders decide

Which responsibilities remain with people, and what authority, evidence and capacity will they need?

Leadership considerations

  • Name accountable owners. Separate overall outcome ownership from responsibilities for systems, knowledge and controls.
  • Place judgment deliberately. Identify decisions that require a person and give that person a workable review path.
  • Support changed work. Develop skills, workload capacity and feedback routines together.

What to watch

A nominal human reviewer can become an approval bottleneck or lack the evidence needed to challenge a recommendation.

Illustrative invoice example

Finance owns the invoice exception outcome. Procurement and Receiving own specific facts and decisions that Finance needs.

bp-workforce

Connected Operating Blueprint dimension

People & capability

Explore this Operating Blueprint dimension

Reviewed on

October 9, 2026

Content edition

1.0

People

decision-placement

decision-placement

Place the decisions

work

process

4

Where does the work actually require a choice?

Distinguish routine execution from decisions involving context, consequence or trade-offs. Place each decision where the necessary evidence and authority can meet.

What leaders decide

Which decisions belong to rules, an agent or an authorized person?

Leadership considerations

  • Identify the real choice. Name the alternatives, uncertainty and consequence at the decision point.
  • Match the mechanism. Use rules for stable conditions and contextual judgment where it is justified.
  • Connect the authority. Keep the right to decide explicit even when preparation is automated.

What to watch

Agents introduced into deterministic tasks, excessive approvals and decisions made before the relevant context arrives.

Illustrative invoice example

A fixed rule may identify an invoice mismatch; a person may still need to decide how an unusual commercial exception is resolved.

bp-operating

Connected Operating Blueprint dimension

Work & decisions

Explore this Operating Blueprint dimension

decision automation rules engine decision architecture

Reviewed on

October 9, 2026

Content edition

1.0

platform-dependencies

platform-dependencies

Platform dependencies

platform-reliability

technology

3

Which external or shared capabilities could change the operating commitment?

Treat models, platforms, tools and shared services as continuing dependencies. Understand their constraints, ownership and change paths, including what happens if a dependency becomes unsuitable.

What leaders decide

Which dependencies are acceptable, who owns them, and what alternatives preserve the service?

Leadership considerations

  • Map the dependency. Identify the capability supplied and the conditions the route assumes.
  • Review material changes. Assess the effect of version, access, service or commercial changes on the operation.
  • Keep an exit path credible. Preserve the information and interfaces needed for a narrower mode or replacement.

What to watch

Unannounced behavior changes, poorly understood service limits and a capability that cannot operate without one unowned dependency.

Illustrative invoice example

A model-version change is evaluated against invoice cases before it becomes the default for the live route.

bp-intelligence

Connected Operating Blueprint dimension

Knowledge & context

Explore this Operating Blueprint dimension

vendor lock in build vs buy third party portability

Reviewed on

October 9, 2026

Content edition

1.0

portfolio-priorities

portfolio-priorities

Portfolio priorities

value

process

2

Which opportunities should move first?

Compare opportunities through value, feasibility, consequence and the shared capabilities they require. A portfolio should reveal dependencies and the capacity needed to support each commitment.

What leaders decide

Which opportunities deserve the next investment, and what must be built or learned first?

Leadership considerations

  • Compare the operating cases. Use a consistent view of outcome, cost, authority and uncertainty.
  • Expose dependencies. Identify common knowledge, interfaces, skills and controls that several opportunities need.
  • Sequence realistically. Account for operating capacity and avoid launching more change than teams can absorb.

What to watch

Many isolated pilots, repeated foundations and high-value proposals waiting on unowned dependencies.

Illustrative invoice example

Resolve shared supplier-data quality before expanding several invoice-related agents that depend on the same records.

bp-value

Connected Operating Blueprint dimension

Value & outcomes

Explore this Operating Blueprint dimension

roadmap use case prioritization portfolio

Reviewed on

October 9, 2026

Content edition

1.0

skills-practice

skills-practice

Practice and feedback

capability

people

2

How will people demonstrate the judgment their new role requires?

Use representative decisions, uncertain evidence and realistic exceptions to develop capability. Combine practice with feedback from actual work and clear routes for asking for help.

What leaders decide

Which judgments must each role demonstrate before taking responsibility?

Leadership considerations

  • Practice the difficult cases. Include incomplete context, conflicting evidence and a plausible but weak recommendation.
  • Make feedback specific. Review the reasoning, evidence and action, not only whether an answer matched expectations.
  • Refresh practice. Use recurring operational difficulties and material system changes to update scenarios.

What to watch

Confidence without demonstrated capability, repeated avoidable escalations and workarounds people cannot explain.

Illustrative invoice example

Reviewers practice recognizing when receipt evidence does not justify the proposed invoice resolution.

bp-workforce

Connected Operating Blueprint dimension

People & capability

Explore this Operating Blueprint dimension

training AI literacy upskilling

Reviewed on

October 9, 2026

Content edition

1.0

process

process

Process

overview

process

2

How should the work change to deliver the outcome?

Start with the result worth improving. Trace work across teams, simplify unnecessary steps and design for exceptions as well as the routine path.

What leaders decide

How should the end-to-end work change, and what will count as an accepted result?

Leadership considerations

  • Set the operating case. Include value, full running costs and the capacity needed to sustain the change.
  • Connect the handoffs. Specify the context, owner and acceptance condition at each transfer.
  • Design the exception route. Decide who takes over, how work continues and when a route should stop.

What to watch

Faster individual tasks can leave the real bottleneck untouched or move effort to another team.

Illustrative invoice example

Treat the invoice exception as one case from first discrepancy to an accepted resolution, rather than three disconnected departmental queues.

bp-operating

Connected Operating Blueprint dimension

Work & decisions

Explore this Operating Blueprint dimension

Reviewed on

October 9, 2026

Content edition

1.0

Process

review-quality

review-quality

Quality of human review

judgment

people

2

Can the reviewer meaningfully challenge the proposed action?

A review step is useful when the person can inspect the evidence, understand the uncertainty and choose a different action. Approval volume alone does not show effective oversight.

What leaders decide

What evidence, time and alternatives must a reviewer receive before deciding?

Leadership considerations

  • Prepare the decision. Show the proposed action, supporting facts, unresolved issues and consequences.
  • Make challenge possible. Provide a clear way to reject, correct, defer or request more evidence.
  • Examine review outcomes. Learn from overrides and missed issues without treating either as automatic proof of success or failure.

What to watch

Very fast approvals, repeated unexplained overrides, missing evidence and growing review effort.

Illustrative invoice example

The reviewer sees the invoice discrepancy and receipt uncertainty together, instead of receiving a recommended approval without its basis.

bp-workforce

Connected Operating Blueprint dimension

People & capability

Explore this Operating Blueprint dimension

rubber stamping human in the loop oversight

Reviewed on

October 9, 2026

Content edition

1.0

readiness

readiness

Readiness and progression

process

process

4

What must be true before this capability takes on real work or more authority?

Progression connects demonstrated capability with the commitments of a live operation. Review evidence, ownership, support and control before changing scope, volume or delegated authority.

What leaders decide

What operating commitment is justified now, and what still needs to be demonstrated?

Leadership considerations

  • Judge the whole capability. Include the work, people, knowledge, interfaces and controls.
  • Separate the commitments. Increasing volume, adding a new case type and granting more authority each need consideration.
  • Keep progression reversible. Be able to narrow the scope or return to an earlier operating mode.

What to watch

Pilot results treated as proof of readiness, unclear ownership at launch and authority expanding without a reviewed decision.

Illustrative invoice example

The invoice assistant can enter a reviewed-draft trial before it is considered for any automatic system updates.

bp-operating

Connected Operating Blueprint dimension

Work & decisions

Explore this Operating Blueprint dimension

launch production readiness scaling

Reviewed on

October 9, 2026

Content edition

1.0

process-redesign

process-redesign

Redesign the work

work

process

3

Which steps and handoffs should change before adding more automation?

Examine the work around the intended result. Remove unnecessary steps, reconnect decisions and context, and distinguish useful controls from avoidable coordination.

What leaders decide

What should the future work look like, including the responsibilities that remain human?

Leadership considerations

  • Trace actual cases. Observe delays, clarifications, duplicate entry and unofficial routes.
  • Question the inherited sequence. Ask which steps exist because information or authority was previously fragmented.
  • Design the whole path. Include routine work, exceptions, acceptance and ongoing improvement.

What to watch

Faster tasks inside an unchanged bottleneck, new duplicate records and additional effort at downstream teams.

Illustrative invoice example

A single evidence-backed invoice case replaces separate requests that each team must reconstruct.

bp-operating

Connected Operating Blueprint dimension

Work & decisions

Explore this Operating Blueprint dimension

workflow redesign process improvement BPM

Reviewed on

October 9, 2026

Content edition

1.0

platform-reliability

platform-reliability

Reliable operation

technology

technology

4

Can the underlying service sustain the business commitment?

Connect technical reliability to the outcome the business has accepted. Understand dependency failures, capacity limits and the evidence needed to diagnose and recover the route.

What leaders decide

What service conditions must hold, and how will the operation respond when they do not?

Leadership considerations

  • Define the service need. Set useful expectations for availability, latency, quality and recovery.
  • Make dependencies visible. Name the models, tools, knowledge sources and platforms required.
  • Design operational response. Connect technical signals to an owner and the permitted fallback.

What to watch

Technical dashboards without business impact, outages that create unowned queues and capacity assumptions that fail at peak demand.

Illustrative invoice example

An invoice service has defined handling expectations and an agreed response when a model or finance interface is unavailable.

bp-learning

Connected Operating Blueprint dimension

Evidence & adaptation

Explore this Operating Blueprint dimension

platform SRE operations availability

Reviewed on

October 9, 2026

Content edition

1.0

representative-testing

representative-testing

Representative cases

release-readiness

process

1

Does the evaluation reflect the work this capability will actually receive?

Build a case set that reflects meaningful variation in the intended operation. Preserve a way to examine difficult cases and outcomes that an average score can hide.

What leaders decide

Which case types and operating conditions must the evaluation cover?

Leadership considerations

  • Cover meaningful variation. Include ordinary, unusual, incomplete and conflicting cases within the intended scope.
  • Define the accepted result. Use outcome criteria that Outcome owners and reviewers can apply consistently.
  • Refresh the evidence. Add relevant cases as sources, patterns and the operating context change.

What to watch

Excellent results on familiar examples alongside poor performance on uncommon but consequential cases.

Illustrative invoice example

The invoice case set includes partial receipts, inconsistent order references, duplicate submissions and legitimate exceptions.

bp-learning

Connected Operating Blueprint dimension

Evidence & adaptation

Explore this Operating Blueprint dimension

test dataset benchmark edge cases

Reviewed on

October 9, 2026

Content edition

1.0

role-readiness

role-readiness

Role readiness

capability

people

1

Are people equipped to do the work the operating model asks of them?

Readiness combines skill, capacity, context and decision authority. Training alone does not establish that a role can absorb its new responsibilities.

What leaders decide

What evidence shows that a role has the skill, capacity and authority to take on its changed work?

Leadership considerations

  • Practice representative cases. Include ambiguous evidence, exceptions and situations requiring a challenge.
  • Check the working conditions. Provide access, time, support and a usable escalation route.

What to watch

Review overload, avoidance, parallel manual work and uncertainty about who may intervene.

Illustrative invoice example

Finance reviewers practice incomplete invoice cases and have a clear route for source verification and escalation.

bp-workforce

Connected Operating Blueprint dimension

People & capability

Explore this Operating Blueprint dimension

Reviewed on

October 9, 2026

Content edition

1.0

exception-routing

exception-routing

Route the exception

recovery

process

2

Does the right owner receive enough context to resolve the problem?

Treat an exception as work with its own owner, priority and acceptance condition. The route should explain why the system stopped and what decision or evidence is needed.

What leaders decide

Which exception goes to which role, and what must accompany the transfer?

Leadership considerations

  • Classify for action. Group exceptions by the response needed, not only by technical error type.
  • Prepare the handover. Include current state, attempted actions, unresolved facts and the requested decision.
  • Close the responsibility loop. Record acceptance, resolution and any change required in the original route.

What to watch

Exceptions circulating between teams, repeated requests for context and work disappearing into an unowned queue.

Illustrative invoice example

A missing receipt goes to Receiving for evidence; a commercial dispute goes to the role authorized to resolve it.

bp-operating

Connected Operating Blueprint dimension

Work & decisions

Explore this Operating Blueprint dimension

exceptions escalation case routing

Reviewed on

October 9, 2026

Content edition

1.0

safe-resumption

safe-resumption

Safe resumption

recovery

process

1

What must be true before paused work resumes?

A restart should follow reconciliation of the actual work state and the cause of the interruption. It must not repeat actions whose results are uncertain.

What leaders decide

Who confirms the actual state of the work and authorizes the next action after an interruption?

Leadership considerations

  • Reconcile what happened. Establish which actions completed and which remain uncertain.
  • Authorize the restart. Confirm that the cause is addressed and the responsible owner accepts the next step.

What to watch

Repeated failures, duplicate actions and restarts without a clear account of the previous attempt.

Illustrative invoice example

Check whether a case update was recorded before retrying after an interface failure.

bp-learning

Connected Operating Blueprint dimension

Evidence & adaptation

Explore this Operating Blueprint dimension

Reviewed on

October 9, 2026

Content edition

1.0

data-protection

data-protection

Sensitive information

knowledge

technology

4

Which information may this task use, retain or disclose?

Translate the information boundary into the way context, tools, outputs and logs handle data. Give owners a clear view of where sensitive information enters and leaves the route.

What leaders decide

What information is necessary, who may access it, and how long should it remain available?

Leadership considerations

  • Map the data path. Identify the records entering context, being written to systems or appearing in logs.
  • Apply the permitted use. Restrict access and sharing according to the task and the enterprise’s information rules.
  • Review retention. Keep enough evidence for the operating need while avoiding unnecessary copies and exposure.

What to watch

Sensitive material in broad context bundles, unrestricted logs and information shared beyond the intended case or role.

Illustrative invoice example

The invoice route uses the fields needed to resolve the case; unrelated supplier records do not enter the reviewer’s context.

bp-governance

Connected Operating Blueprint dimension

Authority & controls

Explore this Operating Blueprint dimension

privacy PII confidentiality data retention

Reviewed on

October 9, 2026

Content edition

1.0

case-state

case-state

Shared case state

work

process

2

Can everyone see what the work currently requires?

Maintain a dependable view of the case in the existing system of work. Connect decisions and dependencies to the record people use to coordinate.

What leaders decide

Where is the authoritative case record, and who keeps ownership, dependencies and decisions current?

Leadership considerations

  • Make ownership current. Show who acts next and what is blocking that action.
  • Preserve decision context. Connect changed commitments to their reason and authorized owner.

What to watch

Parallel trackers, contradictory status and decisions that exist only in conversations.

Illustrative invoice example

Procurement, Receiving and Finance use one case record with linked evidence and a visible next owner.

bp-operating

Connected Operating Blueprint dimension

Work & decisions

Explore this Operating Blueprint dimension

Reviewed on

October 9, 2026

Content edition

1.0

cross-functional-ownership

cross-functional-ownership

Shared responsibilities

accountability

people

2

How do owners resolve a dependency that crosses functions?

A shared outcome depends on explicit commitments between teams. Agree how competing priorities, missing evidence and delayed decisions are resolved before routine work relies on informal negotiation.

What leaders decide

Which obligations does each team accept, and who resolves a conflict between them?

Leadership considerations

  • Agree the working contract. Specify the required contribution, owner, timing and acceptance condition.
  • Name the escalation decision. Clarify who may change priorities or resolve incompatible commitments.
  • Keep the context together. Record changed commitments and their rationale in the existing system of work.

What to watch

Chasing, stalled dependencies and decisions that emerge in conversations without reaching the shared record.

Illustrative invoice example

Finance and Receiving agree how a missing receipt is verified and who decides when the normal response window is exceeded.

bp-operating

Connected Operating Blueprint dimension

Work & decisions

Explore this Operating Blueprint dimension

cross functional coordination dependency

Reviewed on

October 9, 2026

Content edition

1.0

source-quality

source-quality

Source quality

knowledge

technology

1

Can the decision rely on the facts currently available?

The value of context depends on its relevance, origin and currency. Missing or conflicting evidence should affect what the operation is allowed to do next.

What leaders decide

What level of relevance, currency and provenance is needed for the decision at hand?

Leadership considerations

  • Identify the authority. Name the responsible source and the owner who can resolve a conflict.
  • Match freshness to the action. Define how current information needs to be for this decision.

What to watch

Stale policy, contradictory records, missing provenance and assertions that cannot be checked.

Illustrative invoice example

A purchase order does not establish that goods arrived. The receipt needs confirmation from the responsible source.

bp-intelligence

Connected Operating Blueprint dimension

Knowledge & context

Explore this Operating Blueprint dimension

Reviewed on

October 9, 2026

Content edition

1.0

change-sponsorship

change-sponsorship

Sponsorship in practice

leadership-change

people

2

Who resolves the decisions that keep the change moving?

Sponsorship is a continuing responsibility for priorities, resources and unresolved business choices. It should be visible in the decisions that the operating team needs.

What leaders decide

Which conflicts require a sponsor, and how will those decisions reach the work?

Leadership considerations

  • Define sponsor decisions. Clarify authority over competing priorities, scope, resources and cross-team commitments.
  • Keep a review rhythm. Bring unresolved choices and operating evidence to a predictable forum.
  • Record the result. Carry the decision and rationale back into the shared plan and case design.

What to watch

Repeated discussion without a decision, commitments that change informally and teams compensating through extra coordination.

Illustrative invoice example

The sponsor resolves a conflict between Finance review capacity and the proposed invoice rollout volume before expansion.

bp-operating

Connected Operating Blueprint dimension

Work & decisions

Explore this Operating Blueprint dimension

sponsor change management

Reviewed on

October 9, 2026

Content edition

1.0

strategic-alignment

strategic-alignment

Strategic alignment

leadership-change

people

1

How does this capability contribute to the enterprise direction?

Connect the capability to a business priority and its constraints. Revisit the connection when strategy, demand or risk appetite changes.

What leaders decide

Which strategic outcome does this change support, and what should it displace or enable?

Leadership considerations

  • Name the contribution. Explain the effect on service, growth, quality, resilience or cost.
  • Make opportunity cost visible. Compare the commitment with other ways to achieve the outcome.
  • Review the fit. Reassess priorities when the original assumptions no longer hold.

What to watch

Projects justified by AI adoption targets while business priorities or operational constraints remain unclear.

Illustrative invoice example

Invoice exception improvement supports dependable supplier service and payment accuracy, with an explicit boundary on the first release.

bp-value

Connected Operating Blueprint dimension

Value & outcomes

Explore this Operating Blueprint dimension

strategy business alignment

Reviewed on

October 9, 2026

Content edition

1.0

systems

systems

Systems & access

technology

technology

3

Where may the system read, write and take action?

Autonomy becomes consequential at the interfaces to business systems. Permissions, validation and recorded state changes need to hold independently of the model's instructions.

What leaders decide

Which systems may be read or changed, through which interfaces, and under whose authorization?

Leadership considerations

  • Grant only necessary access. Separate reading, drafting, updating and approving. Keep credentials and permissions scoped to the job.
  • Validate state changes. Check inputs, allowed transitions and authorization before consequential writes.
  • Support dependable recovery. Avoid duplicate actions on retries, preserve an audit record and define how failures are reconciled.

What to watch

Overbroad access, unapproved writes, duplicate actions, missing records and inconsistent state across systems.

Illustrative invoice example

The invoice assistant can read permitted records and prepare a case. Payment release and bank-detail changes remain behind separate authority checks.

bp-governance

Connected Operating Blueprint dimension

Authority & controls

Explore this Operating Blueprint dimension

Reviewed on

October 9, 2026

Content edition

1.0

Systems & access

task-scope

task-scope

Task scope

agents

technology

1

What exactly has the agent been asked to accomplish?

An assigned task needs a useful outcome, an explicit boundary and a way to recognize completion. Flexible execution should remain within that assignment.

What leaders decide

What is the exact assignment, what is excluded, and how will completion or blockage be recognized?

Leadership considerations

  • Define the assignment. State the result, the work in scope and what must remain outside it.
  • Make completion explicit. Describe the evidence that the task is complete or cannot safely proceed.
  • Separate intent from permission. A desirable outcome does not authorize every possible action to achieve it.

What to watch

A task expands without approval, produces activity without an accepted result, or continues after it should stop.

Illustrative invoice example

The invoice agent gathers missing receipt evidence. It does not negotiate payment terms or release payment.

bp-governance

Connected Operating Blueprint dimension

Authority & controls

Explore this Operating Blueprint dimension

Reviewed on

October 9, 2026

Content edition

1.0

technology

technology

Technology

overview

technology

3

What enables dependable decisions and action?

Connect trusted context, appropriate intelligence and controlled access to existing systems. Each technical choice should support a specific operating responsibility.

What leaders decide

Which capabilities are necessary for this operating design, and how will their limits be enforced?

Leadership considerations

  • Make context usable. Bring current facts, policy and work state to the decision point.
  • Coordinate deliberately. Choose a workflow, an agent or a combination according to the uncertainty in the work.
  • Enforce access. Make permitted actions real at the system interfaces and record what happens.

What to watch

Fluent answers can conceal stale facts, missing permissions or unavailable downstream systems.

Illustrative invoice example

The invoice case needs purchase-order and receipt evidence, a way to coordinate missing facts, and controlled access to the finance system.

bp-intelligence

Connected Operating Blueprint dimension

Knowledge & context

Explore this Operating Blueprint dimension

Reviewed on

October 9, 2026

Content edition

1.0

Technology

release-readiness

release-readiness

Testing and release readiness

readiness

process

1

What evidence shows that this version is ready for its intended scope?

Evaluate the complete route against agreed acceptance criteria, including difficult cases, failures and attempted boundary violations. Readiness remains specific to the tested scope and operating conditions.

What leaders decide

Which results permit release, which failures block it, and who accepts the remaining limitations?

Leadership considerations

  • Set criteria before the test. Cover accepted outcomes, permissions, escalation, cost and human workload.
  • Test the surrounding operation. Include real interfaces, source quality, review and recovery conditions.
  • Retain release evidence. Record the versions, cases, limitations and approval needed to understand the decision.

What to watch

A single accuracy score, unrepresentative demonstrations and releases with no record of known failure conditions.

Illustrative invoice example

Test missing receipts, conflicting purchase orders, failed writes and attempts to request an unauthorized payment action.

bp-governance

Connected Operating Blueprint dimension

Authority & controls

Explore this Operating Blueprint dimension

evaluation evals testing release gate quality assurance

Reviewed on

October 9, 2026

Content edition

1.0

runtime-observability

runtime-observability

Trace the operation

platform-reliability

technology

1

Can we reconstruct a consequential result well enough to investigate it?

Retain the evidence needed to connect a case, its relevant inputs, tool actions, permissions and outcomes. Trace design should support investigation while respecting information access and retention needs.

What leaders decide

What evidence must be recorded, who can inspect it, and which events require action?

Leadership considerations

  • Follow the case. Connect material decisions and actions across the systems involved.
  • Preserve useful context. Record relevant versions, permissions, results and escalation without collecting everything by default.
  • Make evidence actionable. Give the responsible roles a practical way to investigate and respond.

What to watch

An unexplained result, disconnected logs and records that expose sensitive content without helping resolve the incident.

Illustrative invoice example

A reviewer can trace which receipt source the invoice route used, which update it attempted and whether that action was accepted.

bp-learning

Connected Operating Blueprint dimension

Evidence & adaptation

Explore this Operating Blueprint dimension

observability tracing logs audit trail

Reviewed on

October 9, 2026

Content edition

1.0

untrusted-inputs

untrusted-inputs

Untrusted instructions

knowledge

technology

5

Can incoming content redirect the agent away from its assignment?

Treat instructions found in documents, messages or tool results as untrusted content. They do not change the assigned task or grant permission to use a tool.

What leaders decide

Where could outside content influence the route, and what independent limits contain that influence?

Leadership considerations

  • Keep authority separate. Do not let retrieved content redefine permissions or approval requirements.
  • Constrain possible actions. Enforce tool access and consequential-action checks outside the model.
  • Test and observe. Challenge the route with misleading instructions and review attempted boundary violations.

What to watch

Requests to disregard controls, disclose unrelated records or call tools outside the assigned scope.

Illustrative invoice example

An invoice attachment says to bypass approval and send supplier data elsewhere. Its text cannot authorize either action.

bp-governance

Connected Operating Blueprint dimension

Authority & controls

Explore this Operating Blueprint dimension

prompt injection goal hijacking agent deviation

Reviewed on

October 9, 2026

Content edition

1.0

value

value

Value & priorities

process

process

1

Which outcome makes this change worth pursuing?

Choose an operating problem or opportunity with a clear owner and a baseline. Consider growth, service, quality and resilience alongside efficiency.

What leaders decide

Which outcome justifies the next commitment, including the full effort to run and oversee it?

Leadership considerations

  • Define value and scope. Name the stakeholder, intended result and boundaries of the first commitment.
  • Count the full effort. Include technology, human review, integration, oversight, support and recovery.
  • Set an evidence threshold. Agree what would justify proceeding, redesigning, narrowing or stopping.

What to watch

Benefits claimed from time saved without a plan for capacity, hidden review costs or local gains that worsen the overall outcome.

Illustrative invoice example

Evaluate accepted invoice resolutions, full handling effort and payment accuracy. Model speed alone does not establish business value.

bp-value

Connected Operating Blueprint dimension

Value & outcomes

Explore this Operating Blueprint dimension

Reviewed on

October 9, 2026

Content edition

1.0

Value & priorities

workflow-or-agent

workflow-or-agent

Workflow or agent?

agents

technology

3

Does the next step require flexible judgment or a stable sequence?

Use the simplest mechanism that meets the operating need. A controlled workflow can coordinate predictable steps, while an agent can select among permitted actions when the context genuinely varies.

What leaders decide

Where is flexible step selection useful enough to justify its additional oversight and uncertainty?

Leadership considerations

  • Describe the variability. Identify what changes between cases and why a fixed sequence is insufficient.
  • Keep stable controls explicit. Use deterministic checks for permissions and conditions that must always hold.
  • Compare the full operation. Evaluate quality, cost, failure handling and review effort across candidate designs.

What to watch

Agent behavior used for straightforward rules, repeated unnecessary reasoning and complexity without measurable benefit.

Illustrative invoice example

A workflow routes an invoice by a known condition; an agent may assemble a case when the missing evidence differs each time.

bp-intelligence

Connected Operating Blueprint dimension

Knowledge & context

Explore this Operating Blueprint dimension

agent vs workflow automation deterministic agentic

Reviewed on

October 9, 2026

Content edition

1.0

work

work

Work & handoffs

process

process

2

What must travel with the work so the next owner can act?

Connect tasks, decisions, context and responsibilities around the end-to-end outcome. Make the conditions for accepting and completing work explicit.

What leaders decide

What context and ownership must travel with the work before the next team can accept it?

Leadership considerations

  • Trace the whole journey. Follow work across functions and partners, including delays and repeated clarification.
  • Design a usable handoff. Specify the owner, required context, open questions and acceptance condition.
  • Remove unnecessary work. Simplify avoidable steps before deciding where automation or agent choices add value.

What to watch

Work marked complete before acceptance, repeated chasing, duplicated records and decisions separated from their rationale.

Illustrative invoice example

A shared invoice case shows who must resolve the price discrepancy, what receipt evidence is missing and when Finance can proceed.

bp-operating

Connected Operating Blueprint dimension

Work & decisions

Explore this Operating Blueprint dimension

Reviewed on

October 9, 2026

Content edition

1.0

Work & handoffs

who-owns-ai-enabled-operating-model

Who Owns the AI-Enabled Operating Model?

url

Reading

ai-agents-systems-of-record

AI Agents and Systems of Record: Making Changes Dependable

url

Reading

assuring-ai-services-from-release-to-retirement

Assuring AI Services from Release to Retirement

url

Reading

work-mechanism-completion

Completion evidence and recovery

url

Reading

work-mechanism-scope

Define the outcome before choosing the mechanism

url

Reading

work-mechanism-comparison

Compare workflows, AI assistance and agents

url

Reading

workflow-agent-or-both

Workflow, Agent, or Both? Choosing How Work Gets Done

url

Reading

before-an-ai-agent-acts

Before an AI Agent Acts: Where Authority Is Enforced

url

Reading

leading-change-role-transition

Leading the Change: role transitions

url

Reading

leading-change-adoption-evidence

Leading the Change: adoption evidence

url

Reading

leading-change-sponsor-commitments

Leading the Change: sponsor commitments

url

Reading

leading-change-ai-enabled-operations

Leading the Change to AI-Enabled Operations

url

Reading

governing-ai-enabled-operations

Governing AI-Enabled Operations

url

Reading

redesigning-work-around-outcomes

Redesigning Work Around Outcomes

url

Reading

supplier-payments-operating-record

The Work Behind Faster Supplier Payments

url

Reading

modernize-existing-automation

Modernize the Automation You Already Have

url

Reading

bp-learning

Evidence & adaptation

url

Blueprint dimension

06

bp-workforce

People & capability

url

Blueprint dimension

05

bp-governance

Authority & controls

url

Blueprint dimension

04

bp-intelligence

Knowledge & context

url

Blueprint dimension

03

bp-operating

Work & decisions

url

Blueprint dimension

02

nist-rmf

NIST: AI Risk Management Framework

url

Reading

owasp-agent

OWASP: AI Agent Security

url

Reading

map-N12

Autonomy Map: adapt the operation

url

Reading

map-N11

Autonomy Map: judge the evidence

url

Reading

map-N10

Autonomy Map: build human capability

url

Reading

map-N09

Autonomy Map: design human roles

url

Reading

map-N08

Autonomy Map: apply the controls

url

Reading

map-N07

Autonomy Map: define the authority

url

Reading

map-N06

Autonomy Map: learn from feedback

url

Reading

map-N05

Autonomy Map: establish the knowledge

url

Reading

map-N04

Autonomy Map: ask for human help

url

Reading

map-N03

Autonomy Map: coordinate the work

url

Reading

map-N02

Autonomy Map: build the investment case

url

Reading

map-N01

Autonomy Map: choose the outcome

url

Reading

doctrine

The RePerspective Doctrine

url

Reading

transformation

Transformation Hub

url

Reading

automation-primer

AI Primer: Rules-Based Automation

url

Reading

agent-primer

AI Primer: AI Agents

url

Reading

adoption

AI Adoption: When the Old Way Still Wins

url

Reading

taking-shape

Working with AI When the Problem Is Still Taking Shape

url

Reading

strategy

AI Strategy: The Leadership Approach

url

Reading

leadershipjudgment

Leadership Judgment in the Age of AI

url

Reading

evolution

The Continuous Evolution Loop

url

Reading

controls

Controls by Design for AI Operations

url

Reading

ownership

From Project Team to Business Ownership

url

Reading

pilot

From Pilot to Operating Rhythm

url

Reading

possibilities

Possibilities

url

Reading

businesscase

Building the Business Case for Automation-to-Autonomy

url

Reading

measurement

Measurement

url

Reading

healing

Self-Healing Enterprise: authorize a response

url

Reading

progression

From Automation to Autonomy: choose a commitment

url

Reading

workforce

AI-Era Workforce Capability: readiness evidence

url

Reading

human

Human-in-the-Loop Synergy: decision design

url

Reading

bounded

Bounded Autonomy: the authority record

url

Reading

knowledge

Enterprise Knowledge Backbone: apply the framework

url

Reading

digital

Digital Operating Model

url

Reading

redesign

Operating Model Redesign

url

Reading

map

Autonomy Map

url

Reading

flagship

The Autonomous Enterprise Blueprint

url

Reading

blueprint

Operating Blueprint

url

Reading

bp-value

Value & outcomes

url

Blueprint dimension

01

Accountability · Reading · 4

accountability

Reading

who-owns-ai-enabled-operating-model

Connect outcome accountability to funded commitments and bounded decision authority.

4

Shared responsibilities · Reading · 4

cross-functional-ownership

Reading

who-owns-ai-enabled-operating-model

Compare who can commit shared capacity, fund the work and resolve a mandate disagreement.

4

Dependable state changes · Reading · 4

state-consistency

Reading

ai-agents-systems-of-record

4

Enterprise integration · Reading · 5

interoperability

Reading

ai-agents-systems-of-record

5

Systems & access · Reading · 4

systems

Reading

ai-agents-systems-of-record

4

Readiness and progression · Service assurance

readiness

Reading

assuring-ai-services-from-release-to-retirement

4

Testing and release readiness · Service assurance

release-readiness

Reading

assuring-ai-services-from-release-to-retirement

4

Representative cases · Service assurance

representative-testing

Reading

assuring-ai-services-from-release-to-retirement

4

Challenge the boundaries · Service assurance

adverse-case-testing

Reading

assuring-ai-services-from-release-to-retirement

4

Completion checks · Reading · 5

completion-checks

Reading

work-mechanism-completion

Follow conflicting evidence through an owned hold, authoritative resolution and accepted completion.

5

Task scope · Reading · 5

task-scope

Reading

work-mechanism-scope

Agree the eligible cases, completion evidence and receiving owner before selecting a mechanism.

5

Workflow or agent? · Reading · 4

workflow-or-agent

Reading

work-mechanism-comparison

Compare four operating arrangements and explore their dependencies using the interactive guide.

4

Agents & orchestration · Reading · 4

agents

Reading

workflow-agent-or-both

Choose and combine mechanisms for defined work, with common acceptance criteria and full recurring cost.

4

Task scope · Reading · 4

task-scope

Reading

before-an-ai-agent-acts

Keep the acting service and requested operation tied to the authorized case and assignment.

4

Action limits · Reading · 4

action-limits

Reading

before-an-ai-agent-acts

Enforce scope, exact-action approval, current conditions and refusal before the business effect.

4

Completion checks · Reading · 4

completion-checks

Reading

before-an-ai-agent-acts

Distinguish a proposed, authorized and attempted action from an accepted business result.

4

Untrusted instructions · Reading · 4

untrusted-inputs

Reading

before-an-ai-agent-acts

See how a hostile document or unverified memory is prevented from changing authority.

4

Identity and permissions · Reading · 4

identity-access

Reading

before-an-ai-agent-acts

Distinguish the requester, acting service, information access and authority for the specific action.

4

Controlled tool use · Reading · 4

tool-contracts

Reading

before-an-ai-agent-acts

Follow a constrained fee-reversal operation through execution checks and the tool contract.

4

Trace the operation · Reading · 4

runtime-observability

Reading

before-an-ai-agent-acts

Connect the assigned task, authorization, execution and accepted result through protected evidence.

4

Changing roles · Reading · 4

workforce-transition

Reading

leading-change-role-transition

4

Capability & adoption · Reading · 4

capability

Reading

leading-change-role-transition

4

Adoption and incentives · Reading · 4

adoption-incentives

Reading

leading-change-adoption-evidence

4

Sponsorship in practice · Reading · 4

change-sponsorship

Reading

leading-change-sponsor-commitments

4

Leading the change · Reading · 4

leadership-change

Reading

leading-change-ai-enabled-operations

4

Monitoring & adaptation · Reading · 4

monitoring

Reading

governing-ai-enabled-operations

4

Authority & boundaries · Reading · 4

authority

Reading

governing-ai-enabled-operations

4

Work & handoffs · Reading · 4

work

Reading

redesigning-work-around-outcomes

4

Redesign the work · Reading · 5

process-redesign

Reading

redesigning-work-around-outcomes

5

Redesign the work · Reading · 4

process-redesign

Reading

supplier-payments-operating-record

4

Enterprise integration · Reading · 4

interoperability

Reading

modernize-existing-automation

4

Platform dependencies · Reading · 3

platform-dependencies

Reading

map-N12

3

Platform dependencies · Reading · 2

platform-dependencies

Reading

pilot

2

Platform dependencies · Reading · 1

platform-dependencies

Reading

digital

1

Platform dependencies · Related topic · 3

platform-dependencies

Related topic

governed-change

Dependency changes require a reviewed response.

3

Platform dependencies · Related topic · 2

platform-dependencies

Related topic

interoperability

Interfaces influence replacement effort.

2

Platform dependencies · Related topic · 1

platform-dependencies

Related topic

model-selection

Selection includes the continuing service relationship.

1

Capacity and limits · Reading · 3

resilience-limits

Reading

map-N12

3

Capacity and limits · Reading · 2

resilience-limits

Reading

measurement

2

Capacity and limits · Reading · 1

resilience-limits

Reading

healing

1

Capacity and limits · Related topic · 3

resilience-limits

Related topic

business-continuity

The service needs a realistic fallback.

3

Capacity and limits · Related topic · 2

resilience-limits

Related topic

escalation-capacity

Degradation can transfer demand to people.

2

Capacity and limits · Related topic · 1

resilience-limits

Related topic

action-limits

Resource limits are part of the task boundary.

1

Trace the operation · Reading · 3

runtime-observability

Reading

map-N11

3

Trace the operation · Reading · 2

runtime-observability

Reading

controls

2

Trace the operation · Reading · 1

runtime-observability

Reading

measurement

1

Trace the operation · Related topic · 3

runtime-observability

Related topic

state-consistency

Recorded events must support reconciliation.

3

Trace the operation · Related topic · 2

runtime-observability

Related topic

data-protection

Evidence collection has an information boundary.

2

Trace the operation · Related topic · 1

runtime-observability

Related topic

monitoring

Traces support the wider view of operating performance.

1

Reliable operation · Reading · 3

platform-reliability

Reading

map-N12

3

Reliable operation · Reading · 2

platform-reliability

Reading

pilot

2

Reliable operation · Reading · 1

platform-reliability

Reading

healing

1

Reliable operation · Related topic · 3

platform-reliability

Related topic

platform-dependencies

Each dependency needs an operating owner.

3

Reliable operation · Related topic · 2

platform-reliability

Related topic

runtime-observability

Evidence must show where and why the route failed.

2

Reliable operation · Related topic · 1

platform-reliability

Related topic

business-continuity

Reliability supports the continuity commitment.

1

Enterprise integration · Reading · 3

interoperability

Reading

map-N03

3

Enterprise integration · Reading · 2

interoperability

Reading

knowledge

2

Enterprise integration · Reading · 1

interoperability

Reading

digital

1

Enterprise integration · Related topic · 3

interoperability

Related topic

platform-dependencies

Integration creates dependencies that must be owned.

3

Enterprise integration · Related topic · 2

interoperability

Related topic

tool-contracts

Interfaces need explicit operating contracts.

2

Enterprise integration · Related topic · 1

interoperability

Related topic

case-state

Integration should support a coherent case.

1

Dependable state changes · Reading · 3

state-consistency

Reading

map-N08

3

Dependable state changes · Reading · 2

state-consistency

Reading

controls

2

Dependable state changes · Reading · 1

state-consistency

Reading

healing

1

Dependable state changes · Related topic · 3

state-consistency

Related topic

runtime-observability

Evidence must support reconciliation.

3

Dependable state changes · Related topic · 2

state-consistency

Related topic

completion-checks

Tool success alone may not establish completion.

2

Dependable state changes · Related topic · 1

state-consistency

Related topic

safe-resumption

Recovery depends on the real state of work.

1

Controlled tool use · Reading · 3

tool-contracts

Reading

map-N08

3

Controlled tool use · Reading · 2

tool-contracts

Reading

bounded

2

Controlled tool use · Reading · 1

tool-contracts

Reading

controls

1

Controlled tool use · Related topic · 3

tool-contracts

Related topic

untrusted-inputs

Source content cannot authorize a tool call.

3

Controlled tool use · Related topic · 2

tool-contracts

Related topic

state-consistency

A result must match the recorded state.

2

Controlled tool use · Related topic · 1

tool-contracts

Related topic

identity-access

The tool must verify the acting identity.

1

Identity and permissions · Reading · 3

identity-access

Reading

map-N08

3

Identity and permissions · Reading · 2

identity-access

Reading

controls

2

Identity and permissions · Reading · 1

identity-access

Reading

bounded

1

Identity and permissions · Related topic · 3

identity-access

Related topic

runtime-observability

Recorded actions need attributable identities.

3

Identity and permissions · Related topic · 2

identity-access

Related topic

data-protection

Permissions also govern information access.

2

Identity and permissions · Related topic · 1

identity-access

Related topic

authority

Identity makes the permission boundary enforceable.

1

Coordinating agents · Reading · 3

multi-agent-coordination

Reading

map-N03

3

Coordinating agents · Reading · 2

multi-agent-coordination

Reading

bounded

2

Coordinating agents · Reading · 1

multi-agent-coordination

Reading

digital

1

Coordinating agents · Related topic · 3

multi-agent-coordination

Related topic

action-limits

Delegation must not expand another agent’s permissions.

3

Coordinating agents · Related topic · 2

multi-agent-coordination

Related topic

case-state

The operation needs a coherent case record.

2

Coordinating agents · Related topic · 1

multi-agent-coordination

Related topic

coordination-checkpoints

Each agent handoff needs a controlled transition.

1

Model choice · Reading · 3

model-selection

Reading

map-N11

3

Model choice · Reading · 2

model-selection

Reading

measurement

2

Model choice · Reading · 1

model-selection

Reading

agent-primer

1

Model choice · Related topic · 3

model-selection

Related topic

platform-dependencies

The choice creates a continuing service dependency.

3

Model choice · Related topic · 2

model-selection

Related topic

unit-economics

Model cost is part of the cost per accepted outcome.

2

Model choice · Related topic · 1

model-selection

Related topic

representative-testing

The evaluation needs the real case mix.

1

Workflow or agent? · Reading · 3

workflow-or-agent

Reading

map-N03

3

Workflow or agent? · Reading · 2

workflow-or-agent

Reading

automation-primer

2

Workflow or agent? · Reading · 1

workflow-or-agent

Reading

agent-primer

1

Workflow or agent? · Related topic · 3

workflow-or-agent

Related topic

task-scope

An agent still needs an explicit assignment.

3

Workflow or agent? · Related topic · 2

workflow-or-agent

Related topic

unit-economics

Flexibility has to earn its operating cost.

2

Workflow or agent? · Related topic · 1

workflow-or-agent

Related topic

decision-placement

Mechanism follows the actual decision.

1

Untrusted instructions · Additional reference · 1

untrusted-inputs

Additional reference

owasp-agent

1

Untrusted instructions · Reading · 3

untrusted-inputs

Reading

map-N08

3

Untrusted instructions · Reading · 2

untrusted-inputs

Reading

bounded

2

scale

Build a dependable operation

How do we scale well?

6

4

people

Design the human contribution

What changes for people?

5

4

ready

Earn the next operating commitment

Are we ready to launch?

4

4

value

Follow the full operating case

Will the value hold?

3

4

control

Keep action within authority

How do we keep control?

2

5

start

Start with a worthwhile outcome

Where do we start?

1

4

How do we scale well? · 4 · Change and improvement

scale

governed-change

4

How do we scale well? · 3 · Reliable operation

scale

platform-reliability

3

How do we scale well? · 2 · Shared responsibilities

scale

cross-functional-ownership

2

How do we scale well? · 1 · From pilot to operation

scale

pilot-to-operation

1

What changes for people? · 4 · Practice and feedback

people

skills-practice

4

What changes for people? · 3 · Changing roles

people

workforce-transition

3

What changes for people? · 2 · Quality of human review

people

review-quality

2

What changes for people? · 1 · Decision rights

people

decision-rights

1

Are we ready to launch? · 4 · From pilot to operation

ready

pilot-to-operation

4

Are we ready to launch? · 3 · Role readiness

ready

role-readiness

3

Are we ready to launch? · 2 · Representative cases

ready

representative-testing

2

Are we ready to launch? · 1 · Testing and release readiness

ready

release-readiness

1

Will the value hold? · 4 · Monitoring & adaptation

value

monitoring

4

Will the value hold? · 3 · Outcome ownership

value

outcome-ownership

3

Will the value hold? · 2 · Adoption and incentives

value

adoption-incentives

2

Will the value hold? · 1 · Cost per accepted outcome

value

unit-economics

1

How do we keep control? · 5 · Monitoring & adaptation

control

monitoring

5

How do we keep control? · 4 · Challenge the boundaries

control

adverse-case-testing

4

How do we keep control? · 3 · Untrusted instructions

control

untrusted-inputs

3

How do we keep control? · 2 · Identity and permissions

control

identity-access

2

How do we keep control? · 1 · Authority & boundaries

control

authority

1

Where do we start? · 4 · Investment decisions

start

investment-gates

4

Where do we start? · 3 · Workflow or agent?

start

workflow-or-agent

3

Where do we start? · 2 · Redesign the work

start

process-redesign

2

Where do we start? · 1 · Outcome and baseline

start

outcome-baseline

1

Take the next useful step.

Use this overview to see the connections, then choose the depth or application you need.

Start with the operating question.

My approach connects purpose, architecture and the practical choices needed to change how an enterprise works.

Explore approach