In SAP Activate, discovery happens before the core implementation project. The Discover phase identifies business scope, expected value and benefits, adoption strategy and roadmap. For SAP Cloud ERP, discovery can also use the Digital Discovery Assessment to help match requirements with an appropriate deployment and provide a foundation for implementation.
Discovery answers a decision question before a delivery question
At this point the organization is not yet deciding every configuration value. It is deciding whether the proposed transformation makes business sense, what should broadly be in scope, which SAP capabilities appear relevant, and what needs to be handed to the implementation team.
What is explored before implementation starts?
| Discovery question | Why it matters |
|---|---|
| What business outcome is wanted? | Creates a reason for the investment beyond simply replacing technology. |
| Which processes and capabilities matter? | Shapes high-level scope and helps focus later workshops. |
| Which deployment and solution direction fits? | Prevents detailed planning around an unsuitable starting assumption. |
| Who are the important stakeholders? | Connects executive sponsorship, process ownership and implementation responsibility. |
| What assumptions remain? | Makes uncertainty visible so it can be validated rather than silently becoming a commitment. |
Discovery is not the same as Fit-to-Standard
SAP distinguishes the Discover phase from the Explore phase. Discover establishes business scope, value, benefits and an implementation direction. After the project begins, Explore uses Fit-to-Standard workshops to validate selected standard processes with customer experts, identify configuration decisions and capture approved delta requirements in the backlog.
Discovery should create enough clarity to start the right project, while detailed process validation belongs later in structured implementation work.
Separate a known requirement from an early assumption.
If a stakeholder says, “We need SAP because our current process is too slow,” discovery should ask what is slow, who experiences the delay, what outcome would improve, which processes are affected and how success would be measured. That turns a broad complaint into information that can shape scope and value.
What should pass from discovery into delivery?
Current SAP methodology describes discovery artifacts that capture requirements, technical architecture needs, business value and scope so they can be handed to the implementation team. The exact artifacts vary by solution and engagement, but delivery should not have to rediscover every assumption from scratch.
Once the business case is approved, SAP Activate moves into Prepare, where the implementation project starts, plans are finalized, teams are onboarded and the initial environment is prepared.
Why this matters to an SAP professional
- Projects inherit decisions and assumptions made before configuration starts.
- Good discovery connects technology to measurable business outcomes.
- Scope clarity reduces avoidable confusion during later workshops.
- A disciplined handover protects continuity between sales, presales and delivery.