Cross-Department Training

A common partnership snafu is that companies want partnership success, but don’t provide the resources to get there. I heard of a case where a whole marketing team quit, the partnerships team was given no marketing support, and they didn't yet have an integration with product -- and yet, the CEO expected the partnership strategy to deliver instant revenue. Wild. But not uncommon. Partnerships can't thrive in a vacuum. They need cross-functional support—marketing, product integration, sales enablement—all aligned to succeed. Before you set revenue targets for your partnerships, ask yourself: Do we have the resources to support them? If the answer is no, you have to help your leadership teams to reconsider their expectations. To help create the cross-functional support needed for partnerships to thrive, here are four strategies: 1. Involve Cross-Functional Leaders from the Very Beginning Bring key leaders from marketing, sales, and product into the partnership planning phase. Early involvement gives them a sense of ownership and ensures they understand how partnerships align with their own goals. Strategy: Schedule a kick-off meeting with stakeholders from each relevant department. Create a shared roadmap that outlines how partnerships will impact each team and their specific contributions. 2. Tie Partnership Success to Department KPIs To gain buy-in, tie partnership goals directly to the KPIs of each department. Aligning partnership outcomes with what each team is measured on ensures they have skin in the game. Strategy: During planning sessions, ask each department head how partnerships can contribute to their targets. Build specific KPIs for each function into the overall partnership strategy. 3. Create a Resource Exchange Agreement Formalize the support needed from each department with a resource exchange agreement. This sets clear expectations on what each function will contribute—whether it's a dedicated product team member for integrations or marketing resources for co-branded campaigns. It turns vague promises into commitments. Strategy: Draft a simple document that outlines the roles, responsibilities, and deliverables each team will provide, then get sign-off from department heads and the executive team. 4. Demonstrate Early Wins for Buy-In Quick wins go a long way toward securing ongoing resources. Identify a small pilot project with an internal team that shows immediate impact. Whether it's a small co-marketing campaign or a limited integration, these early successes build momentum and demonstrate the value of supporting partnerships. Strategy: Select one or two partners to run a pilot with, focused on delivering measurable outcomes like leads generated or product adoption. Use this success story to demonstrate value to other departments and secure further commitment. Partnership success requires cross-functional alignment. Because partnerships don’t happen in a silo.

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

#ThrivingToGetWorkDone Post 6 of 9: Fostering Collaboration and Teamwork: Breaking Down Silos Fostering collaboration and teamwork is essential in a complex environment like a hospital, where departments must work together seamlessly to provide the best patient care. Here are two short use cases on how to activate this skill in routine work within the hospital industry: Use Case 1: Collaborating Across Departments for a Multidisciplinary Care Plan You’re involved in creating a multidisciplinary care plan for patients with chronic illnesses. This requires input from various departments, including Cardiology, Nutrition, and Physical Therapy. To foster collaboration, you suggest, “Let’s schedule regular multidisciplinary team meetings where each department can share their insights and updates on patient progress. We’ll use these sessions to ensure that our care plans are fully integrated and that we’re all working towards the same patient outcomes.” By bringing everyone together, you break down silos and ensure that each department’s expertise is utilized, leading to better patient care. Use Case 2: Enhancing Collaboration in a Quality Improvement Project In another scenario, you’re working on a quality improvement project aimed at reducing hospital readmission rates. You notice that different departments, such as Discharge Planning, Pharmacy, and Home Health, are working in isolation. You propose a more collaborative approach: “Let’s form a cross-departmental task force to tackle this issue. We’ll meet bi-weekly to share data, discuss challenges, and develop integrated strategies to reduce readmissions. By working together, we can identify gaps in our processes and ensure a smoother transition for patients after discharge.” This approach not only fosters teamwork but also leads to more comprehensive solutions. #My2Cents: Collaboration is the cornerstone of success in any complex organization. By fostering teamwork and breaking down silos, we can leverage the full spectrum of our collective expertise, leading to better outcomes for our patients and our hospital. These posts aim to invoke a better overall environment by sharing practical ways to enhance workplace collaboration and productivity. What strategies have you used to foster collaboration in your workplace? Share your experiences in the comments! #Leadership #Teamwork #WorkplaceCulture #Collaboration #HealthcareLeadership #ThrivingAtWork #HospitalAdministration #PatientCare

