1. Frame the north star in human terms
Start the workshop by restating the north star metric as a customer outcome, not a KPI. For example, "weekly activated teams" becomes "teams who completed setup and ran their first workflow." This keeps the conversation anchored on behavior.
Write the statement on a whiteboard or shared doc. Everyone should agree on the language before moving forward. I have facilitated sessions where the product team defined the north star as "activated accounts" and the marketing team had been measuring it as "paid conversions" for six months — the workshop surfaced that gap in the first fifteen minutes, which is exactly when you want to find it.
2. Map leading indicators
Ask each function to list the behaviors that lead to the north star. Product might call out activation steps, marketing might call out qualified signups, and customer success might call out onboarding milestones.
Cluster the behaviors into 3 to 5 leading indicators that can be measured weekly. These become your shared measurement language.
3. Identify data sources and owners
For each indicator, confirm where the data lives and who owns it. If the source is unreliable, flag it as a risk. You cannot map a metric you cannot measure.
Create a simple ownership table with columns for indicator, owner, data source, and refresh cadence.
4. Translate indicators into experiment themes
Once leading indicators are clear, ask teams to propose experiments that could move them. Group these into themes (onboarding, activation, retention). Each theme should have at least one experiment ready to scope.
Capture the ideas in the experiment backlog immediately. The workshop should end with a prioritized list, not just notes. My take: the backlog entries you write in the last twenty minutes of this session tend to be sharper than anything produced in a solo ideation session — the collective context refines the hypothesis instinctively.
5. Document decisions and next steps
Summarize the outcomes in a one-page recap: the north star definition, indicators, owners, and top experiment themes. Share it within 24 hours while the context is fresh.
Schedule a follow-up check-in 4 to 6 weeks later to review how the indicators shifted and whether new experiments are needed.
Keep the workshop lightweight
A mapping workshop should feel energizing, not exhausting. Limit it to 90 minutes, bring only decision makers, and focus on clarity over perfection. The best map is the one teams actually use. One limitation worth flagging: this session only works if the data owners attend. I have run versions where someone filled in for the data lead and the ownership table came out with gaps that were not resolved for weeks afterward.