Cross-Functional Design Teams

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

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!

👩💻 Picture this: A global product team is under pressure to innovate. The next big feature must: Delight customers, Beat competitors, Strengthen market position. Leadership sets up weekly cross-functional strategy meetings. On paper, it’s a dream setup: 📢 Marketing brings customer pain points ⚙️ Engineers know the technical possibilities 🎨 Designers understand user experience 📊 Analysts provide market data And yet… every meeting feels the same. 👉 A few senior voices dominate. The rest remain silent. Frustrated, leadership concludes: “They’re not strategic enough.” “They’re disengaged.” “They lack creativity.” But when I spoke to the team, a different story emerged: 😟 Fear of judgment: “If my idea isn’t polished, I’ll look foolish.” 😔 Past dismissal: “The last time I contributed, it was brushed aside.” ⏳ No structure: “By the time I frame my thought, the conversation has already moved on.” 💡 It wasn’t disengagement. It was a design flaw in how participation was structured. As a Learning Experience Designer, I suggested practical shifts: 1️⃣ Pre-work idea collection → A shared digital whiteboard for input before meetings. 2️⃣ Structured discussion formats → Time-boxed rounds (2 minutes each) before open dialogue. 3️⃣ Psychological safety rituals → Leaders began with: “Every idea matters.” and modeled it. 4️⃣ Visible impact loop → Tracked which ideas became pilots, features, or improvements—and gave credit. ✨ The Impact: Employees once labeled “quiet” began sharing bold ideas. A junior engineer suggested a backend tweak that saved 💰 thousands in server costs. A designer proposed a UX change that cut onboarding time by ⏱️ 12%. The same people. The same talent. But in a redesigned environment, their best became visible. 🔑 Silence in meetings doesn’t mean absence of ideas. It often signals: “The environment doesn’t make contribution safe, easy, or worthwhile.” Leaders and L&D professionals share a responsibility: not to “fix people,” but to fix the circumstances that shape behavior. Because under the circumstances, everyone is already doing their best. 👉 Over to you: Have you ever been in a meeting where great ideas were left unsaid? What design changes could have unlocked them? #microlearning #learningwithhiral #learningeveyryda #Collaboration #InnovationAtWork #DesignThinking #FutureOfWork #TeamDynamics

At Microsoft, I learned that embracing cognitive diversity is the key to solving complex problems and driving innovation. But it didn’t come without its challenges. I vividly remember early days in cross-functional teams where conflict seemed inevitable. The Generators would dream big, throwing out bold, unstructured ideas. The Optimizers pushed back, demanding practical plans and immediate structure. Conceptualizers would dive deep into strategy, while Implementers were already asking, “When can we start?” It felt chaotic—like we were all speaking different languages. But over time, I realized that this tension wasn’t a weakness. It was our greatest strength. Min Basadur’s Cognitive Diversity Model opened my eyes: 1. 𝗚𝗲𝗻𝗲𝗿𝗮𝘁𝗼𝗿𝘀 create possibilities. 2. 𝗖𝗼𝗻𝗰𝗲𝗽𝘁𝘂𝗮𝗹𝗶𝘇𝗲𝗿𝘀 build strategic frameworks. 3. 𝗢𝗽𝘁𝗶𝗺𝗶𝘇𝗲𝗿𝘀 bring structure and refine. 4. 𝗜𝗺𝗽𝗹𝗲𝗺𝗲𝗻𝘁𝗲𝗿𝘀 turn plans into action. The conflicts weren’t about “who’s right.” They were about how we solve problems differently. The breakthrough came when we stopped trying to “fix” the tension and started leveraging it. 1. We let Generators challenge limits. 2. Conceptualizers crafted blueprints. 3. Optimizers ensured feasibility, and better, faster, cheaper. 4. Implementers delivered results. Cognitive diversity taught me that innovation thrives on collaboration, not conformity. Call to Action: How do you navigate cognitive diversity in your teams? Have you experienced the tension between vision and execution—and turned it into a superpower? #leadership #innnovation #Microsoft

