What this is for: this platform is designed to build soft skills through a connected journey rather than isolated activities.

Step 1, baseline: the journey starts with a baseline assessment so the learner can see where strengths and development needs sit today.

Step 2, practice: targeted scenarios, assigned practice, and completed sessions help the learner work on the capabilities that matter most next.

Step 3, real-world application: observations bring actual communication moments back into the platform so reflection and coaching are grounded in real work rather than simulation alone.

Step 4, development plan: the development plan ties all of that together into one view of what has been completed, what is active now, and what should happen next.

How to use this guide: start with the part of the journey you are in now, then use the more specific articles linked from each page when you need task-by-task guidance.

What this is for: the platform does not generate guidance from one place only. Different parts of the journey contribute different kinds of signals.

Baseline guidance: recommendations can come from assessment results and the mappings between weaker capabilities and relevant skill-focus areas.

Practice guidance: coaching can come from assigned scenarios, completed session history, and recommendations linked to the learner’s current development needs.

Observation guidance: observation feedback comes from transcript analysis first, then from coach or admin review if the learner explicitly requests it.

Development plan guidance: the development plan pulls those signals together into one current focus and a smaller set of next actions.

How to use this well: if a recommendation does not make sense, check which part of the journey is driving it. That usually tells you where the explanation or correction needs to happen.

What this is for: the baseline assessment gives the platform a starting point for your development. It helps the system understand where your current strengths and development needs sit before practice begins.

Before you begin: set aside enough time to complete the full question set in one sitting if possible. Answer based on how you usually operate in real work, not on the ideal version of yourself.

Steps: open the Baseline Assessment page, work through each page of questions, select the option that best matches your normal behaviour, and submit once every question has been answered.

If you are not ready to do it immediately: some learners may be allowed to skip for now. If that option is available on your account, you can return later from the learner menu.

What happens after submission: your answers are saved and the baseline may go through review before the full report is released back to you.

What you will receive once released: the released baseline can include domain scores, a capability profile, an archetype, and recommendations that influence your next steps across the platform.

If something looks wrong: if the page does not load, your answers do not submit, or the report does not appear when you expect it, open the Help center or contact the team managing the platform.

Tip: treat the baseline as a starting point, not a judgement. The value comes from making your next steps more accurate, not from trying to get a high score.

What this page is for: the development plan is your working view of progress across baseline, practice, and real-world application.

Step 1, read the journey: the journey section shows where you are in each pillar and what is currently active inside each one.

Step 2, check current focus: current focus highlights the one thing that matters most right now. If you are unsure what to do next, start there first.

Step 3, review momentum: momentum shows what has already moved forward so the page reflects progress and traction, not only unfinished work.

Step 4, use next actions: next actions are the most direct route into the next meaningful task. Use them when you want to move immediately from guidance into action.

When to use this page: check the plan when you first return to the platform, after a completed practice session, or after reviewed observation guidance comes back.

If something feels out of date: refresh the page after completing a task or acting on guidance. The plan is designed to adapt as you move through the journey.

Tip: this page is not a static report. It is meant to be the quickest way back into the right next action.

What this is for: assigned practice helps you focus on the scenario that is most relevant to your current development needs.

Before you start: check whether you already have an open practice session. If you do, it is usually better to continue that session than to start a new one.

Steps: open the Practice page, look at the assigned practice section first, choose the preferred or recommended scenario, and start the session from there.

If you already started something: open sessions show conversations that are already in progress. Use those to continue where you left off rather than losing momentum.

During the session: use the session controls when you need to adjust how practice feels. Response speed changes pacing, and AI voice can be turned off if you prefer to read the AI turn instead of hearing it spoken.

After you finish: review the coaching, note any recommended next step, and then return to your development plan to see how practice has changed your current focus.

When to use the scenario library instead: browse the full library when you want more repetition, when you have already completed the current recommendation, or when you are doing extra self-directed practice.

If something looks wrong: if an assigned scenario does not appear, if the wrong session opens, or if a completed session is missing from history, check the Help center or raise it with the platform team.

