Blog
Shared-service ownership maps that stick
Exception bounce between an SSC and entity controllers is rarely a people problem. It is usually an unmarked map inside the tool.
Write ownership as rules, not folklore. For each account family, name who investigates first, who confirms operational context, and who has sign-off authority. Put those names in the reconciliation audit app fields your team already filters on.
Define escalation clocks. If an item sits with an entity contact past two working days, it returns to the SSC with a documented request trail — not a vague chat message. The map should make that path visible to both sides.
Review the map after every close
Ownership drifts when new entities join or when seasonal volume shifts. A fifteen-minute retrospective after sign-off keeps the map honest. Several Manchester teams in our cohorts now treat that retrospective as non-negotiable.
Related reading: aged unmatched triage.