The project has no clear customer. Who should approve requirements?

Undefined outcome ownership

Identify who uses the output, who pays, who operates it, and who accepts it. These may be different people, so assign explicit responsibilities instead of inventing one generic customer role.

What to do now

  1. Map users and affected services
  2. Identify the business outcome owner
  3. Name acceptance and operational authorities
  4. Agree how conflicting needs are resolved
Recommended action flow for undefined outcome ownership: Map users and affected services then Identify the business outcome owner then Name acceptance and operational authorities then Agree how conflicting needs are resolved. Escalate when nobody accepts responsibility for deciding whether the result is usable.

When to escalate

Escalate when

Nobody accepts responsibility for deciding whether the result is usable.

Who decides

The accountable sponsor

Example

A library system names librarians as users, a service manager as outcome owner, and operations as the support authority.

Mistake to avoid

Letting the technical team act as its own customer.

Prevent a repeat

At each stage decision, check that the expected outcome, owner and justification remain valid.

Suggested ApprovedFlow setup

  • Projects
  • Documents
  • Approvals

Keep the decision brief with the project and request a recorded sponsor decision before the next commitment. See the platform

Related cases

Practice references