The Progress Wheel: My favorite Structure to Connect the Dots


The Progress Wheel: My favorite Structure to Connect the Dots

READ ON

HERBIG.CO

PUBLISHED

May 9, 2025

READING TIME

4 min & 48 sec

​Dear Reader,​

Real Progress happens when you choose methods because they create value for you in your context, and you can use each domain to improve the others.

To make Real Progress, teams need to understand and practice two core ideas:

  1. Putting the value of a practice before the selection of a method or framework is crucial to avoid getting lost in chasing correctness.
  2. Letting different practices reinforce each other so you don’t get lost optimizing the local maximum of a specific method.

Especially when teams treat practices as isolated activities, they often fall into the trap of Alibi Progress - optimizing the correctness of one practice while losing sight of how it connects to the overarching priorities.

To counter this, these practices shouldn’t live in isolation. Each practice informs, strengthens, and enhances the effectiveness of the others, forming what I call the Progress Wheel.

The Progress Wheel is a way of thinking that strengthens your development by showing that questions in one domain often require answers from another.

Useful OKRs turn strategic directions into measurable, actionable priorities for teams. They translate broad strategic choices into specific changes in customer behavior and business impacts.

Example: Your strategy may focus on “Become the leading productivity solution for remote-first teams through customization,” but OKRs specify exactly what measurable change (e.g., increasing weekly active usage of collaboration features from specific types of customers) will demonstrate tangible progress.

OKRs need strategic guidance to have clear meaning, or they risk being generic evergreen metrics instead of strategically aligned measures of success.

Example: When strategy clearly articulates "winning through customization options," teams replace general retention goals with targeted OKRs like "increase saved custom workspace configurations by 45% among power users."

Clearly defined OKRs guide Discovery efforts toward reducing the most critical uncertainties.

Know someone who might like this? Share it with them here.

Example: If an OKR seeks to double user activation rates, Discovery prioritizes assumptions around activation and early user engagement, streamlining efforts.

When you're stuck in isolated practices, try moving around the Progress Wheel:

Strategy unclear? Look to Discovery for validated problems worth solving.

OKRs not moving? Check if they connect to strategic priorities.

Discovery overwhelming? Let Strategy focus your research.

Did you enjoy the newsletter? Please forward it. It only takes two clicks. Creating this one took two cups of coffee.

Thank you for Practicing Product,

Tim

PS: How do I know I’ve done enough discovery? Is exactly the type of question I answered in my conversation with Francesca Cortesi on the Tough Stuff Product Podcast. Tune in on Spotify or YouTube.

Content I found Practical This Week

What Successful Product Organizations Have in Common

If you’re a PM, this is your reminder to focus on the work that matters: following up, writing it down, collaborating, creating alignment and clarity, and delivering. And if you’re a product leader, remember that your team looks to you to set the tone. Create the environment, model the habits, and make sure your team knows: doing the work is the real superpower. So, the next time you feel derailed, lose orientation, or get stuck, turn to these first principles —they’re the foundation of every successful product team.

Why you should treat your company as a product

Outcome-driven leaders treat each element of the organization as a “product feature” that exists to help the organization succeed. These “organizational features” include things like processes, metrics, rituals, reports, structure, data, tools, skills, and behaviors.

Designing Frameworks with Clarity

The goal is to identify the existing key concepts in the domain of interest. This information comes in all kinds of types: explicit information from books and documents, heuristics that aren’t documented but communicated within a culture, and personal experience, to name a few. This is essentially a big dump of information; similar to a brainstorming. The output of this work is a content library. Your subject domain is determined by the purpose you defined previously. As you can imagine, it’s easy to drown in information overload during this phase. Without expertise in a domain, where do you even start? The key skill here is the art of questioning

Who is Tim Herbig?

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.

Product Practice Newsletter

1 tip & 3 resources per week to improve your Strategy, OKRs, and Discovery practices in less than 5 minutes.

Read more from Product Practice Newsletter

Product Practice #361 Connecting North Star Metricsto Business Models READ ON HERBIG.CO PUBLISHED May 2, 2025 READING TIME 4 min & 45 sec Dear Reader, In many organizations, there's still a disconnect between product and business metrics. Product teams focus on customer-centric outcomes while business teams chase financial targets, with neither side fully trusting how one drives the other. When done right, a North Star Metric (NSM) can establish a middle ground that brings together both...

Product Practice #360 Why your Product DiscoveryFeels too Theoretical READ ON HERBIG.CO PUBLISHED Apr 25, 2025 READING TIME 4 min & 17 sec Dear Reader, Over the past two weeks, I've explored treating Product Strategy and OKRs like products to avoid Alibi Progress. Today, let's tackle the practice that often gets dismissed as "good in theory, impossible in practice" — Product Discovery. When teams tell me "we don't have time for proper Discovery," they're usually stuck in Alibi Progress —...

Product Practice #359 Make OKRs Drive Decisions,not Spreadsheets READ ON HERBIG.CO PUBLISHED Apr 18, 2025 READING TIME 5 min & 32 sec Dear Reader, Last week, we explored how treating Product Strategy like a product helps you avoid "Alibi Progress" — prioritizing correctness over value. Today, let's apply this same thinking to OKRs. If you've ever found yourself more relieved that the quarterly OKR-setting theater is over than excited about the OKRs themselves, you've experienced the symptoms...