We can't find the internet
Attempting to reconnect
Something went wrong!
Hang in there while we get back on track
When building is cheap, outcomes are the job
Ravi Mehta defines Business Outcome Ownership as linking product improvements to team and company objectives. Every investment has to pass two tests: does it create meaningful customer value, and can that value become value for the company? He also says to stay with the problem after launch, compare the results with what you expected, and decide what to do next . His AI argument: impact used to be capped by how much a team could build. Now outcomes are limited by understanding and judgment, and a team "can... ship more features while creating less value" .
Mehta's most useful example is about economics. An AI support feature can grow usage while customers still need several attempts and still contact support, and the company pays for every interaction . Inference, human review, infrastructure and maintenance belong in the investment case. A feature "can win on usage and still destroy margins." That may be worth it only for a specific strategic advantage with a credible path to better economics .
Marty Cagan says much the same. Most companies use AI to speed up the project model, and teams get faster without getting better outcomes. He cites this "AI productivity paradox" as noted by McKinsey and Atlassian . Strong teams separate building to learn (prototyping to find a solution) from building to earn (building something the business can run on and monetize) . As the cost of building to earn falls, "the bottleneck is what do we build?" . On team shape, he says some teams now have three or four engineers instead of five to ten, while what they own is growing . The PM stays responsible for value and business viability: whether it's affordable, monetizable and compliant .
A warning about metrics
A PM at a very large enterprise says a goal to cut median epic cycle time by 15% led teams to clone aging epics and close the old ones. An internal article then celebrated a 35% drop, with no discussion of the real goal of resolving epics within 90 days .
Pricing an AI product with no usage history
An r/ProductManagement thread offers practical steps:
- Run an announced trial. Absorb costs for two to three months and say upfront that usage pricing will follow. Expect some users to "go hog wild" and then scale back, while moderate users get locked in .
- Use COGS as the floor, not the price. Build forecasts with finance, and pilot with a select group first . For school buyers, set tiers by what a teacher or class needs per term. Model peak demand from the calendar, not from traffic .
- Limit usage by tier. Put a hard cap on the free tier and soft caps (throttling or overages) on paid tiers. The soft caps show who would pay for more .
PMs closer to the build
Aakash Gupta argues PMs need design sense because they are now designing. At AI-native companies they ship to production, and at large enterprises they build AI prototypes . He had Claude Code build a feedback-triage app from one prompt and found three problems. The PRD sat about 470px below the fold. The ranking put a theme with $895K in ARR above one with $1.00M without explaining why. The pasted input took up half the screen . In a separate note he describes Rippling CPO Matt MacInnis's first changes: markdown pushed to a git repo, customer issues found through MCP, and PMs fixing their own copy. Gupta's takeaway is that PMs now need skills such as understanding repo structure and configuring tooling, which used to belong to engineers .
A tech-debt standoff with AI-reliant developers
A non-technical product owner says developers will not touch tech debt until the PO writes stories with acceptance criteria, finds and prioritizes the debt, prescribes fixes and sets time limits. The PO's manager wants them at senior-developer level within three months . The developers reportedly say it's a product-owner failure if a story can't be pasted into Claude and produce a first implementation in one pass . Their AI-generated debt list has 7,700 items, such as "Resolve escape: line 33, file XYZ", and they want the PO to rank them . The PO thinks the developers should own all of this , and most commenters agree.
Launch videos
Hiten Shah says Claude Code built a Beam launch video in nine minutes but left out the one scene showing what Beam does . After reviewing eight product videos, his test for each scene is: what does the viewer understand after it ? One example is Cursor's video, which reaches "All Checks Passed" and a merge button around 19 seconds in. Developers recognize that payoff, and he would hold on it a beat longer .
