Four Ways A Good Hire Fails In Their First 90 Days

Hello Learners,

This is Learn Leadership. Every issue takes one thing that quietly goes wrong between managers and their teams, shows it happening through a real story, and leaves you with something to try this week.

Today it's the new hire who was brilliant in interviews and is somehow stalling by week eight. You'll leave with a one-page first-week checklist covering an owner, a first win, a decision map, and a check-in calendar.

Week eight, and Amara is checking everything twice

Amara joined Thomas's team in March as operations lead for a 90-person logistics company. She'd run a bigger network before, her references were glowing, and her interview case study was the best the panel had seen in two years.

By week eight she was asking Thomas before every decision. The warehouse supervisors had started going around her. Thomas sat in his car after a long Thursday and wondered if he'd hired the wrong person. He'd already started drafting the email to the recruiter in his head.

He hadn't. Amara walked into four gaps, and Thomas could have closed each one in week one. They're common enough that only 12% of employees strongly agree their organization does a great job of onboarding, according to Gallup.

Nobody owned her first month

Thomas assumed HR was running Amara's onboarding. HR assumed Thomas was. So her laptop arrived on day three, her system access on day six, and nobody walked her round the two warehouses until week three, when she asked.

Each gap was small. Together they told Amara something on her first morning: nobody here is responsible for whether you land. A senior hire reads that fast, and she spent her first fortnight working out the basics alone.

The fix is one name. Before the start date, decide who is accountable for this person's first 30 days, and write that name down where both of you can see it. Usually it's you.

That person books the first week: the intros, the site visits, the access requests and a lunch with the people whose work touches theirs. If you hand any of it to a buddy, check the buddy's calendar first so the job has real hours behind it.

She never got a first win

Amara's first assignment was a six-month redesign of the outbound network. It was the reason Thomas hired her, and it was the wrong thing to start with.

By week eight she'd produced an analysis, two workshops, and a draft model. Nothing was finished or visible on the warehouse floor, and the supervisors had no evidence she could fix anything. Meanwhile, a returns backlog of 1,400 parcels sat in the corner of site two, annoying everyone.

That backlog was the win sitting in plain sight. Pick one problem your new hire can solve in their first 30 days that people outside the team will notice and that uses the skill you hired them for. Give it to them in week one, alongside the big project. Clearing the backlog would have bought Amara the trust the redesign needed later.

Nobody drew the map of who decides what

In her offer conversation, Thomas told Amara the carrier contracts were hers. Three weeks in, the first renewal came up, and the carrier's account manager emailed Thomas, the way he always had. Thomas replied, because it was quicker.

The supervisors noticed. Within a fortnight they were checking Amara's calls with Thomas too. So Amara did the sensible thing for someone with no map: she escalated everything, which made her look hesitant.

Olga Fedoseeva, who has hired more than 1,500 people, calls this an authority gap: strong hires go cautious when nobody has written down what they own.

Write the map before day one. List the decisions that are theirs alone, with a spending limit where money is involved, and the ones that still need you. Then, for the first month, send people back to the new hire when they come to you with a decision that's on her list.

Thomas went quiet after week one

Thomas checked in every day of Amara's first week. Then quarter-end hit his calendar, and the next real conversation they had was on day 61, when he raised his worries about her pace.

For seven weeks, Amara had been guessing at the bar. She didn't know whether slow and thorough was what Thomas wanted, or a problem, and she had no way to find out except by waiting. So she did what careful people do: she slowed down further and checked more.

Microsoft saw how much contact matters in a buddy pilot involving 600 employees. Of new hires who met their buddy at least once in the first 90 days, 56% said it helped them get productive quickly. Among those who met more than eight times, it was 97%.

Book the check-ins before the start date: a weekly 20-minute 1:1 for the first month, then written reviews at 30, 60, and 90 days. Put them in the calendar now, while it's still empty, and keep them even when nothing is wrong.

The page you write before day one

Thomas and Amara rebuilt it in week nine. He wrote her decision list on one page, sent the carrier back to her, and handed her the returns backlog. It was cleared in 17 days, and the supervisors stopped going round her by the end of the month.

All four fixes fit on one page, and none of them need anyone's approval. Write the owner, the first win, the decision map, and the check-in dates before your next hire starts. Do it this week if anyone is due to join before Christmas.

Your new hire will read that page in their first hour. It's the first thing that tells them somebody planned for them to succeed.