Spiceworks Community Digest: A matter of control

We’ve all been there: you step into a new job and find that the IT environment is a chaotic mess of old systems and duct-tape fixes. You start cleaning things up by replacing ancient gear, tightening security, and setting up proper protocols only to have your progress met with resistance. This isn’t just a technical problem, especially when a former IT employee starts trying to undermine you.

This dilemma was the topic of a recent post to our Dear SpiceRex series on the Spiceworks Community, an anonymous platform for IT pros to ask for help. A community member wrote in with their story of inheriting a poorly managed network and facing a power struggle over a new hire getting top-level access. The community, as it usually does, rose to the occasion, advising on navigating a difficult situation, blending security principles with career wisdom.

The power struggle and the principle of least privilege

The request for top-level access for the new hire was a massive security risk and likely a “power grab” by the former IT employee. The advice was unanimous: stick to the principle of least privilege.

• HulkSmash: “Has anyone there heard of the Least Privilege Principle? Only give people exactly what they need to do their job.”
• computerdave: “If this coworker is no longer in IT then they should have no authority to request or make demands. The new hire should not be given more permissions than they need to complete their duties… A wolf in sheep’s clothing is still a wolf.”
• Repairatrooper: “It is very possible that someone at the remote site (not the new hire) is trying to run an end game and sees this new hire as someone they can control and manipulate.”

The new hire: Friend or foe?

The second part of the dilemma was whether the poster should take on the new hire as a direct report. On one hand, it’s more work. On the other, the community saw it as a strategic win. By taking charge, they could prevent a future crisis and advance their own career.

• Suzanne (Spiceworks): “I think getting the new person under your wing and making sure they know the rules might be a good thing… so that it won’t turn bad?”
• Stark: “Having them under you, you can teach them the proper way to manage the remote site and guide them through it better then that coworker.”
• lcg86: “You can then set the boundaries and objectives. If new hire wants to remain employed, they will need to perform for you, not the old IT guy.”
• Random Parts: “I echo others and also would suggest the new hire report to you, so you can show him the IT way, instead of the chaos anything goes way.”

Overall, the advice from the community was to trust your gut, document everything, and take control of the situation. By doing so, you can prevent a future crisis and build a better career for yourself. What do you think? How would you handle this situation? Head over to the Spiceworks Community and join the conversation to share your advice!