Impact-First Product Teams and the Death Spiral Trap

Nia: You know, Miles, I was looking at some notes from a Spotify town hall a few years back, and the co-founder, Daniel Ek, said something that really stopped me in my tracks. He mentioned they had too many people doing "work around the work" instead of actually contributing to opportunities with real impact.

Miles: That is such a sharp reality check. It’s exactly what Matt LeMay tackles in his book, Impact-First Product Teams. He argues that many of us have treated "the business" as someone else’s problem, while we just obsess over roadmaps and "the right way" to do Scrum.

Nia: Right! It’s like we’re so focused on the method that we forget the actual goal. LeMay even calls it a "low-impact death spiral"—where you ship twenty useless features fast, but each one just makes the product more complicated and harder to fix later.

Miles: Exactly, it’s "velocity theatre" at its worst. He wants us to move from being a "feature factory" to actually understanding our company’s existential milestones, like hitting a specific revenue goal just to keep the lights on.

Nia: It’s a total shift in how we think about our daily rituals. So, let’s dive into how we can stop hiding behind processes and start prioritizing actual business results.

Nia: It is so easy to get caught up in the bubble of product management best practices—you know, the ones we see in every blog post and LinkedIn thread. But Miles, one thing LeMay really hammers home is that most of these "gold standards" come from companies like Google or Amazon—places with almost limitless resources and very specific, rare commercial conditions.

Miles: Exactly. He calls it out directly—most of those practices are actually irreproducible for the average team. If you are working at a startup that needs a certain amount of cash in the bank by a specific date just to survive, following a framework designed for a multi-billion dollar behemoth might actually be a form of organizational malpractice.

Nia: That is a heavy word, but it fits. It is like trying to train for a marathon using a plan meant for an Olympic sprinter when you actually have a broken leg. You are ignoring your own reality. LeMay says product teams can’t hide behind "process" anymore. If you cannot explain how your work drives business impact, the rest of it—the perfect Jira board, the beautiful slide decks—it just doesn't matter.

Miles: It is that "learned helplessness" he talks about. We tell ourselves, "Oh, I can’t change the strategy, I just manage the backlog," or "Our leadership doesn't understand product-led growth." But LeMay’s counter is so empowering—he says you always have a move. No matter how messy the organization is, you can always choose to align your work with the things that actually keep the company alive.

Nia: I love that phrase—"you always have a move." It shifts the perspective from being a victim of a bad culture to being a proactive business owner. He even quotes Melissa Perri’s definition of product management—facilitating the exchange of value between a business and its customers. It is a two-way street. If the customer gets value but the business goes broke, you failed.

Miles: Right, and he is very blunt about why we avoid this. It is fear. Talking about money and revenue feels high-stakes. It is much "safer" to talk about story points or velocity because those are things we control. If we miss a revenue target, that feels like a personal failure. But LeMay argues that if you don't define what success looks like in business terms, you are taking on an even bigger, unacceptable risk—both for the company and your own career.

Nia: It is like that "Eye of Sauron" analogy he uses. Teams often avoid high-impact work because they don't want the C-suite looking over their shoulders. High-impact work is messy, it involves the CEO and the CFO, and it usually means your hands are going to get dirty in the "engine" of the product. It is way more comfortable to stay in the "bedazzling" phase—adding shiny, low-impact features that make the car look good while the engine is smoking.

Miles: And the tragedy is that the more "rhinestones" you glue onto that car, the harder it is to actually lift the hood and fix the engine later. Every low-impact feature adds coordination cost, technical debt, and noise. You end up in that spiral where you are so busy maintaining the "fluff" that you literally don't have the bandwidth to do the work that matters.

Nia: So, the first step is really just a mindset shift. We have to stop thinking of "the business" as this separate, annoying entity that interrupts our "real" product work. The business is our business. We are hired to make the company successful, not just to "do Scrum correctly."

