Collaboration Barriers in Tech Development

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.

Your technical team can build AI. Your business teams can't use it. The gap between them is killing your AI value… I've learned that the technical-business divide is one of the biggest barriers to AI success. ▶️ THE AI CAPABILITY CHASM: 🔹 Technology Side: Can build sophisticated models, knows the latest architectures, understands model performance metrics and integration. 🔹 Business Side: Understands customer needs, operational realities, regulatory constraints, and value creation. ▶️ THE GAP: 💠 Technical teams build what they can build 💠 Business teams ask for what they think is possible 💠 Neither fully understands the other's domain ▶️ THE RESULT: 💠 AI solutions that are technically impressive but operationally useless… 💠 OR business requests that are technically naive and infeasible. ▶️ WHAT’S NEEDED: BRIDGE BUILDERS 💠 Translators who speak both languages 💠 Product managers who understand AI capabilities and business problems 💠 Champions in business units who can articulate real needs 💠 Engineers who spend time in business operations, not just code 🔹 The Builder’s Architecture: Design systems that business users can configure and refine without technical intervention. The AI should adapt to business logic, not require re-engineering for every change. 🔹 The Educator's Development: The best AI teams have cross-functional business associates who understand AI. Build AI literacy in business teams and business literacy in technical teams. 🔹 The Optimizer's Investment: The highest ROI AI investment is often in bridge building – closing the capability chasm and ensure technical effort maps to business value. I've seen brilliant AI solutions shelved because business teams couldn't operationalize them. I've seen desperate business needs go unmet because technical teams didn't understand them. The chasm between costs millions. ▶️ OPPORTUNITY: 💠 The gap between technical AI ability and business operational reality creates technically sound solutions but are unusable or fail to achieve ROI. 💠 Investing in cross-functional bridge SMEs, and collaborative design processes capture more value from AI investments than isolated technical excellence. #Leadership #AI #FutureOfWork

I’ve found that most HealthTech founders assume innovation is their differentiator. In practice, it rarely is. The UK doesn’t lack technical brilliance or world-class research. What it lacks is translation – the ability to move from promising R&D to meaningful, sustained adoption inside the NHS. The hardest problems aren’t technical. They’re organisational. Structural, financial, and cultural frictions shape the pace of progress far more than the quality of the technology itself. Procurement is the clearest example. Despite endless reform attempts, it still prizes unit cost over value. I’ve watched technologies capable of saving millions across a pathway fail an affordability test because their upfront cost exceeded a local trust’s limit. It’s no surprise that nearly a third of suppliers now avoid NHS tenders altogether – the commercial terms just don’t work. Funding models make it worse. More than 70% of NHS trust leaders cite financial constraints as the main barrier to digital transformation. Even when solutions clearly deliver long-term savings, capital accounting rules often prevent reinvestment of those gains into operational budgets. The result is predictable: effective innovations that never reach scale because the fiscal space to adopt them simply doesn’t exist. Then there’s the human system. Clinical adoption depends less on technical brilliance and more on how technology fits the rhythm of care. Too often it adds friction – extra logins, duplicate steps, more admin. Around one in three trust leaders still call poor IT infrastructure a critical barrier. And culture matters just as much. Clinicians’ scepticism toward opaque AI tools isn’t resistance. It’s accountability. Trust has to be earned through transparency, evidence, and co-development. The technologies that scale are the ones that integrate clinicians early, turning potential critics into advocates. Yes, there are positive shifts. NICE’s move to consider cost-effectiveness, not just cost-saving, is significant. Regulatory agility has improved. But the underlying system frictions remain. The UK is still a world-class testbed, not yet a world-class market. After two decades, my conclusion is simple: HealthTech success in the UK isn’t about innovation quality anymore. It’s about system mastery. The winners will be those who can navigate NHS economics, align incentives, build trust, and embed change deep within clinical practice. The frontier, as I see it now, isn’t technical. It’s organisational. P.S. If you’re a HealthTech founder, DM to explore how to navigate the system, not just build for it.

