The small request that touches everything
A client asks for “just one more field” in a form. It needs validation, permissions, integration, reporting, and translation. The request may make sense; “just” does not reveal the work. An immediate yes creates expectations before consequences are understood. An immediate no may close off a useful opportunity.
Start with the reason: what problem does it solve, who benefits, and what happens if it waits? Sometimes a process change meets the need without changing the product. Sometimes the new request matters more than planned work. Understanding value makes a concrete trade-off possible.
Offer options, not an impossible promise
You can replace a lower-priority deliverable, move the date, or assess additional capacity. Each option has limits. Adding people does not automatically remove dependencies, onboarding, or reviews. If time and capacity are fixed, discuss what is removed or simplified.
For example: “We can include export in this release if the advanced dashboard moves to the next. We keep the date and validate export against these three criteria.” This links the request to a verifiable trade-off. Avoid silently absorbing cost through recurring overtime or skipped tests.
Record the choice and update the plan
Record the request, rationale, estimated impact, decision, and approver. Then update the work list and affected people’s expectations. A spoken agreement that never reaches the plan creates two realities: the client’s and the team’s.
Keep control proportionate. A button color does not need the same process as a financial integration change. In Scrum, scope can be clarified and renegotiated as learning occurs while preserving the Sprint Goal. Flexibility works better with a clear objective and decision authority.
Prepare the next change conversation
Take a pending request and write two options with explicit consequences. State what changes, what stays, and who decides. Ground the conversation in value and real capacity. A good negotiation ends with a shared understanding of the commitment, not simply a yes.
Sources & further reading
Sources accessed October 24, 2026. Numerical examples and scenarios are illustrative.
Ready to put this knowledge into practice?
We can work together on your team’s challenge or your next project.
Talk to Calembe ↗