Originally on Medium

Onboarding Is Leadership in Its Purest Form

A new colleague’s first days show how a team leads, works, and cares. Onboarding is a leadership task, and I treat it as one.

01

Summary

Onboarding is where trust begins, culture becomes tangible, and momentum is built or lost. Across four leadership roles in two companies I have refined a system with nine parts, from a personal welcome and shared to-dos to first assignments, an exchange of READMEs, and an invitation to improve the space. It does not need to be perfect. It needs to be intentional.

02

Why onboarding matters

When a new colleague joins your team, the first day sets the tone for how you lead, how the team works, and how much you care about people succeeding. In many organisations onboarding is still an afterthought: a task for HR, a few links to tools, maybe a welcome lunch.

For me, onboarding is leadership in its purest form. People form their first impressions here: of the team, of the company, and of their decision to join. If you take it seriously, they feel it. If you improvise, they feel that too.

The system I use is now part of every new hire’s experience in my team. It rests on feedback, trial and error, and one belief: people deserve a great start. I am sharing it because I have seen what happens when people arrive with clarity, context, and purpose, and what happens when they do not.

The onboarding lives in a shared workspace, and the structure works in any tool. It has nine parts, and each has a job.

03

Welcome page: start with feeling

The first page is personal and written directly to the new joiner. I say I am glad they are here, give my email, phone, and chat handles, and make one thing clear:

“This is your space: explore it, shape it, make it yours.”

People forget most of what they read on day one. They remember how they were made to feel.

04

First steps and to-dos: shared effort

This page has two halves.

Their to-dos

They are light but meaningful: log into the key tools, explore how we work, and write a Personal README. That is a short document on how you like to work, what you need to thrive, and how others can best collaborate with you. I share mine, my Management README, first. There are no secrets and no hidden rules, which reduces anxiety and starts the relationship with transparency.

Our to-dos

This half lists what we have already done: the device is ready, the accounts are set up, and the invitations to team rituals are out. Onboarding is not something that happens to new joiners. It is something we do with them.

05

People to know: make people reachable

There is no organisation chart. I list the people they will meet first, by role or area. Each entry says what the person does and how their work connects to the new joiner’s, with a short, neutral note on what collaborating with them is like. The notes inform without biasing. I also assign a sherpa, someone who guides them through early projects and questions. The fear of “who do I ask?” goes away.

06

Workspaces and tools: reduce the load

This page is the master list of systems: collaboration, project, design, and HR tools, brand assets, and internal spaces. Each entry has the login structure, the setup instructions or who to ask, a line on what the system is for, and a direct link. Nobody remembers 10 systems on day one, but they remember where to look. New joiners can update the page too, so it stays current.

07

How we work: make the unwritten visible

Culture lives in shared habits and rhythms. This part covers weekly check-ins and team lunches, how feedback flows, where team rituals happen, how to request time off or support, and small things like our Hero of the Week, a space to recognise small contributions. When culture is visible, people belong sooner.

08

First assignments: create momentum

In the first days I give a few small missions, each with clear expectations and someone to ask. For example:

  • Observe a product launch in one market, take notes, and ask questions.
  • Join a cross-functional meeting and summarise your takeaways.
  • Support a small UX research effort and shadow a senior colleague.
  • Explore a live feature and document your first impressions.
  • Test a content flow or checkout process and report usability findings.

Early wins show progress and give people the sense that they are already contributing.

09

README exchange: set expectations early

I share my Management README: how I work, what I value, how I make decisions, and how I give and receive feedback. Then I invite them to share theirs. They are not rigid rules. They remove ambiguity and give both of us a map for how to work together.

10

The day-one message: start with energy

Before the first official moment I send a short, personal email with a warm welcome, the link to the onboarding space, the steps to activate access, and an open invitation to ask anything. It removes the “what now?” feeling and shows that the start was prepared.

11

Ownership: this is their space too

At the end of the space I always add this note:

“You have full access to this space. You’re free to add, change, improve, and shape it however it helps. Make it better for the next person, too.”

The space is never finished. Every new colleague adds to it.

12

Start here

Onboarding is a small act of leadership that leaves a lasting mark. If culture and trust matter to you, start with it. Make it personal, make it structured, and make it better with every new colleague.

All Thoughts

Niklaus GerberDigital & Platform Executive

Twenty years making digital stick in organisations not built for it.

Vice President Digital at Vorwerk Home, responsible for product, platform, and e-commerce across Europe. Before that, I founded the product function at NZZ.

My work sits where digital ambition meets legacy platforms, many stakeholders, and teams that need a reason to change. At NZZ, we shipped AI audio in 2018, among the first publishers anywhere to do so.

Playground

I build tools when the thinking needs a shape. Lately that means hands-on work with agentic AI. Most start as a fix for my own team and then find a wider audience. Each one tests an idea before I put more weight on it.