𝗛𝗼𝘄 𝘁𝗼 𝗕𝗿𝗲𝗮𝗸 𝗗𝗼𝘄𝗻 𝗦𝗶𝗹𝗼𝘀 𝗶𝗻 𝗠𝗲𝗱𝗧𝗲𝗰𝗵 𝗗𝗲𝘃𝗲𝗹𝗼𝗽𝗺𝗲𝗻𝘁: (𝗖𝗿𝗲𝗮𝘁𝗶𝗻𝗴 𝗰𝗿𝗼𝘀𝘀-𝗳𝘂𝗻𝗰𝘁𝗶𝗼𝗻𝗮𝗹 𝗵𝗮𝗿𝗺𝗼𝗻𝘆 𝘄𝗶𝘁𝗵𝗼𝘂𝘁 𝘁𝗵𝗲 𝗵𝗲𝗮𝗱𝗮𝗰𝗵𝗲𝘀) Ever notice how Quality, R&D, Regulatory and Marketing teams seem to speak completely different languages? This disconnect isn't just frustrating, it's costing your medical device company time, money, and potentially regulatory approval In my personal experience, I've seen how departmental friction can derail even the most promising innovations 𝗧𝗵𝗲 𝗥𝗲𝗮𝗹 𝗖𝗼𝘀𝘁 𝗼𝗳 𝗦𝗶𝗹𝗼𝘀 👉 Delayed submissions and market entry 👉 Regulatory surprises late in development 👉 Documentation rework and compliance gaps 👉 Increased development costs 👉 Team frustration and burnout Here's how to create seamless collaboration across your MedTech organization: 𝗦𝘁𝗲𝗽 𝟭: 𝗘𝘀𝘁𝗮𝗯𝗹𝗶𝘀𝗵 𝗖𝗿𝗼𝘀𝘀-𝗙𝘂𝗻𝗰𝘁𝗶𝗼𝗻𝗮𝗹 𝗚𝗼𝘃𝗲𝗿𝗻𝗮𝗻𝗰𝗲 Create a development council with representatives from Quality, Regulatory, R&D, Manufacturing, Marketing and Clinical. Meet bi-weekly with a structured agenda (top tip keep the minutes to use towards management reviews). 𝗘𝘅𝗮𝗺𝗽𝗹𝗲: A Class II device manufacturer implemented this model and reduced their development timeline by 30%, if not more, by identifying regulatory concerns during concept phase rather than pre-submission. 𝗦𝘁𝗲𝗽 𝟮: 𝗜𝗺𝗽𝗹𝗲𝗺𝗲𝗻𝘁 𝗦𝘁𝗮𝗴𝗲-𝗚𝗮𝘁𝗲 𝗥𝗲𝘃𝗶𝗲𝘄𝘀 𝘄𝗶𝘁𝗵 𝗔𝗹𝗹 𝗦𝘁𝗮𝗸𝗲𝗵𝗼𝗹𝗱𝗲𝗿𝘀 Don't move to the next development phase without formal sign-off from every department. This prevents costly backtracking 𝗘𝘅𝗮𝗺𝗽𝗹𝗲: During a stage-gate review (Design Review), a clinical specialist identified that the intended claims presented by the regulatory team would require further clinical data. By catching this early, the company adjusted their development plan rather than facing a surprise 6-month+ delay come submission time 𝗦𝘁𝗲𝗽 𝟯: 𝗖𝗿𝗲𝗮𝘁𝗲 𝗮 𝗦𝗵𝗮𝗿𝗲𝗱 𝗗𝗲𝘃𝗲𝗹𝗼𝗽𝗺𝗲𝗻𝘁 𝗟𝗮𝗻𝗴𝘂𝗮𝗴𝗲 Develop a glossary of terms that bridges departmental jargon. This prevents miscommunication that leads to rework. 𝗘𝘅𝗮𝗺𝗽𝗹𝗲: One client I worked with created a “MedTech Translation Guide” with input from each department. Not only did it reduce confusion, but it also built mutual respect engineers finally understood what the regulatory team meant by “intended use” and marketers stopped using terms that could trigger a knock on the door by Competent Authorities 𝗧𝗵𝗲 𝗕𝗼𝘁𝘁𝗼𝗺 𝗟𝗶𝗻𝗲? When this is done right, it accelerates development, strengthens compliance, and builds a more engaged team ✅ Faster to market ✅ Fewer compliance surprises ✅ Less internal friction If you're building your next-gen device and struggling with internal disconnects, it’s time to rethink how your teams work 𝘵𝘰𝘨𝘦𝘵𝘩𝘦𝘳 💬 I'd love to hear: How does your team keep cross-functional collaboration on track? #MedTech  #MedicalDevice #ProductDevelopment

