Skip to main content
Large People ModelHuman Operating Architecture
AboutSearch the complete site3-minute readiness check

Layer 01 of 07

Ownership

Formal name: Identity & Incentives

Turn contribution into accountability.

Understand this layer in one minute

In one minute

What ownership does

A plain-language definition, the leadership question, and the operating value of getting this layer right.

Layer job

Identity & Incentives defines who owns outcomes, what authority comes with that ownership, and what behaviors the organization rewards or tolerates.

Leader question

Who owns the outcome?

What good looks like

Every priority outcome has one named human owner with enough authority and incentive to carry accountability through execution.

01

Creates the accountability chain

Every decision, workflow, control, and AI use case depends on knowing who owns the outcome.

02

Prevents local optimization

Incentives determine whether teams optimize for enterprise outcomes or protect local metrics.

03

Keeps AI accountable

Automated work still needs a named human owner for adoption, risk, accuracy, and result quality.

Hypothetical worked example

A refund request that falls outside the standard policy

The same scenario follows readers through all seven layers. Here is the part this layer must make work.

A customer asks for an exception. A governed agent can collect the facts and recommend a response, but the organization still needs a named human owner, a decision rule, trusted information, and a reviewable record.

  1. 01
  2. 02
  3. 03
  4. 04
  5. 05
  6. 06
  7. 07

This layer's responsibility

Ownership

Identity & Incentives

Operating move

The head of customer operations owns the quality and risk of refund outcomes.

Result across all seven layers

The customer receives a faster answer, the decision remains traceable, and AI increases capacity without inheriting authority it should not hold.

Diagnose

Start with three questions, three signals, and three measures

These are prompts for a leadership conversation, not a complete assessment instrument.

Ask

  1. 01Who owns the outcome?
  2. 02Who owns the decision?
  3. 03Who owns the risk?

Recognizable symptoms

  1. 01Everyone contributes, but no one owns the result.
  2. 02Decisions bounce between teams because no one has clear authority.
  3. 03Incentives reward local optimization over enterprise coordination.

Measure

  1. 01Ownership clarity score
  2. 02Decision owner coverage
  3. 03Escalation frequency

Failure patterns

What weakness looks like in practice

01

Participation Without Accountability

Many stakeholders attend meetings, provide input, and influence direction, but no one is accountable for the outcome.

Downstream effect: Decisions slow down, communication increases, and execution risk has no owner.

02

Incentive Mismatch

Teams are rewarded for local metrics even when those behaviors create enterprise drag.

Downstream effect: Teams optimize their area while breaking cross-functional flow.

03

AI Without an Owner

AI use cases are launched by innovation, technology, or product teams without a named accountable business owner.

Downstream effect: AI creates activity, but no one owns adoption, risk, accuracy, or outcome quality.

Metric signals

Measure the condition, not the activity

Ownership clarity score

Whether outcomes have named accountable owners.

Weak signal

Owners are assumed, shared, or listed only as sponsors.

Strong signal

Each critical outcome has one accountable owner with defined authority.

Decision owner coverage

The percentage of key decisions with documented owners.

Weak signal

Decisions are escalated or revisited because authority is unclear.

Strong signal

Decision owners are named before work begins.

Escalation frequency

How often ownership gaps move work upward.

Weak signal

Escalation is the default way to resolve responsibility.

Strong signal

Escalations are rare, structured, and tied to explicit thresholds.

Improve

Make three moves with one primary working tool

Keep the first intervention small enough to own, observe, and review.

  1. 01

    Name one accountable owner for each priority outcome.

  2. 02

    Match decision, budget, pause, and override authority to that ownership.

  3. 03

    Review incentives for behaviors that reward local wins at the expense of the enterprise outcome.

Primary working tool

Function ownership map

Map each outcome to one accountable role, its authority, and the contributors around it.

Learn how to use it

Maturity path

Progress from invisible to adaptive

Move one phase at a time. The next phase is credible only when its operating condition is observable in real work.

  1. 01

    Invisible

    Ownership is assumed, undocumented, and dependent on individual initiative.

  2. 02

    Fragmented

    Some teams define owners, but accountability varies by function or leader.

  3. 03

    Defined

    Outcome owners, decision owners, and escalation paths are documented.

  4. 04

    Managed

    Ownership is reviewed through operating rhythms, metrics, and governance.

  5. 05

    Adaptive

    Ownership adjusts as strategy, platforms, AI workflows, and risk conditions change.

Evidence in practice

Put ownership into the work

Use concrete artifacts, bounded use cases, and visible evidence to move this layer from an idea into an operating condition.

Working artifacts

Make the layer visible

01Ownership mapA map of accountable owners across outcomes, workflows, and domains.Use when: Use before transformation, AI adoption, or cross-functional redesign.02Decision rights matrixA record of who can decide, approve, consult, and escalate.Use when: Use when decisions bounce across teams or committees.
03Incentive alignment checklistA test for whether rewards reinforce enterprise outcomes.Use when: Use during operating model and performance management reviews.

AI implication

What changes when AI enters this layer

What changes

AI separates activity from accountability. Models can generate, recommend, summarize, and act, but they cannot own the outcome.

Primary risk

AI use cases create work, outputs, and risk faster than humans can clarify ownership.

Before scaling

Every AI workflow needs a business owner, risk owner, decision owner, adoption owner, and escalation path.

Human accountability

Humans remain accountable for outcomes, exception handling, model use, and business impact.

Continue with evidence

Related reading and tools

ArticleData Readiness Is Really an Ownership ProblemWhy trusted data begins with stewardship and accountability.TemplateOwnership mapMap owners across outcomes, decisions, workflows, and risk.

Layer connections

Read the dependency in both directions

Ownership determines who can make decisions, carry accountability, and govern outcomes across the rest of the operating model.

The foundation

Ownership starts the chain

The remaining six layers depend on a named human owner who can carry accountability.

Current layer

Ownership

Identity & Incentives

Ownership determines who can make decisions, carry accountability, and govern outcomes across the rest of the operating model.

Downstream condition

Decisions

Decision Architecture

Decisions turns this layer's output into the next operating condition.

Open layer

Advanced practitioner material

Choose a topic for the task in front of you

The detailed material remains available, but it is grouped by what you need to do instead of presented as one undifferentiated list.

Start hereThe Ownership SpectrumDefine whether AI drafts, recommends, executes under supervision, or only informs human judgment.
Understand the conditionBuild the minimum shared language needed to see this layer clearly. 1 topic.
Diagnose the conditionRecognize where the layer is weak, inconsistent, or creating downstream drag. 1 topic.
Design an improvementChoose structures and working practices that change how the layer operates. 4 topics.
Govern and measureMake the improvement observable, reviewable, and durable over time. 1 topic.

Apply ownership

Improve one condition in one consequential workflow.

Do not launch a broad transformation program from this page. Use the layer to make one hidden constraint visible, owned, and reviewable.

Your first working session

  1. 01

    Ask

    Who owns the outcome?

  2. 02

    Build

    Use the function ownership map to make the condition explicit.

  3. 03

    Review

    Track ownership clarity score and inspect the result after 30 days.

Run the diagnosticReturn to all layers