# AI Operating Models, Workflow Moats, and the Hybrid PM Market *By PM Daily Digest • June 25, 2026* New PM signals point to a common pattern: AI adoption is high, but operating models, workflow design, and team skills are lagging. This brief covers fresh survey data, a concrete Company OS pattern, Typeform's AI strategy, and what hybrid PM hiring now looks like. ## Big Ideas - **AI adoption is widespread; operating model change is not.** In Melissa Perri's survey of 309 product leaders, 87.7% reported AI coding assistance and 85.4% reported AI use for research, writing, or analysis, yet only 36% said AI is strengthening the product operating model [^1]. Impact is strongest in engineering (50%) and design (45%), and much lower in strategy, research, and collaboration [^1]. Mature operating models are 1.7x more likely to benefit, and teams under 50 report 48% strengthening versus 20% in orgs with 500+ people [^1]. > "Delivery of good decisions became the new bottleneck." [^1] **Why it matters:** delivery is accelerating faster than decision-making. **Apply it:** audit how decisions move, translate AI strategy into operating rules PMs can actually use, and measure cycle time, decision quality, and customer insight velocity rather than adoption alone [^1]. - **A practical response is a "Company OS," not more standalone tools.** Laurel's pattern has three layers: map each function's work first (ontology), encode company-specific workflows in markdown "skill files," then deliver the right skill inside daily Slack workflows [^2]. Laurel also uses a dedicated AI Ops role, companywide hackathons, and workflow-level culture cues to spread adoption beyond engineering [^2]. **Why it matters:** this turns AI from individual prompting into shared operating infrastructure. **Apply it:** first define which work should be automated away versus get more human time, then make the best known workflow the default for everyone [^2]. ## Tactical Playbook 1. **Separate problem from approach before technical debate starts.** Use explicit framing: the business requirement is the outcome; the current solution idea is provisional [^3]. **Why it matters:** it prevents architecture debates from replacing alignment on the actual problem [^3]. **Try this sequence:** - State the user or business outcome - Mark the proposed solution as a hypothesis - Ask for alignment on whether the outcome is worth solving - Only then translate into functional and technical requirements [^3] 2. **Keep the PRD short, but keep the "why."** Several PMs described a one-page PRD or epic covering the what, why, and business case, with build requirements living in Jira [^4][^5]. Another reminder from the same thread: the PRD remains the source of truth for why the feature exists and preserves context for future teams [^6]. **Apply it:** start with the epic, load notes and emails into an LLM to fill a markdown PRD template, then review and commit it to the repo before delivery work starts [^7]. ## Case Studies & Lessons - **Typeform is running both defensive and offensive AI strategy.** Defensively, it embedded conversational AI into core forms using best practices derived from millions of data points [^8]. Offensively, it is expanding from forms into full workflows like lead enrichment, nurturing, and AI-moderated research [^8]. Its new Research Flow compresses 50 customer interviews from weeks or months into hours [^8]. **Why it matters:** this is a concrete example of AI moving a product from a single interaction to an end-to-end workflow. **Apply it:** prioritize AI bets by combining usage analysis, willingness-to-pay, and feature overlap across use cases before scaling the platform [^8]. - **Typeform's moat thesis is shifting too.** The company chose a model-agnostic architecture, added AI observability after early model switches proved costly to evaluate, and argues that broader workflow coverage, integrations, and enterprise security now create a stronger moat than depth in a single use case [^8]. It cites presence in 95% of the Fortune 500 as part of that defensibility argument [^8]. **Takeaway:** in AI products, the more durable question may be "what workflow do we own end-to-end?" rather than "what feature do we do best?" ## Career Corner - **The market is rewarding hybrid PMs - but not shallow ones.** One speaker describes the "impact-led product generalist" as someone deep in select areas who uses AI to fill gaps for faster impact, not a coordinator moving messages between functions [^9]. Market signals point the same way: 73% of senior PMs surveyed expect more hybrid or generalized PM roles [^9]. **Apply it:** first learn what good looks like without AI, then use AI as a co-pilot; watch for the failure modes of overstretching and overstepping other disciplines [^9]. - **A hiring signal to prepare for now:** AI-native PM ability can be assessed on a four-level ladder from chat usage to workflow automation, app building, and shipping shared apps to customers [^2]. At Laurel, candidates are asked to screen-share so interviewers can see whether they have repeatable workflows or just open chat tabs [^2]. Pair that with "tail skills" AI still struggles to replace: domain-specific judgment and relational intelligence [^10]. ## Tools & Resources - **Watch the shift from terminal agents to Slack agents.** Sachin Rekhi frames AI UX as moving from web chatbots (2022) to terminal agents (2025) to Slack-based agents (2026), with each wave reducing friction and widening the audience [^11]. If terminal setup friction is limiting adoption on your team, he recommends evaluating **Claude Code / Claude Cowork / Claude Tag** alongside **Codex / Codex CLI / Codex Workspace Agents** [^12]. For a concrete operating pattern, see [How to Build a Company OS in Claude Code with Jiaona Zhang, CPO at Laurel](https://www.news.aakashg.com/p/company-os-jz) [^2]. --- ### Sources [^1]: [Episode 271: The Gap Between AI Adoption and AI Strategy](https://www.youtube.com/watch?v=anp_R_a6jwc) [^2]: [How to Build a Company OS in Claude Code with Jiaona Zhang, CPO at Laurel](https://www.news.aakashg.com/p/company-os-jz) [^3]: [r/ProductManagement post by u/PerMyLastEmaiI](https://www.reddit.com/r/ProductManagement/comments/1uf1jtk/) [^4]: [r/ProductManagement comment by u/NullAnony](https://www.reddit.com/r/ProductManagement/comments/1uez3ll/comment/otnsvan/) [^5]: [r/ProductManagement comment by u/squealingcircus55](https://www.reddit.com/r/ProductManagement/comments/1uez3ll/comment/oto540z/) [^6]: [r/ProductManagement comment by u/W2ttsy](https://www.reddit.com/r/ProductManagement/comments/1uez3ll/comment/oto0tn0/) [^7]: [r/ProductManagement comment by u/Rolandersec](https://www.reddit.com/r/ProductManagement/comments/1uez3ll/comment/otny2zs/) [^8]: [Typeform CEO on Why Going Broad Now Beats Going Deep as an AI Moat | Jay Choi | E301](https://www.youtube.com/watch?v=RSsF9pWpSRA) [^9]: [The Evolution of the PM Archetypes in the Age of AI | ProductTank London](https://www.youtube.com/watch?v=XrSu_7FjFbo) [^10]: [Don't Be Mean With AI](https://productify.substack.com/p/dont-be-mean-with-ai) [^11]: [𝕏 post by @sachinrekhi](https://x.com/sachinrekhi/status/2069796083644191198) [^12]: [𝕏 post by @sachinrekhi](https://x.com/sachinrekhi/status/2069935188872962536)