Cross-departmental conflict is almost never about personalities.  It's about structures that pit functions against each other, competing for resources, influence, and credit, without ever clarifying what they're supposed to create together. Team-building events don't fix that. Motivational speakers don't fix that. The only thing that fixes it is getting people in a room to answer four questions they've never been asked to answer together:  What value do we create together?  What capabilities do we need to deliver it?  How will we resolve conflicts while maintaining trust?  And what do we actually need from each other to succeed? When R&D and operations in my client organization worked through those questions, they realized neither one controlled speed to market alone, but together they could dramatically influence it. The rivalry didn't disappear because people started liking each other more. It disappeared because they finally understood why they needed each other. I wrote about how to lead those conversations for Harvard Business Review. https://lnkd.in/gCeYNCv #Leadership #CrossFunctional #OrganizationalHealth #Culture #HBR

In so many organisations, so many people have so many ideas, skills and knowledge sets that could be of incredible value but their voices so often go unheard, because they work in a team or department that isn’t leading on the challenge, or their job description is only accessing 10% of their experience, expertise and interest. It is why it is so important to get people to work across teams and to broker and to catalyse that. The U.S. military have liaison officers who facilitate communication between elements of the organisation to ensure mutual understanding and unity of purpose and action. Liaison is the most commonly employed technique for establishing and maintaining close, continuous, physical communication between commands. It ensures that leaders and teams have a real time awareness of talent and expertise, wherever it may be, so that it can be deployed quickly and with immediate impact. Maybe, create a centralised information centre, where people can see what is going on where in the organisation, and can contribute through online portals to offer support and ideas. Increasingly, organisations are holding hackathons, during working hours for people to meet in open spaces, shares ideas and challenges, in order to form working groups and focused teams. I often advise clients to build work exchanges into their professional development cycles, so that people get the chance to experience other roles and responsibilities within the organisation, not only to build empathy but to foster new relationships and opportunities for information and idea exchanges. Start to see roles as missions rather than fixed job descriptions, so that colleagues can move when appropriate but always have a home base to return to.   Make sure that leaders at all levels are not only held to account for planning, strategy, vision, culture and performance but for cross-team collaboration. It is too easy for leaders to role model the silo-ing and cross departmental blame shifting that can so easily poison an organisation’s collegiate potential.  

How I decide PM–PS integration Not during configuration. During blueprint. Most teams ask how to integrate. Few ask when and who owns it. Let me break this from a real plant expansion project on SAP S/4HANA. ⸻ A new packaging line coming to KANT plant Project team working in SAP Project System. Maintenance team preparing technical objects in SAP Plant Maintenance. Commissioning started. Trial runs began. Minor failures happened. Now the big question: Is this project cost? Or maintenance expense? That answer defines integration. ⸻ When Do We Integrate PM–PS? You integrate when: •📍Asset is under construction • 📍Commissioning activities generate costs •📍 Breakdown happens before capitalization • 📍Project budget must absorb technical costs • 📍Contractors perform maintenance-like tasks during project phase If asset is already capitalized and live — Normal PM process. No PS needed. But during CAPEX lifecycle? PM orders must hit WBS. ⸻ What Exactly Gets Integrated? 1. Maintenance Order → WBS Element • Account assignment category “P” • Order linked to specific WBS 2. Settlement Rule • PM Order settles to WBS • WBS settles to Asset Under Construction 3. Equipment Creation During Project • Technical object created early • Linked to functional location • Budget visibility retained in PS 4. Cost Flow Labor → PM Material → PM PM → WBS WBS → AuC AuC → Final Asset Clean chain. No Excel tracking. ⸻ Which Functional Drives It? This is critical. PM consultant alone cannot design it. PS consultant alone cannot control it. It is a joint design between: • PM Functional • PS Functional • FI/CO for settlement & capitalization But ownership depends on trigger: If requirement is “project cost control” → PS leads. If requirement is “maintenance during commissioning” → PM leads. In my experience, best results come when PM initiates and PS validates financial design. Because technical lifecycle starts earlier than finance realises. ⸻ Why It Matters in S/4 With Universal Journal: No CO reconciliation layer. Real-time cost visibility. Project manager sees actuals instantly. Integration is not about configuration nodes. It’s about answering one strategic question: Who owns cost until asset goes live? If you’ve done plant commissioning or brownfield expansion — how did you structure PM–PS ownership?

