The hiring is done, the contracts are signed, the office in Casablanca or Rabat is ready. Many executives breathe a sigh of relief: the hard part is supposedly over. It is the opposite. The hard part starts on the Monday the team arrives.
What you put in place during the first 30 days sets habits, standards and trust. After that you no longer correct: you either live with it or build on it.
The classic mistake: default onboarding
In a local team, onboarding happens by osmosis. You meet colleagues at the coffee machine, overhear decisions, and absorb context without anyone explaining it.
At a distance, none of that exists. If onboarding is not designed, it does not happen. New hires get access, a backlog, and are expected to deliver. They do what they can with what they understand, and nobody sees the gap for several weeks.
Week 1: context before tasks
The goal of week one is not to produce. It is to understand.
- The why of the business: who the customers are, how the company makes money, what really matters.
- The people: a simple map of who does what on the French side, with a named contact for each topic.
- Access: all of it, on day one. An engineer waiting ten days for an account has already learned something about your organization.
- A buddy: one person at headquarters, available, whose role is to answer the "silly" questions without judgment.
If possible, bring the team lead to Paris, or send a senior contact to Casablanca, for that week. A few days of physical presence are worth months of video calls.
Week 2: a first delivery, small and real
Give a real task, small in size, with a real user at the end. Not a training exercise.
The goal is twofold. The team experiences the full cycle: understand, build, ship, receive feedback. And you observe, without drama, how they ask questions, how they flag a blocker, how they react to criticism.
Set the definition of "done" now. This is when you align quality standards, before they drift apart.
Week 3: decision rights
This is the week most often skipped, and the one that costs the most later. Write down, in black and white:
- What the team decides on its own.
- What it decides after informing you.
- What requires prior approval.
Without this grid, everything escalates to Paris, the team becomes a queue, and the best people eventually leave. We covered the mechanism in an earlier article on who decides.
Week 4: the first review, in both directions
At the end of the first month, hold a two-way review.
- What you observed: strengths, gaps, surprises.
- What the team experienced: what was unclear, what was missing, what slowed them down.
The second direction is the one people forget. Yet it reveals the flaws in your setup, not in the team. A team that does not dare say the documentation is unusable will keep improvising for months.
Close with three concrete commitments from each side, with a date.
Rituals that last
Beyond the first month, three rituals are enough to keep the link alive.
- A short daily check-in, fifteen minutes, to unblock people, not to demand reports.
- A weekly delivery review, with users when possible.
- A monthly one-to-one with each member, led by the manager, not delegated.
Nothing sophisticated. Value comes from regularity, not from the tool.
What it changes
A designed onboarding does not cost more. It takes concentrated management time over four weeks, when it has the most effect. In return, you get a team that understands your business, knows its room to maneuver, and knows how to talk to you.
A subjected onboarding, by contrast, is paid for over months: misunderstandings, rework, disengagement, and eventually turnover.
Where to start
Before you sign your next hire in Morocco, write the 30-day plan. If you cannot describe it on one page, the setup is not ready.
This is part of the work we do with clients at Connectis Partners: preparing the team's arrival as much as its recruitment.