Beyond Day One: How to Build an Onboarding Process That Lasts All Year

Part 1 of 6 in a series on onboarding, supervision, and helping new staff find their place.

There’s a difference between orientation and onboarding, and most organizations are much better at the first one.

Orientation helps someone get started. It answers the immediate questions: Where do I go? What systems do I need? Who do I call? What’s on my calendar this week? Onboarding has a bigger job. It helps a new employee understand the organization they’ve joined, the expectations around their role, the people they’ll work alongside, and eventually, how they fit into all of it. That can’t happen in a week.

It also isn’t happening as well as most of us would like to think. Gallup has found that only 12% of employees strongly agree that their organization does a great job onboarding new employees. Most organizations have some kind of onboarding process. The more common gap is how long it lasts and how much thought goes into what happens after the first few days.

Day one still matters. It just can’t be the last designed moment.

The first day matters, and it’s worth designing well. In The Power of Moments, Chip and Dan Heath describe how John Deere redesigned a new employee’s first day. Before the new hire even started, a peer reached out by email to welcome them. On day one, their name was on a sign in the lobby, that same colleague showed them around and took them to lunch, and a message from the CEO was waiting when they logged in.

I tried to design a first day with that same spirit for one new hire. It was a balance of meetings and community building. They were greeted with swag and some of their favorite things, their space was decorated, and there was plenty of time to explore, get comfortable, grab lunch with the team, and not feel as much pressure.

The first day shouldn’t be an attempt to get everything covered or checked off. Focus on a few things and help people experience your culture first. You don’t want someone to walk away from day one saying, “It was good, but all I did was tasks and trainings.” You want them to say, “It was great. I met some awesome people, they took me to lunch, and I was able to start settling in.”

When the calendar clears

I’ve been the new person in an organization where onboarding was fast and furious. The first week was fully loaded, then things died down without much direction.

A list of names isn’t a plan. If you tell a new team member to “schedule time with these folks,” they also need to know why those conversations matter, what they should cover, and when in their first few months each one makes the most sense. The same goes for the meetings they should start attending, the resources they should read, and the programs or processes they should observe. The weeks you didn’t schedule for them still need a shape.

What onboarding looks like across the first year

A thoughtful onboarding process recognizes that someone’s needs in their first month are different from their needs in months two and three, month six, or month twelve. Here’s how I think about each stage.

Month one: relationships, expectations, and transition. Early on, the focus is on building relationships with the team, understanding what’s expected of the role and the team as a whole, and giving the person room for their own transition.

Months two and three: ownership and a shared plan. This is when new staff start taking ownership of projects and responsibilities, while the supervisor keeps making space for questions. It’s also the right time to build a personal and professional development plan together. By around month three, many people have fresh eyes on how things work and are ready to suggest recommendations, efficiencies, or things that could work better. Invite that.

Month six: a low-stakes check-in. A mid-year conversation is a chance to look at progress on the development plan and on any ideas they’ve put forward. It’s also a chance to check in on things that rarely come up in a normal one-on-one: their sense of belonging, their understanding of how processes work, and how they feel about the way they’re being supervised. Keeping it low stakes makes it much more likely you’ll hear the truth.

Month twelve: review and look ahead. The annual review closes out the first year, and a development plan for year two gives the next stage a direction.

Throughout all of it, onboarding should reflect the organization people are actually joining. How you welcome someone teaches them what your values look like in practice, which is a big enough idea that it gets its own post later in this series.

Experience doesn’t replace onboarding

Very often, I see supervisors assume that experience means someone needs less onboarding. If a new hire is more senior, or has done nearly the same job somewhere else, the thinking goes, they should be able to hop in and get to work.

I’ve watched that play out with colleagues, especially at the mid-manager level. Even people with years of experience need time to adjust. We can’t expect someone to take their skills, apply them to new policies and procedures, and be successful without giving them the chance to learn how things work here, understand what’s different, and get a guide for applying what they already know.

Whether someone is an intern or a senior leader, they still need training and development. They need foundational moments that help them feel like they belong. They need to make meaning of how they’ll do their work day to day, the confidence to take ownership of their role, real collaboration with peers and stakeholders, and a meaningful relationship with their supervisor.

What changes is the size of the plan, not whether there is one. Build a framework, then add, subtract, and develop it further based on the person’s background, skills, role, and experience. Then stay flexible. If something isn’t resonating, if they identify gaps, or if they need more help than you expected, adjust. A good onboarding plan is nimble enough to change once you learn more about the person using it.

Give people structure and ownership

One tool I encourage supervisors to build is an onboarding guide. A good guide gives the transition structure without turning onboarding into a checklist to get through. It gives the supervisor and the new employee a shared understanding of what should happen and when, while leaving room for the employee to take more ownership of the process over time.

Creating that kind of resource takes work. But if a supervisor told me they don’t have time to build an onboarding guide, I’d ask them honestly: how do you expect this person to be successful and contribute in a meaningful way without it? If we don’t show someone how things work here, and then they miss an expectation because nobody showed them, we can’t be frustrated when it gets missed. That one is on us.

The work also sends a message. A thoughtful guide tells a new employee, “We’ve thought about your experience here, and we’re investing in your transition.”

The better onboarding question

The goal of onboarding isn’t to get someone through it as quickly as possible. The goal is to help them transition well.

So the strongest onboarding question may not be, “Have we taught them everything yet?” It may be, “What do they need at this point in their transition, and how can we keep supporting them?”

Because onboarding doesn’t end when the orientation calendar does.