How to get employees to post on LinkedIn and keep them posting

The kickoff went well. Twelve people, a shared document, three posts a week each, everybody nodded. Four weeks later two are posting, one of them is the person who called the meeting, and the shared document was last opened on the day it was created. Nothing went wrong. The programme asked twelve people for something none of them had a personal reason to do.

This is how to get employees to post on LinkedIn and still have them posting in month six. It is mostly not a tooling problem, and the parts that are come last.

TL;DR

Step one: give the individual a reason that is theirs

Nobody publishes to raise company reach. They publish because it is good for their own standing, their own network and their own next job, and a programme that cannot say that out loud is asking for a favour while calling it a strategy.

Saying it plainly costs nothing and changes the framing entirely. The company benefits as a side effect of something that was already worth doing for the person, which is a much sturdier arrangement than goodwill.

1. Say what they get. A visible reputation in their field, which follows them.
2. Say what the company gets. Buyers follow people rather than brands. Be specific rather than grand.
3. Make it voluntary and mean it. A reluctant participant produces content that damages the programme's credibility.
4. Never tie it to performance review. The fastest way to get twelve identical, lifeless posts.

Four people who want to do this beat twenty who were asked to, and the measurement is honest because the denominator means something.

Step two: pick a number for the worst week

Three posts a week per person is the number that gets agreed in kickoffs and it is almost always the reason the programme is dead by week six. It is set for the enthusiastic week rather than the ordinary one.

One a week, held for two quarters, produces more posts than three a week held for five weeks, and it produces something more valuable than volume: a habit nobody is behind on. Raising a number that was held is easy. Recovering from a number that was missed for a month is not.

The full reasoning on sizing it is in posting cadence for teams.

Step three: leadership goes first, visibly

A programme where the founder or the department head does not publish is a request. One where they do is a norm, and the difference in adoption is larger than any feature of any platform.

It also has to be visible in the same feed, not in a status update about the programme. Employees are not persuaded by somebody talking about posting. They are persuaded by seeing that person post something slightly uncomfortable and survive it.

Step four: remove the blank page, not the writing

The blocker is almost never time. It is opening the app with nothing prepared, staring for five minutes and closing it. A running list of raw material fixes that and a content library does not, because a library gives people somebody else's words.

• An observation from this week's work. No conclusion required. Two sentences is a post.
• A question they are stuck on. Fast to write, because they were already thinking about it.
• A number from their own work. The most reliable format there is in B2B.
• A belief they have changed. Always available, always specific, and impossible to write generically.

Decide the format of a minimum post once, as a team, so that a busy week has a fallback that is not silence. That single decision does more than a quarter of encouragement.

Step five: a short review that nobody has to prepare

Fifteen minutes, same day every week, one number per person: posts published against posts agreed. Nothing else on the screen.

1. No self reporting. If somebody has to fill in a form, the data will be missing in the week it matters most.
2. Name the misses without drama. The point is a nudge, not a performance review, and the tone decides whether it survives.
3. Celebrate the streak rather than the best post. Consistency is the thing you are actually trying to build.
4. Same time, recurring. A review that gets rescheduled twice has ended.

Tell the team you are counting, and say what is not counted: no private analytics, no messages, no drafts. Framed as removing the Friday chase this is usually welcomed. Discovered rather than announced, it reads as surveillance and the programme never recovers.

Step six: tooling, and only now

Everything above is free. Buying software before the first three steps are done purchases an accurate measurement of a problem you already have.

When it does become worth it, the useful thing is not a library. It is something that fills the published column by reading the profiles, so the weekly review takes two minutes and the record does not depend on the people being measured. How to measure the result honestly is in how to measure employee advocacy.

Who to invite, and who to leave alone

The instinct is to enrol everybody. It produces a large participation number for one quarter and a dead programme by the next, because most people have nothing they want to say in public and should not be made to.

• Founders and department heads. Almost always worth it. The audience wants the person who decided things.
• Sales. Worth it when they write about what they hear from buyers, not when they post product cards.
• Engineering and product. The highest signal content in B2B and the hardest to schedule. Invite, never require.
• Everybody else. Leave them out, and say so warmly. An open door beats a rota.

A smaller group also makes the measurement honest, because the denominator is a named set of people who agreed rather than a headcount.

Four things that kill a programme quietly

None of these announces itself. All four are visible in the weekly review if somebody is looking for them.

The second row is the most common and the most damaging. The reason a personal profile works is that a person is on the other end of it, and a marketing edit removes exactly the thing that made it worth reading. Correct facts, never voice.

One last thing worth planning for: results arrive late. A post read in March produces a conversation in September, and no attribution model will connect them for you. That lag is exactly why the programme needs a cadence number to steer by, because it is the only signal available in the months before anything shows up, and a programme judged on results alone gets cancelled before its results exist.

One more framing that helps at the start. A programme like this is not a campaign with an end date, it is a habit several people are being asked to build at once, and habits are built by lowering the bar rather than by raising the stakes. The reasoning, and what it compounds into over two quarters, is in social media posting consistency.

How Groowth handles this

It does step five and nothing else. Paste the public profile links of the people in the programme, set the number each agreed to, and it reads those profiles daily and shows who published and who did not, with streaks, on one board.

Nobody installs anything, nobody opts in and nobody fills in a form, which is the property that matters in the weeks when everyone is busy. It does not write, suggest or schedule posts, because the reason a personal profile works is that a person is on the other end of it. Three accounts free with no card.

Frequently asked questions