Cross-Functional Process Improvement Tactics

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

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.

🚀 From Customer Complaints to Operational Excellence: A Blueprint for Any Industry As a management consultant, I see many companies struggle with the same challenge: high customer complaints and slow resolution times. But this WCOM case study in viscose fiber manufacturing shows a clear path to turn complaints into a strategic advantage—and the lessons apply far beyond manufacturing. Why This Case Matters Every industry faces customer complaints, but most companies: ❌ Treat them as one-off fires to put out ❌ Lack structured processes to prevent recurrence ❌ Have no real-time visibility into root causes This manufacturer flipped the script—here’s how: 1. Start with Data: Loss Deployment Analysis Instead of guessing, they mapped where and why losses occurred (defects, delays, miscommunication). → Your Takeaway: Use Pareto analysis to identify the 20% of issues causing 80% of complaints. 2. Pilot Before Scaling They tested changes in a controlled environment before full rollout—reducing risk and proving ROI fast. → Your Takeaway: Run a 90-day pilot on one product line or region to refine your approach. 3. Daily Control = Sustainable Results A cross-functional team met daily to track progress, assign ownership, and escalate bottlenecks. → Your Takeaway: Implement a visual management system (e.g., Kanban) to keep complaints visible and actionable. Who Can Apply This? Retail/E-commerce: Reduce returns and negative reviews by spotting quality trends early. Banks/Fintech: Cut complaint resolution time by streamlining cross-department handoffs. Healthcare: Improve patient satisfaction by addressing recurring service failures. The Bigger Picture Complaints aren’t just problems—they’re free feedback highlighting operational gaps. Companies that systematize complaint management don’t just improve satisfaction—they reduce costs, boost retention, and outpace competitors. Need help adapting this framework to your business? Let’s talk. #OperationalExcellence #ProcessImprovement #LeanSixSigma #ComplaintManagement #healthcare 

5S Is Not Housekeeping : It’s How Your Whole Company Works 5S is a simple but powerful method to create a safe, organized and reliable workplace. It removes friction from daily work – people find what they need fast, problems become visible early, and standards are clear. In many companies, 5S stops at production: lines are taped, tools are shadow‑boarded, floors are clean – while warehouses, offices and support areas stay chaotic. That local implementation creates islands of order in a sea of disorder. 5S Must Cover All Areas: ✅ Production is only one part of the value stream; poor 5S in other areas creates delays, quality issues, and safety risks ✅ Cross‑functional 5S makes information flow as good as material flow: tidy offices, clear documents, and organized planning reduces firefighting ✅ Companywide implementation sends a cultural message: “5S is how we work here,” not “something operators must do on the shop floor” Every area touches the product or the information that drives the product: Production, assembly, maintenance, warehouse, offices. When all these zones apply the same 5 steps and the same discipline, materials flow, information flows and people can focus on real value instead of searching, waiting and correcting mistakes 5S Audit is mechanism to sustain ☑️ It verifies that standards are actually followed, not just written in a procedure. ☑️ It makes waste and abnormalities visible (clutter, unsafe operations, bad habits) before they turn into quality or safety problems ☑️ It creates data by scoring per area and per “S”. So you can compare functions, track trends and prioritize improvement actions ☑️ It reinforces ownership and discipline, because everyone knows what “good” looks like what NOT ☑️ It links 5S to results by showing how better organization improves productivity, safety, morale and quality over time How to Perform the Audit 🎯 Define scope and standards: List all areas to be audited 🎯 Create a simple checksheet: For every question, add a numeric scale “actual vs. ideal” and GAP. 🎯 Standardize routine: Use the same checklist for all areas, assign auditors and frequency to follow progress How to Visualize 👍 Use charts for each area to show the score of every S, so all dimensions visible at a glance. 👍 Add a simple gauge or bar showing the overall 5S score per area and for the whole company 👍 Use color‑coded dashboards or boards (green/yellow/red) where teams can see their latest scores, trends and key gaps 5S will never be “just cleaning” if it is measured, visualized and reviewed like any other key performance indicator : it becomes the backbone of safety, quality and delivery, and a daily signal of how seriously a company treats operational excellence.