Miles: Absolutely. And that starts with understanding the existential reality of the company. Are we trying to get acquired? Are we trying to hit an IPO? Are we just trying to survive until the next funding round? If the product team doesn't know the answer to that, they are flying blind.

Nia: Okay, so if we accept that we need to be impact-first, how do we actually define that impact? Because "make more money" is a bit too vague to put on a Trello card, right?

Miles: (Laughs) Yeah, "Number go up" isn't exactly an actionable strategy. LeMay talks about the need for "high impact and high specificity." He gives this great example of a team migrating users to a new platform. When he asked them how many users they needed to move and by when, they had no clue. They were just "working on the migration."

Nia: That is so common! We treat the work as the goal. But as soon as one senior engineer stepped up and said, "I think if we get a thousand users moved by the end of the quarter, that would be a win," everything changed. Suddenly, the team had a filter for their decisions. They could ask, "Does this feature help us hit that thousand, or is it a distraction?"

Miles: Exactly. Specificity is actually what gives you flexibility. It sounds counterintuitive, but if you have a very clear target—like converting a specific number of multi-product users because they have five times the lifetime value—you can be incredibly creative about how you get there. You aren't wedded to a specific feature on a roadmap; you are wedded to a result.

Nia: It’s like that conversation he had with the startup founder who said their "one metric that matters" was retention. When LeMay dug deeper, it turned out the real goal was just having enough cash in the bank to stay in business. Retention was just a hypothesis—a proxy. By identifying the actual existential goal, the team realized that if retention wasn't working, they could pull other levers, like new user acquisition, to hit the same financial target.

Miles: That is a crucial distinction. We often bake our strategy into our metrics and then get stuck when the strategy fails. If we keep the goal—the impact—at the center, we can pivot our outcomes and outputs as much as we need to. He mentions Christina Wodtke’s book Radical Focus here, specifically the idea that the company goal should be the center of gravity.

Nia: I love that visual. Instead of a massive, ten-level "waterfall" of OKRs that takes three months to cascade down, imagine the company goal in the middle, and every team is just one step away from it. Every team should be able to explain, in one simple sentence, how their work orbits that central goal.

Miles: And if you can't do that, you are probably "work-about-working" yourself into a hole. LeMay even suggests that if your internal goals aren't clear, go look at your company's investor reports or public promises. What did the CEO promise the market? That is your North Star. If you are working on something that doesn't help keep those promises, you are an at-risk investment.

Nia: He actually suggests asking yourself the "CEO Question"—if you were the CEO, would you fund your own team right now? Would you look at the work you are doing and say, "Yes, this is a great use of our limited capital"? If the answer is "I don't know," then you have some serious alignment work to do.

Miles: It’s a gut-punch of a question, but it’s necessary. And it leads to what he calls "impact estimation." You don't need a PhD in finance for this. It’s as simple as saying, "Okay, if we send this email to our users, what is the realistic open rate? Maybe fifteen percent? And of those, how many will actually convert? One percent?" Suddenly, you realize that your "big initiative" might only result in three new customers. Is that worth a month of dev time?

Nia: That kind of back-of-the-envelope math is a superpower. It stops the "velocity fetish" in its tracks. Instead of celebrating how fast we shipped the email, we are looking at the fact that the email itself was a low-impact move. It’s about choosing clarity over comfort, even if the clarity tells you that your favorite idea isn't actually going to move the needle.

Miles: One of the most practical tools LeMay offers for getting that clarity is the "One Page / One Hour" pledge. It is exactly what it sounds like—committing to spend no more than one hour creating a one-page document to start a conversation.

Nia: This is such a game-changer because it fights against "presentation culture." We’ve all been there—spending weeks on a hundred-slide deck that is "polished but vapid." LeMay argues that those long decks actually hide misalignment. People just look at the slides they care about and ignore the rest.

