Onboarding
Expectations, set on day one.
Thirty-day objectives are the cheapest performance intervention available and almost nobody does them, because writing them takes twenty minutes that nobody schedules.
Suggested by the role
"Understand the current campaigns, review the funnel, prepare a first growth report." Proposed from the role template, edited by the manager, agreed with the person.
Reviewed at thirty days, deliberately
A scheduled conversation rather than an anniversary that passes unnoticed. This is the first real signal about whether a hire is working.
It becomes the first objective set
Day-thirty objectives flow into the ongoing objectives rather than being a separate exercise that ends when onboarding closes.
Onboarding
The rest of this area.
A workspace per joiner, generated from the role rather than assembled from memory.
Onboarding workspaces
One place per joiner where everything for that start date lives.
Templates
Define an onboarding once per role, not once per person.
Tasks & owners
Each step with a name against it, a date and evidence where it matters.
Access on day one
The accounts and permissions the role needs, prepared before the start.
Before the start date
The fortnight between accepting and arriving, which is usually silence.
Set up your company
From a spreadsheet to a working People Graph in an afternoon.
Run your team with clarity.
From the moment someone joins to the day their responsibilities are handed over, Orglume keeps your people, their work and your organization connected.
Set up from a spreadsheet · Nothing about the AI is metered · [email protected]