A lightning lesson, the follow-on to the hosts' question-framing lesson, presented by one of the co-hosts. It argues that a team should measure a single "true north" metric that captures delivered customer value, then break it into input metrics that individual teams can move. The lesson ends on a method: a seven-test checklist for the true north and a four-bucket decomposition (breadth, depth, efficiency, frequency) for the inputs, with AI cast as a coach for applying them. The planned AI demo of that coaching was skipped for time.
Why metrics mislead. Teams track too many metrics, or the wrong ones. The presenter's example is daily active users rising 30%, a team building on the trend, and the discovery three months later that the rise was bot traffic. The framework, which the presenter says Airbnb, Slack and Netflix use, separates the true north (the outcome) from inputs (the levers). Asked how "north" to go, the presenter says as close to value as can be measured, stepping south when it cannot. Shane adds: picture what the person is trying to accomplish with the product imagined away, and if no signal exists, work with engineering to build one.
Good and bad true norths. Daily active users, revenue and signups are offered as plausible but bad choices, because they are company-oriented or show only attendance. Airbnb's nights booked, Slack's messages sent and Netflix's hours watched are good choices: behavioral, leading indicators of revenue, and direct signals of value. Nights booked captures both sides of the marketplace. Netflix is said to have moved from subscribers added, a vanity metric, to hours watched. The seven tests are strategic (customer value, business outcome, hard to game, one number to rally around) and practical (actionable, understandable, measurable). For B2B, Shane describes his own legal-tech product's true north: the time saved between a contract arriving and leaving, with guardrails on edit quality.
Inputs. For a growth team owning retained signups, the true north breaks into traffic, signup conversion and retention, each owned by a different team. The presenter concedes that most metrics do not decompose this neatly and some faith or proxies are needed. Shane notes that the true north is what exposes a gameable input. Inputs fall into four buckets: breadth (active listings), depth (average booking value), efficiency (search-to-booking conversion) and frequency (repeat behavior).
Exercises. A project-management PM's "grow monthly active users" fails as vanity. The improved true north is team projects completed per week, with one input per bucket. In a food-delivery poll, orders delivered per month wins. Delivery success rate is rejected as a ratio that stays flat while volume doubles, average order value as a depth input, and weekly active customers because showing up is not value. Total order value delivered is ruled out because it can only go up.
Q&A. There is no rule for how many metrics to keep, but six or seven seems fine, and the advice is to prioritize by leverage and cap meetings rather than metrics. Time windows should follow product cadence: daily for a feed, weekly for project tools, monthly for tax tools, longer for a dental practice. New metrics churn for the first one to three months. Zero-to-one teams should instrument a value signal early. Shane treats "aha" moments as milestones on an input, found by regressing that input against the true north to see where gains accelerate.
The AI analyst. The hosts show decks they say their Claude Code AI analyst produced without hand-written code or slides: a co-host's real estate business, Hawaii tourism data, and an interactive campsite deck with presenter notes. They credit Claude Opus 4.6 with making this possible. Shane describes the repo as about 60,000 lines with about 20 specialist agents. In an overnight test, a single markdown "seed" had Claude Code rebuild a data team for a new use case. Asked about careers, he hedges that analysts may become builders of agent systems or technical PMs.