One of the biggest projects I ever worked on was the Microsoft News Center rebuild at WebDevStudios.
38 separate sites. 16 languages. Nearly a decade of content migrated from a proprietary system into WordPress. Enterprise-scale, global reach, zero room for error. This was before anyone was putting enterprise WordPress on Azure at this scale-we were figuring it out as we went.
I was the engineering manager-which at a growing agency meant I was also the guy doing whatever it took to get the project over the line. Late nights. Power programming sessions. Working alongside team members when things got tight. Code reviews at midnight. That was the job, and I loved it.
Here’s what that project taught me about building things that actually work.
The Scope Nobody Talks About
When people hear “Microsoft project,” they imagine unlimited budgets and armies of developers. The reality was different. Yes, enterprise clients have resources. But they also have complexity that would crush most projects-and expectations that don’t leave room for excuses.
Here’s what the Microsoft News Center actually required:
38 Sites, One Platform
Each regional news center needed to function independently while sharing a common infrastructure. Updates to the core platform had to work across all 38 sites without breaking anything. Regional teams needed autonomy without chaos.
16 Languages, Proper Localization
This wasn’t just translation. Different regions have different content needs, different publishing schedules, different compliance requirements. The system had to handle right-to-left languages, different date formats, and content that varied significantly by region.
Editorial Independence at Scale
Microsoft’s communications teams around the world needed to publish without calling IT. They needed a system that empowered them to do their jobs without technical bottlenecks. Self-service, not helpdesk tickets.
Legacy Migration Without Data Loss
Years of news releases, press content, media assets, and archives had to move from the old system to the new one. Nothing could be lost. URLs had to redirect properly. Search had to still work.
What We Actually Built
We built a custom page builder before page builders were a thing. This was early 2010s-Gutenberg didn’t exist, and the visual builders we take for granted today were either primitive or nonexistent. Microsoft’s editors needed to create rich, media-heavy news pages without touching code.
So we built it. Custom blocks. Drag-and-drop layouts. Media management that could handle enterprise asset libraries. All within WordPress, extended to meet Microsoft’s specific needs.
The platform we built had to be powerful enough for enterprise needs but simple enough that non-technical editors could use it daily without training sessions or support tickets.
WordPress Multisite with WPML handled the multi-language, multi-site architecture. Azure hosting (which was relatively new for WordPress at that scale) provided the infrastructure. Custom development filled the gaps between what existed and what Microsoft needed.
The Hard Lessons
Enterprise projects teach you things that smaller projects don’t. Not because the principles are different-they’re the same-but because the consequences of getting things wrong are immediate and visible.
- Architecture decisions compound. A shortcut in the foundation becomes a nightmare at scale. What seems efficient on site #1 becomes technical debt across 38 sites.
- Documentation isn’t optional. When you’re building systems that other teams will maintain, clarity isn’t a nice-to-have. It’s essential.
- Edge cases multiply. The weird scenario that “probably won’t happen” will definitely happen when you have 38 sites in 16 languages. Build for the exceptions.
- Stakeholder management is project management. Technical excellence means nothing if you can’t communicate progress, manage expectations, and align people around solutions.
What Enterprise Taught Me About Small Business
Here’s what surprised me when I started working with smaller businesses: the principles that made Microsoft News Center work are the same principles that make a 5-person company run smoothly.
Clear systems scale down, not just up. Microsoft’s editors needed to publish without calling for help. Your small team needs to run without you micromanaging every step. Same principle. Different scale.
Data portability matters at every size. When Microsoft moved off their old system, nothing got lost. When you switch from one CRM to another, your contacts and history should come with you. Build for migration from day one.
Architecture decisions matter. 38 sites or 3 locations-the structure matters. Build it right once, and growth doesn’t break everything. Build it wrong, and every expansion creates new problems.
The Through Line
I’ve built sites that millions of people use. Platforms for the NBA, Microsoft, Campbell’s, Care.com. Projects that had to work perfectly because the stakes were real and the audience was massive.
But the work I do now for small and medium businesses? Same principles. Same attention to systems and architecture and doing things right. Just a different scale and a different context.
The Microsoft project taught me that complexity is manageable if you respect the fundamentals. My work since then taught me that most businesses skip the fundamentals and wonder why things feel chaotic.
Whether it’s 38 sites or one, 16 languages or your local market, the questions are the same: What’s the system? How does it scale? What happens when things change?
Whatever it takes to get the project over the line. That’s been the approach for twenty years. That hasn’t changed.