Every time you draw an org chart, you're picking sides in battles that haven't started yet. That's just human wiring. Social identity theory shows people quickly form in-groups and out-groups, even on trivial distinctions. Any structure you choose will naturally create "us vs. them" dynamics. Without intentional design, you get the classic blame cycles: Sales says Marketing sends bad leads, Marketing says Sales doesn't follow up, and Engineering blames both teams for changing requirements mid-sprint. But you can architect your organization so those tribal instincts work for you instead of against you. Here's how: Design for the Work --------------------- ↳ Organize around the work. Map how value flows to the customer and align teams to that flow. Don't organize around internal convenience—and definitely don't design around specific people. Organize around the critical path from idea to customer value. ↳ Clarify decision authority. Ambiguity breeds conflict and delays. Be explicit about who decides, who's consulted, and who's informed. Unclear authority creates either turf wars or decision paralysis. ↳ Define cross-team handoffs. Wherever work passes between groups, nail down who owns what, what "done" looks like, and how problems get escalated. The real risk isn't within teams; it's in the transitions between them. Align the Incentives --------------------- ↳ Set common goals. Give cross-functional groups a small set of shared outcomes—revenue growth, customer retention, cost savings or any other collectively important target. Use cascading goals and KPI trees to show how individual work connects to the bigger picture. This keeps everyone pointed in the same direction instead of optimizing their own corner. ↳ Align rewards with cooperation. If bonuses are based only on silo performance, you'll get silo behavior. Shared metrics and joint outcomes encourage people to actually help each other succeed. Enable the Collaboration -------------------------- ↳ Support cross-functional work. Make sure teams have the data, tools, and forums needed to work together effectively. If those supports aren't intentional, collaboration erodes under daily pressures and competing priorities. You can't eliminate tribal instincts; they're hardwired. But you can architect your organization so those instincts work for you instead of against you. You probably can’t eliminate "us vs. them" entirely. But you can design so the structure channels natural group dynamics toward shared execution. #strategy #execution #orgdesign #teamwork

Total Productive Maintenance (TPM) is a comprehensive approach to equipment maintenance that aims to achieve perfect production: zero breakdowns, zero defects, and zero accidents. It integrates maintenance into the daily operations of all employees, from operators to managers, to maximize equipment effectiveness and promote a culture of ownership. The Pillars of TPM: TPM is built on 8 pillars, each focused on proactive and preventive maintenance to enhance operational efficiency: Autonomous Maintenance (Jishu Hozen): Operators take ownership of routine maintenance (cleaning, inspection, lubrication). Empowers operators and reduces dependency on maintenance teams. Planned Maintenance: Scheduled preventive maintenance based on failure data and lifecycle analysis. Reduces unplanned downtime and extends equipment life. Quality Maintenance: Uses root cause analysis and preventive tools to eliminate defects caused by equipment. Focuses on maintaining conditions that assure quality output. Focused Improvement (Kobetsu Kaizen): Cross-functional teams tackle chronic problems and inefficiencies through structured problem-solving. Drives small, incremental improvements in performance. Early Equipment Management: Involves maintenance and production input during equipment design or procurement to improve maintainability, safety, and ease of operation. Education and Training: Develops skills across all levels to ensure correct operation, maintenance, and continuous improvement knowledge. Safety, Health, and Environment: Ensures machines and processes are safe and environmentally friendly. Aims for a zero-accident workplace. TPM in Administrative Functions: Applies TPM principles to office and support areas, optimizing workflows, information flow and efficiency. Benefits of TPM: Fewer breakdowns and unplanned stoppages Higher equipment uptime and productivity Improved product quality Reduced safety incidents Increased employee engagement and accountability Lower total maintenance costs Real-World Example: Context: A bottling plant suffered from frequent filler machine breakdowns, causing lost time and overworked maintenance teams. TPM Applied: Operators were trained to clean and inspect the machine daily (Autonomous Maintenance). Maintenance scheduled a monthly deep inspection (Planned Maintenance). The cross-functional team did a root cause analysis of breakdowns (Focused Improvement). Operator logs and visual indicators were introduced (Education/Training). Result: Breakdowns dropped by 70%, and the plant’s OEE rose from 65% to 85% within six months.

