Driving Engagement at Scale

Engagement problems are usually diagnosed as motivation problems and treated with reminders. That is almost always wrong, and reminders make the real cause harder to see.

Read your four counters as a funnel instead. Each step leaks for a different reason and has a different fix.

Received → opened

If this is leaking, it is a delivery problem, not a people problem.

Check, in order:

Channel. Is the action arriving where the person actually works? An email to an address they read twice a week is a delivery failure dressed as disengagement.
Timing. An action that lands at 07:00 is read on a phone and forgotten by the time anyone is at a desk. Land it near the moment it is meant to be performed.
Calendar. If your holidays and closure days are not loaded, actions land on days nobody is working. Those show as missed, and they are yours, not theirs.
Volume. If people are also getting three other organizational nudges that week, yours loses. This is worth checking with whoever owns internal comms.

Opened → answered

If this is leaking, the action is wrong — too big, too vague, or not their job.

The most reliable fix is to shrink it. An action that needs a clear half-hour will only be done by people who had a clear half-hour, which is a survey of workload, not of development.

Then check relevance. Read ten of your MDAs as if you held the participants’ job. If any of them would make you think this isn’t what my week looks like, the Development Tasks behind them are too generic — that is where to fix it, not in the reminder copy.

Finally, check the first three actions specifically. Early drop-out is usually an onboarding problem: the first action set the expectation that this is going to be effortful.

Answered → assessed

If this is leaking, it is you, and it is the one that kills programs.

People stop answering when nobody answers back. Not immediately — the drop shows up two or three weeks after mentors fall behind, which is late enough that it usually gets blamed on the participants.

This step is a capacity question, and it has capacity answers:

Count mentor hours before participants. A mentor who can review fifteen responses a week can hold a caseload that produces fifteen responses a week. Enrolling forty people does not change that; it just moves where the failure appears.
Watch the assessed counter weekly. It is the earliest available warning, and it moves before the answered rate does.
Keep replies short and specific. A two-line reply that names one thing beats a paragraph, and it is the difference between a sustainable caseload and an unsustainable one.

Things that look like fixes and are not

More reminders. They raise opened slightly, lower answered over time, and train people to ignore the channel. A second nudge for a genuinely missed action is fine; a drip campaign is not.

Leaderboards and streaks. They produce a burst from the people who were already engaged and quiet withdrawal from everyone else — and a streak that breaks after a legitimate absence actively punishes honesty about leave.

Manager escalation. Reliable at producing compliance activity and nothing else. Real answers become defensive answers, and you lose the evidence the program exists to gather.

Extending the program. If people are not engaging in week four, week ten will not help.

What actually holds the curve

The action fits an existing moment in the week.
The minimum version takes two minutes.
A person replies to what comes back, within a few days.
A missed week costs one action, not the program.
Nobody is punished for registering absence.

None of these are motivational. They are design and staffing decisions, and they are the ones that separate a program that is still running in month three from one that is being quietly wound down.