Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.
Core engagement loop map on one page
This is a team plan, best installed into a shared workspace so everyone with a role in it can see and own their tasks. Most consumer apps run on two or three loops, such as post, get a reaction, post again, or practise, see progress, practise again, yet few teams have ever drawn theirs.
First tasks
- List every repeated action a returning user takes in a normal week
- Group those actions into no more than three core loops
- Draw each loop with its trigger, action, reward and investment step
- Mark the step where each loop loses the most people
- Redraw the loop map after the year's biggest release @recurring(yearly)
Engagement metric definitions for each loop
Daily active users tells you people opened the app, not that the loop worked. Defining, for each core loop, a completion rate, a frequency measure such as days active out of the last seven, and one quality signal stops the team celebrating opens while the real cycle stalls. Write these down before anyone sets a target.
First tasks
- Write what counts as a completed cycle for each core loop
- Choose a days-active-out-of-seven or out-of-twenty-eight measure per loop
- Pick one quality signal per loop that rewards value, not minutes
- Publish the definitions and name an owner for each
Loop step event tracking check
A loop cannot be measured if the trigger shown, the action taken and the reward delivered are not logged as separate events, and many apps only log the action. Checking each step of each core loop against the event data, and filing tickets for the gaps, is a short job that makes every later analysis possible. Do it before building the baseline.
First tasks
- Export the current event list from your analytics tool
- Match each loop step on the map to an event name
- File tickets for any trigger, action or reward that is not logged
- Run a test account through each loop and watch the events arrive
- Spot-check that loop events still fire after recent releases @recurring(quarterly)