Connected Boxes on an Org Chart Don’t Make a Team
The new leadership team met every Monday morning.
Each leader provided an update.
Sales reviewed the pipeline. Operations discussed service levels. Finance covered performance against plan. Human Resources shared hiring and talent updates.
The agenda was full. The meeting was well organized. Everyone participated.
Then the leaders returned to their functions and continued managing their own work.
When an issue crossed functional boundaries, it required another meeting.
When priorities competed, each leader defended the commitments of their area.
When a decision affected several functions, it moved upward because no one was sure whether the team—or the individual executive—owned it.
On the organizational chart, the leaders were connected.
In practice, they were a collection of capable functional executives who happened to report to the same person.
The organization called them a leadership team.
They had never discussed what being a team required.
What the chart tells us
An organizational chart is useful.
It shows reporting relationships. It identifies formal authority. It helps people understand how functions and roles fit within the organization.
But the chart tells us very little about how work will actually happen.
It does not show how leaders will resolve competing priorities.
It does not explain whether a decision belongs to one executive, the team, or the person at the top.
It does not reveal which outcomes require genuine interdependence.
It does not define what leaders owe one another when the interests of their functions conflict with the needs of the enterprise.
The lines between boxes create structure.
They do not create shared understanding.
A group of leaders is not necessarily a leadership team
Most executive groups are filled with talented people.
Each leader brings expertise, experience, and accountability for an important part of the organization. Each has been selected because of an ability to lead.
But individual leadership capability does not automatically produce collective leadership capability.
A group can contain excellent leaders and still function poorly as a team.
The distinction becomes visible when work crosses boundaries.
A group of functional leaders asks:
“What does my function need to deliver?”
A leadership team must also ask:
“What do we need to accomplish together that none of our functions can accomplish alone?”
Those are not competing questions. Leaders remain accountable for their individual areas.
But when the second question is never answered, the team becomes a reporting forum rather than a collective leadership body.
Members share information.
They coordinate when necessary.
They escalate unresolved issues.
What they do not consistently do is lead the organization together.
Reporting relationships create membership, not alignment
When someone joins a leadership team, membership is immediate.
Alignment is not.
The new executive inherits a place on the chart, an agenda invitation, and responsibility for a function. They also bring assumptions formed through previous roles and organizations.
They may hold different beliefs about how quickly decisions should be made.
How much autonomy functions should have.
When disagreement should remain in the room and when it should be escalated.
Whether the team is primarily a place to share information, advise the leader, make collective decisions, or own enterprise outcomes.
None of these assumptions is necessarily unreasonable.
The problem is that they are rarely visible.
Everyone begins participating in the same meetings while operating from different ideas about what the team is for and how it should work.
The chart makes the team appear complete before the conversations required to build it have begun.
The work between the boxes
Leadership teams are often evaluated by what happens inside each function.
Did Sales reach its target?
Did Operations deliver?
Did Finance manage the budget?
Did Human Resources fill critical roles?
Those outcomes matter.
But many of the organization’s most important results are created between functions.
A new product succeeds through the combined work of Product, Sales, Marketing, Operations, Technology, and Finance.
Customer experience depends on promises and handoffs that cross organizational boundaries.
Strategic priorities compete for the same money, talent, time, and leadership attention.
No function can resolve those tensions independently.
The work between the boxes requires leaders to make choices together.
Which outcomes matter most?
Where does ownership sit?
Who can make which decisions?
What trade-offs will the organization accept?
How will leaders respond when commitments collide?
How will they surface and navigate tension?
Without shared answers, cross-functional work depends on individual relationships, informal influence, and repeated escalation.
The organization may still perform.
It simply requires more effort than it should.
Meetings do not create a team either
It is easy to assume that a group becomes a team through time together.
Weekly staff meetings.
Quarterly business reviews.
Annual planning sessions.
Executive offsites.
These gatherings can strengthen a team, but only if they contain the conversations the team actually needs.
A leadership group can meet every week for years without discussing its collective purpose.
It can review performance without agreeing on priorities.
It can debate decisions without clarifying decision authority.
It can talk about accountability without defining what members owe one another.
It can describe collaboration as important without addressing the tensions that make collaboration difficult.
Frequency creates familiarity.
It does not necessarily create alignment.
Teams are built through conversations
A leadership team becomes real through the shared understanding its members create.
That understanding develops when leaders discuss questions the organizational chart cannot answer:
Why does this team exist?
What must we accomplish together?
Which priorities take precedence when resources or commitments conflict?
What does each leader own, and where is ownership shared?
How will decisions be made?
How will we work together when pressure increases?
What will we do when we disagree?
These conversations do more than improve relationships.
They create an operating system for the team.
They allow leaders to act independently without pulling the organization in different directions. They reduce the need to renegotiate the same questions every time work crosses a boundary.
The objective is not agreement on everything.
It is shared understanding about how the team will lead together.
Structure is only the beginning
An organizational chart can bring the right people together.
That matters.
But proximity is not partnership. Reporting to the same leader is not a shared purpose. Attending the same meeting is not collective accountability.
Connected boxes describe a formal relationship.
A team is built through the conversations that give that relationship meaning.
Until those conversations happen, the organization may have a leadership structure.
It may not yet have a leadership team.
