rate-guard · deliverable

Needs Analysis — Rate Guard Enablement

Prepared for: CargoDesk B.V. (fictional) — Product Learning & Enablement By: I Wayan Usada — Learning & Enablement Re: Rate Guard launch — enablement for Support, Sales CSAs and partner resellers Status: fictional case; every figure below is an illustrative premise, not data

1. Situation

CargoDesk releases Rate Guard in 12 days: surcharge protection that locks the fuel component of a quote against spikes above a configurable threshold, from send to expiry (72 h by default). Three audiences meet it on day one:

Support tier-1/2 (about 40 agents): get the tickets the moment something confuses users
Sales CSAs (about 25): demo it to customers; a fumbled demo is remembered
Partner resellers (60+ organisations, self-service): onboard without live training, in four languages

Leadership's request: "a training session before launch."

2. The question behind the request

A webinar reaches the people who attend, once. What launch-week system lets each audience answer its own Rate Guard questions the day the feature ships, and tells us within a week which audience it is failing?

Constraints, as set out in the brief:

Support works 24/6 shifts, so no single session reaches everyone.
Resellers span 9 countries and 4 languages; live delivery does not scale.
Premise: after the previous feature launch, about two-thirds of tickets came from five recurring questions. If that holds, most questions are predictable and can be answered before they are asked.

3. What training cannot fix

Missing product guards. Agents and customers both get caught by "edited quotes lose protection". A banner on the quote revision screen ("this ends Rate Guard protection; re-arm before sending") prevents more tickets than any article.
One language. The KB master is English. Partner questions in German and Dutch will arrive anyway; FAQ and tour captions need translation, and the gap log needs to be read by someone who can triage them.
Escalations that bounce. Tier-2 rejects escalations without IDs and evidence. A required-fields form in the ticketing tool does more than reminding agents to attach.

4. Solution: an enablement kit matched to each audience

Audience	Asset	What it practises	How it is checked
Everyone	`02-kb-bundle` — searchable articles + launch FAQ, gap radar	finding the answer before asking	gap radar: zero-result searches per week
Support (and CSAs, partners)	`03-troubleshoot-flow` — launch-week practice queue (9 tickets) + reference tree	search first, route through triage, escalate only with attachments	36-point score per run; leaks per audience
Sales CSAs	`04-inapp-tour` — guided tour + scored demo rehearsal	arm before send; answer three customer questions without over-promising	demo check /4
Leadership	`05-adoption-plan` — launch cadence, proposed KPIs, iterate loop	—	day-7 and day-30 reviews

5. Proposed adoption objective (not measured)

Within 30 days of launch: most active accounts arm at least one quote; Rate Guard tickets fall week on week; CSAs pass the demo check before demoing to customers. Exact targets are for the launch owner to set; this case does not have a baseline.

6. Scope & assumptions

UI in the tour and the triage tree are hand-built mocks; fuel-index linkage simplified for teaching; English master with a localisation checklist in the adoption plan.

Prefer the source? Download the raw markdown.