TEK / working context

Working notes / tek-services.com

Build a context packet someone can use.

A hand-off should give the next reader an informed starting point. Use these prompts to reduce the amount they have to infer.

State the purpose in plain language

Begin with the question or intended outcome. Write it so a reader can understand why the task exists before they know the implementation detail.

“Understand why the selected category is not visible after reload” is a clearer starting point than “Fix persistence.” The narrower wording shows what needs investigation without assuming the cause.

Describe the current state

Record what you observed and the relevant conditions. Include the interaction path or comparison that gives the observation meaning. Avoid a long transcript of every attempt.

Separate an expected result from an observed result. If the expectation comes from an earlier decision, identify that decision in the place where the note will be used.

Name the boundary

Say which part of the work the note addresses. If a nearby question is deliberately separate, explain that boundary in one sentence.

A boundary helps the next reader understand a limited investigation without assuming it settles the whole system. Revisit it when the evidence changes the scope.

Attach evidence to the point it supports

Use a concise description of the reproduction path, a relevant excerpt or another appropriate record in your actual working environment. Explain what the material demonstrates.

Do not make a reader infer why a large collection of material is attached. Identify the detail that supports the observation, and distinguish old evidence from the current state.

Keep interpretations provisional where necessary

List a possible explanation as something to examine. If there are several plausible explanations, state the distinction that further evidence would help resolve.

The question “Is the value absent or only not displayed?” gives an investigation a direction without presenting either explanation as already established.

Choose a useful next action

Write the next action in terms of what it should clarify. “Repeat the path and inspect the restored state” is useful because it connects an action with an unresolved question.

If a decision is needed from someone else, name the decision in the working note. Avoid assigning responsibility by implication or leaving an unanswered request hidden in background detail.

Close the hand-off with a current summary

Read the note from the top as someone joining the work. Remove references that depend on a private conversation and explain unfamiliar labels that matter to the task.

Keep the purpose, current observation and next question easy to find. When the work moves on, update the summary so that earlier possibilities are not mistaken for the latest conclusion.

Return to the overview →