CX Methods
Share the full picture, or pay for it in rework
Drip-feeding context to CX teams guarantees rework and late ambushes. Make full disclosure of constraints a governance rule, not a courtesy.
A familiar anti-pattern: CX teams are treated as order takers, fed context in drips, then ambushed late with objections built on information that existed all along. The cost is rework, delay, and eroded trust. The fix is a governance rule: share everything, early.
The pattern is familiar in most organizations. A CX team is briefed on a project, but only partially. Constraints, stakeholder concerns, and technical limitations arrive in drips, released when someone decides they are needed. Then, late in the work, the ambush: 'what about Z?' The information about Z existed the whole time. It just was not shared. This is information hoarding, and it is rarely accidental. Inside organizations, information is power, and drip-feeding it keeps the holder important.
Why it matters to the business
Every late objection built on withheld information converts directly into rework: designs redone, launches slipped, budget spent twice for one outcome. The deeper cost is structural. Customer journeys cut across departments, and McKinsey's journey research found performance on end-to-end journeys is 30-40% more strongly correlated with customer satisfaction than performance at any single interaction along the way. No single function holds the whole picture, so hoarded context does not just slow the work; it degrades the experience in ways each silo cannot see. Forrester finds fewer than one-third of firms create shared accountability for journey performance, which is the same disease in organizational form.
How to use it
- Open every engagement with a full constraint briefing: technical limits, budget, compliance, stakeholder politics, and past failed attempts.
- Maintain one shared brief that anyone on the project can read. If a constraint is not in the brief, it cannot be raised as a late objection.
- Give CX teams standing access to roadmaps, support data, and compliance requirements by default, not by request.
- Log every late-stage objection and trace when the underlying information first existed. Review the log quarterly.
- Name an owner who enforces the rule. A norm without an enforcer is a suggestion.
Where teams get it wrong
Treating this as a manners problem. Asking people to communicate better changes nothing, because hoarding is rational whenever information confers status and withholding carries no penalty. Only governance changes the payoff: make transparency the rule and treat every late ambush as a recorded process failure, not a discovery.
Ask your team
- What did we know at kickoff that the design team only learned in week six?
- Where is the single document listing every constraint on this project?
- The last time a late objection derailed work, was it treated as discovery or as a process failure?
Withholding information is a power play, not collaboration.
Apply this
Reading about share the full picture, or pay for it in rework is one thing. Seeing where it applies in your journey is the useful part.