Tip: avoid starting lots of sessions without finishing them. Complete cycles of practice and coaching are much more useful than partial attempts spread across many scenarios.

What this is for: the scenario library helps you find extra practice beyond your current assignment or recommendation.

How to browse effectively: use the category filter when you want to stay inside one kind of scenario, such as feedback, stakeholder management, or people development.

How to search: use the search box when you know the kind of moment you want to practise. Search checks scenario titles, summaries, roles, settings, and related skill cues.

How paging works: if there are many results, move through the pages instead of expecting the full library to appear in one long list.

How to choose well: look at the role, setting, summary, and difficulty together rather than choosing only from the title.

If nothing matches: clear the filters, try a broader search term, or return to the assigned practice section for the most guided next step.

How this fits with recommendations: the library is useful for repetition and self-directed practice, but assigned or preferred scenarios are still the best place to start when you want the most targeted next step.

Tip: if you find a scenario you want to revisit, complete the current session first before opening too many new ones in parallel.

What this is for: completed practice sessions can include rubric scores alongside the written debrief and coaching rationale.

What scale is used: the visible rubric scores are shown on a 1 to 100 scale. They are not scores out of 5 or out of 10.

What the numbers mean: a higher score means the learner handled that competency more effectively in this specific conversation, based on the transcript, the scenario success criteria, and the hidden tensions.

What the score is not: it is not a permanent ability rating and it is not meant to summarise your whole development in one number.

How to read the score properly: always read the score together with the rubric rationale, key moments, missed signals, and priority actions. The explanation matters as much as the number.

How to compare scores over time: use repeated scores in the same competency across multiple completed sessions to understand whether you are improving, holding steady, or slipping.

Why two sessions can differ: scenario difficulty, pressure, stakeholder behaviour, and how directly the conversation tests a competency can all affect the result.

Tip: treat practice scores as directional coaching signals. The most useful question is usually not "is this good?" but "what should I do differently next time?"

What this is for: observations let you bring a real communication moment back into the platform so your development is grounded in actual work, not only simulated practice.

Privacy first: observations are private by default. Only you can see them unless you explicitly request review.

Steps: open Observations, create a new observation, add the title and context, paste or upload the transcript, save it, and then run the analysis.

How scoring works here: observations do not currently use one single learner-facing numeric score in the same way practice sessions do. Instead, the platform shows analysis, findings, key moments, themes, and suggested next steps.

What to do after analysis: read the findings privately first. Use that moment to reflect on what happened before deciding whether you want outside guidance.

If you want coaching input: use the request-review action. That sends the observation into the shared review queue while keeping it visible to you the whole time.

What happens after review: once guidance is returned, the reviewed observation can point you to a more specific next step or a linked practice scenario.

How to read the result well: focus on the evidence, the themes that are surfacing, and the suggested next practice rather than looking for one headline number.

What stays private and what does not: the raw observation stays private unless you share it. The platform may still use derived signals for progress and reporting without exposing the full transcript.

If something looks wrong: if the transcript does not upload, the analysis does not appear, or the observation disappears from your list, check the Help center or report the issue.

Tip: you do not need to share every observation. Private reflection can already be very useful on its own.

What this is for: reviewed observation guidance helps turn a real-world communication moment into a concrete next practice step.

Step 1, read the review note: once a coach or admin has reviewed your shared observation, look first at the returned guidance and what it says about the moment that mattered most.

Step 2, check the suggested next step: reviewed observations can include a linked scenario and a short explanation of what the next practice should strengthen.

Step 3, act from the observation: if a scenario is linked, you can add it to practice or start it immediately from the observation itself.

Step 4, return to your plan: once you act on that guidance, the development plan should start to reflect that you are now applying coaching rather than only receiving it.

If there is no linked scenario: sometimes the platform identifies the practice area correctly but there is not yet a matching published scenario available from that screen.

What good follow-through looks like: complete the suggested practice, review the resulting coaching, and then check whether your current focus has moved on.

Common mistake to avoid: treating the review note as the end of the cycle. The real value appears when guidance changes what you do next.