Clearing the Systemic Barriers to Authentic Agility Most so-called Agile “transformations” (oh, if ever there were a misnomer) don’t fail because of the framework, tooling, or training - they fail because of deeply embedded impediments that fall into four systemic categories: Culture, Structure, Process, and Technology. These factors form a complex ecosystem, and if you treat them like separate problems, you’ll get performative agility without real adaptability. Agility isn’t a checklist or a destination. It’s a continuous journey of adaptation. Ignore the interplay between these domains at your peril. Barrier #1: Culture - The Invisible Operating System That Resists Change Problem: Traditional organizational cultures prioritize control over creativity, rewarding compliance while punishing exploration. The result is risk-averse bureaucracy. Questions: Do people feel safe admitting mistakes? Are failures learning opportunities or liabilities? Can the status quo be challenged without retaliation? Strategies: Foster psychological safety with blameless retrospectives and candor-friendly spaces. Celebrate smart failures. Promote learning with cross-functional exposure, rotation programs, and curiosity-based metrics. Barrier #2: Structure - Your Org Chart Is Showing Problem: Hierarchical, siloed structures slow decisions and disconnect teams from value delivery. Questions: Are teams aligned to customer outcomes or department KPIs? Where do decisions get made? How often do handoffs or approvals delay progress? Strategies: Align teams to value streams. Push decision-making closer to the work. Use lightweight governance and clearly delegated authority to reduce drag. Barrier #3: Process - When Following Rules Becomes Valuable Problem: Agile rituals become performative when teams confuse ceremony with value. Questions: Are Agile events energizing or exhausting? Do metrics reflect outcomes or activity? Are teams allowed to evolve their way of working? Strategies: Design outcome-oriented processes. Audit meetings regularly. Enable process experimentation within safe bounds. Focus on feedback loops, not rituals. Barrier #4: Technology - Tools as Thrust or Drag Problem: Legacy systems and fragmented tools create cognitive friction, slow feedback, and kill momentum. Questions: Do your tools promote collaboration or reporting? Can teams release frequently without manual overhead? Does tech accelerate flow or block it? Strategies: Invest in CI/CD, test automation, and self-service platforms. Retire tools that reinforce control or don't add value. Prioritize fast feedback, simplicity, and team autonomy in tool selection. Agility Isn’t Implemented - It’s Cultivated True agility requires systemic change across all four domains. It’s messy, non-linear, and context-dependent. Focus on domain interactions. Create safe-to-learn environments. Measure progress by adaptability, not just delivery. Don't chase transformation; enable evolution.

Why IT/OT Convergence Still Fails - Even Though the Technology Is Mature Technology isn’t the reason manufacturers struggle with IT/OT convergence. The tech is mature. The capability exists. Yet SIRI assessments show connectivity remains one of the lowest-scoring dimensions. So what’s really happening? 1. The Real Barriers Are Organisational, Not Technical Silos remain the biggest blocker. IT and OT still operate with different incentives, budgets and priorities: -> IT → security, standardisation, control -> OT → uptime, throughput, risk avoidance Without shared KPIs, governance or roadmaps, data stays fragmented. Process immaturity is another root cause. You can’t digitally integrate when processes are inconsistent or undocumented. Across SIRI assessments, the pattern is clear: 👉 Low process maturity = low connectivity. Legacy equipment and patchwork modernisation also create islands of automation instead of integrated value streams. And finally, weak architecture and governance mean companies start with tools (“Let’s buy MES/IoT”) instead of capabilities (“What do we need to run the business better?”). 2. What This Costs Manufacturers The value leakage is substantial: 👉 Lost productivity (5–20% OEE gap) Disconnected data slows root-cause analysis and improvement cycles. 👉 Higher operating cost (5–15% avoidable) With no real-time intelligence, maintenance stays calendar-based, buffers stay high and energy visibility is limited. 👉 Lower quality (2–5% avoidable scrap) No closed-loop quality = late detection and rework. 👉 Slower innovation Disconnected systems mean digital solutions take years to scale instead of months. In short: lack of connectivity = lost competitiveness. 3. How to Fix It: Build Vertical Integration, Not Just More Technology Top performers create vertical integration across: -> Shopfloor → Operations → Enterprise -> Automation → manufacturing systems → business systems A single value flow. What works: 1️⃣ Architect the business first. Define capabilities (predictive maintenance, digital quality, real-time scheduling) and build tech around outcomes. 2️⃣ Build a unified integration blueprint. A common data layer, shared security model and reference architecture for ERP, MES, SCADA and IoT eliminates fragmentation. 3️⃣ Align incentives with shared KPIs. Connectivity rate, downtime reduction, OEE uplift, data accuracy, traceability. When IT and OT share metrics, behaviour changes. 4️⃣ Use SIRI to sequence the journey. It provides a baseline, maturity score and prioritised roadmap - preventing random, disconnected initiatives. 5️⃣ Create a continuous improvement engine. Top performers turn data into daily decision-making cycles that close the loop and deliver sustained impact.

A founder vents to me: “We’ve spent a fortune on tools and platforms, and yet we’re still not moving fast enough. The teams are out of sync, progress is slow, and no one agrees on priorities.” This isn’t a technology problem—it’s a leadership problem. When tech investments don’t pay off, the knee-jerk reaction is to add more tools, restructure teams, or shift strategies. But the real blockers are often: • Misaligned decision-making • Conflicting priorities • Low accountability • Culture gaps that undercut change I’ve worked with dozens of teams who were sure the issue was their tooling—only to discover it was about leadership clarity, not software. What actually works: 1. Diagnose the real blockers—not just the symptoms 2. Align around outcomes, not just outputs or features 3. Use AI and data to improve leadership visibility, not just dashboards 4. Strengthen your leadership, not just your systems 5. Lead the change yourself—don’t expect tools to fix culture If this resonates, let’s talk. I help founders and execs cut through the noise, see what’s really going on, and get their teams executing at a higher level. #leadership #startupgrowth #executivecoaching #fractionalleadership #orgdesign #aiandhumans #mindfulwork

