Perfectionist
Attention to detail on exact work beats
O*NET Attention to Detail is being exact and accurate in performing work. GIS scores factual precision on tagged beats, not perfectionism for its own sake.
Detail that scores prevents spill. Detail that mismatches slows a beat that needed speed and loop-in.
What it is
Attention to detail uses library ID attention_to_detail in Drive and Resilience with preparation proxy.
Why it matters in enablement
CRM hygiene and handoff accuracy affect buyer trust and peer load. Wrong-tool detail fixation shows in sim before live damage.
How we measure
Rubrics on precision-tagged beats reward accurate facts, complete handoffs, and appropriate scope of detail.
Deal craft scene
Deal IQ preparation and mutual plan beats score accurate stakeholder and commercial details.
Team craft scene
Team IQ handoff compose beats score complete context without blame noise.
Practice in simulation
Pair attention_to_detail focus with handoff compose rematch and Deal IQ prep beat.
Wrong-tool moments
When situational fit drops, rubrics flag mismatch risk. These are common beats where this skill is the wrong tool for the scene.
- Formatting depth when compose beat tagged brief accountability
- Fact checking delay on time critical handoff
- Correcting peer in public retro instead of repair tag
- Missing the big qualification gap while polishing small facts
- Detail pride without verifying stakeholder map accuracy
FAQ
- Is perfectionism rewarded?
- No. Rubrics reward situational fit. Wrong-tool when speed or loop-in was required.
- Does it score in written beats?
- Often on compose beats where factual completeness is the situational fit.
- Can it be focus with time management?
- Yes. Both can be in the three to five pick set with separate fit charts.