Product Operating Model Series: Sense of Ownership

Issue #219/ Wydanie #219

In today's edition, among other things:

💜 Editor’s Note: The ‘Full-Stack PM’ Trap: Why Wearing All Hats Makes You Worse at Each One
💜 Product Operating Model Series: Sense of Ownership

Join Premium to get access to all content.

It will take you almost an hour to read this issue. Lots of content (or meat)! (For vegans - lots of tofu!).

Grab a notebook 📰 and your favorite beverage 🍵☕.

DeStaRe Foundation

Editor’s Note by Alex 💜

The ‘Full-Stack PM’ Trap: Why Wearing All Hats Makes You Worse at Each One

Here’s the brutal truth your company won’t tell you: Being asked to do more with less isn’t pragmatic leadership—it’s organizational negligence disguised as empowerment.

You’re being told you’re versatile. A “full-stack PM” who can handle UX design in the morning, analyze retention funnels at lunch, write go-to-market strategy in the afternoon, and facilitate stakeholder alignment before dinner. You’re told this makes you valuable—that companies need “T-shaped” professionals who can do it all.

The reality? You’re not becoming a versatile professional. You’re becoming a burned-out generalist producing B-grade work across every dimension while your company congratulates itself on “efficiency.”

The Industry’s Dirty Little Secret: Full-Stack Is Code for Understaffed

Let me decode the euphemisms: When your job description says “full-stack PM,” read it as “we’re too cheap or disorganized to properly staff our product teams.” When you hear “wear multiple hats,” understand it means “we’ll stretch you thin across incompatible roles until something breaks—probably you.”

The product management community has normalized this dysfunction through a brilliant linguistic sleight of hand. We’ve rebranded organizational failure as individual capability. Instead of asking “Why is this person responsible for five distinct professional disciplines?” we celebrate their “versatility.” Instead of questioning why companies can’t build properly specialized teams, we tell PMs they need to “level up” their skillset to include... well, everything.

This isn’t happening because products got more complex. It’s happening because of three converging forces: (1) the 2022-2024 tech layoffs that decimated support functions, (2) the “do more with less” dogma that followed, and (3) a fundamental misunderstanding of how human cognition actually works. The result? Product teams operating at 60% capacity while leadership congratulates itself on lean operations.

What makes this particularly insidious is how it weaponizes the PM’s natural inclination toward ownership. We want to solve problems. We want to fill gaps. So when UX is understaffed, we jump in. When marketing needs help with positioning, we volunteer. When analytics is overwhelmed, we build our own dashboards. Each act feels responsible. Collectively, they’re killing your ability to do actual product management.

The Neuroscience of Why You Can’t Actually Multitask (Even Though You Think You Can)

Here’s where the evidence becomes devastating. University of Washington professor Sophie Leroy spent years studying what happens when people switch between tasks. She discovered a phenomenon called “attention residue”—when you shift from one task to another, part of your cognitive capacity remains stuck on the previous task, impairing your performance on the new one.

In her seminal 2009 research, Leroy found that attention residue doesn’t just happen with major task switches. Even brief interruptions—checking email, answering a Slack message, glancing at a notification—leave cognitive residue that degrades your performance. The effect is cumulative: “If, like most, you rarely go more than 10-15 minutes without a just check, you have effectively put yourself in a persistent state of self-imposed cognitive handicap.”

Now apply this to the “full-stack PM” reality: You’re sketching wireframes for 90 minutes, then jumping into SQL to debug analytics, then pivoting to stakeholder presentations, then reviewing competitive positioning, then back to technical specs. Your brain isn’t smoothly transitioning between these domains—it’s leaving cognitive residue with every switch, systematically degrading your performance across all of them.

But it gets worse. Research on employee interruptions reveals workers are interrupted every six to 12 minutes in the modern workplace. When 40% of workers report being interrupted 10+ times per day, and each interruption creates attention residue, we’re not just context-switching—we’re operating in a permanent state of cognitive fragmentation.

Cal Newport, synthesizing this research, concluded: “The relative cognitive enhancement that would follow by minimizing this effect” is massive. In other words, eliminating constant task-switching doesn’t improve your performance by 10-20%. It transforms it entirely.

The Expertise Paradox: Why Breadth Destroys Depth

