In 2011, researchers at Harvard Business School demonstrated that people place disproportionately high value on things they helped create. Participants who folded their own origami models valued them at roughly five times the price independent evaluators were willing to pay. The cognitive mechanism is simple: the labour invested in building something generates an emotional bond that distorts the creator's perception of objective value. The researchers called this the IKEA Effect.
This cognitive bias creates severe operational damage when it infects an organisation's quality management system. The inspection protocol your engineering team designed from scratch three years ago, the custom Excel dashboard tracking your daily KPIs, and the corrective action workflow that requires six approval signatures are all prime candidates. The teams that built them defend them fiercely, regardless of cycle time data, audit findings, or process bottlenecks.
In my experience auditing and implementing ISO 9001 and IATF 16949 systems across aerospace and automotive plants, the resistance to replacing custom-built quality processes is rarely grounded in technical justification. It is grounded in effort justification and professional identity fusion. Quality professionals must learn to separate their ego from their engineering deliverables to maintain operational excellence.
The Mechanics of Process Attachment
Effort justification is the primary psychological driver. When a cross-functional team invests eighteen months and hundreds of hours developing a bespoke QMS, they need to believe that investment was worthwhile. Admitting that a standard, off-the-shelf ISO 9001 framework could replace 60% of their design with something simpler and faster implies their effort was wasted. The brain protects itself from this conclusion by inflating the perceived value of the custom output.
Professional identity fusion accelerates the problem. A quality engineer who designed a custom PFMEA methodology views that document as a direct reflection of their technical competence. Critiquing the methodology's effectiveness feels like a personal attack on their engineering judgment. Suggesting a replacement feels like an attempt to erase their historical contribution to the company entirely.
These cognitive traps trigger sunk cost escalation. Once an organisation has invested heavily in building a custom process, they continue pouring resources into maintaining and patching it. Every additional workshop held to fix a broken workflow, and every line of VBA code added to a brittle spreadsheet, deepens the emotional attachment. This makes the eventual transition to a superior, standardised solution progressively more difficult.
I have seen plants where the document control process required seven approval signatures simply because a committee could not reach consensus five years ago. The nonconformance workflow had fourteen steps because every department manager demanded a review point. These are not purposeful engineering decisions; they are political compromises hardened into permanent operational bottlenecks by the bias of creation.
Where Customisation Hides Operational Risk
Customisation bias rarely manifests at the macro level of an entire QMS platform. It hides in the granular, everyday tools that quality teams use to execute their work. These seemingly innocuous bespoke solutions accumulate technical debt, slow down cycle times, and create massive variability in how organisations capture and resolve critical defects.
Incoming inspection protocols are a frequent vector for this bias. An organisation designs its own sampling scheme rather than adopting an established standard like ISO 2859-1 or MIL-STD-105E. The custom plan is over-engineered, takes three times longer to execute, and catches roughly the same number of nonconformances. Yet the team defends it passionately because they built it specifically for their product lines, even when the specificity adds zero measurable value.
Bespoke corrective action forms might be the most pervasive example. I have reviewed multi-page CAPA documents featuring embedded decision trees, risk matrices, and layered verification checklists. They are engineering marvels, but they are functionally unusable. The average cycle time for closing a corrective action in these organisations often exceeds ninety days simply because the sheer complexity of the form creates friction that discourages proper root cause analysis.
Homegrown KPI dashboards suffer the same fate. An operations team builds a custom spreadsheet that pulls data from three different ERP modules, requires manual entry for downtime metrics, and takes a specialist four hours per week to maintain. A commercial business intelligence platform could automate the dashboard and display it in real time. But the creators have an emotional investment in every cell and every conditional format, so the manual process survives.
Quantifying the Cost of Bespoke Systems
The financial and operational costs of creation bias compound silently over time. Every hour your quality engineers spend maintaining a proprietary, convoluted audit checklist is an hour they are not spending on actual process improvement. The labour of maintaining what you originally built consumes the resources necessary to build what your manufacturing lines actually need next to stay competitive.
Adaptation costs rise significantly when quality systems are entirely bespoke. When a new regulatory requirement or standard update emerges, organisations using standard frameworks can quickly adopt updated templates. Organisations relying on heavily customised, undocumented QMS platforms must conduct exhaustive gap analyses, redesign the affected processes, rewrite their documentation, and retrain their personnel from scratch.
| Cost Category | Standard Framework Impact | Bespoke System Impact |
|---|---|---|
| Maintenance Labour | Predictable, vendor-supported updates | Continuous internal firefighting and patching |
| Process Cycle Time | Optimised for speed and clarity | Bottlenecked by historical political compromises |
| Benchmarking Capability | Direct comparison to industry peers | Isolated metrics with no external context |
| Auditor Familiarity | Immediate alignment with IATF / AS9100 | Requires extensive custom procedure translation |
Benchmarking becomes practically impossible. You cannot reliably compare your OEE, scrap rates, or cost of poor quality against industry standards if your underlying data collection methodologies are completely unique. This isolation from external reference points makes it incredibly difficult to identify performance gaps, justify capital improvement investments, or demonstrate objective progress to stakeholders who measure success against standard industry norms.
The Paradox of Ownership and Objectivity
A sense of ownership over quality processes is not inherently detrimental. In fact, employee ownership is one of the strongest predictors of a mature, effective quality culture. Organisations where operators and engineers feel personally responsible for their management systems consistently outperform organisations where quality procedures are seen as an external imposition forced upon them by corporate quality departments.
The operational problem is ownership operating without objective constraint. Quality excellence requires a paradoxical approach to engineering work. You must care enough about your processes to invest in them deeply, but remain sufficiently detached to evaluate their effectiveness honestly. You must take pride in the systems you design, but never let that pride prevent you from retiring those systems when they become obsolete or inefficient.
The purpose of a quality process isn't to stand as a monument to its creators. It's to produce quality outcomes.
This is the discipline that separates highly capable quality organisations from mediocre ones. Great organisations can look at their own engineering work and identify its flaws clearly. Mediocre organisations can identify the flaws in external frameworks, vendor software, or standard templates, but remain functionally blind to the exact same flaws embedded in the custom systems they built themselves.
Strategies to Break the Emotional Attachment
Overcoming attachment bias requires structural interventions, not just individual awareness. Conduct external benchmarking before initiating any internal redesign. Before investing capital in fixing a broken custom process, benchmark it against at least three standard industry alternatives. If an off-the-shelf solution performs comparably or better, the burden of proof must fall on the custom solution to justify its continued existence.
Implement mandatory build-versus-buy assessments on a fixed schedule. Every three years, systematically evaluate each element of your quality system against commercially available alternatives. This evaluation must not be framed as a threat to the original developers. It must be established as a routine maintenance practice that guarantees the organisation is always operating with the most efficient, capable tools available on the market.
Approaches to Quality Tool Lifecycle
Attachment-driven behaviour
- Defending custom processes against external audit findings
- Adding complexity to patch failing bespoke workflows
- Evaluating new tools against the old tool's features
- Treating process replacement as a personal failure
Objective-driven behaviour
- Benchmarking custom processes against ISO / industry standards
- Replacing high-friction workflows with simplified templates
- Evaluating tools against current operational requirements
- Treating process replacement as standard system maturity
Rotate process ownership to break the bond between creator and system. The attachment to a custom process strengthens with time and personal investment. Rotating quality process ownership every two to three years prevents individuals from developing entrenched loyalty to specific documents. The incoming owner evaluates the process with fresh eyes and no emotional investment, while the outgoing owner applies their expertise to a new operational area.
Separate process design authority from process evaluation authority. The engineers who designed a control plan or MSA study should never be the only people evaluating its ongoing effectiveness. Independent review through internal audit, peer assessment from sister facilities, or third-party consultation provides the objectivity that creators naturally lack due to their psychological investment in the outcome.
Establishing the Standard for Replacement
Most organisations ritualise creation. They issue formal recognition to teams that develop new inspection protocols, design custom software, or implement novel tracking systems. They almost never reward teams that make the difficult decision to retire a legacy process in favour of a superior standardised alternative. This cultural dynamic actively feeds the creation bias and guarantees operational stagnation.
To counteract this, executive leadership must make process replacement a celebrated outcome rather than a tacit admission of engineering failure. Recognising the maturity required to say a system has served its purpose and must now be retired establishes a culture of objectivity. It shifts the organisational focus away from building bespoke monuments and toward optimising actual quality outcomes on the production floor.
There are, of course, legitimate reasons to invest in bespoke quality processes. Organisations operating in novel regulatory environments, or those utilising manufacturing technologies that existing frameworks genuinely cannot accommodate, often require custom engineering. However, in two decades of quality work, the number of custom quality processes I have seen that were genuinely superior to available standardised alternatives is exceptionally small.
Apply a simple evaluation metric: if another organisation had already built exactly the process you are planning to build, would you purchase it from them, or would you still choose to build your own? If the honest answer is that you would buy the existing solution, your only motivation for building is the psychological reward of creation. Your quality system cannot afford the operational cost of that reward.