Name process, system, data and KPI ownership separately
“Owner” is not one concept. Name the process owner, stage owners, decision owners, system owners, data owners and KPI owners separately—so the exception always has a name.
Independently created. Contains no employer or client implementation detail, internal names or figures.
01Context
A commercial transformation assigned “the business” as owner of the customer lifecycle and “IT” as owner of the CRM. When a customer was created twice, the sales team, the finance team, the CRM administrators and master data each pointed to another. Every one of them owned something; nobody owned the exception.
02Decision drivers
- D01
Exceptions need a named owner
- D02
Business decisions must not be made by system administrators
- D03
Data quality must be fixed at the source
- D04
KPIs need someone to act, not only someone to compute
03Options considered
| Option | Right when | Cost / trade-off | Verdict |
|---|---|---|---|
| One “business owner” per process | Small, single-function processes | Hides decision, data and system ownership; exceptions bounce | Rejected |
| A full RACI per activity | An audit needs a complete record of who did what | Unreadable; rarely used to resolve anything | Rejected |
| Named ownership types per process, decision, system, data concept and KPI | Cross-functional processes on shared platforms | An ownership model to maintain | Selected |
Every option is right under some premises. The verdict applies to the context above.
04Decision
For every value stream, name a process owner accountable for the end-to-end outcome; a stage owner per stage; a decision owner per decision (with separate approvers where needed); a system owner per platform, responsible for configuration and releases but not for business rules; a data owner per concept, responsible for quality at the source; and a KPI owner who acts on each measure, separate from the definition owner where that differs. Record them in one ownership model, and route exceptions by type to the named owner.
05Consequences
What this choice changes elsewhere in the system.
- Exceptions
Exceptions reach a named person on the first attempt.
- Decision rights
System owners stop deciding business questions by implementing them.
- Data quality
Data quality has an owner who can fix it.
- Governance
The ownership model becomes an artefact that changes with the organization.
06Revisit when
The decision holds while its context holds. Challenge it when:
The process lives entirely inside one function and one system.
The organization adopts a product-team model that merges several ownership types by design.
07Where this decision is applied
The decision says why this path was chosen; each case shows how it takes part in a larger architecture.
- Operating-model case / 04Designing customer ownership in a multi-subsidiary organizationOne customer relationship across several legal entities, subsidiaries and sales teams: who owns the relationship, each local transaction and the global account data—and who resolves the conflicts.
- Operating-model case / 05Owning and evolving the operating model after go-liveThe complete post-go-live model: every project responsibility handed to a named operating owner before go-live, recurring friction classified into a governed backlog, change authority per domain, versioned releases, operating and release forums, and adoption and model reviews that turn what users struggle with into design changes—so the model keeps improving after the project ends.
- Adoption case / 01Moving a commercial team from parallel trackers to CRMA CRM that exists but does not run the business: each tracker inventoried and classified, its legitimate value moved into the operating model, the management routines moved in with owners, decision rights set for retirement, definitions and data quality—and a dated freeze, with bypass signals afterwards.
- Adoption case / 04Replacing mandatory fields with data people useA CRM full of complete but meaningless data: each field audited for who enters it, who uses it and which decision it feeds—then removed, derived, prefilled, made conditional or kept, with value returned to the person entering it.
08Related decisions
Decisions this one depends on, or constrains.
- ADR / 004Separate commercial approval from financial validationTwo decisions with different owners, evidence and SLAs should not share one approval step—even when one form collects the data for both.
- ADR / 016Record every local variation with a reason, owner, scope, cost and review dateLocal differences are decisions, not habits. Each one is classified—global change, configuration, local extension or rejected—and recorded with its reason, owner, scope, cost and review date.