SKU rationalization is rarely defeated by weak analysis. It is more often defeated by human behavior. A company may prove that the portfolio is too large, that the tail is costly, and that customers can be moved toward simpler offers with limited loss. Even so, the effort can still slow because people protect familiar products, functions defend their own priorities, and exceptions begin to spread faster than decisions can be implemented.
This chapter addresses that reality. It explains why rationalization efforts stall, how to manage change across functions that experience the portfolio differently, how to deal with politics and legacy commitments, and how to build a culture in which disciplined portfolio management becomes part of normal leadership rather than an occasional cleanup exercise. In most companies, the analysis shows that change is needed. Leadership determines whether the organization actually follows through.
22.1 Why SKU Rationalization Efforts Often Stall
Most SKU rationalization efforts do not fail in one dramatic moment. They erode. Meetings become less decisive, difficult items are deferred, and the organization starts saying that more analysis is needed before action can continue. The program still exists, but it begins to lose force.
Stall pattern: the set of behaviors that slows or neutralizes a rationalization effort after the business has already shown that simplification is justified. The most common cause is fear of revenue loss. Commercial teams live closest to customer reactions, so they often imagine the worst case even when substitution analysis is strong. This is not irrational. Sales is usually judged on revenue and account retention, not on system-wide complexity cost. If leadership does not address that incentive gap, commercial resistance will surface as endless caution.
A second cause is asymmetry of visibility. The revenue of a SKU is obvious and easy to name. The cost of complexity is dispersed across planning, setup loss, inventory, write-offs, working capital, data maintenance, and operational distraction. Because those costs are spread across functions, no one feels them as sharply as a sales leader feels the possible loss of one account. The result is a predictable bias toward keeping the item.
A third cause is decision fatigue. Portfolio reviews can become draining because many items are ambiguous and many stakeholders have opinions. If the process is too slow or too detailed, the business begins to conserve energy by postponing the harder cases. A company that debates every SKU from first principles will eventually stop deciding and start drifting.
Lack of visible sponsorship also causes stall. Rationalization usually asks some groups to give up options they previously controlled. If the executive team is not visibly aligned and willing to hold the line when resistance appears, middle managers quickly conclude that the program is negotiable.
There is also an emotional dimension. Some SKUs are tied to earlier wins, famous launches, or strong personal attachments. People do not simply protect the item. They protect what it represents. Finally, many efforts slow because the business underestimates the burden of change itself. If the destination looks right but the implementation path feels chaotic, resistance rises. Inertia is not passive. It is produced by incentives, uncertainty, and organizational memory.
22.2 Change Management for Cross-Functional Adoption
SKU rationalization crosses too many functions to be managed as a simple announcement. Sales sees the customer relationship. Operations see variability and burden. Finance sees economics and value capture. Product teams see range architecture and innovation logic. Each function interacts with the same portfolio through a different lens, which means each one experiences the change differently.
Cross-functional adoption: the process by which multiple parts of the business accept, support, and begin acting in line with the future-state portfolio. Agreement in principle is not enough. A function can say it supports simplification while continuing to behave as though the old assortment still exists. Sales can keep offering discontinued items. Planning can keep forecasting them. Customer service can keep escalating cases that should already have a clear answer. The test of adoption is behavior.
The first requirement is a shared case for change that speaks to all functions. It should not be framed as a purely financial exercise, because finance language alone will not mobilize commercial or operational teams. Nor should it be framed only as an operations cleanup, because that will sound local rather than strategic. The strongest case combines growth, service, efficiency, and focus. It explains that the portfolio has become harder to sell, harder to make, harder to stock, and harder to manage than necessary, and that simplification will allow the company to invest more effectively in the products customers truly value.
The second requirement is functional translation. People rarely resist change because they misunderstand a broad corporate message. They resist because they do not know what that message means for their own choices. Sales needs to know how customer relationships will be protected. Operations needs to know how cutovers, final runs, and inventory depletion will be managed. Finance needs to know how benefits and one-time costs will be tracked. Product and marketing teams need to know how innovation will continue without reopening the gates to uncontrolled proliferation.
It also helps to create a visible coalition of leaders rather than leaving one sponsor to carry the message alone. When one function is seen as owning rationalization, others often treat it as that function’s agenda. A cross-functional coalition changes the signal. It shows that simplification is not a local preference but a shared leadership choice.
Adoption improves when people can see how the new portfolio will work, not just why the old one is flawed. Future-state assortment maps, sample account conversations, revised size ladders, and cleaner configuration menus make simplification concrete. Local managers matter as much as senior leaders because most employees take their cues from the person who runs their team, plant, region, or category. If those managers are unconvinced or poorly briefed, adoption will remain weak.
Finally, change must be reinforced visibly. Early wins need to be communicated, violations of the new discipline need to be challenged, and measures need to show that the company is observing the new behaviors. Cross-functional adoption becomes durable when people see that simplification is now part of normal performance, not a temporary project layered on top of real work.
22.3 Handling Politics, Sacred Cows, and Legacy Decisions
Every portfolio contains items that survive for reasons far beyond their economics. Some are protected because a senior leader likes them. Some are associated with a famous past win. Some belong to a brand story that people are reluctant to question. Others persist because discontinuing them would mean admitting that an earlier decision no longer makes sense. Once the business reaches these items, the debate is no longer just about volume, margin, and substitution. It becomes a debate about status, history, and influence.
Sacred cow: a SKU, brand extension, customer-specific variant, or product family that receives unusual protection because of politics, symbolism, or institutional habit rather than because of a current and explicit business case. Sacred cows are dangerous not only because they stay in the portfolio. They teach the organization that some complexity is immune to evidence.
The first discipline in handling politics is to make the argument explicit. Many companies allow political protection to remain informal. A leader raises concern, others sense the sensitivity, and the item quietly leaves the agenda without being tested. A better approach requires every defended item to have a stated rationale, such as customer dependence, brand role, contractual necessity, or installed-base support. Even if the rationale is strategic rather than numerical, it should still be named and examined.
The second discipline is to separate reverence from relevance. A SKU may once have mattered greatly and still no longer deserve its current form. A brand may still require a signal of breadth or innovation, but not the exact item people are protecting. A customer relationship may still matter, but the account may now accept a substitute. Leaders should not ask “Did this matter?” but “What role must still be served, and is this the best way to serve it now?” That question weakens nostalgia as a defense while preserving legitimate strategic needs.
Legacy decisions require special treatment because many low-value SKUs exist not because anyone would add them today, but because no one has created a moment to revisit them. Good change leadership treats this as a normal consequence of time rather than as proof that earlier decisions were foolish. The portfolio should be reviewed against current realities, not permanent assumptions.
Political issues also need the right forum. They should not dominate routine working sessions. If a case involves a major strategic customer, a visible brand symbol, or a senior executive’s long-standing preference, it should be elevated quickly into a smaller forum with clear decision rights. This protects the main process from being consumed by a few emotionally charged cases while still treating sensitive issues seriously.
One of the most effective ways to neutralize politics is to use principles publicly and consistently. If leaders preserve a sacred cow, they should say why and under what condition. If they remove one, they should explain that the same decision rules apply to everyone. Over time, that consistency changes the culture and reduces the power of informal influence.
22.4 Creating a Culture of Disciplined Portfolio Management
The final goal of change leadership is not to finish one rationalization wave. It is to make disciplined portfolio management feel normal. A company with that culture does not need to rediscover every few years that it has too many SKUs. It sees complexity early, questions it routinely, and treats portfolio decisions as part of responsible management.
Disciplined portfolio culture: an environment in which people are expected to justify new complexity, review old complexity, and make assortment decisions with both customer value and operational consequence in mind. This culture is not created by slogans. It is created by repeated leadership behavior, reinforced systems, and a shared language for talking about complexity.
The first element is transparency. People need visibility into the shape of the portfolio, the size of the tail, the burden of low-value variants, and the results of simplification. When the portfolio is opaque, complexity feels free. When it is visible, managers begin to understand that every SKU has consequences beyond its own sales line. Transparency also makes it easier to spot early warning signs before the portfolio drifts back into clutter.
The second element is reciprocity between addition and removal. In a disciplined culture, new items do not simply arrive because an opportunity exists. Teams are expected to explain what the item will add, what complexity it will create, and what will be simplified elsewhere if necessary. This shifts the tone of portfolio management from enthusiastic accumulation to intentional design.
The third element is normalizing exit. Many companies celebrate launches and hide retirements, as though discontinuation were an embarrassing sign of failure. That attitude guarantees sprawl. Mature portfolio cultures treat exit as a healthy part of managing relevance. Products should leave when they no longer earn their place, when better substitutes exist, or when the business can serve the need more cleanly in another way.
The fourth element is learning. Every rationalization effort teaches the company something about customer transfer, internal resistance, communication, and implementation risk. Those lessons should be absorbed into standard practice. If certain objections prove smaller than feared, future waves can move faster. If certain account types needed more support, those requirements should become part of the playbook.
The final element is a leadership example. Employees notice whether senior leaders ask hard questions about new complexity, whether they tolerate informal exceptions, and whether they protect the process when resistance appears. Culture changes when leaders demonstrate that assortment discipline is not a one-time campaign but part of how the business chooses, invests, and says no. At that point, SKU rationalization stops being a disruptive special effort and becomes what it should have been all along: a normal expression of strategic and operational discipline.
