Hi friend,
We hope this month's newsletter finds you enjoying some summer breathing room whether you're on vacation, just getting back, or somewhere in between.
As we start in on the back half of the year, one theme keeps coming up in our conversations with IT leaders: supporting multiple locations becomes more complex the longer you operate at scale.
Retail often gets attention here, but the pattern is consistent across distributed environments like healthcare systems, hospitality and hotels, financial services, auto dealerships, and restaurants.
Whether you're managing stores, branches, campuses, clinics, or offices, the same issues tend to emerge over time:
-
Technology standards and setups change from one location to the next.
-
Vendors keep multiplying.
-
Devices move, disappear, and age out across hundreds of sites.
-
Routine moves, adds, and changes create more exceptions than consistency.
-
Unreliable connectivity and experiences kill trust for everyone, from team members to clients and customers.
The challenge is how these issues compound.
As environments grow, complexity accumulates. And once it reaches a certain point, it starts shaping how much time your team members can spend on strategic work and upskilling versus day-to-day stabilization.
For many organizations, it also costs millions in operational inefficiency across vendor management, outage-related revenue loss, delays and bottlenecks, and talent retention.
The IT leaders who manage this most effectively don’t treat it as a collection of separate issues.
They address it as a distributed operating model challenge.
We explore this in a recent blog, and while the examples are from retail, it comes to mind as a useful lens for any organization managing multiple locations at scale. It looks at how this complexity builds over time, why it’s costing organizations millions, and the operating models IT leaders are using to address it.