Miles: Right. He tells this story about a leadership team that had a massive deck for their strategy. He took an hour to boil it down to one page, and when he showed it to them, they absolutely hated it. They were furious. But as they started arguing over what he got "wrong," they realized they weren't actually aligned with each other. Each of them had written their own twenty slides in the big deck without reading the other eighty.

Nia: That is wild! So the one-pager acted like a lightning rod. It forced the disagreement out into the open. That is what we want—we want to find the misalignment early, before we spend six months building the wrong thing. In his view, alignment isn't about everyone nodding and saying "looks good." It is about making sure we are on the same page about the hard things.

Miles: Exactly. And the time box is key. If you need a month to write your strategy, you are probably over-complicating it. A good strategy should feel almost obvious once it’s articulated. It should be a clear response to a specific challenge. By limiting yourself to one hour, you are forced to focus on the core logic rather than the "fluff."

Nia: It also makes the work more collaborative. If I send you a one-page "strawman" document, it’s easy for you to give feedback or even rewrite a section. If I send you a forty-page PDF, you are just going to skim it and say "thanks." The "One Page / One Hour" approach invites people into the process.

Miles: It’s about moving from a "report and critique" culture to a "co-creation" culture. In a lot of companies, people just want to sit in the "critique chair." They wait for the PM to present the perfect plan so they can point out the flaws. LeMay wants to blow that up. He wants everyone—engineers, designers, marketers—to be on the hook for the impact, which means they all need to be involved in the thinking.

Nia: And for the product managers listening, this is how you manage up, too. Instead of asking for permission to do something, you present a one-pager that says, "Here is the business problem, here is our hypothesis, and here is how we will measure success." It’s much harder for a leader to say no to a well-reasoned business case than to a vague feature request.

Miles: It also helps with the "Eye of Sauron" problem. When you provide clear, concise updates that are tied directly to business impact, leadership feels like they have a handle on what’s happening. They don't feel the need to micromanage because you are speaking their language. You are providing clarity, which is the most valuable thing you can give a busy executive.

Nia: I’ve started doing this with AI, actually. I’ll just talk through my messy thoughts with a voice-to-text tool, have it summarize the core points into a one-page structure, and then I spend my "one hour" refining the logic. It makes the "blank page" problem disappear and gets me to the conversation faster.

Miles: That is a perfect use of the tech. Use the AI to handle the "work about the work" so you can focus on the "impact." Because at the end of the day, a one-pager isn't a deliverable—it’s a conversation starter. If it doesn't lead to a better decision, it’s just more output.

Nia: Speaking of decisions, Miles, there was another technique LeMay mentioned that I found fascinating—the "three-option framing." It sounds so simple, but the psychology behind it is brilliant.

Miles: It really is. Most product conversations get stuck in a "yes or no" trap. "Should we build this feature? Yes or no?" That immediately puts people in an adversarial position. If I say yes and you say no, we are just negotiating.

Nia: Right! But if you present three distinct options—Option A, Option B, and Option C—the whole dynamic shifts. Now we are comparing different ways to achieve the same impact. We are looking at the trade-offs.

Miles: Exactly. LeMay suggests that three is the magic number. Two options can still feel like a "this or that" choice, but three forces you to dimensionalize the problem. One might be the "fast and cheap" version, one might be the "high-impact, high-risk" version, and one might be the "balanced" approach.

Nia: He tells a story about a roleplay exercise where a PM presented one option to an executive, and the exec immediately started tearing it apart—"What about this? Why didn't you consider that?" But when a different PM presented three options and said, "We recommend Option B because it optimizes for X," the executive started asking much better questions. They started talking about what they were optimizing for, rather than just what they liked or disliked.

Miles: That is the key—it reveals the hidden criteria for success. Often, leadership hasn't fully articulated what is most important to them. By showing them different paths, you force them to say, "Actually, I care more about speed to market right now than I do about long-term scalability." That is a massive piece of clarity for the team.

Nia: It also builds trust. It shows that the product team has done the homework. They aren't just "falling in love with their first idea," as the saying goes. They have explored the space and are making a reasoned recommendation based on the business context.

