UPI Study › Courses › Principles of Management › Free lessons › Lesson 7.6 Free with a free account
When to Go Divisional: Scaling Through Separation
Principles of Management · Chapter 7: Designing the OrganizationSection 7.6 · lesson 38 of 11712 min · free with a free account
Free preview
Create a free account to keep watching
It takes a minute and costs nothing. Your free account unlocks all of Chapter 1 and 3 more lessons of Principles of Management.
Lesson complete
Earn the 3 college credits for Principles of Management
Enrolling adds a quiz after each lesson, the graded work and the official transcript. Recommended for credit by NCCRS.
Next lesson: Newer Structural Models: Matrix, Team, and Network Designs →← Traditional Structures: Simple, Functional, and Divisional FormsNext lesson: Newer Structural Models: Matrix, Team, and Network Designs →
In this lesson
The triggers, the management, and the costs of the move.
- Identify the conditions that point toward divisions
- Explain how divisions are managed and held accountable
- Compare the 4 bases of division and what each fragments
- Assess the costs an organization incurs in divisionalizing
Transcript
Everything said in the video, section by section (1,583 words). Read along, or search it.
Designing the Organization
When to Go Divisional: Scaling Through Separation
At some point, a growing organization faces a big structural question. Should it split into divisions? This section covers when that move is warranted, and how to read the case from symptoms. It compares the four bases of division, and what each one optimizes and fragments. It explains how divisions are held accountable, and the tension over their autonomy. And it names the five distinct costs, the role of the corporate center, and how to tell if the move worked.
Trigger Conditions
4 Signals That the Move Is Warranted
Four conditions typically indicate that a move to a divisional structure is warranted. The clearest trigger is product or market diversity, one that a functional structure can't serve with a single, coherent set of priorities. When different products or markets genuinely need different priorities, a single shared function struggles to serve them all at once. The second trigger is geographic spread that requires local responsiveness. Here, distance itself makes centrally coordinated decisions too slow, or too poorly informed, for local conditions. The third is scale that has made the functional bottleneck from Subchapter seven point five permanent. When that bottleneck stops being an occasional inconvenience, the organization has outgrown coordination through a single point of authority. The fourth is the need to develop general managers. An organization may realize it has no reliable path for building the broad, cross-functional judgment its future leaders will need. Running a division is precisely the kind of assignment that builds it.
Reading the Case
Symptoms, Not Stated Intention
In practice, the case for divisionalizing is better read from symptoms than from anyone's stated intention. That echoes the diagnostic principle Subchapter seven point three applied to strategy and structure misfit. Three symptoms recur reliably. The first is persistent cross-functional conflict, escalating upward. That's the same bottleneck pattern Subchapter seven point five's case vignette showed. The second is slow response to one market segment, while another segment is well served. That reveals a shared functional structure quietly favoring whichever segment fits its existing priorities best. The third is that no manager below the top is accountable for a whole result. Every result of consequence is jointly owned by several functional heads. And so, in truth, it's owned by none of them individually.
Table 7.6.1
The Basis Decides What Gets Fragmented
Once the move is warranted, the next choice is the basis of division. There are four: product, geography, customer, or channel. The basis determines what the new structure optimizes, and what it fragments. So choosing one isn't a neutral technical step. It decides which activities are grouped together as us, and which are split across divisions. That's the identification and cooperation effect from Subchapter seven point four. A product basis optimizes focus and accountability for one product line's full performance. It fragments a customer who buys across lines. It suits an organization with genuinely distinct products, needing different expertise. A geographic basis optimizes responsiveness to local markets and regulation. It fragments consistent practice and brand across regions. It suits an organization whose regions differ sharply in conditions or requirements. A customer basis optimizes service tailored to one segment, and fragments efficiency across segments that could otherwise share resources. A channel basis optimizes how a product reaches its market, whether retail, wholesale, or direct. It fragments the consistency of the product itself across the channels that sell it.
Drawing the Boundary
What Moves Into Divisions, What Stays Central
Deciding what goes inside a division, and what stays central, uses Subchapter seven point two's decision-mapping logic. The difference is that it's now applied division by division, rather than decision by decision. Some functions typically stay central. These are functions where consistency matters more than local responsiveness, and where economies of scale are large. Legal, treasury, and core financial reporting are common examples. Inconsistent practice in any of them carries real organizational risk. And each benefits a lot from being run once, at scale, rather than duplicated. Other functions typically move into divisions. These are functions where closeness to the division's specific product, market, or customer drives real performance. Sales and product engineering are common examples. Both depend heavily on information that sits inside the division, not at the center.
Managing Divisions
Making Whole-Outcome Accountability Measurable
Divisions are typically managed as profit centers, or as investment centers. A profit center is held accountable for revenue against cost. In other words, its own profitability. An investment center is held accountable for profitability relative to the capital invested in it. That's a broader standard. It also captures how efficiently the division uses the resources committed to it. Both models exist to make one benefit of divisions concrete and measurable: accountability for whole outcomes. Then there's transfer pricing. It arises when divisions trade with each other, and one division's output becomes another's input. The question is what internal price should govern that trade. It matters because the price splits profit between two divisions, on a transaction with no external sale at all. So a poorly set transfer price can distort each division's measured performance. And it does that without changing anything about the organization's actual overall result. These ideas are described conceptually here. The detailed mechanics of performance measurement come later in the course.
The Autonomy Question
Divisional Freedom Against Corporate Coherence
A standing tension runs through every divisionalized organization. It's the tension between divisional freedom and corporate coherence. The more autonomy a division holds, the more fully it can capture the responsiveness divisions are meant to provide. But the more autonomy it holds, the more it also risks drifting from the organization's overall direction. Subchapter seven point five named that risk divisional divergence. Both effects come from the same source, so you can't have one without some of the other. That's why this tension has no permanent resolution. It isn't solved once. It's managed continuously.
The Costs
5 Distinct Costs, Named Separately
Divisionalizing carries five distinct costs. It's worth naming them one by one, rather than treating them as a single, undifferentiated price. The first is duplication of functions. Engineering, sales, or other capability gets repeated in every division. The second, loss of scale economies, follows directly from that duplication. A function run once, at full scale, is generally more efficient than the same function run several times at smaller scale. The third is inconsistent practice. Each division, given real autonomy, develops its own way of doing things. The fourth is internal competition for resources. Divisions compete with one another for a shared pool of corporate capital, and corporate attention. The fifth is divisional optimization at corporate expense. That's the same local optimization problem from Subchapter five point four. A division can behave entirely rationally by its own measured standard, while the organization as a whole is worse off.
Figure 7.6.1
Harborline, Before and After
Figure seven point six point one shows a fictional company, Harborline Manufacturing, before and after divisionalizing by product. Before the move, it runs four functions once, for the whole company: engineering, sales, finance, and support. After the move, there are two product divisions. Engineering and sales now sit inside each division. So does support. Finance stays central, above both divisions. The point to notice is precisely which functions moved, and which stayed. And notice the duplication the move created. Engineering and sales now exist twice, once inside each division. Before, the company ran each of them only once.
The Corporate Center
Adding Value, or Only Adding Cost
What about the corporate center that remains above the divisions? It has a proper role, and that role genuinely adds value. It holds the functions where consistency and scale matter most. It sets the overall direction that divisions operate within. And it provides capability no single division could build as efficiently on its own. That means capital allocation, senior talent development, and shared infrastructure. The failure mode is a center that has drifted away from that role. It adds cost without adding value. It becomes layers of central review, reporting, and approval that slow the divisions down. And those layers don't actually improve the consistency or capability the center exists to provide.
After the Move
Hard to Reverse, and How to Judge It
Reversing a divisionalization is harder than making the original move. That means recombining divisions into a functional or more centralized structure. The reason is specific. Over time, divisionalizing builds three things. Duplicated capability, a distinct identity in each division, and separately developed practice. Unwinding all three means dismantling structures and relationships people have built careers and working habits around. It's not just redrawing a chart. The original move, by contrast, mostly adds structure, without removing anything already in place. So the two directions aren't equally difficult. How would you know the move worked? Look for what it was meant to buy. Better responsiveness to the diversity that triggered it, real accountability in each division's results, and a pipeline of general managers. Evidence that it hasn't worked mirrors the costs. Duplication without a coordination gain, divisions drifting from the overall direction, or a center adding cost the divisions resent.
Case Vignette
3 Divisions, 1 Confused Customer
Here is a composite case, constructed for instruction. Harborline Manufacturing divisionalized by product line, creating three separate divisions. Each had its own sales team, serving what leadership expected would be largely distinct sets of customers. But one large industrial customer bought products from all three divisions. It found itself receiving three separate sales visits, and three separate invoices. And it got three inconsistent answers to the same pricing question. Each division's sales team had no visibility into what the other two were doing with the same account. The product basis had done exactly what Table seven point six point one predicts. It optimized each division's focus on its own product line. And it fragmented the unified view of any customer who bought across more than one line. No individual division had made an error. The basis of division had fragmented a coherent customer relationship, something the structure was never designed to hold together.
About Principles of Management at UPI Study
Principles of Management (Business 101) is a self-paced online course of 117 video lessons in 17 chapters, from the classical schools and the four management functions to leadership, motivation, change, human resources, strategy and ethics. It carries a NCCRS credit recommendation for 3 semester credits.
Every lesson transcript is free on pages like this one, and the videos are free with a free UPI Study account. Enrolling adds a practice quiz after each lesson, the graded work and final exam that earn the credit, lifetime access, and an official transcript on completion. UPI Study has helped over 130,000 students with college credits. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.
Enroll now → Course details Download the syllabus Every course with PRO →
Why take it here
Why students take Principles of Management with UPI Study
Where the credit goes
Universities that work with NCCRS
Principles of Management carries a NCCRS credit recommendation. These universities work with NCCRS; some are UPI Study's signed partners. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.
Thomas Edison State UniversitySigned partner
University of the PeopleSigned partner
Charter Oak State CollegeSigned partner
Strayer UniversitySigned partner
Columbia Southern UniversitySigned partner
Indiana TechSigned partner
Penn StateWorks with NCCRS
Southern New Hampshire UniversityWorks with NCCRS
SUNYWorks with NCCRS
+many more cooperating universitiesFind my college →Find my college → Not listed? Ask Athena in the corner of this page, or book a 15-minute call.
FAQ
Questions students ask us
About When to Go Divisional: Scaling Through Separation
When should a company switch to a divisional structure?
What are the bases for creating divisions in an organization?
What is the difference between a profit center and an investment center?
What are the costs of a divisional structure?
About the Principles of Management course
How many college credits is Principles of Management?
How much does Principles of Management cost and what is included?
Which universities accept UPI Study credits?
How long does Principles of Management take?
How are the exams done?
How do my credits reach my college?
Ready for the full course? Earn 3 credits in Principles of Management.
117 video lessons, a quiz after each one, and the graded work that earns the credit. Recommended for credit by NCCRS.
3 credits · NCCRSEnroll →