Give the problem its surroundings
The same symptom can have several explanations. A broken page may involve its layout, its browser, its screen size, or the way it was deployed. A weak message may need a clearer audience rather than more dramatic words. Context connects the visible problem to the environment around it. Describe when the issue began, where it happens, and what still works. Include the exact message or behavior rather than only saying something is broken. A short, accurate description is more useful than a confident guess about the cause.
Explain what has already happened
Tell the operator what you tried and what changed afterward. If a restart helped temporarily, say so. If the previous version worked, identify it. If an earlier answer misunderstood the goal, explain the difference. This history prevents repeating a failed approach and protects decisions you have already made. For creative work, identify the approved source and the elements that are locked. For technical work, identify the relevant versions and configuration. The point is not to produce a perfect incident report; it is to make the next decision better informed than the last one.
Share useful evidence, not private clutter
A screenshot can expose the actual layout failure, but it can also expose an account name, a private message, or an access token. Review material before sharing it and remove anything unrelated. The current public question form accepts text; it does not include a file-upload control. Describe the evidence in your message or provide an appropriate accessible reference. If additional files are needed, arrange the handoff through the reply channel. Do not assume the operator can see your device, your private storage, or something from a different conversation simply because you can see it.
Separate observations from assumptions
“The button disappears at 844 by 390” is an observation. “The phone is defective” is an interpretation. Keeping those apart makes troubleshooting faster and less destructive. The same principle applies to a business idea, a story, or a personal decision: explain what you know, what you suspect, and what you still need to establish. State your constraints explicitly. No new subscription. No replacement portrait. No changes to the approved wording. Good context narrows the work without trapping it inside an unsupported assumption. The result should be less guesswork, fewer unnecessary changes, and a response that respects the actual situation.
The most useful detail is often the one that rules out the wrong solution.