Miles: And it helps the team avoid that "Eye of Sauron" micromanagement. If you only give an executive one option, they feel like their only job is to be the "quality control." They have to find something wrong with it to feel like they are adding value. But if you give them choices, you are inviting them to be a strategic partner. You are giving them a role in the decision-making process that isn't just "gatekeeper."

Nia: I think this also applies to how we work with engineering. Instead of just handing over a spec, we can say, "Here are the three ways we could solve this business problem. Option A is a quick hack, Option B is a solid build, Option C is the dream state. Which one gives us the best ROI given our current sprint?" It makes it a shared business decision.

Miles: It’s all about getting out of that "order-taker" mindset. If you are just asking "yes or no" on features, you are a feature factory. If you are presenting options for impact, you are a product team. And as LeMay says, even if you have to eventually build the thing leadership wants, having that "Option C" on the table can sometimes act as a pressure valve or a way to highlight what you are giving up.

Nia: It’s such a powerful move. It’s about creating a "system" for alignment rather than just hoping people agree with you. And it ties back to that "high specificity" we talked about. Each option should have a clear, estimated impact. "Option A gets us 500 users by June; Option B gets us 1,000 users by August." Now we are having a real business conversation.

Miles: One thing that often stops teams from being impact-first is the fear of dependencies. We’ve been taught to "atomize" our goals so that our team has 100% control over the outcome. But Nia, LeMay points out that the most impactful work almost always crosses team boundaries.

Nia: It’s the "Eye of Sauron" again! If you work on something that involves marketing, sales, and three other engineering squads, it’s going to be slow and complicated. But that is also where the real money is. If you only work on the tiny corner of the app that no one else cares about, you might have high velocity, but your impact is basically zero.

Miles: Exactly. He worked with one team that resisted setting impact-level goals because they said, "Well, if we do that, we’ll have to work with marketing." And his response was basically, "Yes! That is the job!" Product doesn't exist in a vacuum. If you aren't working with the people who bring the product to market, you aren't really doing product management.

Nia: It’s that "orbit" idea again. If multiple teams are orbiting the same company goal, they should be coordinating, not trying to pretend the other teams don't exist. He mentions a workshop where four different teams realized they were all trying to impact the same part of the funnel. Instead of seeing that as a "dependency" problem, they saw it as an opportunity to amplify each other.

Miles: "Dependency" is often just a scary word for "collaboration." If we align our goals at the impact level, we can see how our work fits into the bigger system. One team might be driving more people into the top of the funnel, while another is improving the conversion rate. If they don't talk, they might both hit their individual "output" goals but fail to move the needle for the company.

Nia: This is where that "velocity fetish" really hurts us. We prioritize the team that "gets stuff done" in their silo over the team that is doing the hard work of aligning across the organization. But shipping ten low-impact features is actually worse for the company than shipping one high-impact feature that required a month of coordination.

Miles: Right, because those ten useless features are just adding to the "low-impact death spiral." They make the product more complex and the "engine" harder to reach. LeMay argues that we have to value the "unseen work" of alignment. It isn't "work around the work"—it is the work.

Nia: It reminds me of the car analogy again. If the marketing team is bedazzling the car with rhinestones while the product team is trying to fix the engine, the car is still going to break down. We have to be on the same page about whether we are fixing the engine or decorating the hood.

Miles: And it requires a level of humility. You have to be okay with the fact that your team might not get 100% of the credit for a win. If the revenue goes up, was it the new feature or the great marketing campaign? LeMay says: who cares? If the company is successful, everyone wins. Instead of fighting over attribution, we should be figuring out how to do more of what worked.

Nia: That is such a healthy perspective. It moves us away from this "hero PM" culture where I have to prove that my feature was the one that saved the day. If I can help the marketing team be more effective by providing better data or a smoother onboarding flow, that is a massive win for the business, even if I didn't "ship" a flashy new button.

