Skip to content

Tutorial content strategy

Why this exists

Tutorials support user onboarding and the docs site. The goal is reliable, product-true how-to content that helps people learn WorkWingman features without support friction.

Why an in-house recorder

We built an in-app tutorial recorder (WING-210 / WING-211) instead of relying only on external screen-capture tooling for product walkthroughs.

Business reasons (from product direction; expand with metrics only when measured):

  • Product fidelity — Capture the real app flow users will see.
  • Repeatability — Re-record when features change; the RECIPE (prerequisites → record → land output → ship) is the operational asset.
  • Onboarding + docs alignment — One content path can feed both first-run learning and documentation.
  • Roadmap control — WING-212 will swap/migrate tutorials to video format, so production stays inside a controlled pipeline rather than ad-hoc external video only.

TODO(verify): Cost, time-to-publish, or support-ticket impact of in-house recording vs external-only production — measure before claiming ROI.

Onboarding value

Guided tutorials reduce time-to-first-success by showing feature use in context. They also give docs a living walkthrough layer alongside written pages.

TODO(verify): Onboarding completion, activation, or support deflection metrics tied to tutorial usage.

Content lifecycle (strategy view)

  1. Decide which feature needs a guided tutorial.
  2. Record with the in-app recorder (WING-210/211).
  3. Land the output in the agreed publish path — TODO(verify) exact storage and packaging.
  4. Ship to onboarding and the docs site.
  5. Migrate to video when WING-212 is ready (pending as of 2026-07-30).
  6. Refresh when the product UI or workflow changes.

What “done” looks like for a tutorial

  • A guided tutorial exists for the feature (current format from the landed recorder).
  • Users can find it via onboarding and/or the docs site.
  • Ownership and refresh cadence are clear — TODO(verify) named owners and SLAs.

Open product decisions

  • Priority order of features to tutorialize — TODO(verify)
  • Success metrics for tutorial-assisted onboarding — TODO(verify)
  • Cutover plan and user-facing change when WING-212 video migration ships — TODO(verify)
Ticket Business meaning
WING-210 / WING-211 In-house recorder capability landed
WING-212 Video format swap + migration (pending, 2026-07-30)