Prioritization

The Most Important ERP Decision: What Not to Fix

May 13, 2026 · 3 min read

You know what not to fix in ERP when a change does not reduce financial risk, improve reporting reliability, or support critical business outcomes. If it does not meet one of those tests, it may be adding complexity rather than value.

Why fixing everything feels reasonable

ERP environments generate a constant stream of issues and requests. Reports need improvement, processes need refinement, and teams want changes that make their work easier. Responsiveness feels like progress.

But ERP is a shared system. Every change affects other parts of the environment. When everything is treated as something that should be fixed, the system expands without enough control.

What should move forward

Useful ERP governance gives leaders clear criteria. Work should usually move forward when it reduces financial risk, improves reporting reliability, protects critical operations, or removes a constraint that is limiting growth.

Work that mostly improves convenience may still matter, but it should not be treated as equal to work that protects reporting, close, operations, or leadership decisions.

Why backlogs create a false sense of priority

ERP backlogs are often treated as roadmaps. They contain valid issues, reasonable enhancements, and requests that make sense in isolation. The problem is that the presence of an item in the backlog creates the assumption that it deserves attention.

Without clear criteria for exclusion, the backlog becomes a list of everything that could be done instead of what should be done.

Why this is a financial decision

Every ERP change carries a cost. It consumes budget, introduces dependencies, and competes with higher-value work. Deciding what not to fix is not merely technical. It is a financial control decision.

• Not all ERP work creates value.
• Backlogs often reflect noise, not priorities.
• Every change introduces cost and risk.
• Control comes from exclusion, not volume.

FAQ