MWG Advisory · Method

The Loop Audit

A reusable rubric for health and fitness apps. It scores whether a product actually changes the user's state — and whether it holds their attention while doing it.

The core test

Does the product make the user measurably better — and make that improvement legible and worth returning to, at a friction cost the user will keep paying?

01Thesis

Improvement and attention, not one or the other

A retentive loop creates value only when both things are true: the user's state improves — more capability, less pain, better wellbeing — and the loop is engaging and low-friction enough that they keep running it.

Improvement without attention goes unnoticed and unrenewed. Attention without improvement is ineffective.
QUIET GAIN They get better and leave Real but invisible, unclaimed at renewal. Slow measurement, nothing in between. The assessment-led failure. COMPOUNDING LOOP Better, and they can see it Improvement produced, made visible, and converted into the next cycle. The target state. NOT YET A PRODUCT Neither happens No change, no reason to return. ENGAGEMENT THEATER Busy, and no better The mechanics work. The state doesn't move. The meter records showing up. Duolingo draws some criticism here. What most critiques catch. ATTENTION — DO THEY KEEP RUNNING THE LOOP? low high high low IMPROVEMENT — DOES THEIR STATE CHANGE?
Both axes have to be positive. A product can be honest and still fail, by producing change the user never sees.

One correction this forces: dependence on prompts may fall over time, but engagement with the loop should not. A working loop keeps producing new targets and may evolve habits, so the user keeps having a reason to run it. Graduating the user out of the product is not the goal; graduating them out of one objective and into the next one is.

02The loop

The loop, not the layer

Games did not win retention by adding points. They connected a clear objective, appropriately scaled challenge, legible feedback, and a reason to attempt the next cycle. Health and fitness apps often copy the visible layer — streaks, badges, notifications — and leave the loop underneath incomplete.

The Loop Audit tests two things at once: whether the product changes the user's state, and whether it holds attention while doing it. The unit of analysis is not a feature. It is the complete cycle from “what is true?” to “what should I do next?” — and the friction the user pays to run it.

The canonical loop

Diagnose what’s true? Assign what now? Enable can I do it? Verify did it happen? Coach what changed? Progress am I better? Re-enter why return? THE CYCLE ONLY COMPOUNDS IF THE OUTPUT OF ONE STAGE CHANGES THE NEXT DIAGNOSIS ASSIGNMENT VERIFICATION PROGRESS the four stage names used in the published teardowns FRICTION LEDGER — SCORE 0 TO 3 PER STAGE: TIME, EQUIPMENT, ANOTHER PERSON, COGNITIVE LOAD, EMOTIONAL COST. REPORTED BESIDE THE SCORE, NOT INSIDE IT.
The friction ledger runs underneath all of them, because friction suppresses both axes at once and shows up in none of the dimensions on its own.

Seven stages for scoring; four for publishing. Diagnosis maps to Diagnose. Assignment covers Assign and Enable. Verification covers Verify and Coach. Progress covers Progress and Re-enter.

The value compounds only when the output of one stage changes the next. A dashboard that does not alter the prescription is reporting. A plan that ignores performance is content. A streak that rewards opening the app is attendance, not progress.

03Score

Score the loop in eight parts

Rate each dimension from 0 to 5, multiply by its weight, and total to 100. Keep both the weighted score and the raw profile: two products can earn 72 for entirely different reasons.

DimensionWeightThe testFailure mode
Diagnosis10%Which input actually alters the plan?An absent or long intake that produces a generic home screen
Assignment15%Is today's choice obvious, and the reason legible?A library or dashboard posing as a plan
Action enablement10%Can the user start in 30 seconds and finish unaided?High production value, poor fit to time or ability
Verification15%Does the product know the behavior occurred, and how well?Logging activity instead of measuring the target
Coaching & adaptation15%Can the user point to evidence that yesterday changed today?Static tips, generic praise, hidden logic
Progression & mastery15%What can the user do now that they could not before?Streak length as the only durable progress
Re-entry & cadence10%What happens after three missed days?Push frequency substituted for relevance
Trust, agency & safety10%Can users override, export, recover, understand?Incentives that reward anxiety or overtraining

A scoring scale that travels across categories

ScoreMeaningObservable standard
0AbsentThe product does not attempt the job.
1CosmeticA label or generic prompt exists, using no meaningful context.
2FunctionalThe job works, largely through static rules or manual input.
3ContextualThe experience responds to goals, state, or recent behavior.
4AdaptiveThe system changes difficulty, dose, timing or guidance from observed outcomes.
5CompoundingThe loop improves both the user and its own model; progress survives novelty.

Read the score as a system

TotalInterpretationWhat it usually means
85–100Compounding loopEvidence changes action; mastery and trust deepen with use.
70–84Strong but leakyA credible loop with one or two material breaks.
50–69Useful toolDelivers value, but retention relies on user motivation.
30–49Feature stackSeveral jobs exist without causal connection.
0–29Engagement theaterThe visible mechanics exceed the behavior-change value.

Minimum evidence standard

Do not infer adaptation from changing content alone. Require a visible or testable connection between user state or performance and the next prescription. Mark every score O, I or X — observed in use, inferred from behavior or documentation, or not testable in the observation window. Only observed scores get published as firm conclusions.

04Friction

Friction is a tax on both axes

Friction suppresses improvement and attention at the same time, and it hides from the eight dimensions because it isn't a job the product does — it's a cost the user pays. Score it separately: for each stage, rate what the user pays to run it — time, equipment, another person, cognitive load, emotional cost — from 0 (negligible) to 3 (blocks the stage for most users).

Measurement friction deserves particular attention. An objective test that needs a second person, or a ten-minute setup, will risk being run rarely — which caps verification and progression however good the instrument is. A product can hold the best measurement in its category and still show the user nothing, because the measurement is too expensive to repeat.

Report the ledger beside the score. Two products with the same weighted total behave very differently when one costs three minutes a day and the other costs an afternoon.

Three cuts that matter more than the headline score

  • The broken-link test. Any core stage below 2 caps the practical loop. A brilliant diagnosis cannot rescue an absent assignment.
  • The causality test. Can the product explain why an input changed a recommendation? Correlation dashboards are not coaching.
  • The graduation test. After 30 days, has the user gained capability, insight or self-efficacy — or only accumulated usage?
05Metrics

Metrics that match the loop

MetricOperational definitionWhy it matters
ActivationFirst personalized action completedReplaces signup or first open
Loop completionDiagnose → action → evidence → next planSeparates use from value
Adaptive yieldShare of cycles where evidence changes the next actionTests whether personalization is real
Progress velocityChange in outcome per completed cycleConnects retention to efficacy
Recovery rateReturn after lapse without downgrade or churnMeasures humane re-entry
Friction costMedian time and inputs per completed cycleThe tax that suppresses both axes
TrustUse of correction, override, export, explanationSurfaces agency and confidence

Five questions worth carrying into every teardown

  • What does the product know now that it did not know last cycle?
  • What did that knowledge change for the user today?
  • How does it distinguish completion from quality?
  • What compounds after the novelty and the streak anxiety fade?
  • Does the system create capability, or dependence on prompts?

The sharpest closing move

Don't end a teardown with “add more gamification.” End with the missing causal link: use [evidence] to change [assignment], explain [why], and make [progress] visible at [cadence].

MWG Advisory · mwgadvisory.com Good retention is repeated value, made legible

← Back to all research