The method
- Identify the equipment involved: model, operating system, software version and accessory. Record what is available without opening the hardware. Separate a product name from its exact reference, and leave the latter blank when it is unknown.
- Describe one reproducible situation: attempted action, expected outcome, observed outcome and exact message. Include what still works. A connection failing on one device and an outage affecting the whole home raise different questions; your note does not establish their cause.
- List changes preceding the problem and tests already performed, with their outcomes. Prepare a cropped screenshot when it clarifies the message, removing private identifiers. Send the note through your chosen support channel; avoid risky operations merely to fill a field.
Your recording grid
Use these columns to keep information about your own project. The sheet is blank; you can print it and fill it in.
Fictional worked example
In a fictional case, a computer shows a message when one file is opened, while other files open normally. The note records the application, file type and message, and marks another device as untested. This boundary prevents a local observation from becoming a claim about the whole computer.
The record to keep
Keep a dated version of the note and the replies received. Give each new attempt its own row so the initial observation remains distinguishable from later changes.
What this method can establish
The note supports a precise question; it establishes neither a hardware fault nor replacement compatibility. Microsoft’s reference covers Windows. For another operating system, use its publisher’s documentation.
Supporting documentation
Documentation consulted on
An editorial method, a fictional example and references for further reading.