Global Onboarding System for a Distributed Company

Modern architectural building with curved white exterior walls and a staircase visible through a circular opening, against an overcast sky.

AURORA TECH

They asked for "better onboarding" but the problem was the system underneath it.

  • Overview: privacy-first software company, ~1,200 people across 35+ countries. Remote-first, async culture. Limited tracking tools due to privacy constraints.

  • Result: 20–30% faster time to first contribution. Fewer repeated questions to managers. More consistent experience across all regions.

  • Geometric drawing of an outline square with sections divided by vertical, horizontal, and diagonal lines.

    Diagnosis

    The problem wasn't knowledge gaps. It was decision overload.

    New hires were being asked to make too many decisions too early, without a shared structure, a clear starting point, or a system they could trust.

    Key insight: No training program fixes a broken system. The system needed to be redesigned first.

  • Geometric drawing of an outline square with sections divided by vertical, horizontal, and half circle lines.

    Design

    Three phases. One goal: independent contribution in 30 days.

    Phase 1 orients. Phase 2 guides. Phase 3 executes. Each phase reduces the decisions a new hire has to make, until they don't need to ask anymore.

    Key insight: Clear structure → fewer decisions → less confusion → faster contribution.

  • Geometric drawing of an outline square with sections divided by vertical, horizontal, and circle lines.

    Measure What Matters

    Success isn't completion. It's time to first meaningful contribution.

    Three signals: time to first contribution, reduction in repeated questions, self-reported clarity at week 1 vs week 3.

    Key insight: If managers are still answering the same questions in week 3, the system isn't working.

  • Geometric drawing of an outline square with sections divided by vertical, horizontal, and diagonal lines.

    Keep It Working

    Governance isn't a maintenance task. It's a design decision.

    Clear ownership per section, content updated based on real usage signals, feedback loops built in from day one. The system stays accurate without depending on a single person.

    Key insight: A system that requires heroic effort to maintain will eventually fail. Design for sustainability from the start.

The decision-making process

  • We did not create additional training until the system was diagnosed. Adding training to a broken system adds noise, not clarity. The instinct to build something had to be resisted until we understood what was actually failing.

    We reduced the number of decisions new hires make in the first 30 days. The goal wasn't to give people more information. It was to give them fewer choices, until they had enough context to make good ones.

  • Onboarding was separated into core (everyone) and role-specific tracks. Consistency and autonomy are not opposites. Everyone gets the same foundation. Role specifics are layered on top.

    Tool access was sequenced based on onboarding phase. Exposing all tools on day one creates cognitive overload. Access was tied to the moment each tool became relevant, not all at once.

    A single clear starting point was defined for all onboarding-related knowledge. One entry point. No ambiguity about where to go first. This decision alone reduced repeated questions significantly.

    • Structured, self-serve flows were prioritized to fit the async culture. A system that requires a manager to activate it doesn't scale in an async environment. Every flow was designed to work without someone in the room.

    • Ownership, review cycles, and feedback loops were defined before launch. Governance designed after launch is governance that never gets done. Ownership was documented as a prerequisite, not an afterthought.

    • Success was defined as time to first contribution, not completion rates. Completion tells you someone clicked through. Contribution tells you the system worked. These are not the same metric.

Diagnose an issue yourself
Check out other projects

Explore the system

  • A grayscale photo of a simple, symmetrical staircase leading up to a series of arched doorways or windows, creating a tunnel-like corridor with a series of repeating arch shapes.

    30-Day Onboarding Plan

    A structured 30-day path from orientation to independent contribution. Three phases, sequenced by what a new hire needs to know, not by what's easiest to document.

    See the full plan
  • A modern pendant light fixture hanging from a ceiling, with a simple metal shade and visible light bulb, in a minimalist style.

    Role Specifics

    The core system stays consistent. Role-specific layers adapt it: adding the tasks, tools, and knowledge that only matter for that function, at the moment they matter.

    See how roles adapt the plan
  • Close-up of a black sharpened pencil tip on a white background.

    Governance & Maintenance Model

    A system that can't be maintained will drift. This model defines who owns what, how updates are triggered, and how the system stays accurate without depending on one person.

    See how it scales