What happens when the systems that helped your business grow become the things holding it back?
For Rob Calvert, that question has become a central part of helping businesses navigate the realities of distributed teams.
As companies moved from local offices to teams spread across states, countries, and time zones, the technology supporting them became increasingly complex. Devices need to be protected. Data needs to be secured. Employees need access to the tools they depend on. And workflows need to keep functioning even when the people using them may never meet in person.
In this episode of Second Life Leader, Rob joins Doug Utberg for a wide-ranging conversation about distributed teams, cybersecurity, Apple-centric IT, software platforms, scalability, and the hidden complexity created when businesses build their operations around rigid systems.
At the center of the conversation is a simple question:
Are your systems flexible enough to survive the growth and change of your business?
TL;DR
The goal isn’t to eliminate problems. It’s to understand which problems you’re going to have and prepare for them before they become emergencies.
Rob’s perspective includes:
Distributed teams create new challenges around cybersecurity, devices, data, and intellectual property.
Avoid becoming completely dependent on one technology platform or vendor.
Balance user experience with security and scalability.
Moving data between platforms can be easier than recreating the workflows built around that data.
Every additional third-party tool can create another potential failure point.
Technology should support the way your business operates—not force your business into unnecessary rigidity.
Proof-of-concepts can expose problems and assumptions before implementation.
Complicated systems can make it harder for employees to consistently follow business processes.
Onboarding and offboarding become increasingly important as companies scale.
Major technology changes should be planned instead of compressed into an unrealistic timeline.
Sometimes the best immediate solution isn’t making a bad situation perfect—it’s creating enough room to eventually fix it properly.
The goal isn’t to build a system that never changes.
It’s to build a system that can change without breaking the business.
Memorable Lines
“You have to expect that some of these things are going to happen to you.”
“You can’t always win the battle. We very much believe you’ve got to pick the right tool for the job.”
“There is no way to expand a business without something being painful.”
“The technical decision is almost always the easiest one. Hardest one is the cultural impact and the work impact.”
“Every time you have to insert a third-party app into a workflow, that is a place where you are dependent on them staying up to date.”
“The worst way to deal with the problem is to ignore it.”
“I can make your situation suck less, but I can’t make it good in the timeline you’re giving me.”
Guest: Rob Calvert
Rob Calvert is the founder of Second Son Consulting, an Apple-centric IT consulting firm. He has been working in outsourced IT for more than two decades, helping businesses manage Apple environments, distributed teams, cybersecurity, devices, and technology systems.
His experience includes helping organizations adapt as their teams become increasingly distributed and as businesses scale across states and countries.
Rob also participates in the Mac Admins community, a global community of IT professionals focused on sharing knowledge, tools, and experience.
Why This Matters
For founders, executives, and growing companies, technology decisions can look deceptively simple.
Which platform should we use?
Can we eliminate this subscription?
Can we move everything into one system?
Can we customize this workflow?
But underneath those questions are people, processes, security requirements, company culture, and dependencies that can become increasingly difficult to change.
A system that works for a small company may not work the same way when that company reaches hundreds of employees.
A workflow that seems efficient today can become a bottleneck tomorrow.
And a platform that appears cheaper can sometimes introduce additional tools, dependencies, and security gaps that make the overall system more complicated.
One of the biggest ideas in this conversation is that the technical decision isn’t always the hardest decision.
The harder question is what happens to the people and processes around that technology.
When businesses change systems, they’re not just moving data.
They’re changing how people work.
And the more complicated the system becomes, the more difficult it can be for employees to consistently execute the processes required to keep it working.
For growing businesses, the lesson is simple:
Don’t wait until the system breaks to discover how difficult it is to change.
Plan for the problems.
Build flexibility into the system.
And give your business enough time to make changes properly.
You can’t eliminate the pain that comes with growth.
But you can decide whether that pain becomes a crisis—or simply part of the process of building something that lasts.
Listen to the full conversation with Rob Calvert on Second Life Leader.
