Home The 61 Specialists & 8 Departments Product: roles and what it does

Product: roles and what it does

Last updated on May 30, 2026

Discovery that stays close to users. Releases that ship clean. Docs that pull their weight.

The team (head: PM Lead)

  • PM Lead
  • Docs & Technical Writer
  • Product Analyst
  • Release Manager
  • User Research
  • UX Designer
  • Voice of Customer

What this department actually does

  • Owns strategy and the roadmap. Quarterly themes set, the roadmap maintained, prioritization defended. The product has a direction, not a backlog of loudest requests.
  • Keeps discovery close to users. Studies planned and run, interviews synthesized, feedback from support and sales aggregated into prioritized input the team can act on.
  • Measures what shipped. Event taxonomy owned, adoption and retention tracked per feature. The PM decides on data, and dead features get caught early.
  • Ships clean and documents it. Release calendar and feature flags managed, UI reviewed against the design system, docs and changelog written so nothing ships into a vacuum.

Example missions in your own words

You do not assign these tasks by hand. You type one sentence and the department scopes it. A few realistic examples:

  • "I want to hear from five users a week without scheduling it myself."
    A running interview cadence with recruiting, scripts, and synthesis. Themes rolled into product input so the roadmap stays close to real users.
  • "We keep shipping silently. Every release needs notes."
    A release-notes pipeline where every ship is paired with notes and a one-line changelog. Customers and the team know what changed.
  • "Tell me whether people actually use the feature we just shipped."
    Event tracking in place, the activation funnel and retention curves measured weekly, adoption of the new feature reported instead of assumed.
  • "Our docs are out of date and support is paying for it."
    The top 10 features documented and kept current, the changelog written. Tickets-per-feature tracked so you can see the support load drop.

Every artifact this department produces runs through the four-step review (builder, QA, reviewer, security) before it reaches you, and any risky move waits at one of the five approval points.