Onboarding in Two Weeks: A Map, Not a Legend
Show people the territory as it actually is, and autonomy arrives fast.
My record as a manager: someone reached full autonomy two weeks after joining the team. The other results are not far behind. As a rule, a newcomer in my teams understands how everything works within the first week and takes their place in the chain of processes — after that only the difficulty of the tasks grows. Other companies, I am told, budget a quarter for this, sometimes two. Here is how it works for me.
The foundation: the map equals the territory
Processes always exist in a company — even when nothing is written down anywhere. Work inside a team and between teams is always the same thing: receive an artifact at the input, process it, pass it on. Full stop. Everything else is nuance (which of course also has to be described, but the essence does not change).
People like to say the map is not the territory. And usually it is not: the rules describe one thing (if they describe anything at all) and something else happens in practice. People want to present their processes as better than they are — and that shoots them in the foot over the long run. But if you draw a person the factual map and break the journey through it into levels, onboarding goes quickly and easily.
The key is describing processes so you can move from the general to the specific and back again. Everything is stated concisely, point by point, with convenient navigation: the person keeps one link that answers every question.
Before meeting the team
Good onboarding starts before the first meeting. I talk with the person one on one first. A welcome and genuine pleasure that they joined — of course. But immediately after that come the simple rules:
- There are no stupid questions here. Every question counts.
- We do not play the hero.
- Nobody will judge you for a mistake, because there are no mistakes. There is experience.
- The rest of the principles are in the playbook.
Then I prepare the person to meet the team. I explain who is who: how long they have been here, what they are known for, what to watch out for. So it is not like school: you are the new kid, thirty unfamiliar faces are staring at you, and you have to run standup without embarrassing yourself.
The first meeting and the “magic” after it
At the meeting I introduce the person, they see the team for the first time and say a few words about themselves — standard stuff. And then I take the newcomer aside again, and the important part happens.
New people almost always worry about expectations: they are professionals, they have to perform from day one or they will be fired. I deliberately dismantle those expectations. The simplest tasks are selected, and it is said out loud: for a while, until you settle in, the tasks will be primitive. The goal is to immerse you in the processes without risk. Yes, just recolor a button. But the person will learn the workflow everything runs on.
Right there I also say that the tasks will get harder as they learn the rules of the game. That kills three birds with one stone:
- The person eases in smoothly.
- They close tasks successfully (the tasks are simple, after all), catch a solid dose of dopamine, and are ready to move mountains.
- They get to know adjacent teams — the tasks are picked so that some of them require contact with analytics, backend, and QA.
A map where everything is called by its real name
From the specific we move to the general: the person is shown that map. What the overall flow looks like — from the “left” edge (stakeholders) to the “right” one (stakeholders again). Which departments depend on whom, in what order the artifact is handed over, where the acceptance rules live, what to do if the artifact looks “off” — and in general if something has gone wrong.
The most important part: the boundaries of ownership are explained clearly. Where the newcomer’s responsibility begins and ends. Where their teammates’ begins, where adjacent departments’ begins. Who is formally responsible in other teams, and who actually decides and allocates the resources.
These look like obvious things — but this is exactly where the catch is. Beyond the mandatory part (“what you are supposed to do”), the person needs to be shown how the world around them actually works, not how the documents say it works. Which informal connections and agreements have formed, what is and is not done here, who is difficult, who is easy, who you can joke with and who you should not. Where to act head-on, and where politics begins — and whether it is worth getting into. Anyone who believes politics and backstage agreements do not exist will spend months pushing through something that one right conversation resolves.
A special case: “you do everything wrong here”
It happens — especially with experienced people — that someone is used to different rules and processes, and in the new place it seems to them that “everything is wrong.” At best they simply stall; at worst they try to impose their old rules everywhere. I have had these situations, and they were all resolved the same simple way: an honest conversation.
I explain that I would be genuinely glad — and I mean it — to hear how things were arranged elsewhere. I do not consider my system a gold standard, and surely everyone has something to contribute. But right after that I remind them of the simplest law of physics: every action has an equal and opposite reaction. And I politely ask: how ready are they, right now, in their second week, to shoulder the burden of going against the system and working through the resistance of everyone in it — their own team and every adjacent one?
Instead, we agree on something else. The person takes the position of an observer and, as onboarding goes on, shares their observations: which processes work suboptimally. Then the rules of the game are simple:
- If the person brings facts rather than emotions, we discuss it with the whole team. These are the people who will have to live with the new process if we adopt it.
- If the practical benefit is proven, the process changes. First as a pilot, and we say up front: while we are adjusting, some things may go clumsily — bear with it.
- Most importantly, the person signs up to own the rollout and the enforcement of the new rules.
That last point works as a filter. Sometimes a person soberly assessed their capacity and dropped the idea — they realized they had flared up. There have also been successful rollouts: with a solid evidence base, a professional is usually ready to take ownership.
Feedback: how I know onboarding is on track
The person is told immediately: at first my contact with them will be regular, but as soon as the questions thin out they move into open water. At the same time, the team and I are always ready to answer — without sarcasm or rolling eyes, see the rule about stupid questions.
My metric is simple: artifacts arrive on the expected date. If a task is perfectly prepared, estimated at “1 day,” and it is delivered roughly “tomorrow” — the person has understood everything. A few successful tasks like that, a few successful contacts with adjacent departments, and the newcomer is standing on their own feet, even if not yet confidently.
My bar: a month is the maximum for reaching full autonomy. In practice, when the rules of the game are explained and written down, a person already understands what is what within a week.
Instead of a conclusion
All of this consists of simple actions. Genuinely simple: you only have to be honest with yourself and with others, showing the map as it is. That is how a person reaches autonomy quickly. The rest is a matter of technique — you are hiring a professional, after all.