Well-designed cross-functional processes are powerful. They create customer experiences that are effortless for the customer and more efficient for the organization. Here's a story that illustrates this point. A colleague of mine visited the contact center for a well-known health insurance company and relayed this experience to me. While she was meeting with team members, she saw job aids referring to “building empathy” and delivering “apologies with heart.” The quality assurance (QA) form measured employees on how well they helped customers manage their intense emotions over delayed claims. The training content emphasized how to explain complicated claims processes. When she met with the contact center director, she asked, “Why so much time and energy on training reps to manage customers who are disappointed… by you? Why not just fix the claim issue?” He sighed. “It’s not that easy. The claims department has their way of doing things. We’ve tried to meet with them over this issue a few times, but the message is clear—‘stay on your side of the fence.’ We do our best, but customers express frustration every day. We can’t magically make customers okay with it.” This gap between what customers want and what is being delivered—and I suspect you may have similar stories—is all too familiar in many organizations. Customer-centric organizations, however, spend proportionally more time designing processes and proportionally less time getting better at appeasing unhappy customers. They devote their attention to eliminating what makes customers unhappy in the first place. Of course, glitches will still happen, and the processes you use to resolve those issues are essential. Effective complaint resolution will always be part of your CX portfolio. But that shouldn’t be the main focus. The challenge? Without deliberate intervention, departments don’t naturally work across functional lines. The marketing team focuses on messaging and response rates. The product management team is occupied with product design and development. Billing concentrates on revenue and collections. Each team fixates on being the best they can be within the boundaries of their department. Every department can agree that designing processes and technology with the customer in mind makes sense. Even so, being customer-focused within a silo doesn’t fix the most exasperating barriers to good experiences. Great experiences happen by design through cross-department collaboration. They are shaped with a clear-eyed view of the customer as they traverse through the work done by marketing, product management, billing, and the contact center. That work must be coordinated and seamless for the trip to feel effortless, satisfying, and yes, sometimes even WOW. And to create that collaboration, your organization must have high-level sponsorship. Senior leaders must define a common vision and goals, and hold all accountable to pursue them.

In my previous post, I explored the hidden costs of data silos. Today, I want to share practical steps that deliver value without requiring immediate organisational restructuring or technology overhauls. The journey from siloed to integrated data follows a maturity curve, beginning with quick wins and progressing toward more substantial transformation. For immediate progress: 1) Identify your "golden datasets": Focus on the 20% of data driving 80% of decisions. Prioritise customer, product, and financial datasets that cross departmental boundaries. 2) Create a simple business glossary: Document how terms differ across departments. When Finance defines "revenue" differently than Sales, capturing both definitions creates transparency without forcing uniformity. 3) Implement read-only integration patterns: Establish one-way flows where analytics platforms access source data without disrupting existing systems. These connections create cross-silo visibility with minimal risk. 4) Build a culture of trust: Reward cross-departmental collaboration. Create incentives that make data sharing a path to recognition rather than a threat to influence or expertise. 5) Establish cross-functional data forums: Host regular meetings where data users share challenges and use cases, building relationships while identifying practical integration opportunities. As these initiatives gain traction, organisations can advance to more substantial approaches: 6) Match your approach to complexity: Smaller organisations often succeed with centralised data management, while larger enterprises typically require domain-centric strategies. 7) Apply bounded contexts: Map where business domains have distinct needs and terminology, creating clear translation points between areas like Sales, Finance, and Operations. 8) Adopt a data product mindset: Designate product owners for critical datasets who treat data as a product with clear consumers and quality standards rather than simply an asset to be stored. 9) Develop a federated metadata approach: Catalogue not just what exists, but how data relates across domains, making relationships between siloed systems explicit. 10) Maintain disciplined data modelling: Well-structured data within domains makes integration between them far more manageable, regardless of your architectural approach. This stepped approach delivers immediate value while building momentum for more sophisticated strategies. The most successful organisations pair technical solutions with cultural transformation, recognising that effective data integration is ultimately about people collaborating across boundaries. In my next post, I'll explore how governance models evolve with data integration maturity. What approaches have you found most effective in addressing data silos? #DataStrategy #DataCulture #DataGovernance #Innovation #Management

