Resile
Resilience after setbacks in deal and pod scenes
O*NET Resilience is recovery after setbacks. GIS scores observable recovery moves, not optimism self-talk.
Resilience shows up in the next choice after a miss, not in how positive the rep sounds.
What it is
Resilience uses library ID resilience in Drive and Resilience with resilience core category proxy.
Why it matters in enablement
Setbacks are constant in quota and pod life. Enablement needs recovery behaviour evidence, not trait labels.
How we measure
Rubrics on post-miss beats reward ownership, adjusted plan, and appropriate tone without deflection.
Deal craft scene
Deal IQ debrief and stall recovery beats score rep recovery after lost momentum on a thread.
Team craft scene
Team IQ spill and retro beats score bounce back with peer-visible ownership.
Practice in simulation
Use resilience focus on Team IQ spill episode and Deal IQ retrospective beat with rematch.
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.
- Positive spin without owning the miss
- Immediate re-push without reflecting what failed
- Blame shift after spill compose beat
- Withdrawal from retro instead of repair attempt
- Recovery talk to manager without changed next step
FAQ
- How is resilience different from optimism?
- We score recovery behaviours after a miss, not positive self-talk.
- Can resilience co-occur with accountability?
- Yes on beats where owning the miss is part of recovery rubric.
- Is it a common focus pick?
- Yes after visible miss patterns on dossier week over week.