Lore

product management

How to align product work to business goals | Corinna Stukan (CEO, Bizzy)

Karina argues that most product-business misalignment comes from product people failing to connect their day-to-day work to how the business actually makes money, and that closing this gap requires curiosity and disciplined communication (asking stakeholders directly, using tools like a metrics one-pager, limiting messages to 2-3 points) rather than financial credentials or precise revenue-attribution math.

Mind the Product · 2026-02-25 · English

Key ideas

  1. Misalignment occurs when a product leader can't trace their specific work (e.g., onboarding) through customer acquisition, strategic segment growth, and up to revenue.

  2. Karina broke a prioritization deadlock only after asking a CEO directly what the business cared about and where the money came from.

  3. At a past company, she learned 90% of revenue came from one specific customer segment — information no one had shared and she'd never asked for.

  4. Business acumen, as she defines it, is not about reading financial statements or holding an MBA/CFO credential — it's curiosity about how the business simply makes money.

  5. Misalignment has two structural causes: organizations often don't share real business goals/numbers with teams, and product roles are frequently hired/structured around delivery rather than outcomes.

  6. Product management historically was closer to outcomes (product, packaging, sales, go-to-market) and drifted toward backlog/delivery execution; the field is now correcting back toward business context.

  7. The 'metrics one-pager' exercise maps the top current business goal, then shows how the product and its sub-areas (acquisition, engagement, retention) connect to it, before any roadmap work happens.

  8. For marketplace businesses, the 'matching rate' between two parties is typically the core metric driving the revenue goal.

  9. Strategy has three parts — where we are, where we're going, how we'll get there — and misalignment usually stems from the 'how' never being communicated.

  10. Karina frames opportunity areas as 'bets,' chosen collaboratively with the team each quarter, with roadmap creation happening only afterward.

  11. New hires proposing 'wrong' roadmap ideas shouldn't be penalized, since the missing 'how' is typically a leadership communication failure, not a thinking failure.

  12. Karina self-critiques her earlier PM communication as 'fluffy' (e.g., 'improve onboarding so customers are less frustrated'), which didn't land with financially-driven stakeholders competing for ROI-justified budget.

  13. The interviewer's output → outcome → impact model frames 'impact' (business/financial translation) as the piece most often missing from product communication.

  14. Overcorrecting into pure business-speak is its own failure mode — reframing customer-facing work entirely in commercial terms can distort the actual story.

  15. Precise revenue attribution to a single team's work is generally unrealistic; Karina calls chasing it 'a waste of time,' citing that customers may need ~12 touch points before signing up, spanning marketing, product, design, and engineering jointly.

  16. Over-attribution attempts in large organizations devolve into unproductive 'attribution fights' between departments.

  17. Citing research that people retain no more than 2-3 arguments/benefits at once, Karina limits every presentation slide to 2-3 key points.

  18. Presentations should be numbers-first, short, and end with recommended actions after context is established; she cites a client's 76-page roadmap deck as a cautionary example.

  19. Karina uses LLMs to aggregate/summarize recurring reports (monthly KPIs, CRM qualitative notes) via a personal 'internal agent,' but avoids using LLMs to simulate stakeholders, believing that understanding real people in the room can't be replaced by AI.

  20. She profiles stakeholders as 'numbers people,' 'business-impact people,' or 'story/context people' based on role and background (e.g., CFO vs. Chief Experience Officer).

  21. Her top technique for high-stakes presenting is treating it as 'discovery': asking stakeholders directly if content is relevant, reading body language even on video calls, and adjusting the next presentation based on what's learned.

  22. When stakeholders are under heavy delivery pressure, she advises framing requests as ways to help/contribute rather than repeatedly asking for more.

  23. Metrics one-pager exercise — A single-page mapping exercise that puts the company's current top-level business goal at the top and shows how the product and its sub-areas (acquisition, engagement, retention, etc.) connect to it, built with or validated by key business stakeholders. Apply: Draft the goal-to-product hierarchy yourself or with stakeholders, get feedback, and use it to open roadmap conversations with 'we're here, we want to go there, here are the opportunity areas' before proposing a roadmap.

  24. Output → Outcome → Impact framework — A three-stage model distinguishing the thing built (output), the behavioral/business result it drives (outcome), and its translation into financial/business language (impact) — with impact identified as the stage most often left out of product communication. Apply: When presenting work, explicitly state all three layers — what was built, what changed as a result, and what that means in the business's financial or strategic terms — rather than stopping at output or outcome.

  25. Strategy's three-part structure (where we are / where we're going / how we'll get there) — A framing of strategy as three elements, where misalignment typically arises because the 'how' is either never articulated or misunderstood, leaving people to substitute their own hypothesis. Apply: Leaders should explicitly state all three parts, including the often-skipped 'how,' and treat filling it in as a collaborative exercise with the team rather than assuming it's self-evident.

  26. "Bets" framing — Naming specific market/opportunity areas (e.g., industry verticals with high demand) as 'bets' that the team collectively chooses to pursue for a given period, done before any roadmap is created. Apply: After sharing current state, target state, and observed opportunities, get the team to agree on 2-3 'bets' for the coming quarter, then build the roadmap around those bets.

  27. Marketplace matching-rate metric — The observation that two-sided marketplaces typically generate revenue at the moment two parties are successfully matched, making 'matching rate' the metric that most directly drives the top-level revenue goal. Apply: In a marketplace business, when building the metrics one-pager, identify and prioritize the matching-rate metric as the primary link between product work and revenue.

  28. Two-to-three-point rule — A rule, attributed to research Karina cites, stating that audiences cannot retain more than two or three arguments or benefits presented at once, so adding more points reduces overall retention. Apply: On every slide or pitch, ask 'what's the key message here' and cut content down to the two or three most important points rather than listing every benefit.

  29. Numbers-first, short-deck presentation structure — A presentation format that leads with numbers, then builds the story around them, structured as goals → where growth will come from → roadmap → current tracking vs. goals → data learnings → recommended actions (placed last). Apply: Structure stakeholder decks in this order, keep them as short as possible since senior audiences want headlines, and place the ask/recommendation at the end after context has been established.

  30. Discovery-based stakeholder presenting — Treating presentations to stakeholders as an ongoing discovery process — asking directly whether content is relevant, reading body language (including on video calls) for disengagement, and using what's learned to adjust the next presentation. Apply: During and after presentations, ask stakeholders direct questions ('is this relevant?', 'is something missing?'), watch for signals like shifting in their seat or raised eyebrows, and incorporate what you learn into how you frame the same topic next time.

  31. LLM as internal reporting agent — Using an LLM as a personal 'internal agent' to aggregate and summarize recurring, formulaic reporting — combining quantitative KPIs with qualitative CRM notes (customer feedback, deal notes) into a consistent report format. Apply: Automate the data-aggregation and summarization layer of regular reporting (e.g., monthly KPI check-ins) with an LLM, while keeping stakeholder-specific framing and persuasion judgment as a human task.

  32. LLM-as-virtual-stakeholder review — A technique the interviewer describes some teams using, where a presentation deck is given to an LLM prompted to act as a virtual replica of a specific stakeholder, asking it to flag what's missing or could be misunderstood — not to draft the content itself. Apply: Feed a near-final deck to an LLM configured to represent a target stakeholder's perspective and ask it to critique gaps or ambiguities before the real presentation; Karina notes she personally doesn't use this, believing it can't replace knowing the actual people in the room.

