Skip to content

Enterprise CM

Every failure adds a signature

Every failure adds a signature

This article is part of the How Do YOU CM2? blog series in collaboration with the Institute for Process Excellence (IpX). Although I receive compensation for writing this series, I stand behind its content. I will continue to create and publish high-quality articles that I can fully endorse. Enjoy this new series, and please share your thoughts!  In my article on Conway’s Law, I describe the change process as the place where the right… Read More »Every failure adds a signature

Can Configuration Management Defeat Conway's Law?

Can Configuration Management Beat Conway’s Law?

This article discusses the challenges organizations face due to siloed structures, as highlighted by Conway’s Law. It emphasizes the importance of a change process in fostering cross-functional collaboration, enabling better communication between departments. The author advocates for configuration management as a means to effectively manage change and break down silos, ultimately enhancing organizational efficiency.

The Question Your Configuration Management System Can't Answer!

The Question Your Configuration Management System Can’t Answer!

The article examines the concept of Product Memory within the context of configuration management (CM), highlighting the importance of preserving the reasoning behind engineering decisions. It emphasizes that while CM effectively manages the “what” of product data, it often overlooks the critical “why.” This gap can lead to significant risks, particularly in complex systems. The integration of AI could assist in retrieving and recording this reasoning, reinforcing the value of… Read More »The Question Your Configuration Management System Can’t Answer!

Configuration errors don't age out. They compound.

Configuration errors don’t age out. They compound.

The article discusses the concept of configuration debt in product development, highlighting how initial errors in product variant assessments can lead to compounded issues over time. Unlike technical debt, configuration debt manifests in hidden warranty claims and field failures, stemming from unaddressed applicability confirmations that impact subsequent engineering decisions.

Applicability Before Effectivity

Whether Before When / Applicability Before Effectivity

The article discusses the importance of distinguishing between applicability and effectivity in change management. It highlights how confusion arises when both concepts are tackled simultaneously, leading to unresolved issues during meetings. The author advocates for a structured process that separates scope confirmation from effectivity assignment, enhancing productivity and decision-making in organizations.

Without Governed Baselines, AI Compares Opinions. With CM2, AI Compares Records.

Without Governed Baselines, AI Compares Opinions. With CM2, AI Compares Records.

The article discusses the challenges in reconciling discrepancies between the as-designed, as-built, and as-maintained baselines in engineering and manufacturing. It highlights how AI can systematically identify these gaps, enabling better tracking and traceability, while emphasizing the human role in interpreting these discrepancies to ensure effective configurations and risk management.

How CM2 Protects Organizations From Decision Atrophy

CM+AI: How CM2 Protects Organizations From Decision Atrophy.

This article discusses the importance of human accountability in AI-assisted configuration management, emphasizing that governance failures, rather than technical issues, led to AI’s biggest failures in 2025. It highlights the necessity for clear ownership in processes and warns against over-relying on AI, which cannot replace human judgment, responsibility, and engagement in organizational culture.

When software velocity breaks your framework

When Software Velocity Breaks Your Framework

The article emphasizes the need for organizations to reassess their configuration management frameworks in light of rapid software deployment. It suggests that a granular approach, distinguishing between low-risk and high-risk changes, is essential. By implementing tiered governance, companies can maintain both speed and control, enhancing overall software delivery efficiency.

Why CM2 Separates Assessment, Decision, and Implementation

Why CM2 Separates Assessment, Decision, and Implementation

This article discusses the importance of separating change governance functions within organizations to improve project outcomes. It introduces the Enterprise Change Assessment, Change Review Board, and Change Implementation Board as distinct roles that clarify assessment, decision-making, and implementation, addressing common issues like budget overruns and unclear responsibilities in project management.

How three industries handle the same CM problem differently

How Three Industries Handle the Same CM Problem Differently

This article compares change control processes across aerospace, automotive, and medical device industries, highlighting their distinct approaches shaped by different failure modes. It emphasizes the need for cross-industry learning to adapt traditional frameworks to modern challenges, particularly in handling continuous software updates. A unified CM2 framework is proposed for enhanced governance.