One organization,
from day one to its first evaluation.
Read it like a book. Each chapter plays as you scroll to it: who does what, in the order things are made, from the platform console to the yearly evaluation.
Scroll to beginThe platform creates the organization.
Every organization is its own tenant: its own people, skillsets, programmes, connections and history. It is born on the platform console.
A name, a slug, a timezone, and whether only addresses on its domains may sign in. The platform runs the platform; it is never a member of what it creates.
Platform superadminThe first administrator is invited.
The platform invites one person by name and address. The link is shown once and works once; it is shared the way the company shares things.
On the link, they choose a password and set up an authenticator, and keep their recovery codes. From then on the organization is theirs, and the platform steps back.
Platform superadmin → organization administratorInvitation · organization administrator
First sign-in
The administrator takes over.
Settings first: the second factor, the evaluation date, and the tools the company already uses.
Microsoft or Google for sign-in and GitLab for assignments with a repository of their own. Each connection is the organization's own; the platform only allows it. Invitations and notices go by the platform's own mail, where it sends mail. The organization's own questionnaires, on what every department shares, are written here too.
Organization administratorDepartments and teams give the organization its shape.
A department is a body of knowledge: Engineering, Design, Marketing. Teams are where people work: Frontend, Backend, DevOps.
A new organization starts with no department. The administrator creates the first, names its head, puts teams under it and names each team's lead. A lead may add mentors.
Organization administratorThe department writes what good looks like.
A skillset lists the capabilities and their levels: U for not yet assessed, 0 to 4, NA where a capability does not apply.
A programme turns the skillset into weeks of work, each with a checklist, what acceptance looks like and an effort estimate. Leads draft; the head publishes; a published version is frozen, and a change is a new version. A draft can be written for you from a sentence.
Department head · team leadsSkillset · Engineering skillset · v1 Published
| Capability | Level |
|---|---|
| Builds features | |
| Owns delivery | |
| Explains decisions |
Programme · Engineering foundations · 9 weeks
People join by invitation, and say where they start.
Nobody signs up. The administrator invites a person by name and work address, into a department and at least one of its teams.
On their first day they answer what the invitation asks them about themselves, part by part: their department’s skillset and the organization’s own questionnaires. "I don’t know" is a real answer. Nobody scores it; it stays with their record for the people who follow their work, and a head or an administrator can ask again later.
Organization administrator → memberAda's questionnaire · what you said when you joined
A learning path starts.
One person, one team, one programme, from a kickoff date. The weeks become tasks, counted from the kickoff's Monday.
No programme may run past the evaluation date: a kickoff whose weeks would cross it is refused by name. Once the date has passed, nothing new starts until the next date is set. Work already under way goes on.
Team lead · department headRefused, by name
Engineering foundations would run until Sunday 6 December, past the evaluation on 22 October.
Work is done, and somebody looks at it.
A week's task carries evidence: a file, scanned before it is stored, or a repository the platform provisioned in the company's GitLab.
A reviewer accepts it or asks for changes, and the feedback stays on the task. A week closes on its due date: a warning two days before, no evidence after, and the lead can reopen it by moving the deadline.
Member → lead, mentor or headWeek 3 · Ship a feature behind a flag
The programme gets its result.
When the weeks are done, the path is assessed once, on one page: a level and a note per capability, then what the person is told.
The person reads the levels, the notes and the feedback; private notes stay with the assessors. Nobody assesses their own work. Publishing completes the path, and published results are what skill evidence is built from.
Team lead, head or administratorYour draft Only assessors, until published
The result they read Published
| Builds features | 3 |
| Owns delivery | 2 |
| Explains decisions | 3 |
Strong progress. Next: own a service end to end.
Once a year, the evaluation, in words.
On the evaluation date, the head of each department writes, for each of their people, where they stand and where the head wants them to be.
One record per member, per department, per year: the home department always, and every department whose programme the person was on. No level per capability, no grade. It is written over a frozen record of that department's facts, private until published, and the year is gathered on one PDF for the person and the administrators.
Department headAda · Engineering · 2026 Draft
Where you standEverything that happened is written down.
Every change in an organization is appended to a chained audit history. A row cannot be altered or removed without the break showing.
Each role sees what it is responsible for and nothing it is not: a head their department, a lead their team, a member their own work. Platform support sees how it is set up, never anybody’s work, and only under a grant its administrators are told about, for a reason, for a day at most.
Everybody, each within their responsibilityWho sees what
Eleven chapters, one order of work.
- 1The platform creates the organization.
- 2Its first administrator is invited and signs in.
- 3Settings, domain, evaluation date and integrations.
- 4Departments with heads; teams with leads and mentors.
- 5Skillsets and programmes, published by the head.
- 6People invited into teams; the questionnaire on day one.
- 7A learning path from a kickoff, never past the evaluation date.
- 8Evidence, review, weeks that close.
- 9One result per programme, published, completing the path.
- 10The yearly evaluation per department, gathered on one PDF.
- 11An audit history nobody can edit; each role in its scope.