SAP Activate Discover Phase: Activities, Deliverables, and Project Decisions

The Discover phase establishes why an SAP project should proceed, what business outcomes it must support, and how the initial opportunity will be evaluated. It creates enough alignment for stakeholders to make an informed decision before detailed planning begins.

Discover is an early decision and framing stage. The team defines the business problem, identifies the expected value, outlines the solution scope, and records major assumptions. Detailed configuration, sprint execution, and cutover planning belong to later phases.

01What the Discover phase is designed to achieve

The main outcome is a shared direction for the initiative. Business sponsors, process owners, IT leaders, finance representatives, and implementation partners should understand the reason for change and the decisions required to move forward.

A useful Discover phase connects four elements:

• The business capabilities that require improvement
• The current operational pain points and constraints
• The expected benefits and measures of success
• The proposed scope, delivery approach, and decision path

The team should express the opportunity in business terms rather than beginning with a list of transactions or technical features. For example, a program may aim to improve order visibility, shorten financial close activities, standardize procurement, or establish a reliable integration model across business units.

Teams often use an SAP Activate overview to align terminology and understand how Discover connects to the remaining project phases.

02Core Discover phase activities

Confirm the business case

Document the reason for the project, the business outcomes it is expected to support, and the consequences of delaying action. Include measurable indicators where possible, such as cycle time, close duration, inventory accuracy, service levels, or manual effort.

The business case should identify who owns each expected benefit. A benefit without an accountable owner is difficult to measure and easy to lose during delivery.

Define the initial scope

Describe the organizational units, countries, business processes, products, and interfaces that are expected to be included. Record important exclusions as well. A clear boundary prevents early conversations from becoming an unlimited requirements list.

At this stage, scope is directional rather than configuration-ready. The team can state that procurement, sales, finance, manufacturing, or warehouse operations are in scope without yet defining every process variant.

Identify stakeholders and governance

Create a stakeholder map covering executive sponsors, process owners, technical owners, security representatives, data owners, change leads, and implementation partners. Define how decisions will be made and how unresolved issues will be escalated.

A simple governance model usually identifies the sponsor, steering group, program manager, workstream leads, and decision forums. It should also specify the cadence for status reporting and risk review.

Assess the current landscape

Capture the systems, interfaces, data sources, custom developments, reporting tools, and operational dependencies that may affect the initiative. The assessment does not need to be a complete technical inventory, but it should expose constraints that could change scope, timing, or cost.

Include known dependencies involving identity management, integrations, data retention, regulatory controls, third-party applications, and organizational readiness.

Compare solution directions

Evaluate the broad solution direction against business goals, operating-model needs, strategic architecture, and delivery constraints. The comparison should be evidence-based and should make assumptions visible.

Avoid committing to detailed design before the relevant process discussions take place. Discover should create a credible direction while preserving the ability to validate fit during Explore.

Establish the initial delivery roadmap

Outline the major milestones, decision gates, workstreams, environments, data activities, integration work, testing strategy, change activities, and deployment expectations. The roadmap should show dependencies and identify items that require confirmation in Prepare.

The SAP Activate roadmap viewer usage guide can help teams organize the work packages and accelerators used to structure the delivery plan.

03Typical Discover phase deliverables

Deliverables vary by project size, but a practical baseline usually includes the following:

The deliverables should be concise enough for governance use and detailed enough to support the Prepare backlog. A large collection of disconnected documents is less useful than a small set of linked decisions.

04How to run Discover workshops

Start with business outcomes and constraints. Ask participants to describe what must improve, how the problem is measured today, which groups are affected, and what would demonstrate success.

Use a structured workshop sequence:

1. Confirm the strategic objectives and business drivers.
2. Map the affected capabilities and high-level processes.
3. Identify pain points, constraints, and dependencies.
4. Define the initial scope and major exclusions.
5. Record assumptions, risks, and open decisions.
6. Agree on benefit owners and success measures.
7. Review the delivery direction and next-stage actions.

Keep an explicit decision log during each workshop. Separate a confirmed decision from an assumption, an open question, and a future design topic. This distinction prevents unresolved issues from being treated as settled scope.

Workshop participants should leave with named owners and due dates. A follow-up action without ownership is not a reliable project control.

05Discover phase roles and responsibilities

The executive sponsor owns the business case and confirms that the initiative supports strategic priorities. Business process owners describe the operational outcomes and identify the groups affected by change.

The program manager coordinates the work, maintains the decision and risk logs, and prepares governance decisions. The architecture and integration leads assess landscape dependencies and outline the solution direction. The data, security, and change leads identify readiness concerns that may affect scope or timing.

Implementation partners can facilitate workshops and provide delivery experience, but business leadership must own the business outcomes and scope decisions. This ownership keeps the project anchored in operational value.

06How Discover transitions into Prepare

Discover is complete when the organization has a clear reason to proceed, an agreed initial scope, accountable decision makers, visible risks, and a realistic next-stage plan. It does not require every requirement to be finalized.

Prepare converts the direction into an executable project structure. It develops the team, confirms environments and governance, refines the plan, establishes working methods, and turns open items into managed activities. The SAP Activate Prepare phase guide provides a useful companion when converting Discover outputs into delivery controls.

Before the transition meeting, check that:

• The business outcomes have measurable owners.
• Scope and exclusions are documented.
• Major dependencies and assumptions have owners.
• Risks have response actions or an accepted treatment.
• Governance forums and decision rights are agreed.
• The initial roadmap has realistic dependencies.
• The next-stage backlog contains specific actions.
• Sponsors understand the decisions and residual uncertainty.

07Common Discover phase problems

Starting with detailed requirements

A long requirements catalogue can create the appearance of progress while the business case and scope remain unclear. Begin with outcomes, capabilities, and constraints, then defer detailed requirements to the appropriate process and design activities.

Treating every request as in scope

Uncontrolled scope expansion makes cost and timing unreliable. Use explicit inclusion, exclusion, and decision criteria so that new requests can be assessed consistently.

Leaving benefits without owners

Benefits need accountable owners, measures, baselines, and review dates. Assigning ownership early makes the business case testable during later governance reviews.

Hiding uncertainty

Early projects contain assumptions. Recording them openly allows the team to validate them, assign owners, and plan responses. An unrecorded assumption becomes a hidden dependency.

Treating governance as administration

Governance is a decision mechanism. Meetings should review outcomes, risks, dependencies, and decisions rather than only reporting activity completed.

Designing the solution too early

Premature design can lock in assumptions before process fit and organizational needs are understood. Keep the Discover solution direction at the right level and carry design questions into the next phase.

08A practical Discover phase completion checklist

Use the following checklist in the final review:

• The project purpose is stated in measurable business terms.
• Expected benefits and benefit owners are documented.
• Initial scope, exclusions, and affected organizations are recorded.
• Current systems, integrations, data concerns, and constraints are summarized.
• Stakeholders, governance forums, and escalation routes are named.
• Risks, assumptions, dependencies, and open decisions are maintained.
• The proposed delivery direction has sponsor support.
• The roadmap identifies major milestones and decision gates.
• Prepare activities have owners and target dates.
• The transition decision and residual uncertainty are documented.

A strong Discover phase gives the project a defensible starting point. Its value comes from making the business purpose, scope, ownership, and uncertainty visible before the team commits to detailed execution.