Define the Performance Gap in Observable Terms
A gap statement gives the rest of the diagnosis a real target. State what the person is or is not doing in terms a peer could verify, put a number on the current level and the standard, and back it with evidence anyone could look up. Keep any assumed cause out so the diagnosis stays open. Written clearly enough to reuse, it becomes a shared standard, and the rest of the diagnosis gets easier to check.
Proficiency Level
This is a preview of how skill assessment works in Admire
Measurable Behaviors
Behaviors are optimized to be directly observable for evidence-based skill tracking.
Cite specific evidence rather than impressions
Points to concrete instances, records, or output, such as a dated example or a dashboard figure, that someone else could check independently.
Quantify the gap between current and expected performance
States the current level against the named standard in numbers or frequency, since without the standard there is no gap, only an opinion.
Separate the performance gap from its assumed cause
Strips out any explanation that would pre-decide the diagnosis and states only the observable fact.
State the performance gap as a specific behavior, not a personality trait
Describes what the person is or is not doing in observable terms a peer could spot, not a trait word like careless.
Write gap statements the team reuses as a shared standard
Writes gaps clearly enough to apply without rewriting and files them in one consistent current-level-against-standard format.
This is a preview of how behavior tracking works in Admire
What Mastery of Gap Definition Looks Like
A mastered gap statement names an observable behavior, carries a number for both the current level and the standard, and cites evidence someone else could pull. It folds in no cause, and it is written well enough that another manager could reuse the wording without a rewrite.