Team Structures and Reporting Lines: Getting Them Right

How should teams be structured?

One of the most fundamental choices in structuring teams is whether to group people by their function, their area of specialty, or around the outcomes the organisation is trying to deliver. Functional grouping puts together people who do similar work, all the specialists of one kind in one team, which builds deep expertise and clear professional development within each specialty, and lets each function develop consistent standards and practices. The trade-off is that delivering an outcome usually requires several functions to coordinate, and when those functions sit in separate teams, that cross-functional coordination becomes harder, requiring deliberate effort to bridge the boundaries between specialties.

Grouping around outcomes takes the opposite approach, bringing together the different specialists needed to deliver a particular outcome into one team focused on that outcome. This makes coordination toward the outcome much easier, since the people who need to work together are together, and it gives the team clear ownership of delivering the result. The trade-off is that expertise becomes spread across outcome-focused teams rather than concentrated, which can make it harder to develop deep specialty expertise and maintain consistent professional standards across the organisation, as each specialist works somewhat in isolation from others of their kind.

Because both approaches have genuine advantages and drawbacks, the right choice depends on what matters most for the particular work, and many organisations use a mix. Where deep expertise and consistency within a specialty matter most, functional grouping serves better; where coordination toward outcomes and clear ownership of results matter most, outcome-focused grouping serves better. Some organisations organise primarily one way while using elements of the other, or apply different approaches in different parts of the organisation depending on what each part’s work requires. The key is to choose deliberately based on how the work actually needs to flow, rather than defaulting to one approach without considering whether it fits, since the grouping fundamentally shapes what coordinates easily and what struggles.

What is span of control and why does it matter?

Span of control refers to how many people report directly to a single manager, and it is a structural choice with significant consequences that organisations often get wrong by accident. A wide span of control, where a manager has many direct reports, keeps the organisation flatter with fewer management layers, which can speed decision-making and reduce hierarchy, but it risks overloading the manager, who may be unable to give each report adequate attention, support, and development. A narrow span, where each manager has few reports, allows closer attention to each person but creates more management layers, which can slow decisions, add cost, and distance the top of the organisation from the front line.

The right span of control depends on the nature of the work and the people involved, which is why a single rule applied everywhere tends to cause problems. Work that is complex, varied, or requires close management support warrants a narrower span, so that managers can give the necessary attention, while work that is more routine and performed by capable, self-directed people can support a wider span without the manager becoming a bottleneck or neglecting their reports. Setting spans appropriately for the actual work, rather than applying a uniform number or letting spans grow by accident, is what keeps managers able to manage effectively while avoiding unnecessary layers.

Span of control interacts with the overall shape of the organisation in ways that matter for how it functions. Many narrow spans produce a tall organisation with many layers between top and bottom, which can make the organisation slow, bureaucratic, and disconnected, while wide spans produce a flatter organisation that can be faster and more connected but risks under-managing people. Organisations that think deliberately about spans of control, setting them to match the work while being mindful of the overall number of layers they create, can shape an organisation that is neither overburdened with hierarchy nor stretched too thin, whereas those that ignore the issue often end up with structures that are accidentally too tall or with managers accidentally overloaded, both of which impair how the organisation works.

When does a matrix structure help, and when does it hurt?

A matrix structure is one in which people report to more than one manager along different dimensions, for example to both a functional manager who oversees their specialty and a manager responsible for a particular outcome or project to which they contribute. The appeal of the matrix is that it attempts to capture the benefits of both functional and outcome-based grouping at once: people retain a connection to their specialty and its expertise while also being directed toward the outcomes that need cross-functional work. For organisations that genuinely need both strong functional expertise and strong outcome coordination, the matrix offers a way to pursue both rather than sacrificing one for the other.

The cost of the matrix is the complexity and ambiguity that dual reporting introduces, which can be substantial and is frequently underestimated. When a person answers to two managers, the potential for conflicting priorities, mixed signals, and unclear accountability is real, and resolving the tensions that arise requires effort and goodwill that organisations do not always have. A poorly implemented matrix can leave people caught between competing demands, unsure who has authority over what, with accountability so diffuse that important things fall through the gaps. The very dual reporting that is meant to capture the benefits of both dimensions can instead produce confusion and frustration if it is not managed carefully.

Whether a matrix helps or hurts therefore depends heavily on whether the organisation genuinely needs it and implements it well. Organisations that face a real, ongoing need to balance functional expertise with outcome coordination, and that invest in making the dual reporting work, through clear agreements about decision rights, good communication between the managers involved, and a culture that can handle the inherent tensions, can benefit from a matrix. Organisations that adopt a matrix without a genuine need, or that fail to manage its complexity, often find it creates more problems than it solves. The matrix is a powerful but demanding structure, and the decision to use it should reflect both a real need for what it offers and a realistic commitment to handling the complexity it brings.

What ties good team structure together?

Across all these choices, the principle that matters most is clarity of accountability: whatever structure an organisation adopts, it must be clear who is responsible for what, who has authority to make which decisions, and how the parts are meant to work together. Structures fail most often not because the wrong grouping or span was chosen but because accountability is muddy, leaving people unsure what they own, decisions stuck because no one is clearly empowered to make them, and work falling between roles because everyone assumes someone else is responsible. A structure with clear accountability can work even if its other features are imperfect, while a structure with unclear accountability struggles regardless of how elegant it looks on the chart.

Good team structure also depends on matching the design to how the work genuinely needs to flow, rather than imposing a structure for its own sake. The purpose of structure is to enable the organisation’s work, so the test of any structure is whether it helps the work get done, helps the right people coordinate, and lets decisions be made well and quickly. Structures designed from this practical perspective, asking how the work needs to flow and arranging teams and reporting lines to support that flow, tend to work, while structures designed from abstract preferences or imported from elsewhere often fit the actual work poorly. Keeping the focus on enabling the real work is what keeps structural choices grounded.

Finally, good team structure requires the willingness to adjust as the work and the organisation change, since no structure stays right forever. The grouping, spans, and reporting lines that suit an organisation at one point can become misaligned as the work evolves, the organisation grows, or its strategy shifts, and organisations that revisit their team structures when problems emerge or circumstances change keep their structures serving the work. Those that treat structure as fixed accumulate the friction of an outdated design. Combining clarity of accountability, a structure matched to how the work actually flows, and the willingness to adjust as needed is what allows team structures and reporting lines to support the organisation effectively, which is the whole point of designing them deliberately rather than letting them happen by accident.

For leaders shaping their teams, the most reliable guide is to start from how the work genuinely needs to flow, who must coordinate with whom, where deep expertise matters, how decisions need to be made, and to design the grouping, spans, and reporting lines to support that flow, while keeping accountability unambiguous throughout. Combined with the willingness to adjust as the work and the organisation change, this practical, work-led approach to team structure is what allows the design to enable the organisation rather than impede it, which is the entire purpose of structuring teams and reporting lines deliberately.

Frequently Asked Questions

Frequently Asked Questions