The research on skill acquisition makes the full-stack PM model even more absurd. Anders Ericsson spent decades studying expert performance across domains—chess, music, medicine, athletics. His finding? True expertise requires what he called “deliberate practice”—focused, sustained effort on specific skills, with immediate feedback, far beyond your comfort zone.

Ericsson’s research revealed that becoming genuinely skilled at any complex discipline requires thousands of hours of this type of practice. Not just time spent, but deliberate practice with full cognitive engagement. The popularized “10,000-hour rule” (which Ericsson himself hated as an oversimplification) actually understates the requirement for most domains—he estimated elite-level performance often requires 20,000-25,000 hours of deliberate practice.

Now consider what happens when a PM splits time across five disciplines. You’re not building toward expertise in any of them. You’re engaging in what research calls “dabbling”—surface-level exposure that creates the illusion of competence while systematically preventing actual skill development.

Research on specialist versus generalist performance consistently finds that specialists outperform generalists in their domain of expertise. This isn’t controversial. What’s interesting is why: specialists develop what cognitive scientists call “chunking”—the ability to recognize patterns and make high-quality decisions rapidly because they’ve built extensive mental models through deliberate practice.

When you’re a full-stack PM doing a little UX, a little analytics, a little strategy, and a little stakeholder management, you never develop these expert mental models. You remain perpetually at the novice-to-intermediate level across all dimensions—precisely the level where you make the most mistakes, work the slowest, and add the least strategic value.

Warren Bennis, the leadership authority who coined the term “deep generalist,” described professionals who “develop a unique blend of knowledge depth and knowledge breadth.” The key word? Develop. This means building genuine expertise first, then adding complementary knowledge. It doesn’t mean spreading yourself so thin across domains that you develop expertise in none.

The Real Cost: Burnout, Bad Decisions, and Broken Careers

The consequences of the full-stack PM delusion extend far beyond sub-optimal work quality. The human toll is catastrophic.

In 2025, 82% of workers are at risk of burnout—up from 43% just five years ago. Among managers specifically (which includes most product managers), 43% report experiencing burnout, 10% more than executives. The numbers are worse for younger workers: 59% of workers under 35 face work-related stress daily, compared to 50% of those 35 and older.

Research consistently identifies being overworked as the primary cause of stress for 37% of US workers, with one-third citing lack of work-life balance. When product managers are expected to be full-stack—handling design, analytics, strategy, marketing, and stakeholder management—they’re not just overworked. They’re attempting the cognitively impossible while being measured against standards that assume specialized focus.

LaunchNotes research on product manager burnout specifically identified that PMs experience burnout “as a result of their relentless pursuit of perfection, constant multitasking, and the pressure to deliver results within tight deadlines.” The full-stack PM model takes the already-demanding PM role and multiplies these stressors by requiring competence across five distinct professional domains simultaneously.

But the damage extends beyond individual burnout. When PMs operate in constant cognitive overload from task-switching, their decision quality plummets. Research shows that “people experiencing attention residue after switching tasks are likely to demonstrate poor performance on that next task. The thicker the residue, the worse the performance.”

This manifests as:

• Strategic decisions made without deep analysis because you’re too busy with tactical UX work

• Poor prioritization because you lack time for proper customer research

• Technical debt accumulation because you’re splitting attention between stakeholder management and technical specs

• Weak product positioning because you’re doing surface-level competitive analysis between meetings

The compounding effect of mediocre decisions made under cognitive load creates products that systematically underperform—not because the PM lacks talent, but because the operating model guarantees suboptimal outcomes.

Perhaps most insidious: the full-stack PM model destroys career development. When you spend years as a jack-of-all-trades, you never develop the deep expertise that makes you genuinely valuable. You can’t compete with specialized UX designers on design thinking. You can’t match data analysts on analytical depth. You can’t rival experienced strategists on competitive positioning. You end up replaceable precisely because you tried to be everything to everyone.

What Must Change: A Prescription for Sanity

Here’s what needs to happen, and it needs to happen now:

For Companies: Stop Calling Understaffing “Agility”

If your product teams need design work, hire designers. If they need analytics, hire analysts. If they need marketing support, hire PMMs. The ROI calculation is simple: one properly specialized professional produces higher-quality output faster than three generalists splitting attention. Research shows specialists outperform generalists in task-specific performance while generalists experience higher burnout rates. Stop pretending thin staffing is sophisticated org design.

