
The engineer looking after your systems needs years on the craft and years on your business. Neither one can be rushed.
When we assign a primary engineer to a Circle Square client, I’m thinking about two kinds of time. The time that engineer has spent learning the craft, and the time they’ll spend learning you.
Both matter, and neither can be rushed.
The confident mistake
The most expensive problems I’ve seen in IT weren’t caused by careless people. They were caused by confident people who were new.
I come across what they left behind all the time when we take on a new environment. A firewall rule that looked fine and quietly opened something it shouldn’t have. A migration that should have worked, and mostly did, except for the part that mattered. A fix for one problem that broke something else, because the person making it didn’t know the second thing existed.
None of those people were trying to do damage. They just didn’t have the hours yet to know what they didn’t know. In IT, the gap between “looks fine” and “is fine” is often where the outage lives.
How trust got earned on the flight line
I spent six years as a KC-10 crew chief at McGuire Air Force Base. You didn’t get trusted with a system because you’d read the manual. You got trusted after you’d done the work many times, with someone senior watching who had seen it go wrong. Check everything, assume nothing. Every job was signed for, and a signature meant something because of everything that came before it.
Our industry doesn’t always work that way, and I understand why. Good engineers are in high demand, and a certification plus a few months on a help desk can put someone in front of a firewall sooner than anyone would like. Certifications matter. They tell you someone passed a test. They don’t tell you whether that person has watched a change go sideways at 4 p.m. on a Friday and calmly put it back together.
Time on the craft
The first kind of time is experience. Years on the work, much of it alongside people who’d done it longer. It’s what lets an engineer look at a change and sense that something’s off before they can say exactly why.
You can’t speed that up. A single-barrel bourbon that names its barrel on the label spent every one of its years in that barrel, and nobody found a way to buy the time back. Expertise works about the same way.
Time on you
The second kind of time is specific to your business. What’s connected to what. Which systems you can’t run without. Why a rule that looks wrong on paper is there on purpose. Which vendor takes three calls to reach.
A senior engineer who has never seen your network can still make the confident mistake. Someone who knows your network but hasn’t put in the years can miss what a veteran would catch. You want both kinds of time in the same person.
How we put them together
At Circle Square, every client has a primary engineer who owns the account. Where we can, they already know your industry. We match by experience and by capacity, so the engineer has room to learn your environment properly instead of squeezing it in around too many other accounts.
Over the years, that engineer builds the second kind of time. They see your environment through upgrades, staff changes and the occasional bad day. When work touches something critical, it goes through someone with both the experience and the context.
This is No. 3 in the Circle Square Standard, the ten commitments every client can hold us to: every client has a person, and that person should have both kinds of time behind them.
Building that depth is slow, and it limits how quickly we can grow. It’s a tradeoff we’re glad to make. It’s also a big reason the clients who started with us almost six years ago are still with us today.
If you’d like to meet the people who’d be looking after your systems, I’d be happy to introduce you.
One standard. Every client. The door is always open.
Meet the people who own your account, and see where our standards come from, from the flight line to your front office. circlesquareconsulting.com/about-us