What Tom Brady taught me about your IT infrastructure
I was listening to a podcast last week, one of those late-night drives where the right content lands at exactly the right moment and the host dropped a line that I had to listen to twice.
He said: “A great team will always outperform a group of individual players, no matter how talented those individuals may be.”
Then he played a clip of Tom Brady.
Now, I know. Sports analogies. Construction people have heard them all. But stick with me for a second, because Brady wasn’t talking about football. He was talking about how championship teams are built, and what he said maps almost perfectly onto something I see broken in Arizona construction firms on a weekly basis.
Brady’s Take on Stars vs. Champions
In the clip, Brady talked about how the Patriots would draft “people before players.” Meaning they cared more about intangibles: coachability, commitment, willingness to sacrifice for the team, than they did about raw talent.
He said: “Champions do what stars aren’t always willing to do.”
He talked about receivers who would crack safeties. Running backs who’d step up in pass protection when they didn’t have to. Defensive linemen eating double teams so a linebacker could make the play. Nobody scoring touchdowns on those plays. Nobody getting the highlight reel. But the team winning because everyone did their job and trusted the guy next to them.
And he made the point that a lot of athletes today are so focused on their individual stats, their personal brand, their contract numbers, that they’ll never be champions. Even if they’re stars.
“I would prefer to be on a team full of champions over a team full of stars.” - Tom Brady
Okay. So What Does This Have to Do With Your IT?
Everything.
Here’s what I’ve noticed in my years working with Arizona contractors: most firms have technology stars. They’ve got one guy who’s exceptionally proficient in Procore. One estimator who can do takeoffs blindfolded. A project manager who’s built a spreadsheet tracking system so good it should be a product.
But their tech stack? Their actual IT infrastructure? That thing is not playing for the team.
It’s playing for itself.
- The backup software that runs every night but nobody has ever tested a restore from. It logs a green checkmark and calls it a win. Individual stats look great. Until a server fails on a Tuesday morning before a concrete pour and nobody can pull a file.
- The Autodesk environment that was set up three years ago by an IT guy who no longer works there and didn’t really understand the unique environment. It technically works. Mostly. But the RFI workflow breaks randomly, the field team has given up on it, and the PM just emails photos from his phone instead. That tool opted out of the team.
- The endpoint security that sends reports to an inbox nobody checks. It’s doing its job. In a silo. While ransomware groups scan your network for the one device that skipped last Tuesday’s patch.
Individual players, doing individual things, with no real coordination toward the outcome.
What a Technology Team Actually Looks Like
When your IT is working as a team, it looks like this:
- Your backup solution doesn’t just back up, it gets tested. Regularly. Someone confirms a restore worked. Everyone on the team trusts the backup the way Brady trusted his offensive line.
- Your security stack talks to itself. Endpoint protection, email filtering, DNS security, layered protection, they’re not three separate products generating three separate reports. They share information. One flags a threat, the rest respond.
- Your cloud environment and your field devices are on the same page. The super in the field has the same access to project files as the PM in the office. Not a workaround. Not a VPN that only works when Mercury is in retrograde. The same access.
- Your software platforms are actually adopted. Procore, Autodesk, Bluebeam, they’re not installed, they’re used. By the whole team. Consistently. Which means the data in them is real, and decisions made from that data are good and you can effectively leverage AI and scale.
That’s a technology team. It’s not the most glamorous thing in the world to describe. But it’s what separates the firms that hum from the ones that scramble.
The Prima Donna Problem
The podcast host made a point about prima donnas that stuck with me. He said too many organizations tolerate a star player who doesn’t buy into the team culture because they think they need that individual to hit the number. And what ends up happening is the culture rots around them.
I see the same thing in tech. The prima donna isn’t always a person. Sometimes it’s a legacy server that everyone’s afraid to touch because “that’s where the accounting software lives.” Sometimes it’s a software tool the owner loves but that doesn’t integrate with anything else and creates an island of data nobody can reach.
The team works around it. The team compensates for it. And over time, workarounds become process, and broken becomes normal.
“When a technology is so fragile or so isolated that your team has built their workflow around its limitations, that’s not a tech problem. That’s a culture problem. And culture problems compound.”
What Brady Would Say About Your Next Tech Decision
When the Patriots evaluated a player, they weren’t just asking “can this person perform?” They were asking “will this person make the team better?”
Before your next technology purchase, those are both good questions. But the second one is the one most firms skip.
Can this tool perform its core function well? Sure. But does it integrate with what you already have? Does it create visibility or does it create another silo? Does it require tribal knowledge to operate, or can a new hire get up to speed in a reasonable amount of time? Does it help the whole firm get to the goal, or does it just make one department’s life easier while making everyone else’s harder?
Draft people, not players. Buy tools that play for the team, not just for themselves.
The Bottom Line
Tom Brady won seven Super Bowls. He’s not wrong about teams.
And the firms I’ve watched build genuinely great technology environments, the ones where operations run smoothly, where field and office are actually connected, where a ransomware event or a server failure is a recoverable inconvenience rather than an existential crisis, those firms built a team.
Not a collection of software subscriptions. Not a stack of individual tools filing individual reports. A team.
If you’re not sure whether your tech is playing for the team or playing for itself, that’s worth finding out. That’s what we do.
Ready to see if your tech stack is built to win, or just built to survive?
Book a Free Consultation Review with Computer Dimensions.
For over 20 years, Computer Dimensions has been the trusted IT partner for Arizona's architecture, engineering, and construction industry. We help AEC firms communicate better, collaborate smarter, and actually use the technology they've invested in. Because in construction, the tools only work if your team does.
IT Built For Builders.
