this post was submitted on 17 Jun 2023
3 points (100.0% liked)

Sysadmin

5584 readers
1 users here now

A community dedicated to the profession of IT Systems Administration

founded 5 years ago
MODERATORS
 

Hi guys, I recently started working at a company with about 50 people that has grown to large for their current IT setup. They have no documentation or any SOPs. Has anyone been in a similar situation and how did you go about creating documentation, especially when you are new and don't fully understand all of the services they have in place?

Thankfully it's mostly a Microsoft shop and pretty low tech but there are dozens of exchange rules in place that no one knows why they exist or what they do, dozens of SharePoint sites with critical information strewn about them and so on. It's hard to think where to even start and decide what the best way to organize this information will be, and keep in a place a system where we will update it regularly. Any advice would be greatly appreciated.

top 1 comments
sorted by: hot top controversial new old
[–] badcommandorfilename@lemmy.world 1 points 1 year ago* (last edited 1 year ago)

One thing that worked for me in a similar situation was to enforce an "owner" tag or some kind of registry on everything.

Basically, if you set something up, change some configuration, whatever - put your email address on it.

Write a readme.md or wiki or guide too, but at the very minimum put your name down as the owner so that when someone comes along and wants to know if it's safe to change/upgrade/delete, they can find you and ask. If someone leaves, you can do a quick search and get them to handover/write up anything they were responsible for.