Why I Build Teams Like Architecture Projects
As someone who started in architecture before shifting into technology and operations, I've discovered that building teams follows the same fundamental principles as designing buildings. You need a solid foundation, clear sight lines, and every element must serve both form and function. My engineering background taught me to think systematically, but architecture showed me something deeper: great structures emerge when you balance technical precision with human needs.
This philosophy shaped how I approached team building during my years as COO at various technology companies. I don't just fill positions. I design organizational structures where people can do their best work while serving the company's mission. The process starts with understanding the load-bearing requirements of each role, then figuring out how those roles connect to create something stable and scalable.
When I joined a mid-stage fintech company in 2019, they had 47 employees scattered across six departments with unclear reporting lines. It was like walking into a building where the support beams were randomly placed. Talented people were working hard, but the structure couldn't handle growth. Revenue was stalling despite strong market demand, and employee turnover was creeping up.
My first step was mapping the actual workflow, not the org chart. I spent two weeks shadowing different teams, watching how decisions moved through the company. The sales team couldn't get technical questions answered quickly. Product development was happening in isolation from customer feedback. Finance was chasing down approvals from people who didn't understand the context. Classic structural problems.
Instead of reorganizing immediately, I applied what architects call "adaptive reuse." We kept the existing talent but redesigned how they connected. I created cross-functional pods of four to six people, each responsible for a complete customer outcome. Sales, product, engineering, and operations sat together. Decision-making authority moved to the pod level for everything under $10,000.
The results showed up within three months. Customer response time dropped from days to hours. Feature requests moved from idea to implementation 40% faster. Employee satisfaction scores jumped because people could see their direct impact on customer success. We'd taken the same materials and created a structure that could handle much more weight.
This approach has guided every team I've built since then. You can't just hire great people and hope they figure out how to work together. You need to design the connections, the communication paths, and the decision points as deliberately as you'd plan the electrical and plumbing systems in a building. The human elements matter just as much as the technical ones.
Looking ahead, I think this architectural approach to team building becomes even more critical as companies grow faster and work becomes more distributed. The old command-and-control hierarchies are like designing buildings that can only handle one type of weather. Today's organizations need to be both stable and flexible, ready for conditions we haven't seen before.