/
/
/
Progress

Progress

Red, amber, green. While there is still time to do something.

Define the steps a member should pass through and the pace they should pass through them, and Progress flags anyone falling behind. This is the GPS system, and it is the part of RPM that changes outcomes rather than describing them.

The intelligence loop

Unify

Data leaves its silos

>

Summarize

The shape becomes visible

>

Investigate

You drill into the detail

>

Intervene

Someone acts in time

Revenue is a lagging indicator

By the time churn appears in your numbers, the decision was made months earlier. The member went quiet in week four, drifted through weeks five to twelve, and cancelled in week fourteen citing not using it. Everything useful happened in week four, and nothing in your stack was watching. Progress watches week four. It compares where a member should be against where they are, and it says so while a coach message still changes the outcome.

Available now as custom development.

Gamplify RPM is implemented by our team for partner platforms today. A self-managed plugin with dashboard builders, shortcode generators, and configuration panels is actively being built.

How the GPS works

Everything available to you.

You define the journey once. It runs against every member continuously.

Any sequence

What can be tracked

What turns green into amber

Defining pace

What each means

The three states

Routing the flag

Who gets told

Who sees what

Views

Worked example

Cohort 12, onboarding, day nine

Fifty-three members. The dashboard sorts them into three groups and tells three different people about it.

GPS: Cohort 12 onboarding

Six steps, expected pace 2 days each

unify

Fifty-three members, six steps, one view

Pulled from LMS, events, and gamification data at once.

Green

41 on or ahead of pace

No action taken. The most common mistake in this whole system is intervening on people who are fine.

Amber

9 slipping, no activity for six days

Still inside the journey, just slowing. This is the group where a message actually changes the outcome.

Red

3 stalled at step two since day three

Coach notified by name, with the specific step each one is stuck on.

act

Amber gets a nudge, red gets a human

The nudge fires from a Flow with no guilt language and one next step. Red goes to a person, because automation has already failed there.

Recipes

Three you could build this afternoon.

Read them as when, only if, then. That is the whole grammar of the system.

Catch the fade at week four

When

A member goes six days without activity

Only if

They are past their first month and were previously active

Then

Move to amber, notify their coach, and send a low pressure nudge naming one specific next step

Escalate a genuine stall

When

A member has not moved a step

Only if

Twice the expected pace has elapsed

Then

Move to red and route to a human. At this point automation has already failed

Stay quiet on the new ones

When

A first-week member misses two days

Only if

They are inside their first month

Then

Do nothing. Telling a beginner they are behind is the fastest way to make them stop

Before you build

Three things worth knowing.

Note

Amber needs an owner. An early warning nobody is responsible for acting on is a color on a screen.

Note

Set pace from what your good members actually do, not from what you wish they did. An aspirational pace turns everyone amber and the signal becomes noise.

Note

Be careful telling members their own state. Green is motivating, amber can be, and red almost never is.

The rest of rpm

Progress is one of 3 parts.

Reports

Gamplify RPM

Progress

You are here

Metrics

Gamplify RPM

Put Progress to work.

Tell us what you are trying to get members to do, and we will show you the Flow that does it.

Scroll to Top