About Us – Office Proofed
I spent more than a decade inside small and mid-sized offices watching the same problems repeat. Not the dramatic, movie-style breaches. The ordinary ones. Someone reused a password. Someone clicked a login page that looked almost right. Someone brought a personal laptop onto the network because it was easier than waiting for IT. Someone left. No one revoked the accounts. A week later we were cleaning up the mess.
I was the person who got the call after those moments. First as an IT operations manager for a regional professional-services firm in Madison, Wisconsin, later coordinating security and compliance for other small-business environments. My job was never to design enterprise-grade architecture. It was to translate risk into something managers and employees could actually live with on a Tuesday morning when the real priority was still serving clients.
Madison is a practical place. People here run firms, agencies, clinics, and accounting offices. They are smart and busy. Most of them do not have a full-time security team. They have an operations lead, an office manager, or a hybrid IT person who already wears six other hats. That is the world I know best.
What the notebook taught me
I keep a notebook. Not a fancy system. Just a running list of avoidable problems I have watched unfold more than once. Reused passwords that turned into full account takeovers. Unmanaged devices that introduced malware. Offboarding that stopped at collecting the laptop and forgot the cloud accounts. Vendor demos that sounded perfect until the first week of actual use, when half the team found workarounds because the tool was too complicated.
The pattern is almost always the same: the risk was real, the solution was available, and the gap was that nobody had translated the security requirement into language and steps that fit the actual workflow of the office. Fear-based messages rarely help. Overly technical policies rarely stick. What works is making the safer choice the easier one.
How the work changed
Over time the questions shifted. Early on it was “Can you fix this?” Later it became “How do we stop this from happening again without slowing the whole office down?” I spent years evaluating endpoint tools, rolling out MFA, writing basic policies that non-technical managers could enforce, and sitting in the room after an incident while people tried to figure out what to do first.
Those years left me with a strong preference for boring, defensible setups over impressive-looking ones. A tool that the team will actually keep updated and that managers can explain in plain English is almost always more valuable than a feature-heavy platform that only the security specialist understands.
Why this site exists
Office Proofed is the place where I write down the practical version of that experience. It is written for the people who still have to run the business while trying to keep the doors locked. Not for CISOs at Fortune 500 companies. For the 15-person agency, the accounting firm, the hybrid team that works from home, coffee shops, and a small office, and the operations manager who just wants fewer blind spots.
I write about the risks that show up in real workplaces, how to choose antivirus and related tools without getting lost in marketing, the lightweight policies that actually matter, what to do in the first hour of an incident, and the daily habits that quietly lower exposure. The goal is always the same: help ordinary offices become a little more defensible without turning security into a second full-time job.
Security gets easier when the rules make sense.
— Grant Dorsey
Office Proofed
Madison, Wisconsin