Leading Cross-Functional Teams

HR doesn’t need more dashboards. It needs better listening. Most people teams measure what’s easy…like engagement scores or turnover. But the best teams? They build feedback loops that help them predict problems, not just react to them. This post gives you 11 of the most useful, often-overlooked loops you can implement across the employee lifecycle: 🟢 Week 2 new hire check-ins (capture early impressions) 🟠 Post-interview surveys (from both sides) 🔵 Onboarding reviews (day 90 is your goldmine) 🟡 Skip-level 1:1s (cross-level truth-telling) 🟣 Quarterly team health check-ins (lightweight, manager-led) …and 7 more. 📌 Save this if: • You’re building a modern HR function • You want fewer “We should’ve seen this coming” moments • You believe listening is strategy Which feedback loop is missing in your company?

When people feel genuinely appreciated, they’ll go above and beyond 🙏🏾

 It’s not rocket science, when you value your team, they start seeing their work as meaningful, and they’ll give you way more than just what’s expected. 

It’s a simple formula: look after your people, and they’ll look after your customers, which will, in turn, look after your business.
 Here’s how to make that happen, step by step:
 1. Show Real Appreciation: Don’t wait for the annual review to recognise someone’s hard work. Make it a habit to acknowledge wins, big or small. A simple “thank you,” a shoutout in a meeting, or a quick message goes a long way in showing that you see their effort.
 2. Give People Autonomy: Trust your team to do the job you hired them for. Micromanaging makes people feel undervalued, but giving them the freedom to make decisions shows you trust their abilities. When people feel trusted, they take more ownership and pride in their work.
 3. Invest in Their Growth: If you want your team to see their work as valuable, invest in them. Offer training, mentorship, or opportunities to take on new challenges. When you help your people grow, they’ll bring that extra value back to your business.
 4. Create a Culture of Respect: Encourage open communication where everyone feels heard. When your team knows their ideas and feedback are valued, they’ll feel like a key part of the bigger picture—and that motivates them to give their best.
 5. Recognise the Impact of Their Work: Connect the dots for your team—show them how their efforts contribute to the success of the business. When people can see the real-world impact of what they’re doing, it turns everyday tasks into something more meaningful.
 6. Support Work-Life Balance: A healthy, happy team is a productive one. Encourage your employees to take breaks, use their holidays, and maintain a good work-life balance. When people feel supported in managing their lives outside of work, they’re more energised and focused when they’re on the job.

 7. Celebrate Wins as a Team: When something goes right, celebrate it! Whether it’s hitting a major milestone or wrapping up a tough project, recognising the team’s collective effort builds a sense of community and makes everyone feel appreciated.
 When your team feels valued, they’ll go the extra mile without being asked. 

Happy employees create happy customers, and happy customers drive business growth. 

So, take care of your team—they’re your greatest asset, and the returns will be massive. ♻️Eric Partaker

A Product Manager is nothing without the development team, who make the product vision a reality. Yet, as a PM, it's so easy to forget oneself and take all the glory for a release success. Here are 10 ways to ensure your team feels appreciated and recognized: 1) Celebrate Team Achievements Publicly Always acknowledge the team's hard work in company meetings, emails, or on social media. A public shout-out boosts morale and shows that you value their contributions. Perhaps invite a team member to join or replace you in a big presentation of a successful release. 2) Share Credit Generously When discussing successes, use "we" instead of "I". Highlight individual contributions and how they impacted the project's success. I often forget that even though I truly believe in every word of this post. 3) Provide Growth Opportunities Offer team members opportunities to learn new skills or take on new responsibilities. Investing in their growth shows you care about their professional development. Work with their team leader so everyone has a varied set of tasks to complete to make the work interesting. 4) Listen Actively Make time to hear your team's ideas and concerns. Active listening fosters a collaborative environment where everyone feels heard and valued. Never skip a retro! 5) Give Constructive Feedback Provide timely and constructive feedback that helps team members improve and grow. Be specific about what they did well and where they can enhance their skills. Remember to provide negative feedback privately. 6) Recognize Efforts Not Just Results Acknowledge the hard work and dedication, even if the project didn't turn out as expected. This encourages a culture of effort and resilience. 7) Foster a Positive Team Culture Encourage teamwork and camaraderie. Organize team-building activities or informal gatherings to strengthen relationships. It can be as trivial as taking lunch together. 8) Be Transparent Share information about your vision, company goals, and any changes. Transparency builds trust and shows respect for the team's role in the bigger picture. Be there corporate ally/ 9) Empower Decision-Making Allow team members to make decisions in their areas of expertise. This trust empowers them and increases their investment in the project's success. 10) Express Gratitude Personally A simple "thank you" can go a long way. Take the time to personally thank team members for their contributions. Name the success so it is not a lazy, generic gratitude. There you have it, my 10 tips to ensure your development team feels valued and appreciated. Do you agree with these suggestions? Which ones do you already practice? What's your number 11 advice? Share your thoughts in the comments! #productmanagement #productmanager #teamappreciation 📌 P.S. To become a great Product Manager who leads with appreciation, check out my courses at www.drbartpm.com :)

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

