Every Circle Square environment review starts by assuming something will fail. The goal is making sure one failure never takes the whole business down with it.
When a Circle Square engineer looks at a new environment for the first time, we start with one assumption. Something in here is going to break. Our job is to find out what, and to make sure that when it does, the business keeps running.
I picked that habit up on the flight line. I spent six years as a KC-10 crew chief at McGuire Air Force Base, and the rule there was check everything, assume nothing. The aircraft carried redundancy in almost every system that mattered. Nobody expected parts to fail on a schedule. But the cost of being wrong was measured in people, and you don’t want to learn at altitude that your only backup was the thing that broke.
The single thread
Most office environments grow one decision at a time, and each decision makes sense when it’s made. Over the years, that leaves single threads holding up important things.
One internet connection. One server in a closet that runs the accounting system, the file shares and the printers. One person who knows the admin password. A backup that copies to a drive sitting next to the server it protects, in the same building, on the same power, exposed to the same fire, flood or ransomware.
None of that is a sign of a careless business. It’s usually a sign of a busy one. But each single thread is a spot where one failure turns into a very long day.
There’s an old hand saddle stitch that runs two threads through every hole from opposite sides, so if one breaks, the seam still holds. That’s the whole idea in one picture: assume something will break, and build it so one break doesn’t take everything with it.
A copy is not a plan
Backups are where people feel safest and are often least covered. They have a backup. The job report says “success.” But a backup is a copy. A plan is how you get back to work.
A copy tells you the data exists somewhere. A plan tells you which systems come back first, how long that takes, who makes the calls, where people work in the meantime, and what each hour of waiting costs. Most businesses have the first and assume it covers the second.
What it looks like on a real day
One of our clients, a law firm, had a security incident. Downtime was held to an hour or two. Other clients of ours run with significant redundancies for the same reason: they can’t stop, and they’d rather put the second thread in place before they need it than after.
Nobody enjoys paying for something they hope never to use. I understand that. But for a business that runs on billable hours, appointments or orders, an hour of downtime has a real dollar figure attached. Once you know that number, redundancy starts to look a lot less like overhead.
That’s why we built the Downtime Ledger. It takes about 60 minutes and uses your numbers, and you keep the result. Even if you never work with us, you’ll know what an hour costs your business.
How we build it
At Circle Square, the rule is simple. If one thread is holding up something important, you should know about it, in writing.
In practice that means backups that run daily, with copies both onsite and in the cloud, so your data lives somewhere other than your building. It means recovery verified every day, because a backup you’ve never restored is a guess. It means restore tests on a schedule, with the results shared with you instead of filed away.
On top of that sits a written continuity plan, something your leadership team can read and use on the worst day of the year. If the gaps are too big to write a real plan yet, you get a written gap list instead, so you know what’s missing and what it would take to close it.
This is No. 2 in the Circle Square Standard, the ten commitments every client can hold us to: every client has a plan. A report that says the backup ran doesn’t count.
We don’t promise uptime. We engineer for it. If you’d like a second set of eyes on where your single threads are, ready now or just curious, I’m happy to take a look.
One standard. Every client. The door is always open.
See how Circle Square handles backup and disaster recovery: daily backups onsite and in the cloud, daily recovery verification, and a written continuity plan with scheduled restore tests. circlesquareconsulting.com/backup-disaster-recovery