Sharp
Decisive Judgment auf Cost-and-Benefit-Beats
O*NET Judgment and Decision Making wägt relative Kosten und Nutzen ab. GIS bewertet, wann Reps Tradeoffs vor Commit benennen.
Urteil, das bewertet wird, macht den Tradeoff sichtbar, bevor sich der Raum bewegt.
Was es ist
Decisive judgment is explicit weighing of what you gain and what you give up in a high-stakes moment. In GIS, it appears when the rep folds a weak path with clear rationale or prioritizes one decisive next step under committee or manager pressure.
Warum es im Enablement zählt
Executive rooms and manager 1:1s punish silent tradeoffs. Enablement scores explicit judgment moves reps can practice before live rooms where hesitation reads as weak qualification.
Wie wir messen
Rubrics on judgment-tagged beats reward explicit cost benefit framing aligned to scene facts. Mismatch when the beat required listening or repair before judgment.
Beobachtbare Signale
Gut passend
- Folds weak path with clear rationale
- Prioritizes one decisive next step
Mismatch-Risiko
- Waiting for perfect information
- Confusing consensus with clarity
Episoden-Karte
| Team-IQ-Episoden | Fold discipline · Manager priority · Deal desk (Ep9) |
|---|---|
| Deal-IQ-Szenen | Walk-away judgment |
Manager-Coaching
Coach Decisive Judgment on scene type, not personality. Well matched looks like: Folds weak path with clear rationale Mismatch risk looks like: Waiting for perfect information Assign it as a focus skill, rematch the same scene type in Team IQ or Deal IQ, and compare debrief fit before the next live call or pod forum.
Deal-Craft-Szene
Deal IQ executive and walk-away beats score judgment under committee and commercial pressure. Fold discipline scenes reward folding weak paths with rationale buyers and managers can follow.
Team-Craft-Szene
Team IQ managing-up beats score judgment on priority tradeoffs with manager. Manager priority scenes surface whether the rep names what drops when something new enters the queue.
Üben in der Simulation
Use Decisive Judgment focus on Deal IQ executive altitude and Team IQ 1:1 priority beats. Cross-sim dossiers compare judgment fit in buyer rooms versus manager conversations.
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.
- Commit without naming what the rep is giving up
- Walk-away without qualification rationale documented
- Judgment call that ignores values rubric on visible beat
- Delay disguised as analysis when the beat tagged decide
- Benefit claim without stakeholder specific cost in scene
FAQ
- Is this the same as decision making?
- Related O*NET titles, separate rubric emphasis on cost benefit versus solution choice.
- Can judgment be wrong-tool?
- Yes when the beat required listening or repair before judgment.
- Does it score in snapshots?
- Yes on tagged judgment beats in snapshot episodes.