Turning an onboarding guide into a welcome session deck

Many teams have a written onboarding guide. It covers who’s who, which tools to set up, how work gets done and where to find things. It’s a great reference. It’s also far too much to take in on day one.

A welcome session fills the gap. It’s a short, live walk through the essentials, usually in the first day or two, with time for questions. The deck for it should come from the guide, so the two never disagree. Here’s how to build it.

Decide what the session is for

The guide’s job is to be complete. The session’s job is to help someone feel oriented and know where to look next.

Before you open the guide, write down what a new joiner should be able to do after the session. For example:

• Say what the team does and who it serves
• Name the people they’ll work with most
• Know what their first few weeks look like
• Find the guide and know who to ask for help

That list is your outline. Anything in the guide that doesn’t support it can wait.

Sort the guide into now, soon and later

Go through the onboarding guide section by section and give each part a label.

Label	Meaning	Where it goes
Now	Needed in the first day or two	The welcome deck
Soon	Needed in the first month	Mentioned in the deck, detail in the guide
Later	Reference for when it comes up	Guide only

Typical “now” items are the team’s purpose, key people, the first-week plan and how to get help. Tool set-up steps, expense rules and detailed processes are usually “soon” or “later”. They matter, but nobody remembers them from a slide.

A welcome deck in eight slides

A structure that suits most teams:

1. Welcome. Their name, the date, and one friendly line about why they’re here.
2. What we do. The team’s purpose in a sentence or two, and who it serves.
3. Who’s who. The handful of people they’ll work with first, with roles. Photos help if you have them.
4. How we work. Three or four habits that define the team, such as where decisions are written down or how meetings run.
5. Your first weeks. A simple timeline of what to expect in week one, week two and the first month.
6. Where things live. The guide, the main channels and the key documents, named and briefly described.
7. Who to ask. A buddy or point of contact for each kind of question.
8. Questions. Leave this open and actually wait for them.

Eight slides can easily fill thirty minutes once people start asking things, which is the point.

Write it for someone with no context

New joiners don’t know your shorthand yet. A few things to watch for:

Spell out names and acronyms. “The ops review” might need a line: “a weekly meeting where we check orders and delivery times”.

Use people’s names, not just roles. “Ask Priya about access” is more helpful than “contact the admin team”. (Illustrative.)

Show, don’t list. A simple diagram of how a request moves through the team is easier to follow than a paragraph about it.

Keep slides light. The guide has the detail. The slides are prompts for you to talk.

If your guide is written with clear headings and short sections, this step gets much easier. The same principles apply to any document, and how to turn a written document into a presentation covers them in full.

Keep the guide and the deck in step

Onboarding guides change often: new tools, new people, new processes. If the deck drifts from the guide, new joiners get mixed messages.

• Update the guide first, then the deck.
• Put the guide’s link on every slide’s footer or at least on slide 6.
• Review both whenever someone joins. Ask each new joiner what was unclear after their first month, and fix the guide.

A useful side effect: running the session regularly shows you which parts of the guide confuse people. Those are the sections to rewrite.

Running the session

A few habits make the session feel welcoming rather than like a lecture:

• Keep it small. One to a few new joiners plus one or two hosts works better than a big room.
• Bring in the people on the “who’s who” slide for a few minutes each, if you can.
• Pause after the first-weeks slide. It’s usually where the most questions come from.
• Send the guide link straight after, with a note pointing to the “soon” sections they should read that week.

If the new joiner is arriving into a specific project, pair the welcome session with that project’s kickoff material. From project plan to kickoff presentation shows how to build that deck.

Ready for the first day?

• Does the deck cover only what’s needed in the first few days?
• Does every slide link back to where the detail lives in the guide?
• Have acronyms and internal names been explained?
• Is there a named person for each kind of question?
• Is there real time left for questions at the end?