UPI Study › Courses › Leadership and Organizational Behavior › Free lessons › Lesson 14.6 Free with a free account
Case Study: Structural Redesign and Innovation in the Consumer Products Industry
Leadership and Organizational Behavior · Chapter 14: Organizational Structure, Design, and Behavioral ImplicationsSection 14.6 · lesson 86 of 12211 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 Leadership and Organizational Behavior.
Lesson complete
Earn the 3 college credits for Leadership and Organizational Behavior
Enrolling adds a quiz after each lesson, the graded work and the official transcript. Recommended for credit by NCCRS.
Next lesson: Evaluating Structural Effectiveness and Aligning Design With Organizational Goals →← E-Business Organizational Forms, Behavioral Implications, and Staff ControlNext lesson: Evaluating Structural Effectiveness and Aligning Design With Organizational Goals →
In this lesson
A structure that was excellent for one era became the obstacle in the next.
- Diagnose slowing launches in terms of strategy-structure fit
- Explain why a matrix was layered on rather than swapped in
- Name the practices that made dual authority workable
- Convert one case into a repeatable diagnostic template
Free study notes
Get this lesson's notes by email
The key points and 4 practice questions with answers, in your inbox. One email, free.
One email. Unsubscribe in one click.
Transcript
Everything said in the video, section by section (1,527 words). Read along, or search it.
Organizational Structure, Design, and Behavioral Implications
Case Study: Structural Redesign and Innovation in the Consumer Products Industry
This case study is a fictional one, but the pattern in it is entirely real. A company runs a structure that works beautifully for decades. Then the environment changes, and the very same structure becomes its biggest obstacle. Nothing about the original design was wrong. The world moved. Watch for four things as the story unfolds. How the leaders diagnosed the problem, using concepts from earlier in this chapter. Why they layered a new structure on rather than replacing the old one. What specific practices made dual authority survivable. And how they handled the human reaction, which was where the change could most easily have died. At the end we turn all of it into a template you can apply to any organization.
The Situation
Northbrook Household Goods
Northbrook Household Goods is a fictional mid-sized manufacturer. It makes cleaning, kitchen, and personal-care products, sold through retailers across several regions. For decades it ran a classic functional structure. Large central departments for research, manufacturing, marketing, and sales. And each of those departments served every single product line. You already know what that design buys, from earlier in this chapter. It builds deep expertise, and it captures economies of scale. And for years it genuinely served Northbrook well. The market was slow-moving, and annual product refreshes were the norm. Hold on to this before we go further. Nothing about the design was wrong. The market was simply patient, and the structure was well matched to a patient market.
The Shift
When the Environment Stopped Cooperating
Then the environment stopped cooperating, in four distinct ways. Smaller, nimbler rivals began launching novel products in months rather than years. Those products often targeted narrow consumer niches. Niches that Northbrook's broad functional machine struggled even to see. Retail partners started demanding faster customization. And consumers increasingly discovered products through digital channels. Channels that rewarded speed and distinctiveness above all else. Meanwhile Northbrook's launches crawled through sequential functional hand-offs. Research finished, then handed to manufacturing, then to marketing, then to sales. Each unit optimized its own piece of the chain. And no single owner was accountable for a product's whole journey. So time-to-market lengthened, at exactly the moment the market demanded the opposite.
The Diagnosis
Four Chapter Concepts, Applied
Northbrook's leaders diagnosed this using four ideas from earlier in the chapter. First, a classic strategy-structure mismatch. A new strategy of fast, niche-focused innovation sat on top of an old functional design. A design that had been built for slow, broad efficiency. Second, the coordination weakness inherent in functional grouping. Cross-functional work stalls at hand-offs, which is exactly what the launches were doing. Third, the mechanistic-organic continuum. Their highly mechanistic form was wrong for an environment that had become turbulent. Fourth, the contemporary lateral designs, weighed against each other. Team-based and matrix approaches could pull functions together around products. And could do so without dismantling the expertise those departments had accumulated. The core diagnosis is worth stating carefully. The structure was not broken. It was misaligned.
The Redesign
A Matrix Layered On, Not Swapped In
So what did they actually build? Rather than scrap the functional departments, they layered cross-functional product teams on top. That creates a matrix, which is precisely what it sounds like. Each priority product line gained a dedicated team. Drawn from research, manufacturing, marketing, and sales. Each team was led by a product leader accountable for that line's full results. Meanwhile the functional managers kept something real. They retained responsibility for developing expertise and standards. Product leaders directed the day-to-day work of getting specific products to market. Now recall the four supports a matrix needs, from the earlier section. Leadership invested early in explicit priority rules, and in regular conflict forums. And in shared metrics, so both axes were judged partly on launch success.
The Rollout
Why Piloting Beat a Big Bang
The rollout is the part most worth copying. The move unfolded over roughly two years, and the sequence mattered as much as the design. Leadership resisted the temptation to flip the entire organization at once. Instead they chose three high-priority product lines as pilots. Everything else stayed in its familiar functional form. The three were chosen partly because they faced the most acute speed pressure. Success there would be the most visible, and therefore the most persuasive. The pilot approach contained the disruption. It let the model be refined before any wider rollout. And as the pilots delivered faster launches without sacrificing quality, confidence grew. The matrix then extended to additional lines in waves, each learning from the last. Consider the alternative. One failed big-bang restructuring can poison an organization for years.
The Resistance
Two Predictable Human Reactions
The transition was not smooth, and the friction came from two directions. Functional managers experienced the change as a loss of control. Their specialists would now take daily direction from product leaders. And some feared a loss of status and relevance along with it. Frontline specialists experienced something different. Confusion, and stress. They suddenly had two bosses with potentially competing demands. It was unclear whose direction took precedence when the two disagreed. Now, here is the move that mattered most. Both reactions were entirely predictable, given what the change actually did to each group. Northbrook's leaders treated them as legitimate rather than as obstinacy to be overridden. That framing is not a nicety. It is what made an effective response possible at all.
The Response
How Each Reaction Was Answered
Each reaction got a specific response, rather than a general appeal to get on board. Functional managers felt a loss of control and status. So leadership reframed their role as expertise development, and said clearly it was still essential. Their role was evolving, not disappearing, and that distinction was communicated repeatedly. Specialists were confused by having two bosses. So they got clear guidance on handling competing demands, and forums to raise conflicts. Rather than absorbing those conflicts silently, which is what usually happens. Senior leaders faced the risk of a half-hearted change. So they gave visible, consistent support. That signaled the matrix was a settled direction, not an experiment that might be abandoned. And the whole organization doubted the new model, so early wins were used as proof.
The Outcome
What Changed by the End
What actually changed by the end? As trust in the new arrangement grew, cross-unit launches accelerated markedly. The group regained ground against its nimbler rivals. And crucially, it preserved the deep functional expertise that remained a genuine advantage. The functional departments themselves adapted. They moved from directing daily work to developing expertise and standards. By the end of the transition, the matrix covered all major product lines. The supporting practices had been strengthened with each successive wave. Now for the most interesting part of the outcome. The dual-authority tension did not disappear. It changed character. What had caused early confusion became a manageable source of debate. Healthy debate, between functional priorities and product priorities.
Lessons
Five Transferable Conclusions
Five lessons transfer out of this case. First, restructuring should follow a clear diagnosis of misalignment. Not a fashion for any particular design, however impressive it sounds. Second, adding lateral coordination need not mean destroying valuable vertical expertise. A matrix can preserve both, which is the whole reason to choose one. Third, dual-authority tension is manageable, but only with deliberate investment. Priority rules, conflict forums, and shared metrics are not optional extras. Fourth, structural change is as much a behavioral and emotional transition as a technical one. Fifth, structure must keep pace with environment. A design that fit perfectly in a stable era can quietly become the chief obstacle to success. The deepest lesson is the surgical one. Add what is missing, and keep what works. Most structural problems are specific weaknesses to remedy, not total failures to sweep away.
The Pattern
One Case, Many Applications
The value of this case is not its industry. It is its pattern. A hospital, a software firm, or a public agency could be substituted with the arc intact. The trigger was faster, more varied demand. The portable principle is that strategy outpaces structure. The symptom was slow cross-unit decisions. The principle is that friction signals misalignment. The diagnosis was functional silos against a new strategy. The principle is simply this. Locate the structural gap before you touch anything. The redesign was a lateral overlay on the existing functions. The principle is to add coordination while keeping the strengths you already have. What makes these lessons portable is that they concern relationships rather than specifics. The relationship between strategy and structure. Between a structural gap and the symptoms it produces. And between a redesign and the human transition it requires.
Your Turn
A Template for Diagnosing Any Organization
Turn all of that into a template you can run on any organization. Begin by asking what the current strategy actually demands. Speed, consistency, innovation, responsiveness, or some particular mix of them. Then ask what the current structure is built to deliver. Read its degree of formalization, its basis of grouping, and its coordination mechanisms. Where the demands and the delivery diverge is where misalignment lives. And the size of that divergence tells you whether a targeted fix or a deeper redesign is warranted. Next, ask what minimal change would close the gap while preserving genuine strengths. Exactly as Northbrook preserved the functional expertise it still needed. Finally, ask how the human transition will be managed. Who will resist and why, how the rationale gets communicated, what early wins build confidence. Because structural change is never purely technical, and this is where sound designs go to die.
About Leadership and Organizational Behavior at UPI Study
Leadership and Organizational Behavior (Business 206) is a self-paced online course of 122 video lessons in 20 chapters, from personality, perception and motivation to leadership and power, teams, decision-making, conflict, organizational structure, culture, ethics and change. 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 All Business courses Every course with PRO →
Compare: Management and leadership courses · Foundations of Leadership vs Leadership and OB
Why take it here
Why students take Leadership and Organizational Behavior with UPI Study
Where the credit goes
Universities that work with NCCRS
Leadership and Organizational Behavior 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 Case Study: Structural Redesign and Innovation in the Consumer Products Industry
How do you diagnose a mismatch between an organization's strategy and its structure?
Why would a company add cross-functional product teams instead of replacing its functional departments?
Why should a major restructuring start with a pilot?
How should leaders handle resistance when moving to a matrix structure?
About the Leadership and Organizational Behavior course
How many college credits is Leadership and Organizational Behavior?
How much does Leadership and Organizational Behavior cost and what is included?
Which universities accept UPI Study credits?
How long does Leadership and Organizational Behavior take?
How are the exams done?
How do my credits reach my college?
Ready for the full course? Earn 3 credits in Leadership and Organizational Behavior.
122 video lessons, a quiz after each one, and the graded work that earns the credit. Recommended for credit by NCCRS.
3 credits · NCCRSEnroll →