Prepare for a discovery session

Prepare a small, useful evidence set

Discovery works best when the team can follow a real process from its beginning to its outcome. A redacted example usually explains more than a long list of desired features. Select a normal case and, where useful, one case that goes wrong.

1. Write the business question in one paragraph.
2. Identify the person doing the work and the person accountable for the result.
3. Prepare a redacted example showing the steps, handoffs and expected result.

• Do not send passwords, API keys or private sign-in links.
• Arrange any necessary access through the agreed administrator and access process.

Include the operating context

List the systems that hold the records, the systems that carry out work and any manual checks between them. Mark what is known and what still needs verification. Approximate volumes can help scope a discussion when clearly labeled as estimates.

• The current process and the exceptions that consume time.
• A named source for any figures used in the discussion.
• Provider dependencies, approval steps and changes already planned.

Before the session

Confirm participants and preparation with the Platformz team. If essential evidence is unavailable, say so before the session so the discussion can focus on the decisions that can be made.

• Your question and intended output.
• The evidence available and any gaps.
• Who will review findings and approve the next scope.