How do I handle staff blaming me for problems in an inherited IT setup?

November 16, 2026 5 answers
Asked by 5y!foldgrommet_394

I'm the only IT person at a small company, and some staff are blaming me whenever something changes or breaks. I flagged a security concern about external chat access but haven't changed the policy. Now they're saying I removed an external user, although an audit event names someone else.

My manager supports me but isn't technical. How can I address the accusations and raise security risks without making the relationship worse?

Answers

7d+socketlantern_526

Keep your manager in the loop, but make the explanation easy to act on. Separate what you proposed from what you actually changed, then give them a short timeline of the reported issue and what the audit record shows.

Ask your manager to help set expectations for how concerns get raised. A meeting with the affected staff might help if the goal is to understand their workflow and agree on how to report problems, not to put anyone on trial. Having your manager there also means you aren't handling the people side alone.

Reply to this answer
RUSTY~RIVET

Be careful with the audit event. A name attached to an event is useful evidence, but check the event type, timestamp and details before saying that person deliberately removed anyone. It may not explain every part of what happened.

Ask for the affected user's details and when the issue occurred, then compare those with the relevant logs. If there are supposedly more removals, get examples and check those too. A report showing one event is a finding, not necessarily proof that no other issue exists. The other organization's settings are another possibility, but they're not a confirmed cause.

5d~socketladder_742:

It may help to describe the result as what the record shows rather than who is at fault. That keeps the investigation focused on getting the chat working.

Reply to this answer
c.638!tagwinder

Start a simple change log. Record proposed and completed changes separately, including the reason, approval, timing and expected impact. Tell affected staff ahead of a change when possible, and keep a record of what was communicated.

That gives you something concrete to check when someone says a problem started after an IT change. It also makes actual changes less surprising for everyone.

Reply to this answer
_v29+ctrlspoke.8

You weren't wrong to flag external access as a risk. But an allowlist is a business decision too, since it can interrupt legitimate communication. Explain the exposure and the possible options to your manager, including who might be affected, and get agreement before changing the policy.

Don't describe the proposal as if it's already been implemented. That distinction matters both for trust and for troubleshooting this particular complaint.

Reply to this answer
4v~drumspanner_729

Try treating the complaints as support requests first, even when the blame is annoying. Ask what stopped working, when it happened and who was affected. Follow up with what you found and the next step.

If the accusations keep escalating despite that, let your manager deal with the conduct side. You can be responsive without accepting responsibility for a change you didn't make.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions