A plant can have excellent individual departments and still fail the customer. I have audited organisations where production hit their OEE targets, quality passed their final inspections, and engineering released designs on schedule. Yet, the overall scrap rate was unacceptable, lead times were increasing, and customer complaints were rising. The disconnect happens at the boundaries between departments.

When a defect occurs, the natural response in a siloed organisation is defensive. Production blames engineering for tight tolerances. Engineering blames the supplier for material inconsistency. Quality blames production for process drift. The actual problem is rarely owned by a single function, but the resolution gets trapped in the gaps between them. An 8D report gets passed around like a hot potato.

Over the last twenty years implementing and transitioning ISO 9001 and IATF 16949 systems, I have seen that structural integration matters more than individual departmental strength. The solution is mandating cross-functional teams for problem-solving, continuous improvement, and risk management. You force the boundaries to dissolve by putting production, engineering, quality, and supply chain representatives in the same room with a shared mandate.

Rebuilding the 8D Process for Complex Supplier Failures

Consider an automotive supplier facing a catastrophic component failure resulting in a 10,000-part customer return. In a functionally managed environment, the initial reaction is fragmented. Each department points to the others: production claims the process is running to standard, engineering insists the design is valid, and supplier quality points to the material certificate. The 8D process stalls at D2 because no single function owns the full process map.

To break this deadlock, you must restructure the 8D team. Put a Quality Manager in the lead, but mandate that Process Engineering, Production Management, Development, and Supplier Quality Engineering are core members. At D0 and D1, the team operates with a single shared data set rather than departmental filtered reports. The problem description at D2 must integrate production symptoms, engineering tolerances, and material realities into one unified statement.

The root cause analysis at D4 is where the silo mentality truly breaks down. In this automotive scenario, applying tools like 5 Why and Fishbone across functions reveals that the defect is multifactorial. Engineering specified a tolerance too tight for the production environment's capability. The supplier could not consistently meet the print, and the quality control plan lacked the automated inspection necessary to catch the drift early. No single department caused the failure, and no single department could fix it.

Rebuilding the 8D Process for Complex Supplier Failures — where the principle meets the process.
Rebuilding the 8D Process for Complex Supplier Failures — where the principle meets the process.

The corrective action at D5 and D6 then becomes a synchronized effort. Engineering opens the tolerance band where Cpk data proves it is safe to do so. Production adjusts the process parameters to increase stability. Supplier quality works with the vendor to upgrade material consistency, and quality engineering installs automated vision inspection. Updating the DFMEA, PFMEA, and Control Plan is done collectively, preventing recurrence.

Cross-Functional Project Management in Manufacturing

The same integration principle applies to new product introduction and industrialisation. When projects are managed sequentially—engineering throws the design over the wall to production, who throws it to quality—the result is missed deadlines and budget overruns. An industrial automation manufacturer struggling with a 60% project success rate shifted to a cross-functional project management model to align their APQP process.

Instead of function-specific plans, the project manager coordinates a single integrated team. Daily stand-up meetings include development, production, and quality engineers. This eliminates the classic scenario where production builds tooling that quality later realises cannot be practically inspected. When all functions contribute to the planning phase, the scope, timeline, and budget reflect manufacturing and quality realities, not just design intent.

Integrated Project Execution Phases

  1. 01InitiationCross-functional team defines scope, budget, and timeline with full operational visibility.
  2. 02Integrated PlanningDevelopment, production, and quality submit synchronous plans rather than isolated silos.
  3. 03ImplementationDaily cross-functional stand-ups identify and resolve bottlenecks in real-time.
  4. 04ClosureTeam collectively reviews performance against the APQP requirements and documents lessons learned.
Phased approach where quality and production constraints are evaluated alongside design intent.

Driving Productivity Through Integrated Kaizen

Continuous improvement initiatives often stall because they are owned by a single department. A heavy manufacturing plant looking to improve OEE found that production-focused Kaizen events only optimized machine speed, ignoring the quality defects that followed. Maintenance optimized schedules, but operators still struggled with complex setups. The functional improvements cancelled each other out at the system level.

By mandating cross-functional Kaizen teams, the dynamic changes. A team composed of a process engineer, quality engineer, maintenance technician, and line operator approaches a problem like long setup times from all angles. Production outlines the operational complexity, quality flags the time spent on first-piece inspection, and maintenance highlights tooling inefficiencies. This holistic view is what enables methodologies like SMED to actually succeed.

In this environment, setup times were reduced from 45 minutes to 13 minutes because the team could redesign the process comprehensively. They implemented external preparation while the machine was still running, simplified the clamping mechanisms, and standardized the first-piece inspection process. OEE jumped from 68% to 92% because the solutions addressed the entire value stream, not just a single workstation.

Managing Aerospace Risk Across Disciplines

In highly regulated environments like aerospace, functional risk assessments are dangerous. When a safety engineer evaluates a new component design in isolation, they may miss process capability limitations. When a quality engineer assesses the inspection plan without understanding the maintenance schedule, they may underestimate the probability of failure. Risk becomes invisible at the intersections of the business.

I introduced Routing Verification KPIs at a major aerospace manufacturer to cut internal lead times, and a critical part of that success was cross-functional risk management. A team comprising safety, design, process, and quality engineers must sit together to score probability and impact. If safety identifies a potential failure mode with a high impact score, design and process engineering must immediately collaborate on mitigation strategies, such as redundant design features or process simplification.

Problems are inherently cross-functional. Forcing a single department to own a multi-departmental failure guarantees delays.

This collaborative approach to FMEA and risk assessment reduces the time required to evaluate and approve new components. More importantly, it drastically reduces both safety and quality incidents. Because the team implements holistic mitigation strategies—combining design safety margins, robust process controls, and automated quality checks—the overall risk profile of the product drops significantly before it ever reaches the production floor.

Structural Requirements for Dismantling Silos

Creating effective cross-functional teams requires more than just putting people in a room. Leadership must explicitly mandate this structure for every 8D, every APQP project, and every continuous improvement event. If executive management allows departments to retreat to their silos during conflicts, the integration fails. Performance metrics and recognition systems must be tied to team outcomes, not departmental efficiencies.

Functional vs. Cross-Functional Problem Solving

What siloed teams do

  • Defend departmental KPIs and shift blame during failures.
  • Pass incomplete 8D reports between functions, delaying root cause analysis.
  • Optimize local speed at the expense of downstream quality and total OEE.
  • Assess safety and process risks independently, missing systemic interactions.

What integrated teams do

  • Share accountability for customer returns and overall scrap rates.
  • Analyse failure modes collectively using unified data sets and process maps.
  • Apply methodologies like SMED with inputs from production, maintenance, and quality.
  • Evaluate probability and impact collaboratively to design robust mitigation strategies.
The operational difference between managing by department and managing by value stream.

Training must also reflect this reality. Teaching problem-solving tools like 5 Why or Fishbone to only the quality department is a waste of time. Production supervisors, design engineers, and supplier managers need to understand the methodology. When everyone speaks the same quality language, the friction in identifying root causes and implementing permanent corrective actions disappears.

Ultimately, maintaining functional silos is a choice to accept substandard results. When I built a greenfield QA/QC department for a 900+ employee plant at SNOP, the priority was not creating the strongest independent quality function. It was integrating quality professionals directly into the production and engineering teams. We achieved operational excellence not by policing the process, but by dismantling the boundaries that prevented the process from improving itself.