Managing networks and deploying change faster and safer

Managing networks well comes down to one habit: never make a change you cannot take back. Everything else I do follows from that.

Know what you have before you touch it

Every network I inherit starts the same way. Someone built it years ago, it mostly works, and nobody is quite sure why. Before I change anything I write it down: the gateway, every switch and access point, which port feeds which wall jack, and what lives on which segment. It is the dullest part of the job and it prevents the worst phone calls.

Segment so one mistake stays small

Cameras, door access, guest Wi-Fi, office computers and a livestream encoder should not share one flat network. I split them apart so a noisy device cannot take down the front desk. On a church campus I rebuilt with Ubiquiti UniFi gear, that separation is what lets the cameras, the door locks and the people in the office each do their jobs without stepping on one another.

Script the checks, not the fixes

Before and after every change I run the same short list: can the gateway see each switch, are the cameras recording, does the VPN come up, is DNS answering. A script does it in seconds and writes the result to a log, which beats my memory at the end of a long day. Automation can watch the network all day. A person decides what changes.

Make every change reversible

Back up the configuration. Change one thing. Test it. If it is wrong, put it back. I write the rollback note before I make the change, not after it goes sideways. The same rule applies at home, where my own gateway and VPN let me reach the archive server from the road. One careless step there could lock me out of my own building, so I make those changes one at a time too.

Faster comes from safer

It sounds backward, but the more reversible and checked each change is, the faster I can move. You stop dreading changes, so you make small ones often instead of one big frightening one every few years.

If you are running a network nobody wants to touch, that is usually the right place to start. The same discipline protects my video archive, which you can read about in safe archival compression. If you would like a second set of eyes on your own setup, get in touch.


Written with AI assistance. Every idea, opinion and experience here is mine. I just thrive on strategy and execution more than eloquent wordsmithing.

What are you trying to grow?

Tell us what’s happening and what would be better. You don’t need to know which division you need.

Start a conversation