We can't find the internet
Attempting to reconnect
Something went wrong!
Hang in there while we get back on track
Big Ideas
AI-agent UX is moving from disclosure to earned context. Scott Belsky’s first-mile framing treats progressive personalization—and staged requests for data—as the new progressive disclosure. Trust becomes an innovation variable: users may accept more privacy trade-offs when the return is clear, while agent-to-agent referrals may become a major onboarding path. He also puts personality, actionability, hospitality, and contextual memory alongside the graphical interface as core UX. The PM implication is to sequence permissions and personalization around demonstrated value, and to design the social handoff and memory experience rather than treating chat as the product.
Novel form factors need both a quality bar and a job hypothesis. Tony Fadell presents Apple’s foldable iPhone as a deliberate late entry: best-in-class hardware first, followed by developer-created experiences. Early user discussion points to two plausible jobs—media consumption and side-by-side productivity—while another PM frames the opportunity as closing the gap between “small internet” and “big internet” tasks, where habits and trust matter as much as technical capability. Treat those as hypotheses, not proof of product-market fit: instrument which users actually use the extra screen for after launch.
Tactical Playbook
Keep discovery human-led even when AI makes prototyping cheap. A practical small-team loop is: align with the organization on the time discovery deserves; interview ideal and non-ideal, paying and non-paying customers; synthesize recurring needs; revalidate them through non-leading conversations and surveys; then prototype with a deliberately mixed alpha group and iterate. Use AI to take notes, surface missed points, generate concepts, and accelerate prototypes—but not to replace customer conversations, because it lacks product-specific and customer-specific context. This matters because one PM-community report describes an AI research tool amplifying leadership’s existing beliefs while burying unusual feedback. Require direct customer evidence and an explicit dissent check before an AI-generated theme becomes a roadmap priority.
Case Studies & Lessons
Onboarding a complex product is context archaeology, not document retrieval. In a new role, one product practitioner built a “subway map” connecting roles, handoffs, artifacts, outputs, signals, and decision points, then converted it into reusable tables to pressure-test the end-to-end experience. Existing notes may be stale, weakly validated, or AI-summarized without real convergence; AI can point toward useful artifacts while still producing polished but incorrect understanding. Tickets were useful for delivery but poor for a newcomer; production code was the more definitive account of what the product actually does. For onboarding or a major product area, map one critical workflow, label live versus relic context, talk to an experienced operator, and verify the result against production behavior.
Career Corner
Replace mass applications with targeted proof. A reported job-search comparison produced five responses from 70 applications, versus eight replies and four interviews from 11 direct messages. Find two or three likely hiring managers through the company’s People page and recent team or product posts. Then send a short, company-specific work sample, a genuine point of overlap, or a low-friction coffee request. The message should ask an easy-to-answer question, demonstrate homework, and arrive before the application is buried.
Tools & Resources
Teresa Torres’ upcoming workshops focus on two increasingly important PM skills: AI Evals: The New Discovery Habit on September 23 and Story-Based Customer Interviews on September 24. The first offers an evaluation blueprint for personal workflows and customer-facing features; the second addresses how to choose what to build as delivery gets cheaper, using continuously collected customer stories.
- Motivation triangle for sustained product execution: Separate the benefit (why the goal matters), the behavior (what must be done), and the belief that connects them; motivation is unlikely to persist when someone doubts the payoff or their ability to perform the behavior. Use this when a PM or team knows the plan but repeatedly fails to follow through: diagnose the missing belief or incentive, not just the missing information.
- Persistence-versus-quitting framework: Before starting a product bet or career experiment, set a mile marker—a fixed trial period. Continue while you are still learning and persistence can pay off; quit only when the mile marker is met, learning has stopped, and persistence no longer matters—all three conditions must be true.
- Burnout and execution risk: Burnout is framed as high expectations combined with low control; high expectations with high control are treated differently, so the proposed remedy is to increase control or agency rather than simply lower expectations. For launch or roadmap planning, use mental contrasting: visualize the desired outcome, then identify likely obstacles and what you will do when they arise instead of visualizing only success.
- Turnaround for limiting assumptions: When a recurring belief about a stakeholder, project, or one’s own capability blocks action, write it down; ask whether it is true, absolutely true, how holding it affects you, and who you would be without it. Then test opposite interpretations and select a belief that increases motivation and reduces suffering. The method treats beliefs as revisable tools rather than immutable truths.
Jobs and value proposition: One Fold owner separates the product’s goals into media consumption and productivity: more space for reading and social media, plus side-by-side apps such as email with a browser or an AI window. Other owners describe ebooks, documents, videos, gaming, and on-the-road work as meaningful uses, while retaining pocketability. One user says the foldable replaced a Kindle, tablet, and standard phone.
Segmentation and validation lens: The small-internet/big-internet distinction frames device choice as a function of task complexity plus habit, trust, and privacy; the same level of complexity does not guarantee that users will accept a mobile workflow. PMs can use this as a behavioral segmentation hypothesis: identify users who regularly switch devices, rely on a phone as their primary computer, or need larger text and screen space, then measure actual post-launch usage. The thread proposes creating an analytics segment to observe what customers do with the extra screen after release.
Risk and discovery lesson: Demand remains contested. One commenter argues that Apple’s foldable is technology-led rather than built against a specific user problem. Another questions whether the roughly $2,000 price and product compromises justify the use case. The discussion also illustrates that value can be both functional and emotional: iPhone commentary credits mobile-browser and multitouch improvements for making existing smartphone tasks easier and faster, while also treating feeling cool as part of the user goal.
- A startup can serve as a strong product-management apprenticeship: low hierarchy, rapid decisions, cross-functional exposure, fast learning, and a norm of challenging ideas rather than people made the journey from $0 to $10 million especially educational. Those informal, high-speed relationships do not transfer automatically to larger companies, so PMs should adapt their operating model as organizations scale.
- Autodesk’s product-portfolio pruning used three tests: does the company have a right to win, how adjacent is the opportunity to the current business, and is there a team with the right product vision to execute it? Anagnost distinguishes “hops” into adjacencies from “leaps” into new technologies when a paradigm shift threatens the existing business; Autodesk treated its subscription transition as a leap.
- Autodesk’s SaaS transition highlighted a product-scaling dependency: Anagnost shifted investment to the back office after concluding that even strong products could not reliably reach existing or new customers without scalable operating infrastructure. He then expanded Autodesk from design software into design-and-make software through large construction acquisitions; the move required overspending during the build-out but ultimately scaled the business.
- For AI products in high-consequence verticals, Autodesk favors domain-specific models and context over generic “probably right” answers, because errors can produce unsafe or unusable designs. The stated trade-off is that smaller, purpose-built models can reduce compute and prompting while improving precision, speed, and total cost of ownership; Autodesk says it trains custom models on customer data for productivity and offers opt-out and data removal if data were used to train others.
- During major product and organizational change, Anagnost repeatedly communicated the “why,” left parts of the “what” open for challenge and engagement, cross-pollinated groups instead of punishing people for prior affiliations, and focused on preventing strategic thrashing. He viewed the first one to two years as the window to earn trust while making difficult calls such as shutting down favored projects.
- The core career recommendation is to build product thinking rather than accumulate courses; the proposed PM reading range covers operating models, customer conversations, decision-making, design, marketing, discovery, behavior, agents, and evals, with product sense developing slowly despite changing tools and frameworks.
- Discovery and outcomes: Aakash credits Continuous Discovery Habits with moving Fortnite D30 retention by 10% and growing Affirm app MAU 3.5x, while cautioning that shipping 12 times a week is excessive. The Lean Startup principle is to ship quickly to learn—not merely to build an MVP—and Escaping the Build Trap is especially relevant in the AI era because output is becoming cheap while outcomes remain difficult.
- AI product practice: PMs working on AI products need evaluation skills; the recommended practice is to inspect interactions and record what went wrong before building dashboards. For agents, model-in-the-loop workflows are often sufficient, and autonomy should be purchased only where the product can afford the resulting errors.
- PM job search: Targeted outreach can outperform mass applications: one example produced 5 responses from 70 applications, versus 8 replies and 4 interviews from 11 direct messages. Identify two or three likely hiring managers by searching the company’s People page for the relevant function and recent team, product, or opening posts; if no one is posting, trace the listed recruiter’s internal connections. Effective message patterns include a company-specific work sample, an authentic personal overlap, or a low-friction offer such as coffee; each should ask an easy-to-answer question, demonstrate research, and arrive before the application is buried.
- Aakash’s career and personal-brand lesson is that audiences ultimately respond to the work rather than the job title: his newsletter revived after employer changes, a VP-role transition, reduced posting, and weakened platform recommendations.
- Asynchronous hybrid AI research: Hiten Shah gives Perplexity Computer a question and lets it investigate while he works on something else, applying the workflow to market research, product questions, and learning a new space. Use local compute when it is sufficient, then reach into cloud models and the web when stronger capabilities or external information are needed.
- Implementation pattern: Delegate a clearly defined research job, let the system continue working, and return to its findings rather than requiring an immediate response.
- Teresa Torres will host an AI Evals: The New Discovery Habit mini-workshop on September 23, 2026, introducing AI evaluations, providing a getting-started blueprint, and covering applications in personal workflows and customer-facing products and features.
- A Story-Based Customer Interviews workshop on September 24, 2026, teaches continuous collection of customer stories to uncover opportunities and guide product decisions; it includes hands-on practice and responds to the growing temptation to build every idea as delivery becomes cheaper and faster.
- Evaluate AI against a job, not a generic benchmark. Start with one narrow task you already understand, provide enough context, rerun the same work, and judge it against a known quality bar. A practical adoption test is whether you would hand the same job back to the model tomorrow.
- Choose model and deployment per job. The article reports a 27B open model trailing a frontier model by two points on one long-context reasoning evaluation but by 46 points on terminal work; latency also changes the trade-off, with fast simpler responses better for inline assistance and stronger slower models better for difficult research. Keep work local when it is fast, useful, or repeatedly convenient; use cloud models when failure is expensive or reasoning is difficult. The benchmark examples are explicitly narrow rather than general rankings.
- Diagnose the workflow before replacing the model. One experiment improved from 0/15 to 14/15 after changing a setting; prompts, output budgets, and workflows can conceal existing capability. Change one variable and rerun the task to distinguish a model limitation from an integration or operating-environment failure.
- Search for product opportunities in repeated micro-frictions. Writing assistance, file organization, text cleanup, change detection, and repetitive steps may look too small for an AI demo but become valuable when they occur throughout the day; product discovery should look for recurring, previously uneconomical reasoning tasks.
Local models may gain adoption first through repetitive work: nearly half of the people Hiten Shah asked said they would assign a local model repetitive tasks, and Shah recommends starting with a recurring task to test whether a computer can take it over. He also announced a live demonstration of six such use cases.
- Use a job-first evaluation loop for local AI: start with repetitive work you already understand, provide enough context for one narrow task, rerun the same kind of work, and judge failures against an existing quality bar. If you keep handing the work back to the model, it has earned that job.
- Evaluate models against the specific job, not a general benchmark: one comparison showed an open 27B model only two percentage points behind a frontier model on a long-context reasoning test but 46 points behind on terminal work. Latency also changes the product trade-off—fast, simpler responses may be preferable for inline assistance, while difficult research can justify slower, stronger reasoning.
- When an evaluation fails, change one variable before replacing the model. A 0/15 result became 14/15 after a setting change because thinking mode exhausted the output budget; prompts, workflows, and surrounding tools can expose or hide a model’s capability.
- Local models make previously uneconomical small reasoning tasks viable, such as text cleanup, file routing, change detection, and removing repetitive steps. A practical deployment split is local AI for reliable, fast, repeatable work and cloud models for messy research, difficult reasoning, or long tool-using jobs where failure is costly.
- Evaluate enterprise demand with leading indicators, not closed-won alone. Four months with zero closes is ambiguous because enterprise sales cycles vary; the useful test is whether qualified opportunities progress from first meeting to a second meeting with an economic buyer, then to demos, pilots, proposals, and an explicit path to close, with a forecast that grows over time.
- Instrument the funnel in three layers: activity (contacts, meetings, and follow-ups), pipeline (named accounts, qualified meetings with decision owners, written next steps, and stage progression), and outcomes (pilots, proposals, signed contracts, and revenue). Review why opportunities stall or slip rather than treating revenue as the only milestone.
- Surface enterprise blockers during discovery. Ask about legal, security, and procurement in the first one or two meetings and schedule working sessions with the buyer; failing to track these milestones can leave a rep engaging prospects who are merely being polite rather than actively buying.
- Separate partnership value from closing capability and keep the operating system company-owned. Partnerships can open doors, but partnership work and direct selling are different roles; clarify whether the hire owns partnerships, market opening, or enterprise closing, because partner-led selling is difficult before a startup has a customer base and repeatable sales motion. Require weekly reviews of new pipeline, deal next steps, follow-ups, and slipped or lost opportunities, while keeping contacts, deal history, contracts, meeting transcripts, and sales materials in a shared CRM and involving a founder in major deals.
- Customer insight sharing is fragmented across customer calls, interview notes, CRM comments, and isolated quotes; product, marketing, and leadership reportedly select evidence that supports existing roadmaps, creating recurring disputes over what customers actually want.
- The proposed operating model is a shared source of truth with tagged themes and interview clips that teams can skim quickly before making decisions such as changing pricing.
- For onboarding into a complex product organization, build a “subway map” of workflows: connect roles, handoffs, artifacts, data sources, signals, access points, and decision points across the end-to-end experience. Use the map to make sense of how the product works and pressure-test whether the experience fits together; it can then be converted into structured tables for reuse.
- Treat onboarding as context archaeology, not simple document retrieval. Before relying on existing notes, check whether the customer’s business has changed, whether the material was carefully validated or merely summarized, and whether it represents current convergence; distinguish continuously updated “live” artifacts from outdated relics. Context-sharing sessions with experienced coworkers help surface implicit knowledge, while exploring the artifacts yourself helps connect the dots.
- Use AI as a breadth and navigation aid, not as a substitute for context creation and preservation. In this experience, AI could point toward useful artifacts and summarize work, but its answers were sometimes mediocre and could produce coherent-sounding yet incorrect understanding; human collaboration supplied a different layer of implicit context.
- Standard delivery tools have different onboarding value: Linear tickets were useful for their intended purpose but lacked enough context for someone new, whereas inspecting production code provided a more definitive view of what the product actually does.
- An aspiring APM building two products for real users can use them to develop product skills by shipping properly, measuring usage, talking to users, writing documentation and specs, and owning roadmap trade-offs.
- Additional preparation includes seeking PM-like internship experience and reading Decode and Conquer and Lean Product Playbook; the advice also cautions that PM hiring is currently difficult.
- A practical continuous-discovery loop for small teams is to align with the manager and organizational culture on the appropriate discovery investment; interview a range of customers—including ideal and non-ideal users, and paying and non-paying users—to understand how and why they use the product; synthesize recurring needs; revalidate them through non-leading customer conversations and targeted surveys; then prototype with a deliberately mixed alpha cohort and iterate through testing.
- AI can support discovery by taking session notes, surfacing missed points, identifying themes, generating concepts from interview material, and rapidly creating prototypes for alpha testing. However, it does not replace direct customer conversations because it lacks product-specific and customer-specific context; its stronger role is summarizing collected evidence and assisting with market or competitor research.
- The approach is presented as applicable across team sizes, including teams without dedicated UX research resources; the practitioner argues that meaningful product unlocks and conversions come from understanding what users actually need through conversations, rather than relying on data alone.
AI increases the number of product opportunities a team can pursue, but customer understanding should determine which direction to prioritize.
- AI use creates a product-management quality risk when it replaces understanding: one PM described a lead designer using AI to produce highly technical work outside her expertise, raising the problem of defending reasoning that the author does not understand; another commenter stressed that AI outputs require intellectual honesty, rigor, and validation.
- Capacity pressure is driving adoption as much as individual preference. A commenter reported that half their product team had been cut and AI was being pushed to keep the team operating without added headcount; another reported a C-suite instruction to “just have an LLM do it” for a cross-functional initiative they believed required more engineers.
- One practitioner is adapting product communication by replacing long documents that “only AI is going to read” with more visible, interactive artifacts created rapidly with Claude, and reported positive feedback. The same discussion cautions that building AI products can add coordination and evaluation work with Data Science, so automation may reduce routine effort without eliminating PM workload.
- Validate AI product pull beyond headline ARR. Rapid early ARR claims may lack a renewal cycle, reflect sales within a cohort, or use inconsistent ARR definitions; assess demand through direct customer conversations, deployment, usage, engagement, and alternatives rather than financial analysis alone. Harvey illustrates the pattern: initial usage was mediocre, but reasoning models increased lawyer value, drove higher usage and engagement, and shifted customers toward demanding that law firms use the product.
- Treat AI as workflow redesign, not a bolt-on feature. The speakers warn that simply adding AI customer-service agents without rebuilding the workflow can cause customers to churn and create a downward spiral as NPS and revenue decline; effective transformation requires aligned boards, investors, and management willing to make difficult decisions. They cite Intercom as an example of bringing the founder back, rebuilding around an AI-native product, scaling it, and then selling it.
- Size AI opportunities around task value, not incumbent software spend. For example, the discussion contrasts $60–$100 billion in annual healthcare IT spending with the roughly trillion-dollar value of healthcare labor and tasks such as claims, billing, and administration, while noting that the company’s eventual capture rate remains uncertain.
- Expect consumer AI products to evolve beyond chat interfaces. The speakers predict that the next consumer paradigm will be native and proactive, performing work on the user’s behalf rather than merely offering a chatbot interface.
A product team reports that its AI-powered customer-research tool amplifies existing organizational bias: it prioritizes themes aligned with leadership’s beliefs and buries unusual or novel feedback, creating concern that bias has been automated at scale. The post asks for safeguards that do not require manually reviewing every transcript.
A mid-size B2B company is evaluating whether to adopt a no-code platform or continue building small business applications in-house. The demand centers on request tracking, approvals, inventory checks, and customer-facing forms; the workloads are described as low-scale but operationally fragmented, with many Excel-dependent users.
- Streaming/OTT product management largely relies on core PM fundamentals—understanding users, the team, and the technology—while also requiring familiarity with the niche’s industry and technical context.
- For content products, PMs should use the service themselves to build firsthand context, then understand their audiences and how, when, and why they consume content.