Short answer
A good project starts with the process, not the technology. Observe the work and measure a baseline; design a limited flow; test it with real cases; only then integrate and expand.
What to observe
Discovery involves the people who do the work, decide and receive the outcome. Design separates rules, information, exceptions and approvals. A prototype validates the journey; a pilot proves behaviour and value; implementation strengthens security, monitoring and operation. Any stage can stop when evidence is missing.
The problem is clear but the shape of the solution is not.
Real cases are available for testing.
The business can name a process owner.
A concrete example
For proposals, week one may map requests and measure time. A prototype prepares two proposal types with controlled sample data; a pilot uses real cases with human review; only then are CRM, pricing and final documents connected.
How to move safely
- Discovery: observe, interview and measure.
- Prototype and pilot: test the smallest valuable journey.
- Implementation: integrate, secure, monitor and transfer knowledge.
Test your process
Tick what happens today. The result changes as you answer.
There is not enough evidence to automate yet. Observe the process for a few days and record volume, exceptions and time spent.
Frequently asked questions
Must the interface be known in advance?
No. It may become an invisible integration, dashboard, customer area or another form. Discovery prevents the answer being forced.
When is the project finished?
When the solution is operational, measured, documented and clearly owned. Later evolution should respond to real use, not a speculative feature list.