Miles: It’s about being a "business owner" first and a "product person" second. When you care more about the existential success of the company than the specific "way" you do your job, the silos start to melt away. You start asking, "What is the most important lever we can pull right now?" regardless of whose department it sits in.

Nia: Miles, we keep coming back to this idea of "velocity," and I think it’s because it’s so deeply ingrained in how we measure software teams. But LeMay is very clear: speed without direction is just a faster way to get to the wrong place.

Miles: It is the ultimate proxy metric. We use velocity because it’s easy to measure and it makes us feel like we are "doing something." But in the age of AI, where we can generate code and ship features faster than ever, velocity is becoming less and less of a competitive advantage.

Nia: That is such a good point. If everyone can ship fast, then "fast" isn't a strategy anymore. The differentiator becomes what you choose to build. It’s about discernment. LeMay argues that the "cost of shipping" is going down, but the "cost of complexity" is staying the same or even going up.

Miles: Exactly. If you use AI to ship twenty mediocre features in a week, you’ve just created a massive maintenance headache for yourself. You’ve accelerated your way into the death spiral. We have to shift our celebration from "Look how much we shipped" to "Look what changed for our customers and our business."

Nia: He mentions that the most effective product managers he knows—like a team he visited in France—are actually the ones who don't have a "busywork" culture. They want to do the most meaningful work and then go home and have a life. Because they aren't trying to "prove" their value through a high volume of output, they are forced to be much more selective about what they actually spend their time on.

Miles: I love that. "Laziness" can actually be a superpower if it’s channeled into finding the shortest path to impact. If I only want to work six hours a day, I’m going to be very, very careful about which Jira tickets I pull into the sprint. I’m going to look for the high-leverage moves that don't require a hundred hours of "bedazzling."

Nia: It’s a total rejection of "hustle culture." LeMay admits that early in his career, he thought being a "good PM" meant working sixty hours a week and "doing whatever it takes." But he realized that companies often don't reciprocate that sacrifice, and more importantly, it doesn't actually lead to better products.

Miles: Right. He even changed a core principle in the second edition of his other book, Product Management in Practice. It used to be "no work above, no work beneath," which can be weaponized to make people do endless grunt work. Now it is "all efforts in service of outcomes." That is a much healthier boundary.

Nia: It puts the focus back on the result. If doing the "grunt work" helps us hit our revenue goal, fine. But if we are just doing it to "look busy" or because we have a "hustle" mindset, we are wasting the company’s resources. We should be the ones cutting the "work about the work," not adding to it.

Miles: And this applies to our rituals, too. Why are we having this stand-up? Why are we doing this grooming? If these rituals don't help us stay aligned on impact, we should change them. LeMay’s whole "Impact-First" approach is a call to be pragmatic. If Scrum is getting in the way of shipping value, fix the Scrum, don't just "do it harder."

Nia: It’s about being "impact-led" rather than "process-led." The process is just a tool. If the tool is blunt, you don't just keep hitting the nail with it; you go find a sharper tool. Or you ask if the nail even needs to be there in the first place.

Miles: We’ve covered a lot of the "why" and the high-level frameworks, but I want to make sure we give our listeners some real "Monday morning" moves. If someone is sitting at their desk feeling like they are trapped in a feature factory, where do they start?

Nia: The very first thing, according to LeMay, is to stop pretending you don't care about the business. Go find those investor reports, or listen to the last town hall recording. Identify the one thing the company is most worried about right now. Is it churn? Is it a specific competitor? Is it hitting a profit target?

Miles: Once you have that, do the "one-step ladder." Look at your current roadmap and ask, "Can I explain, in one sentence, how this feature directly impacts that big company worry?" If you can't, that is your first "move." Start a conversation. Use the "One Page / One Hour" rule to write down your concerns and suggest a more impactful alternative.

