Pilot and launch

A pilot is not a platform mode: it relies on ordinary groups and distribution, with the usual rights of each screen. This page describes the order of operations for opening the platform to learners: what to settle before anyone is invited, a pilot group, an opening in waves, a communication plan, a first piece of content, then the continuous arrival of newcomers.

Settle the long lead times first

Two things do not wait for the pilot, because one is slow and the other stays invisible until a learner runs into it.

• The app your learners will install. With Beedeez Training, the account can be opened the same day. With a white-label app, the formalities with Apple and Google come first, followed by a store review whose duration is not guaranteed: start them before you announce a launch date. See The mobile app.
• The support address your learners write to. As long as none is set, the app displays Beedeez’s own support address, and the requests never reach your learning team. Set it in Configuration → General settings. See General options.

Build the pilot group

Create a group dedicated to the pilot, like any other group. See Creating and organising user groups.

Pick a small but representative set of people: two or three sites, varied profiles, including those least comfortable with technology. The learning team alone is not enough: they already know the tool.

Add the members from the group’s edit view, with the Add/Create a learner button. ⚠️ If your account uses SSO, learners are added by identifier, not by email. See Adding users.

Distribute the launch content to the pilot group, and to it only: the pilot tests your distribution as much as your content.

Check the distribution before inviting anyone

Before any invitation goes out, open the app with a learner account and check what a pilot member will see, with Signing in as one of your learners. That right is not granted by default: request it before launch day. If the track or a capsule does not appear, fix the distribution before opening. See Common problems: distribution.

⚠️ Run that check on a test account placed in the pilot group, not on a real pilot member. Everything you do in that session is recorded on the account you opened: the capsules count as started and the last connection date is updated. An account opened this way no longer shows as never connected, which is precisely the indicator the pilot relies on.

Also proofread the invitation email in Customization → Email: it is your learners’ very first contact with the platform. See General options.

Send the invitations

Creating the accounts does not invite anyone, and accounts created by an HRIS synchronisation receive nothing either. Invitations are sent from the user list: select the people concerned, then Send invitation. See Exploring the user list.

Check the pilot, in order

1. They manage to sign in. This is where identifier, SSO and install problems surface. Verify it in the user list: an account still in Not connected status has not cleared this step. See Exploring the user list.
2. They see the right content. For an individual case, look through the person’s eyes via Signing in as one of your learners.
3. They understand what to do without being told in person.
4. They know who to write to when something blocks them.

Fix what the pilot reveals before widening: every untreated problem multiplies by the size of the next wave.

Open in waves

Do not open to everyone on the same day. Go by arrival waves: one site, then a region, then the rest. Support absorbs one wave at a time, and each wave teaches you something you fix for the next one.

💡 Create one group per wave. That is what later lets you compare one wave’s activity with the next in the statistics; retrospectively, it is impossible. See Understanding groups and Learner and group analytics.

Prepare the communication

Three messages, at minimum: before (what is coming and why), at launch (how to sign in, with the exact install instruction), after (a reminder for the people who have not signed in).

For the reminder, the user list filtered on connection status gives you the exact list of people to contact again; reminders about a specific piece of content go through notifications. See Notifications.

⚠️ On Beedeez Training, the install instruction must be explicit: the app does not carry your name, so your learners search the store for Beedeez Training, not for your company. Give the exact app name, the publisher and a screenshot of the icon. See The mobile app.

Open with a first piece of content

Do not launch with an empty platform, nor with your whole catalogue at once. A short welcome track gives people a reason to come back a second time.

The First steps track is built for this role: it opens on first sign-in and reaches learners without being distributed to a group, so it works even if your segmentation is not in place yet. See The First steps track.

⚠️ The learner still has to belong to at least one group. An account that is in no group receives no content at all, the First steps track included.

Create accounts at hiring

Once launched, the subject becomes the continuous arrival of new people. Create the account when the contract is signed, not on day one: the person can prepare before arriving. The same reasoning applies to returns from leave and internal moves.

So that these arrivals do not depend on a manual add, describe the population by criteria in a dynamic group: the platform places each new account in the right groups.

Going further

• Signing in as one of your learners: the check to run before each wave, and what it records on the account.
• The First steps track: the welcome content your communication plan announces.
• Notifications: targeting reminders after launch.
• The mobile app: white label or Beedeez Training, and the install instruction that follows from it.
• General options: the support address and the invitation email to set before opening.