Reflections on Managing Cross-Functional Teams

Too often, I’ve been in a meeting where everyone agreed collaboration was essential—yet when it came to execution, things stalled. Silos persisted, friction rose, and progress felt painfully slow. A recent Harvard Business Review article highlights a frustrating truth: even the best-intentioned leaders struggle to work across functions. Why? Because traditional leadership development focuses on vertical leadership (managing teams) rather than lateral leadership (influencing peers across the business). The best cross-functional leaders operate differently. They don’t just lead their teams—they master LATERAL AGILITY: the ability to move side to side, collaborate effectively, and drive results without authority. The article suggests three strategies on how to do this: (1) Think Enterprise-First. Instead of fighting for their department, top leaders prioritize company-wide success. They ask: “What does the business need from our collaboration?” rather than “How does this benefit my team?” (2) Use "Paradoxical Questions" to Avoid Stalemates. Instead of arguing over priorities, they find a way to win together by asking: “How can we achieve my objective AND help you meet yours?” This shifts the conversation from turf battles to solutions. (3) “Make Purple” Instead of Pushing a Plan. One leader in the article put it best: “I bring red, you bring blue, and together we create purple.” The best collaborators don’t show up with a fully baked plan—they co-create with others to build trust and alignment. In my research, I’ve found that curiosity is so helpful in breaking down silos. Leaders who ask more questions—genuinely, not just performatively—build deeper trust, uncover hidden constraints, and unlock creative solutions. - Instead of assuming resistance, ask: “What constraints are you facing?” - Instead of pushing a plan, ask: “How might we build this together?” - Instead of guarding your function’s priorities, ask: “What’s the bigger picture we’re missing?” Great collaboration isn’t about power—it’s about perspective. And the leaders who master it create workplaces where innovation thrives. Which of these strategies resonates with you most? #collaboration #leadership #learning #skills https://lnkd.in/esC4cfjS

Over the years, I've discovered the truth: Game-changing products won't succeed unless they have a unified vision across sales, marketing, and product teams. When these key functions pull in different directions, it's a death knell for go-to-market execution. Without alignment on positioning and buyer messaging, we fail to communicate value and create disjointed experiences. So, how do I foster collaboration across these functions? 1) Set shared goals and incentivize unity towards that North Star metric, be it revenue, activations, or retention. 2) Encourage team members to work closely together, building empathy rather than skepticism of other groups' intentions and contributions. 3) Regularly conduct cross-functional roadmapping sessions to cascade priorities across departments and highlight dependencies. 4) Create an environment where teams can constructively debate assumptions and strategies without politics or blame. 5) Provide clarity for sales on target personas and value propositions to equip them for deal conversations. 6) Involve all functions early in establishing positioning and messaging frameworks. Co-create when possible. By rallying together around customers’ needs, we block and tackle as one team towards product-market fit. The magic truly happens when teams unite towards a shared mission to delight users!

Let's be honest: extensive cross-team coordination is often a symptom of a larger problem, not an inevitable challenge that needs solving. When teams spend more time in alignment than on building, it's time to reconsider your organizational design. Conway's Law tells us that our systems inevitably mirror our communication structures. When I see teams drowning in coordination overhead, I look at these structural factors: - Team boundaries that cut across frequent workflows: If a single user journey requires six different teams to coordinate, your org structure might be optimized for technical specialization at the expense of delivery flow. - Mismatched team autonomy and system architecture: Microservices architecture with monolithic teams (or vice versa) creates natural friction points that no amount of coordination rituals can fully resolve. - Implicit dependencies that become visible too late: Teams discover they're blocking each other only during integration, indicating boundaries were drawn without understanding the full system dynamics. Rather than adding more coordination mechanisms, consider these structural approaches: - Domain-oriented teams over technology-oriented teams: Align team boundaries with business domains rather than technical layers to reduce cross-team handoffs. - Team topologies that acknowledge different types of teams: Platform teams, enabling teams, stream-aligned teams, and complicated subsystem teams each have different alignment needs. - Deliberate discovery of dependencies: Map the invisible structures in your organization before drawing team boundaries, not after. Dependencies are inevitable and systems are increasingly interconnected, so some cross-team alignment will always be necessary. When structural changes aren't immediately possible, here's what I've learned works to keep things on the right track: 1️⃣ Shared mental models matter more than shared documentation. When teams understand not just what other teams are building, but why and how it fits into the bigger picture, collaboration becomes fluid rather than forced. 2️⃣ Interface-first development creates clear contracts between systems, allowing teams to work autonomously while maintaining confidence in integration. 3️⃣ Regular alignment rituals prevent drift. Monthly tech radar sessions, quarterly architecture reviews, and cross-team demonstrations create the rhythm of alignment. 4️⃣ Technical decisions need business context. When engineers understand user and business outcomes, they make better architectural choices that transcend team boundaries. 5️⃣ Optimize for psychological safety across teams. The ability to raise concerns outside your immediate team hierarchy is what prevents organizational blind spots. The best engineering leaders recognize that excessive coordination is a tax on productivity. You can work to improve coordination, or you can work to reduce the need for coordination in the first place.

I can tell you what leading cross-functional teams has taught me about breaking down silos. Early in my career, I thought that if I just got the right engineers, the perfect product managers, and top-tier program managers, magic would happen. Easy, right? Well… not exactly. I didn’t realize that each group had its own language, priorities, and ways of communicating. The result? There was a lot of head nodding in meetings, but then everyone would go back to their corners to do their own thing. It’s no wonder we couldn’t move the needle. I’ll never forget one project in particular. The engineers were deep into solving technical issues (and having fun with it), product was focused on the customer experience (which, of course, led to endless feature requests), and program management just wanted it all delivered on time (preferably yesterday). Each team was doing great work in their silo, but we weren’t aligned. The fix? Once we stopped treating these groups like separate kingdoms and started operating like a team with one mission, things changed. I made it a point to bring the engineers into customer discussions, get product involved in technical decisions, and have program managers understand why a delay wasn’t just a bottleneck but a chance to build something better. It wasn’t about flattening the org -- it was about flattening the conversations. When product, engineering, and program actually started talking, we didn’t just hit deadlines-- we built something better. And suddenly, that “magic” I thought would happen? It did. Breaking down the silos wasn’t easy. It took time, trust, and a lot of awkward cross-functional conversations. But, the payoff was better products, stronger teams, and more alignment across the board. So, here’s my question to you: How do you break down silos in your organization? What’s worked (and what hasn’t)? Drop a comment -- I’d love to hear your stories about getting product, engineering, and program to work together.