This week, I asked my AI PM students why so many promising AI/ML initiatives fail to secure executive sponsorship. Their answers were spot on: • "Unclear or unquantified business value" • "Too much focus on tech capabilities instead of business outcomes" • "Poor risk assessment for implementation challenges" But they missed one critical barrier I've encountered repeatedly across my work at T-Mobile, Nike, and now with enterprise clients at Greenscale AI: Technical jargon that creates communication barriers. I learned this lesson the hard way during my transition from healthcare to tech. In microbiology, precise terminology meant nothing to patients. Three approaches that have consistently worked for me: 1. Start with the "So what?" Frame AI capabilities in terms of business metrics executives already track. 2. Use analogies from the executive's domain. For example, when explaining ML models to your CFO, compare them to financial forecasting tools they already trust. 3. Create a jargon glossary— Maintain a simple reference that translates technical concepts into business outcomes. My healthcare background taught me that technical knowledge without effective communication rarely leads to meaningful action. #AIProductManagement #ExecutiveCommunication

The Truth About Silos in Tech Companies That No One Talks About 🤔 "We need better collaboration tools!" "Our teams need more meetings!" Wrong. Here's what 15 years in Professional Services taught me about silos: They're not a technology problem. They're a success problem. The inconvenient truth: Your most successful teams are often the biggest silo creators. Why? 3 counter-intuitive reasons: 1️⃣ Success Breeds Isolation High-performing teams develop their own "winning formula" They become protective of their methods Result: They stop learning from others The very excellence you praised created the wall you now fight 2️⃣ The Expertise Trap Deep technical knowledge creates communication barriers Experts start speaking their own language Everyone else nods politely, but alignment is gone Your best people might be your biggest communication bottleneck 3️⃣ The Scale Paradox As teams grow, they optimize for internal efficiency Each optimization becomes a brick in the silo wall Yesterday's solution becomes tomorrow's barrier Growth itself is silently sabotaging collaboration The Solution? Think Different: ✅ Reward Cross-Pollination Make "stealing" good ideas from other teams a KPI Celebrate those who adapt others' methods Create recognition for "bridge builders" ✅ Build Translators, Not Tools Identify people who speak multiple "team languages" Give them time to translate and connect Make translation a valued skill ✅ Design for Controlled Chaos Too much structure kills innovation Create intentional overlap between teams Allow for productive conflict The companies that win aren't the ones with the best tools. They're the ones who make collaboration part of their success metric. What unexpected silos have you discovered in your organization? Share below 👇 ♻️ Repost this to help others in your network. ➕ Follow me (Maxime Saporta) for more Leadership Content.

Technology and procurement teams often hit the same roadblocks when working in silos. Some are obvious, while others catch teams by surprise. Here are some of the most common barriers between both teams and practical ways to fix them: 𝗣𝗼𝗼𝗿 𝗰𝗼𝗺𝗺𝘂𝗻𝗶𝗰𝗮𝘁𝗶𝗼𝗻 𝗮𝗻𝗱 𝘂𝗻𝗰𝗹𝗲𝗮𝗿 𝗼𝘂𝘁𝗰𝗼𝗺𝗲𝘀: Lack of clarity on the business problem and success criteria can turn quick-turn initiatives into months-long projects that frustrate both teams and deliver underwhelming results. Procurement teams should embed Technology into their processes and hold regular check-ins to prevent any miscommunication. 𝗠𝗶𝘀𝗮𝗹𝗶𝗴𝗻𝗲𝗱 𝗽𝗿𝗶𝗼𝗿𝗶𝘁𝗶𝗲𝘀: the Technology team often laser-focuses on systems, while procurement focuses on cost. Both teams must establish common ground, setting shared goals and KPIs and planning together so trade-offs are clear from the start. 𝗦𝗶𝗹𝗼𝗲𝗱 𝗽𝗿𝗼𝗰𝗲𝘀𝘀𝗲𝘀 𝗮𝗻𝗱 𝗹𝗶𝗺𝗶𝘁𝗲𝗱 𝘃𝗶𝘀𝗶𝗯𝗶𝗹𝗶𝘁𝘆: Independent workflows create handoff gaps and duplicative efforts. Align workflows, involve Technology early in vendor selection, and ensure systems and contracts support business needs. Which barrier hits closest to home for your organization?