Use this whenYou need people to keep up with something administrative, like timesheets, data entry, or ticket updates, and reminders aren’t working.
Why it exists
Administrative work is where adoption quietly dies. Nobody objects to filling in the new form. They just don’t, or not on time. Reminders become noise, and managers chase the same people every week. Visibility changes that. When adherence is measured objectively and shown to everyone, most people fix it themselves.
The framework
- Step 1Define it objectivelyCan a system tell who is compliant?
- Step 2Show the leaderboardAre the people doing it right being recognized?
- Step 3Show the gaps neutrallyCan people see who isn’t, without blame?
- Step 4Follow up privatelyWhat happens with repeat cases?
Define it objectively
Can a system tell who is compliant?
The rule has to be clear and checkable without judgment, like submitted by Friday at five, or every ticket updated within two days. If it needs interpretation, it doesn’t belong on a list.
Show the leaderboard
Are the people doing it right being recognized?
Publicly and often, recognize the people and teams who keep adhering. Lead with this. It sets the norm and rewards the majority who are already doing the right thing.
Show the gaps neutrally
Can people see who isn’t, without blame?
Share who is behind, lightly and smartly. Plain numbers, no commentary, often by team. Objective, neutral reporting does the work. Most people catch up as soon as they see their name.
Follow up privately
What happens with repeat cases?
For people who stay on the list, a manager follows up one to one. Public visibility gets most people there. The rest is a conversation, not a bigger spotlight.
How to use it
- Write the rule so a system can check it without judgment.
- Automate the report. It should come from the data, not from someone compiling it by hand.
- Publish the leaderboard on a regular rhythm, and lead with recognition.
- Include the gaps in the same report, in plain neutral language.
- Have managers follow up privately with anyone who stays behind for more than a couple of cycles.
- Retire the report, or make it less frequent, once adherence is steady.
Keep it light and smart
- Recognition first, gaps second, every time.
- Report facts, not opinions. Late is late, without adjectives.
- Show teams before individuals when you can.
- Make sure the data is right before you publish. One wrong name destroys trust in the list.
What it looks like
Picture a project organization where timesheets are always late. Every Monday a short automated post goes to the team channel. It names the teams at one hundred percent, thanks the three people with the longest on-time streaks, and lists, without comment, the people still missing last week. Within a month the list is short. The few who remain get a quiet conversation with their manager.
Where it breaks down
This only works for clear, objective rules. Used on anything that needs judgment, it feels like surveillance. Done heavily, it turns into shaming and damages trust. Check the culture first. In some places team-level reporting is as far as it should go. And the data has to be right, every time.
Try it with AI
Help me set up a leaderboard and a gaps report for an administrative task people keep falling behind on. Ask me one question at a time about the task, the rule, what a system can measure, and the culture of the team. Then help me write the rule so it can be checked objectively, draft a weekly report that leads with recognition and lists gaps in neutral language, and plan how managers follow up privately. Warn me if anything would come across as shaming.