Insights
About us
Contact
Français English
My account

Insight Onboarding, integration and retention

A good welcome can mask poor integration

You can feel very well received and still spend a long time without understanding how to actually succeed in the work.

Mosaïca ConseilsAugust 18, 20264 min read

Two workers in orange safety coveralls talking on an industrial site, one handing a hard hat to the other.
The act of welcoming is visible. What is passed on with it — the expectations, the room to act, the way things get validated — far less so.

TWO DIFFERENT THINGS

Being well received and knowing how to work here are not the same thing.

A good welcome is measured in warm signs: someone comes to meet the person, introduces them, shows them around, leaves them a number to call. Those gestures matter, and an organization that skips them starts a long way back.

But they answer one question — “am I welcome here?” — and leave the other untouched: “how do you succeed here?” That second question concerns things no one thinks to say, because they are self-evident to people who have been living them for years.

The welcome answers a question of belonging. Integration answers a question of competence.

WHY THE FIRST MASKS THE SECOND

Warmth makes doubt feel impolite.

This is the most counter-intuitive mechanism in the whole question. The more generous the welcome, the harder it becomes to admit you do not understand. Saying “I don't know what's expected of me” to a team that has been impeccable feels like ingratitude, or like admitting incompetence.

So the person does what anyone would do: they observe, imitate, infer, and wait for things to become clear. From the outside, everything is fine. They are cheerful, present, well liked. The welcome indicators are excellent, and that is precisely what keeps anyone from seeing that integration is not moving forward.

The gap shows up later, and rarely under its real name: an error no one explains, an initiative never taken, a question asked six months too late, a departure no one saw coming.

WHAT HAS TO BE MADE EXPLICIT

The rules no one writes down are the ones that cost the most.

What is missing is almost never the job description. It is everything else: what you do when you are stuck, at what point you are disturbing someone, what gets decided alone and what gets validated, how you flag a problem without it sounding like a complaint, what work done well looks like as opposed to work that is merely acceptable.

Those rules exist in every organization. They are simply written down nowhere, because no one has needed to learn them recently.

Making them explicit does not mean writing a manual. Above all it means giving up a question that does not work — “is everything okay?”, which no one answers with a no — in favour of questions about situations: what the person would do in a given case, what they found most confusing this week, what they preferred not to ask. The answers then come without anyone having to admit anything.

What would this person do tomorrow if they got stuck and I wasn't there?

An organization that can answer that question has integrated someone. An organization that can only answer “she feels good here” has managed the welcome, and knows nothing more.