Turn a broad request into a project by naming the boundary, evidence, participants, deliverable, and completion decision.
Write a One-Sentence Objective
State what the team needs to understand or decide and why it matters. Keep the objective tied to a product, process, work center, handoff, or capital question.
List the Required Access
Identify people, records, shifts, machines, areas, systems, and representative events needed. Note safety, confidentiality, customer, and production constraints.
Define Completion
Specify the agreed output and who accepts it. If implementation, training, testing, or follow-up is needed, include it rather than assuming it comes with the analysis.
Use a Change Test for New Requests
When a new issue appears, ask whether it changes the original decision, required access, deliverable, timing, or responsible people. If it does, record the change and its effect before expanding the work. If it does not, place it in a separate opportunity list so the current engagement can finish cleanly.
This keeps discovery useful without allowing every adjacent problem to become an unpriced or unfinished commitment.