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 uses library ID decisive_judgment in Judgment and Leadership with process_discipline proxy.
Warum es im Enablement zählt
Executive rooms and manager 1:1s punish silent tradeoffs. Enablement scores explicit judgment moves.
Wie wir messen
Rubrics on judgment-tagged beats reward explicit cost benefit framing aligned to scene facts.
Deal-Craft-Szene
Deal IQ executive and walk-away beats score judgment under committee and commercial pressure.
Team-Craft-Szene
Team IQ managing-up beats score judgment on priority tradeoffs with manager.
Üben in der Simulation
Use decisive_judgment focus on Deal IQ executive altitude and Team IQ 1:1 priority 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.
- 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.