SHORT ANSWER
Product managers use AI to compress the artefact half of the job: synthesising interviews, drafting specs and tickets, building clickable prototypes, summarising support and review data, and pressure-testing decisions. The best PMs also use it inside the product, designing evaluation sets and quality metrics for AI features. What they do not delegate is the decision, the customer conversation or the accountability.
Answered by Andrew Crossley, Fractional Chief Product Officer · Updated 2026-08-01
AI fluency is now a screening criterion for product roles, and the productivity gap between fluent and non-fluent PMs is roughly a day a week.
Used badly, it produces more documentation and worse decisions — the volume was never the problem.
Transcribe interviews, extract patterns, cluster reason codes. Always keep and occasionally read the raw transcripts.
First drafts in minutes with your context pasted in. You edit for judgement; it handles structure.
A clickable version of the idea in an afternoon, so validation happens on something real instead of a slide.
Write and explain queries, sanity-check cohort logic, draft analysis narratives — then verify the numbers yourself.
Ask for the strongest argument against your plan. Useful precisely because it has no political stake.
Build the golden set of examples, define acceptance criteria, and track override rates in production.
FROM EXPERIENCE
Across a typical product week, AI takes over first-draft writing, interview synthesis, competitive scans and prototype scaffolding. That is roughly a day and a half reclaimed.
The value only materialises if that time goes into customer conversations and decisions. Teams that reinvest it in more documents end up exactly where they started, with a larger backlog.
Customer conversations, prioritisation calls, performance conversations, and anything you will be accountable for in front of a board.
Give it real context — data, transcripts, constraints — instead of short prompts. Context quality drives output quality.
Yes. Smaller product teams with higher seniority is the visible trend in 2026.
IN SHORT
What the role actually involves and how it differs from a classic PM.
Read moreContract, fractional and advisory engagements — current availability.
Read moreTurning LLMs, RAG and agents into products that hold up in production.
Read moreA short call to work out whether the problem is strategy, scope or speed.
Work with AndrewTHE FRAMEWORK
MORE ANSWERS
You become a product manager without a degree by producing evidence instead of credentials: ship something real, own a metric in an adjacent role, and document decisions publicly. Support, sales, operations and QA are the highest-converting entry routes because they give you customer contact and data. Hiring managers screen for judgement and shipped outcomes; almost none check for a degree at interview stage.
Four skills carry most of the job: customer discovery, prioritisation under uncertainty, written communication, and data literacy. In 2026 add two more: AI-assisted execution, and evaluation design for AI features. Frameworks, roadmapping tools and ceremonies are teachable in weeks; judgement about what not to build is the skill that separates senior PMs from everyone else.
Product managers usually fail for structural reasons, not talent ones: no clear mandate, no owned metric, no direct customer contact, an organisation that rewards shipping over outcomes, and an unwillingness to create conflict by saying no. Four of those five are fixable by the company. The fifth — avoiding conflict — is the personal skill most often missing in PMs who stall at mid-level.
Product-market fit is the point where a defined group of customers keeps using and paying for your product without you pushing them, and demand grows faster than you can comfortably serve it. Practical signals: week-four retention that flattens rather than decays, over 40% of users saying they would be very disappointed to lose it, organic word of mouth, and shortening sales cycles.