main lights

North Star metrics

Which metrics show OmenHall health without vanity husks: safe next step, saved scroll, journal return, and low repeated issues.

North Star exists so the team does not chase click counts that damage trust.

safe_next_step_rate

Share of users who took a calm useful step after a page.

Do not count anxious repeat reading as useful.

saved_scroll_rate

Shows the answer has value after delivery.

Saving must not require unnecessary personal data.

resolved_support_rate

Shows whether issues are solved without repeated user pain.

Do not close tickets for a prettier metric.

healthy_return_rate

Shows returns to journal, inbox, My Day, not repetition of one anxiety.

Filter compulsive loops.

Collect the signal

Define the event, page, source, and moment where the user acted or stopped.

  • The event does not contain a private question or full scroll text.
  • There is a clear timestamp and route.
  • The signal can be tied to an owner decision.

Compare against expectation

Every number must be read beside a hypothesis: what should have happened, what happened, and how much it matters.

  • There is a baseline or first-week manual estimate.
  • No conclusion is made from one random day.
  • Devices are checked separately: mobile and desktop.

Turn into an edit

Analytics becomes useful only after action: rewrite a block, simplify a flow, add FAQ, fix an error, or close an extra door.

  • There is an owner, priority, and expected effect.
  • The change is written into the decision log.
  • A re-check date is assigned after the change.

dashboard

  • Monthly North Star scorecard.
  • Safe next-step rate by content category.
  • Saved scroll and journal return by product.
  • Repeat issue rate after support resolution.

alerts

  • Revenue grows while support and refund problems grow faster.
  • Traffic grows, but safe next-step rate falls.
  • Retention grows mainly through repeated anxiety loops.

decisions

  • Prioritize trust fixes if revenue grows with refund/support noise.
  • Strengthen journal and pause patterns if healthy return drops.
  • Rethink a page if it brings traffic without a safe next step.

red flags

  • The team chooses revenue only and ignores trust damage.
  • A metric rewards dependency on readings.
  • Nobody can explain why each number is collected.

related doors