AfterAgile™
Lens
Get the PDF

KPIs in Layers

How Thursday reads slow KPIs

MTWThF

Thursday AM – KPI Learnings

Not every KPI moves in a day. So Thursday reads in three layers – this week's fast signals, and the slower KPIs from Intents that shipped two and four weeks ago. Every Thursday, three Intents get a read.

This Thursday, Week 41 – KPI Learnings reads three weeks at once

  1. Layer 1 · Fast signalsWeek 41This weekShipped WednesdayCredit card payments
  2. Layer 2 · BehaviorWeek 392 weeks backShipped WednesdaySaved payment methods
  3. Layer 3 · OutcomesWeek 374 weeks backShipped WednesdayACH bank payments
Layer 1 · This week

Fast Signals

Read the day after it ships. "Was this better?" responses, how many customers use the new flow, errors, and calls to support.

The question – Is it working, and do people like it?

The call – Keep the flag, expand it, or roll back.

Layer 2 · 2 weeks back

Behavior

Read once customers have had time to come back. Completion, repeat use, drop-off, how long the task takes.

The question – Did it change what customers do?

The call – Keep, refine with a new Intent, or retire it.

Layer 3 · 4 weeks back

Outcomes

Read after a full monthly cycle. Retention, churn, revenue, cost to serve, NPS – the numbers Product promised the business.

The question – Did it pay off for the business?

The call – Close the Intent, or bring it back to The Collab.

Each Intent names its layer. The success measure says when it can be read – Layer 1, 2 or 3.

Two and four weeks are a default, not a law. Set the layers to your traffic and your billing or usage cycle.

The Dashboard keeps the layers lined up.