# Smaller Pods, Better User Telemetry, and the PM Taste Layer *By PM Daily Digest • July 10, 2026* Meta’s shift toward smaller pods and a broader “product staff” role stood out this cycle, alongside YC’s dot-plot framework for seeing real user behavior. The brief also covers a concrete B2B retention playbook, an AI design workflow for PMs, and practical career signals for the AI era. ## Big Ideas - **At Meta/Instagram, the product team is getting smaller and more generalist.** Adam Mosseri said the old ~13-person specialized team is shifting to pods of **4-6 generalist engineers plus one "product staff"** role that can cover parts of PM, design, data, and research work, with senior specialists pulled in only when needed. The smaller 6-7 person core is intended to reduce coordination overhead and design-by-committee. [^1] - **As building gets easier, PM leverage moves up the stack.** Mosseri's framing was that *taste*, judgment, strategy, and curation matter more in an AI-heavy environment. He also argued that strong product leaders are often curators of people, ideas, and strategy—and that team chemistry matters because trust and rapport determine how well leaders work through problems. [^1] > "No, I think taste matters a ton. In a world where it’s easier to build things, it’s more important to make sure that your time is spent figuring out what you should be building in the first place." [^1] ## Tactical Playbook 1. **Use dot plots to see behavior that DAU charts hide.** YC described a simple setup: put **users on rows** and **days on columns**, then add a dot whenever a user completes a value-creating event. Choose a real value event—not something generic like opening the app—and mark onboarding day with a distinct symbol. Then layer in feature or state markers and sort by attributes like device, geography, or onboarding date. Pair the plot with cohort retention curves; for early products, it can even be the primary dashboard before you have hundreds of users. [^2] **Why it matters:** dot plots surface patterns that aggregates miss, like weekday vs. weekend usage, first-use drop-off, or feature behaviors that correlate with stickiness. In one YC B2B example, it would have exposed a churned **$80k account** where only **3 of 10 seats** activated and nobody used the product more than two days per week. [^2] 2. **For AI design work, front-load context and review.** Aakash Gupta's Codex workflow is: keep a project folder with the right amount of context; start with **plan mode**; give the model screenshots instead of long written descriptions when possible; ask for several divergent designs; and default to **HTML** unless someone specifically needs a Figma file. Then steer the build mid-task and spend time on the final iteration pass, which the guide says is where quality separates from slop. [^3][^4][^3][^4] ## Case Studies & Lessons - **B2B SaaS retention: deliver value outside the product first.** One AdTech PM traced low trial activation to dashboard cognitive load and found that only **27% of new users returned on day two**. The team then identified users who had not logged back in within seven days, pulled Amazon campaign data through existing APIs, used Gemini 3.1 Flash-Lite to flag anomalies like spend with zero orders, and emailed personalized insights plus a Calendly link for a Customer Success audit. Results: **+22% cohort reactivation** and **18%** of targeted users booked optimization sessions. [^5] - **Instagram Reels: momentum is not the same as foundation.** Mosseri said the first version of Reels was built on top of Stories in 2019 because Stories had momentum, but it proved to be the wrong surface: story read-through was low, many Reels were never seen, and Instagram ended up out of position as TikTok surged in 2020. [^1] ## Career Corner - **Hiring signals moving up:** Mosseri said his baseline remains **grit, quick learning, and self-awareness**, with **curiosity and willingness to try things** rising in importance. He also said there may be fewer roles centered on managing very large organizations as teams get smaller. [^1] - **If you're switching into PM, translate domain work into product outcomes.** One game producer reframed experience around live-ops ownership, incident management across **60+ developers**, feature-level KPIs, funnel fixes that improved first-session conversion and DAU, and prioritization tools like Kano, personas, and product/live-ops roadmaps. [^6] - **If AI is fragmenting your team's working style, standardize lightly.** One PM dealing with very different AI usage patterns set up a weekly tools sync, a shared prompt library, and lightweight review checklists to reduce chaos from mismatched workflows and low-quality AI output. [^7][^8][^7] ## Tools & Resources - Worth bookmarking for AI-enabled PM work: Aakash Gupta's [The PM's Guide to AI Design that isn't Slop](https://www.news.aakashg.com/p/pm-guide-ai-design), the [taste skill](https://github.com/Leonxlnx/taste-skill), and the related setup of PostHog/Linear connectors, Figma/Slack plugins, and ChatGPT Atlas for sites without APIs. [^3][^4] --- ### Sources [^1]: [Adam Mosseri: Building Instagram for an AI world](https://www.youtube.com/watch?v=yQ_EWmtfWvQ) [^2]: [Dot Plots: How to Actually See What Your Users Are Doing](https://www.youtube.com/watch?v=e5-6rEwzxLs) [^3]: [The PM's Guide to AI Design that isn't Slop](https://www.news.aakashg.com/p/pm-guide-ai-design) [^4]: [substack](https://substack.com/@aakashgupta/note/c-291543168) [^5]: [r/prodmgmt post by u/Striking-Water878](https://www.reddit.com/r/prodmgmt/comments/1usc8ve/) [^6]: [r/ProductManagement post by u/poundofcake](https://www.reddit.com/r/ProductManagement/comments/1urn5i8/) [^7]: [r/ProductManagement comment by u/Existing-Fact5797](https://www.reddit.com/r/ProductManagement/comments/1usc7ey/comment/own142u/) [^8]: [r/ProductManagement comment by u/rechcher](https://www.reddit.com/r/ProductManagement/comments/1usc7ey/comment/owmuxoh/)