Product & Dashboard Training

Large accounts adopted a product whose feature set had grown faster than anyone's ability to explain it. Staff needed a single training artifact that covered everything, in an order that matched how a real user moves through the interface.

Feature documentation was organized by internal structure, which meant training sessions jumped between unrelated areas and staff left with a list rather than a mental model. Adoption of the more valuable features was low, not because people disliked them but because nobody had ever put them in context.

• Start with anatomy. Show the whole map before touring any single room.
• Describe every feature twice: what it is, and why anyone should care. The second half is the part that gets remembered.
• Order by user journey, not by menu structure. Quick actions and check-in come before profile settings because that is the real sequence.
• Name the constraints honestly. Fields that cannot be edited in the app should be flagged, or the training creates its own support tickets.
• Keep each feature to one page so the deck doubles as a reference after the session.

1. 01

   A product anatomy map

   The full feature set grouped into progress, rewards, quick actions, identity, and profile, presented as one page before anything was explained in detail.

2. 02

   A what it is and benefits pattern

   A consistent two-part treatment for every feature, so the training explained value rather than mechanics alone.

3. 03

   Journey-ordered sequencing

   Features taught in the order a member meets them, starting with entry and check-in and ending with settings and support.

4. 04

   Known-limitation callouts

   Explicit notes where data is owned by an upstream system, including what a customer must do instead.

• Gave account teams one artifact that worked as both a live session and a later reference.
• Raised awareness of the features that drove engagement rather than the ones that were easiest to demo.
• Established the anatomy-first pattern I still use when introducing any system to a team.

The best decision was refusing to teach features in menu order. The weakest part was that the training assumed a single audience. Managers and front line staff needed different depths, and one deck for both meant each got a version slightly wrong for them.

• Enablement & Training
  Staff & Member Enablement Guides →

  Step-by-step onboarding and account setup guides written for front line staff during large multi-location rollouts, including migrations between billing systems.