Cross-Functional Innovation Teams

“Let’s celebrate our differences!” — easy to say when you’ve never actually had to WORK through real differences. Here’s the thing: Real differences don’t feel like a celebration. They feel messy, uncomfortable, even threatening. 🧠 Our brains are hardwired to detect difference as potential danger. When someone thinks, works, or communicates differently than we do, our first instinct isn’t to embrace it—it’s to resist it. Recently, I worked with a team trapped in conflict for years. The problem wasn’t competence or commitment. It was cognitive diversity they didn’t know how to handle. 👉 One part of the team was task-focused—eager to get to the point and skip the relational aspects of collaboration. 👉 The other part was relationship-driven—prioritizing emotional connection and dialogue before diving into action. Celebrate their differences? Not likely. 🚫 The task-focused group saw the others as emotionally needy attention-seekers. 🚫 The relationship-driven group saw their counterparts as cold and disengaged. So, what changed everything? Not a shallow celebration of their diversity, but finding their common ground. 🚀 I used my D.U.N.R. Team Methodology to transform their conflict into collaboration: 1️⃣ D – Diversity: we explored their differences without judgment and recognized the strengths in both approaches. 2️⃣ U – Unity: we found their shared purpose—every one of them cared deeply about the team’s success, just in different ways. 3️⃣ N – Norms: we co-created practical norms that guided their interactions and set clear expectations. 4️⃣ R – Rituals: we introduced rituals to honor both styles while reducing friction and fostering collaboration. The real breakthrough? Not pretending their differences were easy, but building bridges through shared values. My honest take: If you’ve truly worked through real differences, you know it’s not about celebrating them—it’s about navigating them with care and intentionality. 💡 Celebrate your common ground first.  That’s how you unlock the power of team diversity. What’s your experience with managing real differences on a team? 🔔 Follow me for more insights on inclusive, high-performing teams. ___________________________________________________ 🌟 If you're new here, hi! :) I’m Susanna. I help companies build an inclusive culture with high-performing and psychologically safe teams.

Many senior leaders I work with care deeply about innovation. And still, they experience a tension they don’t always state out loud. Control vs. curiosity. Alignment vs. disagreement. They know innovation doesn’t come from everyone just doing what they’re told. But they also believe that too much freedom, without enough structure, can quickly turn into chaos. What they often do not realize is that they do not need to pick a side. Instead, they need to learn how to hold both at the same time. In my work, I’ve seen that innovative teams don’t try to get rid of dissent. They embrace it and shape it. And they don’t just tell people to “be curious.” They use practices that make curiosity possible, every day. Here are a few principles that help leaders navigate this tension: 1. Keep dissent about ideas, not people. The best debates focus on the work: the data, the assumptions, the trade-offs. Not egos, titles, or who’s “right.” When leaders stay open (especially when they’re being challenged) it gives everyone else permission to do the same. 2. Give curiosity clear boundaries. Curiosity actually works better with structure. Be clear about where experimentation is encouraged, what constraints matter, and when decisions are final. Too much freedom without clarity is overwhelming. Clarity creates room to explore. 3. Don’t mix learning moments with performance moments. If every conversation feels like a test, people stop taking risks. Say out loud when the goal is learning, reflection, or trying things out. And protect those spaces. 4. Reward contribution, not agreement. If people get ahead by agreeing, that’s what they’ll do. If they get ahead by improving thinking, raising risks, and expanding options, you’ll get better decisions. 5. Remember: culture follows behavior, not demands or promises. Curiosity isn’t what leaders say they want. It’s what they notice, what they ask about, and what they act on, especially when things get tense. To me, innovation does not mean letting go of control. It’s about using control more thoughtfully, in ways that leave room for learning, challenge, and discovery. Leaders who get this right build teams and organizations that keep learning long after today’s problems are solved. #teams #collaboration #control #innovation #rules #practices #tension #learning #leadership

𝗛𝗼𝘄 𝘁𝗼 𝗕𝗿𝗲𝗮𝗸 𝗗𝗼𝘄𝗻 𝗦𝗶𝗹𝗼𝘀 𝗶𝗻 𝗠𝗲𝗱𝗧𝗲𝗰𝗵 𝗗𝗲𝘃𝗲𝗹𝗼𝗽𝗺𝗲𝗻𝘁: (𝗖𝗿𝗲𝗮𝘁𝗶𝗻𝗴 𝗰𝗿𝗼𝘀𝘀-𝗳𝘂𝗻𝗰𝘁𝗶𝗼𝗻𝗮𝗹 𝗵𝗮𝗿𝗺𝗼𝗻𝘆 𝘄𝗶𝘁𝗵𝗼𝘂𝘁 𝘁𝗵𝗲 𝗵𝗲𝗮𝗱𝗮𝗰𝗵𝗲𝘀) 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

