Role Playbook · 2026

Product Manager

Self-serve product metrics without a SQL queue. Measure launches against certified activation and retention KPIs.

18 min read Runbooks Metadata only Apache 2.0

Executive summary

Use Company Brain for weekly metrics. Trust certified activation and retention. Drill into lineage when something looks off.

Shipping without trusted before/after metrics means guessing if a launch worked. Ask in plain English and get answers tied to certified product KPIs, not week-old exports.

HoursNot weeks for launch readouts
FewerAnalyst interrupts for routine questions
SameKPIs finance uses for revenue narrative
01

What broken lineage costs you

Typical patterns for Product Manager teams. Ranges, not guarantees.

Launch readout due Friday

Jira ticket; stale data by decision time

With Metroflow: Brain query: before/after on certified activation.

Activation metric disputed

Product vs growth different numbers

With Metroflow: Certified spec with traced lineage.

Feature shipped blind

No trusted baseline

With Metroflow: 7-day certified baseline before launch.

Analyst bottleneck

Team waits on data for prioritization

With Metroflow: Self-serve within certified guardrails.

◇

Metadata only. Metroflow crawls schemas, job names, manifests, and dashboard definitions. Your production data rows never leave your network.

02

Your stack, one graph

Metroflow sits above the data path, not inside it. One searchable map for your entire role.

Product events flow: SDK → warehouse → fct_activation → product dashboards. Certified metrics ensure your readout matches what exec sees.

03

Where are you today?

Most teams land at L1 or L2. Target L4 in 90 days.

L1Siloed docsWikis and spreadsheets disconnected from production.
L2Partial lineageSome tool lineage exists. Cross-layer gaps remain.
L3Unified graphOrchestration, warehouse, and BI in one map.
L4Certified metricsKPIs owned, enforced, and traced end-to-end.
L5Proactive opsPre-merge gates. Stale assets caught early.

Quick self-check

  • Answer "what breaks if X fails?" in under 15 minutes?
  • Cross-functional teams share one definition of core KPIs?
  • Incidents include downstream dashboard impact without Slack archaeology?
  • Changes include cross-layer impact checks before merge?
  • Named owners for certified metrics and critical pipelines?

0–2: Start Week 1 connect · 3–4: Certify metrics · 5: Add change gates

04

Choose your path

Every org is different. Pick the track closest to your context.

B2B SaaS product

Activation, time-to-value, feature adoption

Priority: Certify first: activation rate, WAU/MAU

Consumer / mobile

Retention, session depth, funnel conversion

Priority: Certify first: D1/D7 retention, core action rate

Platform / API product

Developer signups, API usage, expansion

Priority: Certify first: active developers, API call volume

05

Who owns what

Assign decision rights up front. Metric fights are governance problems.

RoleOwnsOn Metroflow
Product managerLaunch measurement, prioritizationSelf-serve Brain queries. Certified KPI readouts.
Head of dataMetric certificationApprove activation and retention definitions.
AnalyticsEvent instrumentationEnsure events feed certified models.
Finance / growthAligned narrativeSame activation definitions in board materials.
06

30 · 60 · 90 day rollout

A program with gates, not just a connector checklist.

Days 1–30

Learn the map

  • Brain training for PMs
  • Certified activation published
  • First launch before/after query
Gate: PM runs first self-serve metric query
Days 31–60

Launch discipline

  • Baseline template before every launch
  • Readout on certified metrics only
  • Lineage drill-down playbook
Gate: Last 3 launches measured on certified KPIs
Days 61–90

Scale self-serve

  • PM office hours with data (monthly)
  • 80% routine questions self-serve
  • Shared glossary with finance
Gate: 50% fewer analyst interrupts from PMs
07

Incident runbook

When activation_launch_readout is in trouble. Follow this timeline.

T+0 · Question
Did launch work?

Stakeholders ask if activation improved after redesign.

T+5 min · Query
Company Brain
"Did activation rate change after the onboarding redesign last Tuesday?"
T+15 min · Validate
Check lineage

Confirm certified activation metric, not stale export.

T+30 min · Readout
Share findings

Before/after with cited lineage for leadership.

T+1w · Follow-up
Retention check

D7 retention on same certified definition.

Slack template

[PM] Onboarding launch readout: certified metrics Activation: +2.1pt vs 7-day pre-launch baseline (certified activation rate) Source: product_events → fct_activation → Product Health dashboard Not a pipeline delay: lineage verified Metroflow query: [paste link]
08

Metric certification pack

Copy into your governance doc. One definition. One owner. Full lineage.

Activation rate

Certify first
Formula
% new signups completing core action within 7 days.
Event
signup_complete → core_action_complete
Owner
Product + Growth + Analytics

D7 retention

Certify second
Formula
% of cohort active on day 7 per certified "active" definition.
Owner
Product + Growth
Lineage
product_events → fct_retention → Product dashboard
09

Daily workflows

Four situations you will hit every week.

🚀

Before feature launch

  1. Baseline

    7-day certified metric snapshot.

  2. Verify events

    Schema in event catalog.

  3. Dashboard ready

    Certified KPI wired.

📊

Launch readout (week 1)

  1. Brain query

    Before/after on certified activation.

  2. Lineage check

    Pipeline delay vs real change.

  3. Share readout

    Cited proof for leadership.

🔍

Metric looks wrong

  1. Open spec

    Formula and exclusions.

  2. Trace lineage

    Event → dashboard.

  3. Escalate

    If definition issue, to Head of Data.

📋

Quarterly planning

  1. Certified trends

    Activation, retention, adoption.

  2. Align finance

    Same definitions as board.

  3. Prioritize

    Data-informed roadmap.

10

Copy-paste queries

Company Brain or lineage search. Context included.

Launch
"Did activation rate change after the onboarding redesign last Tuesday?"
Retention
"Show D7 retention for the March cohort on the certified definition."
Funnel
"Where do users drop off between signup and core action?"
Validate
"Is the activation drop a pipeline delay or a real change?"
Alignment
"Does product activation use the same definition as the board deck?"
Feature
"Trace feature adoption for workspaces to the product dashboard tile."
11

Glossary

Plain English. "Why it matters" tells you when to care.

Activation
User completes the core value action.
Why: Your primary launch success metric.
Certified metric
Approved KPI shared across teams.
Why: Your readout matches exec dashboards.
Cohort
Users grouped by signup period or exposure.
Why: Before/after requires consistent cohorts.
Company Brain
Plain-English product metric queries.
Why: No SQL ticket for Friday readouts.
Event catalog
Registered product events and schemas.
Why: Verify instrumentation before launch.
Lineage
Path from event to dashboard tile.
Why: Proves your number is fresh and correct.
12

Outcomes checklist

Measure if the program is working.

Success metric90-day target
Launch readout turnaroundHours vs weeks
Launches measured on certified KPIs100%
Analyst interrupts from PMs50% reduction
PM self-serve queries / month≥ 20 per PM

Ready to put this playbook to work?

Week 1: connect your stack and run your first blast-radius query. Week 4: certify your first KPI. Week 8: operationalize the runbook.

Try the live demo Self-host Talk to us