Work & Theory logoWork & Theory
Back to decision paths

Executive decision path

Persistent Performance Drift

A decision path for leaders facing recurring misses, inconsistent execution, or accountability conversations that have become repetitive and personal.

Start the free Health Check

Decision thread

Move from the observable situation to one evidence-based decision before changing people, process, or structure.

View the 50–60 minute working-session guide

  1. 01

    Situation

    A decision path for leaders facing recurring misses, inconsistent execution, or accountability conversations that have become repetitive and personal.

  2. 02

    First leadership question

    What specific outcome is drifting, and what is its operational impact?

    Decision to leave with

    Test whether the gap may involve role design, capability, capacity, context, expectations, or a formal process outside this session.

  3. 03

    Evidence to bring

    • The role purpose, expected outcomes, authority, and available feedback agreements.
    • Observable work evidence from two recent examples, including relevant conditions and support.

  4. 04

    Working output

    A provisional Performance Contract review: the outcome gap, conditions to test, support or design action, formal-process boundary, owner, and review date.

  5. 05

    Working artifact

    Use a simple document or meeting note to capture the owner, evidence, decision, and next review. Keep the record close to the work it is meant to improve.

Use this path when

The organizational moment needs a system view.

  • A critical outcome keeps missing despite more attention, urgency, or corrective conversations.
  • Leaders suspect a performance problem but cannot separate individual, role, and organizational conditions.
  • The same failure appears across more than one team or operating cycle.

Executive working session

First working session

55 minutes

Use this as a structured leadership working session to test an organizational hypothesis. It is not legal, HR, or performance-management advice.

Session agenda

  1. 01

    Brief · 5 min

    Describe the persistent performance gap as an observable work outcome, not a conclusion about a person.

  2. 02

    Evidence review · 15 min

    Review expected outcomes, actual evidence, authority, workload, support, feedback, and two relevant operating examples.

  3. 03

    Decision framing · 15 min

    Test whether the gap may involve role design, capability, capacity, context, expectations, or a formal process outside this session.

  4. 04

    Working output · 15 min

    Set a bounded performance-contract hypothesis and identify what must be clarified or referred before consequential action.

  5. 05

    Owner and date · 5 min

    Name the next operating action, any needed formal-process check, and a date to review evidence.

Evidence packet

  • The role purpose, expected outcomes, authority, and available feedback agreements.
  • Observable work evidence from two recent examples, including relevant conditions and support.
  • Current workload, competing priorities, handoffs, information, and decision constraints.
  • Existing policy or formal-process requirements that may apply before consequential employment action.

Working output

A provisional Performance Contract review: the outcome gap, conditions to test, support or design action, formal-process boundary, owner, and review date.

Keep the output close to the work

Write the agreement in a document or meeting note your team already uses. Name an owner, the evidence to review, and when you will return to it.

What leaders see / what may be underneath

Visible symptoms are useful evidence—not conclusions.

Common visible symptom
Likely organizational cause to test

Leaders repeat the target but the result does not improve.

The outcome, authority, workflow, capacity, or feedback conditions may be insufficiently clear.

Accountability conversations become defensive or personal.

The group has not made the work, evidence, interfaces, and decision rights explicit.

A capable person succeeds only through exceptional effort.

The role or surrounding system is relying on heroics rather than a workable design.

The organization alternates between tolerance and abrupt escalation.

Expectations, feedback cadence, and consequences are not operating as an explicit agreement.

The diagnostic lens

Read the moment across the organization.

Direction

Confirm that the outcome and priorities are still coherent and not competing silently.

Design

Review workflow, dependencies, information, and decision authority around the repeated miss.

Talent

Assess required capability, capacity, commitment, and context without collapsing them into one judgment.

Performance

Make purpose, outcomes, expectations, feedback, development, and consequences explicit.

Culture

Examine whether leaders reward candor, early escalation, learning, and responsible ownership.

Leadership questions

Questions that create a more useful working conversation.

  1. 01What specific outcome is drifting, and what is its operational impact?
  2. 02Where in the workflow does the miss first become visible?
  3. 03What authority and information did the accountable role have?
  4. 04What capability and capacity did the role require?
  5. 05What feedback was available early enough to change the work?
  6. 06Which dependency or decision boundary keeps recurring?
  7. 07What evidence points to an individual issue, a design issue, or both?
  8. 08What would a fair and explicit next agreement look like?

A practical 30-day sequence

Create evidence before committing to a larger change.

Days 1–7

Reconstruct the pattern

Select a repeated miss and trace the outcome, timing, decisions, dependencies, and evidence from the most recent cycle.

Days 8–14

Separate conditions

Assess role clarity, authority, capacity, capability, commitment, and context without assuming one explanation.

Days 15–21

Make one agreement explicit

Document the outcome, decision boundary, feedback, support, and review point for the role or interface most connected to the miss.

Days 22–30

Review what changes

Use the next operating cycle to review the evidence and decide whether the condition calls for further design, development, or performance action.

Common errors to avoid

Avoid mistaking movement for progress.

  • Using organizational ambiguity to avoid a necessary performance conversation.
  • Treating a people decision as sufficient when the same drift appears across the system.
  • Adding metrics without clarifying who can act on them and how feedback changes the work.
  • Confusing more pressure with clearer accountability.

Selected Knowledge Bank resources

Continue the diagnosis without adding noise.

Performance / Article

Persistent Performance Drift Needs Operating Evidence, Not a Stronger Message

When a result keeps missing, leaders need to separate individual accountability from the conditions around the work. More urgency may intensify effort without clarifying the constraint.

Read resource

Performance / Article

Performance Problems Are Often Design Problems

Before treating a performance concern as an individual failure, test whether the role has clear outcomes, authority, conditions, and feedback.

Read resource

Performance / Template

What Should Actually Be in a Performance Contract?

A usable Performance Contract replaces vague role descriptions with an explicit agreement about the work, authority, evidence, and support required.

Read resource

Practice / Tool

Leadership-Team Accountability Conversation Guide

A practical conversation guide for resolving a recurring accountability problem without turning it into a debate about personalities.

Read resource
    Persistent Performance Drift | Work & Theory Decision Path