What a discovery gives you
I have led many discoveries. Each one ended with a scope: a written description that the client and the delivery team could agree on, plan against and price. That is what a discovery is for, and it is worth doing carefully.
What it does not give you is a finished vision. The client is still forming its picture of the product while the discovery runs, and it keeps forming it once real screens and working software appear. The scope is the best shared understanding at one moment in time. It is not a promise that nothing will move.
The vision keeps refining
On my projects, change requests kept appearing during implementation because the client kept refining its vision. I do not read that as a failure of the discovery, or as a difficult client. People understand what they want much better when they can react to something concrete.
The refinement itself is healthy. The risk is in how it enters the project. If a new idea is absorbed as a clarification of the original scope, the work grows while the budget and the timeline stay where they were, and the team quietly pays the difference.
Show a change as a change
How you show it matters as much as the decision itself. A change request is the way to make the new work visible, so that the budget and the timeline are adjusted together with the scope. The approach is simple:
- The discovery output is the baseline. It is written, agreed with the client and kept as the reference for everything that follows.
- Compare before you discuss. Every new request is checked against the baseline in writing, so the conversation starts from the same page.
- Say what it is. Either it was already in the scope or it is new. Both answers are fine, as long as they are said openly.
- Move budget and timeline together. A change that adds work but moves neither the price nor the date is not a change request. It is a hidden cost.
This is new compared with the baseline we agreed. Here is what it does to the budget and the timeline.
The comparison takes the emotion out of it. Nobody has to argue that a request is too big or too small, because the baseline and the estimate do the talking.
Write the discovery with change in mind
A discovery can make the later conversations easier. I try to record the assumptions and the exclusions next to the scope, and to say plainly which areas the client expects to keep refining. When a request later falls in one of those areas, nobody is surprised that it is handled as a change.
I also keep the baseline in one place that the client can open at any time, so the comparison never depends on anyone's memory of what was said in a workshop.
The client's vision will keep sharpening, and I would not want it any other way. My job is to make sure each step of that sharpening is visible, sized and decided by the person who owns the budget. That keeps the relationship calm and the plan honest.