Use cases
Seven moments where development happens and nothing is written down
Each of these is already in the calendar. It does not add a step to any of them — it is present, and what happens becomes evidence.
What the organisation declares
An organisation declares which of these it wants captured before anything is switched on. Nothing outside that list is captured in the room, and the list is visible to the people it concerns. What a person’s own connected sources contribute is a separate channel — theirs to authorise and theirs to revoke — set out on the product page.
- 01
Selection interviews
The first conversation, before anyone is an employee.
- What is captured
- What the candidate demonstrated, what they were asked, and what was agreed about their development if they join.
- What comes out
- A development record that starts on day zero instead of being reconstructed six months in — and a handover from hiring to management that is evidence rather than an impression.
- 02
Meetings
The working meetings where people explain, decide and get corrected.
- What is captured
- What a person explained, where they were confident, where the discussion had to go back over something.
- What comes out
- Evidence of applied knowledge in the place it is actually applied, rather than in a test.
- 03
Tutoring
One-to-one sessions between a person and whoever is bringing them on.
- What is captured
- What was worked through, what was still difficult at the end, and what the tutor asked for next.
- What comes out
- A tutor who can see the whole path rather than only their own sessions, and a record of what the tutoring actually changed.
- 04
Webinars
Remote sessions, usually with many people and little feedback.
- What is captured
- Participation and the questions asked, for the people who agreed to be captured.
- What comes out
- Some signal from a format that today produces almost none beyond an attendance list.
- 05
Seminars
In-person training, often expensive and rarely measured.
- What is captured
- What was covered, what was practised, and what participants demonstrated during it.
- What comes out
- A basis for asking whether the seminar was worth repeating, answerable with something other than a satisfaction score.
- 06
Other learning moments
Whatever else an organisation recognises as development and declares.
- What is captured
- The same as any declared moment, on the same terms.
- What comes out
- The record follows how the organisation actually develops people, rather than how a course catalogue is structured.
- 07
Checking what stuck
The moments where what was learned, or what was put into practice, is actually verified.
- What is captured
- What the person could do afterwards, and in what conditions.
- What comes out
- The difference between attendance and capability, recorded rather than assumed.
The moment most organisations skip
Training is measured at the end of the session, when nothing has been applied yet. The moments that would answer whether any of it held — a week later, in a real meeting, under pressure — are exactly the ones nobody records. They are on this list deliberately.
Everyone in the room knows
Every moment on this page involves people. They are told before capture begins, the declared list is visible to them, and the same limits apply whether they are the subject of the record or simply present. How that works is set out in full on the recording and rights page.