MECE: Double the Usefulness
|
Dear Reader,
Many resources say your metrics trees need to be "MECE." But how do you do it?
MECE stands for:
Mutually
Exclusive
Collectively
Exhaustive
In the context of metrics trees, this means mapping the individual drivers of an overarching goal in a way that allows us to identify and improve domain-specific levers through selective focus, while creating holistic improvement.
Let's take the example of being an online micro coffee roasting brand (wild idea, right?).
A high-level metric could be Total Profit. Instead of jumping straight into (and getting lost) in various metrics that are easy to throw around, let's collect the driver categories first. There isn't one right way to create a MECE metrics tree. So, here's one starting point:
Sales Volume
Unit Economics
Coffee Quality
From here, we want to find one main representative metric for each category, and then connect its individual drivers (which could also each be broken down further).
Sales Volume: Represented by Number of Bags Sold, which could be driven by Number of Website Visitors and Conversion Rate.
Unit Economics: Represented by Average Margin per Bag Sold, which could be driven by Raw Material Purchase Price and Labor Cost.
Coffee Quality: Represented by Average Purchase Rating, which could be driven by Roasting Process Consistency Adherence and Average Bean Supplier Rating.
You could add more driver categories, like product variety or production volume. But I save these for the secret business plan in this daydream of mine. 🤫
Yes, you could also map these out into a long vertical correlating branch. But that can make levers to focus on getting buried quickly.
Now, here's the thing: Understanding MECE is one thing. Actually building metrics trees that drive real decisions in your organization, connecting them to your North Star Metrics, OKRs, and KPIs, is another.
That's exactly what I'm covering in my upcoming free metrics masterclass: "Use Real-Life Metrics Trees to Define NSMs, OKRs, and KPIs."
In 60 minutes, you'll learn:
📅 March 4th at 5:00 PM CET | 60 Minutes | Hands-on Live Cases | No Recording
| CLAIM YOUR FREE SPOT |
Thank you for Practicing Product,
Tim
As a Product Management Coach, I guide Product Teams to measure the real progress of their evidence-informed decisions.
I focus on 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. Explore my new book on realprogressbook.com
Product Practice #399 How to Connect Strategy,Goals and Discovery PUBLISHED Mar 12, 2026 READ ON HERBIG.CO Most product teams don't have a strategy or OKR problem. They have a connection problem. My new Progress Wheel Intensive is a full-day working session for ambitious product teams where we fix that together — using your actual product context, not hypotheticals. Book a call to talk about it. Dear Reader, Often, the core concepts I share on how teams can make real progress by connecting...
Product Practice #398 The AI-Assisted ProductDiscovery Cheatsheet PUBLISHED Mar 6, 2026 READ ON HERBIG.CO Dear Reader, I'll cut to the chase: A few weeks ago, I thought about synthesizing high-level guidance on what stays the same and what needs to change in Product Discovery with AI - beyond the ever-changing tool details. So, I reached out to one of my favorite Product AI-thinkers right now, Julia Bastian (who's knowledgeable, pragmatic, and practical), and we compiled this graphic for you....
Product Practice #397 3 Things to Put into YourNext Strategy Document PUBLISHED Feb 27, 2026 READ ON HERBIG.CO Dear Reader, The most effective strategy document I've seen doesn't worry about the looks or format. Whether it's a scrappy Google Doc or a fancy Miro template, what matters is the quality and cohesiveness of the information it contains. Make sure what you cover aligns with your company's expected standards to ensure stakeholder understanding and, consequently, buy-in. But make sure...