Midway through a project, the client keeps adding requests. How do you handle it?
Client delivery · Pro 1
Short answer
Acknowledge each request, write it down and assess its impact on timeline, cost and risk. Then give the client a clear choice through the agreed change process: add it and move the date or budget, swap it for something of similar size, or park it for a later phase. Keep the sponsor informed and protect the core deliverable.
Deeper answer
Saying no is easier when the scope of work is clear, which is why it pays to write it well. Frame trade-offs in the client's terms: 'If we add the Hindi interface now, the pilot moves two weeks. Shall we do it in phase two?'
Track changes in a log the client can see. Small favours add up; even if you accept them, record them.
What a strong answer covers
- Acknowledges and records requests
- Assesses impact on time, cost and risk
- Offers options: add with trade-off, swap or defer
- Uses the agreed change process
- Keeps the sponsor informed; protects the core
Answer it out loud in the mock interview about 1.5 min
Follow-ups to expect
- How would you say no to a senior stakeholder?
- What goes into a change log?
Common mistakes
- Silently absorbing extra work
- Refusing without offering options
Learn it
- How would you connect an AI assistant to a client's SharePoint, Salesforce and Jira?
- How do you update a client's executives on an AI project?
- A client tells you their AI assistant invented a policy clause and a customer acted on it. What do you do?
- How do you hand over an AI system to the client's team?
- How do you move an AI solution from proof of concept to production?
- You start with a new enterprise client. How do you run discovery?
- A client says 'automate our sales process'. What do you do first?
- The client's staff are worried your automation will replace them. How do you handle it?
- What goes into a scope of work for an AI project?