Implement what research calls “cognitive load management”: structure teams so individuals can achieve flow state—sustained, focused work on compatible tasks. This means PMs focus on product strategy, user insight, and roadmap decisions. Not everyone does everything.

Create what Gallup research identifies as essential: supportive leadership that reduces burnout by 70%. This doesn’t mean cheerleading. It means giving people the resources, team structure, and reasonable scope to actually succeed at their jobs.

For PMs: Reclaim Your Role Boundaries

You have permission—no, you have a professional obligation—to say no to responsibilities that pull you away from core PM work. When asked to design mockups, respond: “I can define the requirements and success metrics. We need a designer for the visual solution.” When asked to build analytics dashboards, respond: “I can articulate what we need to measure and why. We need an analyst to implement tracking properly.”

This isn’t shirking responsibility. It’s professional boundaries based on cognitive science. Teresa Torres emphasizes that “product management is no longer a siloed discipline. It’s a team sport.” But team sport doesn’t mean everyone plays every position—it means each position has specialized responsibilities that together create success.

Document your actual work allocation. Track how many hours you spend on core PM activities (strategy, discovery, decision-making) versus auxiliary functions (design, analytics, stakeholder appeasement). If you’re spending more than 30% of your time on non-PM work, you’re not being versatile—you’re being misused.

For the Industry: Demand Better Standards

We need prominent product leaders to stop celebrating the full-stack PM mythos and start calling out the organizational dysfunction it represents. When Brian Chesky talks about taking back product control, we should ask: “Why were PMs given scope so broad they became ineffective?” When companies boast about “lean” product teams, we should ask: “Lean compared to what? Functional?”

Thought leaders like Marty Cagan, Teresa Torres, and Melissa Perri need to explicitly address this: the PM role has a specific scope, and diluting it across five disciplines doesn’t make PMs more valuable—it makes them less effective. The industry needs to standardize around what PM actually means, rather than letting companies use the title as a catch-all for “whoever fills this role does whatever we’re too understaffed to handle properly.”

Stop attending conferences that celebrate “how I balanced 8 different roles” and start demanding sessions on “how we built properly specialized product teams.” Vote with your attention and your career choices for companies that understand cognitive science.

The Revolution Starts With You Saying No

The full-stack PM mythology persists because it’s convenient for companies and flattering to PMs who mistake exhaustion for effectiveness. But the science is clear: humans cannot maintain high-quality output across multiple distinct cognitive domains simultaneously. Every hour you spend context-switching is an hour you’re not developing genuine expertise. Every responsibility you accept outside core PM work is a step away from becoming strategically valuable.

The solution isn’t individual heroics—working harder to somehow transcend human cognitive limits. The solution is structural: companies must staff product teams properly, and PMs must defend role boundaries backed by decades of research on attention, expertise, and burnout.

When your manager next suggests you’re being “empowered” to handle design, analytics, marketing, strategy, and stakeholder management, you now have the research to respond: “I appreciate the confidence, but cognitive science shows this approach guarantees mediocre outcomes across all dimensions. Instead, let’s discuss how to build a properly specialized team where I can focus on the strategic product decisions that actually require PM expertise.”

Will saying this be uncomfortable? Absolutely. Will it risk making you seem “not a team player”? Possibly. But here’s what’s more uncomfortable: burning out while producing substandard work across five disciplines because you accepted an organizationally dysfunctional operating model.

The product management community faces a choice: continue celebrating the full-stack delusion while our best people burn out producing mediocre work, or acknowledge what the research proves—that expertise requires focus, quality requires specialization, and human cognition has limits we ignore at our peril.

Your career, your mental health, and the quality of your products depend on which path you choose. Choose wisely.

---

---

---

---

---

---

---

---

---

Product Operating Model

Sense of Ownership: Quick Reference Guide

Core Definition

What It Is: Product teams take genuine responsibility for their product areas, treating them as if they were their own business, leading to higher quality, innovation, and motivation.

Source: Third principle of the Product Operating Model from Marty Cagan’s “Transformed” (2024)

---

The Fundamentals

What Teams Must Own

• Something Meaningful: Not trivial tasks, but substantial product areas that