Organizing Teams in the Real World Organizing dev teams isn’t just about dividing headcount by the optimal Scrum team size. It’s about creating structures and interactions that minimize inefficiencies and maximize throughput. Imagine you’ve got 40 engineers (front-end, back-end, security, DevOps, BAs, etc.). Some are seasoned; others are less experienced. With limited specialists, equal skill distribution isn’t possible. So how do you balance customer focus, reduce handoffs, and optimize delivery? Approach 1: Functional Teams w/ Centralized Specialists Functional teams are organized by skill. F/E devs in one team. B/E in another. Centralized specialists support everyone. Ex: Five functional teams and a central pool of 3 security engineers and 2 DevOps experts. Pros: Deep expertise within domains. Efficient use of scarce specialists. Cons: Lots of handoffs and delays as features move between teams. Specialists become bottlenecks. Low throughput due to coordination overhead. Result: Prioritizes expertise but sacrifices efficiency and speed. Approach 2: Component Teams w/ Platform Support Component teams own specific architectural layers (e.g., database, APIs), supported by a platform team that builds reusable tools. Ex: Four component teams and a 5-person platform team for shared services. Pros: Clear ownership of systems. Standardized tools reduce redundant work. Cons: Features spanning components require coordination. Platform dependencies can delay delivery. Teams may lose focus on customer outcomes. Result: Improved scalability, but handoffs and misaligned priorities persist. Approach 3: Hybrid Cross-Functional Teams w/ Specialist Support Feature teams are organized around end-to-end business domains, supported by floating specialists or a platform team for niche needs. Ex: Six cross-functional teams, 3 floating specialists, and a 2-person platform team. Pros: Low handoffs. Teams handle most work independently. Customer-centric focus. Efficient specialist use through targeted support. Cons: Demand spikes can stretch specialists. Upskilling generalists requires investment. Result: Balances autonomy, specialization, and throughput. Best Fit: Hybrid The hybrid cross-functional model provides the best balance of autonomy, scalability, and efficiency. This topology reduces handoffs and mitigates skill shortages. Implementing the Hybrid Model 1) Organize teams around business domains (e.g., onboarding, reporting). 2) Use floating experts or a platform team for shared needs (e.g. security, DevOps). 3) Upskill generalists to reduce dependence on specialists for routine tasks. 4) Standardize tools and create reusable solutions to streamline dependencies. Reality Perfectly balanced teams are a rarity. The hybrid model delivers a practical compromise. By minimizing handoffs, focusing on customer outcomes, and optimizing the use of specialists, you can enjoy faster delivery and greater agility despite real-world constraints.

Designers and developers speak different languages. But when they listen early, magic happens. A few months ago, we kicked off a new product build. The usual setup: designers finalize flows, hand off to dev, then... endless Slack threads, clarifying questions, and "this isn't what I expected" moments. Sound familiar? This time, we took a different approach. Instead of working in silos, we brought everyone into the same (virtual) room—from day one. We ran cross-functional workshops: 👉 Designers walked through their thinking 👉 Developers flagged edge cases early 👉 Everyone had a say in feasibility before pixels were polished We used Figma’s handoff tools—not just as a delivery method, but as a shared language. And we held quick weekly syncs to stay aligned, not just at kickoff. The result? ✅ Build time dropped by 25% ✅ Fewer bugs ✅ Zero surprise revisions ✅ And... team morale? Way up. Here’s what I learned: When design and dev teams collaborate early, they don’t just move faster—they trust each other more. And that trust? That’s where the real magic starts. 👥 Tag a designer or developer you love working with. And share your best tip for making the collaboration smoother.

My client's teams weren't misaligned. They just never once asked what the other side needed to win. That one conversation changed how I think about cross-functional collaboration entirely. It's rarely about conflict. It's about structure, or the lack of it. Here are 6 things leaders can do to actually fix it: 1. Name a shared goal Default: Each team optimizes for its own metric. Reality: silos form around scorecards, not people. Try this: "What outcome do we all lose if this fails?" 2. Create a shared rhythm Default: teams operate on separate cadences. Reality: cross-functional work only happens when there's a crisis. Try this: one joint check-in, even monthly, changes the dynamic. 3. Clarify who decides what Default: everyone collaborates on everything. Reality: no one owns the call. Deadlock. Try this: "Who has final say, and by when?" 4. Surface the handoff gaps Default: each team finishes its part and moves on. Reality: things break in the white space between functions. Try this: "Where does ownership blur?" 5. Make tension visible early Default: protect the relationship, keep things smooth. Reality: misalignment goes underground and multiplies. Try this: "What are we not saying that matters?" 6. Ask what the other side needs Default: leaders only hear their own team's view. Reality: blind spots accumulate at the seams. Try this: "What does the other function actually need from us to succeed?" Cross-functional collaboration doesn't fail because people don't care. It fails because no one built the conditions for it to work. What would you add? Follow Shirley Braun , Ph.D., PCC for insights on building leadership capabilities in Tech and Biotech that scale without breaking. #Leadership #LeadershipTeams #collaboration #TechLeadership