In transformation, how do you solve the conflict between a function owner having accountability just for their function and an end-to-end accountable owner having authority across functions? I’ve been giving this some thought. I believe we need to separate accountability for capability (functional owners) from accountability for outcomes (end-to-end owner), and then hard-wire how conflicts are resolved. 💡 Functional owners retain authority over standards, people, and domain execution. They control: 👉 How work is done within their function 👉 Technical standards, controls, and compliance within their domain 👉 Resource allocation inside their team They are accountable for quality of input, not the end business outcome. 💡 The end-to-end owner has decision rights over prioritisation and trade-offs. They control: 👉 Sequencing of work across functions 👉 Allocation of shared capacity where conflicts arise 👉 Acceptance criteria for what “good” looks like across the full flow 👉 Trade-offs between speed, cost, and risk at the system level They are accountable for outcome delivery, but they do not manage the functional teams day-to-day. 💡 A formal “tie-break” mechanism should be defined upfront. When there is a conflict: 👉 It escalates to a clearly defined forum (not ad hoc discussion) 👉The end-to-end owner has the final decision within agreed guardrails 👉 Functional owners retain veto only where regulatory/compliance thresholds are breached 💡 Incentives are aligned to shared outcomes, not just functional KPIs. 👉 If a function is only measured on local efficiency, it will rationally resist cross-functional trade-offs 👉 A portion of performance measurement needs to reflect contribution to the end-to-end outcome 💡 Constraints are made explicit, not negotiated repeatedly. 👉 Functions publish their non-negotiables (regulatory limits, capacity ceilings, architectural constraints) 👉 The end-to-end owner plans within those constraints rather than rediscovering them during delivery ✅ The underlying principle is: 👉 Functional owners control how, end-to-end owners control what and when, and governance defines who decides when they disagree What are my networks thoughts on this?

"Most leaders think their teams need to get better at change. The truth? Their teams need to get better at disagreeing." Across SEA, stakeholders keep telling me: "We can handle change. We just can't handle how fast everything changes." But here's what I see when I dig deeper: Teams don't break because change happens. Teams break because they can't adapt together. And the World Economic Forum December 2025 report confirms this: Flexibility will be critical economic skills from 2026–2030. Not new frameworks. Not better tools. Human capabilities. COMB has been solving this exact problem for nine years, long before WEF made it official. Earlier this year, I worked with a cross-functional team in crisis where marketing said product was too slow. Product said operations was too rigid. Operations said everyone dumped last-minute requests. Leadership labeled it "lack of adaptability." But during our COMB session, the real issue surfaced: A manager said honestly: "We don't struggle with change... We struggle because we don't trust how people will respond when we speak honestly." That was it. Teams cannot adapt to external uncertainty when they feel unsafe with internal uncertainty. Because adaptability isn't just technical. It's emotional. When people don't feel safe, they: ❌ Won't challenge ideas ❌ Won't ask crucial questions ❌ Won't disagree constructively ❌ Won't reveal blindspots ❌ Won't collaborate at speed This is why psychological safety isn't "soft culture work." It's the backbone of competitive advantage. For nine years, COMB has been developing what we call "soft power skills", the human capabilities that drive organizational adaptability. Long before WEF identified flexibility as critical, we've been training teams across Indonesia and Singapore to master constructive conflict, emotional regulation, and trust-building under pressure. Most teams avoid conflict because they only know destructive conflict: defensive reactions, personal attacks, shutdowns. But we teach the real engine of adaptability: Constructive conflict. Where teams learn to say: "I see it differently, here's why" or "Help me understand your constraints." When teams master constructive conflict: 💥 Speed increases dramatically 💥 Decision-making sharpens 💥 Innovation accelerates 💥 Client communication improves 💥 Silos dissolve naturally Because trust isn't built when people agree. Trust is built when people can disagree safely. What the WEF identifies, COMB operationalizes. From 2026–2030, companies will rise or fall on one capability: how well their people adapt to uncertainty together. Lead Beyond Yourself. Rise Beyond Limits. If your teams hesitate, avoid difficult conversations, or slow down when the world speeds up — is it really a skills issue or a safety issue? Ready to build adaptability as your competitive edge? Let's talk. #softpowerskills #teamadaptability #psychologicalsafety #futureskills #organizationalchange #cassandracoach

