The Product Manager’s New Job Is Acceptance
Adversarial Testing from ICP to Adoption

A release passes QA and a scripted acceptance test, and the demo looks great. Then real customers arrive. Setup takes days, the person who does the work never saw the promise, and success has to rescue every account. Nothing was broken. The feature worked and the promise did not hold.
AI has made software cheaper to build. It has not made customer attention, trust, workflow change, or proof of value any cheaper. This Rolebook is for senior product managers and product leaders whose job is changing, and it introduces Acceptance Engineering: testing the whole path from the ICP and the market promise through evaluation, onboarding, real use, demonstrated value, and continued adoption.
It shows where QA and UAT stop, why the buyer and the user are often different people, and how to design tests that can fail, record every rescue, and keep evidence that does not go stale. It says what evidence would show that its own argument is wrong.
Never UAT a product without UATing the promise that caused the user to try it.
Inside, you will learn how to
- tell what QA, UAT, usability testing, and acceptance testing can and cannot show;
- define an ICP tightly enough to test;
- map who buys, who uses, and who can force adoption;
- test the promise that earned the customer’s attention along with the product;
- design an adversarial test and log every rescue;
- challenge your own metrics and keep evidence that does not go stale;
- use AI to design and challenge tests without letting it stand in for the customer; and
- decide what evidence would make you narrow, change, or stop.
Details
- Category
- Business & Economics / Product Management
- Series
- Intellectual Frontiers Rolebooks
- Publisher
- Intellectual Frontiers Press
- Format
- 7x9.19in Rolebook, 15 chapters
What's new
Latest: New book: The Product Manager's New Job Is Acceptance.
Online companion
The book argues that a senior product manager’s scarce job is producing evidence that the intended customer will find, use, and keep a product. This companion holds the working material.
Request a review copy
Tell us who you are and what you want to get out of this book. The button opens your own mail program with the request written out, addressed to the editors. Nothing is stored here.
Put this to work
Working fit brief
Decide whether this work fits a real operating problem, partnership, license, or build.
- For
- Practitioners, researchers, founders, and operating leaders.
- What you keep
- A working fit brief you can review, revise, and send.
- What counts as sound
- Answers a named decision
- Separates evidence from assumptions
- Includes the strongest contrary case
- Names missing evidence
- Ends with a test, owner, and date
A promising fit still needs evidence from the intended setting.
Nothing entered here is stored or sent. Review the prompt before sharing confidential, personal, patient, or privileged information.
Review the prompt
You can leave any field blank. The prompt will mark it as not provided.
If the record survives your review, send the question, evidence, unknowns, and requested next step.