The Fab Whisperer: Why Fabs Struggle with Change? Fabs are masterpieces of precision — and monuments of inertia. Every system is tuned for repeatability. Every deviation looks like risk. So when fabs need to evolve — new process, new toolset, new flow, new way of working — the immune system attacks the change itself. Most fabs don’t fail to change because people resist. They fail because systems are designed not to change. Change competes with three powerful antibodies: 1. Optimization for stability – personnel trained to “lock” things not to experiment. 2. Fragmented ownership – Improvements that cross boundaries die between silos. 3. Metrics addiction – Everyone optimizes their own KPI, even when it hurts fab-wide flow. You can’t “lean out” a fab that punishes deviation. I’ve seen fabs that hold daily CIP meetings — yet every idea needs four sign-offs. Fabs that build beautiful dashboards — but hide the real numbers because they might “confuse” executives. And fabs where different teams each run their own Kaizens — canceling each other’s gains. When culture, metrics, and risk tolerance collide, even the smartest digital roadmap stalls. So What do I do about it? I separate “stable to operate” from “safe to change.” A fab runs in two modes: operate and improve. Operate mode locks parameters and minimizes variability. Improve mode deliberately introduces controlled variability, measures, and folds back what works. Without that boundary, everything feels unsafe to touch. I try to build cross-functional alignment without breaking the org. We may not need to redraw boxes; we need to connect them. The fastest fabs I’ve seen use temporary flow teams — small, time-bounded task forces that cut across Process, Equipment, IE, and Production to attack one measurable constraint end-to-end. They report results into the existing structure but operate outside its inertia. Essentially rewiring how problems flow through the structure. I always try to empower real change agents. Change won't happen through slogans but rather through trusted operators who bridge functions. Effective change agents share three traits: They have credibility on the floor — peers listen because they deliver. They think in system effects — they see how a fix in etch can hurt litho. They speak data fluently and humanly — turning dashboards into action. Their value? They accelerate learning loops. I reward evidence, not activity. Real change isn’t the number of workshops held — it’s variance reduced per month. I build feedback loops, not blame loops. Measuring learning speed, not fault. In the best fabs, the only constant is change. They’ve learned that stability isn’t the absence of motion — it’s the ability to evolve without losing control. Those fabs don’t fear drift, they fear stagnation. #TheFabWhisperer #Semiconductor #FabOperations #ChangeManagement #ContinuousImprovement #ManufacturingExcellence #CultureOfChange #OperationalExcellence #SemiconductorManufacturing

How hard should you work to solve a problem? Maybe hard. Maybe not—if you eliminate it altogether. Like processes. Why spend time improving a process that shouldn't exist in the first place? Like reporting. Which, in many (most?) organizations, is a mess. During a client assessment this week, we uncovered a weekly report that was robbing leaders of valuable time. While it *only* takes 10 minutes to complete (best case process time), that's 2,383 hrs per year across the organization. ➡️ That's the equivalent of paying more than one leader a full salary to do nothing but complete a report. And the report? - Requires information that already exists in systems - Asks for monthly data . . . in a weekly report - Includes questions where the answers are already known The solution is NOT: - Automating the report - Using AI to complete the report The report—in its current form—needs to go. Some of the information IS vital to know weekly. But it needs to be delivered in a more efficient way, with less human effort. Those 2,383 hours (freed capacity) could be spent: - Coaching and developing teams - Solving real problems - Spending time with customers - Planning for growth - Not working 60 hours a week And here's the part most organizations miss: Reports don't deliver value to customers unless they actually use them. If you want to clean this up, start here: 1️⃣ Assemble a cross-functional team (no more than 10) 2️⃣ Decide who needs what information and when (cadence)—with a bias toward data that drives decisions, not "nice to know" 3️⃣ Conduct a current state "report inventory": who gets it, when, and why. 4️⃣ Revisit actual needs based on what you find. 5️⃣ Redesign how information is delivered (format matters!)—with as little human effort as possible. Question every report. Quantify the time. Eliminate what shouldn't exist. Cleaning up reporting is one of the most respectful things you can do for your people. And it will almost always reveal bigger problems worth solving.