Collaborating Across Teams For User Experience Innovation

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.

Ensuring collaboration is central to a product's success during the UX strategy phase begins with uncertainty about where to start. ➡️ It's important to start by integrating resources and knowledge from various areas of expertise. Here's a combined approach on my experience to get a successful results and great user satisfaction rate 1️⃣ Get Smart Early in the Process: Involvement: Bring in PMs, Engineers, Designers, Researchers, and key stakeholders early to gain insights. Understanding: Focus on the "4W's" (Who, What, When, Where), technical impact, and project scope.
 2️⃣ Learn and Explore: Understanding Customer Needs: Identify customer pain points and their actual needs. Analysis and Metrics: Make assumptions, conduct competitive analysis, and define success metrics and current statistics.
 3️⃣ Define Problem: Validation and Conceptualization: Validate the problem, draft high-level concepts, and define hypotheses for testing.
 4️⃣ Design: Concept Creation: Develop low-fidelity (low-fi) concepts and involve researchers for testing. Collaboration: Show concepts to Tech and PMs, and address technical challenges.
 5️⃣ Re-iterate: Feedback and Refinement: Fix the main journey (happy path), take internal and external feedback, and implement changes. Testing: Conduct another round of testing.
 6️⃣ Hand off to Development: Finalization and QA: Design the final prototype, perform QA testing, and ensure all workflows are correct. Cross-Platform Check: Ensure designs are optimized for all viewports. Approval: Get sign-off from all parties before handing over to development.
 7️⃣ Launch and Monitor: Post-Launch Feedback: After launching, gather feedback through success metrics and third-party tools. Client and User Feedback: Seek feedback from real clients and conduct user interviews. Refinement: Address major feedback issues, prioritize, and monitor. Useful Resources ✅ Ux Vision — A vision is an aspirational view of the experience users will have with your product, service, or organization in the future. https://lnkd.in/gPPY-zPJ https://lnkd.in/g8Rc9pzp ✅ Outcome over Outputs — Work towards purposeful outcomes (problems solved, needs addressed, and real benefits) leads to better results. https://lnkd.in/gAFX_Wxw ✅ OKR in UX — Define objectives and measurable key results to guide and track UX work. https://lnkd.in/gDYvreN2 ✅ UX Goal Analytics — Focus on UX goals to drive analytics measurement plans, rather than tracking superficial metrics. https://lnkd.in/g3QmZqBd #UxStrategy #TransitionToUx #UxCoach #BeAvailable

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