Conflict isn’t an enemy. Poor handling of it is. In healthy workplaces, tension will emerge, over priorities, personalities, power, and progress. The best leaders don’t fear conflict. They don’t avoid it. And they certainly don’t fan its flames. 🟨 They step in with steadiness. 🟨 They de-escalate with intent. 🟨 They create clarity where confusion could reign. If you're dealing with silent resistance, sharp emails, turf wars, or unspoken jealousy, consider this - it’s not the presence of conflict that derails a team. It’s the absence of skill in navigating it. Here’s a practical set of strategies that have worked for me and those I now work with - 🔷 Breathe Before You Speak. The fastest way to derail a conversation is to jump in too soon. Start by asking: “What might be happening beneath the surface?” 🔷 Get Clear on the Core Issue. Is this about control? Clarity? Respect? Ego? Naming the real issue helps everyone respond more wisely. 🔷 Stay Grounded, Even When It’s Personal. Notice your emotional cues. Respond from curiosity, not combat. It’s hard, and worth it. 🔷 Model Constructive Disagreement. Don’t shut down conflict. Shape it. When teams know how to disagree well, innovation follows. 🔷 Recognise the Subtle Signs of Jealousy. It’s rarely overt. But it can show up as snide comments, cold shoulders, or overcompensating. Be kind, be firm, and guard your energy. 🔷 Plan Before the Big Conversation. Walk in with your purpose clear, your tone calm, your first sentence ready & your boundaries in place. Handled with skill, conflict can become a catalyst for trust, better decisions, and a stronger, more honest culture. #Leadership #ConflictSkills #EmotionalIntelligence #CultureBuilding #Teamwork #LeadershipDevelopment

In leadership, every choice is a vote — for yourself, or for the system. Over three modules with Ankura Hospitals paediatric team, we built a journey: - Module 1: Self-awareness as the cornerstone of leadership. - Module 2: Communication patterns that shape collaboration. - Module 3 (yesterday): Conflict Management, anchored by a psychometric tool. We began with the deceptively simple game “Win as Much as You Can.” Each team had two choices every round: X (protect yourself) or Y (trust the group). Playing X = short-term gain for the individual, but loss for others. Playing Y = trust, collaboration, and long-term collective gain. The results were striking: > Team A chose Y nearly 60% of the time, showing willingness to trust. > Team D played it 50% — half trust, half protect. > Teams B and C only 20%, holding back from collaboration. In the debrief, the lesson was clear: * Some defaulted to competition — protecting themselves at the cost of the system. * Others avoided risk, waiting for others to act. * A few leaned into collaboration and accommodation, willing to lose individually so the team might win. 👉 This mirrored exactly what the Conflict Management Psychometric Tool later revealed. How they played the game reflected how they handle conflict in the wards, with parents, and with peers. And here’s what mattered most: Dr. Srinivas, as HOD, openly appreciated the tool and its insights. When leadership acknowledges the value of conflict fluency, the entire culture shifts. For hospital L&D leaders, the implications are profound: - X is not just a letter — it’s a culture. Too much of it breeds silos and mistrust. - Y is not just a choice — it’s a future. It builds consistency, trust, and safer patient experiences. For corporate leaders, the parallel is undeniable: - X is the short-term target, the quarterly win, the individual bonus. - Y is the shared vision, the cross-functional trust, the long-term sustainability. Every team, whether in a hospital or a boardroom, faces this choice daily: Do I play for me, or do I play for us? 💡 The next frontier of excellence — in healthcare and corporates — is not just skill or strategy, but conflict fluency. Because how your leaders choose between X and Y today will define the culture of your organisation tomorrow. At Nirvedha Executive Coaching, we believe: how you face one storm defines how you’ll navigate every sea. 🌊 #LeadershipInHealthcare #ConflictManagement #HospitalExcellence #CorporateLeadership #FutureOfWork #Nirvedha