Most changemakers stall progress because we over-index on one trait: Boldness or Empathy. Very early in my career, I leaned heavily toward boldness — partly out of fear that work wouldn’t get done well. I pushed for higher standards. I intervened quickly when quality slipped. In one case, I escalated directly to a vendor’s Managing Director to address recurring performance gaps. My intention was improvement. But the team felt exposed. I had broken hierarchy. We finished the work — but it didn’t feel right. Most leadership friction happens because we over-index on one and neglect the other. My own experience and observations across industries formed a simple Boldness-Empathy model I now use when coaching cross-function teams: 1️⃣ Low Boldness / Low Empathy — The Bystander Avoids tension. Avoids progress. Lets mediocrity thrive. 2️⃣ High Boldness / Low Empathy — The Bulldozer Drives standards. Challenges norms. Damages trust. 3️⃣ Low Boldness / High Empathy — The Protector Over-relates to context. Preserves peace at the cost of progress. Struggles to execute change. 4️⃣ High Boldness / High Empathy — The Leader Sets high standards. Protects dignity. Challenges and cares at the same time. Boldness without empathy smacks like judgment. Empathy without boldness breeds hesitation. Sustainable change requires both — it’s the best way to mobilise people. Raise the bar. Respect the person. When I coach people facing logjams now, I ask two questions: • How clear are we about the standard? • How thoughtful are we about how it lands? The intersection is where influence lives.

Autonomy is often wrongly confused with independence. This mistake negatively affects accountability. People sometimes mistakenly think that giving people autonomy means leaving them completely to their own devices (this is independence). In the organizational sense, autonomy is not the opposite of structure—it’s the freedom to operate WITHIN a structure that supports continuous improvement and accountability. A Lean mindset and approach helps leaders to understand how to foster BOTH accountability and autonomy. Lean leaders do this by intentionally moving away from making people feel like they are "being held accountable" (which feels imposed) and inspiring them to "take accountability" (a sense of ownership that naturally fosters autonomy). Here’s how you can adopt this approach in YOUR team: 🟢 Be clear about goals, roles, and responsibilities: Use tools like RACI charts or visual management boards to clarify who does what. 🔴 Define success together: Involve the team in setting performance standards or KPIs so they have a say in what they’re working toward. 🟣 Encourage regular 1:1 check-ins and team huddles: create spaces for discussing challenges without fear. 🟡 Engage people in problem-solving: Use structured techniques and Kaizen to involve the team in addressing inefficiencies. 🔵 Ask for their ideas first: Instead of directing what needs to change, coach them with powerful questions like, “What do you think is the best next step?” 🟤 Use visual management: Team dashboards or Kanban boards make progress visible, reduce micromanagement and highlight areas needing attention. 🟠 Review metrics as a team: Make this part of regular meetings, so progress and accountability are a collective effort. ⚫ Own your commitments: If you make a mistake or miss a deadline, acknowledge it openly. ⚪ Model humility: Admit when you don’t have all the answers and seek input from the team. (This makes people feel valued!!) 🤔Reflection time for leaders... Are you balancing structure and flexibility in your team? Which of the above could you act on to shape a culture of autonomy?

