Takeaways
đ Most product teams donât understand revenue. They know user needs, but not what closes a deal. They talk to customers, but rarely prospects. Thatâs a big gap. Product decisions often ignore willingness to pay, sales pressure, and retention blockersâbecause theyâre seen as âsomeone elseâs job.â
đ They moved from slow waterfall to fast Agile. But fast doesnât mean right. Shipping the wrong thing quickly just piles up tech debt and wastes money. In todayâs worldâwhere capital is expensive and every headcount countsâteams need to prove impact. Not story points.
đ Product education focuses on craft, not commercial understanding. Most PMs hear about financial literacy only when they hit VP level. By then, itâs almost too late. It should start earlierâwith simple questions: how does the company make money? What metrics does the CFO care about? What would make a customer renew?
đ Most teams track too many things. That spreadsheet with 35+ metrics? Nobodyâs driving any of them. Instead, pick a few business-aligned metrics. Review them weekly. Cut the noise. Track progress. Adapt fast.
đ Teams often mirror the platform, not the customer. But real impact comes when teams are aligned to outcomes across the journeyâactivation, engagement, retention. Itâs uncomfortable. It creates overlap. But it gets results. Features donât win markets. Experiences do.
đ Should product own revenue? Yes. Every team is a revenue team. The pushbackââwe canât control the saleââis weak. Sales canât control it either. But everyone contributes. R&D should have revenue targets. Even platform teams. Even engineers. Especially engineers.
đ Some decisions are art, not science. Outdated UI killing deals? You wonât have hard numbersâuntil itâs too late. Use industry benchmarks, customer signals, support tickets, and experience. Know when to trust your gut. But gut â guess. Back it with rationale.
đ A product team that costs $1M/year must deliver $3â5M/year in value. Most bets wonât pay off. The few that do must cover the rest. Thatâs the math. If your initiative isnât worth at least $5M/year, why build it?
đ Donât get paralysed by perfect metrics. Just start. Review every 30â90 days. Adjust. Test assumptions fast. Kill slow-moving re-platform projects before they kill you.
đ Empowered teams arenât just given freedom. Theyâre given trust. Right now, fear dominates. Layoffs. Burnout. Board pressure. The result? Output obsession. Rebuilding safety and alignment starts at the top. Executives must cascade clarity, not anxiety.
đ Forget product books for a bit. Read about valuations. Talk to your CFO. Sit in on sales calls. Study why companies growâor die. Read business case studies. Learn the language of money.
Top Quotes
đŹ Incentives and goals drive behavior... if product and engineering are incentivized based on delivery or outputs, then thereâs no motivation or change to behavior to really understand whatâs driving the business.
đŹ We default to building software, which is super expensive and most often than not, unvalidated
đŹ We are still at a point where we're keeping engineering in a basement and there's so much discomfortâthey're locked away, stop talking to them
đŹ People are so anxious and what people do when they're anxious is they do the easiest thing to control, which is build output, output, output.
đŹ Everybody talks about empowered teams, everyone loves that term, but nobody actually isâand it starts at the top.
Episode: Mackenzie Hughes & Tara Goldman: From Jira Junkies to Profit Prophets