A few of you have asked whether we have anything structured to give learners when you onboard them to the beta, So I put one together for you.
It's intentionally lightweight. Six short tasks covering the main things Companion can do right now, with a couple of questions after each one. The questions designed to get at whether it actually fits how people work day to day. Use them as a conversation starter with your testers, or just include them in whatever feedback process makes sense for your team.
Feel free to copy this, adapt it, and make it your own. Drop your platform name, your space URLs, and any example topics that are relevant to your context.
Companion — Learner Testing Guide
Before you start
Answer these two questions;
We want to understand how you currently work — not how you think Companion will change things. There are no right answers.
- When was the last time you needed to find something to help you do your job — while you were already in the middle of a task? (Walk us through what happened. What were you doing, what did you need, and how did you find it?)
 - What do you normally do when you need a quick answer or piece of information while working? (e.g. Google it, ask a colleague, go to the LMS, check a doc, ignore it and carry on.)
Setup Instructions
- Install Companion from the Chrome Web Store: [INSTALLATION LINK]
- Click the button that appears on the right side of your browser to open the panel.
- Enter your [PLATFORM NAME] & select Login
- Use your normal credentials as prompted.
Task 1 — Find content on a page that has a Learning Space
Go to [SPACE URL] and open Companion. You should see content appear in the panel. Browse through it and open something that looks relevant to your role.
Reflect:
- What did you expect to happen before you clicked anything?
- If Companion wasn't there, how would you normally have found that content?
Task 2 — Visit a page without content
Go to a site  you use regularly for work — a tool, an internal page, anywhere outside the platform. [provide example for your users] Open Companion. You'll probably see an empty panel.
Reflect:
- When you saw nothing, what did you think was happening?
- Did it feel like something was broken, or did it make sense?
Task 3 — Search for something you'd actually want
Use the search bar inside Companion to look for a topic that's genuinely relevant to your role — not a test topic, a real one [provide example search]. Open something from the results and spend a minute with it.
Reflect:
- Were the results what you expected, or were you looking for something different?
- Was the search and content consumption experience what you expected and was it easier then searching for it via other traditional methods.
Task 4 — Ask Harmony something real
(Skip this if Harmony isn't enabled on your platform)
Open the Harmony chat and ask it something you'd normally ask a colleague or elsewhere [INSERT EXAMPLE SEARCH PROMPT]. Then ask a follow-up.
Reflect:
- Was the response useful enough to actually use?
- What would you have done to find that answer if Harmony wasn't there?
Task 5 — Change a setting
Open Companion's settings and change at least one thing — try switching how the button displays, for example. Then navigate to a few pages and see if it takes effect.
Reflect:
- Did it work the way you expected?
- Were the settings easy to find and did they feel relevant to how you'd actually use this, or did they not matter to you?
After you're done — three questions worth asking your testers
These are the ones that tend to reveal the most:
- Walk me through what you were doing the first time you opened Companion today. What were you thinking? On any task where Companion wasn't useful — what did you do instead?
- Who on your team do you think would get the most out of this, and why them specifically?
- What would have to change for this to become a habit rather than something you tried once?
-  Where do you think we should setup content and where would you like to use Companion?
-----------------
Please share the feedback from your learners directly with me so i can take it onboard.
As always — the more honest the feedback, the more useful it is.
Thanks.
Kristian