"Why aren't we talking to each other?" I've asked this question as a frustrated engineer. So have many others I've worked with. In one case, a team spent six weeks redesigning a component another department had already optimized. Nobody knew. This isn't a communication problem. It's structural. Organizational silos don't just hinder communication; they systematically destroy innovation and experimentation. Gartner and IDC research shows data fragmentation and silos cost companies millions in inefficiencies, delayed launches, and duplicated efforts. Yet these costs never appear on financial statements. The real damage isn't wasted resources. It's the impact on innovation velocity: ➡️ Problems get fragmented When challenges span departments, each team optimizes their piece without seeing the whole. I've seen quality issues persist for months because departments hit their targets while the overall process failed. ➡️ Knowledge gets trapped Critical insights never reach teams that could use them. One manufacturing leader told me: "We solved the same problem five times in five facilities because we had no way to share lessons learned." ➡️ Decision-making slows to a crawl Every handoff between engineering, operations, supply chain, and quality adds delay and distortion. When markets shift, this friction becomes fatal. How to transform siloed organizations: First, create shared outcomes. Replace department-specific metrics with cross-functional KPIs that require coordination. Second, establish structural bridges. Rotate high-potential team members through different functions for 90-day assignments. This builds human connections that span silos. Third, implement structured experimentation across departmental boundaries. Collaborative problem-solving dissolves silos naturally. The highest-performing manufacturers aren't those with the strongest departments, but those with the most effective connections between them. --- If this is a problem in your organization, let's talk.

Did you realize that inventory is completely interconnected with every other part of the supply chain? Procurement decisions, production schedules, warehouse operations, transportation capacity, and customer demand patterns all feed into it. That interconnectedness can make inventory tricky to manage because it doesn’t just pop up out of nowhere and move on its own. It’s the result and reaction to all decisions made upstream. When your functional areas (procurement, production/manufacturing, warehousing, transportation, distribution, sales, forecasting…) aren’t aligned, inventory (and ultimately your customer) ends up carrying the consequences. Let me give you an example: If supplier lead times extend but reorder points don’t adjust, the business has no choice but to hold more inventory to protect service. Production reacts by running longer batches to “get ahead,” which ties up product in forms that don’t always match what customers are ordering. That excess then moves downstream, where warehousing takes the hit in terms of holding the wrong product at the wrong locations, holding too much inventory, or having to use extra labor to keep product moving. Transportation is next in line with having to expedite shipments, moving product to different locations to position inventory in the right spots, or mode/capacity issues related to inventory discrepancies. Then, this doesn’t match the sales or forecasting plans that were set at the start which kicked off the whole S&OP process. Cross-functional integration is about preventing these disconnects before they cascade through the system. Yes, that does start with understanding your processes and how the impacts can cascade... BUT… it's ultimately about matching your inventory to the reality of your supply chain capabilities. Procurement sets order cycles in step with production schedules. Production builds to demand signals, not just efficiency goals. Warehousing plans space and labor against expected flows. Transportation aligns modes and routes with real demand. Sales makes commitments that the rest of the chain can back up. For small and mid-sized businesses, cross-functional integration can start with consistent communication and discipline across functions, built around a few key questions: 🔵 Procurement — are supplier cycles aligned with both demand and production schedules? 🔵 Production — are we building to demand signals or just running for efficiency? 🔵 Warehousing — does available space and labor reflect stocking policies and flows? 🔵 Transportation — are modes and routes aligned with where demand is actually occurring? 🔵 Sales/Forecasting — are customer commitments and projections grounded in operational capacity? The takeaway is simple: inventory is the mirror of cross-functional alignment. If it feels like you’re always carrying too much in one area and scrambling in another, the issue isn’t necessarily inventory. It’s the misalignment of your upstream integration.