Team challenges at work that people actually join (without surveillance)

Why mandated programs feel like monitoring

When a challenge is announced from the top, tracked automatically and displayed on a company-wide board, it stops feeling like an invitation. It starts to feel like another metric. People wonder who can see their numbers, whether skipping will be noticed and what happens to the data later.

Step tracking makes this sharper. It measures something deeply personal: how your body moves, when you sleep, whether you had a slow week. Some people love that. Many others have injuries, caring duties, long commutes or simply a different idea of what being well means. A single step count turns all of that into one ranking, and the people at the bottom feel exposed.

• Participation that is "optional" but tracked by HR rarely feels optional.
• One shared goal excludes anyone whose life does not fit it.
• Public rankings reward the people who were already doing it.
• Passive data collection feels like being watched, not supported.

Make it voluntary, and let people choose the goal

The fix is not a cleverer app. It is a different contract. A good team challenge is something people opt into because it looks fun or useful, and leaving it costs nothing. No reminders from a manager, no notes in a review, no awkward questions.

It also helps to widen what counts as a goal. Movement is one option. So is reading for twenty minutes, taking a real lunch break away from the screen, practising a language, drinking water, writing a line in a journal or going to bed before midnight. When the goal fits the person, the challenge becomes about consistency and support, not about who is fittest.

You can run a single shared theme with flexible tasks ("do one small thing for yourself each workday") or a few parallel challenges people pick from. Either way, the person decides what showing up looks like for them.

Privacy by default, not as an afterthought

People join more freely when they know exactly who sees what. Spell it out before launch. Check-ins are visible to the people in the challenge. Anything beyond that, such as a public profile, should be the person’s own explicit choice, never a default.

If your challenge uses proof, like a photo of a book page or a walk, treat it carefully. Proof should be seen only by the person, whoever verifies it and the admins who run the challenge. It should never be broadcast to the whole team. Many challenges do not need proof at all; trust is often enough, and asking for evidence of a lunch break sends a strange signal.

• Say who can see check-ins and proof, in plain words.
• Never connect challenge activity to performance reviews.
• Keep anything public opt-in, per person.
• Let people leave without explanation.

Start small as a team lead

You do not need a company-wide launch. A team lead with five interested people can run something better than a program built for five hundred. Small groups know each other, notice when someone is missing and cheer in a way that feels genuine.

1. Mention the idea casually in a team meeting and ask who would be interested. Do not chase anyone.
2. Agree on a short length, such as two or four weeks, and a loose theme.
3. Let each person set their own task and frequency, including rest days.
4. Join yourself, with a modest goal, and be honest when you miss a day.
5. Share one short encouraging note a week, not a status report.
6. At the end, ask what people want next, if anything.

Your role is host, not supervisor. If you treat missed days as normal and celebrate small streaks, the group will follow your lead.

Check in where people already work

One reason workplace challenges fade is friction. Another app, another login, another notification. If your team lives in Slack or Microsoft Teams, a check-in there feels like part of the day rather than an extra chore.

Keep the channel light. A quick tap to mark a task done, an occasional photo someone chose to share, a cheer when a colleague hits a week. Avoid daily roll calls or posts that list who has not checked in. The aim is a warm background hum, not a scoreboard in everyone’s face.

Design goals that include everyone

Inclusive design is mostly about removing assumptions. Do not assume everyone can walk ten thousand steps, has a quiet evening or wants to talk about their body. Offer goals that work for parents, night owls, people with chronic conditions and people who just want a calmer week.

• Offer a minimum version of every task, like five minutes instead of thirty.
• Rank by consistency, not totals, if you rank at all.
• Plan rest days in advance so a weekend away is not a failure.
• Make joining late completely normal.
• Avoid weight, calories or body measurements as goals.

Where MyGritWall fits

MyGritWall was built around these ideas. Organizations are private by default, and anything public is a person’s explicit choice. People can check in from Slack or Microsoft Teams. Proof, when it is used, stays private to the person, their verifier and admins. The leaderboard ranks by completion rate since each person joined, so joining late is never a penalty and nobody is shown at the bottom. Rest days can be planned ahead and do not count against anyone.

There is a free team trial for up to 15 members for 30 days, with no payment details, which is enough to test the small-group approach before deciding anything bigger.