# Continuous Discovery, Cursor-Layer AI, and Open Source PM Lessons *By PM Daily Digest • May 21, 2026* This brief covers the latest thinking on continuous discovery, cursor-layer AI design, team structure realities, enterprise AI trust patterns, and open source product management. It also highlights practical resources for PM knowledge management and AI feature prioritization. ## Big Ideas ### Continuous discovery is a structure and a cadence Teresa Torres frames discovery as three linked moves: define the **outcome**, uncover **opportunities** (customer needs, pain points, desires), then test **solutions** against those opportunities [^1]. The method can vary, but the rhythm should not: teams should talk to customers every week, synthesize continuously, and keep roadmaps as living documents instead of rebuilding them in separate planning phases [^1]. > "You synthesize as you go." [^1] Why it matters: Julia Austin argues AI can speed prototyping, but it cannot replace ethnographic research or direct contact with real users and buyers; skipping that foundation often means building fast without understanding adoption problems [^1]. How to apply: make one customer touchpoint per week a team habit, update your opportunity map after each session, and treat roadmap items as current/next opportunities rather than fixed quarterly promises. ### The next AI interface may sit beside the cursor, not inside a chatbox Aakash Gupta argues many AI features still force Stage 1 behavior: users open a separate window, restate context, then return to work [^2]. Cursor-layer products such as Clicky and Magic Pointer remove that round-trip by letting AI see the screen and answer in place [^3]. Why it matters: teams may think they shipped embedded AI when users are still doing manual context handoffs. How to apply: audit current AI features for context re-establishment. If the user still has to explain what is on screen, fix that friction before adding another sidebar or chat feature [^2]. ### Team definitions fail when they ignore how work really happens Product, design, technology, and actual collaboration patterns all create different maps of the same organization, and those maps rarely align cleanly [^4]. Product can redraw boxes cheaply, while engineering absorbs headcount, on-call, and reliability consequences; design often sees the seams without having the structural power to resolve them [^4]. How to apply: map teams honestly on a few spectracustomer proximity, technology ownership, work intake, performance criteria, and real mandatebefore redesigning the org [^4]. ## Tactical Playbook ### A practical checklist for getting enterprise AI through review One repeatable playbook for enterprise AI approval is: lead with isolated VPC-first architecture, frame AI as deterministic background workflows instead of open chatboxes, add human approval pause-states for high-risk actions, and keep prompts/rules in version control for audits [^5]. Julie Zhuo adds the product-side complement: observability, audit trails, structured data, and clear trust signals are what turn AI from a demo into a tool [^6]. How to apply: bring those controls into the first Legal, Compliance, or buyer reviewbefore debating model choice. ### For AI-scale VoC, combine tagging with targeted outcome slices At roughly **50k AI agent conversations per month**, one PM team found 1% random sampling useful for "vibe" but not for statistical decisions, while generic LLM topic tagging still failed to explain why specific customers did not convert [^7]. Their practical workaround: keep LLM tagging, but review targeted slices like pricing, rage clicks, or handoff and tie those slices to outcomes [^8]. How to apply: define 3-5 slices tied to a business outcome before transcript review; start there instead of browsing random conversations. ## Case Studies & Lessons ### Open source PM trades control for a bigger market Dan Cerulli's Kubernetes-era lesson is that open-source PMs do not fully own the roadmap, and success often requires letting competitors participate [^9]. Google concluded it could not define a standard alone, but could as part of a consortium; monetization then came through proprietary tools, managed services, or support layered on top of open source [^9]. Cerulli's advice when open sourcing internally: be explicit about business value and bring other companies in early for legitimacy and safer adoption [^9]. He also notes the model adds drama and loss of control, but created more value than solo efforts for early Kubernetes participants [^9]. Lesson: if ecosystem adoption matters, optimize for shared legitimacy before perfect ownership. ## Career Corner ### The AI-native PM pitch is resonating After speaking to more than **800 PMs** at PM3 Summit, Sachin Rekhi said the strongest reaction came from the upside of becoming an AI-native PM: more time on solving customer problems and less time on coordination overhead [^10]. He believes this could be a "golden era of product management" [^10]. How to apply: start by identifying the coordination-heavy parts of your week and judge AI tools by whether they give that time back to product craft. ## Tools & Resources - **PM Brain OS**: a local markdown + `CLAUDE.md` system that loads relevant context before tasks, updates the right files afterward, surfaces contradictions, and runs a weekly maintenance sweep [^11]. Its key design choice is provenance tagging: decisions outrank research, which outranks verbal claims [^11]. In the walkthrough, it immediately exposed a strategy gap: **38 of 47** shipped Jira tickets focused on enterprise permissions/admin tooling while only **4** touched the activation funnel [^11]. MIT-licensed and installable with one shell command [^11]. - **Cursor-layer toolkit**: Gupta's package includes a design spec, three prototypes to test this week, and a 30-minute audit that scores AI roadmap items; in his worked example, the top priority was a one-sprint fix rather than a multi-quarter rewrite [^2][^3]. --- ### Sources [^1]: [Episode 269: Continuous Discovery Habits That Actually Work](https://www.youtube.com/watch?v=0ueggyZ1u6Y) [^2]: [substack](https://substack.com/@aakashgupta/note/c-262578805) [^3]: [Is the Chatbox the Wrong Interface for AI? Google and Farza think so.](https://www.news.aakashg.com/p/cursor-layer-toolkit) [^4]: [TBM 423: Why Defining Teams Is So Hard](https://cutlefish.substack.com/p/tbm-423-why-defining-teams-is-so) [^5]: [r/ProductManagement post by u/MrBemz](https://www.reddit.com/r/ProductManagement/comments/1tiz6so/) [^6]: [𝕏 post by @joulee](https://x.com/joulee/status/2057184115372466581) [^7]: [r/prodmgmt post by u/Overall_Challenge_66](https://www.reddit.com/r/prodmgmt/comments/1tispah/) [^8]: [r/prodmgmt comment by u/AssignmentDull5197](https://www.reddit.com/r/prodmgmt/comments/1tispah/comment/omwn8rp/) [^9]: [How PMs can win with open source - Dan Ciruli \(Product Leader, Nutanix\)](https://www.youtube.com/watch?v=WTJyUTUTwgk) [^10]: [𝕏 post by @sachinrekhi](https://x.com/sachinrekhi/status/2057081263450734676) [^11]: [PM Brain OS: The Second Brain for Product Managers, Made of Markdown](https://www.productcompass.pm/p/pm-brain-os)