Plan Your Program Launch

Launch is the single biggest predictor of whether a program takes hold. The first three days create the social proof that makes everything afterwards easier, and a quiet launch is very hard to recover from. This article covers what to have ready, what has to happen on day one, and the rhythm for the first four weeks.

Get these ready before you launch

Work backwards from your launch date. Most of this needs one to four weeks of lead time, and the IT items need the most.

1. A named executive sponsor who has committed to a specific action on day one. This is the item most often left until last and it matters most. See Set Up Executive Sponsorship.
2. Ten or more pieces of content in every group, so nobody arrives at an empty feed.
3. Groups and assignments configured, so people see relevant content without hunting for it. See Plan Your Content Group Strategy.
4. Sign-in confirmed working, whether that is single sign-on, provisioning, or a plain invitation.
5. Email domains allowlisted with your IT team, or your invitations will land in spam. See Allowlisting Steps for IT Departments.
6. Slack or Microsoft Teams connected, so announcements can land where people already are. See Integration for Slack and Microsoft Teams Integration.
7. Your launch email and internal announcement drafted and scheduled.
8. A support contact identified for day-one sign-in problems.

Do these on launch day

Six things, and the first one is not optional.

1. Your executive sponsor shares or posts from the platform. This is the social proof moment. Employees take their cue from whether leadership actually showed up.
2. The launch email goes to everyone, with one clear action and a link.
3. The internal announcement goes live on the intranet or wherever company news lives, reinforcing why the program exists.
4. The Slack or Teams announcement fires, short, with a link.
5. Your best content is marked as important, so it triggers notifications rather than sitting in a feed.
6. The first content email goes out to everyone who has registered. See Create Content Emails.

Then celebrate the first sharers publicly the same day. Naming three people in a Slack channel on day one does more for adoption than any amount of training.

Run the first four weeks deliberately

The most common launch mistake is treating it like a product release: announce once, then move on. Adoption comes from repetition.

• Week one. Announcements land, the sponsor posts, the first content email goes out, and you publicly celebrate early sharers by name.
• Week two. Refresh the content, remind people in channel, and get a second leader to post. Highlight your top early adopters where colleagues will see it.
• Week three. Share early results internally. Real numbers create urgency. Announce any department-specific content tracks.
• Week four. Hold informal office hours, follow up individually with leaders who have not shared yet, and close out whatever campaign you launched with, announcing winners publicly.

Keep the content email weekly throughout. Consistency is the whole mechanism.

Judge the launch against realistic benchmarks

Activation rates vary enormously by company size, because a 400-person company and a 40,000-person company are not doing the same thing.

• Activation at 30 days. Roughly 20 to 35 percent for small and mid-sized organizations. Roughly 7 to 12 percent at enterprise scale.
• Content per group per week. Three to five pieces for smaller programs, five to ten at enterprise scale.
• Shares per active user per month. Four to five for smaller programs, two to three at enterprise scale.
• Executive activation. At least one or two leaders genuinely active on day one.

Track these from the start rather than reconstructing them later. See Measure Program Health.

Consider a soft launch at enterprise scale

For large or regulated organizations, a pilot with a friendly group of 50 to 200 people before the full rollout is usually worth the extra weeks. It surfaces sign-in problems, tells you whether your group structure makes sense to people who did not build it, and produces the internal examples that make the full launch credible.

FAQ

How long does a launch take to prepare?

Two to four weeks of preparation is typical once the platform is configured, and the constraint is usually IT lead time and getting executive commitment, not the platform work.

What is a good activation rate?

It depends on size. See the benchmarks above. An enterprise program at 10 percent in the first month is doing well; a 300-person company at 10 percent is not.

Do we have to run a campaign at launch?

No, but it helps, and a simple one works as well as a complicated one. See Run Recognition and Leaderboard Campaigns.

What if our executive sponsor will not post?

Reduce the ask. A written post, a Slack message endorsing the program, or approving a post someone else drafted all deliver most of the signal. The best option is the one that actually happens.

What if activation stalls after the first month?

That is normal and it is planned for. See Keep Your Program Going After 90 Days.