Hiring Is Not the Bottleneck

Good morning,

A new person starts, and the first 90 days still depend on whoever happens to have time. Accounts show up late. Training is a pile of logins and old docs. The existing team answers the same questions again, so hiring adds work before it adds capacity.

Showing the tools felt like onboarding. Being available for every question felt like support. What it actually was is an operating path that never got written down, so every new hire had to borrow someone else’s week.

The cost is not the welcome lunch. It is a long ramp, copied habits from a broken process, and managers who cannot get back to their own work. Growth starts to feel expensive because the first 90 days never compound.

The tells are ordinary:

The Long Ramp
The hire is on payroll, and they still cannot see how work moves here, so useful output takes months instead of weeks.

The Pile of Logins
They got access to the stack, but not the workflow, so they know where to click and not what “done” looks like.

The Drain
Every question still interrupts the people who already know, which is how a new seat makes the current team heavier.

The Fix: Build the path from day one to productive

This is not a welcome packet. Write how work moves for one role, what they own, and where to look when they get stuck. Your job this week is not a warmer first day. It is making the next hire stop borrowing the team.

Something to consider today...

Pick one role you are likely to hire again, or the last person who is still ramping. Write the path they need for the first two weeks and put it where they will actually look. Let them use that path this week, and if they move a little slower than when you sat next to them, leave it.

Chet