Your Onboarding Is a Hazing Ritual and You Call It Agile

I recently watched someone start a new job at a large company. Two weeks in, the pattern was already obvious.

Week one: no structured training. No onboarding buddy. No ramp-up period. Just a Jira board, a Slack invite, and an implicit expectation to deliver. The task was assigned on day two. The deadline was next week.

That same week, the new hire's calendar filled with over 12 hours of meetings. Recurring syncs, sprint ceremonies, cross-team alignments, stakeholder updates. All mandatory. All two hours long. And because you're new, you can't zone out and do your actual work during them. You have to sit there, absorb context you don't yet have the framework to understand, nod along, and pretend you're learning.

So let's do the math. A 40-hour work week. Subtract 12+ hours of meetings. Subtract the context-switching tax. A UC Irvine study found it takes 23 minutes to refocus after an interruption. If you have four meetings scattered across a day, you don't have four gaps of productive time. You have four gaps of re-orientation time followed by maybe 20 minutes of real work before the next meeting pulls you out.

The new hire had maybe 15 hours of actual focused time that week. For a task that was supposed to take the full week. While learning a new codebase, new tools, new domain, new team norms, and new deployment processes. Simultaneously.

Nobody planned for this person to fail. But nobody planned for them to succeed, either. The system just assumed they'd figure it out, and if they didn't, well, probation exists for a reason.

The Sprint Review as Public Trial

At the end of the sprint, everyone presents what they accomplished. In a healthy team, this is a celebration of progress and an honest discussion of blockers. In this team, it was a performance review conducted in front of 20+ people.

The unspoken rule: if you didn't finish your work, everyone knows. The boss frames it as transparency. It felt more like a trial. Caktus Group's engineering blog put it well: public criticism brings on shame and humiliation, causes people to doubt themselves, and destroys confidence. It's also contagious. Once blame becomes normal, it spreads.

Now imagine you're two weeks into a new job. You're in probation. You didn't finish the task because you physically did not have enough hours. And now you're standing in front of two dozen people, expected to explain why. What are you going to say? "I spent 12 hours in meetings that I couldn't decline because I'm new"? You'd sound like you're making excuses. So you absorb the shame, work the weekend, and show up Monday pretending everything is fine.

Atlassian's own research found that 78% of workers say meeting overload makes it hard to get their work done, and 51% work overtime just to compensate. This isn't a personal failing. It's an arithmetic problem. But the sprint review doesn't care about arithmetic. It cares about output.

Same Sprint, Same Expectations

Whatever the reasoning was, the new hire got the same sprint workload as everyone else on the team. Week two. No adjusted expectations. No lighter first assignment to learn the ropes. Just a task, a deadline, and the same presentation slot at the end.

This is like handing someone a bicycle on their first day in a new city and saying "keep up with traffic." Sure, the bicycle works. But the person doesn't know the roads, the traffic patterns, the one-way streets, or where the potholes are. Asking them to move at the same speed as someone who's memorized the route isn't fairness. It's just lazy management that happens to look fair on a spreadsheet.

A reasonable ramp-up looks like this: month one, you learn. Month two, you contribute with support. Month three, you carry a normal load. That's not coddling. That's how you avoid the stat where 80% of undertrained new hires plan to quit, according to a Paychex survey of over 1,000 workers.

But ramp-up periods require someone to accept that a new hire will produce less in the short term. And in a culture where sprint output is public, that looks like a gap in the numbers.

The Probation Silence

Here's what makes the whole thing work. Probation.

Probation is supposed to protect the company from bad hires. In practice, it also protects bad management from feedback. When you're in probation, you can't push back on unreasonable meeting loads. You can't say "this deadline is impossible given my calendar." You can't flag that the onboarding process is nonexistent. You can't do any of that because every interaction is an audition, and complaining during an audition gets you cut.

So the new hire stays quiet. Works the weekend. Goes home exhausted. And the boss never hears that the system is broken because the one person experiencing the breakage is the one person who can't speak.

This is a feedback loop designed to produce silence. The company gets to maintain the illusion that the process works. The new hire gets to maintain the illusion that they're coping. And nobody fixes anything because nobody with power sees a problem.

What "High Performance" Actually Looks Like

I keep hearing companies describe cultures like this as "high performance." Fast-paced. Results-driven. No hand-holding.

But the Society for Human Resource Management found that 76% of organizations fail at onboarding. I looked this up because I wanted to know if what I saw was normal or exceptional. It's not exceptional. It's the default. Professor Miriam Posner went further and called the daily standup, as commonly practiced, an "exercise in surveillance." These aren't fringe critiques from people who hate work. This is mainstream workplace research.

High performance means giving someone the tools, context, and time to do excellent work, then holding them accountable for the result. What I described above skips straight to accountability. That's just hazing with a Jira board.

The Part That Gets Me

The new hire didn't complain. Didn't push back. Didn't flag the impossible math. Instead, they went to a cafe on Saturday, opened their laptop, and finished the sprint task on their own time. Unpaid. In their second week.

And on Monday, they'll present it at the sprint review as if it was completed during normal working hours. The boss will see a completed task and conclude that the system works. The workload was fair. The timeline was reasonable. The new hire is performing.

Nobody will ask what it actually cost to deliver that task.

That's the thing about these cultures. They don't look broken from the outside. The people inside them absorb the failure personally, convert it into unpaid weekend hours and quiet stress, and present a clean surface to the org. The metrics look fine. The burnout is invisible until it isn't.

When someone quits four months in, leadership will say "we thought they were doing great, they never said anything."

They were in probation. What were they supposed to say?