Nia: And don't do it alone! This is about "Impact-First Product Teams," not just the PM. Bring the engineers and designers in. Ask them the "CEO Question"—"If we were paying for this out of our own pockets, would we still build this?" You’d be surprised how much clarity you get when you frame the work as a personal investment.

Miles: Another great move is "impact estimation." Before you start the next sprint, take ten minutes to do the math. "If this feature works perfectly, what is the best-case scenario for the business?" If the answer is "not much," then you have a strong case for reprioritizing. It’s not about being a pessimist; it’s about being a realist.

Nia: I also love the "three-option" move. The next time you have to present a plan to your manager or an executive, don't just bring one roadmap. Bring three versions. Show them the "low-risk, low-reward" version, the "high-impact, high-effort" version, and your recommended "sweet spot." It changes the conversation from "Are you doing what I told you?" to "Which of these business paths should we take?"

Miles: And finally, don't be afraid of the "Eye of Sauron." If you want to do high-impact work, you have to be willing to engage with the people who run the company. Speak their language—talk about revenue, retention, and risk. When you show them that you are just as focused on the company’s survival as they are, they stop being "scary bosses" and start being stakeholders you can actually collaborate with.

Nia: It’s really about choosing clarity over comfort every single day. It’s more comfortable to just take orders and ship features, but it’s more impactful to ask the hard questions and focus on the work that actually matters. LeMay’s message is ultimately one of hope—you aren't just a cog in a machine. You have agency.

Miles: "You always have a move." I think that is the perfect mantra for any product person. Whether you are at a tiny startup or a massive corporation, you can always choose to point your efforts toward real-world impact. It’s not just better for the company—it’s better for your career and your own sanity.

Nia: Absolutely. Being in an "impact-first" team means you aren't just "busy"—you are indispensable. You are the person who understands how the engine works and how to keep the car on the road. And that is a much better place to be than just bedazzling the hood.

Miles: As we wrap this up, Nia, I’m struck by how much LeMay’s philosophy is really just a return to the roots of what product management was always supposed to be. It is not about being a "mini-CEO," but it is about being a business-minded problem solver.

Nia: Right. It’s about getting past the "framework madness" and the "velocity theatre" and getting back to the simple exchange of value. I think for everyone listening, the biggest takeaway is that impact isn't something that just happens if you follow the right process. It has to be the starting point.

Miles: Exactly. "Impact-first" isn't a destination; it’s a lens. It’s a way of looking at every meeting, every ticket, and every roadmap item and asking, "Is this the best way to ensure our company lives to fight another day?" It’s a demanding way to work, but as LeMay found, it’s also the way that makes people the happiest.

Nia: There is something deeply satisfying about knowing your work actually matters. When you can see the direct line from your keyboard to the company’s success, the "ambiguity" of product management becomes a lot more manageable. You aren't just guessing; you are experimenting with purpose.

Miles: So, to our listeners, I’d encourage you to pick just one of these moves for next week. Maybe it’s the one-pager, maybe it’s the three-option framework, or maybe it’s just asking that "CEO Question" in your next team meeting. See what happens when you prioritize impact over output.

Nia: And don't be discouraged if it feels messy at first. Moving from a "feature factory" to an "impact-first" team is an incremental journey, not a revolution. It happens one conversation at a time. But as LeMay says, 90% of product management is just not letting yourself get trapped.

Miles: You have the keys to the trap! You just have to be willing to use them. It’s been such a fascinating deep dive into this book. It really challenges a lot of the "comfortable" myths we tell ourselves in the product world.

Nia: It really does. I’m definitely going to be more careful about my "rhinestone-to-engine" ratio from now on. Thank you so much for joining me for this, Miles. It’s been a blast.

Miles: Same here, Nia. And thank you to everyone for listening. We hope this gives you some fuel for your own "impact-first" journey.

Nia: Take a moment to reflect on your current roadmap—is it a list of features, or a list of intended impacts? That might be the most important question you ask all week. Thanks for spending this time with us!

Miles: Cheers, everyone. Go make an impact.