Most designers have trouble balancing solo and team work. But the truth is, the most impactful work comes when you can think and work in different layers, knowing exactly which people to involve and when: - Solo - Product trio - Product squad - Cross-functional group - Wider company 1. Thinking, sketching, and focused design work is mainly done solo, even though it's up to you to include people as much as you want in that process. 2. In key product decisions, discovery, and ideation, you will usually want to involve a product manager, a technical lead, and a researcher if you have the luxury. 3. Planning, design reviews, and implementation discussions should happen with your whole product squad. 4. For big initiatives, your working group should expand to include people from marketing, sales, customer support/success, domain experts, and so on. A cross-functional group that expands beyond a squad is one of the most powerful ways to reduce silos in a business and leverage everyone's collective expertise. 5. Some of your work should be played back to the whole business, both for visibility and to fuel the wider team's understanding of your customers and how you are attempting to solve their problems. This can be through show & tell sessions, Slack announcements, or any other format that works for you and your organization. The exact shape might look very different depending on your organization's size, design maturity and ways of working. And the more senior you get, the more natural it will become for you to choose that exact scope and the teams that you need to tap into. How do you separate between solo and team work? -- If you found this post helpful, consider reposting ♻️

New case study out today about eval and AI optimization workflows with Cisco Duo Security, and this one's a bit different: A big part of their success involves Design. 👀 Most of the conversation about AI quality focuses on engineering. Duo deeply involves designers into AI quality work, alongside engineering and product. They shared what their process looks like, and why they do things this way. For the past year, the Duo AI Assistant team has been running what they call a "communal" quality practice. Every week, designers, PMs, data scientists, and engineers each review 15-20 real assistant conversations. They calibrate together on Fridays. They've turned cross-functional collaboration into cadence. What stood out to me: the Design team doesn't see this as a chore. They see it as part of their user research process. Jillian Haller, Design Manager: "This is the next best thing to a contextual inquiry... We're actually able to see how the interaction unfolds." A year in, the results speak for themselves: Duo is expanding their AI Assistant to global customers, their team and leadership have clear visibility into quality, and the team has built the operational muscle to keep improving week over week. Huge thanks to Brianna Penney, Jillian Haller, Laura Cole, and Shakeel Ahamed for sharing their story with us. They built this practice without a blueprint, and now it's become a model for other teams to learn from. We're proud Freeplay is the shared surface where their cross-functional team collaborates on AI quality. Full case study in the comments. 👇

Who’s your team? If it’s only those who report to you, you’re doing it wrong. That’s the premise posed by Keith Ferrazzi, author of "Never Lead Alone", on a recent podcast episode of “Curious Leadership” with Dominic Monkhouse. You'll find it an interesting and at times controversial conversation. The concept is simple. Instead of building teams by org chart, build them by outcomes: Cross-functional, multi-disciplinary, formed around a specific objective, not a department. Not only does this improve collaboration and introduce new perspectives, it also creates shared ownership as team members see the value they bring to the goal. Research also shows that employees in cross-functional teams feel more prepared to handle unexpected change. And when you have teams from different parts of the organization, they are more likely to speak up without being intimidated by the hierarchy in the room. This concept is not new. It was pioneered by an insurance company in the 1950s and continued to gain popularity as the need for innovation became more pressing for businesses. It has been applied by Ikea, Microsoft, Ford, and many others. But this concept extends beyond the formal project teams in the company. It should extend to how you build your informal team within a company. Connecting and engaging with people from different parts of an organization gives you a better view of its performance, allows you to better understand the unwritten processes within the organization, and creates allies that can help you understand the context of the company. The concept can also extend to your personal life. While we tend to have friends who think in similar ways, we gain just as much from those who don't. They can shake the complacency in our mindset and force us to reframe personal decisions in a new way. So, who’s your team?