Read a sample: 1. Leadership When the Map Changes
The announcement arrives on a Tuesday morning. Your department will be reorganized, several teams will move under new leaders, and a revised operating model will be shared when it is ready. The message sounds confident about the direction and careful about the details. Your team reads it and immediately wants to know what it means for the work in front of them.
Will the project continue? Who will approve the next release? Are priorities changing? Will everyone still have a role?
You have some of the same questions. You may also know pieces of information you cannot yet share, or have heard possibilities that are not firm enough to repeat. Meanwhile, customers still need answers, deadlines still exist, and people are watching how you respond.
This is the difficult middle of organizational change: the old map no longer seems entirely reliable, but the new one is not finished. Leading in that middle does not require you to predict the final destination. It requires you to help people understand the ground beneath their feet, choose a useful next step, and notice when the conditions have changed.
That responsibility is both narrower and more substantial than having all the answers. You may not control the reorganization, its timing, or the decisions being made above you. You can still influence how your team experiences the uncertainty: whether people know what is expected today, whether concerns have a route to the right decision-maker, and whether a plan is adjusted when it stops making sense.
Uncertainty exists when relevant information is unavailable or an outcome has not yet been decided. A new reporting structure may genuinely be under discussion. A budget may be awaiting approval. Two departments may still be deciding which team will own a service. No amount of confidence from you can turn those open questions into settled facts.
Confusion is different. It arises when people lack clarity they could reasonably have. Team members may not know which work is still active, who can make a routine decision, where to raise a concern, or when they will hear from you again. Those gaps can often be reduced even while larger questions remain open.
Consider the difference between these messages:
> “Everything is up in the air. Keep doing your best, and I’ll let you know when I hear something.”
> “The final reporting structure has not been decided. For now, our customer commitments remain active, and I will continue to approve the work I normally approve. We’ll pause the proposed internal redesign until we understand whether it fits the new structure. Bring urgent conflicts to me, and I’ll update the team after Thursday’s leadership meeting, even if the answer is that those decisions are still open.”
Neither message resolves the reorganization. The second gives people a workable understanding of the present. It identifies what is unknown without allowing that uncertainty to spread into every decision.
Of course, a leader cannot remove all confusion. You may lack authority to settle an issue, or receive conflicting instructions yourself. The aim is not to produce a perfectly ordered environment. It is to locate the uncertainty accurately, clear up what you can, and make the remaining gaps visible.
A useful question is: What does my team need to know in order to work responsibly until the next decision? The answer will vary. Sometimes people need a priority order. Sometimes they need permission to stop a task. Sometimes they need to know that a difficult question has been heard and sent to someone who can answer it.
Imagine a hypothetical customer operations team led by Maya. The company has announced that customer operations and product support will be brought closer together. Senior leaders say the change is intended to improve the customer experience, but they have not yet announced the final team structure or assigned ownership for every process.
Maya’s team is midway through a project to improve how customer requests are routed. The work involves another department, and the next phase requires approval from a director whose future responsibilities are unclear. At the same time, the team must continue handling incoming customer issues.
Within a day of the announcement, several things happen. One employee stops working on the routing project because she assumes the new organization will replace it. Another continues as planned and asks the director for approval. A third hears that product support may take over some customer requests and begins redirecting questions there. A colleague in product support is surprised to receive them.
Each person is trying to act sensibly with incomplete information. The problem is that they are acting on different assumptions, and those assumptions are beginning to create real work for other people.
Maya cannot settle the organizational design. She can, however, create a temporary operating agreement. At the next team meeting, she says:
> “Here is what I know: customer operations and product support are expected to work more closely together. I do not yet know the final reporting lines or who will own the routing process. Until we hear otherwise, our team remains responsible for the customer issues we currently handle. Please don’t redirect requests to product support without agreeing on the handoff first. > > “For the routing project, continue the work needed to document the current process, but hold the proposed rollout. I’m checking who can approve the next phase and whether the project still fits the intended…