What post-SKO reinforcement system keeps behavior change from collapsing?

Question

Pulse RevOps · The Machine · Accepted Answer

## Post-SKO Reinforcement Architecture

The **"90-day decay curve"** is real: teams lose **60% of kickoff learning by day 45** without structured reinforcement (Force Management + Bridge Group). Here's the system that prevents backslide.

### The Reinforcement Cadence

**Weeks 1–2: Activation Phase**
- **Daily 10-minute standup** (manager-led): one rep shares how they applied new framework in yesterday's deal
- **Peer war-gaming**: AE pairs practice new objection handles; manager sits in and scores on **3 criteria** (comfort, language alignment, objection coverage)
- **Weekly manager QA call**: enablement audits manager execution; if manager skips, escalate to VP

**Weeks 3–4: Integration Phase**
- Drop daily standups; move to **Monday manager sync** (30 min, pure coaching)
- **Manager coaching scorecard**: track adoption per rep (% of calls using new discovery path, average discovery questions per call)
- **Peer recognition**: every Friday, highlight **3 reps** who nailed the framework; tie to comp if possible

**Weeks 5–8: Sustainability Phase**
- Monthly manager skill share (30 min); one manager teaches others their coaching wins
- **Ramp rep cohort reviews**: SDRs/AEs in ramp get weekly 20-min framework practice (not separate from standard coaching)
- **Sales ops dashboard**: expose adoption metrics real-time; reps see their own % of calls using new process

### The Manager Accountability Lock

This only works if **managers own execution**. Deployment checklist:

1. **Manager kickoff (pre-event)**: 2-hour deep dive on new framework + how to coach it in real deals
2. **Manager scorecard**: each manager's name tied to **% adoption per rep** (public; visible to peers)
3. **Sales ops audit**: weekly 5-min pulse: "Did you coach [framework] this week?"
4. **VP spot-check**: 2x per month, VP sits in on a manager's coaching call; gives feedback

### The Collapse Trigger

If adoption dips below **70% by day 35**, trigger:
- **Rapid re-engagement**: 30-min re-teach for that segment
- **Peer pressure**: call out low adopters by name in manager meeting (not punitive, but visible)
- **Incentive nudge**: if comp has flexibility, temporarily boost adoption-based acceleration

```mermaid
stateDiagram-v2
    [*] --> Week1Activation: Kickoff Ends
    Week1Activation --> Week3Integration: Day 15 Review
    Week3Integration --> Week5Sustain: Day 30 Check
    Week5Sustain --> Day45Checkpoint{Adoption >70%?}
    Day45Checkpoint -->|Yes| Locked: Behavior Change Locked
    Day45Checkpoint -->|No| ReEngage: Rapid Re-Teach
    ReEngage --> Week5Sustain
    Locked --> [*]
```

TAGS: post-kickoff-coaching,reinforcement-cadence,adoption-tracking,manager-accountability,behavior-change

What post-SKO reinforcement system keeps behavior change from collapsing?

Post-SKO Reinforcement Architecture

The Reinforcement Cadence

The Manager Accountability Lock

The Collapse Trigger

What does the score mean?