Why Discovery Isn't a Waste of Time
Good discovery shortens implementation time and reduces changes during development. It creates a common foundation for the project team, departments, and management — what is built, why, and who is responsible for it.
Essential Deliverables
A well-executed Discovery produces at least the following deliverables:
- As-Is and To-Be process mapping with clear decisions.
- Initial data model — objects, key fields, relationships.
- Conceptual permissions model — profiles, roles, sharing.
- List of required integrations with flow direction.
- Documented backlog with prioritization for the first release versus subsequent phases.
- Concrete success metrics for the period after Go-Live.
The Right Questions for Process Owners
Good Discovery doesn't ask 'what do you want in the system,' but rather tries to understand how people actually work:
- What happens when a new inquiry or lead arrives? Who handles it, who approves it, what is saved?
- What decisions are made outside the system (email, Excel, WhatsApp)?
- What reports are truly needed by management and team leaders?
- What data quality rules are critical for operations?
- What happens when an employee leaves or changes roles?
What Ruins Discovery Processes
- Discovery managed only with IT and not with actual process owners.
- A massive document that no one reads or approves.
- Decisions postponed to the 'development phase,' creating unending dependency.
- Avoiding saying 'no' to requests that don't belong in the first release.
Frequently Asked Questions
Focused discovery for a first release typically takes between two to eight weeks, depending on the complexity of the processes and the availability of stakeholders.