Back to playbooks

Workplace Issue Map

Use when: something at work feels broken, but the failure mode is still fuzzy.
Goal: name the real mechanism, find the decision point, and turn complaint into one concrete ask.

Why this matters

Workplace problems often get described as personality problems or one-off bad experiences.

Sometimes that is true. Often it is not.

The repeatable questions are:

• what rule or workflow is doing the damage?
• who owns it?
• what metric would show it is failing?
• what is the next decision point where it can change?

Common workplace failure modes

Look for the pattern before you pick the ask.

Capacity failure

Too few people, too much work, no slack.

Signals:

• chronic backlog
• rushed handoffs
• burnout
• delay treated as normal

Metric failure

The score is shaping behavior in the wrong direction.

Signals:

• speed beats quality
• workers optimize for the dashboard instead of the job
• edge cases get dumped or hidden

Admin-drag failure

People spend time proving, routing, documenting, or re-entering instead of doing the work.

Signals:

• duplicate forms
• unnecessary approvals
• multi-system entry
• handoff confusion

Accountability failure

People are affected by decisions they cannot inspect, challenge, or appeal.

Signals:

• “that is just what the system says”
• no named owner
• no escalation path
• no records

Training-path failure

The organization still wants senior skill but is shrinking the path that produces it.

Signals:

• junior roles disappear
• onboarding gets thinner
• “learn by doing” work gets automated away
• promotions depend on experience no one can get

Incentive failure

The organization says one thing and rewards another.

Signals:

• safety, quality, or care are praised but not resourced
• managers are rewarded for short-term savings only
• complaints are treated as disloyalty

Quick map

Write one line for each:

• problem:
• who is affected:
• likely failure mode:
• rule, workflow, or metric involved:
• owner:
• next decision point:
• best evidence available:

One-ask examples

• Publish turnaround times by team and staff the slowest handoff.
• Remove one approval step that adds delay without reducing risk.
• Add a named appeal path for scheduling or discipline decisions.
• Keep a junior hiring lane open instead of filling the gap only with automation.
• Review one performance metric that is causing obvious gaming.

Scoreboard

• Failure mode named? (Y/N)
• Owner named? (Y/N)
• Metric named? (Y/N)
• Next decision point identified? (Y/N)
• One ask drafted? (Y/N)

Use with

• Workplace AI Procurement and HR Guardrails

Definition of done

Leave with:

1. one named mechanism
2. one owner
3. one metric
4. one next step

Back to playbooks