Insights

The 90% revenue-concentration discovery came only from asking directly, not from analysis — implying organizations often withhold or fail to surface which segment matters most even from the people making prioritization calls.

Blaming new hires for 'wrong' strategic proposals is reframed as misplaced: the real defect is leadership's failure to articulate the 'how,' turning roadmap missteps into a leadership communication gap rather than an execution error.

Precise cross-team revenue attribution is presented as actively counterproductive rather than merely hard — 'attribution fights' are framed as an organizational pathology to avoid, not a measurement problem to solve.

Overcorrecting toward commercial framing is treated as symmetric to under-communicating business value, implying there's a narrow band of 'just enough' translation between customer language and business language.

Karina treats repeated live practice as more valuable than any framework — 'nothing beats being in that room' — positioning tools like the one-pager as scaffolding rather than a substitute for reps.

She draws a specific boundary around LLM use: offloading the 'admin' layer of reporting to AI while deliberately keeping stakeholder-reading and persuasion as an exclusively human task, a line other practitioners (per the interviewer) draw differently by using LLM role-play for stakeholder simulation.

She collapses the boundary between product, sales, and marketing by framing product work as inherently a selling function and discovery as a transferable skill across all three.

«If you as a product leader can't connect the dots between I'm working on this onboarding experience now that will help us with acquiring more customers and that matters because we want to grow in this segment and that will make us more money. If you can't connect those dots that's when we have that misalignment issue.»

— 00:00

«I was trying to prioritize all these things that we had to do and it was actually impossible until I went and had a conversation with the CEO of that company and asked what do you really care about? How does this all work together? Where's the money coming from?»

— 00:14

«What the CEO shared in this moment was that 90% of the revenue came from a very specific target segment of their customers which I actually I just didn't know.»

— 09:28

«I didn't go through any of the financial statements here or through the numbers. I didn't become a CFO. I didn't have to do an MBA for this. I just had to actually ask the questions about what makes a business money.»

— 10:06

«So then it becomes an attribution game or an attribution fight between different departments and I think that's fundamentally... not it's not very productive.»

— 22:51

«There's no way either of us, neither marketing nor our product designer nor our engineering team can say exactly this change contributed to X amount of revenue growth. And I think it's just a waste of time if I'm being blunt.»

— 23:49

«You only grow confidence where you have not... where you have none. So you just actually have to do it.»

— 26:05

«It's always harder to make it shorter than to make it longer.»

— 26:42

«The more you add the more it actually takes away from the points you were really trying to make.»

— 28:59

«To me, the things that an LLM can't replace for me is knowing and understanding the people and the personalities in the room.»

— 30:08

«I always say you're in the job of selling whatever your job is.»

— 34:20

«Don't just talk at them. Actually ask the question, is this relevant?»

— 34:55

«It does. Yeah. I use discovery in sales and marketing in any area. So the product hat comes in handy in so many things in life.»

— 36:33

Reception

No comments are available, so audience reception cannot be determined.

The interview offers a coherent, practitioner-grounded case for treating business acumen as curiosity rather than credentialism, backed by concrete frameworks (metrics one-pager, output-outcome-impact, discovery-based presenting), though its research citations (e.g., the 2-3 argument retention limit) are asserted without sourcing and its evidence is largely anecdotal to Karina's own career.

37:17

↳ Mind the Product · YouTube

Watch original