We can't find the internet
Attempting to reconnect
Something went wrong!
Hang in there while we get back on track
Big Ideas
Separate build-to-learn from build-to-earn. Teresa Torres and Petra distinguish cheap, disposable interactive prototypes from production software that customers pay for. The latter still requires maintainability, non-functional requirements, reuse, security, scalability, cost control, and skilled human oversight. AI products add error analysis, meaningful evaluations, and prompt/orchestration iteration; Torres describes the first 60–70% as relatively easy prototype work, while the final 30% can take months to years. Apply: label every artifact as learning or production before work starts, and do not let a successful prototype waive production gates.
Cheaper building raises the evidence bar. Hiten Shah argues that AI can make a weak idea look real—a polished site, working demo, and persuasive analysis—while changing little for customers; compliments, signups, repeated use, displaced behavior, payment, and retention are progressively stronger signals. In Beam’s research, more than 100 people replied and 42 documented their workflows; 29 interacted with another Mac several times a day, 28 kept it nearby, and only four usually wanted the whole computer while 18 wanted one application or a few specific ones.
Tactical Playbook
Use AI as an internal context multiplier, not an unsupervised customer oracle. One workplace experiment connected Claude to server logs, code, Swagger, ticketing, and Sentry to answer impact and incident questions, then proposed a Slack/Teams or SaaS interface for non-technical colleagues. A separate team found that exposing the codebase directly to support produced confident but incorrect customer answers, especially when answers required multiple repositories, business context, configuration/data, or judgment beyond the visible code. Start with three gates: connect the sources; use the agent to accelerate technical staff; then expand access only as documentation and permissions are good enough.
Validate replacement behavior, not enthusiasm. Match the research method to the unanswered question and its cost: conversations for premise checks, observation for workflow detail, manual fulfillment for willingness to pay, and software when real use will teach more than another discussion. Once a product is in the workflow, ask, “If it were not installed, what would you have done instead?” Look for the old workaround to disappear, then measure repeat use, payment, and retention. Your own pain is customer zero—not proof of a market; the idea still has to earn customer one by surviving contact with other people’s workflows.
Case Studies & Lessons
Superhuman is extending meeting notes into follow-on work. Superhuman says users had long requested a notetaker and that Fathom’s category expertise helped drive the decision. Its stated opportunity is not merely capturing and summarizing meetings, but turning what was discussed, decided, and committed into useful work by combining meeting context with email, calendar, documents, and other workplace data. The teams are building the roadmap in parallel, with a planned Superhuman Mail integration. The product lesson: define the downstream job an AI artifact should trigger, then connect it to the systems where that job is completed.
Career Corner
Product-sense interviews reward deliberate narrowing. Aakash Gupta’s rubric spans prioritization, user empathy, structured thinking, creativity, judgment under ambiguity, and metrics fluency. His recommended shape is to defend one segment, rank pains by severity × frequency, choose one solution while naming its trade-off, and define a success metric with a counter-metric; practice one question aloud, timed, each day.
Scope the “AI PM” role before preparing for it. A current hiring discussion describes startups testing system design, API debugging, and model-latency understanding because small teams need contributors who can ship. But another practitioner argues that PMs should own the customer and business outcome, understand what technical evaluations measure and when they matter, and not be pushed into doing a data scientist’s job. Ask what the role will own over the next year; if it is meant to discover the path through repeated pivots, hiring advice favors a creator-builder with product sense rather than a generic “AI PM” label.
Tools & Resources
A lightweight agentic shipping review. The Product Compass guide points PMs to a free pm-skills repository and a practical sequence: compare product documentation with the codebase, audit unit/integration/end-to-end/live/CI tests, and request prioritized code, security, and performance findings. Keep a human in the loop for common user flows: the guide notes that agents can miss dynamic or briefly visible UI elements, so manually clicking through those flows remains necessary.