Skip to content
Leadership

Performance Diagnosis Playbook

Last Updated: 2026-08-20

Run performance diagnosis as one sequence, from the first gap statement to a closed case. Replace the reflex to fix what a problem looks like with the discipline of finding what actually causes it.

Common Pitfalls with Performance Diagnosis

  • Naming a trait instead of a behavior. 'Lazy' or 'not a fit' cannot be observed, checked, or fixed. State the specific action or count you can see, and put a number on it against the standard.
  • Reaching for training before checking the environment. Training a person who already knows how wastes money and signals the wrong problem. Name at least one environmental factor you ruled out first.
  • Listing causes without naming the one that controls the behavior. Rank the survivors and pick the one whose removal changes the outcome most; treating every factor as equal spreads effort across ones that do not matter.

Frequently Asked Questions

How do you write a performance gap statement?

State what the person is or is not doing as an observable behavior, put the current level against the standard in a number or frequency, and cite one piece of evidence anyone could check. Leave the cause out. 'Submits three of ten reports late against a target of zero' is a gap statement; 'is careless' is not.

In what order should you check for causes?

Check the environment before the individual. Confirm expectations were stated, feedback arrived in time, and tools, time, and process allowed the behavior, before considering a skill or motivation gap. The environmental causes are cheaper and more common, so ruling them out first avoids spending on the least likely cause.

How do you choose between two possible fixes?

Map each fix to the diagnosed cause, price it in money, time, and disruption, and rank the options by how much behavior change each buys for its cost. Run the cheaper environmental fix first and measure before escalating to an expensive individual one. The most familiar option is rarely the highest-leverage one.

Why document a solved performance case?

A documented case turns one solved problem into a path others can follow. When the gap, the controlling cause, the fix, and the result are recorded in a shared format, a colleague facing something similar can reuse the diagnosis instead of starting over. Recurring problems become a library of cases.

Unlock Skill Progression

Coaching Personalized to your current level
Progress Tracking Across every skill area
Mastery Validation Evidence-based, not guesswork
Speak to an Expert