Resolver
Decision Making und Problem Solving in der Szene
O*NET Making Decisions and Solving Problems analysiert Information für die beste Lösung. GIS bewertet Choice-Qualität auf getaggten Beats mit sichtbaren Tradeoffs.
Entscheidungsqualität ist die Choice, die der Rep macht, wenn Optionen on screen sind, keine nachträgliche Story.
Was es ist
Decision making uses library ID decision_making in Judgment and Leadership with process_discipline proxy.
Warum es im Enablement zählt
Bad qualification decisions waste pipeline. Bad pod decisions erode trust. Same rubric spine, different scene tags.
Wie wir messen
Rubrics on decision-tagged beats reward evidence use, tradeoff naming, and fit to qualification or team values.
Deal-Craft-Szene
Deal IQ qualification and next-step beats score solution choice against visible MEDDPICC gaps.
Team-Craft-Szene
Team IQ 1:1 and retro beats score team process decisions after validation.
Üben in der Simulation
Assign decision_making on Deal IQ qualification fork and Team IQ retro decision 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.
- Fast close on beat that tagged more discovery
- Decision that ignores economic buyer signal in scene
- Pod decision that reassigns without peer input tag
- Analysis loop without choosing when beat timed out
- Copy prior deal decision without scene specific facts
FAQ
- How is this different from decisive judgment?
- Decision making emphasizes problem solution choice. Decisive judgment emphasizes cost benefit of actions. Related IDs, separate rubrics.
- Do LLMs pick the decision?
- No. Rep choices on tagged beats drive deterministic scores.
- Can walk-away score here?
- Walk-away beats may tag decisive_judgment or decision_making depending on rubric design.