The Rewrite

How the core PM artifacts and rituals are being rewritten for the AI era.

• Should a change to an agent's harness be treated as a redesign?Jakob Nielsen says treat model changes as redesigns. The change users feel is the harness: a prompt cut on a Thursday. Six lines under every harness commit.
• Should last-mile design feedback be fed back into the design system?Luke Wroblewski's agents get a screen 90% right from the design system and close the rest on screen. Log the fix and promote it on the third surface.
• What is a repair rate, and why should design own it?The repair rate counts how often users re-ask, rephrase, or say they can't follow an AI answer. It's the live signal for output you can't predict.
• What should an agent console answer first when resolution rate drops?Sierra's Agent Studio answers why resolution dropped in one chat. The first answer has to be which resolution. My 48-hour definition held for 98% of cases.
• Can synthetic users replace real user testing?No. A twin fills the where column, stuck points and edge cases. Only a real person, asked, fills the felt column. My onboarding agent shipped with it blank.
• How do you keep a design system current when AI agents read it?When agents read the design system on every call, cap what always loads, write the reason next to each rule, prune on model upgrades, and sign the weekly diff.
• How should a voice agent read back a corrected name or number?As a diff: the old value, the new value, and which one is on file. Sierra found only 24 to 37% of re-checked wrong values get fixed, so make the swap audible.
• How long can an AI agent's write sit before a person sees it?After SaaStr's two agent deletions, Jason Lemkin named the copy. The field nobody named is the window: minutes before a named reader sees the write.
• What replaces the design artifact as proof that judgment happened?The design decision record. One page, four fields: the decision, the constraints behind it, what you gave up, and the signal that would prove it wrong.
• What should design hand to engineering instead of a mockup?When prototypes arrive as production-shaped code, design hands engineering the behavior spec as test rows: hard fails, graded floors, failure fixtures.
• How do you measure a human and AI team before shipping it?Jakob Nielsen's joint cognitive systems gate scores accuracy, speed, and error recovery. Add a fourth column, refusal rate against the human alone.
• What should a prototyping dashboard measure besides adoption?Reddit Proto has 700 prototypes and 100% adoption. Its dashboard needs two columns: shipped, with the reviewer named, and landed, with the behavior changed.
• What has to travel when a customer changes model providers mid-engagement?Two settings travel in the interface. The eval threshold per surface has to survive the switch, run before a fallback is listed and again when it fires.
• What should an overnight agent show you the next morning?Three lines at the next session: what it did, what it is doing, and what you can still take back, with the undo window next to the gap between sessions.
• What leaves with the forward deployed engineer when the engagement ends?The operational knowledge, says Milos Mandic, and about 70% of it should become product. Do not ask what left. Get the handback packet at three moments.
• Who signs off on the decisions inside an AI-generated prototype?An AI prototype carries choices nobody made. The PM ratifies what answers the question, design ratifies behavior, and model-made choices wait for an owner.
• Why do designers use AI less in the Deliver phase?A 443-designer survey puts AI at 72% in Discover and 41% in Deliver. Nielsen says late errors ship. They ship because nobody wrote the failure inventory first.
• Should designers be the quality gate for PM prototypes?No. A person as a gate caps throughput at what one person can review. Design writes the rubric, the rubric is the gate, and PM prototypes arrive scored.
• How do you know if a product strategy is working?Not by how much of the team's energy goes to it. A strategy is working when it produced a no this week that cost something. Keep a ledger of the nos.
• What is Figma Specs, and what does it change for design teams?Figma Specs is a Markdown editor for a team's design language, read by people and agents. It moves design's core output from screens to the spec.
• How do SaaS companies charge for AI in 2026?Of 41 software brands, 21 sell a seat plus AI credits and only 4 charge per outcome. Why credits won, and the three numbers to ask any vendor for.
• How do you measure whether a research finding landed, not just shipped?Re-code next quarter's comments against the codebook and report which themes shrank. Why fixfluence needs a second verb, with the 31-call and 3-call themes.
• What should an always-on AI agent's charter include?Three lines beyond the job: a slot, a budget line, and a reader's name. From a fleet where 13 of 39 agents fired in one window and 13 were never read.
• What should an AI pilot cost estimate include?Four lines: cost per answered question, the multipliers with their triggers, a name beside each, and three re-check dates. One number gets outgrown.
• When should you train a team on a new AI tool?In each person's first week. Prompting habits set within about 5 sessions, so a training months after rollout is asking people to unlearn.
• Is a product builder just a PM who uses AI?No. A builder is accountable for something in production: an eval set, a cost per request, and a rollback condition. Only 1 in 8 AI PM listings asks.
• Should product managers rotate through forward deployed engineering?Atlassian says every PM should be an FDE, by mandate. Take the tour, but first name the PM who owes the field a written decision in two weeks.
• Who should approve exceptions to an AI agent's rules?A second agent can flag and fix rule breaks. A person should read every blessed exception, counted by rule. I modeled 50 exceptions a week once and got 600.
• What happens to a pricing migration when the executive sponsor leaves?It gets re-argued at the trough unless the commitment was written for the seat. My 18-month playbook named four people and had no line for one leaving.
• Is outcome-based pricing a myth?Scott Woody says price an output, not an outcome. A resolved ticket is countable, and it still drew 200 contested cases a week. Pick the dispute you can afford.
• Should an auto eval tool pick your first eval?No. Let it find candidate failures, then read fifty outputs and rank by count times customer cost. A feature of mine passed on average and failed a fifth.
• What can a customer digital twin tell you before launch?Whether your questions and flows hold up. Not how people will feel about a feature that does not exist yet. My onboarding agent is the case a twin would miss.
• Should you ship an AI feature that hallucinates 3% of the time?Not on the 3%. Find which traffic slice holds it, then name who measures it in week six. Two launch numbers, a fifth of traffic and 89% to 61%, say why.
• What should a prototyping tool report instead of prototypes created?Not prototypes created. Report the outcome split (shipped, replaced, killed) and the median time to kill. Stripe's Harbor has 12,000; here is the missing one.
• Who owns the observation record when agents run across several interfaces?Four interfaces onto one record is a claim about reads. Whichever interface keeps the richest local trace becomes the real system of record.
• Is llms.txt enough to make a site useful to AI assistants?llms.txt is an index, not content. Anthropic, Vercel, and Supabase publish one. What the 780+ sites doing it are still missing, and what to ship next.
• Why is a polished mockup no longer evidence of conviction?Fidelity was a proxy for how much thinking sat behind the work. AI broke it, so the most finished-looking work now gets the shallowest critique.
• Should you be the platform underneath or the application on top?Glean and Alation both retreated to the substrate. You cannot own a daily habit and be neutral plumbing at once. Decide by renewal mechanism.
• What do designers do when AI generates the screens?Drawing got cheap, deciding did not. The designer's job moves from producing artifacts to specifying behavior: constraints, ranges, rubrics, and the wrong path.
• How do you level and promote PMs when the deliverables are gone?When AI collapses the documents PM promotions ran on, leveling has to measure judgment. What counts as evidence at each level, L4 to Principal.
• What does it cost to land a product versus build it?Building costs collapsed, landing costs did not. Where each cost lives, who pays, when it hits, and why orgs fund the cheap half and starve the other.
• What does it mean to land a product, not just ship it?Shipping is code in production, launching is the announcement, landing is durable behavior change with realized value. The definition and four failure modes.
• Who owns product landing in an organization?Landing falls in the seam between product, marketing, sales, and success, each handing off before adoption. Why it is nobody's job, and three fixes.
• Why does Whatnot run product with so few PMs?Whatnot runs an $8B GMV marketplace with ~22 senior PMs, hired 1 of 31,832 applicants, and maps PMs to problems, not pods. Never hire by default.
• Why is the PM career ladder breaking in the AI era?The PM ladder runs on artifacts as promotion evidence. When AI collapses the document, it removes the currency the ladder was calibrated on.
• If building is cheap now, what is the real constraint on product builders?Building stopped being the bottleneck. The 2026 CPO report shows speed to market became the top CPO challenge. The constraint moved to landing, not launching.
• Does AI delete the director of product?AI does not delete the PM or the VP first. It exposes product middle management, the Director and Group PM whose main job is moving information up and down.
• Does continuous discovery scale for AI-native products?Teresa Torres' continuous discovery fits human-centric SaaS and breaks for agent products. Punctuated discovery is the alternative: 60/40, three-week sprints.
• How do you hire a Builder PM?The old PM hiring loop tests presentation and frameworks that LLMs made easy to fake. Hire by what a candidate can ship in four hours, not how they talk.
• How does AI change the PM-to-engineer ratio?The 1-to-7 PM ratio was never about engineers. It priced how much build output one PM could direct. AI raised each engineer's output and broke the math.
• How is the product manager role changing with AI?AI-forward companies hire Product Builders, not spec-writers. The PM role now rewards six skills led by rapid prototyping and customer proximity.
• Is Agile dead, and what replaces it?Agile was a coping mechanism for slow, costly building. AI killed both founding constraints. What replaces it is not waterfall, it is the spec-first loop.
• Is being a Product Builder about coding?No. Product Builder was never about a PM learning React. It is about collapsing the distance between deciding and making, and killing the coordination tax.
• Is being AI-first a product decision or a tooling one?Being AI-first is a product decision, not a tooling one. Using AI runs your old process faster. Being AI-first rebuilds the process as if AI was there day one.
• Is product management dead?Product management is not dead, it escaped the product team. Every function deploying AI workflows is structurally a product team that needs builders.
• Is Scrum obsolete for AI-native teams?Scrum is obsolete and the market is voting with hiring. The replacement has a name: a four-to-six person builder pod with no ceremony tax.
• Is the PM-as-translator role dead?For 15 years PMs were professional middleware, reformatting customer input into decks for engineers. AI and MCP stripped away three layers of translation.
• Is the PRD dead?The PRD is dead because building got cheap. A clickable prototype, a one-pager, a 5-minute Loom, and a 30-minute conversation replace it.
• What is the difference between a PM and a Product Builder?A PM shipped documents and ran handoffs. A Product Builder ships prototypes, writes evals, and owns a surface end-to-end. The line-by-line difference.
• What belongs in a PRD versus a spec versus a brief?A PRD did three jobs badly. Split them: the brief carries the why and the bet, the eval carries the commitments, the prototype carries the solution.
• Should you call yourself an AI PM?No. AI-native describes tool familiarity, not decision ownership, and it will not survive resume screening. Name the outcome you own, like I own activation.
• Should you merge the PM and product owner roles?Merging PM and product owner fixes the symptom, not the cause. The real fix is killing the Scrum frame the PO role exists to staff.
• What are the three artifacts that replace a PRD?A one-page brief, a throwaway prototype, and an eval. Each does one job the PRD did badly: memory, alignment, and commitment. With the templates.
• What do boards expect from product in 2026?The 2026 CPO board deck is seven slides: outcome ledger, unit economics, eval scorecard, agent inventory, cycle time, headcount-to-output, downside.
• What is a one-page brief and what goes in it?A one-page brief replaces the PRD with six sections: problem, evidence, solution with a prototype link, metrics, risks, and the ask.
• What is an AI product engineer?An AI product engineer combines PM strategy, design, and engineering, with AI amplifying each. One person now does what used to take a team of three.
• What is dual transformation for a product org?Dual transformation runs a legacy SaaS and its agent-native successor on two clocks: two cadences, three talent categories, six CEO numbers, three rituals.
• What is service-as-software?In service-as-software, AI agents do the work and humans review and handle edge cases. It changes UX, reliability, pricing, and the PM role itself.
• What is substrate-first engineering?Substrate-first engineering means engineers build the platform that lets non-engineers ship safely, not the features. Four pieces make it up.
• What is the AI noise tax?The AI noise tax is the credibility cost of three patterns: superpower LinkedIn posts, bolted-on AI sidebars, and PMs arguing prototyping breaks empathy.
• What is the AI product operating model?The AI product operating model keeps empowered teams and continuous discovery, but agents kill the PRD and compress discovery from four weeks to four days.
• What does the org chart for an AI product company look like?AI coding tools raised developer output but org velocity stayed flat. The new org chart fixes three layers: adoption, review, and the coordination middle.
• What does a Product Builder job ladder look like?A four-level Builder PM ladder from L4 to Principal. Five dimensions scale with level; the operating model does not: prototypes, evals, user validation.
• What replaces the product org by 2028?Ten checkable predictions for product orgs by mid-2028: median team of six, code in week one, evals the top skill, hybrid pricing, extinct APM programs.
• What should a PM job description look like in 2026?I audited 200 PM job descriptions. 196 could have been written in 2022. The four tells of a dead JD, the four tells of a live one, and how to rewrite.
• Which software categories is AI killing?Three forces are collapsing software categories: search becoming answers, tools becoming agents, subscriptions becoming outcomes. A PM's field guide by bucket.
• Why does distribution beat product in the AI era?AI made product cheap to build, so product quality gets copied in an afternoon. Distribution, the channel and brand and install base, is the only moat left.
• Will AI replace product managers?No, but AI will replace 80% of what most PMs do. The surviving 20% is customer empathy, judgment, leadership, and vision, and it becomes everything.