Perfectionist
Attention to Detail auf Exact-Work-Beats
O*NET Attention to Detail ist exaktes, genaues Arbeiten. GIS bewertet faktische Präzision auf getaggten Beats, kein Perfektionismus um des Perfektionismus willen.
Detail, das bewertet wird, verhindert Spill. Detail-Mismatch bremst einen Beat, der Speed und Loop-in brauchte.
Was es ist
Attention to detail uses library ID attention_to_detail in Drive and Resilience with preparation proxy.
Warum es im Enablement zählt
CRM hygiene and handoff accuracy affect buyer trust and peer load. Wrong-tool detail fixation shows in sim before live damage.
Wie wir messen
Rubrics on precision-tagged beats reward accurate facts, complete handoffs, and appropriate scope of detail.
Deal-Craft-Szene
Deal IQ preparation and mutual plan beats score accurate stakeholder and commercial details.
Team-Craft-Szene
Team IQ handoff compose beats score complete context without blame noise.
Üben in der Simulation
Pair attention_to_detail focus with handoff compose rematch and Deal IQ prep beat.
Wrong-Tool-Momente
Sinkt die situative Passung, markieren Rubriken Mismatch-Risiko. Das sind typische Beats, in denen diese Kompetenz das falsche Werkzeug für die Szene ist.
- 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.