Blog
Notes on building products in the AI era, from someone who still ships code every week. New posts most days. Failed experiments included.
- 405 posts
2026
- Marco Di Santo's Five Vendor Questions Come Back Described. Ask for the Day-60 Page.Di Santo's five questions for an AI agent vendor are the right five, and sales answers them from memory. The vendor's FDE holds the evidence. Ask for one page.
- People Paid More for AI-Designed Games. Make Your Design Beat the AI Version.Buyers paid 27% more for games an AI designed alone than for amateurs' games. Research's new job: prove a design beats the AI-only version with real users.
- Lenny Counts 3.8 Open PM Roles per Designer. Kill the Ratio. Count the Surfaces With a Rubric.Lenny's job report puts 3.8 open PM roles against every design role. The ratio counts who draws, and drawing got cheap. Count surfaces with a current rubric.
- SaaStr Runs $20M on 3 Humans and 20 Agents. Revenue per Human Hides the 13-Hour Review Day.Lemkin's revenue-per-employee table has SaaStr at $6.7M per human and a 13-hour day spent reviewing agents. The ratio counts heads. Count reviewed hours.
- Spotify's Three AI PMs Share a Vocabulary. Put a Row Set, a Floor, and a Date on Every Seam.Three Spotify principal PMs say the word eval shifts meaning by layer. No seam in the piece has a number. A row set, a floor, and a date fix that.
- Lesson 11 Lost 83 Documents in 26 Files. Count the Questions Too, and Keep the Copies.Lesson 11 of Becoming FDE counts 83 lost documents, not 26 unreadable files. Add the questions lost, keep unread copies in the loss, and name an owner.
- Ramp's Non-Engineers Shipped 7,000 PRs in a Quarter. The PM's Day Is Decisions Now.Ramp's non-engineers shipped 7,000 PRs in a quarter and PostHog's agents open their own. The PM's day becomes a queue of decisions.
- Nielsen Says Review the Decisions You Never Made. The Card Is a Missing Line in the Brief.Nielsen reports Sidecar, a side chat that lists what an agent decided unasked. Mental demand doubled. Answer each card once and write it into the brief.
- Vercel Runs 'Our Internal Sierra' for $150K a Year. Write the Invoice Nobody Sends.Vercel's COO says its support agent costs about $150K a year all-in. That is tokens and infrastructure. Add the engineers and three resolution rates.
- Willison Folds the Agent's PR Essay. Keep What Wasn't Checked Above the Fold.Simon Willison hides agent-written PR descriptions behind details-summary. The verification went under the fold. Three lines belong above it.
- Atlassian Says Its FDEs Aren't a Services Business. Put the Field Under the CPO.Atlassian says its FDEs speed customer request to delivery. HubSpot's agent resolved 2M issues. The field's signal is product work. Put it under the CPO.
- The Midterms Didn't Reject AI. They Priced the Moat. That Is Good News, Even for the Billionaires.Voters rejected data centers in 40 of 41 votes and handed Democrats Congress. The compute moat got a price. Why that moves AI money to adoption, and who wins.
- Atlassian's Agents Write 50% More in Jira. Count What the Humans Closed.Atlassian's Q1 FY27 letter: 50% more created in Jira after MCP, adopters grow ARR 2x, RPO up 44%. The agent writes on a human seat. Count what humans closed.
- Canva Merged Its Product Org. Finish the Job: Put the Whole Loop Under the CPO.Canva merged product, growth, and platform into one org to end fragmented ownership. Finish it: design, PMM, and FDE report to the CPO too.
- Cutler Says Let the Customer Pick the Score. Kill the Scorecard Menu.John Cutler says prototype three versions of the engagement score and let the customer choose. In an FDE engagement the score was fixed at signature.
- The Prototype Is Free. The Positioning Is the Problem Statement Now.Emily Kramer's 1,100 job posts show PMM splitting in two. When the prototype is free, the problem statement and positioning are one file, owned by one team.
- Cagan Lists Three Product Roles. The Fourth Is the One Hiring Fastest.Marty Cagan sorts the product role into three definitions by operating model. The forward deployed engineer fits none, and demand for it is up 2,100%.
- Nielsen Says a Map Beats a Babysitter. Write the Map for the Next Run.Nielsen's five upgrades for long-running agents assume a person comes back. 13 of my 39 agents had no reader. The report template written for the next run.
- NICE Moved Its FDEs Into Go-to-Market. The FDE Org Belongs Under the CPO.Three earnings calls named FDE teams this week with only sales and delivery numbers. The field's output is a product decision. Put the org under the CPO.
- Elena Verna Says Feature Discovery Is Ending. It Moved Into the Harness. Count Fires per Tool.Elena Verna says AI makes feature discovery unnecessary. Paweł Huryn measured 8,200 tokens of tool manuals before anyone types. Discovery moved, curve and all.
- Figma's Agent Made Three Prototypes From 'Surprise Me.' Kill the Brief. Write the Rubric First.Figma's workflow lab briefs its agent with 'surprise me,' picks the option the designer likes, and writes the spec last. Write the rubric before the prompt.
- Salesforce's FDE Slackbot Says Leave the Call With Better Questions. Leave It With Rows.Salesforce's Ask Slackbot tells an FDE to leave discovery with better questions. Leave with three labeled records per firm opinion and the product's number.
- Anthropic Bought $5B of Burst Compute and Flipped to a Loss. Match the Lease, Then Watch the Minimum.Anthropic's S-1/A shows $5.0B of burst compute and a $567M Q3 loss. Tunguz's fix is a minimum that matches the lease. I sold minimums. Watch usage against them.
- Your Buyer's Agent Reads One File. Product Marketing Reports to the CPO Now.Sierra and 50+ enterprises are drafting how buyer agents talk to companies. When the story is a product surface, product marketing belongs under the CPO.
- Palantir Can't Satiate Demand: What Breaks in the FDE Org at 100Palantir says it 'cannot satiate demand' and must re-resource. Five things break between the tenth FDE and the hundredth, and what the inventor did instead.
- Salesforce's AI Org Routes Field Feedback Through One Slack Channel. Kill the Channel as the Loop.Salesforce's 700-person Agentforce org puts FDE feedback in a Slack channel with two tags. A channel is an inbox. The loop is a packet, a date, and a decision.
- Salesforce Hires PMs to Say What Good Looks Like. The PM Is the Product Builder Now.Salesforce's 700-person AI org hires PMs for prototyping and evals. The PM becomes the Product Builder, inside one loop under the CPO.
- Salesforce Put a $50 Seat Next to the Credit on Agentforce Coworker. The Seat Is the Budget's Unit.Salesforce added a $50 per-user price to Agentforce Coworker at 185,000 users and 21x usage. The release says why: budget. It does not say what the seat buys.
- Nielsen Says Treat a Model Change as a Redesign. The Redesign Your Users Feel Is the Harness Commit.Jakob Nielsen's guideline: treat model changes as redesigns. The change users feel is the prompt cut on a Thursday. My harness: 51 commits, 30 with no name.
- Lesson 10 Tripled the Window and Accuracy Held at 60%. Add the Cited Doc and the Twin Column.Lesson 10 of Becoming FDE tripled the context window. The right doc arrived 90% of the time, the model answered 60%. My agent lost that way, next to a twin.
- 84,000 Chats Show When Users Re-Ask the AI. Design Should Own the Repair Rate.A study of 84,000 ChatGPT and Gemini chats counts when users re-ask. When you can't predict the output, design the states and own the repair rate.
- Salesforce, Snowflake, and Atlassian Shipped the Agent Budget Cap. Kill It as the Control.Three control planes shipped the agent budget cap in one week. The cap fires at the end of the money. The bill was set when someone changed top-k from 5 to 20.
- Legora Cut the FDE Seat in Two. The Eval Fell in the Gap.Legora has about 100 legal engineers who ship no code and FDEs who never see a client file. Behind a data wall the field owns the rows; only the rate crosses.
- LukeW's Agents Get 90% From the Design System. Don't Feed the Last 10% Back In.Luke Wroblewski's agents get a screen 90% right from the design system and close the rest on screen. Don't feed it back. Promote the fix on the third surface.
- Reddit Fell 29% on 'AI Mode Does Not Drive Traffic.' Notion's Top Channel Is an AI Tool.Reddit fell 29% and will wall the page behind a login. Notion's top channel is an AI tool at 25.4%. The assistant sends people to the page it can read.
- 43 Skills, 39 Auto-Activate. Kill the Skill Count. Keep the Four You Type.Paweł Huryn's pack auto-activates 39 of 43 skills. Figma's PM OS has 31. In my library 30 of 51 commits have no author. Count fires and acted-on, not skills.
- Agents Prompt People Now, Says Arca. Put the Default on Silence in the Ask.Arca says agents prompt people more than people prompt agents. Anthropic's agents idle 80% waiting on a human. Four fields on every ask, and a ledger column.
- ServiceNow Fell 27% on a 70.5% Gross Margin. Name the Trough and the Month.ServiceNow lost 27% on a gross margin of 70.5%. Sierra doubled in five months. My pricing migration bottomed at 58 to 62% and came back to 71% by month 22.
- Sierra's Console Answers 'Why Did Resolution Drop?' Ask It Which Resolution.Sierra rebuilt Agent Studio around a chat that answers why resolution dropped. The first answer has to be which resolution. My 48-hour definition held for 98%.
- Five Real Users Beat Fifty Synthetic Ones, If You Ask Them How It FeltNielsen: five real users beat 50 synthetic ones, fake users make fake data. My twin had every stuck point right. What it missed, only a question held.
- 70% of LangChain's Agent Runs Are Scheduled. Count the Ones Somebody Read.LangChain says 70% of its agent runs come from a schedule, not a person. In my fleet 13 of 39 agents ran clean and nothing read them. Publish the read share.
- Rules 97.5%, Trained 100%, Model 87.5%. The Bake-Off Table Needs a Slice and a Date.Lesson 09 of Becoming FDE scores rules, a trained classifier, and an LLM on 120 fragments. My 89% was 61% by week six. Add a slice column and a re-run date.
- Anthropic's S-1 Has No Gross Margin Line. Your AI Product Needs One.Anthropic's S-1 books compute as opex and shows no gross margin. Where inference sits, and who keeps a 40% price cut, are now CPO decisions.
- LangChain's Design Agent Updates Its Own Design System Weekly. Someone on Design Should Sign the Diff.LangChain's design agent learns its own design system. When agents read the system, design owns the context budget, the reasons, and the weekly diff.
- A Model Alone Is Not an Agent: What the Tooling Changed for the FDE SeatAnthropic's S-1 defines forward-deployed engineers on page one and sells the harness they used to write. What that moves in the FDE seat, and what it doesn't.
- Kill 'Find the Root Cause Yourself' on the AI-Native CSM ScorecardChad Horenfeldt's 150 interviews want CSMs who find the root cause themselves. Kill that line: triage to the layer, name the keys holder, know the recall rule.
- Sierra's Voice Agents Fix a Third of the Details They Catch. Read Back the Diff.Sierra's τ-Entity benchmark: when a voice agent re-checks a wrong name or number, 24 to 37% get fixed. Speak the repair as a diff and score the pilot per call.
- Should Anthropic Buy Salesforce? The Model Company Shouldn't Buy the System of RecordNo. Split Salesforce into its eight or nine businesses and the parts worth owning (Slack, the headless harness) are the parts Claude already reaches by default.
- Jira's MCP Judges Agents by Final State. The Record Still Has No Cause Field.Jira's MCP went from 15 endpoint tools to 52 job tools, judged by final state. Its v1 critique called the cause record unneeded. Amplitude's agents fill it in.
- Reddit's Handoff Ships a Draft PR. Design Should Hand Engineering the Tests.Reddit's feature capsule hands engineering code that may or may not merge. When prototypes are production-shaped, design hands engineering test rows, not code.
- Kill 'The Team Would Be Slower Without It' as the Test of a Leader's Real WorkPatrick Neeman wants design leaders making again, and his test for real work is that the team would be slower without it. That test selects for the bottleneck.
- SaaStr's Clean Copy Was Luck Twice. Name the Copy, the Reader, and the Window.Jason Lemkin says the question after an agent deletes your data is where the clean copy lives. The copy is the reversal. Nobody named the window.
- Milos Mandic Can't Tell From 24 FDEs. Seven of Them Already Answered.Milos Mandic's State of FDE survey got 24 answers and he says they can't settle residency versus burnout. Seven who still hold their systems can.
- Who Would Notice in a Day? The Maturity Level Nobody Checked Has a TestMarco Di Santo's four questions check the level an AI roadmap starts from. One of them is the assessment: 12 of my accounts and one expense agent say which.
- The FDE Writes the Eval: Almost Right Has a NumberAneel Bhusri: 'almost right isn't good enough.' Colin Jarvis: FDEs built the evals. The eval is the deployment artifact, and the FDE writes it.
- Mark Pincus Left the Better Column Empty. Here Is Heidi's Board.Mark Pincus left Better empty for his own product on Aakash Gupta's show. Heidi's board: Better empty, one failed new, one new that is the company.
- Nielsen's Joint Scorecard Has Three Columns. My Expense Agent Failed the Fourth.Jakob Nielsen's gate for a human and AI team scores accuracy, speed, and error recovery. My expense agent won all three for two weeks. It lost on refusal.
- The Prompt Commit: Score, Rows, Name, Undo Under Every Prompt ChangeLesson 08 of Becoming FDE says the eval score is a field of the prompt version. My repo says two fields are missing: the rows it was scored on, and the name.
- MIT, LangChain, and Google Put Agent Risk on Reach This Week. Add the Name.Three posts this week moved agent risk from the decision to what the agent can reach. In my 39-agent fleet, reach growing unsigned is what killed agents.
- Reddit Has 700 Prototypes on a Dashboard. The Column It Needs Is Shipped.Blair Metcalf showed Reddit Proto on How I AI: 700 prototypes, 100% adoption, real data, and no shipped column. Figma got 17x the code and 1.3x the releases.
- Anthropic Runs 17 Engineers per PM. The Ratio Is the Wrong Question.Anthropic runs about 17 engineers per PM and junior tech hires fell from 27% to 9%. The CPO's org question is spans, layers, and who builds the bench.
- When Not to Hire Forward Deployed Engineers: The Honest CasesMilos Mandic estimates three in four FDE teams are dev shops. Five honest cases where the forward deployed seat is the wrong hire, and what to hire instead.
- Kill the Thumb. The Preset Reason Is the Rubric Dimension.Nielsen says the thumbs that train AI deserve usability testing. The widget was never the failure. A thumb is one bit with no dimension, output id, or slice.
- 1% of Users, 75% of the AI Cost. The Brake Goes on the Loop, Not the User.Lehrskov-Schmidt, Databricks, and LangSmith all put the AI spend brake on the user this week. Cost and value are independent, so brake the loop and the surface.
- One Interface, Several Providers Is the Easy Half. The Eval Threshold Travels.Lesson 07 of Becoming FDE makes the interface survive a provider switch. LangSmith and Databricks shipped the switch at runtime this week, with no eval on it.
- Personal Agents Will Call Every Few Hours. Kill the Front Door.Salesforce says personal agents will call your contact center every few hours; put a business agent at the door. They are polling a field you never published.
- Nielsen's 1-Second Contract Has a Sixth Band. The Agent Ran Overnight.Nielsen says today's AI latency is the worst you will ever suffer. The chat wait is shrinking. The agent wait is leaving the screen, and it needs three lines.
- Two Months, Then One Day: OpenAI Published the FDE ScorecardColin Jarvis published OpenAI's FDE numbers: 90% of custom code gone, a second team live in one day. Put that date on the scorecard, and read the 60% case.
- Your Prototype Made Decisions Nobody Made. Who Owns the Spec Now?Ravi Mehta found an AI PRD full of decisions nobody made. When the prototype is free, the PM owns the question, design owns the behavior, nobody owns the rest.
- What Leaves With the Engineer: Get a Copy of the PacketMilos Mandic says buyers should ask what leaves with the forward deployed engineer. Do not ask. Get the handback packet, at two weeks, go-live, and day 60.
- Ramp Built Its Harness in Six Weeks. Kill the Build-Versus-Buy Memo.Ramp built its agent harness in six weeks. Building got cheap, landing did not. Kill the build-versus-buy memo. Three lines instead, and buy if any is blank.
- The Mod Fired on 99 of 111 Turns. Off by Default Is the Design.Dan McAteer's supervisor mod spoke on 99 of 111 turns. Anthropic ships its own watcher off by default. My 44-agent fleet learned the same lesson.
- AI Is Startware, Says Nielsen. It Finishes the Day the Failure Inventory Exists.443 designers: 72% use AI in Discover, 41% in Deliver. Nielsen says wait for finishware by 2028. Late errors ship because nobody inventoried them. Ten rows do.
- Code Got Faster. Releases Didn't. The CPO and CTO Have to Split the Substrate.79% of engineering leaders say agents write code faster and releases aren't. The fix is the substrate, and the CPO and CTO have to split who owns it.
- Buying From an FDE Company: Write the Move-Out Into the ContractA CIO wrote 'stop sending me engineers.' An exit clause gets you out of an FDE contract. Six contract lines get you what you paid for.
- Kill the Correction Queue: The Agent Lands When the Fix Stops Waiting for Its BuilderMarco Di Santo built an agent fast and became its bottleneck. Kill the queue where every fix waits for the builder. Three replacements, and a weekly ledger.
- Salesforce Just Bought the SignalSalesforce is buying Braze for $5.66 billion. Marketing Cloud was built on a send. Braze is built on a signal. The integration is brutal. That's the point.
- The Threshold Card: Tune the Judge Before You Trust the Score, and Date the Re-TuneHamel Husain and Antaripa Saha show the 0.50 default can catch nothing. My classifier went 89% to 61% in six weeks. One card per judge, six lines, with a date.
- The Data Flywheel Has a Reverse GearCharacter.AI filed Chapter 11 with 12M monthly users. It fails Deepak Mukunthu's 3-question moat test, and adds a fourth: is your data an asset or a liability?
- Agents Idle 80% Waiting on Humans. Put the Date on the Decision.Anthropic's workforce data: agents idle 80% waiting on humans, 8,500 standing instructions, a swag doc that kept drawing requests. The fix is a dated line.
- Figma's Trial Closed 70% of the PM Gap. The Gate Is the Rubric, Not the Designer.Figma's randomized trial put PMs 35% faster with Figma Make. Nielsen says make designers the quality gate. A person caps throughput. The rubric is the gate.
- Which Model Is the Smallest Knob in the Architecture ReviewLesson 6 of Becoming FDE opens on a review asking which model, two candidates three points apart. Same week, harness-only changes moved 13.7 points.
- A Strategy Is Working When It Said No This Week. Count the Nos.Tim Herbig says a strategy works when the team's energy goes to it. Mine passed that test while I said yes to 39 builds and 13 became orphans. Count the nos.
- 17x the Code, 1.3x the Releases. Design's Job Is the Spec Now.Figma shipped a spec editor for agents as its design chief reported 17x more code and 1.3x more releases. Design's job moved from screens to the spec.
- Kill the Batch of Forty: Count the Unopened, Not Review TimeJakob Nielsen says to put review time on the AI invoice. 13 of my 39 agents produced work nothing ever read. Kill the batch of forty, count the unopened.
- Lovable Isn't Ready for Outcome Pricing. Here Is the 21-Month Bill.Elena Verna says Lovable would not survive the road to outcome pricing. I ran it once: 21 months, a margin trough, 600 disputes a week. The bill, by month.
- Your CEO Is Graded on AI. Hours Saved Won't Save Either of You.Wharton finds product teams lag on AI ROI and most firms count hours saved. The AI story a CPO owes the CEO, and what the CEO should hold the CPO to.
- FDE Comp and the Equity Problem: Whose Stock Goes Up When the Loop ClosesIndian FDE postings grew 19-fold at about ₹12 lakh base while frontier labs pay up to 70 percent in equity. The seat is spreading where the upside isn't.
- 86% Engaged, 20% Resolved: Kill the Engagement Rate HeadlineSalesforce's Tottenham release leads with 86% engagement for Ask Spurs and buries 20% resolved alone. Kill the engagement headline, lead with resolution.
- The Three-Call Theme Was the Renewal. Count What Landed, Not FixesNielsen says AI codes user comments as well as researchers and the test is fixfluence. My ranker buried a 3-call theme under a 31-call one. It was the renewal.
- Atlassian Split the Reviewer in Two. Ship the Matcher's Reject Pile.Atlassian's AI reviewer commented on code nobody touched. The fix: a matcher, a reviewer, a dull file between them. The loop misses the comment never written.
- 41 Brands Price AI Five Ways. The Credit Is the New Seat.Only 4 of 41 brands charge per outcome. 21 sell a seat plus credits, and the other columns are drifting there. Who sets the exchange rate is the real price.
- Somebody Has to Steer: The CPO Now Owns the Operating ModelAtlassian's AI builders sped up, then stalled: everyone rowing, no one steering. When prototypes cost a day, the CPO owns the operating model.
- 44 Appointed Agents, One Attention Budget: Three Lines on the CharterJakob Nielsen says nobody knows how people use always-on agents. I appointed 39. Thirteen fired in one window, thirteen went unread. Three charter lines fix it.
- Kill the Finish-Line Price. A Relay Has a Definition Per Handoff.a16z wants agents paid on the settlement at the end of a months-long journey. Fin's one-outcome meter split. My one definition drew 200 disputes a week.
- The Scope Guard Caught 6 of 9. Name the Keys That Carry the Bill.Lesson 05 of Becoming FDE ships a scope guard that catches 6 of 9 bad changes. One miss raised top-k from 5 to 20. A list of cost-bearing keys makes it 7 of 9.
- The Pilot Was Approved on the SixtyA course lesson prices a 120-person claims team at $60 a month, then shows three sensible decisions making it $2,106. Put four cost lines on the handshake.
- The Career Out of the Seat: Draw the Exits, Not Just the LadderThe FDE career ladder is unsettled, and founders are now walking into the seat for paid work. Three exits to write into the offer, and one rule for the ladder.
- Find Your Strikethrough: The Agent Shortlist PanelJason Lemkin's agent picked Render and struck Vercel off in one phrase. No lost deal in any CRM. A biweekly panel of workload questions finds your phrase.
- Agents Fit the Human Pattern Nine Times in Ten. Design the Tenth.Atlassian's rule: agents follow the patterns built for humans, nine times in ten. I put an agent in an approver's seat. The tenth is the unwritten judgment.
- Snyk Ran Its Agent Inside for a Year. Copy the Gate.Snyk moved an internal support agent to every paying customer. The surface was not the only change. Copy the four-part gate, not the year inside.
- Five Sessions, Then the Prompting Habit SetsUsers settle on 2 to 4 prompt templates within about 5 sessions. My onboarding agent lowered activation. Put a person in the first week instead.
- Who Writes Your Agent's Rules? I Counted the Commits.NN/g found Claude power users let the agent edit its own context files and rarely check. Mine are in git: 51 commits, 21 by an agent, 30 unattributed.
- Kill 'Human in the Loop' as a Control. Keep a Gate Ledger.Jakob Nielsen says vigilance fatigue dooms human in the loop and to prefer undo. Undo moves the problem. Keep a ledger: one row per gate, with numbers.
- A Product Builder Is Not a PM Who Uses AIAakash Gupta and Ankit Shukla define the product builder as any PM building with AI. Only 1 in 8 AI PM listings asks for production. That is the gap.
- Run the Oracle Before You Swap the ModelA wrong answer is a retrieval miss, a model miss, or a stale page. A no-reasoning oracle splits the first two in two hours. I add the third column.
- The FDE Scorecard: Count What Stayed, Not Who Was SentAnthropic will train 10,000 FDEs and AWS will credential them. Neither tells you whether an engagement worked. Four numbers that do, and five to stop counting.
- Agents Read the Design System. Read Is Not Checked.Luke Wroblewski says agents read the design system every time. Vercel's 1,000-line prompt got read too. Sort every line: machine check, named reviewer, or cut.
- Every PM an FDE? The Rotation Is Not the LoopAtlassian has 46 FDEs and says every PM should be one, by mandate. A PM back from one customer is an anecdote. Make the mandate a decision owed to the field.
- One Support Agent, Three Resolution RatesGorgias's benchmark: top support agents resolve about 70%, the median 48%. Looser rules count customers who gave up. Score 30 conversations three ways.
- Month Two: The FDE Leaves, the Workflow Has to StayGartner predicts 70% of enterprises will abandon FDE-built agentic AI by 2028. The FDE to customer success handoff is where that starts. Here is the page.
- Jev Is 400x Cheaper Per Call. Price the Wrong Pick.Three creators explained Jev by price per call this week. My classifier went from 89% to 61% in six weeks. Rank branches by what a wrong pick costs to undo.
- Agents Don't Answer Interviews. Amplitude's Left a Note.Amplitude added one optional parameter to every MCP tool: why are you calling this. Agents fill it in three quarters of the time. That is the interview.
- Fourteen Rules, and Who Blesses the ExceptionVercel cut a 1,000-line prompt to 14 rules, and a second agent blesses the exceptions. I modeled 50 exceptions a week once and got 600. Read every blessing.
- A Name on the Definition, and the Reject PileBasia Kubicka and Henry Cipolla say agents need a name on every definition. I run one in a single JSON file. Add the pile of what the definition threw away.
- The Migration Outlives the SponsorJason Lemkin's data: 49.7% of executives changed jobs in 16 months. A pricing migration takes 18 to 22. Take each commitment in a form a successor inherits.
- Twenty Minutes Is Not a Reason to BuildJason Lemkin's agent rebuilt Calendly in 20 minutes. I said yes to 39 cheap builds in 80 days and 13 became orphans. Build time is the wrong gate.
- Kill the Hidden BufferDr Bart Jaworski says plan at 70% of capacity and keep the buffer quiet. Keep the 70. A hidden buffer works once per stakeholder. Publish the variance.
- Label Before You RouteLangChain's model router cut median cost per thread 64%, proven by an A/B on its own engineers. For a customer-facing agent, label 150 real threads first.
- One Problem a WeekAndreessen says Musk fixes the biggest problem at each company every week, 52 times a year. Strip out the hero and it is the leadership loop that survives AI.
- The Output Gets Disputed TooStripe's Scott Woody says price an output you can objectively count, like a resolved ticket. I priced that unit. It drew 200 contested cases a week.
- The Kill Switch Has Nothing to Trip OnAT&T, Sammons, Databricks, and Google all named a kill switch this week. Matthew Green described the agent failure that trips none of them.
- Not Every Cost Center Has a Revenue Engine InsideSalesforce says AI turns cost centers into revenue engines. Canada Goose is the IKEA play, and it needs unserved demand next to the work you automated.
- The Menu Is Not the Error AnalysisHamel Husain tested Claude's auto eval tool and said hold off. Use it to find failures, then read fifty outputs and rank before any grader is built.
- Drawdown Is Not AdoptionSierra can now be paid from your OpenAI commitment. I had 12 accounts paying committed minimums and using less than the minimum. Report outcomes, not drawdown.
- Nothing Refunds a SentenceStripe now covers a purchase an agent gets wrong. The same week a Muse agent's mistake was a false auto-reply. Insure, budget, or verify: three classes.
- OpenAI Dots: The Agent Department Is Now a Line ItemOpenAI Dots gives every Pro user an always-on agent with its own cloud computer. The agent department is now a line item. Here is what product owns by Friday.
- The Twin Would Have Shipped ItSalesforce is buying Listen Labs to simulate what customers will do. A twin of my users had every stuck point right and missed how being watched felt.
- In the Room, Not on the Quota: Who Owns the FDE PromiseA Forbes piece put FDEs on the sales team. Job data says zero percent carry a quota. Who owns the promise, and the one-page handshake that says so.
- Kill the Per-Call Agent MeterJason Lemkin puts Salesforce's agent meter at 60x to 1,200x its integration rate. I ran product there. A meter on the seat takes the trough and skips the move.
- The Stop RuleSalesforce's Agent Designer repairs an agent team twice, spends at most $3, then escalates. LangSmith Engine v2 tests fixes until one passes. Mine had no cap.
- Which Slice Holds the 3%?Marily Nika asks what is inside a 3% hallucination rate. Mine sat in one slice, a fifth of traffic, and an 89% was 61% by week six. Ask which slice, and when.
- Count the Kills, Not the PrototypesStripe's Harbor has made 12,000 prototypes since May. The number to report is how many were killed in 20 minutes. In my fleet that third paid for the tool.
- The Receipt GateBasia Kubicka's agent said all checks pass while some never ran. The receipt gate: every check writes a receipt with the draft's hash, and a hook reads them.
- Three Token Bills, One UnitThe AI token bill got measured per task (SoL-Pi), per engineer (Larridin), and per company (GitLab) in one week. Product's unit is per outcome. Here is why.
- Same Model, Twice the Bill: The FDE Codebase ContractA UC Berkeley study found the harness, not the model, sets what an answer costs. So what an FDE changes on site is a margin call. The contract, in three layers.
- Absorb Pain, Excrete Product: The FDE HandbackPalantir made Fujitsu a Global FDE Partner. When someone else does the deploying, the handback has to be a written packet with a date, and a decision back.
- Kill the System-of-Record SlideServiceTitan cut off Podium, kept 1,000 customers, and added zero revenue. Why 'we are the system of record' is a retention fact, not a growth slide.
- 2,000 of 17,000: The FDE Shortage Is a Product ProblemOnly 2,000 of 17,000 US forward deployed engineers can deliver real ROI, and demand is up 2,100%. The gap is not talent. It is what the product lets an FDE do.
- What 267 Posts Are For: A Map of the Field Log267 posts, 49 handbook chapters, 203 answers, 115 templates. What each part is for, who it was written for, and where to start from your seat.
- Nobody Is Reading AnythingThe viral voxium post is not about Claude Code. It is about a company that made generation free, never funded the reader, and the fix for that.
- Percent Migrated Is a Vanity MetricWe modeled 50 pricing disputes a week and got 600. Percent migrated said the migration was done. The exception rate said nobody believed it yet.
- I Automated My Reading. The Filter Was Wrong Three Times.A filter over 45 sources cut 102 posts to 34. Version one dropped the best piece of the week. Here is each bug, with the titles that exposed it.
- Every Check Was Green. Four Sources Were Dead.My source monitor reported 43 of 45 feeds healthy. Four had published nothing for 72 to 612 days. Every one returned HTTP 200 and parsed perfectly.
- Which Door Keeps the ReceiptFour interfaces writing to one record only stays one record if all four write back. Whichever keeps the richest local trace becomes the real system of record.
- The AI Eval Starter Kit: Six Templates, Error Analysis to GateTeresa Torres's evals method as six copyable templates: error analysis log, type chooser, code assertions, golden dataset, judge prompt, and the gate.
- Torres Wrote the Evals Guide PMs Needed. Here Is Step Four.Torres's three-step evals guide is the best hands-on primer for product teams. I'd add a fourth step, a cost column, and one warning about the cheap tier.
- Benioff Said AI Replaces the UI. Then He Named the Product.At Dreamforce 26 Benioff said AI replaces the UI and Stokes said the value is trust to hold your data. Read together, that is Salesforce's new product.
- The FDE Is the Product Builder Wearing a Visitor BadgeOpenAI raised $4 billion for a deployment company. Anthropic launched a $1.5 billion one. The role they hire for is the Product Builder, from the services side.
- The Enforceable HalfSpotify cut agent token costs 90% by routing grunt work to a cheap model. The useful finding is that they could only enforce half their own rule, and why.
- Cagan's Definition Is Right. The Weights Are Wrong.Cagan maps Benedict Evans's three product skills onto his risk framework. The skills are right. Their AI exposure is wildly different, and that is the story.
- Salesforce Named the Harness. The Missing Piece Isn't on the Slide.Salesforce named the enterprise AI harness: six capabilities, a control plane, a 2027 window. The layer that decides whether it works cannot be bought later.
- Context Is King. Written Context Is Rented.Everyone is racing for the context layer. The quadrant nobody occupies is empty for a structural reason, and importing your wiki will not fill it.
- The Canvas Was Never the WorkMiro sold at 2.3x ARR while profitable with $435M in net cash. Compression explains the range, not the position. The mechanism is legibility.
- Polish Stopped Being EvidenceFidelity used to be a proxy for conviction in design review. AI broke that proxy, so the work that looks most finished now gets the shallowest critique.
- Everyone Wants to Be the Layer UnderneathGlean and Alation arrived at the same posture from opposite ends: be the substrate, not the assistant. You cannot own a daily habit and stay neutral.
- Salesforce Put Its CRM Inside ClaudeSalesforce beat on GAAP because it owns a piece of Anthropic, then shipped its CRM inside Claude. The app layer just volunteered to be the substrate.
- The Wince Is the Spec: Bottom-Up Evals a Model Can't WriteClaude writes half your evals. It's the half that catches nothing. Top-down vs bottom-up evals, and how I turn gut reactions into verifiers on Heidi.
- Cost Gets You In. Usage Keeps You.Glean's jump from $100M to $300M ARR got read as growth. The better read: why a buyer approves your product and why they keep using it have come apart.
- SpaceX Just Bought Cursor for $60B. What It Actually Bought.SpaceX closed its $60B all-stock buy of Cursor on Aug 14. Not a model story, an operating one: the choices that made a 2022 MIT project worth $60 billion.
- The Harvey Playbook: How AI Cracked Big LawHarvey hit $350M ARR and an $11B valuation selling to Big Law. The six operating choices behind it, and the one place the playbook could break.
- The IKEA Story Does Not Prove What You Think It ProvesSalesforce fired 4,000, IKEA reskilled 8,500, and LinkedIn decided this settles the AI question. The facts are real. The comparison is junk.
- 100 to 3,000 in a Week: Why Microsoft's Best Agent Is Not Called CopilotMicrosoft's Scout agent, formerly ClawPilot, went from 100 to 3,000 users in a week with no mandate. What its naming, identity, and org design teach.
- Every Artifact Is Somebody's Promotion PacketThe PM ladder runs on documents because documents are the evidence promotions are built from. When AI collapses the artifact, the currency disappears.
- Malleable Software Was Never the Point. The Loop Is.Dave Killeen's Dex files its own bug reports: your agent tells his agent what broke, the fix ships. Why malleable loops beat malleable software.
- One Org That Got Landing RightSnowflake made landing its business model: it only gets paid when customers use the product. How consumption pricing solved what an org chart could not.
- The Eval That Caught What the Demo Did NotThe demo was flawless. The eval I ran against 200 real cases failed on a slice that was a fifth of our traffic. The failure the demo structurally hid.
- The Landing Ledger: What It Costs to Build vs What It Costs to LandBuilding costs collapsed. Landing costs did not. Line by line, where the money and attention actually go, and why orgs starve the cost that dominates.
- The Launch That Worked and Did Not LandEvery launch metric was green: press, signups, week-one activation. Two months later the usage curve was flat. The exact place it fell through.
- The Person Whose Job This Shift ThreatenedThe Product Builder shift is a thesis until it has a face. The best PM on my team, whose craft was the thing AI made cheap, and how I handled it badly.
- The Repricing, Beyond AirtableAirtable at 2.7x ARR is not an anecdote. Chegg, Stack Overflow, Squarespace, and Smartsheet are the same repricing, in two kinds. Which one is yours?
- The Sierra Playbook: What They Actually Do DifferentlySierra hit $100M ARR in seven quarters and $200M by mid-2026. Not a model story: six operating choices on pricing, accountability, and go-to-market.
- The Week the Prototype Beat the SpecA twelve-page spec we argued over for three weeks lost to a prototype I built in an afternoon. The number that ended it, and what I stopped doing.
- What Landing Actually IsShipping is not landing. Landing is when a customer's behavior durably changes and the value sticks. A working definition, and the four ways it fails.
- What Replaces the PM Ladder When the Deliverables Are GoneIf documents were the evidence promotions ran on, and AI collapsed them, leveling needs a new currency. What counts as evidence from L4 to Principal.
- 31,832 PMs Applied. Whatnot Hired One. The Premise Is the Point.Whatnot runs on the premise that it regrets product management existing: 22 senior PMs, $8B GMV, managers doing 90% IC work. Where it corrected me.
- Who Owns Landing? Right Now, NobodyLanding falls in the gap between product, marketing, sales, and success. Each hands off before behavior changes. Everyone's concern, and nobody's job.
- Airtable Sold for 2.7x ARR. That Number Is the Whole Lesson.Airtable did not fail. It has ~$480M ARR growing over 20%. What collapsed was the story investors were paying for, and the AI pivot could not save it.
- Twelve Builders, Twelve Products, Zero LandingsThe 2026 CPO Insights Report says product builders replace PMs by 2030. The role is real. The framing points at building, just as building stopped binding.
- What Anthropic's Dianne Penn Taught Me About the FrontierWho Dianne Penn is, what she leads at Anthropic, and the four ideas she argues for: evals as the new PRD, the jagged edge, product overhang, and judgment.
- How I Build Eval RubricsThe eval rubric method I actually use: grade thirty outputs first, tie every dimension to downside exposure, and go binary wherever you can.
- The PM Does Not Make Decisions. Make Sure They Get Made.The PM's job was never to make decisions, it was to make sure decisions get made. In the AI era, when agents build in a day, that job becomes the whole game.
- AI Can't Understand the User. That User Is Disappearing.The best defense of the human PM is that AI can't understand the user. But that user is a departmental role, and agents are dissolving the departments.
- The Agent Layer Is Not the Catalog. Enterprises Will Learn This the Hard Way.Alation's AIOS rebrand says what most agent builders miss: it is not trying to be the agent platform, it is trying to be what every agent plugs into.
- Writing for Machines Is the New Writing for ExecutivesHalf your readers are now agents. Writing that executes faithfully is its own craft: specs as eval sets, prompt hygiene, GEO basics, and the cold-read test.
- Is This Product Bet Group Stage or Knockout? Reversible vs. IrreversibleThe World Cup is two tournaments bolted together. Knowing whether a product decision is group stage or knockout is the same question as downside exposure.
- Stage Wins or the Yellow Jersey: You Don't Win the Tour by Winning StagesThe rider with the most stage wins almost never wins the Tour. A model for AI product management: cumulative outcome over heroics, on a team you never see.
- Judgment Reps: How PMs Train Decision Quality DeliberatelyJudgment is trainable, but only with reps and a scorecard. The decision log, calibration habit, premortems, and a 4-week plan to train PM decision quality.
- Stop Calling Yourself an AI PMThe PM role is fragmenting into AI-native, growth, monetization, platform, and GTM labels. Most of it hedges an org-design decision. Name the outcome you own.
- The Product Builder Was Never About CodingLinkedIn replaced its APM program with Product Builder and framed it as generalists. The real shift is collapsing the distance between deciding and making.
- Comment With a Frame: The Only Move That CompoundsApplause adds nothing and dunking loses the room. Concede the strongest objection, then add a frame the thread did not have. Two exchanges show how.
- The QBR Deck Template That Forces Decisions, Not ApplauseA 9-slide QBR deck template: scoreboard vs plan, decision review, kills, next-quarter bets with confidence and reversibility. Outline plus PowerPoint.
- Financial Fluency for PMs: Own the Margin Before It Owns YouFinancial fluency is now a PM job requirement. The five numbers to know cold, the finance working session agenda, and a 4-week plan to own your margin.
- The PRD Was Already Dead. Slack Proved It in Public.Slack is running tiny cross-functional squads that prototype continuously instead of committing to fixed roadmaps. The org-chart version of the PRD collapse.
- Stop Picking Winners. Design the Tournament.Cheap prototyping did not kill product judgment. It moved the decision from picking the winner to seeding the bracket of what gets prototyped at all.
- The Resume Is Dead. Here Is What Replaced It.If you hire PMs off resumes in 2026, you screen for prompting skill, not product skill. What still correlates: published thinking a model cannot compress.
- The Exec Update Template: Five Numbers, Three Calls, One AskAn exec update template read in 90 seconds: five-number scoreboard, three decisions with evidence, one ask. Plus the agent prompt that drafts it.
- Rank AI Features by Downside Exposure, Not EngagementEngagement rewards features people fiddle with. Rank AI features by downside exposure instead: how fast a silent 20% quality drop would cost you customers.
- GTM Is Not Someone Else's Job AnymorePMs are absorbing pricing, activation, and positioning. The PM who stops at requirements is describing half a job in a market that pays for the whole one.
- Storytelling for PMs: The Skill That Decides Whose Evidence WinsStorytelling for PMs is not polish, it is how decisions get made. Three frameworks, the retelling test, and a 4-week practice plan to win the room.
- Falkster's Messaging Gateway: A Prototype-First Ship StoryInstead of three integrations for Signal, WhatsApp, and Telegram, we bridged through one Matrix homeserver. What building it taught that a PRD could not.
- What Competing Against Claude Taught Me About FalksterAn honest gap analysis of Falkster against Claude: memory maturity, workspace surface area, long-running agents, and distribution. The gaps, not a battlecard.
- Downside Exposure, Extended: When the Model Is Wrong About YouDownside exposure covered your AI feature failing a user. The second half: when an AI you don't control represents you inaccurately to a buyer.
- The First 90 Days as an AI-Native CPOFirst 90 days as a CPO in 2026: audit reality, instrument cost and quality, kill dead ceremonies, and defend the judgment calls only you can make.
- The PRD Collapsed Into Three Artifacts (Brief, Prototype, Eval)The PRD collapsed into a one-page brief, a prototype, and an eval. Answering the four objections 21 PMs raised, with copy-paste templates.
- The PR/FAQ Template: Amazon's Working Backwards for Your BetsA complete PR/FAQ template: press release skeleton, external and internal FAQ, the narrative meeting protocol, and when not to use it. Markdown and Word.
- AI Evaluators Are Your New PM AudienceAI systems now decide if your product gets recommended before a human sees it. Product legibility to a model is a new PM deliverable, not SEO reskinned.
- The CEO Who Can't Read Their Own Product AnymoreAgents break the link between dashboards and your product. Numbers stay green while the experience degrades. Three things to read instead of more KPIs.
- PM Days 61 to 90: Own One Bet and Kill One CommitmentPM days 61 to 90 in a new job: put your name on one falsifiable bet, kill one inherited commitment, and close the loop with a day-90 note to your manager.
- Product Ops Is the Job AI Made NecessaryAs the PM role splits and roadmaps flatten, coordination has to go somewhere. It goes to product ops, quietly the highest-leverage seat, not an admin function.
- The Decision Log Template: Train Judgment Like a MuscleA decision log template for PMs: schema, worked examples, the weekly 10-minute ritual, and the quarterly calibration review. Markdown and Excel.
- I Ran My Staff Meeting Off a Live Dashboard for a QuarterI replaced weekly staff meeting status updates with a live agent-built dashboard. What it killed, what it surfaced, and the one mistake I would not repeat.
- CPO Days 61 to 90: The Kill List, the Bets, and the ReadoutMonth three for a new CPO: build the kill list with the inertia test, kill two things publicly, size 2-3 first bets, and write the SCQA day-90 readout.
- The Founder Mode MisreadFounder mode got read as permission to micromanage. The real lesson: stay close to the few decisions only you can make, automate the rest.
- PM Days 31 to 60: Ship One Artifact That CompoundsPM days 31 to 60 in a new job: skip the quick win, ship one compounding artifact. Four options, selection criteria, a worked example, and the failure modes.
- The Board Deck Product Section: An SCQA Slide KitA 7-slide board product section in 10 minutes: scoreboard, what changed, bets table, kill list, the one risk, and asks. No feature parade. Templates inside.
- The AI Product Operating Model Has a Survivorship ProblemThe AI product operating model diagnosis is right. The evidence is every company that lived. Survivorship bias makes a true claim look far more proven.
- I'm a Company of One Because I Refused to Vibe CodeI crossed ~$1.5M ARR solo in under two months. It only works because I built agentic engineering, not vibe coding. The substrate does the carrying.
- The Cost of Being Wrong Is the Only Number That Matters NowSpeed is free now. The binding constraint for CPOs is reversibility: ship cheap-to-undo decisions instantly, slow down deliberately on the ones you cannot undo.
- Kill the 'I Built It in a Weekend' FlexSpeed to demo is a vanity metric. The 'I built it in a weekend' flex measures the cheapest, least durable thing. Ask if it was still running the weekend after.
- The Mental Models That Break When Building Gets CheapMost decision frameworks quietly price building as scarce. When AI makes building cheap, four of them invert and start giving the wrong answer.
- The Vibe Coding Crossover Point: Google's New SDLC WhitepaperGoogle's whitepaper puts the vibe coding crossover at 3 to 10x. The part that costs you is the quiet graduation, and it is a CapEx versus OpEx call.
- The Product Strategy Memo Template (Pyramid Principle)A six-page SCQA strategy memo template after Minto: answer first, three grouped arguments with evidence slots, anti-bets, premortem risks, and the ask.
- Five Questions That Make a Product Review Worth Your TimeMost executive product reviews are status theater. Five questions convert them into decision-forcing sessions that surface judgment, cost, and risk.
- CPO Days 31 to 60: Instrument the Org Before You Steer ItMonth two for a new CPO: stand up three instruments, build the coalition map, ship one visible decision, and renegotiate the scoreboard with your CEO.
- The PM First-90 Kit: Contract, Map, and Day-90 Note TemplatesFour templates for a PM's first 90 days: a one-page manager contract, signal map, decision archaeology worksheet, and the day-90 note. Fill in 10 minutes.
- Your First 30 Days as a PM: Build a Signal Map, Skip the Coffee ChatsFirst 30 days as a PM in a new job: run decision archaeology, build a signal map of where truth enters the building, and write the manager contract.
- PM Skills 2.0 Is Half a Funeral and Half a BlueprintPaweł Huryn's PM Skills 2.0 review: which of the 68 Claude skills to install (red-team-prd, ship-check) and which half embalms a dying PM role.
- Your Next Competitor Has Eight People and Your Whole RoadmapThe most dangerous competitor is eight people with agents: no coordination tax, no legacy, shipping your roadmap faster at a cost base you cannot match.
- The CPO First-90 Kit: Ledger, Map, and Readout TemplatesFive templates for a new CPO's first 90 days: listening tour guide, trust and claim ledgers, coalition map, and the day-90 readout. Usable in 10 minutes.
- Cagan Built the Church. I Argue We Don't Need One.Marty Cagan's product operating model optimizes for a constraint AI erased. The case for product builders over empowered PMs, and where my thesis breaks.
- The Product Budget Is a Compute Budget NowIn an agent-native company, output scales with compute and judgment, not headcount. That breaks how CPOs and CFOs plan.
- The CPO Listening Tour Is Broken. Run a Ledger Instead.Replace the 40-coffee-chat listening tour with a listening ledger: nine fixed questions, falsifiable claims, contradiction tracking, and a Friday synthesis.
- The Prototype Graveyard: Why Cheap Demos Kill Good IdeasPrototype-first is my thesis, and it has a failure mode no one names. When building is free, the demo replaces the argument and good ideas die in review.
- Any Competitor Can Clone Your Feature in a Week. Now What?Any competitor can clone your feature in a week. The moat has moved to distribution, proprietary data, switching cost, and trust. Here's how to audit yours.
- Taste Is the Last Moat: Why CEOs Can't Delegate Product JudgmentWhen execution costs nothing, the scarce input is judgment about what to build. Taste is a balance-sheet asset, and the one thing a CEO cannot delegate.
- Being AI-First Is a Product Decision, Not a Tooling OneA Twilio CMO drew the line between using AI and being AI-first. Swap marketing for product and the argument gets louder. Here is the product translation.
- Product Judgment vs Frameworks: What No Framework TeachesProduct judgment vs frameworks: 20 years at Microsoft, Adobe, and Salesforce taught me what no PM framework can. Judgment comes from being wrong at scale.
- AI Isn't Replacing Developers. It's Eroding Them.Michael Lawrence's piece on AI eroding developer craft lands. The 2020 dev would have caught the null check in 12 seconds. The fix is evals, not nostalgia.
- IDSD Is Spec-Driven Development With a New Acronym. Kill Both.Intent-Driven Software Development (IDSD) is pitched as the fix for SDD. Same methodology layer, different sticker. The prototype is the spec.
- The PM/PO Split Is Broken. Merging Them Misses the Point.Paweł Huryn is right that splitting PM and Product Owner is broken. The fix isn't merging them. It's killing the Scrum frame the roles exist inside.
- The 5 PM Websites in Your Bookmarks Need to Become Agents.ProductHunt, Growth.Design, Medium, IndieHackers, TechCrunch. Ankush Panday's daily PM list. In 2026 you don't visit them. Five agents watch them for you.
- Yes, Scrum Is Obsolete. The Replacement Already Has a Name.Alex Polyakov's case that Scrum is obsolete lands. He stops short of naming what replaces it. The builder pod: outcome ledger, eval, no ceremony tax.
- Three Designer Archetypes in 2026. The PM Split Is the Same Shape.Jenny Wen at Claude hires three designer archetypes; the traditional senior isn't one. The same split hits PMs: builder, specialist, prototype-coder.
- The Five-Row Eval Template That Replaced My PRDFive-row eval template that replaces the PRD: Behavior, Input, Expected, Scorer, Threshold. Six failure modes that kill bad evals. Worked example included.
- Kill the AI Office Hours. They're 2026's Agile Transformation.AI office hours are 2026's agile transformation: ceremony, no shipped output. Three replacements: paired shipping sessions, eval reviews, kill list reviews.
- The PM Interview Question I'd Refuse to Answer in 2026PM interview red flags 2026: three questions that signal a translator PM role, three that signal a builder PM role, and the polite exit script for a mismatch.
- Ship Story: The Discovery Week I Ran With Three Agents and No CallsAI agent discovery week, no live customer calls. Three agents (triage, theme synthesizer, opportunity ranker), 20 hours total. Stack, inputs, where it broke.
- The 20-Minute Customer Call Triage AgentCustomer call triage agent: 60-minute call to tagged, theme-clustered artifact with a one-line action in 20 minutes. Stack, prompt, eval rubric, batch run.
- PMs Should Vibe Code Internal Tools, Not Customer FeaturesVibe coding with Claude Code is the best new skill for PMs. But shipping vibe-coded features to customers is malpractice. Build internal tools instead.
- Product Management Isn't Dead. It Escaped the Product Team.Aaron Levie called the emerging role 'agent operator.' The cleaner name: Product Builder plus Agent Operator. Same skill, multiplied across every P&L function.
- Six pushbacks I keep hearing on vibe codingSix confusions I hear most when I say vibe coding isn't a strategy: 'demos sell deals,' 'speed beats clarity,' 'evals slow us down.' Here's how I respond.
- Customer Discovery When Your Customer Is an AgentContinuous discovery assumes a human customer. When your customer is an agent, six methods apply: agent telemetry, failure-mode interviews, capability audits.
- Software Categories AI Is Killing: A PM's Field GuideThree forces are collapsing entire software categories. Which are dead, which are reshaping, which have moats, and what to do this quarter if you build in one.
- Distribution Beats Product, and AI Made It HarsherAdobe taught me distribution beats product. I unlearned it at startups for a decade. AI made product cheap to build and distribution the only moat.
- Per-Outcome Pricing: What Gets Clearer and What Gets TerrifyingThree SaaS-to-per-outcome pricing redesigns: support automation, sales enablement, contract review. Margin math, dispute mechanics, and contract terms.
- The Builder Trap. Field Notes from Two AI Calls This Week.Two calls this week. A CMO buying more sophisticated silos. An engineer building more sophisticated silos. Same trap. What outcome thinking looks like.
- From SaaS to Service-as-Software: The CPO's Field GuideThe CPO field guide to Service-as-Software: outcome-based pricing, what changes inside the product, the new org chart, and when to make the shift.
- Agile Was a Coping Mechanism. What Replaces It Isn't Waterfall.AI killed Agile's two founding constraints. Right diagnosis, wrong destination: waterfall is not back. What replaces Agile in 2026 is the spec-first loop.
- Kill the OKR. The Quarterly Cycle Is Now a Liability.The 12-week OKR cycle is now a liability. Replace it with a Rolling Outcome Ledger: 3-7 active bets, 2-4 week decision deadlines, no end-of-quarter scramble.
- What a PM Actually Does All Week, Now and in 2028An hour-by-hour breakdown of the modern product manager's week, and a side-by-side comparison of every task before and after the agent fleet rewires the job.
- AI Deletes the Director of Product, Not the PMEveryone asks if AI replaces the PM. Wrong layer. The role automated first is middle management, the Group PM and Director who mostly move information.
- Survivorship Bias in AI: Interview the Planes That Didn't Come BackWald's WWII bomber lesson still runs product management. AI worsens the bias, but agents finally make missing data affordable to study. Here's how.
- The CFO Conversation: Defending a 20-Point Margin DropThe single most important conversation of the entire pricing migration. The script, the part that almost didn't land, and the seven leading indicators.
- Field Report: What Broke When We Killed Our Per-Seat TierMigration drift, an unexpected churning cohort, a unit definition that broke at scale, dispute volume at 12x projection. After-action from the sunset day.
- Kill the Feature Request Queue: Your Backlog Is a SignalYour 847-item backlog rationed scarce engineering time. Three replacements: signal synthesis, prototype-first investigation, and an outcome bet ledger.
- The PM-to-CPO Bridge in 2026Most PM-to-CPO advice is generic. The 2026 CPO seat demands business-model literacy, agent fleet operations, and public strategic posture. The 12-month track.
- Direction Dashboard AgentCompiles seven leading indicators every morning, predicts outcomes 4-8 weeks ahead, runs a weekly Goodhart audit. Direction at AI-native velocity.
- Outcome Accountability Is a Luxury Good. Measure Direction.Outcome-driven roadmaps assume 6-12 month measurement cycles. Agents iterate ten times a week. The dual-cadence direction-metric system that closes the gap.
- Field Report: 90 Days Inside a SaaS-to-Agents TransitionWhat we believed, what we did, what broke, what we changed. An anonymized after-action report from the first 90 days of a $30M ARR cannibalization.
- Continuous Discovery Doesn't Scale for AI-Native ProductsTeresa Torres' continuous discovery is the right answer for human-centric SaaS and the wrong answer for agent products. The punctuated discovery alternative.
- Renewal Risk Agent for Migration CohortsCatches the accounts whose operational dashboard says fine but whose qualitative signals say otherwise. Three-dimension scoring, 90 days before renewal.
- The Jevons Cliff in Outcome PricingInference costs drop 50% per year. Your $0.50/resolution price is a moving target. Hold or pass? The framework nobody has published until now.
- Kill the APM Program. Hire, Train, Promote Builders.LinkedIn CPO Tomer Cohen killed the APM program. The 12-week Product Builder apprenticeship replaces it: four prototypes, one production ship, no rotation.
- Margin Watch AgentTracks gross margin per outcome daily, classifies compression cause, and forecasts the Jevons cliff. Pricing reviews stop being post-mortems.
- The Pricing Migration Sequence: An 18-Month Quarterly PlaybookPer-seat is dying, but it pays your payroll. The quarter-by-quarter playbook for moving $20M ARR to hybrid outcome pricing without crashing NRR.
- Against Product Intuition: Why I Stopped Trusting MineWhy I stopped trusting my product intuition after 20 years. It is pattern-matching on a world that no longer exists, and AI rotates the patterns faster.
- Board Narrative Drafter AgentThe most expensive document in product management compiled while you sleep. Quarterly board updates from data sources, comp set, and last quarter's narrative.
- The AI Noise Tax. Three Patterns Killing Product Credibility.Three AI patterns I'm done with: LinkedIn 'Claude superpowers' posts, SaaS apps with bolted-on AI sidebars, and PMs claiming prototyping kills empathy.
- The Triad Is Dead. Pods Are Dead. Agent Departments Now.Forrester still talks about human-with-agent teams. Wrong unit. Agents form their own departments and interface with human departments on exception.
- The Dual Transformation Operating ModelTwo clocks, one product org. Run a legacy SaaS on a six-week rhythm and an agent-native successor on a one-week rhythm without tearing the team apart.
- Pricing Migration Tracker AgentWatches every migration account daily, classifies drift type, and recommends a specific intervention. Catch quiet drifters in week one, not week six.
- Build a Discovery Agent Stack: Continuous Customer ListeningDiscovery agent stack: seven open-source Claude repos turn customer interviews, support tickets, and public reviews into a continuous loop. Install + recipes.
- Build a Measurement Agent Stack: End the Dashboard Hamster WheelMeasurement agent stack: seven open-source Claude repos turn dashboards into a daily outcome digest, a variance detector, and a stakeholder update writer.
- Build a Prototype Agent Stack: PRD to Working Demo in a DayBuild a prototype agent stack: eight open-source Claude repos take a PM from idea to working prototype in a day, with TDD, design, and security review.
- Meet the Agent Operator Team at Falkster.aiSix new hires at falkster.ai. They manage the AI agents that build the product. They are paid strictly in treats. The team has not missed a single anomaly.
- The PM Agent Stack: A Bridge to the Enterprise AI BrainFive-part series for PMs whose company is 6-18 months from an enterprise-wide AI brain. Build the personal PM agent stack today with open-source Claude repos.
- 10 AI Agents I Built That Failed. The Honest Retrospective.Ten AI agents that failed in production: auto-approve expenses, sentiment classifiers, autonomous pricing, stale-docs RAG. The lessons that stuck after each.
- The CPO's Coalition Map: Why You Can't Run a Migration AloneFive seats, ninety days, one playbook. The argument that wins each seat in the executive coalition behind any AI-era pricing migration.
- Why "Soft Pivots" Always Become Two Companies in One OfficeEvery CPO running a 'gradual transition' to AI ends up running two companies inside one org chart. The five patterns and how to escape them.
- The Cannibalization Playbook: How CPOs Win the AI TransitionThe honest CPO move when AI replaces your SaaS: set a sunset, kill the comp asymmetry, pre-sell the gross-margin trough. The seven-decision sequence.
- The Eval-First Product Org: Rebuild Around Quality, Not VelocityRebuild a product org around evals, not velocity. The Quality Spine, Product Builder pods, Economics Unit, Discovery Network. The 90-day rebuild plan.
- Kill the PRD. The Prototype Is the Spec.The PRD was a 2015 solution to a 2015 problem. Three artifacts replace it: a working prototype (built in Claude Code), an eval rubric, and a one-page README.
- What Replaces the Product Org in 2028: Ten PredictionsTen checkable predictions for product orgs by July 2028: median team size six, evals the highest-status skill, hybrid pricing mainstream, APM programs extinct.
- 200 PM Job Descriptions Reviewed: 98% Hire for a Dead Job200 PM job descriptions audited. 196 could have been written in 2022. The four tells of a dead JD, four tells of a live one, and a before-and-after rewrite.
- The PM-to-Engineer Ratio Is the First Thing AI BreaksThe PM layoffs of 2025 and 2026 are not a skills story. They are a ratio correction. When each engineer ships 3x more, the math that sets PM headcount changes.
- 39 PM AI Agents Deployed: What Stuck, What Died, and WhyAn honest accounting of 39 PM AI agents across 4 product orgs in 80 days. Stage skew, cadence patterns, and the failure mode I kept repeating.
- The Agent Sandbox (PM Version): A Complete User ManualThe agent management system I built to run falkster.ai, now public. Nine views, 39 agents, three workflows, a 4-layer brain. See what an AI-native fleet does.
- The CPO Mandate 2026: What Boards Expect From ProductThe 2026 CPO board deck: outcome ledger, per-outcome unit economics, eval scorecard, agent inventory, cycle time, headcount-to-output, and willing-to-be-wrong.
- The Seven-Agent Reset: A Lean PM AI Fleet, One Agent Per StageStarting over: the seven-agent PM AI fleet I'd build today. One per PM OS stage, each with named signals, a single surface, and a quarterly kill-switch test.
- My Best Product Decision Was a Kill, Not a LaunchKilling a product feature is the rarest leadership skill. The best decision of my career was a kill, not a launch. The industry rewards exactly backwards.
- Empowered Product Teams Were a ZIRP FeatureThe empowered product team was a ZIRP luxury, not a timeless truth. With capital expensive and AI shifting the constraint, the orthodoxy is breaking.
- Auto Bugfix Agent: Zendesk Ticket to Reviewable PR in 11 MinutesAn AI agent that reproduces customer-reported bugs, locates the broken code, writes the fix, adds a regression test, and opens a reviewable PR.
- Instant Prototype Agent: Customer Request to Prototype in MinutesAn AI agent that turns customer feature requests into working prototypes. Deploys a preview URL, opens a PR, files a Linear ticket, drafts a Notion doc.
- Launch Comms Agent: Six Channels Generated on Every ReleaseAI agent that generates website copy, LinkedIn post, customer email, in-app banner, changelog, and X thread when a feature ships. Six channels, four minutes.
- Signal-to-Ship Cycle Time Agent: Measure PM Velocity Across 7 StagesAn AI agent that tracks PM cycle time across the 7 stages of the Product Operating System (Sense to Amplify) and surfaces the weekly bottleneck.
- pragmatic-pm-ai-skills Review: A Claude Skill That Tightens PM OutputReview of Valentin Brain's pragmatic-pm-ai-skills: a Claude Skill library that makes PM-AI output incentive-aware, evidence-tied, and free of generic advice.
- The Ten-Day Dev Loop: Three AI Agents Collapsed Our 8-Week CycleHow three AI agents (Instant Prototype, Auto Bugfix, Launch Comms) turned a customer Slack DM into a shipped, announced feature in 10 days instead of 8 weeks.
- KPI Watchdog Agent: Catch Metric Drops and Ship a Fix PrototypeA watchdog agent monitors your KPIs hourly, investigates the root cause of any drop, and ships a working prototype fix before you finish your morning coffee.
- The New Org Chart for AIAI coding tools boosted developer output but org velocity stayed flat. Three fixes: engineer adoption, faster review process, and flattening coordination.
- How PMs Ship Their First Pull Request With AI ToolsFour-level PM PR ladder, PLANNING.md templates, PM PR review skill file, and CTO pitch docs. Built from real coaching engagements across B2B SaaS orgs.
- Your Product KPIs Are Your Job, DailyA product builder without a daily KPI ritual drives with the rear-view mirror. Pick three KPIs, watch them every morning, elevate to OKRs when they slip.
- Mob Prototyping: One Day, One Room, One PrototypeOne day a week, your PM, designer, and engineer build a working prototype together. Cheaper than spec-driven handoffs. Better output than solo prototyping.
- Product Builder Job Ladder: Four Fork-Ready JDs from L4 to PrincipalFork-ready job descriptions for Builder PMs at four levels: L4 to Principal. Scope, architecture, mentorship, and experience floors calibrated per level.
- The PM Role Is Being Rewritten. Are You Rewriting Yourself?AI-forward companies are hiring for 'Product Builders.' This isn't a quirky experiment. It's the new standard. Here are the six skills that actually matter now.
- Build a PM Second Brain from Meeting RecordingsPMs forget 90% of meeting context within a week. How to record, transcribe, embed, and query meetings into a searchable knowledge base that compounds.
- I Gave My AI Agents a Performance Review. Three Got Fired.If an agent does the work of a team member, manage it like one. The scorecard, the coaching loop, and the firing criteria for the agents on your product team.
- Stakeholder Communication AgentGenerate tailored updates for different audiences: exec summaries, board updates, investor reports, team briefings. All from the same data.
- Retrospective Synthesis and Learning AgentExtract learnings from sprint retros automatically. Update playbooks, surface patterns, and drive continuous improvement.
- Win/Loss Analysis AgentBi-weekly analysis of won and lost deals. Extract product insights from sales outcomes. What's winning business, and what's holding you back?
- Feature Adoption Tracking AgentDaily adoption curves for new features. Identify stuck cohorts and recommend interventions before adoption stalls.
- Automated PRD GeneratorConvert prioritized opportunities into PRDs automatically. Drafts based on research context, design specs, and technical requirements.
- Automated Release Documentation AgentAuto-generate release notes, customer comms, and doc updates as features ship. Saves hours on documentation and keeps comms consistent.
- Tech Debt Impact and Prioritization AgentWeekly analysis of tech debt impact on velocity. Which debt items actually matter? What's the priority order to reclaim speed?
- Testable Assumptions Tracker AgentConvert opportunities into testable assumptions. Track validation status weekly. Know which assumptions are holding up your roadmap.
- OKR Progress and Prediction AgentDaily OKR tracking with outcome scoring. Weekly confidence predictions for OKR achievement. See what's on track and what needs intervention.
- Opportunity Prioritization and Synthesis AgentWeekly synthesis of all your DISCOVER agent outputs into a prioritized opportunity stack. OST-ready opportunities with impact estimates and dependencies.
- Automated Sprint Planning AgentConvert prioritized opportunities into user stories and sprint plans every Monday. Accounts for team capacity, tech debt, and dependencies.
- Customer Segmentation AgentWeekly updates to your customer segments and personas. Cohort analysis, segment evolution, and behavioral groupings - automatically maintained.
- Customer Interview Synthesis AgentWeekly automated synthesis of your customer interviews. Key themes, hypotheses, and actionable insights - without the tedious manual work.
- Automated Customer Journey MappingBuild rich customer journey maps bi-weekly from session replays, support patterns, and research data. See exactly where users get stuck.
- Every Type of PM Needs a Different Agent StackTechnical PMs, Growth PMs, Platform PMs, and Product Ops have different jobs. Their AI agent stacks should be different too. Here's what works for each role.
- Every CPO Job Is a Turnaround: The First 90 DaysNobody hires a CPO when things are going well. Every CPO role is secretly a turnaround. What the first 90 days actually require, in the AI-native era.
- NPS and CSAT Deep Dive AgentDaily and weekly analysis of your NPS and CSAT scores. Segment breakdowns, feature drivers, and what's actually making your customers happy or frustrated.
- Automate Support Pattern DetectionA daily agent that extracts signals from your support queue: which problems are rising, which segments are hurting, and what real trend lies beneath the noise.
- Claude Skills Every PM Should Build TodaySkills are the most underused feature in Claude. Here's how to build five that genuinely improve your daily PM workflow - with exact prompts and templates.
- Founders Don't Want a CPO. Here's What They Want.The CPO founder relationship fails for one unspoken reason: founders want their product judgment cloned and scaled without losing control. What I learned.
- Build Your Market Intelligence AgentBi-weekly deep dive into your competitive landscape. Win/loss analysis, market shifts, feature parity, and strategic recommendations so you're never surprised.
- Agent-to-Agent Dispatch: The Product Org Chart Nobody Is DesigningEveryone is building single AI agents for PMs. The real shift is agents handing work to other agents, with the PM as dispatcher. Here is the architecture.
- The PM Automation Stack: OpenClaw vs Claude vs Everything ElseOpenClaw went viral. Claude Code went deep. n8n went wide. What each tool actually automates for PMs, what's vaporware, and the exact setup that works today.
- How a 2-Hour Prototype Killed a 3-Month ProjectFive customer calls and a two-hour prototype showed our feature design was structurally wrong. How prototype validation saved 600 engineering hours.
- Build Your Release Checker AgentThe final gate before you ship. This Thursday agent verifies QA, docs, GTM materials, and sign-offs, giving a clear go/no-go for each feature.
- Two Weeks of Agent Tuning: What I LearnedMy first agent reports were 60% noise. After two weeks of calibration, they became the first thing I check every morning. Every adjustment I made and why.
- From Zero to Weekly Discovery in 30 DaysWe went from 'we talk to customers quarterly' to 'every PM runs weekly discovery calls.' It wasn't a mandate - it was a system. Here's the 30-day playbook.
- The PM-as-Translator Is DeadFor 15 years, PMs were professional middleware reformatting customer input into decks for engineers. AI just stripped away every translation layer.
- What Happened When We Killed Our Most-Requested Feature200+ customer requests. Sales demanding it. The CEO mentioned it in an all-hands. We killed it anyway - and activation improved 15%. Here's why.
- Build Your Daily Red Flag AgentThe first agent every PM should deploy: a morning scan of support, backlog, Slack, and production that tells you exactly what needs your attention today.
- How I Caught a Churn Signal 3 Weeks EarlyA Red Flag agent caught a 400% support spike on a tier-1 account. Three weeks later they renewed at full terms. Here's exactly what happened.
- Product Management Without Revenue Made Me BetterThe highest-stakes product of my career had no revenue model. Mission-driven product management forced pure outcome thinking, the way AI agents force it now.
- The PRD Is Dead. Here's What Replaces It.Product Requirements Documents were a necessary evil in a world where building was expensive. That world is gone.
- The Quarterly Business Review Template That Gets You PromotedA QBR template for product managers: 5-section structure, the metrics leadership cares about, narrative framework, and how to land a clear ask. Free download.
- Build Your Product Health AgentDaily 4 PM pulse check: engagement, activation, performance, and support trends synthesized into one story. Know exactly where your product stands each day.
- Setup Guide: Connecting Claude to Your Data SourcesStep-by-step guide to wiring Claude into your actual work tools via MCP. Based on my production setup at Smartcat.
- Setup Guide: Self-Hosted Agents with OpenClawFor teams that need on-premise data control. Same agents, same data sources, self-hosted infrastructure.
- The AARRR Dashboard You Actually NeedForget vanity metrics dashboards. Here's how to build a pirate metrics dashboard that tells you where your product is leaking value - and what to fix first.
- Build Your Competitive Intelligence AgentStop manual competitive research. This agent monitors competitors, tracks customer mentions, and delivers a weekly intel report so you always know your market.
- 20 AI Prompts That Replace 20 Hours of PM WorkCopy-paste AI prompts for product managers into Claude or ChatGPT. Tested across discovery, roadmapping, retros, and stakeholder updates. Save 20 hours a week.
- The Guerrilla PM PlaybookNo research team. No data analyst. No design support. Here's how to run world-class product management anyway with AI, scrappiness, and 2 hours a week.
- OKR Writing That Doesn't SuckMost OKRs are disguised task lists. How to write outcome-focused OKRs that drive product decisions, with templates, anti-patterns, and real examples.
- Build Your Team Triage AgentYour #team-product channel is a firehose. This agent reads every message, categorizes issues, assigns owners, and surfaces what's unanswered, twice daily.
- Empowered Teams When Your CEO Doesn't Buy InYour CEO wants feature roadmaps. You want empowered teams. Here's the guerrilla playbook for building autonomy from the inside without getting fired.
- Prompt Logs Are the New Switch InterviewStop scheduling discovery calls to learn what customers want. They are already telling your AI in plain language. Mine the prompt logs instead.
- Build Your Engineering Capacity AgentEngineering capacity agent: flags overloaded engineers, catches PTO gaps weeks early, and tells you if the roadmap won't fit before the sprint starts.
- Running Your First Product TrioProduct, Design, and Engineering making decisions together weekly, not in a meeting, but as an operating rhythm. How to start even if your org doesn't do trios.
- PMs Won't Be Automated - They'll Be AmplifiedThe hot take that AI will replace PMs is wrong. But the PMs who survive will look nothing like the PMs of today.
- Build Your Documentation Gap AgentFeatures ship without docs and customers find the gaps. This agent scans tickets and the release calendar to catch documentation gaps before they become fires.
- Shipping Velocity vs Being Right: My Two Years Shipping ZeroMicrosoft Research paid me to ship nothing for two years. It was the best product training I ever got. Shipping velocity is not the same as being right.
- The AI-Powered Weekly Review: A System for PMs Who ShipA step-by-step weekly review system that uses AI agents to gather data, surface insights, and prepare your week - in 30 minutes instead of 3 hours.
- Build Your Weekly Ops Digest AgentDaily agents catch fires. This weekly digest spots the trends: recurring issues, degrading resolution times, and systemic problems that daily reports miss.
- Build Your Product Ops AgentDaily product ops report ranked by ARR at risk: top complaints, feature gaps, usage anomalies, and at-risk customers synthesized from five data streams.
- Build Your Daily Focus AgentYour AI chief of staff: reads your calendar, scans Slack, checks the roadmap, and delivers the 3 things that actually matter today before your first meeting.
- How to Build a Working Prototype in 60 Minutes (Step-by-Step)A concrete walkthrough of building a real prototype with AI - from problem statement to deployed, testable app. With the exact prompts and workflow.
- Build Your Customer Commitment AgentSales promised a feature by Q2. CS said 'next month.' This agent tracks every commitment, cross-references the roadmap, and flags what is overdue.
- Why Acquisitions Fail: The Integration AutopsyWhy acquisitions fail at integration: I watched it three times at Salesforce. The acquired team loses its constraint, inherits parent process, stops shipping.
- Put Stakeholder Updates on Autopilot: The Complete Setup GuideHow to build an AI agent that generates weekly stakeholder updates, project status reports, and exec summaries - so you never write one manually again.
- Build Your PM Issues AgentCatch slipping features, overdue customer promises, and cross-team dependency failures before they become fires. Scans roadmap and commitments every morning.
- Build Your Product Health Dashboard AgentGo deeper than daily metrics. Weekly agent analyzing feature adoption curves, cohort retention, engagement depth, and performance trends to shape strategy.
- Build a Customer Feedback Pipeline in One AfternoonConnect Zendesk, Slack, and app reviews into a single AI-powered insight engine. Step-by-step setup guide with code snippets.
- Jobs to Be Done Has a Half-Life Now (And AI Is Shrinking It)JTBD assumes the underlying job is stable. AI breaks that assumption. Why the job your customer hired your product for is decaying faster than your roadmap.
- Build Your Release Readiness AgentPrevents launch disasters. Checks PRDs, release notes, feature flags, and GTM readiness every Wednesday so nothing ships without proper preparation.
- The One-Pager That Replaced Our PRDs (Template Included)The exact one-page template we use instead of PRDs. Covers problem, evidence, solution, metrics, and risks - nothing else.
- Build Your GTM Release Monitoring AgentTrack if features are ready to sell, support, and succeed. Monitors discovery compliance, beta standards, and GTM materials daily across five readiness gates.
- Leading a Product Team Through Layoffs: What SurvivesLeading a product team through layoffs: the cut is not the hard part. Keeping the survivors building is. What I learned running product through three.
- What Happens After Acquisition: My Product Was KilledAfter acquisition your product often dies, and that can be correct. Microsoft killed the product I built. Here is why it was the right call.
- Set Up a Competitive Intelligence Agent in 30 MinutesBuild an AI agent that monitors your competitors across 8 sources and delivers a weekly brief to Slack. 30-minute setup, no code, runs forever.
- Build Your Roadmap Progress AgentYour roadmap says in progress but engineering hasn't touched it in weeks. This agent cross-references your backlog against actual dev activity daily.
- Build Your Executive Report AgentAuto-generated Monday leadership brief: roadmap status, top wins, key risks, and metrics in a 3-minute read. Your CEO walks in already prepared.
- Run a 15-Minute Sprint Retro That Actually Improves ThingsAn AI-assisted retro format that gathers data before the meeting, identifies real patterns, and generates action items that stick.
- What Acquirers Actually Buy in a Startup AcquisitionWhat acquirers actually buy is not your product or revenue. I sold MVC to Microsoft. They buy a capability, a team, a defensive block, or time.
- The Reorg Is a Product Decision Nobody Calls OneOrg design product strategy and Conway's Law: your reorg ships more than your roadmap. Why leaders treat structure as HR when it is product.
- Startup Exit Lessons: My $6.5B Win Taught Me NothingMy biggest startup exit was mostly timing and luck. The failure that returned almost nothing is where the real product-leadership learning lived.
2024
- Your 'AI Agent' Is Probably Just a Cron JobMost things marketed as AI agents are workflows or automations with a chatbot bolted on. Here's how to tell the difference and why it matters for how you build.
- Many AI Agents Are Actually Workflows or Automations in DisguiseAutomations, AI workflows, and real AI agents behave differently. Knowing which you have prevents inflated expectations and missed opportunities.
- The AI Revolution Is Faster and Deeper Than the Industrial RevolutionThe AI revolution compresses centuries of change into decades. Here's how companies and SaaS providers can adapt before it's too late.
- Is Mob Programming the Right Approach for Your Team?Mob programming promises collaboration and quality, but at what cost? A look at why fully empowered Scrum teams are almost always the better bet.
- The AI Product Engineer: One Person Doing What Used to Take a TeamAI is blurring the lines between PM, design, and engineering. People who work across all three with AI tools will own the next decade of product.
- The Rise of the AI Product EngineerAI is enabling one person to own the full product lifecycle. The AI Product Engineer blends PM, engineer, and designer skills - all amplified by AI.
- The Evolution of Product Management Over the Last 20 YearsFrom project coordinators to strategic leaders to AI-powered product engineers. A 20-year journey through PM's transformation and what comes next.
- SaaS Is Becoming Service-as-SoftwareSoftware used to help people do work. Now it does the work itself. This shift changes how you build, price, and think about product. I'm living it at Smartcat.
- AI Agents and the Future of Work: A Pixar-Inspired JourneyA narrative-style exploration of what happens when AI agents become your coworkers - told through a Pixar-inspired story about Casey and the future office.
- When Your Data Becomes the ProductMany nonprofits offer free services but monetize the insights from your data. With AI making deeper analysis possible, the stakes are higher than ever.
- How to Avoid Survivorship Bias in Product ManagementThe British bomber study teaches us that the most critical data is often what we can't see. Here's how survivorship bias shows up in PM and how to fix it.
- You're Only Listening to the SurvivorsSurvivorship bias is quietly wrecking your product decisions. You're building for the users who stayed and ignoring the ones who left. Here's how to fix that.
- Why Users Don't Know What They Want Until You Show ThemFeature requests are reactive. Visionary product development means anticipating needs users can't articulate yet - and showing them what's possible.
- Show, Don't Tell: Why Users Can't Describe What They NeedFeature requests tell you what's broken. Prototypes tell you what's possible. I stopped treating user feedback as a roadmap and started using it as input.
