Induct Them Into the Week, Not the Chaos: Building a First 168 Hours That Actually Sticks

There's a version of onboarding that lives in a folder: the org chart, the health and safety policy, a password sheet, a tour of the kitchen. Then there's the version that actually happens, which is a new starter sitting quietly for five days and absorbing every habit in the building by osmosis. The second one always wins. Which is why the question worth asking before anyone's first Monday isn't "what do we tell them?" but "what are they about to copy?"

Because a working week is 168 hours, and most of a new starter's first one will be spent watching other people spend theirs.

Start with an honest calendar audit

Before you write a single induction slide, pull the last four weeks of calendar data for the role, the line manager, and anyone the new person will work closely with. You're not looking for a tidy picture. You're looking for the truth.

Ask three questions of every recurring meeting you find:

• Does this meeting exist to make a decision, share information, or because it has always existed? If it's the third, don't invite the new starter to it. You'll be teaching them a habit you'll resent in six months.
• Who actually speaks in it? If the answer is one person, the meeting is a document with extra steps, and the new starter should read the document.
• What would break if it moved? Any meeting that can't be moved is either genuinely time-critical or held together by superstition. Worth knowing which.

This audit is uncomfortable, which is the point. A new starter's first week is the only moment where you get to decide, deliberately, which of your existing routines get passed on. After that, they inherit the lot.

Pick your shadows on purpose

The instinct is to pair a new starter with the busiest person in the team. Resist it. The busiest person is usually busy because they've become the human firewall for everything that isn't working, and what they'll teach — inadvertently, generously — is firefighting.

Choose shadows who model the routine you'd actually like to see replicated. If you want people to leave at half five, have them shadow someone who leaves at half five. If you want quotes turned around in two days rather than two weeks, put them next to the person who does that. Shadowing is a values transfer, whether you frame it that way or not.

A workable structure: two days with someone in the same role, one day with a person in an adjacent team, one day with the person who handles your messiest process, and half a day with whoever deals with customers. That last one is often skipped and shouldn't be.

Set the defaults in week one

Defaults are the habits nobody debates because nobody remembers choosing them. Week one is when they set.

A few worth stating out loud in the first 48 hours, because they will otherwise be inferred from whoever's nearest:

• Meetings are 25 or 50 minutes, not 30 or 60, unless there's a reason.
• An invite without an agenda is a suggestion, not a commitment.
• The first hour of the day is for work that needs a brain, not a tray.
• Nobody is expected to answer anything between seven in the evening and eight the next morning.

Say them, write them down, and then — this is the part that matters — visibly follow them yourself in front of the new person. A default that the founder ignores is not a default. It's a rumour.

A skeleton for the first five days

Not a minute-by-minute timetable; those collapse by Tuesday lunchtime. More of a spine.

Day one. Arrive to a working laptop and a named person who is expecting them. Tea, tour, team introductions, and one small, genuinely useful task completed before home time. The task matters more than the tour — finishing something on day one sets a tone that a week of shadowing cannot.

Day two. Sit with the role's closest counterpart. Watch, then do a piece of it with someone alongside. No solo work yet.

Day three. The messy process, explained honestly. Say why it exists, who it frustrates, and what's being done about it. Context turns chaos into a workaround; without context, it just looks like the standard.

Day four. A real piece of work with a real deadline, small enough to finish, with a check-in at the halfway point rather than at the end.

Day five. A 30-minute debrief with the line manager, and one question that earns its keep: what felt odd this week? New starters are the only people who will ever see your business clearly. That clarity has a shelf life of about ten days.

Be explicit about what you're not handing over

There's a temptation to present every process as settled. It isn't. A new starter who is told "this report exists because a client asked for it in 2019 and we never stopped" learns something valuable: that the business can tell the difference between a rule and a relic.

Handing over bad habits isn't inevitable. It's just the thing that happens when you don't decide otherwise.

The bit people forget

Onboarding doesn't end on Friday. It ends somewhere around week six, when the new starter stops asking why and starts doing it the way everyone else does. If the first 168 hours were designed, that moment is a good one. If they weren't, it's the moment your newest hire quietly becomes your oldest problem.

Worth a calendar audit, then. It's a fraction of the time you'll otherwise spend unpicking it.