Meetings cut in half. Escalations down 75%. No new tools required. A cross-functional marketing team at a major global retailer was drowning: only 22% thought their meetings were a good use of time, and just 39% understood the metrics they were being evaluated against. No calendar audit fixed it. What did? Getting their team working norms aligned, starting with cross-functional goals. With help from Sacha Connor at Virtual Work Insider, the team worked through five intensive 90-minute sessions over two months. Three focus areas made the difference: 🔹 Align goals before anything else. They mapped KPIs side by side and found one function's top priority barely registered for the other. They worked to get aligned, and shared understanding of team metrics went from 39% to 83%. 🔹 Clarify decision rights first. Designated points of contact absorbed a brutal 15:1 staffing ratio, without adding headcount. It also cut down on meetings ("where are we on X") and reduced escalations by 75%! 🔹 Create norms for communication. One rule on Teams: drop an eyeball emoji to acknowledge you've seen a message. Information-flow effectiveness jumped from 41% to 83%. As Sacha put it about Team Working Agreements: most companies put a toolkit on the intranet, maybe a couple teams download it, work through the logistics and call it done. It's not. Three-quarters of teams have never established formal norms. If you're about to layer AI on top of that foundation, you're building on sand. 👉 Full case study in today's newsletter, linked in comments What's actually standing in the way of your team doing this work? #Meetings #Management #AI

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

2 — Solving Goal & Priority Misalignment with Is/Is Not + Perspective Circle.  SOLVING THINGS with SYSTEMS THINKING (STwST) — a series of mini, real-world applications of DSRP. When a team says, “We’re working hard but not pulling in the same direction,” it’s usually not a motivation problem. And it’s rarely a communication problem. It’s a distinction + perspective problem. Different people are carrying different mental pictures of what the goal is and is not, and different perspectives on what actually counts as a priority. So even when everyone uses the same words, they’re not aiming at the same thing. They might be reading the same page but interpreting it differently. Two simple thinking moves fix this. The first is an Is / Is Not list. Take the goal and the priorities and make them explicit: what this goal is, what it is not; what matters now, and what does not. This forces clarity where assumptions usually hide. The second is a Perspective Circle. You don’t need everyone to think the same way—but you do need everyone looking at the same picture. Different roles, levels, and functions can keep their own viewpoints, as long as they’re all anchored to the same shared view. Then keep that shared model on the table. Revisit it at the start of meetings. Use it when tradeoffs show up. Let people argue with it, stress-test it, and refine it. Don’t laminate it. Put it to work. Alignment doesn’t come from hearing the right words once. It comes from people rebuilding their own internal picture until it matches the shared one. When that happens, language cleans up, decisions get faster, resources line up, and the friction fades—because action always follows the mental model. If you listen carefully, misalignment announces itself in sentences that shouldn’t exist if the goal were truly shared. Those sentences are the signal. #STwST #SystemsThinking #CabreraLabPodcast #SystemsThinkingStandardsInstitute

Shared understanding is fundamental to any change endeavour. But how do we orchestrate a journey towards a shared understanding? This framework - from the fantastic Challenge-led system mapping handbook by Climate-KIC - highlights a structured progression inspired by the DIKW pyramid. I really like the way iterative dialogue is embedded in a way that ensures resources become living documents that evolve with stakeholder insights, reflecting the dynamic nature of the system. "The evolving conversation contributes to the collective understanding of the challenges, the questions, and the mapped system itself." This journey begins with participatory processes and data generation, which lay the foundation for understanding the makeup of the system. These steps involve diverse stakeholders coming together to identify core components and relationships within the system. As the process evolves, we move into harvesting and documentation, where data transitions into manageable sources and is organised into coherent information. This phase involves physical structuring and cognitive processes, framing data into actionable insights and beginning to illuminate system patterns. The next phase—conceptualisation and analysis—builds on this structured base to foster a deeper understanding. Here, information transforms into knowledge through analytical structuring. This stage involves recognising connections, patterns, and dynamics, enabling stakeholders to identify key indicators of progress or change. Finally, the journey culminates in wisdom, where insights are communicated through visualisation and interpretation. This stage bridges the gap between abstract analysis and practical application, enabling informed decision-making and co-produced practices. Wisdom reflects a high level of both structure and understanding, empowering stakeholders to act collaboratively toward systemic change. This iterative and participatory process emphasises the importance of feedback loops and incremental understanding, ensuring that stakeholders grasp the complexities of the system and also feel invested in its transformation. "Knowledge management integrates links between interpretation, analysis, and action, allowing practitioners to move from traditional 'learning to manage' practices to 'management as learning'."