Enablement Curriculum Timing Audit: Skill-to-Deal-Stage Map
A structured template that maps every competency in your enablement programme to the deal-stage moment when it first becomes testable in live pipeline, exposing gaps between when skills are taught and when reps actually need them. Includes a pre-built late-breaking skills list, recommended teach and reinforcement windows, and a 90-day competency check protocol for managers.
How to use it
Pull your current enablement calendar and list every skill or module taught. Work through the Skill-to-Stage Map table, filling in when each skill is currently taught versus when it first appears in live deals, then use the gap-flag column to surface misalignments. Run the 90-Day Competency Check on a sample of Stage 3+ deals monthly to detect whether skills taught during ramp are still present, degrading, or absent.
What's inside
- Skill-to-Deal-Stage Map table with columns for competency, first testable deal stage, current teach timing, and gap flag
- Pre-built list of 12 late-breaking skills with recommended first-teach and first-reinforcement windows in months and pipeline stage
- Definitions for each gap-flag status (Too Early, Aligned, Too Late, Never Taught)
- Scoring guide for prioritising which misalignments to fix first
- 90-Day Competency Check protocol with structured manager questions for Stage 3+ deal reviews
- Skill status classification system (Present, Decaying, Absent) with observable deal evidence for each
- Notes on when this audit is not the right tool and what to do instead
- Blank audit template rows for adding organisation-specific competencies
What this is for
Most enablement calendars are built around ramp weeks, not deal-stage triggers. Skills get taught in sequence because it is administratively tidy, not because the rep has pipeline at the stage where the skill becomes real. The result is two failure modes:
Too early. The rep learns multi-threading in week four of ramp. They have no stalled deal to thread. The skill evaporates.
Too late. Champion testing gets a half-day in month six. By then, half the team has already lost deals to weak champions and formed bad habits to compensate.
This template gives you an instrument to find both failure modes and a protocol to detect skill degradation after launch.
Part 1: Skill-to-Deal-Stage Map
How to complete this table
- List every competency or module in your current programme in the Competency column.
- Fill in the Stage When First Testable column using the pipeline stage definitions your team actually uses (example stages are shown; adapt them).
- Fill in Currently Taught At from your calendar.
- Set the Gap Flag using the definitions below the table.
- Use the Priority Score to sequence fixes.
Pipeline stage reference (adapt to your CRM)
| Stage | Label | What is happening in the deal |
|---|---|---|
| S1 | Qualified | ICP confirmed, pain identified, discovery started |
| S2 | Active Discovery | Full discovery running, stakeholders being mapped |
| S3 | Solution Presented | Demo or proposal delivered, evaluation underway |
| S4 | Validation | Legal, security, procurement, references engaged |
| S5 | Negotiation | Commercial terms live |
| S6 | Closed/Won or Lost |
Gap flag definitions
| Flag | Meaning |
|---|---|
| Too Early | Skill taught more than one full stage before it is testable. Retention risk is high. |
| Aligned | Skill taught within one stage of when it is first testable. |
| Too Late | Skill first testable at a stage the rep has already reached before the training arrives. |
| Never Taught | No training exists for this skill at any point in the programme. |
Priority score: how to sequence fixes
Score each flagged row 1-3 on each dimension, then sum.
| Dimension | 1 | 2 | 3 |
|---|---|---|---|
| Deal-loss evidence | No data linking skill gap to losses | Anecdotal manager reports | Win/loss data or CRM stage data confirms |
| Frequency of stage reached | Fewer than 20% of deals reach this stage | 20-60% | Over 60% |
| Reteach difficulty | Skill can be drilled in a single call review | Requires structured practice | Requires live deal experience to develop |
Score 7-9: fix in current quarter. Score 4-6: fix in next quarter. Score 3: monitor.
The map table
Complete one row per competency. Blank rows at the bottom for your additions.
| # | Competency | Stage When First Testable | Currently Taught At | Gap Flag | Priority Score |
|---|---|---|---|---|---|
| 1 | ICP qualification | S1 | |||
| 2 | Discovery questioning | S1-S2 | |||
| 3 | Pain quantification | S2 | |||
| 4 | Stakeholder mapping | S2 | |||
| 5 | Demo or presentation structure | S3 | |||
| 6 | Objection handling (evaluation-stage) | S3 | |||
| 7 | Champion identification | S2 | |||
| 8 | Champion testing | S3-S4 | |||
| 9 | Multi-threading stalled deals | S3-S4 | |||
| 10 | Procurement and legal navigation | S4 | |||
| 11 | Reference management | S4 | |||
| 12 | Late-stage disqualification | S4 | |||
| 13 | Negotiation under pressure | S5 | |||
| 14 | Concession sequencing | S5 | |||
| 15 | Mutual close plan management | S3-S5 | |||
| 16 | |||||
| 17 | |||||
| 18 |
Part 2: Late-Breaking Skills Reference List
These twelve skills share a common property: they are almost universally taught too early or never reinforced at the stage where they break deals. Use this list to cross-check your map or to pre-populate it.
| Skill | First Testable Stage | Recommended First Teach | Recommended First Reinforcement | Why it breaks when taught too early |
|---|---|---|---|---|
| Champion testing | S3 | Month 3-4, ahead of first S3 deals | Month 5-6, on live S3 pipeline | Rep has no champion to test. Concept stays theoretical. |
| Multi-threading stalled deals | S3-S4 | Month 4, framed around stuck deals | Month 6, triggered when a deal stalls at S3 for 3+ weeks | No stalled deals exist in ramp. Skill is forgotten before it is needed. |
| Late-stage disqualification | S4 | Month 5-6 | Quarterly, in deal reviews | Emotionally and commercially difficult. Needs live deal context to land. |
| Negotiation under pressure | S5 | Month 6 minimum | At first live negotiation, with debrief within 48 hours | Taught in role-play, applied months later under real pressure with no recall. |
| Concession sequencing | S5 | Month 6, paired with negotiation module | After first negotiation debrief | Same as above. Abstract sequencing frameworks do not survive first real negotiation without reinforcement. |
| Procurement navigation | S4 | Month 4-5 | When first deal enters procurement | Low frequency in early pipeline means no hooks for learning. |
| Legal and security review management | S4 | Month 4-5 | First deal entering legal review | Same low-frequency problem. |
| Mutual close plan construction | S3 | Month 3 | Month 4-5, on live S3 deals | If taught at ramp, rep has no deal to attach it to. |
| Reference management | S4 | Month 4 | First time a reference is requested | Reps improvise badly without a process. Often never formally taught. |
| Stakeholder mapping (full political map) | S2-S3 | Month 2 | Month 3, on a live multi-stakeholder deal | Basic version can be taught early. Full political mapping needs real deals. |
| Objection reframing at S3+ | S3 | Month 3 | Monthly call reviews at S3+ | Early objection handling training focuses on S1-S2 patterns. S3 objections are structurally different. |
| Competitive displacement (mid-cycle) | S3-S4 | Month 4 | When first competitive deal reaches S3 | Taught generically in ramp. Needs live competitive deal to be useful. |
Part 3: 90-Day Competency Check Protocol
Purpose
This is not a coaching session or a performance review. It is a signal check. You are trying to answer one question: is this skill present, decaying, or absent in live pipeline right now?
Run this protocol monthly on a rolling sample of three to five Stage 3+ deals per rep. It takes fifteen to twenty minutes per rep if you have reviewed the deals in advance.
Skill status definitions
| Status | What it looks like in the deal |
|---|---|
| Present | Rep can describe specific actions taken and their result. CRM notes reflect the skill. Deal progression is consistent with skill being applied. |
| Decaying | Rep describes the right idea but cannot name specific actions. Notes are vague. Deal has not progressed in ways the skill should drive. |
| Absent | Rep has no answer, gives a generic response, or describes actions inconsistent with the skill. Deal shows characteristic failure pattern for missing this skill. |
The protocol: questions to run per deal
Pick two to four skills relevant to the deal's current stage. Ask the questions below. Record the status against each skill.
Champion testing
- "Who is your champion on this deal? What have you done in the last two weeks to test whether they are real?"
- Listen for: specific actions (asked champion to arrange an exec meeting, asked for internal data they would need to pull, tested their willingness to push back on procurement). Generic answers ("they seem engaged") indicate Decaying or Absent.
Multi-threading
- "Who else in the account is active in this deal beyond your main contact? How did you get to them?"
- Listen for: named individuals with a stated reason for engaging them. "I haven't spoken to anyone else" at S4 is Absent.
Late-stage disqualification
- "What would have to be true for you to remove this deal from the forecast?"
- Listen for: a specific, concrete threshold. "Nothing, I think it's solid" is Decaying. No answer is Absent.
Negotiation preparation (for S5 deals)
- "What is your walk-away position on price? What is your first concession if they push?"
- Listen for: a specific number and a named concession. Vague answers indicate Decaying or Absent.
Mutual close plan
- "Can you walk me through the agreed next steps with the customer, with dates and owners on their side?"
- Listen for: customer-owned steps with dates. Rep-only steps with vague customer commitments indicate Decaying.
Stakeholder mapping
- "Who is against this deal inside the account? How do you know?"
- Listen for: a named individual and the evidence for their position. "I don't think anyone is against it" at S3+ is Absent.
Recording the results
Use this log. Run it monthly. After three months you will have a baseline degradation rate per skill and per rep cohort.
| Rep | Deal | Stage | Skill Checked | Status | Manager Note | Date |
|---|---|---|---|---|---|---|
What to do with the data
| Pattern | Action |
|---|---|
| One rep, multiple Absent or Decaying skills | One-to-one coaching plan. Check whether the rep attended the original training. |
| Multiple reps, same skill Decaying | Skill was taught too early or not reinforced. Move the teach date or add a reinforcement trigger. |
| Multiple reps, same skill Absent | Skill may never have been covered properly. Return to the map in Part 1 and re-audit that row. |
| Skill present across all reps | No action needed. Redirect coaching time. |
When not to use this template
- If your team has fewer than three reps, a formal audit is overhead you do not need. Run the competency check questions informally in deal reviews instead.
- If your pipeline is too thin to have multiple deals at S3+ for most reps, wait until pipeline density justifies the protocol. Running it on a single deal per rep produces noise, not signal.
- If your deal cycle is under thirty days, stage-based timing collapses. Run skill checks by week of cycle instead.
The thinking behind this
Your Enablement Programme Was Designed for the Room, Not for the Rep Six Months Later is the argument this resource puts to work.