Snapshots

North star: weekly hand off stores, and nothing is counted yet

Waiting on you
  • North star: stores that hand off at least one pick a week.
  • Five goals sit under it: activation, return, taste, making and trust.
  • No usage analytics exist on cards, jams or shares today.
  • Proposed: our own event table in Postgres, with no third party trackers.
  • Targets wait for four weeks of partner data.
5goals under the north star
Your call

Who builds the decision log, and when? Proposal: engineering, as v1 groundwork.

Product · 2.18

Product metrics

Needs youLast checked Mon Oct 26Owner Param

Answer

The north star is stores that hand off at least one pick a week, with activation, return, taste, making and trust under it; none is counted yet, and targets wait for a baseline.

Today

What exists Can count Source
No usage analytics Nothing on cards, jams or shares docs/handover/product/07-open-questions-and-next-steps.md:36
Visitors log since 23 Oct Which emails open which brand memory brew-access-rules
Sessions and access log table on production Sign ins memory brew-prod-backend
Brief status Briefs sent to our team and their state brief-status.js:8
Source health treg and Apify calls per source memory brew-apify-watch

Tomorrow

Metric Version Tag Definition
North star: weekly hand-off stores v1 New Stores where anyone hands off a pick in a Monday to Sunday week, brand time
Activation v1 New First heart, make and hand-off in the first session
Return v1 New Share of stores that open Today the week after the Monday drop
Taste v1 New Share of picks with a heart or Not for me
Making v1 New Share of hearted picks with a version made
Trust v1 New Share of to confirm facts corrected
Approved posts v2 New Share of hand-offs that become a scheduled post
Measured share v3 New Share of shipped picks with a How it went result
Rules kept v4 New Share of ad runs inside the rules with no undo

Source for all: brand-directions/book/content/b.js b-10 goals.

How we do it

  1. Build the decision log: one event per act, with brand, person, week, pick and area.
  2. Events: read started and finished, heart, Not for me, Later, Make it opened, paid make confirmed, new version, handed off with who, brief status moved, notification sent and opened brand-directions/book/content/j.js j-1 events.
  3. Count demo visits apart; never log what a store's customer does.
  4. These numbers never show in the product.

Numbers

Metric Definition Where measured Status
Weekly hand-off stores As above Decision log Proposed
First win minutes Minutes from paste to first hand-off Decision log Proposed
Funnel steps Pasted, signed in, read finished, first heart, first make, first hand-off, second Monday Decision log Proposed

Open

  1. Is the north star right? Proposal: yes, weekly hand-off stores.
  2. Who builds the decision log, and when? Proposal: engineering, as v1 groundwork before the redesign.
  3. Targets. Proposal: none until four weeks of partner data.
  4. Analytics tool. Proposal: our own event table in Postgres, no third party trackers.
Sources
  • brand-directions/book/content/b.js b-10 north-star, first-win, goals; j.js j-1 what-we-count, onboarding-funnel, events
  • brew origin/main b91e364: docs/handover/product/07-open-questions-and-next-steps.md:35-36, brief-status.js:8
  • brand-directions/BRIEF.md section 3.5
  • memory: brew-access-rules, brew-prod-backend, brew-apify-watch

Source file content/product/product-metrics.md · For agents: Markdown · JSON