Applying Cummings & Worley Group Diagnostic Model #OrganizationalDevelopment #TeamDynamics #PharmaIndustry #Leadership #ChangeManagement Scenario Background: A mid-sized pharmaceutical company has been experiencing declining productivity and increasing conflict within its research and development (R&D) teams. The leadership suspects that ineffective team dynamics and poor alignment of goals might be contributing factors. To address these issues, How L & D professional can utilize the Group Level Diagnostic Model, which focuses on diagnosing and improving group effectiveness within an organization. Step 1: Entry and Contracting: Objective: Establish a clear understanding of the project scope, objectives, and mutual expectations with the R&D teams. Actions: Conduct initial meetings with team leaders to discuss the perceived issues and desired outcomes. Step 2: Data Collection Objective: Gather information to understand current team dynamics, processes, and challenges. Actions: Distribute surveys and conduct interviews to collect data on team communication, collaboration, role clarity, and decision-making processes. Observe team meetings and workflows to identify misalignments and potential areas of conflict. Use assessment tools to measure team cohesion, trust levels, and satisfaction among team members. Step 3: Data Analysis Objective: Analyze the collected data to identify patterns, root causes of dysfunction, and areas for intervention. Actions: Compile and analyze survey results and interview transcripts to identify common themes and discrepancies. Map out communication flows and decision-making processes that highlight bottlenecks or conflict points. Assess the alignment between team goals and organizational objectives. Step 4: Feedback and Planning Objective: Share findings with the teams and plan interventions to address the identified issues. Actions: Conduct feedback sessions with each team to discuss the findings and implications. Facilitate workshops where teams can engage in problem-solving and planning to improve their processes and interactions. Develop action plans that include specific, measurable, achievable, relevant, and time-bound (SMART) objectives to enhance team performance. Step 5: Intervention Objective: Implement interventions aimed at improving team dynamics and effectiveness. Actions: Initiate team-building activities that focus on trust-building and role clarification. Provide training sessions on conflict resolution, effective communication, and collaborative problem-solving. Realign team goals with organizational objectives through strategic planning sessions. Step 6: Evaluation and Sustaining Change Objective: Assess the effectiveness of interventions and ensure sustainable improvements. Actions:Conduct follow-up assessments to measure changes in team performance and dynamics. Hold regular meetings to discuss progress and any ongoing issues. Adjust interventions as necessary based on feedback and new data.

Conflicts within a team are rarely about tasks alone—they often come from unresolved emotions like comparison, lack of recognition, or past grievances carried silently. When managers try to solve these issues by simply #grouping people together in the same assignment, it only masks the problem for a short time. The unspoken tensions will show up in missed deadlines, subtle resistance, or lack of trust. It’s important to realize that outer collaboration without inner healing is like painting over cracks in a wall—the structure still remains weak. True leadership requires going #deeper than surface solutions. Managers carry a responsibility not just to distribute work but to create an environment where inner conflicts can dissolve. This means moving from task management to people understanding. They can hold one-on-one conversations to listen without judgment, facilitate team circles where concerns can be voiced respectfully, and lead by example through fairness and humility. Introducing mindful check-ins, communicating transparently, celebrating small wins, and recognizing efforts equally helps reduce hidden competition. Over time, these practices shift the team’s energy from ego-driven reactions to collective trust. A manager who takes responsibility in this way does more than resolve conflicts—they cultivate a culture where people evolve, both as professionals and as human beings.

Your team isn't arguing about solutions. They're solving different problems. A senior leader I coached expressed frustration. The same issues kept resurfacing, no matter how often they met. Marketing wanted faster product launches. Product wanted more customer data upfront. Operations wanted clearer handoffs. Each team saw a different problem. They all proposed solutions.None of them stuck. What I saw: ❌ They were solving different problems ❌ No one named what they were actually solving for ❌ Solutions were developed in silos, then defended in meetings ❌ They skipped alignment because speed felt like progress The conflict wasn’t about disagreement. It was about unspoken assumptions. What we did instead: ✅ Slowed down before solving ✅ Asked: What problem are we solving, and for whom? ✅ Named what success looked like from each function's view ✅ Made space for different contexts before debating solutions ✅ Built agreement on the problem before proposing fixes What changed: → Meetings became fewer, shorter, and more focused → Solutions lasted instead of unraveling → Cross-functional tension dropped → Teams stopped firefighting the same issues → Decisions stuck because everyone was solving the same problem Over time, the shift became part of how they operated. As the leader put it: “The context step is non-negotiable. It saves us from solving the wrong thing fast.” When you rush to solutions, you create the firefighting that keeps you stuck. When you slow down, you start to realize: Shared understanding is the fastest way to solve something once (and well). 💬 What's one question you could ask before offering your next solution? 💾 Save this for your next cross-functional meeting 🔔 Follow Michelle Awuku-Tatum for more human-centered leadership insights that shift how teams work together.