Shopfloor Suite (opens in a new tab)
Company
Worksheet

Discovery checklist for an enterprise technology project

A practical worksheet for clarifying the business problem, systems, responsibilities and first delivery decision before a technology project.

Use this worksheet with a business process owner and a technical owner. Record evidence, an owner and an unresolved question for each section. Leave unknown answers open; the purpose is to make uncertainty visible before choosing a solution.

Share on LinkedIn

Download PDF worksheet ↓

1. Define the decision

  1. Which process causes difficulty, and who experiences it? Describe one real example from start to finish.
  2. What outcome would justify a change? Record the current baseline, how it is measured and who can verify it.
  3. What is explicitly outside the first project? List deadlines, budget boundaries and operational constraints.

Notes: evidence · owner · open question · next verification step

2. Map systems and information

  1. Which SAP, Dynamics, Salesforce, custom applications or production systems participate in the process? Record versions, owners and support arrangements.
  2. Which system owns each business record? Trace one order or transaction across interfaces, including manual spreadsheets and re-entry.
  3. What access, sample data and interface documentation can be provided safely? Identify personal or commercially sensitive fields before sharing.

Notes: evidence · owner · open question · next verification step

3. Make operational constraints explicit

  1. When can changes be tested or released? Identify peak business periods, factory shifts and required availability.
  2. Who approves security, access, data handling and process changes? Name the responsible roles and review sequence.
  3. How would you recover if the first release failed? Agree the rollback decision, business fallback and recovery owner.

Notes: evidence · owner · open question · next verification step

4. Define the first verifiable delivery

  1. Choose one representative workflow for a pilot. State its input, expected output, exception cases and acceptance evidence.
  2. Separate a mandatory requirement from a preference. Record assumptions that need validation before estimating work.
  3. Agree who supplies test cases, who accepts the result and who supports it after handover.

Notes: evidence · owner · open question · next verification step

Output and next step

Bring a one-page problem statement, a system-and-interface list, one representative process example and a ranked list of open questions to the discovery discussion. Use the evidence to choose a bounded next step; this worksheet is not a fixed scope or a delivery estimate.