We can't find the internet
Attempting to reconnect
Something went wrong!
Hang in there while we get back on track
Big Ideas
AI shifts the bottleneck; it does not remove the need to find it. Ramp’s presentation defines speed as the time from customer pain to a product that solves it; as coding got easier, constraints moved to defining, coordinating, reviewing, testing, and releasing. Ramp reports its Inspect agent builds 75% of PRs, including 1,000 submitted by non-engineers in the last month; Review Buddy automatically handles 93% of PRs, and Testo caught 425 bugs in 30 days. Those are company-reported metrics, not universal targets. The transferable move is to connect AI to company systems and customer evidence, automate a repeatable bottleneck, then look for the next one.
AI-generated output needs an explicit quality bar. In a Stripe design talk, the speaker says a design-document-connected MCP produced results that were vague and inconsistent; the team moved to a CLI built on its design system, with full templates and flows. Then assess the whole experience as a user: does it solve the problem, fit the user’s mental model, and cohere? Built is not the same as good. A separate product-model talk says PMs own business viability: will customers buy, can the business market, sell, and service the product, and is it legal, compliant, privacy-respecting, safe, and ethical—a particularly difficult test for AI. It also warns against letting problem validation crowd out solution discovery and urges teams to ask why people stop using the product.
Tactical Playbook
Keep the PRD alive through the learning loop: draft a speclet while widening the problem space; revise it if design changes the solution; add risks and engineering feedback at launch readiness; then link the post-launch impact review. A companion feature-results checklist asks teams to record good and bad outcomes, run a 5 Whys on “so what?”, and document lessons and next steps—so launch results can inform strategy.
In a PM discussion about meeting overload, practitioners recommend estimating capacity and communicating cut lines, making side quests temporary or self-maintaining, and attending meetings only when you need to decide, provide input, or own the work. Align remaining effort with the product-area KPI, customer and analytics evidence, and leadership priorities; visibility need not mean attending every status call.
Case Studies & Lessons
Toast VP of Product Maggie Crowley describes a cautious rollout into the restaurant and retail platform: 10 design partners in WhatsApp, one mobile-reporting use case, and about a year of walled-off iteration before scaling. She stresses the trust risk: slow, inaccurate, or underperforming AI can drive installed-base users away. Toast IQ uses in-product entry points and starter prompts tailored to users’ roles, platforms, and timing, with re-onboarding as capabilities change. The bar is business value, not AI novelty: one customer reduced marketing-agency spend by over 70% and could attribute sales to marketing.
Cosign launched as a startup-community reputation directory, with more specific signals than a generic professional connection: who shaped your career, who you would work with, and who is a person to watch. Users can privately signal willingness to hire or fund someone, with introductions when interest is mutual. The team makes positive endorsements durable on profiles but does not preserve criticism in the same way; it also says AI helps populate profiles from public sources to address cold start, while inviting edits. The design prioritizes high-conviction signals, not a complete reputation record.
Career Corner
Ramp’s presentation sketches three possible PM tracks as automation expands: technical PMs build the internal product “factory,” taste-makers set the quality bar, and GMs own outcomes across marketing, sales, growth, and operations. The speaker presents these as a forecast; they are also a useful lens for choosing whether to deepen systems-building, product judgment, or cross-functional business ownership.
Tools & Resources
Explore The Product Shelf’s technical PM library: 56 free, no-code guides, cheat sheets, and glossaries across APIs, architecture, SQL/data, product metrics, observability, security, and CI/CD/releases. Follow its optional sequence or jump to a live question; the resources are intended to help PMs ask better questions and discuss trade-offs with engineering, data, and security.
The supplied README presents the library as a free, no-coding-required resource for Product Managers, with 56 resources across APIs, software architecture, SQL & data, product metrics, observability, security, and CI/CD & releases.
- Usability: It describes the guides, cheat sheets, and glossaries as standalone, with plain-English explanations, illustrative product scenarios, and questions to take to a team. The suggested topic sequence is optional; it says SQL examples introduce syntax as needed, with no prior coding knowledge required.
- Public-facing use: The README links directly to individual GitHub guides and invites corrections through Issues or pull requests. This supports treating it as a public-facing, self-serve resource, though the supplied material does not verify live access to every link.
- Reuse and caveat: The repository's original educational content is licensed CC BY-NC 4.0, with attribution and other license conditions; that license does not cover linked books or other materials. Its example metrics, policies, and launch conditions are described as discussion aids, not universal benchmarks, and should be adapted with Engineering, Data, and Security.
- Product managers must own business viability alongside customer value, usability, and feasibility: check that customers will buy the product and that it can be marketed, sold, and serviced legally and compliantly while respecting privacy, safety, and ethics; this challenge is especially significant for AI products. In open markets, products must also be dramatically better than competitors to motivate switching.
- In discovery, establish the problem, target user, and success definition, but avoid spending too much time gatekeeping problem validation; reserve effort for solution discovery, where innovation happens. Ask customers who churn or do not use the product why—they are an underused source of insight.
- Treat roadmaps and PRDs as communication, not as predictions of unvalidated features and dates. A PRD is useful after learning, testing, and gathering evidence that the solution can achieve the intended outcome; speculative feature plans waste engineering capacity, and predictability should not come at the expense of outcomes or trust.
- Empowered product teams need better management, not simply less management: product leadership supplies context, including a strategy that prioritizes the problems to solve.
- Practice humility by knowing and admitting what you do not know, and protect time for thinking: a craving for process and frameworks can substitute for product judgment.
- The speaker argues that AI makes product strategy and discovery more important, and distinguishes building to learn (discovery) from building to earn (delivery); the PM’s job is to ensure what gets built achieves the needed outcome, not merely to produce output.
- Cagan says product managers must assess both whether customers will buy a solution and whether the business can market, sell, and service it—and whether it is legal, compliant, privacy-respecting, safe, and ethical. He says business viability is especially challenging for AI products and calls for holistic systems thinking.
- In discovery, establish the problem, who has it, and what success means, but do not spend so much time acting as a problem gatekeeper that solution discovery suffers; Cagan sees solution discovery as where innovation happens. He urges teams to ask people why they do not use or have stopped using a product, calling that question a major route to innovation.
- PRDs and roadmaps are not inherently the problem; using them to present untested feature ideas as known answers creates a project-model failure and can waste engineering capacity. Use evidence from learning and testing to establish that work can achieve the intended outcome; then a PRD can serve as a useful communication device.
- Empowered teams need better management, not simply less management: product leadership should provide context, including a product strategy framed as a prioritized list of problems to solve. Cagan also warns that product work involves corporate politics and governance, and that products must be dramatically better than competitors to persuade customers to switch.
- Cagan argues that product work depends on thinking, which process, frameworks, predictability, or AI can become substitutes for. Distinguish building to learn (discovery) from building to earn (delivery): discovery should help ensure that what gets built achieves the required outcome. He says AI makes product strategy and discovery more important.
- The first two Lenny & Friends Summit talks are online: Dan Shipper on “How to Build Products at the Moving Frontier” (video) and Claire Vo on “The Last Roadmap” (video).
- Three more talks are online: Stripe’s Katie Dill on scaling intent, quality, and artistry with “Al”; Ramp’s Geoff Charles on designing an AI software factory for speed; and Marty Cagan on “Strong opinions, loosely held.”
- For AI in an established SaaS product, Toast started with 10 design partners in WhatsApp, a mobile reporting use case, and a walled-off environment for rapid iteration; the team continued this approach for about a year, while recognizing that slow, inaccurate, or poorly performing features could erode trust with the installed base.
- Don’t expect users to discover an AI assistant or know what to ask: Toast used entry points throughout the product and starter prompts tailored to what users were doing across platforms and times of day, and emphasized re-onboarding users as capabilities changed.
- Judge AI by whether it helps customers make or save money or time, not by the novelty of the technology; Maggie Crowley recommends staying close to users and observing their work rather than over-indexing on predicting market winners.
- Toast IQ Grow applies AI to restaurant marketing through channels including email and text; Crowley cited one customer that reduced marketing-agency spend by over 70% and could attribute sales to its marketing. A Toast IQ demo also showed moving from insights to menu changes in chat, with action cards generated for the requested task and options for bulk or scheduled actions.
- For PM leadership in the AI era, Crowley recommends staying close to how teams build: she takes on PM work during leave or vacancies and directly manages frontline teams in some areas.
- Operating model: Ramp frames product speed as shortening the time from customer pain to a product that solves it—not merely coding faster. PM leaders should repeatedly identify the current bottleneck, remove it, and then find the next one; when AI eases engineering work, the constraint can shift to defining, coordinating, testing, or releasing work.
- Discovery and definition: Customer pain is scattered across sources such as support tickets, calls, logs, surveys, and emails. Ramp built an insight system that combines company data, clusters related context, and makes it accessible and traceable; use those signals to decide which customers to interview, not as a replacement for talking to customers. For scoping, connect AI to company data, research, product strategy, spec conventions, and code so it can help identify jobs to be done, assess feasibility, and produce a working prototype. Give engineering the combined evidence, usable requirements, and prototype rather than relying on a long spec or prototype alone.
- Execution and quality: Ramp reports that its Inspect coding agent has had one million sessions, built 75% of PRs, and enabled non-engineers to submit 1,000 PRs in the prior month; the speaker cautions that coding agents work best with a strong architecture and codebase. As coding volume grows, Ramp uses Review Buddy to route context-aware reviews, with 93% of PRs automatically handled, and Testo to test product flows across 100 combinations using production data; Testo caught 425 bugs in 30 days.
- Coordination and iteration: Make the organization legible to agents by connecting questions to formal records and sources of truth; agents can answer project or launch-status questions with evidence, update roadmaps, and follow up on late deliverables. Ramp says AI now fully answers 85% of questions previously asked to PMs, while unresolved questions are routed or fed back into the system. For small, repeatable issues, automate routing, backlog matching, deduplication, prioritization, planning, coding, testing, and release, keeping a human check in the loop; Ramp reports that 60% of identified UX issues are fixed within 24 hours.
- Strategy and career implications: Under resource constraints, choose a dimension where the team can excel and start with the bottleneck most likely to materially improve the company, rather than trying to remove every constraint at once. The speaker sees PM work expanding into three paths: technical PMs building the systems that help teams build products, taste-makers setting the bar for product quality, and GMs owning business outcomes across functions.
AI-driven build speed and diffuse ownership make an explicit product point of view and quality bar more important: define what the product is for, who its users are, what you want to mean to them, and what they care about; develop standards by noticing needs beyond what users say and studying what feels good or great in products and other contexts.
- Encode those standards in the systems people and AI use to build. At Stripe, an MCP connected to design documentation produced results that were not specific enough, and the same prompt could yield three different results; the team moved to a design-system-based CLI that uses documentation at the relevant time and includes full templates and flows, aiming to make generation more consistent with how the product should behave.
- Add a post-build editing gate: because AI makes it possible to build many ideas quickly, quality filtering shifts later, when rejecting work is harder. Assign someone to assess the end-to-end experience as a user—whether it solves the problem, fits the user's mental model, and feels coherent—and decide what needs further work; built does not mean done or good.
- Use AI to expand creative possibility, not just make familiar work faster: provide specific prompts, brand standards, and source material; push outputs further and use adversarial agents to critique them. Leaders should make room for exploration and protect unusual ideas rather than defaulting to cookie-cutter patterns.
- Distribution: Muse’s Shopify and Instacart checkout integrations illustrate how an agent can reach users inside purchase flows they already use, rather than relying only on a standalone destination app. For agentic products, identify moments when users already have intent and consider completing the task within an existing workflow.
- Platform incentives: Shopify and Instacart opened checkout access, while Amazon blocked Muse; Amazon cited concerns about how the agent browsed and handled account information, which Meta disputed, leaving the technical disagreement unresolved. The episode argues that agents bypassing product discovery may conflict with platforms whose revenue depends on that browsing. Assess a platform’s incentives and access constraints early, especially when your product removes friction the platform monetizes.
- Enterprise adoption: The speaker suggests that consumer use of agents may help users become comfortable delegating multi-step work, potentially weakening enterprise objections to agent adoption; this is not proof that trust is solved, as the episode also notes unresolved trust concerns and issues found by Meta testers. For B2B products, treat consumer familiarity as a possible change-management tailwind, not a substitute for earning users’ trust in the work context.
A PM new to an organization described 1:1s as 90% manager talk, leaving too little room to check their thinking and assumptions . For more useful meetings, commenters recommend sending an agenda in advance, putting P0/P1 or other priority topics first, and identifying whether each item is status the manager may need or an area where the PM needs advice; one PM reported that an executive appreciated receiving such lists because no one else sent them . If the conversation crowds out those items, gently redirect or schedule a follow-up, then send a recap of what was discussed and what remains open .
- AI coding-agent specs: Pathmode addresses vague requests that leave agents to make implicit product choices by linking user evidence to specs, stating intended outcomes and boundaries, and routing contradictions or missing decisions found during implementation back for review.
- Feedback prioritization: Feedsense proposes combining support, Slack, in-app, and CSV feedback into a brief highlighting common and rising issues, to counter roadmaps skewed by the loudest or most recent requests; its maker is still testing whether the brief is more useful before or after a prioritization call.
- AI-assisted PM docs: Kelve proposes having PMs read source pages instead of receiving summaries, surfacing likely reviewer questions before drafting, and placing each source page beside its related point—a workflow intended to preserve learning and make claims easier to inspect.
- A hardware PM team used agile-adjacent, two-week cycles with measurable feature objectives: run discovery, form hypotheses, experiment, and validate quickly. It sent demo devices that were only control interfaces with sales teams, then pushed OTA updates from feedback while the hardware continued iterating in the lab.
- One hardware PM described legacy-company product work as more program-management-oriented, with strong P&L ownership; GTM, discovery, R&D, and supply-chain security also differ from software. A contributor framed PM’s focus as customer outcomes and voice of the customer rather than technical problem-solving, while noting that the role varies by industry and organization.
- For software PMs moving into hardware, a hardware-side hiring commenter recommends finding an industry overlap and demonstrating hardware product-development ability, including sourcing parts and dealing with parts that are difficult to change. The commenter cautions that software PM experience may be viewed negatively because the roles and practices differ.
A Senior PM at a reputed FAANG company reports five years without promotion despite strong performance reviews and two manager-sponsored promotion cases; higher-ups denied them for lack of a business case because her product was performing poorly, and leadership blocked lateral transfers because she was a needed subject-matter expert. This individual case suggests that product performance and assignment can constrain career progression even when performance reviews are positive.
She is considering quitting without another offer after a year of unsuccessful external applications, which she says have been difficult to pursue alongside demanding work; she has more than a year of savings and is targeting external Staff or Principal PM roles.
In AI product development, newly coined terms can shape what gets built as they spread, making naming a potentially high-leverage product decision .
- Choose a framework by the question: JTBD identifies the customer job before ideation ; AARRR locates funnel drop-off ; Kano distinguishes expected must-haves from delighters ; RICE ranks a long list, with honest confidence estimates ; MoSCoW scopes work against a fixed deadline, while guarding against everything becoming a “Must” ; SWOT helps decide whether to proceed, provided it ends in a decision . The recommended order is understand the problem, rank solutions, then cut scope; treat anything short of a clear yes as a no .
- Treat the PRD as a living record of team progress and increasing clarity, not a one-time document . Start with a planning-cycle speclet for major work while reopening the problem space; once the problem is selected, detail the solution but let design replace the PM’s initial sketch . Update the PRD if the solution changes during review, add risks and mitigations and get engineering feedback at launch readiness, then link the post-launch results review .
- Make a feature-results writeup a learning tool for future strategy: include a clear structure, the good and bad outcomes, a 5 Whys analysis of “so what?”, lessons learned, and next steps .
- The author argues that ChatGPT made polished applications cheap and that employers’ use of AI screening has weakened résumé tailoring as a signal . For PM job searches, prioritize warm referrals, a brief direct note to the hiring manager referencing something their team shipped, and clickable proof of work such as a portfolio, project, or product teardown . Apply on the day a role opens: Greenhouse co-founder Jon Stross says recruiters often review candidates in application order and stop once they have enough good ones .
- For a bootstrapped startup with a few enterprise customers, one commenter proposed using existing accounts as a low-cost growth channel: ask each buyer for one peer introduction and test expansion into another team or department, adding revenue without hiring . Another commenter advised building around the use case customers already pay for before hiring specialists .
- For a product with high token costs, a reply suggested usage-based pricing that passes those costs to customers rather than absorbing them, as a way to ease burn pressure; this was a proposal, not a reported result .
- A commenter recommended setting an overall direction, focusing on the primary issue each week, using data to guide decisions and pivots, and moving at a controlled brisk pace rather than maximizing speed .
- Against AI-native competitors, emphasize user outcomes and proven product performance rather than AI branding alone: the post describes rivals attracting attention with flashier demos, simpler UX, and lower prices despite perceived gaps in product depth, while a participant recommends focusing on what the product solves rather than how it works. Another participant says buyers may accept a perceived 50% cost reduction and commit long term even when demo performance may not reflect operational reality, making evidence of scalability and real-world results important.
- Tailor differentiation to the buyer: security and governance may resonate with larger, risk-averse organizations, but be a harder sell to SMBs and startups. In regulated markets, an HCM participant cites a reported AI-discrimination case and ruling holding both vendor and software users liable as reasons AI risk can affect adoption; this is a commenter-reported example, not independently verified here.
- Set capacity and communicate cut lines clearly and often, framing omitted work as deliberate prioritization; keep side quests temporary or put them on systems that require no ongoing PM maintenance.
- Prioritize against the product-area KPI and customer needs, using analytics, competitive analysis, and customer conversations to identify what matters most. Before attending a meeting, check whether you are needed to decide, provide input, or own the work; protect time for product strategy and what must happen over the next 6–18 months rather than routine workstream coordination.
- Visibility may carry substantial weight in some organizations, so learn what leadership values and communicate progress without treating attendance at every meeting as the goal. One reply also flags revenue proximity: avoid breaking commitments to sales during a high-stakes enterprise deal.
- a16z announced Cosign, a professional-reputation directory for the startup community, to make it easier to assess people and companies for hiring, investing, and career decisions. Its premise is that existing networks often flatten connections into a simple yes/no and lose context about how people actually know or have worked with one another.
- Cosign’s profiles organize endorsements into “who shaped your career,” “would work with,” and “person to watch,” while supporting private and public signals. It also lets people express specific interest—such as meeting, hiring, or funding—so matches can happen when both sides are interested.
- The feed is focused on questions and announcements, with announcements attached to profiles to make endorsements durable rather than ephemeral. The team deliberately chose a positive-only product positioning: accurate praise and celebration are recorded, while critique is not preserved in the same way.
- To address the cold-start problem, the team said AI enables profiles to be generated from publicly available information and described covering professional transitions to build the directory; the launch was also framed as an invitation for users to edit profiles, submit updates, and co-sign people.
An r/ProductMgmt poster says their organization has outgrown its current idea-management setup and asks what software other teams use, whether it holds up over time, and what is working for them.
A free GitHub library offers 56 technical resources for PMs across APIs, software architecture, SQL/data, product metrics, observability, security, and CI/CD/releases. It is designed to help PMs understand software without learning to code, ask Engineering/Data/Security better questions, interpret technical evidence, and evaluate decision trade-offs. Library