Product Practice #299 |
Dear Reader,
Independent of the specific metric "framework" (think NSMs or OKRs), companies need a clear understanding when asking teams to work on their Input or Output Metrics.
From my perspective, two approaches exist to develop shared language: The deterministic definition and the relative position of metrics.
Personally, I associate the deterministic definition with the work of Josh Seiden (and others). Outputs are shipped features, produced artifacts, or completed activities to drive an Outcome. Inputs describe the allocated resources (people or time) to produce an Output. Let‘s use a made-up Miro example below.
Relative position considers a metric's relationship to another. Brian Balfour, Shaun Clowes, and Casey Winters describe them like this: „Input metrics are leading indicators and output metrics are lagging indicators. By definition, it can take time for the output to reflect positive or negative changes in the inputs.“
But what is an Input or an Output is a question of perspective, as shown on the simplified KPI tree below. Make sure to consider that when choosing metrics.
No matter the approach, the leading and lagging nature of each metric determines how useful the metric is for the product team. Don‘t just paint by the numbers, but check the potential metrics against your criteria for usefulness and value.
None of these approaches is „better“ or more correct than the other. What matters is that your company agrees on a set of terms and definitions for a shared understanding. This comparison might help with the confusion when some insists that "Outputs are bad." Outputs are often helpful starting points for metrics discussions and can mean two different things.
That's (almost) all, Reader. If you enjoyed today's issue, please do reply (it helps with deliverability). If you didn't, you can unsubscribe here.
Thank you for Practicing Product,
Tim
What did you think of this week's newsletter?
Click here if you only want to see what's behind each option
As a Product Management Coach, I guide Product Teams to measure the progress of their evidence-informed decisions.
I identify and share the patterns among better practices to connect the dots of Product Strategy, Product OKRs, and Product Discovery.
1 tip & 3 resources per week to improve your Strategy, OKRs, and Discovery practices in less than 5 minutes.
Product Practice #368 How a Product Vision Board saved my Strategy READ ON HERBIG.CO PUBLISHED Jun 20, 2025 READING TIME 3 min & 53 sec Dear Reader, I once led a newly formed product team that aimed to develop a product to increase the monetization of a specific user segment. I co-led a long Discovery effort that validated and scoped this product. At one point during our Delivery journey, my boss approached the team while I was on leave and asked them what they were trying to accomplish....
Product Practice #367 3 Prompts to help TeamsGo from KPIs to OKRs READ ON HERBIG.CO PUBLISHED Jun 13, 2025 READING TIME 3 min & 56 sec Dear Reader, In theory, distinguishing KPIs from OKRs should be simple. KPIs are reactive metrics you monitor, but only act on when they exceed or drop below a certain threshold. Think revenue or conversion rate. Objectives and Key Results (OKRs) contain proactive metrics that help you measure your progress towards strategic priorities. Consider revenue from a...
Product Practice #366 Why bol.com made itsgoal-setting more pragmatic READ ON HERBIG.CO PUBLISHED Jun 6, 2025 READING TIME 5 min & 30 sec Dear Reader, This is the final part of my mini-series on how bol.com, one of Europe's largest e-commerce companies, shapes its fintech products. After exploring their product definition and discovery practices, let's look at how they've adapted traditional goal-setting frameworks to their reality. Particularly as a function that wears two hats, enabling...