The client changes their mind repeatedly. How do we manage the relationship?

Repeated preference changes

Use early examples to clarify decisions and make the cumulative consequences visible. Preserve a constructive relationship while requiring explicit choices about rework and commitments.

What to do now

  1. Identify which decisions keep changing
  2. Use examples to resolve ambiguity early
  3. Track cumulative rework and schedule effects
  4. Agree decision checkpoints and change rules
Recommended action flow for repeated preference changes: Identify which decisions keep changing then Use examples to resolve ambiguity early then Track cumulative rework and schedule effects then Agree decision checkpoints and change rules. Escalate when repeated reversals make the agreed outcome infeasible.

When to escalate

Escalate when

Repeated reversals make the agreed outcome infeasible.

Who decides

The authorized change decision maker

Example

A design team obtains approval of a representative page before applying the pattern throughout the site.

Mistake to avoid

Accepting every reversal without showing what it displaces.

Prevent a repeat

Compare delivered changes with authorized decisions and keep the current baseline distinguishable from earlier versions.

Suggested ApprovedFlow setup

  • Documents
  • Approvals
  • Tasks

Keep the change request, impact assessment and recorded decision together; update affected tasks only after the appropriate authorization. See the platform

Related cases

Practice references