Read a sample: 1. Lead the Work Between Teams
The assignment sounded straightforward: improve the way the company brings new customers onto its software platform.
Maya, an operations manager, was asked to lead the initiative. Customer Support had heard repeated complaints about confusing setup instructions. Product wanted to reduce unnecessary steps. Sales wanted customers to begin using the platform quickly. Engineering was already committed to other work. No one disagreed that onboarding could be better.
At the first meeting, the group generated a long list of ideas. A week later, Maya sent a recap and asked for volunteers. Support offered to rewrite the instructions. Product suggested changes to the setup flow. Engineering asked for more detail before estimating anything. Sales wanted to know whether the changes would affect promises already made to customers.
Then progress slowed.
Maya had a deadline from her sponsor, but she did not manage the people whose work she needed. Each participant had a different understanding of what the initiative was supposed to accomplish. The group had discussed solutions before agreeing on the problem, and several decisions had been left with no clear owner.
This is a hypothetical case, but the situation is familiar. Cross-functional work rarely stalls because everyone has stopped caring. More often, the work becomes difficult in the space between teams: between one department’s request and another’s capacity, between a discussion and a decision, or between a promise and a handoff.
Leading in that space is a discipline. It requires you to make the work visible, connect people who hold different pieces of the answer, and help the right people make choices they can support. You may not control every resource, but you can influence how the initiative is understood and how its participants work together.
In a single team, a manager may be able to set priorities, assign work, and resolve disagreements within a defined area. Even there, authority has limits. Across departments, those limits become more apparent.
A cross-functional initiative might involve a project lead, functional managers, specialists, a sponsor, and people who will eventually use or support the result. Each person may have authority over a different part of the work. One person can explain a technical constraint but cannot approve additional capacity. Another can approve a policy change but does not know how that change will affect customers. A sponsor can resolve a priority conflict but may not know one exists until someone brings it forward.
That distribution is not necessarily a flaw. Organizations divide responsibilities for good reasons. Expertise develops within functions, managers coordinate the work of their teams, and important decisions often require review from more than one perspective.
The difficulty is that the initiative must still move as a whole. If nobody connects those separate areas of responsibility, reasonable local decisions can produce an unreasonable collective result.
In Maya’s case, Support could improve the instructions without changing the product. Product could propose a better setup flow without knowing whether Engineering had capacity to build it. Sales could communicate a faster onboarding experience without knowing whether the changes would be ready. Each action might make sense on its own. Together, they could create inconsistent expectations and more work for the people meant to benefit.
The cross-functional lead’s job is to notice those connections before they become expensive surprises.
That does not mean taking over every decision. It means asking questions such as:
- What outcome are we trying to achieve together?
- What must happen in one area before another area can move?
- Who can make this decision, and whose input is needed?
- What has each person actually agreed to do?
- What happens if the current plan is no longer feasible?
These questions may sound basic. They are also easy to skip when a project arrives with urgency and people are eager to show progress.
One of the most misleading moments in a shared initiative is the enthusiastic kickoff. People nod, offer ideas, and say they support the goal. The lead leaves feeling that alignment has been achieved.
Support for a broad goal matters, but it is not the same as a workable agreement. “Improve onboarding” can mean shorter setup time, fewer customer questions, better documentation, fewer errors, or a smoother handoff from Sales to Support. Those aims may reinforce one another, but they can also compete for attention and resources.
Even when people interpret the goal similarly, they may picture different levels of effort. A Support manager may believe the initiative calls for a review of existing instructions. A Product manager may expect a redesigned experience. An Engineering manager may assume the work will wait until the next planning cycle.
None of them is necessarily being difficult. They may simply be filling in the blanks from their own vantage points.
The lead’s task is to turn broad agreement into a shared understanding specific enough to guide action. That includes the intended outcome, the boundaries of the work, the decisions still open, and the contributions that need to be negotiated. You do not have to settle every detail immediately. You do have to distinguish what is known from what is assumed.
Maya could begin by saying:
> “We all want a better onboarding experience, but I think we may be picturing different changes. Before we assign more work, I’d like to agree on the customer problem we’re addressing and what would count as an improvement.”
That statement does not accuse anyone of misunderstanding.…