English Version
In the world of engineering and quality management, we tend to believe that if we can design a better process, build a more robust system, or adopt superior technology, the results will follow. We invest heavily in technical excellence: statistical models, inspection protocols, PLM platforms, MBSE frameworks, supplier scorecards. We treat organizational transformation as an engineering problem that can be solved with the right specifications.
But what if the real obstacle has nothing to do with technology at all?
This is the unsettling finding behind Chad Jackson’s “Resistance Paradox,” a research report based on surveys of 303 engineering executives and change agents conducted through Lifecycle Insights. Jackson, who has spent over 20 years analyzing engineering technology decisions and surveyed more than 20,000 practitioners, uncovered something that challenges the fundamental assumptions of how quality and engineering leaders approach transformation:
The main reason for the slow progress of engineering change is the emotional reactions of the people involved. Not process gaps. Not technical debt. People.
The Research Behind the Resistance Paradox
Chad Jackson is the Chief Analyst and CEO of Lifecycle Insights, an independent research firm focused on engineering transformation. His work sits at the intersection of technology adoption, organizational behavior, and engineering leadership. Unlike vendor-sponsored research, Jackson’s studies are designed to reveal what actually happens inside engineering organizations when new processes, tools, and systems are introduced.
The Resistance Paradox report emerged from a survey of 303 engineering executives and change agents across multiple industries. The research was not looking for resistance — it stumbled into it. As Jackson wrote: “This finding was surprising enough that we’re developing a full report on it.”
The data revealed a distribution of obstacles that defies conventional wisdom:
| Obstacle Category | Percentage of Total Friction |
|---|---|
| Emotional reactions (fear, insecurity, uncertainty) | 45% |
| Process instability during transition | 28% |
| Technical gaps, resource constraints, other | 27% |
Nearly half of everything that slows down an engineering transformation lives in what Jackson calls “the human interior” — something far harder to architect than any workflow or governance model.
The Core Paradox
The paradox is this: successful engineering transformations do not avoid friction — they navigate it.
Most organizations operate on an implicit assumption: if a transformation encounters resistance, something is wrong with the plan. The solution, then, is to refine the plan, fix the process, upgrade the tool, or replace the vendor. But the research shows that successful transformations face just as much resistance as failed ones. The difference is not in the absence of friction, but in how the organization responds to it.
As Jackson put it: “The technical case for a transformation can be airtight. The business value, demonstrable. And still, the initiative moves at a fraction of the expected pace because the emotional groundwork wasn’t laid first.”
This is the paradox: the organizations that succeed are not the ones that eliminate resistance. They are the ones that expect it, prepare for it, and build support structures before the resistance compounds.
The MBSE Collaboration Paradox
Jackson identified a related paradox in the adoption of Model-Based Systems Engineering (MBSE). Most people assume that MBSE is fundamentally about modeling — creating digital representations of complex systems to reduce errors and accelerate development. The technology is sophisticated and the value proposition is clear.
But Jackson found that the number one reason organizations fail to adopt MBSE successfully is not technical. It is collaboration.
MBSE requires engineers who have worked in silos for decades to suddenly share their models, expose their assumptions, and coordinate their work in ways that feel fundamentally uncomfortable. The tool demands collaboration, but the culture has never been built for it. The technology creates the possibility of working together, but the people resist that possibility because it threatens their autonomy, their expertise boundaries, and their established ways of working.
This is the Collaboration Paradox: the tool that promises better collaboration is rejected precisely because it requires collaboration.
How This Impacts Quality Management
For quality professionals, the Resistance Paradox is not an abstract organizational theory. It is a daily operational reality. Consider how resistance manifests in common quality initiatives:
1. Supplier Quality Improvement Programs
When a quality team introduces new supplier scorecards, tighter AQL standards, or more rigorous PPAP requirements, the supplier’s reaction is rarely a rational assessment of the new requirements. Instead, the typical responses are:
- Fear of losing business — “If I admit defects, they will find another supplier.”
- Insecurity about capability — “We have been doing this for 20 years. Why do they think we need new processes?”
- Uncertainty about expectations — “What exactly do they want from us? The requirements keep changing.”
The technical solution — a better scoring system, a clearer specification — addresses none of these emotional barriers. The supplier who is afraid will hide data. The supplier who is insecure will resist change. The supplier who is uncertain will comply superficially and fail fundamentally.
In our own experience managing supplier quality across multiple product categories, the pattern repeats consistently. The supplier with the best technical capability but the worst cultural openness consistently underperforms compared to the supplier with moderate capability but high trust and transparency.
2. Internal Quality System Overhauls
When a company migrates from an outdated quality management system to a modern digital platform, the resistance profile is strikingly similar:
- Engineers fear losing their established workflows — “The old system works. Why change?”
- Inspectors fear being replaced by automation — “If the system can do my job, what happens to me?”
- Managers fear losing visibility and control — “I won’t know what’s happening if it’s all in a dashboard.”
The 28% of friction attributed to process instability is real — transitions are genuinely disruptive. But the 45% attributed to emotional reactions is the dominant cost driver, and it is the one that quality leaders most often neglect in their implementation plans.
3. Root Cause Analysis and Corrective Action
The Resistance Paradox also explains why root cause analysis so frequently fails to produce lasting corrective action. When a quality engineer conducts a 5-Why analysis or builds a fishbone diagram, the technical methodology is sound. But if the people involved fear that identifying the root cause will lead to blame, punishment, or reorganization, they will actively resist the investigation.
The result is superficial root causes that point to “operator error” or “material variation” rather than the systemic issues that actually need to be addressed. The quality team produces a technically complete CAPA report that solves nothing, because the emotional groundwork — creating psychological safety for honest investigation — was never laid.
The Cost of Ignoring Resistance
Jackson’s research quantifies what quality leaders have felt intuitively: resistance is a cost driver, not a soft issue.
When resistance is not anticipated and managed, it taxes the transformation in three measurable ways:
| Cost Dimension | Impact |
|---|---|
| Bandwidth | Engineers and quality professionals spend time managing resistance instead of executing the transformation |
| Morale | Unaddressed resistance creates a toxic undercurrent that spreads beyond the immediate initiative |
| Executive attention | Leaders are pulled into firefighting and conflict resolution instead of strategic direction |
The research suggests that organizations that anticipate resistance and build support structures around it before the resistance compounds reach value realization faster and with less organizational damage. This is not about being “soft.” It is about being strategically effective.
The Value-Risk Miscalculation
Jackson identified another critical failure pattern: how organizations evaluate the risk of transformation.
Most investment decisions weigh business value against disruption risk. But disruption risk is almost always framed in operational terms — timeline delays, resource costs, program continuity. What the research reveals is that the real disruption risk is human, not operational.
When a quality leader proposes implementing a new statistical process control system, the business case focuses on defect reduction, cost savings, and cycle time improvement. The disruption risk assessment considers implementation timeline, training hours, and system integration complexity. But neither evaluation accounts for the emotional reactions of the engineers who will use the system daily, the inspectors whose roles will change, or the managers whose oversight methods will be transformed.
This is the Value-Risk Miscalculation: organizations systematically underestimate the human dimension of disruption risk while overestimating their ability to absorb it through technical competence alone.
What Quality and Engineering Leaders Should Do Differently
Based on Jackson’s findings and their alignment with practical quality management experience, here are five actionable recommendations:
1. Do the Emotional Groundwork Before the Technical Work
Before introducing any new quality process, inspection protocol, or engineering tool, invest time in understanding the emotional landscape of the people who will be affected. What are they afraid of? What makes them insecure? What uncertainties do they carry?
This is not a “nice to have.” It is a prerequisite for successful implementation.
2. Build Support Structures Before Resistance Compounds
Jackson’s research shows that organizations that succeed build support networks before launching the transformation. This means:
- Training programs that address fears, not just technical skills
- Peer champions who can model the new behavior
- Feedback channels that allow resistance to be expressed constructively
- Leadership visibility that demonstrates commitment without dismissiveness
3. Treat Resistance as Data, Not Defiance
When people resist a quality initiative, they are providing valuable information about what the initiative is missing. Fear signals that the change has not been explained clearly. Insecurity signals that training is inadequate. Uncertainty signals that expectations are ambiguous.
Each form of resistance points to a specific gap in the implementation plan. Listen to it.
4. Expect Friction, Do Not Fear It
The Resistance Paradox teaches that friction is not a sign of failure. It is a normal part of the transformation process. The goal is not to eliminate friction but to navigate it effectively.
5. Build Trust Before Redesigning Processes
As the research notes: “Building trust takes longer than redesigning any established process.” This is particularly true in quality management, where trust between the quality team and production engineers, between the company and its suppliers, and between leadership and front-line workers is the foundation of every successful initiative.
Invest in trust-building as deliberately as you invest in process design. It will pay dividends that no technical optimization can match.
The Quality Leader’s Mandate
The Resistance Paradox ultimately challenges quality and engineering leaders to expand their definition of competence. Technical excellence is necessary but insufficient. The most sophisticated quality management system in the world will fail if the people who must use it are afraid, insecure, or uncertain.
Jackson’s research, grounded in data from 303 engineering executives, delivers a clear message: the future of quality and engineering transformation belongs not to those who build the best technology, but to those who understand and navigate the human dynamics that determine whether that technology will ever be used effectively.
This is not a soft skill. It is a strategic capability. And it is the one that separates organizations that merely announce transformations from those that actually achieve them.
What resistance have you encountered in your quality initiatives, and how did you navigate it?
中文版
在工程與品質管理的世界裡，我們傾向相信：只要設計出更好的流程、建立更穩健的系統、採用更優秀的技術，成果自然會隨之而來。我們在技術卓越上投入大量資源：統計模型、檢驗流程、PLM 平台、MBSE 框架、供應商評分卡。我們將組織轉型視為一個可以用正確規格解決的工程問題。
但如果真正的障礙與技術完全無關呢？
這是 查德·傑克森（Chad Jackson）的「抵抗悖論（Resistance Paradox）」 研究中令人不安的發現。這份研究報告基於 Lifecycle Insights 對 303 名工程高管和變革推動者的調查。傑克森花了超過 20 年分析工程技術決策，調查了超過 20,000 名從業者，他發現了一些挑戰品質和工程領導者轉型基本假設的東西：
工程變更推進緩慢的主要原因是涉及人員的情緒反應。不是流程缺陷。不是技術債務。是人。
抵抗悖論的研究背景
查德·傑克森是 Lifecycle Insights 的首席分析師兼 CEO，這是一家專注於工程轉型的獨立研究機構。他的工作處於技術採用、組織行為和工程領導力的交叉點。與廠商贊助的研究不同，傑克森的研究旨在揭示當新流程、新工具和新系統被引入時，工程組織內部真正發生的事情。
抵抗悖論報告來自對303 名工程高管和變革推動者的跨行業調查。這項研究本來不是在尋找抵抗——它意外發現了抵抗。正如傑克森所寫：“這個發現令人驚訝，以至於我們正在為此撰寫一份完整的報告。”
數據揭示了顛覆傳統智慧的障礙分布：
| 障礙類別 | 佔總摩擦的百分比 |
|---|---|
| 情緒反應（恐懼、不安全感、不確定性） | 45% |
| 過渡期間的流程不穩定 | 28% |
| 技術差距、資源限制、其他 | 27% |
減慢工程轉型進度的事情中，幾乎一半都存在於傑克森所說的"人類內心"中——這比任何工作流程或治理模型都難設計。
核心悖論
悖論在於：成功的工程轉型不是避免摩擦——而是駕馭它。
大多數組織都有一個隱含的假設：如果轉型遇到抵抗，那就表示計劃出了問題。因此，解決方案是完善計劃、修復流程、升級工具或更換供應商。但研究表明，成功的轉型面臨的抵抗與失敗的轉型一樣多。差別不在於有沒有摩擦，而在於組織如何應對它。
正如傑克森所說：“轉型的技術論證可以無懈可擊。商業價值可以證明。然而，行動仍然以預期速度的一小部分推進，因為情緒基礎工作沒有先做好。”
這就是悖論：成功的組織不是消除抵抗的組織。它們是預期它、準備它、並在抵抗加劇之前建立支持結構的組織。
MBSE 協作悖論
傑克森在基於模型的系統工程（MBSE）的採用中發現了一個相關的悖論。大多數人認為 MBSE 基本上是關於建模——創建複雜系統的數字表示以減少錯誤並加速開發。技術很精密，價值主張也很明確。
但傑克森發現組織無法成功採用 MBSE 的第一大原因不是技術問題。而是協作。
MBSE 要求幾十年來一直在孤立中工作的工程師突然分享他們的模型、暴露他們的假設、並以令人根本不舒服的方式協調他們的工作。工具要求協作，但文化從未為此而建立。技術創造了共同工作的可能性，但人們抵抗這種可能性，因為它威脅到他們的自主權、他們的專業邊界和他們既定的工作方式。
這就是協作悖論：承諾更好協作的工具被拒絕，恰恰是因為它需要協作。
這對品質管理的影響
對於品質專業人士來說，抵抗悖論不是一個抽象的組織理論。它是日常運營現實。考慮抵抗在常見品質舉措中如何表現：
1. 供應商品質改善計劃
當品質團隊引入新的供應商評分卡、更嚴格的 AQL 標準或更嚴格的 PPAP 要求時，供應商的反應很少是對新要求的理性評估。相反，典型的反應是：
- 害怕失去業務 —— “如果我承認缺陷，他們會找另一個供應商。”
- 對能力的不安全感 —— “我們已經這樣做了 20 年。為什麼他們認為我們需要新流程？”
- 對期望的不確定性 —— “他們到底想要我們做什麼？要求一直在變化。”
技術解決方案——一個更好的評分系統、一個更清晰的規格——無法解決這些情緒障礙。害怕的供應商會隱藏數據。不安全的供應商會抵抗改變。不確定的供應商會表面服從但根本失敗。
在我們管理多個產品類別供應商品質的自身經驗中，這種模式一再重複。技術能力最好但文化開放度最差的供應商，一貫表現不如能力中等但信任度和透明度高的供應商。
2. 內部品質系統全面改革
當公司從過時的品質管理系統遷移到現代數字平台時，抵抗情況驚人地相似：
- 工程師害怕失去既定的工作流程 —— “舊系統能用。為什麼要改變？”
- 檢驗員害怕被自動化取代 —— “如果系統能做我的工作，那我怎麼辦？”
- 經理害怕失去可見性和控制力 —— “如果都在儀表板上，我不會知道發生了什麼。”
28% 的摩擦歸因於流程不穩定是真實的——過渡確實是破壞性的。但 45% 歸因於情緒反應的是主導成本驅動因素，而這正是品質領導者在實施計劃中最常忽略的。
3. 根本原因分析和糾正措施
抵抗悖論也解釋了為什麼根本原因分析如此頻繁地無法產生持久的糾正措施。當品質工程師進行 5-Why 分析或建立魚骨圖時，技術方法是合理的。但如果涉及的人擔心識別根本原因會導致指責、處罰或重組，他們就會積極抵抗調查。
結果是表面的根本原因，指向"操作員錯誤"或"材料變化"，而不是真正需要解決的系統性問題。品質團隊產生了技術上完整的 CAPA 報告，但什麼都沒解決，因為情緒基礎工作——為誠實調查創造心理安全——從未建立。
忽略抵抗的成本
傑克森的研究量化了品質領導者直覺感受到的東西：抵抗是一個成本驅動因素，不是一個軟性問題。
當抵抗沒有被預期和管理時，它會在三個可衡量的方面對轉型徵稅：
| 成本維度 | 影響 |
|---|---|
| 帶寬 | 工程師和品質專業人員花時間管理抵抗，而不是執行轉型 |
| 士氣 | 未解決的抵抗創造了一種有毒的暗流，蔓延到直接舉措之外 |
| 高管注意力 | 領導者被拉入滅火和衝突解決，而不是戰略方向 |
研究表明，在抵抗加劇之前就預期抵抗並圍繞它建立支持結構的組織，能夠更快地實現價值實現，並減少組織損害。這不是關於"軟"。這是關於戰略性有效。
價值-風險誤算
傑克森確定了另一個關鍵的失敗模式：組織如何評估轉型的風險。
大多數投資決策權衡商業價值與干擾風險。但干擾風險幾乎總是以運營術語來框架——時間表延遲、資源成本、計劃連續性。研究揭示的真正干擾風險是人的，不是運營的。
當品質領導者提議實施新的統計過程控制系統時，商業案例專注於缺陷減少、成本節省和週期時間改善。干擾風險評估考慮實施時間表、培訓小時和系統集成複雜性。但兩種評估都沒有考慮每天使用該系統的工程師、角色將改變的檢驗員或監督方法將改變的經理的情緒反應。
這就是價值-風險誤算：組織系統性地低估了干擾風險的人類維度，同時高估了僅通過技術能力吸收它的能力。
品質和工程領導者應該做什麼不同的事情
基於傑克森的發現及其與實際品質管理經驗的一致性，以下是五個可行的建議：
1. 在技術工作之前做好情緒基礎工作
在引入任何新品質流程、檢驗流程或工程工具之前，花時間了解將受影響人員的情緒狀況。他們害怕什麼？什麼讓他們不安全感？他們承擔什麼不確定性？
這不是"有了更好"。它是成功實施的先決條件。
2. 在抵抗加劇之前建立支持結構
傑克森的研究表明，成功的組織在推出轉型之前就建立了支持網絡。這意味著：
- 解決恐懼的培訓計劃，而不僅僅是技術技能
- 可以模範新行為的同儕倡導者
- 允許建設性表達抵抗的反饋渠道
- 展示承諾而不輕視的領導能見度
3. 將抵抗視為數據，而不是挑釁
當人們抵抗品質舉措時，他們正在提供關於舉措缺少什麼的有價值信息。恐懼表明變更沒有被清楚解釋。不安全感表明培訓不足。不確定性表明期望不明確。
每種形式的抵抗都指向實施計劃中的特定差距。傾聽它。
4. 預期摩擦，不要害怕它
抵抗悖論教導我們，摩擦不是失敗的標誌。它是轉型過程的正常部分。目標不是消除摩擦，而是有效地駕馭它。
5. 在重新設計流程之前建立信任
正如研究所指出的：*“建立信任比重新設計任何既定流程需要更長時間。"*這在品質管理中尤其如此，在品質管理中，品質團隊和生產工程師之間、公司和供應商之間、領導層和一線工人之間的信任是每個成功舉措的基礎。
像您在流程設計上投資一樣有意識地在信任建立上投資。它將帶來任何技術優化都無法匹敵的回报。
品質領導者的使命
抵抗悖論最終挑戰品質和工程領導者擴展他們的能力定義。技術卓越是必要的但不夠。世界上最精密的品質管理系統如果必須使用它的人害怕、不安全感或不確定，就會失敗。
傑克森的研究基於 303 名工程高管的數據，傳達了一個明確的信息：品質和工程轉型的未來不屬於那些建立最好技術的人，而屬於那些理解和駕馭決定該技術是否會被有效使用的人類動態的人。
這不是軟技能。它是一種戰略能力。而正是這種能力將僅僅宣佈轉型的組織與真正實現轉型的組織區分開來。
您在品質舉措中遇到了什麼抵抗？您是如何駕馭它的？