Own the work.
Build what’s next.
Clear expectations, practical learning and progress you can see, for every person on your team.
- Invitation only
- Seen by who is responsible, nobody else
- Every change in the history
From what good looks like to work that shows it.
Six steps, in the order things are made. The workspace keeps the same order.
A department writes its skillsets and programmes
A skillset says what good looks like; a programme says how somebody gets there.
Teams gather the people
Each team has a lead, its mentors, and the kinds of work it can hand out.
People join by invitation
Invited by name, they answer a few questions about themselves on day one, and again whenever they are asked.
A learning path is started
The programme becomes one person’s weeks of work, each closing on its day.
Work is done and reviewed
Evidence goes on the task; a reviewer accepts it or asks for changes.
Progress is assessed
A finished programme is scored in private, then the result is published.
One workspace, three ways of looking at it.
Team members
Your tasks, your learning path and your goal skillset in one place, seen by nobody but the people responsible for you.
Team leads and department heads
Write skillsets and programmes, start the paths, review the work and assess where people are, and ask people again where they stand. The sidebar says what is still missing.
Organization administrators
Invitations, settings, roles, the organization’s own questionnaires, the audit history, and the Microsoft, Google and GitLab connections you already use.
Sign in, assign and send from the tools you already have.
Microsoft sign-in
The account your people already have.
Google Workspace sign-in
Its own domain, its own second factor.
GitLab assignments
A repository of its own for each assignment.
Mail that says one thing
A notice links to its page and carries no token; an invitation or recovery link is erased once sent.
Private by construction, not by promise.
Built for a company’s own evaluations of its own people: what is private stays private, and what is done is written down.
An authenticator for everybody
Set up at first sign-in, with recovery codes.
Sessions that end when they should
One sign-out, password change or recovery ends them all.
Evidence scanned before it is stored
Every upload is checked before it reaches storage.
A history that cannot be edited
Every change is appended to a chain; a break shows.
Support that has to be granted
For a reason, for a day at most, and the organization’s administrators are told.
Tenants that stay apart
Each organization has its own people, skillsets, programmes and history.
Ready to see it with your own team?
Tell us about your department and how your people learn today. We will show you how the learning plane fits, and set up your first organization with you.