Proactive
Initiative when the scene needs ownership
O*NET Initiative is willingness to take responsibilities and challenges. GIS scores proactive moves that fit alignment tags, not lone wolf heroics.
Initiative that scores loops in the right people before acting.
What it is
Initiative uses library ID initiative in Drive and Resilience with urgency_creation proxy.
Why it matters in enablement
Deals need proactive thread advancement. Pods need proactive fixes that respect peer impact.
How we measure
Rubrics on ownership beats reward proactive next steps with appropriate stakeholder and peer alignment.
Deal craft scene
Deal IQ beats score rep-led thread advancement on qualified opportunities without manager prompt.
Team craft scene
Team IQ spill and managing-up beats score proactive fixes with visible loop-in.
Practice in simulation
Assign initiative with Team IQ managing-up 1:1 and Deal IQ qualified thread advancement.
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.
- Acting on buyer thread without peer handoff notice
- Manager bypass when loop-in early was tagged
- New work accepted without capacity check with pod
- Initiative that reopens resolved retro tension
- Speed celebrated when alignment beat was required first
FAQ
- Can initiative be wrong-tool in team scenes?
- Yes when beats required alignment or listening before action.
- How does it relate to objective setting?
- Initiative scores taking on challenges. Objective setting scores defining goals and strategies. Different IDs.
- Does it score in snapshots?
- Yes on tagged beats in snapshot episodes, not on completion alone.