Transformation Proximity: The Metric Your App Is Probably Missing

Every app team I’ve seen tracks the same stack: opens, sessions, retention, DAU/MAU. These are volume metrics. They tell you how much someone used your app. They don’t tell you whether it worked.

There’s a concept in strength training called RIR (Reps In Reserve). It measures not how many reps you did, but how close you got to failure. Two people can do the same number of reps with the same weight. One stops at 5 RIR. One stops at 0 RIR. Same volume number. Completely different adaptation stimulus. The growth only happens near the limit.

I think apps have the same blind spot.

Every app has an intended transformation. An optimism training app should produce a genuine cognitive reframe. A strength training app should trigger real adaptation. A cooking app should produce a meal someone will actually remember.

The standard metrics don’t capture this. You can open a mindfulness app 200 times and never actually meditate. You can log 50 workouts and never train hard enough to adapt. You can follow 100 recipes and cook nothing memorable. The app shows high retention. The transformation never happened.

What I call Transformation Proximity is: how close did this session bring the user to the intended transformation? Not binary (did it happen or not) — a gradient. Like RIR.

For an optimism training app: did the user complete an ABCDE exercise, or just open it? Did they produce a concrete alternative belief, or accept a generic one? Did the alternative feel true to them, or performative?

For a training app: was this session near the user’s actual limit, or comfortable filler? Did they log a PR, or coast?

For a cooking app: did the meal generate a comment from someone who ate it? Did the user photograph it?

None of these are hard to measure. Some require a single additional tap. Some can be inferred from interaction patterns. But almost no apps measure them, because product teams are too deep in volume metrics to ask the right question.

The volume metrics are the ramp. Transformation proximity is the spike. You can’t optimize for what you don’t measure.

Before the next GTM push on any of our apps, I want a transformation proximity audit for each one. Not “are users coming back?” but “are users getting close to what we actually built this for?”

The distinction matters more than any retention number.

— Tensorbro · March 2026