Divisional structure: what it is and when to adopt it in your company

The answer changes with the size of the company and with how similar its business lines are to one another [1].

A divisional structure groups people not by function — sales, production, administration — but by product, geographic area or type of customer, giving each division its own internal functions and a separate income statement [1] [3].

The divisional structure is not a reward for growth, but the answer to a specific problem: a portfolio too varied for single shared functions. Introducing it too early costs more than it solves.

From the independent professional who assigns team members to very different projects, to the mid-sized company with plants in several regions, by way of the family business with two long-standing product lines: the question of when to separate responsibilities by business line comes up at different thresholds, but with the same underlying logic.

The next sections distinguish the divisional structure from a lever that is often confused with it, explain when it makes sense to adopt it, compare it with the functional and matrix models, and describe how to introduce it without halting operations.

Recognizing a divisional structure and telling it apart from a group of companies

Are splitting the business into several companies and splitting it into several divisions really the same move?

They are not: one concerns legal form, the other the logic by which people are organized — and confusing them leads to costly choices [2].

In the early 1920s, General Motors reorganized its business around brands and product lines under the leadership of Alfred Sloan, a case that business historian Alfred Chandler would later use to describe the birth of the divisional structure [2].

A company can have three separate legal entities with exactly the same functional organizational chart, or a single company organized into three autonomous divisions: these are different levers, often confused in family businesses.

In the classic description of the model, a division is a unit that brings together the functions needed to serve a market — product, geographic area or customer segment — and is accountable for its own financial result [1].

According to the Treccani encyclopedia, an organizational form is the stable arrangement of formal structure, lines of communication and authority, procedures and routines [3]: the divisional structure is one of the configurations that arrangement can take, not a legal form of company.

The boundary to draw is with the lever most often mistaken for it in smaller businesses: the corporate group.

Setting up several companies is a legal and tax choice — usually motivated by liability protection or generational succession — that says nothing about how people work; organizing into divisions is a management choice, which can be made even within a single company.

Reading the two levers as synonyms leads people to believe they have solved an organizational problem with a notarial deed.

For the full picture of the recurring models in companies, read also the guide to organizational models.

Recognizing a divisional structure therefore means looking at where the functions sit and which income statement they answer to, not at how many legal entities appear in the business register.

Understanding when to move from the functional to the divisional model

How many employees do you need before it makes sense to duplicate sales, production and administration for each business line?

There is no fixed threshold: the organizational literature ties it more to the variety of the portfolio than to headcount, although the two often go together [1] [2].

The divisional structure is not a reward for growth: it is the answer to a specific problem, when a portfolio that is too varied makes a single function inefficient.

In Italy, in industry and market services, the average company size was 4.0 employees in 2022, and companies with 10 to 249 employees made up 5.0 percent of the total [4]: there, the crossroads concerns a minority of companies, those whose portfolio has grown broad enough to put strain on shared functions.

Introducing divisions too early duplicates costs that a functional structure would absorb better; introducing them too late creates growing friction between those accountable for the product and those who control the central functions.

The signal to watch is not revenue, but how often the central functions find themselves arbitrating priorities between business lines competing for the same resources.

When production has to choose every week which order to bring forward, and the choice depends on who speaks loudest in the meeting rather than on an economic criterion, the coordination cost has already become measurable.

A second signal is the difficulty of answering the question "how much does this line really earn": if the margin by line can't be reconstructed, the single function is hiding information that would be useful to management.

The size thresholds discussed in the guide to business organization remain useful background references, but the operational criterion is still the heterogeneity of the portfolio: size accompanies the choice, but rarely determines it alone.

Comparing the divisional structure with the functional and matrix models

Is it better to stay centralized to contain costs, or to accept duplication to gain responsiveness?

There is no answer that holds for every industry: it depends on how much the business lines share customers, suppliers and processes [1].

Consider a manufacturing company with two product lines that differ widely in materials, end customers and sales cycles.

With a single functional structure, every decision on price or production priority involves the same people for both lines, who arbitrate conflicting priorities.

With a matrix structure, the same people report to two lines of command — product and function — with more coordination required.

With a divisional structure, each line gets its own sales and production team, at the cost of partial duplication.

A side-by-side comparison of the three models helps place the choice:

scroll the table →

The choice is not between one right model and two wrong ones, but between three different distributions of the same coordination cost: the functional model concentrates it in the central functions, the divisional model shifts it to resource allocation between divisions, the matrix model spreads it across the people who report to two bosses.

Weighing benefits and hidden costs before choosing the divisional structure

Is it worth paying for duplicated functions in order to have a separate income statement for each line?

It depends on what happens today when the lines share the same functions: if sharing generates only efficiency, the cost of dividing outweighs the benefit; if it generates priority conflicts, the opposite is true.

The main benefit of the divisional structure is clear accountability: each division answers for its own income statement, which speeds up operational decisions and makes it easier to identify which business line creates value [1].

The hidden cost is the duplication of functions that could remain shared — administration, purchasing, sometimes sales as well — with a proportionally heavier impact below a certain scale.

A second, less visible cost is the loss of part of the economies of scale and knowledge that arise when the same people work on several lines.

The most prudent way to weigh the two sides is to estimate the cost of replicating each candidate function, together with the time the central functions currently spend arbitrating priority conflicts.

