Comforter
Empathetic support when others need concern
O*NET Concern for Others is sensitivity to needs and helpful understanding. GIS scores concern moves on tagged beats without collapsing into generic niceness.
Support that scores shows up as named concern plus a helpful next move, not as vague sympathy.
What it is
Empathetic support uses library ID empathetic_support in Influence and Communication with stakeholder empathy proxy across sim tracks.
Why it matters in enablement
Buyers and peers both signal stress before they signal no. Enablement needs concern scored as behaviour, not trait empathy.
How we measure
Rubrics on concern-tagged beats reward named validation plus appropriate help or boundary.
Deal craft scene
Deal IQ beats score stakeholder concern when buyers express risk, overload, or internal politics stress.
Team craft scene
Team IQ retro and 1:1 beats score helpful understanding after peer frustration without removing ownership.
Practice in simulation
Use empathetic_support focus on Team IQ Ep3 retro and Deal IQ stakeholder stress dialogue 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.
- Sympathy without a workable offer when the beat tagged action
- Over-support that removes accountability from the rep
- Concern talk that skips asking what the person needs
- Buyer empathy that ignores peer spill impact
- Support offered instead of required loop-in to manager
FAQ
- How is this different from active listening?
- Listening scores attention and understanding. Empathetic support scores helpful concern moves after understanding.
- Can concern score as wrong-tool?
- Yes when the beat required accountability or direct loop-in instead of comfort.
- Is it a focus skill for ICs?
- Yes. Any library ID can be in the manager three to five pick set.