Onboarding is a feedback loop for organizational health

At one company, every planning meeting ran an hour over. I noticed by my second week and asked somebody about it.

"Oh, that's just how it is here," they said.

They sounded as though the meetings were weather. To me, still new enough to be irritated, they looked like a sign that priorities were unclear and nobody could close a decision.

That gap has stayed with me. A new hire notices the things everybody else has learned to step around.

The interview ends, the evidence begins

I wrote about codebase-first interviews a while ago. Letting candidates work with your real code reveals more than a whiteboard puzzle, and I still believe in it.

Even an honest interview can't show how the company behaves every day. Candidates don't see who can make a decision, what happens when somebody disagrees with leadership, or which recurring problem has become "just how it is here." Interviews are polished by design. Onboarding removes the polish.

I felt that more sharply in a job where my first three weeks were spent waiting for decisions. My manager needed approval from their manager, who needed alignment with a peer, who was away until the following month. By week four, I was already wondering whether I'd made a mistake in joining.

Nobody needed to explain the leadership problem to me. The holding pattern did it for them.

New people notice the promise-reality gap

In the 2/3 pattern, I describe organizations in terms of leadership, strategy and team health. The weak part is often hard to hide from somebody who has just arrived.

Unclear ownership shows up as unresolved meetings. A drifting strategy appears when each person gives a different answer to "What are we building?" A struggling team can look friendly at first, until somebody offers the direct feedback promised in the culture deck and gets punished for it.

A friend joined a startup that sold candidates on its amazing culture. Within two weeks, she'd learned that the local meaning of "amazing culture" included not disagreeing with the founder. She then watched another new hire get criticized publicly for challenging a technical decision. She left after three months.

By the time somebody resigns, leaders sometimes say, "They never raised any concerns." Often the concern was there in an early one-on-one, a retrospective, or a casual conversation. Nobody followed up, so the new hire learned something else about the company: raising the issue wouldn't change it.

An exit interview is late confirmation of a conclusion they may have reached months earlier.

Ask while the observations are still fresh

I've started treating the first month as a source of feedback about the organization, alongside the usual work of helping somebody become productive.

The questions can be simple:

• What surprised you?
• What feels different from the interview?
• What has been harder than it should be?

The important part comes after the conversation. If several new hires mention the same problem and nothing happens, the check-in becomes another piece of onboarding theater. People quickly learn to give a polite answer.

You won't be able to fix every observation. Some things need context, and sometimes the new person has only seen part of the picture. You can still explain what you're keeping, what you're changing, and why. That response tells them their perspective entered a real decision.

Think back to your first month in your current job. What did you notice before somebody taught you to stop noticing it?