Sharp
Decisive judgment on cost and benefit beats
O*NET Judgment and Decision Making considers relative costs and benefits of actions. GIS scores when reps name tradeoffs before committing.
Judgment that scores makes the tradeoff visible before the room moves.
What it is
Decisive judgment uses library ID decisive_judgment in Judgment and Leadership with process_discipline proxy.
Why it matters in enablement
Executive rooms and manager 1:1s punish silent tradeoffs. Enablement scores explicit judgment moves.
How we measure
Rubrics on judgment-tagged beats reward explicit cost benefit framing aligned to scene facts.
Deal craft scene
Deal IQ executive and walk-away beats score judgment under committee and commercial pressure.
Team craft scene
Team IQ managing-up beats score judgment on priority tradeoffs with manager.
Practice in simulation
Use decisive_judgment focus on Deal IQ executive altitude and Team IQ 1:1 priority 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.
- 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 beat tagged decide
- Benefit claim without stakeholder specific cost in scene
FAQ
- Is this the same as decision making?
- Related O*NET titles, separate library IDs and rubric emphasis on cost benefit versus solution choice.
- Can judgment be wrong-tool?
- Yes when beat required listening or repair before judgment.
- Does it score in snapshots?
- Yes on tagged judgment beats in snapshot episodes.