What Can Go Wrong?
The most common and expensive mistakes in BSS/OSS transformation — architectural, delivery and organisational. Each has been repeated across dozens of operators, and each is avoidable.
Every pattern below has been observed across multiple real-world BSS/OSS transformations. They are not hypothetical — they are documented, repeatable failure modes.
Catalog Without Runtime Consumers
Introducing a TMF-aligned catalog without COM, SOM, or ROM to consume it
Why It Happens
The catalog feels like a safe, contained starting point. It is a "design-time" deliverable that does not require runtime integration. Vendors promote it as a foundational first step.
Assumptions
- Legacy systems will be adapted to consume the new catalog
- The catalog can be valuable as a standalone product repository
- Runtime consumers will follow naturally
What Goes Wrong
- 1The catalog becomes a static artefact with no runtime value
- 2Legacy CPQ, CRM, and billing continue using their own product definitions
- 3Two sources of truth emerge
- 4The programme claims delivery but nothing changes operationally
Cost Impact
6-12 months wasted modelling effort plus platform licensing for a system nobody uses. The real cost is lost momentum and credibility.
The Right Approach
Never introduce a catalog without at least one runtime consumer (CPQ, COM, or SOM) that will process real orders. Deliver them together.
What the research says
Every finding sourced, dated and qualified in Did You Know? →- Pattern · Technology-first transformationTechnology is implemented without sufficient business and process redesign.
- Pattern · Weak business ownershipTransformation remains an IT initiative instead of an enterprise transformation.
Every anti-pattern shares the same root cause: optimising for short-term comfort over long-term outcomes. The correct approach is almost always harder to start but cheaper to finish.