The easiest part of a workplace assessment programme can be sending the links. The harder questions arrive before and after:
- Why are we asking people to take part?
- What will each person receive?
- Who needs assessment access and who needs ongoing coaching?
- Which completed profiles should contribute to Team dynamics?
- What will managers do with the insight once it exists?
If those answers are missing, quick invitations can create a slow problem: uneven expectations, teams without enough context, coaching promised to people who will not receive it, and profiles that are interesting on launch day but absent from the next real conversation.
A good rollout is not defined by a universal timetable. Organisations vary too much for an honest “go live in a week” promise. It is defined by sequence, ownership and clear decisions.
Use the following stages as planning gates. Move on when the answer is ready, not because an invented implementation clock says you should.
1. Name the workplace outcome
Start with a sentence a participant would recognise.
Weak: “We are rolling out a personality platform.”
Stronger: “We want project teams to discuss communication and decision-making differences before the next phase of work.”
Other credible outcomes might be:
- help managers prepare for better development conversations;
- give a newly formed function a shared language for working preferences;
- improve the structure of recurring 1:1s;
- understand a wider organisation before selecting people for ongoing coaching; or
- help cross-functional teams agree how they will handle pace, detail and challenge.
Keep the outcome limited enough to evaluate. An assessment cannot “fix culture” or predict performance. It can give people practical language and a profile-based starting point for better conversations.
Gate: Can the programme owner explain what should become easier or clearer without using Product terminology?
2. Define the participating groups and owner
Map who is included and who is responsible for each decision.
The Organisation Admin manages access and always occupies a Coaching seat. A Team Lead requires a Coaching seat. Those Product rules do not replace programme ownership: someone still needs to decide the rollout audience, explain its purpose, respond to participant questions and arrange the follow-through.
For each group, record:
- why it is included;
- which team or teams are relevant;
- who will introduce the programme;
- who will handle data/privacy questions;
- who will facilitate any Team dynamics discussion; and
- who can decide when access should change.
Do not use “the whole organisation” as a substitute for a participant list. Organisational structures contain leavers, contractors, people on extended leave, duplicate records and teams with different needs. Resolve the audience before creating invitations.
Gate: Is there one accountable owner and a confirmed participant source for every included group?
3. Plan the access mix around the outcome
MyTeamBuilder uses one subscription with two seat types.
An Assessment seat gives someone a unique invitation to the 36-question, 5-minute assessment and their Personality profile. Where permissions allow, a completed profile can contribute to Team dynamics. The person does not receive a MyTeamBuilder coaching account or Bilee.
A Coaching seat adds an authenticated account and private, always-on support from Bilee, the AI Coach. It suits selected people who need continuing help with workplace moments such as difficult feedback, a new management responsibility or an important 1:1. Feature-specific tools have their own requirements and should not be promised universally.
Use an access worksheet:
| Participant group | Outcome they need now | Starting access | Review trigger |
|---|---|---|---|
| Organisation Admin | Manage rollout and use private coaching | Coaching seat | Role rule: remains a Coaching seat |
| Team Leads | Lead their teams and use required team areas | Coaching seat | Role change |
| Wider participants | Profile and permitted Team dynamics contribution | Assessment seat | New responsibility or ongoing coaching need |
| Selected managers/leaders | Profile plus private continuing preparation | Coaching seat | End of programme phase or role change |
Check Pricing for current commercial terms and capacity. Do not assume Assessment seats are unlimited. Pending invitations can reserve capacity as well as completed participants, so include outstanding invitations in the plan.
Compare access before finalising the mix.
Gate: Can every included person be placed into an access path for a stated reason, with current capacity confirmed?
4. Design teams and permissions before profile completion
Team dynamics depends on completed Personality profiles and the relevant permissions. A list of assessment participants is not automatically a useful team structure.
Decide:
- which real working teams need a Team dynamics view;
- whether someone belongs to more than one relevant team;
- who acts as Team Lead;
- who should see the team view under the organisation's permissions; and
- how a facilitator will use it without turning preferences into labels.
This is also the point to separate Team dynamics from Organisation Insights in your communication.
Team dynamics is profile-derived and supports a shared conversation about working preferences. Organisation Insights is a different feature using eligible, anonymised and aggregated coaching-derived signals. It does not show individual coaching messages and should not be described as a team profile dashboard.
Gate: Do the team structures reflect actual working relationships, and can the owner explain the data source and audience for each view?
5. Write the invitation journey in plain language
Assessment Users do not register for an account. They receive a unique invitation link that takes them to the assessment and later to their profile experience.
Your invitation and briefing should answer five things:
- Why the organisation is asking them to take part.
- That the assessment has 36 questions and is described as a 5-minute assessment.
- That they will receive a Personality profile.
- Whether their completed profile may contribute to Team dynamics, where permissions allow.
- Whether they have Assessment access only or will also receive a separate Coaching-seat account.
Avoid sending an Assessment User to the normal sign-in page. They use the unique link from their invitation. Avoid promising Bilee to everyone; only Coaching-seat users receive authenticated coaching access.
Plan how people will recover the invitation, who will answer questions and what happens when a link has expired or been forwarded. Do not put real links into shared slide decks or screenshots.
Gate: Can a first-time participant explain what happens next and whether they will receive Bilee?
6. Prepare the first use before completion rises
Do not wait until profiles are complete to decide what will happen with them.
Choose a real workplace moment close enough to feel relevant:
- a team meeting about how decisions will be made;
- a manager 1:1 focused on communication preferences;
- preparation for a difficult feedback cycle;
- a project kickoff where people agree how to challenge and share detail; or
- a facilitated Team dynamics session that ends with one observable working agreement.
Give participants permission to question their profile. Ask what feels useful, what feels incomplete and what colleagues should not assume. Treat the results as hypotheses, not fixed truths.
End the first use with a specific practice to try. “Share the decision question before the meeting” is easier to review than “communicate better”.
Gate: Is a named person ready to facilitate a specific use of the insight, with an action the team can revisit?
7. State the privacy boundary before coaching begins
People may be comfortable with a profile and still be uncertain about an AI Coach. Do not leave them to infer who reads the messages.
Use the canonical wording:
Individual coaching is 100% confidential. Organisation Insights are anonymised; no individual messages are visible to Organisation Admins or Team Leads.
Explain that Team dynamics is created from completed profiles where permissions allow; it is not created from private coaching. Explain Organisation Insights separately and do not suggest that it reports named use, personal topics or message text.
Give participants a route for privacy or support questions. The Trust page can support the explanation, but it should not replace a direct rollout briefing.
Gate: Can participants identify what is shared, what is anonymised and what remains private?
8. Review completion, usefulness and access separately
Completion is necessary, but it is not the same as value.
Track operational questions:
- Were invitations delivered to the intended people?
- Which invitations are pending and still reserving capacity?
- Are the right teams represented by completed profiles?
- Do participants know where to find their profile through their unique link?
Then ask practical questions:
- Has a team used the insight in a real meeting or decision?
- Has a manager prepared differently for feedback or a 1:1?
- Did the agreed working practice help, need adapting or create a new problem?
- Does anyone's responsibility now justify a different access type?
An Organisation Admin can assign a Coaching seat later as needs develop. Access review should be linked to role and work changes, not to private coaching content; admins and Team Leads cannot inspect individual messages.
Gate: Is there a review that distinguishes operational completion, practical use and future access needs?
A compact rollout brief
Before sending the first invitation, the programme owner should be able to complete this brief:
Outcome: We are using the assessment so that ____________________ becomes easier or clearer.
Audience: The participating groups are ____________________.
Access: Assessment access is for ____________________; Coaching access is for ____________________.
Team use: Completed profiles may support ____________________ Team dynamics views under the agreed permissions.
First practical use: We will use the insight in ____________________.
Privacy explanation owner: ____________________.
Access review trigger: ____________________.
If the blanks are difficult to complete, pause the invitations. The missing decision will be harder to make once participants are already asking what the programme is for.
Roll out understanding, not just access
An organisation-wide assessment succeeds one conversation at a time. The technology can issue unique links, build Personality profiles, combine permitted profiles into Team dynamics and give selected people private support from Bilee. It cannot choose the purpose, create trust through vague language or make managers use the insight well.
Plan those human decisions before scale. Then use access that can change as the work changes.
See the organisation assessment rollout guide, see how the full journey works or talk to us about a specific rollout.