Insights / Articles & guides

Business technology, explained

The Same IT Problem Keeps Returning. What Should You Record?

Staging editorial review.

A useful first conversation starts with a clear description of what is happening. You do not need to diagnose the cause or choose a replacement product before asking for help.

Describe The Interruption

Record what the person was trying to do, what happened instead and when it occurred. Is the problem constant, occasional or linked to a particular task?

Identify The Scope

Is one person affected or a whole team? Is the issue on one device, an application or a shared connection? These details help define the discussion without assuming the cause.

Explain The Business Impact

Describe the work that is delayed and any deadline involved. Note recent changes you know about, and what has already been tried. Avoid repeatedly changing settings without recording what changed.

Share Information Carefully

An error message can be useful, but screenshots may contain customer names, account information or confidential documents. Remove those details before sharing. Never include passwords in a website enquiry.

Bring One Clear Example

Use the IT-problem form to explain the issue and the affected work. An enquiry starts a conversation; it does not promise a diagnosis or a resolution time.

Further reading: Microsoft troubleshooting documentation.

Discuss a recurring IT problem →

Turn The Question Into A Useful Next Step.

Explore business challenges, try a self-check or talk to T Strategy.