This guide focuses on deciding whether the available information supports a start or requires a specific question. The worked example follows three units: “prospect need”, “demo scenario” and “journey validation”.
Reference input: prospect needs and verified capabilities. Expected output: a needs-based demo script. Before assigning work, confirm the current input version and who will review the result.
Define the input before assigning work
For the custom sales demo preparation, a usable request lets someone start without reconstructing the original conversation. The reference input is prospect needs and verified capabilities. Add the intended outcome, the person who can resolve questions, the current material version and the constraint that governs delivery. Separate required facts from optional conveniences. A field is required when its absence prevents execution or verification. Avoid turning intake into an endless questionnaire: request each fact for a specific decision and show a valid completed example. The person supplying the input should understand why it matters to the next stage.
Compare an incomplete request with a usable one
“We need the prospect need as soon as possible” expresses an intention rather than a ready assignment. A usable request identifies the destination, reviewer, current source material and evidence needed for acceptance. If the date is unconfirmed, write “to be agreed” and identify who must resolve it. Inventing a date to fill a field creates a fictional commitment. Before starting production, ask the executor to describe the expected delivery in their own words. If that interpretation differs from the request, repair the input before estimating effort or promising a completion date.
Worked example
The fictional prospect needs to coordinate a review between two people. The demo script shows that journey using verified capabilities in the available environment. An unverified extra need remains a question rather than a confirmed capability.
The example involves Valeria, Camila and Nora. Names, situations and numbers are illustrative and do not represent customer results. The three units let you test the proposed approach before extending it to other work.
| Unit | Required fact | Intake decision | Next action |
|---|---|---|---|
| prospect need | Confirmed version, destination and approver | Accept when complete | Valeria checks the input |
| demo scenario | Current reference without a confirmed date | Return a specific question | Camila confirms the constraint |
| journey validation | Ambiguous intended outcome | Investigate before committing | Nora obtains an acceptable example |
Choose between accepting, returning and investigating
Accept the request when its inputs support producing a needs-based demo script and checking the result. Return it with a specific question if a critical requirement is missing. “Confirm the approved version” gives the requester a clear action; “more information needed” merely moves the problem. When resolving uncertainty requires work, create a bounded investigation with an owner and an observable output. This keeps exploration distinct from committed execution. Acceptance should make known facts, unresolved questions and the condition for progressing to the next stage visible to everyone affected.
Keep context available during execution
The original request stops helping when changes become scattered across messages. When an input changes, retain the previous decision, new version and reason for the adjustment. Pay particular attention to the risk of showing an unverified capability to answer an objection. The proposed check is to test the promised journey in the available environment. A notification does not establish that its recipient read every earlier discussion. Include a short change summary and its effect on the task. Production, review and delivery should operate from the same current input while preserving enough history to explain why the assignment took its present form.
What to check before closure
The risk to control in this case is showing an unverified capability to answer an objection. A completed label needs a supporting observation. Keep the following beside the decision so the receiver can establish what was checked:
- Input and version used: prospect needs and verified capabilities.
- Case check: test the promised journey in the available environment.
- Outcome under review: a needs-based demo script.
