The fastest way for a new functional or operational leader to fail is to start changing the team before becoming part of it. The better sequence is simpler and harder: converge first, then evolve.
That distinction matters because not every leadership role has the same job to do. A general manager is responsible for the whole enterprise imperative, so the onboarding conversation can and should reset mission, vision, values, and priorities. Because leadership is nested culturally, strategically, operationally, tactically, a functional or operational leader has a different mandate: make the function or operation fit the enterprise, then improve the way the enterprise works across boundaries.
In practice, that means your first task is not transformation. It is integration. You need to understand how the overall team really works, where the friction lives, how decisions actually get made, and what other groups need from your function or area to win. By “functional” leader, I’m referring to the head of finance, HR, marketing, IT, etc. By “operational” leader, I’m referring to the head of a business unit or segment, geography or the like.
Become part of the system
Convergence is not passive assimilation. It is the disciplined work of learning the system before trying to improve it. New leaders often arrive with a plan and assume clarity will create momentum. More often, it creates resistance because the team has not yet decided whether the leader understands its reality.
The first phase of onboarding should therefore be about trust, observation, and alignment. Listen hard. Watch closely. Ask where work slows down. Identify who influences what. Learn the unwritten rules as well as the written ones. You can’t change something you can’t see. And once people see that you understand and respect the system, they are far more likely to support changing it.
Nest the imperative
A functional or operational leader’s team imperative must nest inside the enterprise imperative. That sounds obvious, but too many functions optimize for themselves in ways that create drag elsewhere. Finance tightens control. Sales wants speed. HR wants consistency. Manufacturing wants reliability. Each goal can be legitimate and still be misaligned if it does not help the larger whole.
The real test is whether your function makes other parts of the business better. A strong functional leader does not just run a better department. They improve enterprise throughput. They reduce friction at the seams. They make collaboration easier than avoidance.
That is why the pivot for a functional leader is usually not a new strategy. It is a new way of working.
While operational leaders may have their own sub-culture and strategy, those must nest within the overall enterprise’s culture and strategy in a way that works best with shared resources and makes the whole stronger than its parts.
Build the workshop around input
This is where the imperative workshop becomes powerful. The leader and direct team should define priorities, but they should not do so in isolation. Select representatives from adjacent functions or operational groups should be invited to provide input on what helps, what hurts, and what needs to change.
The point is not to create a shadow governance forum. It is to surface truth from people who live the consequences of the function or operational group’s decisions. These participants should not show up as peers with a vote. They should be informed contributors whose perspective helps the new leader understand where the function enables the business and where it slows it down and how the operational group links with others.
That distinction matters. If people think they are being asked to co-govern, politics enters the room. If they understand they are there to inform, the conversation gets more candid, more useful, and more actionable.
Shift the interface
Once convergence is achieved, the work shifts to evolution. For functional leaders, the biggest gains usually do not come from making the function internally better. They come from improving the interfaces between functions. Operating units must grow together.
That means revisiting decision rights, handoffs, escalation paths, and operating rhythms. It means measuring cycle time across teams, not just output inside one team. It means rewarding collaboration when collaboration improves the enterprise, not merely when it feels cooperative.
Early wins should reflect that logic. Faster approvals. Fewer surprises. Cleaner accountability. Better cross-functional communication, collaboration, and decisions. Those are the signals that the leader is not just running the function or operation well, but helping the business work better as a system.
The leadership test
The best functional and operating leaders do two things in sequence. First, they earn the right to belong. Then they earn the right to influence change. Skip the first step and the second will fail. Respect the sequence and the organization is far more likely to follow.
That is the real onboarding lesson for operational and functional leadership. Converge into the team. Nest the function or operation inside the enterprise imperative. Then improve the way the whole organization works together. The leader who gets that order right does more than succeed in a role. They make the entire enterprise stronger.
