Blokken AIFIELD GUIDE
← 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 ManagementRequirements DefinitionGrowing Practice

Requirements Definition

Draft requirements and identify ambiguities.

The workflow, side by side

Traditional workflow

Before generative AI assistance
  1. 1

    Clarify the goal using validated customer needs and technical constraints

  2. 2

    Describe the desired outcome

  3. 3

    Define scope and acceptance criteria

  4. 4

    Review feasibility with the team

  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 validated customer needs and technical constraints

  3. 3

    Ask AI to draft requirements and identify ambiguities

    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

Are the criteria testable and tied to an agreed customer need?

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 requirements and identify ambiguities. 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 validated customer needs and technical constraints against independent evidence.

Professional skillsCommunicating tradeoffs and taking responsibility.

Where AI can go wrong3 things to check

A plausible but wrong answer

AI may add features outside the validated scope. It can fail the underlying goal even when it sounds convincing.

Your check

Separate required recovery behavior from unvalidated scope additions.

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

A password-reset requirement grows into a full identity-platform redesign.

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

These are illustrative workflows, not claims that AI is always better or that every organization works this way. The scenarios and checkpoints are editorial teaching examples.

Reviewed September 2026 · Growing PracticeO*NET — Market Research AnalystsSupports market-research tasks only. Product Management spans several occupational categories.Nielsen Norman Group — Accelerating Research with AIDescribes assistance during research planning and analysis. Broader product-decision examples are editorial extrapolations.How we build these examples