Start With a Clear Problem

Start with the smallest accurate statement. Does an app close when you open it? Does a page stay blank? Does a device fail to charge? Does the problem happen on every network or only one? Specific language narrows the next step and makes support easier later.

Note timing and scope. When did you first notice it? What were you trying to do? Does it happen every time, only with one file, one person, or one location? A pattern matters more than your first theory about the cause.

Separate the symptom from the explanation. ‘The printer says offline’ is an observation. ‘The printer is damaged’ is a conclusion you may not yet be able to support. Holding the difference reduces rushed changes that create more confusion.

Capture the details safely. A screenshot of a non-sensitive error, the exact wording of an alert, or a short note of the steps that led to it can be enough. Do not capture or share passwords, codes, personal records, or private conversations just to document a problem.

Choose one outcome. You may only need the app to open, a file to send, or an account to sign in. Keeping the goal small helps you know when a test has actually worked.