STMC All articles
Operations & Performance

Three Roads to the Same Fix: Pricing Redundancy in the Transformation Portfolio

STMC
Three Roads to the Same Fix: Pricing Redundancy in the Transformation Portfolio

Photo: business portfolio review duplicate projects transformation workshop, via img.freepik.com

Large organizations rarely fund the same bad idea twice under the same name. They fund it three times under different names, in different business units, with different sponsors and slightly different language. The duplication is not usually malicious. It is the natural result of portfolio governance that reviews projects one at a time and rarely compares problem statements across the enterprise. The cost shows up as rising transformation spend without compounding returns.

Duplication Is Not Always Waste, Until It Is

Some redundancy is deliberate. Competing teams can accelerate learning, and a degree of local variation is necessary when markets, customers, or regulations differ. The audit should not assume that every overlap is waste. It should distinguish between productive experimentation and unmanaged duplication. Productive experimentation has a hypothesis, a time box, a shared learning mechanism, and a clear path to convergence. Unmanaged duplication has separate budgets, separate vendors, separate definitions of success, and no owner responsible for reconciling the results.

A Method for Surfacing Overlap

Begin with a capability taxonomy, not a project list. Group initiatives by the capability they are meant to create or improve: pricing, claims intake, supplier onboarding, data access, field scheduling, compliance reporting. Then normalize each initiative into a problem statement of no more than two sentences. The wording matters. If two initiatives describe the same problem in different vocabulary, the portfolio is likely paying twice for one solution.

Next, build a comparison matrix with five columns: problem statement, owner, budget, technology or vendor, and expected outcome. Add a sixth column for dependencies. Duplication often hides behind different technologies. One unit buys a workflow tool, another builds a custom module, and a third funds a consultant to redesign the process. Each project looks distinct until the matrix shows that all three are trying to reduce the same handoff delay.

Interview the sponsors separately. Ask what would happen if the initiative were paused for six months. If the answer is that another unit already has a workaround, the duplication is real. If the answer is that the workaround is inadequate and the units have different constraints, the portfolio may need a shared platform with local configuration rather than a single mandated solution.

Pricing the Redundancy

Price duplication in three layers. First, direct spend: licenses, contractors, hardware, and internal labor. Second, coordination cost: the meetings, steering committees, and integration work required to keep parallel efforts from colliding. Third, opportunity cost: the capability that was not built because scarce specialists were spread across overlapping efforts. The third layer is usually the largest and the least visible.

Do not stop at a single number. Present a range and state the assumptions. A range is more credible than a false precision, and it gives the portfolio committee something to test. Include the cost of retiring a duplicate, because consolidation is not free. A credible audit shows both the savings and the transition expense, along with the risk of disrupting a unit that has already built local momentum.

Governance That Rewards Shared Solutions

Portfolio governance should make duplication visible before funding, not after. Require every initiative above a threshold to name the problem it solves and the existing efforts that address the same problem. Give a central portfolio function the authority to convene sponsors when overlap is detected. Do not give it the authority to mandate a single solution on day one. Mandates without diagnosis tend to produce compliance theater and shadow work.

Create a shared-solution track for problems that appear in more than one unit. Fund discovery once, then decide whether to build, buy, or reuse. Hold the sponsors of parallel efforts jointly accountable for a convergence decision by a fixed date. If convergence is not appropriate, document why. A recorded exception is governance. An unrecorded exception is duplication with better manners.

The Portfolio Conversation

The point of a duplicate initiative audit is not to shame business units. It is to change the question the portfolio asks. Instead of asking whether each project is justified on its own terms, ask whether the enterprise is buying the same capability more than once and calling it strategy. In 2026, with technology costs rising and specialist capacity scarce, that question belongs in every funding cycle. The organizations that answer it well will not necessarily spend less. They will spend more deliberately, and the returns will compound instead of colliding.

All Articles

Related Articles

Following the Number Home: A Lineage Audit for the Metrics You Govern By

Following the Number Home: A Lineage Audit for the Metrics You Govern By

The Output Audit: Separating Transformation Office Activity from Enterprise Change

The Output Audit: Separating Transformation Office Activity from Enterprise Change

Where the Process Bends: Reading Shadow Work as Operating Model Evidence

Where the Process Bends: Reading Shadow Work as Operating Model Evidence