What Should I Do if the Client Keeps Delaying Data, Interviews, or Decisions?
Treat repeated client delays as project dependency risks, not personal frustrations.
Diagnose the Blocker
Ask what is preventing progress. Common causes include unclear ownership, legal review, system complexity, competing priorities, stakeholder resistance, or unresolved decisions.
Useful questions include:
- Who owns the next step?
- What is blocking completion?
- Can we use a simpler temporary input?
Make the Impact Visible
Track each dependency, owner, due date, affected deliverable, and escalation point.
For example:
“We need the profitability file by Wednesday to complete segmentation for next week. If it arrives later, the recommendation will remain directional.”
Continue Unblocked Work
Use available data, build analysis templates, prepare interview guides, test hypotheses, or identify reasonable proxies. Clearly label assumptions and limitations.
Escalate With Options
If delays threaten quality, timing, or scope, align with your manager and propose alternatives:
- Use assumptions
- Narrow the deliverable
- Involve another owner
- Reset the milestone
- Escalate to the sponsor
Afterward, document delayed items, agreed workarounds, owners, decisions, and revised timing.
How Do I Handle Client Sandbagging Without Damaging the Relationship?
Avoid accusing the client of intentionally delaying or obstructing the work. What appears to be sandbagging may reflect fear, competing priorities, limited authority, political concerns, or uncertainty about how findings will be used.
Look for a Pattern
One delayed file is not necessarily meaningful. More concerning signs include:
- Repeated delays before milestones
- Late objections to agreed assumptions
- Withholding information without explanation
- New concerns introduced near completion
Ask Neutral Questions
Say:
“What is making this request difficult?”
“Are there concerns about how the analysis will be used?”
“Who else needs to approve this?”
Curiosity reduces defensiveness and helps reveal the actual blocker.
Explain the Impact
Connect the issue to the client outcome:
“Without plant-level cost data by Wednesday, we can provide a directional view but cannot validate the savings estimate.”
Invite the stakeholder to correct early drafts and explain how their input improves the work.
Align Before Escalating
Brief your manager or partner using facts, impacts, and options—not accusations.
Possible responses include revised milestones, sponsor involvement, stated assumptions, or documented limitations.
Confirm owners, deadlines, decisions, and risks in writing. Calm transparency protects both the client relationship and project delivery.
How Do I Keep a Project Moving When the Client Is Not Providing What We Need?
Shift from passive waiting to active dependency management.
Separate Blocked and Unblocked Work
Identify which activities require the missing data, interviews, access, or decisions and which can continue.
You may still:
- Draft the storyline
- Build analysis templates
- Review benchmarks
- Prepare interview guides
- Develop preliminary hypotheses
Use Proxies Carefully
Where appropriate, use prior reports, historical data, smaller samples, expert input, or directional assumptions.
State the limitation clearly:
“This is a directional view based on available information and will require validation when the full extract arrives.”
Never present an assumption as confirmed evidence.
Track Dependencies
Maintain a simple record showing the required input, owner, due date, affected deliverable, impact, and next action.
Instead of repeatedly requesting updates, ask what would unblock delivery or whether another owner should become involved.
Escalate With a Recommendation
If the dependency threatens scope, timing, or quality, align with your manager and propose a solution:
- Proceed with assumptions
- Narrow the analysis
- Defer the affected work
- Involve the sponsor
- Reset the milestone
Effective escalation helps the client choose a path forward rather than merely reporting frustration.
How Do I Document Client Dependencies So Missed Deadlines Do Not Become Our Fault?
Document dependencies before they become overdue, using neutral language focused on delivery rather than blame.
Define Each Dependency
Record:
- Required file, interview, approval, or decision
- Owner
- Due date
- Affected workstream
- Delivery impact
- Next action
- Escalation point
For example:
“Customer profitability file from Finance, owned by Priya, due Tuesday at 5 p.m. for Friday’s segment-margin readout.”
Explain the Consequence
State what changes if the dependency is late:
“If the file arrives after Tuesday, Friday’s discussion can include directional hypotheses but not a validated recommendation.”
This connects timing to quality and decision-making.
Use a Consistent Tracker
Review dependencies during status meetings and working sessions. Confirm verbal agreements in writing:
“Regional interviews will move to next week. We will use existing notes for the interim discussion and adjust the synthesis timeline.”
Keep the Tone Neutral
Avoid saying the client caused the delay. Say:
“The revised data timing limits validation for this milestone. We recommend using a directional view or moving the final recommendation.”
Good documentation shows that the team identified the dependency, explained its impact, proposed options, and managed expectations professionally.
What Should I Do if the Client Gives Incomplete, Messy, or Unreliable Data?
Treat poor data quality as a project risk rather than quietly forcing unreliable information into the analysis.
Diagnose the Problem
Identify whether the data is:
- Missing
- Duplicated
- Outdated
- Inconsistently defined
- Incomplete by region or period
- Impossible to reconcile
Describe specific implications:
“Missing customer IDs prevent customer-level profitability analysis.”
Find the Owner and Definitions
Ask who owns the source system, which file is authoritative, how major fields are defined, and whether known limitations exist.
Useful questions include:
- How is churn defined?
- Which system is the source of truth?
- Should totals reconcile with Finance?
- Which periods and regions are included?
Use Assumptions Transparently
When corrected data will not arrive in time, consider samples, proxies, or directional estimates. Label them clearly:
“This is a directional view based on the current extract and should not be treated as final.”
Explain Options
Avoid simply declaring the data unusable. Offer alternatives:
- Request a revised extract
- Narrow the analysis
- Proceed directionally
- Adjust the timeline
- Use stated assumptions
If quality affects the recommendation, brief your manager with the evidence, impact, workaround, and decision required.
