A LinkedIn posting challenge for employees that outlives its prize
Most challenges end the week the prize goes out. The ones that last reward the week held, not the post that travelled.
The challenge launched on a Monday with a prize, a Slack channel and thirty days of posting. The first week the channel was full of screenshots. By the third week it held two people, a reminder from the organiser and a link to somebody's viral post that nobody could explain. The prize went out on day thirty, and so did the posting.
A LinkedIn posting challenge for employees can work. It works when it rewards the week held rather than the post that travelled, counts without asking anyone to report, and is designed from the first day to turn into a standing cadence. This page is for whoever is about to launch one.
TL;DR
| Choice | Holds | Collapses |
|---|---|---|
| Unit | Posts published per week | Likes, views or followers |
| Length | Six to eight weeks, then a cadence | Thirty days of daily posts |
| Streak | Counted in weeks | Counted in days |
| Reward | A draw among weeks held | A prize for the best post |
| Counting | Read from public profiles | A check-in thread or a form |
| Comparison | Each person against their own goal | Everyone against the top poster |
What a posting challenge is actually for
A challenge is not a strategy. It is a starting motor. Its job is to get several people through the part of a new habit where nothing is automatic yet, with a little public pressure and a reason to start this week rather than next quarter.
That framing matters because it sets the success criterion. A challenge succeeds if, a month after it ends, the same people are still publishing at a rhythm they chose. It does not succeed because one post reached two hundred thousand people in week two.
Judge the challenge on week ten, not on week two. Week two measures excitement. Week ten measures whether you built anything.
One public example, and what it actually rewards
In September 2026 Fortune described Warp, an employee management startup, paying its employees to post on LinkedIn and X. The mechanism is a monthly raffle. Every post is one entry, and three winners each receive a couple of hundred dollars. The company also runs weekly brainstorming sessions and offers AI drafts that employees are encouraged to rewrite in their own voice.
The company reported that about a third of its employees post at least twice a week, and linked the programme to hiring: thirty people hired in a quarter, most of whom said they had first seen the company on LinkedIn. Treat those as the company's own figures rather than a benchmark, but the design is worth reading closely.
Notice what the raffle rewards. It pays for publishing, not for reach. A post that reached forty people is worth exactly one entry, the same as a post that travelled. That is the single decision most internal challenges get wrong, and it is why this one keeps a third of a company posting instead of three people chasing a viral hit.
Why thirty day challenges break in week two
The classic format asks for a post a day for thirty days. It is easy to announce and almost impossible to hold, because it is sized for the most enthusiastic day of the month rather than an ordinary one. The first missed day resets the count, and a reset streak is a reason to stop.
The habit research points the other way. In the field study usually quoted for the 66 day figure, the time people needed to make a behaviour automatic ranged from 18 to 254 days, and missing a single opportunity did not meaningfully set anyone back. A format that treats one missed day as failure is stricter than the evidence it borrows.
Count weeks instead. If the goal is two posts a week, the streak counts weeks where both happened, and a quiet Tuesday inside a good week costs nothing. The full reasoning is in content posting streak.
Six rules for a challenge that holds
- Let each person choose the number. One post a week is a legitimate goal. A goal set for the worst week of the month survives the month.
- Count posts, never reach. Reach depends on the network, the topic and luck. Publishing depends on the person, which is the only thing a challenge can change.
- Streaks in weeks. A streak that dies over one busy day teaches people that the challenge is not for them.
- Compare each person to their own goal. A leaderboard of raw post counts rewards whoever has the most free time.
- Keep it voluntary. Five people who want to do it produce better posts and an honest denominator.
- Decide the ending before the start. Announce on day one what happens after the last week, so the finish line is a handover rather than a cliff.
Sizing the number is the rule people argue about longest. The short version is to pick the number for the worst week, freeze it for two periods, and raise it only after it was held. The long version is in posting cadence for teams.
Rewards that do not wreck the feed
Money works, as the raffle shows, but the shape of the reward matters more than its size. A prize for the best post turns colleagues into competitors for the same attention, and the feed fills with engagement bait. A prize for the most posts turns into volume for its own sake.
| Reward | What it teaches |
|---|---|
| A draw among everyone who held their week | Consistency, at the size each person chose |
| A team treat when every goal is hit | That the last person's week matters |
| Visible thanks from leadership | That this counts as work |
| A prize for the best performing post | Chase reach, whatever it costs |
| A prize for the most posts | Post more, whatever it says |
The strongest reward is not on the table at all. It is the reason each person has for publishing in the first place, which is their own reputation in their field. A challenge that says so out loud needs smaller prizes. How to have that conversation is in how to get employees to post on LinkedIn.
Count it without asking anyone
Most challenges are counted with a check-in thread: post a screenshot, get a reaction, the organiser tallies on Friday. It works for a week. Then the busy people stop checking in, the tally goes wrong, and the organiser spends the challenge chasing screenshots instead of encouraging anyone.
Everything a challenge needs to count is already public. A post on a personal profile shows up on that profile, dated, for anybody to see. Reading those profiles once a day gives the organiser a record nobody has to maintain, and it removes the most awkward conversation in any programme: asking a colleague whether they really posted.
Tell the participants what is counted and what is not. Published posts, yes. Private analytics, messages and drafts, never. Announced on day one, this reads as removing a chore. Discovered in week three, it reads as surveillance. The measurement side of this is covered in how to measure employee advocacy.
What happens on day forty
The end of the challenge is the moment most programmes lose everything they built. The prize goes out, the channel goes quiet and nobody decided what the rhythm is now. Plan the handover before the start.
- Keep the goals. Each person keeps the weekly number they held, with no prize attached.
- Keep the board. The same view the challenge used, so being behind stays visible.
- Keep a short review. Fifteen minutes a week, one number per person, no preparation.
- Run the next challenge as a season. A new six week season with a small draw restarts attention without resetting anyone's history.
A team that does this does not need a bigger prize next time. It needs a reason to keep going, and a record of the weeks it already held is a surprisingly strong one.
How Groowth handles this
Groowth counts the challenge for you. Paste the public LinkedIn profiles of the people taking part, set the weekly goal each person chose, and it reads those profiles once a day. Each goal is a lane that fills as posts are detected, streaks count weeks rather than days, and a crew banner counts the finish lines the whole team has crossed.
Nobody installs anything or checks in, and it never reads reach or impressions, so the only number on the board is the one a challenge should reward. When the challenge ends, the board simply keeps running as the standing cadence. Three accounts are free with no card, and the same works on Instagram, TikTok and YouTube. A setup without any app at all is described in employee advocacy without an app.
Frequently asked questions
What is a LinkedIn posting challenge for employees?
A time-boxed programme, usually six to eight weeks, in which employees agree to publish on LinkedIn at a rhythm they choose, with a light reward and a shared view of who is keeping it. It works as a starting motor for a habit, not as a strategy on its own.
How long should a posting challenge last?
Six to eight weeks, counted in weeks rather than days, and followed by a standing cadence decided before the start. Thirty days of daily posting is the most common format and the one that breaks fastest, because the first missed day resets it.
Should a posting challenge reward the best post?
No. A prize for the best performing post rewards luck and pushes colleagues to compete for the same attention. Reward the weeks held instead, for example with a draw among everyone who met their own goal, so the number people chase is the one they control.