AS9100 readiness is rarely a clean split between process design and cultural change. In most aerospace and defense environments, organizations that sustain certification over time treat it as roughly 50/50:
- Process design & systems (about half): Defining, documenting, and integrating procedures, controls, and records that satisfy the standard.
- Cultural change & behaviors (about half): Making those processes the normal way of working so they are followed under real schedule, cost, and change pressure.
What falls under process design for AS9100?
Process design is the visible part: what auditors read and what systems enforce. Typical scope includes:
- Documented processes and interactions: Clear process owners, inputs/outputs, interfaces to MES, ERP, PLM, and QMS, and how you control changes.
- Risk-based thinking and planning: Formal risk assessments for design, production, special processes, outsourced work, and critical characteristics.
- Configuration and change control: How engineering changes, deviations, concessions, and rework are requested, approved, traced, and communicated to the shop floor.
- Nonconformance and corrective action flows: NCR, MRB, and CAPA workflows, including containment, root cause, verification of effectiveness, and evidence.
- Internal audits and management review: A structured internal audit program and management review cadence aligned to AS9100 requirements.
- Evidence and records management: How you capture, store, and retrieve records from legacy systems, paper travelers, and newer digital tools.
In brownfield environments, a large share of the process work is not invention, but mapping, rationalizing, and closing gaps across existing practices and systems. You often have to reconcile:
- Multiple versions of work instructions across paper, PDFs, MES, and local network drives.
- Inconsistent routing and traveler structures across product lines or cells.
- QMS procedures that do not fully match how work is actually executed on the floor.
Because systems replacement is expensive to validate and risky for traceability, most organizations do not solve AS9100 readiness by swapping out core MES/ERP/PLM platforms. They instead:
- Tighten process definitions and governance around existing tools.
- Add lighter-weight layers (digital travelers, audit trails, document control) on top of legacy systems.
- Standardize how data is captured and retrieved for audits without redesigning every system.
What falls under cultural change?
Cultural change is what determines whether the designed processes survive real-world pressure. Common cultural elements include:
- Leadership behavior: Whether supervisors and managers consistently prioritize conforming process over shortcutting for schedule.
- Attitudes toward documentation: Moving from “paperwork for auditors” to “records that protect us and our customers.”
- Ownership of quality: Operators, planners, buyers, and engineers seeing quality and traceability as their responsibility, not just QA’s job.
- Comfort with escalation: People raising issues, stopping work for unclear or incorrect instructions, and opening NCRs without fear of blame.
- Follow-through on corrective actions: Actually implementing and sustaining changes from CAPA and internal audits, not just closing them on paper.
Without this cultural foundation, you can be “audit-ready on paper” but brittle in practice. Typical failure modes:
- Procedures that exist but are quietly ignored in favor of tribal knowledge.
- Training that is signed off quickly to clear a requirement, not to build competence.
- Internal audits run as a formality, with minimal challenge and little impact on decisions.
- Corrective actions that focus on containment and documentation rather than changing upstream behaviors.
These issues are common in regulated, long-lifecycle environments where legacy habits are deeply entrenched and “we survived past audits” is used to justify not changing.
How the balance shifts by maturity and context
The apparent split between process design and culture depends heavily on where you are starting from:
- Low process maturity, weak culture: You must do both at once. New procedures, clarified roles, and systems changes in parallel with clear expectations and coaching. Neither side can wait.
- Strong informal culture, weak documentation: Much of the work is codifying what already works, adding controls and traceability. Culture work focuses on accepting formalization and evidence as non-negotiable.
- Heavy documentation, weak culture: The process stack may be nominally complete, but not lived. Here, 70% of the effort can feel like culture and leadership alignment: simplifying procedures, aligning incentives, and making it safe to say “we don’t actually do it that way.”
- Brownfield, multi-system sites: Extra effort is required to align culture across different cells, plants, and systems so that AS9100 is applied consistently despite different tools.
In all cases, AS9100 readiness is not just a project to build manuals and process maps. It is an ongoing alignment between how work is specified, how it is executed, and how the organization responds when those diverge.
Why focusing on only one side usually fails
Two recurring patterns tend to fail in aerospace-grade environments:
- Process-only focus: Large consulting or documentation efforts produce a complete QMS on paper, but operators and engineers perceive it as overhead. Audits may pass initially, but nonconformances and customer escapes continue because the real work still follows legacy habits.
- Culture-only focus: Emphasis on “quality mindset” and slogans without tightening processes, interfaces, and records. Enthusiastic teams still struggle to produce coherent evidence, manage configuration, or show consistent risk-based decision-making during audits.
In regulated, long-lifecycle operations, the cost of incomplete change is high: re-audits, customer findings, repeated CAPAs, and plant-level friction between operations, engineering, quality, and IT. Closing those gaps almost always requires revisiting both process design and culture together, within the constraints of existing systems and limited downtime.
Practical way to think about the split
A useful working model for AS9100 readiness in most plants is:
- About half the effort is designing, tightening, and integrating processes, controls, and evidence flows across your existing systems and suppliers.
- About half is building and reinforcing behaviors so people reliably follow those processes, surface gaps, and engage with audits and corrective actions honestly.
The exact ratio in your environment will depend on your starting point, the age and heterogeneity of your systems, and the credibility of leadership when tradeoffs arise between schedule, cost, and conformance. Treating either dimension as secondary usually shows up later as audit risk, operational friction, or both.