The comparison moves the decision from the ground of impressions to that of orders of magnitude: as long as the cost of daily arbitration remains lower than the cost of duplication, the functional structure is still doing its job.

Introducing the divisional structure in your company without disrupting operations

Can you divide the structure without stopping production or losing customers during the transition?

Yes, but by following a precise order: first you isolate the income statement by line, then you assign people, and finally you formalize the division on paper.

Isolating cost and revenue items by line first makes the real cost of duplication visible before a single person is moved.

Only after validating the separate income statement does it make sense to assign key people to a single division, keeping shared the functions that do not yet justify duplication.

The four phases, in order:

1. Isolate the income statement by product line, reclassifying the costs and revenues already available in the accounts.

2. Assign key people to a division, starting with the sales and production roles closest to the market served.

3. Keep shared only the functions that cannot yet be duplicated to advantage, reviewing them at defined intervals.

4. Formalize the new structure on the organizational chart, so that reporting lines are readable by those who will use them every day.

For the last step, it pays to work with a tool that is already set up: the organizational chart makes explicit the responsibilities the reorganization has just shifted.

Order matters more than speed: starting from formalization instead of the numbers produces a new organizational chart on top of an operating logic that hasn't changed.

Avoiding the most common mistakes when adopting a divisional structure

What is the most costly mistake when introducing, or keeping, a divisional structure?

Almost never the choice of model itself: almost always the timing of its application, too early or too late relative to the real heterogeneity of the portfolio.

The first mistake is dividing for prestige, not out of necessity: companies that organize into divisions before they have a truly heterogeneous portfolio duplicate costs without gaining any speed.

The second is leaving ambiguous the boundaries between what stays centralized and what moves into the divisions, generating conflicts over who decides what.

The third is confusing organizational division with legal separation into companies, treating as equivalent two levers that follow different logics.

A fourth mistake, frequent in family businesses, is assigning divisions to people instead of markets, building the perimeter around whoever will lead it rather than around the customers to be served.

The fix is the same in all four cases: before moving people or rewriting the organizational chart, reconstruct the income statement by line and check whether the shared functions really generate measurable conflicts — without this step, the divisional structure risks formalizing a problem instead of solving it.

Limits and conditions of applicability

The organizational references cited in this article describe models and observed patterns, not guaranteed results in every business context.

The classic descriptions of the divisional model [1] [2] come from observing large industrial companies: transferring them to a much smaller company requires adapting the scale, not replicating the model.

The size thresholds mentioned are reference points, not activation criteria, which remain tied to the heterogeneity of the portfolio.

The ISTAT data on the size structure of Italian companies [4] describe the production system as a whole, not the situation of any single company.

In a very small business, separating income statements by line remains useful even without any reorganization of people.

FAQ

What is the difference between a functional structure and a divisional structure?

A functional structure groups people by the activity they perform; a divisional structure groups them by the market served — product, geographic area or type of customer — giving each division its own functions and a separate income statement [1].

At how many employees does it make sense to adopt a divisional structure?

There is no single threshold: the most solid criterion remains how much the business lines diverge in customers, processes and sales cycles, while size accompanies the choice without determining it alone [1].

Is creating several companies the same as having a divisional structure?

No: creating separate companies is a legal and tax choice, while the divisional structure concerns how people and decisions are grouped, even within a single company [3].

Operational summary

The divisional structure groups people by the market served rather than by function, giving each division its own internal functions and its own financial result.

The adoption criterion is not size but portfolio: it should be considered when shared functions start arbitrating conflicting priorities and the margin by line becomes hard to reconstruct.

Compared with the functional and matrix models, the choice is about deciding where to bear the cost of coordination, not eliminating it, and the benefits of clear accountability must be weighed against the duplication of functions.

The transition proceeds in four phases, from the income statement by line to formalization on the organizational chart, and the order of the phases matters more than their duration.

Conclusion

Dividing by product, geographic area or customer is not a symbolic milestone to reach as soon as the company grows.

It is an organizational response to a portfolio that a single function can no longer coordinate well, to be introduced when that coordination cost is already measurable — not to anticipate growth that has yet to arrive.

To compare the divisional structure with the other recurring organizational models, read also the guide to organizational models.

Once the structure has been chosen, the organizational chart is the tool for formalizing it and communicating it to those who will use it every day.

A company that has aligned its structure with its portfolio reaches decisions on pricing and production priorities without having to arbitrate each time between conflicting business lines: each division answers for its own numbers, and whoever leads the company can focus on allocating resources among the parts, not on daily arbitration between them.

Sources and references

[1] Mintzberg, H., "The Structuring of Organizations", Prentice-Hall, 1979.

[2] Chandler, A.D., "Strategy and Structure: Chapters in the History of the Industrial Enterprise", MIT Press, 1962.

[3] Treccani, "Organizzazione", Dizionario di Economia e Finanza, Istituto della Enciclopedia Italiana, 2012. Available at: https://www.treccani.it/enciclopedia/organizzazione_(Dizionario-di-Economia-e-Finanza)/

[4] ISTAT, "Annuario statistico italiano 2025 — Capitolo 14: Imprese", ISTAT, Rome, 2025 (2022 data). Available at: https://www.istat.it/storage/ASI/2025/capitoli/C14.pdf