← Back to home
THE WORK, NOT THE HYPE

Product Management with AI.

Explore how AI changes your work — and what to learn next.

A practical guide to
the work ahead
Product ManagementProduct DocumentationGrowing Practice

Product Documentation

Draft release notes and user guidance.

The workflow, side by side

Traditional workflow

Before generative AI assistance
  1. 1

    Clarify the goal using approved behavior and release decisions

  2. 2

    Identify audience questions

  3. 3

    Draft guidance from verified behavior

  4. 4

    Review and test examples

  5. 5

    Check the result against the agreed criteria

  6. 6

    Communicate the outcome and record the decision

AI-assisted workflow

AI contributes. You guide and verify.
  1. 1

    Define the goal, constraints, and permitted information

  2. 2

    Provide relevant, sanitized context from approved behavior and release decisions

  3. 3

    Ask AI to draft release notes and user guidance

    AI + YOU
  4. 4

    Inspect suggestions against original evidence and domain rules

  5. 5

    Revise the output and independently validate the result

    YOU
  6. 6

    A responsible professional approves and communicates the outcome

HUMAN CHECKPOINT

Does this describe the shipped product and its actual limitations?

Your judgment matters

The shift: Evaluating AI-generated themes while preserving customer context. Foundational skills still matter.

Build the skills behind the work.

A practical learning path for Product Management.

GO A LITTLE DEEPEROpen only what you need
What changes — and what doesn’tSkills & responsibilities
AI HELPS WITH
DraftSummarize

Draft release notes and user guidance. The output is a starting point to inspect, not a decision to accept automatically.

STILL YOUR RESPONSIBILITY

Preserve customer context, weigh tradeoffs, choose priorities, and own decisions.

Skills to develop

FoundationsCustomer research, product strategy, experimentation, and analytics.

AI collaborationProviding task-specific context and requesting explicit assumptions.

VerificationChecking approved behavior and release decisions against independent evidence.

Professional skillsCommunicating tradeoffs and taking responsibility.

Where AI can go wrong3 things to check

A plausible but wrong answer

Generated copy may promise an unavailable feature. It can fail the underlying goal even when it sounds convincing.

Your check

Check shipped behavior and correct the promise before publication.

Missing or invented context

AI may fill gaps with unsupported assumptions, which can send the work in the wrong direction.

Your check

Trace claims to original evidence and ask the relevant person about unknowns.

Information shared in the wrong place

Sensitive records or code can cross confidentiality boundaries if supplied to an unsuitable tool.

Your check

Use approved tools, share the minimum context needed, and follow your organization’s rules.

Try a quick exerciseA practical scenario

Release notes say exports include deleted records, but the release excludes them.

What is the most important next step in this scenario?
Sources & contextEvidence behind this example