o you know much about hermit crabs? In captivity, as they grow, their caretaker provides bigger shells and, when the crab is ready, it moves into a new one.
In the wild, this process is fascinating. When a larger shell becomes available, it creates a cascading set of transitions. Crabs line up beside the new shell in order of size. The largest crab moves into the empty shell, leaving its old one behind. The next crab moves into that one, and so on, down the line.
Biologists call this a vacancy chain, and a similar thing happens in organizations. A director retires, and a manager gets promoted to fill the role. A senior employee steps into management, and a new hire backfills the team. One transition triggers a chain reaction, and everyone must move into a bigger shell and learn to navigate the unfamiliar space.
The difference for people is that they are vulnerable for much longer. Instead of taking a few minutes to settle in, a manager will spend months feeling exposed as they get comfortable in a new role. During that time, every habit, every instinct, every pattern they built in the old role is on full display.
Initially, it isnโt a problem. Things work because the manager knows everything, responds quickly, and keeps the team running smoothly. But it doesnโt scale, and they quickly become a chokepoint. People wait for approvals that didnโt previously require waiting. Decisions that should take an hour now take a week. The manager feels overwhelmed, and the team feels micromanaged. The behavior hasnโt changed; itโs just been amplified into a larger space. And the harder they work to keep up, the more it magnifies the problem, and the longer theyโre exposed.
One complaint I often hear from managers scaling up is that their teams arenโt meeting the quality standards they expect or require. This happens during transitions. When they had a small team, they could keep expectations in their head and communicate them through daily interactions. A quick correction or an impromptu conversation would result in the improvement needed.
But as the team scales, the manager canโt always be there. With informal enforcement gone, quality drifts, and they canโt understand why, because the standards seem obvious to them. However, they werenโt obvious. They were just always present because the manager was involved in the details.
Conflict often grows during transitions as well. Managers are often mediators, resolving tension before it becomes visible. With a small team, this keeps things running smoothly and productively. When the manager moves up or takes on more responsibility, the small tensions that used to be handled quietly start to compound. By the time they notice, the problem has grown beyond a quick conversation.
These arenโt failures. Theyโre habits that didnโt scale. The transition didnโt cause the problem; it made the problem visible. The manager is the single point of decision-making, the unofficial quality control, and the unspoken standard-setter. What was manageable with six people becomes unmanageable with eighteen, and theyโre working harder than ever but falling further behind.
This is true whether the transition is a promotion, leading a rapidly growing team, or absorbing a new group after a reorganization. The dynamics are different, but the principle is the same: transitions donโt create leadership problems, they expose the ones that were already there.
Preparation starts with self-awareness. Managers must build a habit of honestly assessing themselves and their teams. There are practical tools managers can use to identify where their personal involvement is what makes things work. That will be a weak point during a transition.
For instance, I always find it curious when managers tell their employees to take a vacation and disconnect, but then they donโt do the same themselves. At some level, I understand. It can be easier to just work a little during vacation rather than prepare to be totally gone. But managers who do this are missing a golden opportunity. Fully checking out for a week and observing what happens upon return is one of the most revealing tests of readiness. I call it the Vacation Test. When a manager returns from vacation, I encourage them to notice what happened. How were decisions made? Where did quality slip? Who stepped up?
Distribute operational ownership. Managers can review their operational duties and start moving them to the team. For example, they can identify a standing meeting to move to a team member. They coach them on the intent and desired outcomes, give them freedom to adjust, and then set a date to stop attending.
The goal isnโt to hand off just a single meeting, though. Itโs about building a pattern where operational work runs through the team rather than the manager. They must be systematic about identifying other responsibilities to assign, providing support, and following good delegation principles. Each time a responsibility is successfully moved, the managerโs role shifts from operator to leader, and the teamโs capacity grows.
Start a playbook. This documents the recurring decisions, standards, and operating norms that currently live only in the managerโs head. It becomes a living record of how work gets done, how decisions get made, and what good looks like. When those things are written down, they become the teamโs standards, not just the managerโs preferences. A playbook allows new team members to onboard faster and enables existing team members to make decisions with confidence. When the transition comes, the playbook becomes the bridge between how the manager led and how the team continues to operate.
A playbook also forces clarity. The act of writing down โthis is how we handle Xโ often reveals that the standard was more vague than expected. That is the benefit of creating the playbook now. It means catching the gap early, while the team is small enough to course-correct, rather than discovering it after a transition, when the consequences are greater.
Both of these behaviors are investments that can start this week. Neither requires permission, a budget, or a reorganization. And they compound. A manager who practices distributing ownership and codifying standards for six months will find their role and their team structurally different. Theyโll be ready when the opportunity to move up arrives.
The managers who settle into their new shell and start succeeding in the new role arenโt the ones who figured it out during the move. They are the ones who built a foundation before the opening appeared. They distributed decisions, codified standards, and developed their teamโs capacity to operate without them in the room.
Transitions donโt create readiness; they expose it. The best way to prepare for a bigger shell is to outgrow the current one in the right way.