Skip to main content
BSS/OSS Academy

The Dependency Nobody Owns

Intermediate6 min+100 XP
Page 1 of 5

The Situation

Your role

Enterprise / Lead Architect

You are accountable for the order completing, not for your layer of it behaving correctly.

Eight domains, every interface built to spec, and a 30% order-fallout rate nobody owns.

A B2B connectivity order crosses sales, CPQ, commercial order management, service order management, service inventory, resource inventory, activation and billing. Eight teams, eight backlogs, eight definitions of done.

Each interface meets its contract. Roughly 30% of orders still stop somewhere in the chain, and the average time to identify which team owns a given failure is four days — longer than the activation SLA.

Our API returned 200. Whatever happened after that is not our defect.

A domain lead, in three separate incident reviews
The Concept-to-Market chain, blocked at catalogue governanceFour stages in sequence: Product Portfolio, Catalogue Governance, Implementation and Launch. Catalogue Governance is marked with a warning symbol and the word Blocked — nothing reaches implementation, and so nothing reaches launch, until the modelling question it holds is answered.PRODUCTPORTFOLIOCATALOGUEGOVERNANCE!BLOCKEDIMPLEMENTATIONLAUNCH
  • Interfaces

    All built, all meeting contract

    Ready

  • Order completion

    ~30% stop mid-chain

    Blocked

  • Fault ownership

    4 days to identify owner

    Blocked

Activation SLA is 5 working days