A North Star metric is useful when it represents value customers actually receive, is influenced by the product and marketing system, and can lead toward sustainable business results. Revenue alone is often too delayed and activity totals such as posts or leads can reward volume without value. The metric tree makes the assumptions visible by connecting the North Star to a small set of inputs teams can change and guardrails they must not damage.
VISUAL LESSON
What you will learn
- 01Distinguish a North Star metric from revenue and activity counts.
- 02Map input metrics and guardrails.
- 03Turn one weak branch into a measurable experiment.

ILLUSTRATIVE SERVICE-BUSINESS TREE
Completed valuable outcomes depend on multiple inputs
METRIC WORKSHOP MAP
Build the tree from customer value backward
Choose a count, rate, or ratio that represents customers successfully receiving the core value within a clear period.
Map reach, activation, frequency, completion, quality, retention, or other controllable factors with exact formulas and owners.
Add margin, complaints, refunds, response time, churn, or capacity so teams cannot improve the North Star by harming the business or customer.
THE METRIC TREE
Customer value above; controllable inputs below
THE LEAD ATLAS METHOD
Lead Atlas Data can research business contacts matched to the locations, categories, and market behind a growth plan, while the North Star tree keeps outreach volume subordinate to qualified customer value.See how custom list research works ↗Start with realized customer value
Describe the moment when the customer receives the core benefit: a completed service, delivered order, active team workflow, resolved case, or another observable success. Choose a time window and unit.
Avoid vanity candidates such as registered users, raw leads, page views, or posts published unless the business model genuinely creates value at that action. Revenue remains an important result and guardrail, but it may not explain what teams should improve this week.
Test the North Star candidate
Ask whether the metric represents value, lies within the combined influence of product and marketing, leads toward durable results, can be defined consistently, and cannot be inflated without real customer benefit.
Compare historical periods or cohorts where possible. If movement has no relationship to retention, referrals, revenue, or customer success, revisit the definition rather than forcing the framework.
Build the input branches
Choose three to five factors that together plausibly drive the North Star. For a service business, these might include qualified demand, response completion, booking conversion, service capacity, and successful delivery rate.
Give every input an exact numerator, denominator, time window, data source, and owner. Inputs should be actionable enough that a team can design an experiment around one branch.
Add guardrails and review cadence
Protect customer trust, margin, capacity, quality, retention, refunds, and complaints. A growth team should not increase completed jobs by overbooking crews or raise activation by removing essential qualification.
Review the tree monthly or when the business model changes. Use a weekly view for inputs, but avoid rewriting the North Star after every short-term fluctuation.
Complete the North Star workshop
Ask leaders from marketing, sales, delivery, finance, and customer success to propose candidates and draw causal input branches. Score each candidate, choose one provisional metric, and identify the weakest evidence link.
Deliverable: one-page metric tree, formulas and owners, three to five inputs, guardrails, data gaps, one branch experiment, and a thirty-day review date.
THE TAKEAWAY
Choose one value-centered outcome, define three to five controllable inputs and guardrails, validate the causal story with data, and use the tree to select experiments.OFFICIAL REFERENCES