--- title: "When Product Managers Become the Scrum Secretary: How to Reclaim Product Discovery From Engineering Rituals" description: "For CPOs and CTOs: when junior PMs become Scrum secretaries, discovery stops and growth slows. How to reset roles and tie delivery to business outcomes." image: https://www.drcpo.com/hubfs/blog-scrum-secretary.jpg --- [Skip to content](https://www.drcpo.com/blog/when-product-managers-become-the-scrum-secretary-how-to-reclaim-product-discovery-from-engineering-rituals#main-content) [![DrCPO LOGO Small Color](https://www.drcpo.com/hs-fs/hubfs/DrCPO%20LOGO%20Small%20Color.png?width=797&height=262&name=DrCPO%20LOGO%20Small%20Color.png)Homepage](https://www.drcpo.com/) - [The Problem](https://www.drcpo.com/the-problem) - [Services](https://www.drcpo.com/services) - [Why DrCPO](https://www.drcpo.com/why-drcpo) - [Education](https://www.drcpo.com/education) - [Insights](https://www.drcpo.com/blog) [Contact](https://www.drcpo.com/contact) - [The Problem](https://www.drcpo.com/the-problem) - [Services](https://www.drcpo.com/services) - [Why DrCPO](https://www.drcpo.com/why-drcpo) - [Education](https://www.drcpo.com/education) - [Insights](https://www.drcpo.com/blog) [Contact](https://www.drcpo.com/contact) ![A product manager at a sprint board while a notebook labelled "Customer interviews" sits untouched](https://www.drcpo.com/hs-fs/hubfs/blog-scrum-secretary.jpg?width=1536&height=1024&name=blog-scrum-secretary.jpg) CPO/Head of Product (Audience) CTO/VP Eng (Audience) Academic/DBA/PhD (Audience) # When Product Managers Become the Scrum Secretary: How to Reclaim Product Discovery From Engineering Rituals ![Ken Pulverman](https://www.drcpo.com/hs-fs/hubfs/ken-pulverman-avatar.jpg?width=48&height=48&name=ken-pulverman-avatar.jpg) Ken Pulverman January 13, 2026 **If your PMs spend most of their week in Scrum ceremonies and backlog grooming, your company is likely optimizing *engineering throughput* while under-investing in *market discovery* and *outcome ownership*.** Agile methods emerged from software engineering needs, but the **Product Owner** role is explicitly accountable for maximizing product value, not serving as an administrative buffer. ([Beck et al., 2001](https://agilemanifesto.org/principles.html); [Schwaber & Sutherland, 2020](https://scrumguides.org/scrum-guide.html)). **What to do:** 1. Reset decision rights and role boundaries (PM vs PO vs EM). 2. Install a continuous discovery cadence alongside delivery. Make product accountable to outcomes (not output). ([Cagan, 2017](https://www.wiley.com/en-us/INSPIRED%3A%2BHow%2Bto%2BCreate%2BTech%2BProducts%2BCustomers%2BLove%2C%2B2nd%2BEdition-p-9781119387503); Torres, 2021; Perri, 2018). **Call to action:** - **Want the full playbook + a completed vendor-ready RFI + a blank RFI template?** Get it on Substack (paid) or request it in a working session. **What this looks like in the business (symptoms)** You’ll typically see 5–8 of these at once: - PM calendars are dominated by ceremonies, refinement, and ticket management - “Discovery” means reading customer notes, not running structured learning loops - Engineers complain requirements are unclear, so PMs over-specify solutions - Product strategy decks exist, but roadmaps behave like feature backlogs - Teams ship, but revenue, retention, or activation don’t move (or don’t get measured) These patterns are often a role-clarity failure and a coordination failure, not an effort problem—classic conditions for **role ambiguity** and **role conflict**, which are strongly associated with worse performance and stress outcomes in organizations. ([Rizzo et al., 1970](https://doi.org/10.2307/2391486); [Tubre & Collins, 2000](https://doi.org/10.1177/014920630002600104)). **How it impacts revenue and competitiveness** When PMs become “ceremony glue,” companies usually pay four compounding costs: 1. **Slower learning** → you test fewer product bets per quarter ([Torres, 2021](https://books.google.com/books/about/Continuous_Discovery_Habits.html?id=HsJzzgEACAAJ)). 2. **Worse problem selection** → you ship polished solutions to low-value problems ([Perri, 2018](https://www.google.com/books/edition/Escaping_the_Build_Trap/c_-JDwAAQBAJ?hl=en)). 3. **Increased rework** → teams build the wrong thing faster ([Ries, 2011](https://www.penguinrandomhouse.com/books/306999/the-lean-startup-by-eric-ries/); [Patton, 2014](https://books.google.com/books/about/User_Story_Mapping.html?id=y5f1zgEACAAJ)). 4. **Weak accountability** → product becomes a “support function,” not a growth engine. **Why it happens (root causes)** This failure mode usually shows up when: - PM is defined as “whatever the team needs” (role scope expands infinitely) Discovery is treated as a phase, not an operating system (Torres, 2021; [Cagan, 2017](https://www.wiley.com/en-us/INSPIRED%3A%2BHow%2Bto%2BCreate%2BTech%2BProducts%2BCustomers%2BLove%2C%2B2nd%2BEdition-p-9781119387503)). - The org rewards harmony over productive tension between product and engineering ([Ancona & Caldwell, 1992](https://eric.ed.gov/?id=EJ457246)). - Incentives measure “shipping” more than customer + business outcomes ([Perri, 2018](https://www.google.com/books/edition/Escaping_the_Build_Trap/c_-JDwAAQBAJ?hl=en)). **What you have to do (public, practical steps)** **Step 1 — Re-define roles in one page (and enforce it)** Create a one-page “role contract”: - **PM (or Product Manager):** owns *problem selection*, *outcome definition*, *discovery learning loop*, and *product narrative* - **PO (if you use it):** owns *backlog integrity* and *acceptance criteria*, but not strategy - **EM:** owns delivery execution, technical tradeoffs, and team health - **Trio:** PM + Design + Tech jointly run discovery ([Torres, 2021](https://books.google.com/books/about/Continuous_Discovery_Habits.html?id=HsJzzgEACAAJ); [Gothelf & Seiden, 2016](https://www.amazon.com/Lean-UX-Designing-Great-Products/dp/1491953608)). Also align to Scrum’s explicit expectation that product leadership maximizes value. ([Schwaber & Sutherland, 2020](https://scrumguides.org/scrum-guide.html)). **Step 2 — Install continuous discovery without slowing delivery** Use a **dual-track** pattern: discovery and delivery run in parallel, with discovery feeding validated backlog. ([Cagan, 2012](https://www.svpg.com/dual-track-agile); [Patton, 2014](https://books.google.com/books/about/User_Story_Mapping.html?id=y5f1zgEACAAJ)). Minimum viable cadence: - Weekly customer touchpoints - A visible assumption map - Two small tests per week (prototype, concierge, fake door, pricing test) - A “decision log” that links each delivery item to a validated insight ([Torres, 2021](https://books.google.com/books/about/Continuous_Discovery_Habits.html?id=HsJzzgEACAAJ)). **Step 3 — Replace output metrics with outcome metrics** For each product slice, define: - Customer outcome metric (activation, retention, time-to-value) - Business metric (ARR expansion, conversion, churn reduction) - Guardrails (latency, CSAT, support load) This is how you stop becoming a feature factory. ([Perri, 2018](https://www.amazon.com/Escaping-Build-Trap-Effective-Management/dp/149197379X); [Cagan, 2017](https://www.wiley.com/en-us/INSPIRED%3A%2BHow%2Bto%2BCreate%2BTech%2BProducts%2BCustomers%2BLove%2C%2B2nd%2BEdition-p-9781119387503)). **Our approach (what DrCPO does)** This aligns to your doc’s intent: anchor PM in **modern product discovery** and **accountability**. **Phase 1 (2 weeks): Diagnose & reset** - Shadow ceremonies, map time allocation, identify “ritual gravity wells” - Produce a one-page role contract + decision-rights map - Create an outcome-based roadmap skeleton **Phase 2 (30 days): Install the operating system** - Stand up discovery cadence and a product-trio rhythm - Implement decision logs and lightweight experiment templates - Train PMs on interview hygiene + assumption testing **Phase 3 (60–90 days): Make it stick** - Align leadership incentives to outcome metrics - Upgrade intake, prioritization, and roadmap governance - Coach PMs into confident tension with engineering (healthy conflict, not chaos) **CTA (on-site):** - Link to Substack (paid toolkit) - Link to contact form for a working session + slide deck **FAQ**  **Isn’t this just “Scrum done wrong”?** Sometimes. But the durable fix is clarifying roles and restoring discovery, not relabeling ceremonies. ([Schwaber & Sutherland, 2020](https://scrumguides.org/scrum-guide.html); [Torres, 2021](https://books.google.com/books/about/Continuous_Discovery_Habits.html?id=HsJzzgEACAAJ)). **Will continuous discovery slow delivery?** Not if you reduce rework by validating assumptions early. ([Ries, 2011](https://www.penguinrandomhouse.com/books/306999/the-lean-startup-by-eric-ries/); [Patton, 2014](https://books.google.com/books/about/User_Story_Mapping.html?id=y5f1zgEACAAJ)). **What if we don’t have designers?** You can still run discovery with lightweight prototypes and structured customer learning; design is a capability, not a job title. ([Gothelf & Seiden, 2016](https://www.amazon.com/Lean-UX-Designing-Great-Products/dp/1491953608)).   **References** Ancona, D. G., & Caldwell, D. F. (1992). Bridging the boundary: External activity and performance in organizational teams. Administrative Science Quarterly, 37(4), 634–665. [https://doi.org/10.2307/2393475](https://doi.org/10.2307/2393475) Beck, K., Beedle, M., van Bennekum, A., Cockburn, A., Cunningham, W., Fowler, M., Grenning, J., Highsmith, J., Hunt, A., Jeffries, R., Kern, J., Marick, B., Martin, R. C., Mellor, S., Schwaber, K., Sutherland, J., & Thomas, D. (2001). Manifesto for Agile Software Development. [https://agilemanifesto.org/](https://agilemanifesto.org/) Cagan, M. (2012, September 17). Dual-track agile. Silicon Valley Product Group. [https://www.svpg.com/dual-track-agile/](https://www.svpg.com/dual-track-agile/) Cagan, M. (2017). INSPIRED: How to create tech products customers love (2nd ed.). Wiley. [https://www.wiley.com/en-us/INSPIRED%3A%2BHow%2Bto%2BCreate%2BTech%2BProducts%2BCustomers%2BLove%2C%2B2nd%2BEdition-p-9781119387503](https://www.wiley.com/en-us/INSPIRED%3A%2BHow%2Bto%2BCreate%2BTech%2BProducts%2BCustomers%2BLove%2C%2B2nd%2BEdition-p-9781119387503) Gothelf, J., & Seiden, J. (2016). Lean UX: Designing great products with agile teams (2nd ed.). O’Reilly Media. [https://www.amazon.com/Lean-UX-Designing-Great-Products/dp/1491953608](https://www.amazon.com/Lean-UX-Designing-Great-Products/dp/1491953608) Patton, J. (2014). User story mapping: Discover the whole story, build the right product. O’Reilly Media. [https://books.google.com/books/about/User\_Story\_Mapping.html?id=y5f1zgEACAAJ](https://books.google.com/books/about/User_Story_Mapping.html?id=y5f1zgEACAAJ) Perri, M. (2018). Escaping the build trap: How effective product management creates real value. O’Reilly Media. [https://www.amazon.com/Escaping-Build-Trap-Effective-Management/dp/149197379X](https://www.amazon.com/Escaping-Build-Trap-Effective-Management/dp/149197379X) Ries, E. (2011). The lean startup. Crown Business. [https://www.penguinrandomhouse.com/books/306999/the-lean-startup-by-eric-ries/](https://www.penguinrandomhouse.com/books/306999/the-lean-startup-by-eric-ries/) Rizzo, J. R., House, R. J., & Lirtzman, S. I. (1970). Role conflict and ambiguity in complex organizations. Administrative Science Quarterly, 15(2), 150–163. [https://doi.org/10.2307/2391486](https://doi.org/10.2307/2391486) Schwaber, K., & Sutherland, J. (2020). The Scrum Guide: The definitive guide to Scrum. Scrum Guides. [https://scrumguides.org/scrum-guide.html](https://scrumguides.org/scrum-guide.html) ## Share this post [mailto:https%3A%2F%2Fwww.drcpo.com%2Fblog%2Fwhen-product-managers-become-the-scrum-secretary-how-to-reclaim-product-discovery-from-engineering-rituals](mailto:https%3A%2F%2Fwww.drcpo.com%2Fblog%2Fwhen-product-managers-become-the-scrum-secretary-how-to-reclaim-product-discovery-from-engineering-rituals) ## Keep reading ### [![Run: the eight-step AI-powered product management system](https://www.drcpo.com/hs-fs/hubfs/pm-model-run.png?width=1600&height=900&name=pm-model-run.png) CPO/Head of Product (Audience) AI in Product Management (Pillar) CEO/GM (Audience) The Run Version of the New Product Management Model: The Full AI-Powered System](https://www.drcpo.com/blog/run-product-management-model) ### [![Walk: the five-step structured product learning loop](https://www.drcpo.com/hs-fs/hubfs/pm-model-walk.png?width=1600&height=900&name=pm-model-walk.png) CPO/Head of Product (Audience) AI in Product Management (Pillar) CEO/GM (Audience) The Walk Version of the New Product Management Model: A More Structured Product Learning Loop](https://www.drcpo.com/blog/walk-product-management-model) [![](https://www.drcpo.com/hs-fs/hubfs/DrCPO%20LOGO%20Small%20Color-1.png?width=797&height=262&name=DrCPO%20LOGO%20Small%20Color-1.png)](https://www.drcpo.com) - [The Problem](https://www.drcpo.com/the-problem) - [Services](https://www.drcpo.com/services) - [Why DrCPO](https://www.drcpo.com/why-drcpo) - [Education](https://www.drcpo.com/education) - [Insights](https://www.drcpo.com/blog) ##### Some of the Product Management thought Leaders we are following: [🌐 of PM](https://www.drcpo.com/pm-thoughtleaders) --- Privacy Policy · Legal · © 2026 DrCPO. All rights reserved. ```json { "@context" : "https://schema.org", "@type" : "BlogPosting", "author" : { "@type" : "Person", "name" : "Ken Pulverman", "url" : "https://www.drcpo.com/blog/author/ken-pulverman" }, "dateModified" : "2026-01-20T07:05:35.592Z", "datePublished" : "2026-01-13T01:24:05.000Z", "headline" : "When Product Managers Become the Scrum Secretary: How to Reclaim Product Discovery From Engineering Rituals", "image" : [ "https://www.drcpo.com/hubfs/blog-scrum-secretary.jpg" ], "mainEntityOfPage" : { "@id" : "https://www.drcpo.com/blog/when-product-managers-become-the-scrum-secretary-how-to-reclaim-product-discovery-from-engineering-rituals", "@type" : "WebPage" }, "publisher" : { "@type" : "Organization", "logo" : { "@type" : "ImageObject", "url" : "https://www.drcpo.com/hubfs/DrCPO%20LOGO%20Small%20Color-1.png" }, "name" : "DrCPO" } } ``` ```json { "@context" : "https://schema.org", "@id" : "https://www.drcpo.com/#org", "@type" : "Organization", "description" : "Fractional CPO consulting and product management education for B2B software companies and business schools.", "founder" : { "@id" : "https://www.drcpo.com/#ken" }, "logo" : "https://www.drcpo.com/hubfs/DrCPO%20LOGO%20Small%20Color.png", "name" : "DrCPO", "url" : "https://www.drcpo.com/" } ``` ```json { "@context" : "https://schema.org", "@id" : "https://www.drcpo.com/#ken", "@type" : "Person", "image" : "https://www.drcpo.com/hubfs/ken-pulverman-portrait.jpg", "jobTitle" : "Fractional Chief Product Officer", "knowsAbout" : [ "Product management", "AI in product management", "B2B software product strategy", "Product operating models" ], "name" : "Ken Pulverman", "url" : "https://www.drcpo.com/about", "worksFor" : { "@id" : "https://www.drcpo.com/#org" } } ```