You've built the structure, filled it, and designed the journey through it. Now your team needs to know it exists, and to find it faster than asking someone.

A launch is a moment you plan, not an invite you send. This module covers how to run one that sticks.

Before anything else, pick two things.

A date. A specific day when your team starts using Waybook. Put it in the calendar and tell people it's coming. A launch your team can see approaching gets a far better first week than one that simply appears in their inbox.

One number. The single measure that tells you it worked. How long it takes a new starter to work unsupervised. Completion of your first Learning Path. How often the same question still comes to a manager. One number, agreed up front, beats five you'll never look at.

Immerse Education hire hundreds of seasonal staff each year across the UK, US, Singapore and Tokyo. A planned, dated launch got them 50% faster onboarding and saved over $50,000 replacing their previous LMS.

Going team by team is a good plan, and often the right one for a business with several departments or sites. It gives you a smaller group to support properly, and what you learn in phase one makes phase two easier.

A phased launch works when every phase has three things:

Start with the team that will feel the benefit fastest, usually the one doing the most onboarding or answering the most repeat questions. Their result is what sells phase two internally.

If a new starter logs in and sees every process for every department, they'll close the tab. What you want them to see is a short, obvious set of things that are clearly theirs.

Member Groups control what each person can see. Build them two ways at once:

People can, and usually should, belong to more than one. A marketing manager sits in both Marketing and Managers, and sees everything either group gives them.

It's also worth separating viewing from editing - a read group for the whole department, and a smaller group for the few people who build content. It keeps permissions easy to reason about as you grow. Where one person needs an exception, use a permission override rather than a new group.

If you want the full picture of how groups, member types and permissions fit together, member types vs. permissions is the article to read alongside this one.

You'll see a preview of exactly what each person will be able to access before the invite goes out, and you can match a new team member's permissions to someone already on the team. Inviting your team to Waybook walks through it in full.

The habit forms in the first 48 hours. If your team finds their first three answers in Waybook, they'll keep looking there. Bring it to where they already work:

The habit is set by whoever leads it. Instead of writing the answer out in chat, post the Waybook link. It takes the same ten seconds, and it teaches everyone where answers live.

When leadership treats Waybook as the single source of truth, the rest of the team follows within weeks.

The engine is built, the access is set, and your team is about to walk through the door. Pick the date first - everything else lines up behind it.

In Module 6: Measuring and Optimizing, your launch turns into a rhythm.