This guide focuses on deciding whether the available information supports a start or requires a specific question. The worked example follows three units: “release brief”, “product landing page” and “customer email”.
Reference input: release brief and launch date. Expected output: a launch deliverables register. Before assigning work, confirm the current input version and who will review the result.
Define the input before assigning work
For the digital product launch, a usable request lets someone start without reconstructing the original conversation. The reference input is release brief and launch date. 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 release brief 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 brief introduces a new capability to existing customers. The landing page explains its use, the email invites discovery and support needs the same message. The date still requires confirmation from whoever will handle questions.
The example involves Camila, Nora and Sofia. 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 |
|---|---|---|---|
| release brief | Confirmed version, destination and approver | Accept when complete | Camila checks the input |
| product landing page | Current reference without a confirmed date | Return a specific question | Nora confirms the constraint |
| customer email | Ambiguous intended outcome | Investigate before committing | Sofia obtains an acceptable example |
Choose between accepting, returning and investigating
Accept the request when its inputs support producing a launch deliverables register 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 publishing a date the support team cannot cover. The proposed check is to compare the offer and date across all three assets. 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 publishing a date the support team cannot cover. 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: release brief and launch date.
- Case check: compare the offer and date across all three assets.
- Outcome under review: a launch deliverables register.
