What does an AI product manager do?

Define an AI product manager’s role through outcomes, acceptable errors, human review and value. Use the free Tenhaw Way working method.

An AI product manager decides which outcome an AI feature should achieve, how its value will be measured and what level of accuracy and human review is acceptable. They then write the work as outcomes rather than prescriptive stories. The Tenhaw Way, published free, sets out how to write value-focused epics and measure value.

Book a 30-minute call

30 minutes with James · how this would work in your organisation

Theme
Whole programmes
Read time
2 minutes
Questions answered
5 in full
Updated
Evidence basisOur approach
Usually engaged as
Agentic Proof of Concept. 2–4 weeks, Fixed price · £20k–£55k.
see the engagement →
Evidence basis

The basis for this approach

This is our role and working-method guidance, grounded in the published Tenhaw Way. It is not a separate priced product-management service.

On this page

The demand signal

The PPL operating-method work involved Product, Engineering and QA. It connected outcome-based work with AI-assisted building, testing and review, with the method documented for the client’s team to keep using.

Bring the reason this is on your agenda to a 30-minute call with James, and we can explore what it would take in your organisation.

Book a 30-minute call

Why it stalls

2 failure modes we keep meeting

The feature is specified without an acceptance decision

An AI feature needs examples of an acceptable result and a decision about cases requiring human review. Those choices connect product value to engineering and testing.

The backlog counts features instead of value

A list of tasks does not show which outcome matters or what evidence would justify the investment. Write the outcome and measurement before breaking the work into implementation tasks.

If one of these sounds familiar, bring it to a 30-minute call with James and we can explore a way past it.

Book a 30-minute call

How we approach it

3 moves, in order

  1. 01

    Write the outcome and its value

    Use a value-focused epic to state who needs the improvement, what changes and how it will be measured. Bring the process owner’s baseline into the requirement.

  2. 02

    Agree the examples with engineers and reviewers

    Clarify accuracy, exceptions, source access and the human-review boundary. Use those examples to test the implementation and to make the acceptance decision.

  3. 03

    Keep learning tied to the product decision

    Measure the value and revise assumptions as real examples are tested. A £20,000–£55,000 proof of concept can prove the riskiest part before a separate 90-day production scope.

Clarify accuracy, exceptions, source access and the human-review boundary.
Ask a technical questionanswers from all 34 guides
Ask anything technical about what does an AI product manager do? and I will answer from this guide, and tell you first whether this is work we have delivered or an approach we would be taking.

Prefer to talk it through? Ask us on a discovery call →

Sources

Every source below was opened and read before it was attached. Where nothing survived that check, the claim on this page was softened rather than given a plausible-looking link.

Tenhaw, Agentic Proof of ConceptPPL, the six-month Embedded Agentic Lead engagementThe 54 vs 1 front-end changes are one reported epic comparison, not a general productivity benchmark.The Tenhaw Way, write a value-focused epicThe Tenhaw Way, measure value
engage via

Work out the next step for your team.

A 30-minute call with James Rooney to discuss your workflow, people and budget. Leave with a rough scope and a useful next step.

Agentic Proof of Concept · £20k–£55k fixed · 2–4 weeks · excluding VAT

// pick a slot · cal.com/tenhaw/professional-servicesLIVE CALENDAR

No time that suits? Email hello@tenhaw.com. Calendar not loading? Open it on cal.com.

Describe the work

Describe the work in a paragraph. James replies with a rough scope and budget range within two working days.

Send James a paragraph about the work

We use these details to respond to your enquiry. Read our privacy notice.

Questions this guide answers

How is this different from a normal PM?

The core job still connects customer needs, priorities and value. AI makes acceptable error, evaluation examples and human review explicit parts of the product decision, alongside the feature behaviour.

Do they need technical skills?

They need to work with engineers on the implications of data, access, evaluation and review. The product manager owns the desired outcome and acceptance decisions; engineering owns how the system is built.

How do they write requirements for AI?

Write the outcome, value and acceptance examples, then make gaps and contradictions visible with the team. The Tenhaw Way publishes a free method for value-focused epics.

How do they measure value?

Agree the baseline, the named benefit owner and the measurement before the build. Keep released capacity separate from cash savings, and measure actual use and review cost as well as output.

How can we test an AI product idea?

Tenhaw’s proof of concept tests one chosen workflow in your tenancy for £20,000–£55,000 fixed over two to four weeks. It ends in a go/no-go decision and a separate fixed quote for the 90-day programme.