Skip to content

newsletter

Turn on Change Control.

When Should Change Control Begin in New Product Development/Introductions?

The article discusses the critical timing of change control in new product introductions, emphasizing its strategic importance. It argues that initiating change control early within the product lifecycle prevents costly rework and configuration debt. By fostering accountability and communication from the start, organizations can enhance innovation, collaboration, and adaptability.

How Do YOU CM2?

How Do YOU CM2? – Part 3

In case you missed them, you can find the following How do YOU CM2? posts in the 46th edition of the Future of CM newsletter:

1️⃣ What Works Better: One Change Process or Many?
🔀 Is Your Data Model Truly Change-Proof?
🧠 Is Your Organization Truly Model-Based or Does It Still Rely on Tribal Knowledge?

parts don't have revisions

Why Parts Don’t Have Revisions (Only Datasets Do)

This article emphasizes that parts do not have revisions; rather, datasets do. It discusses the confusion and inefficiency created by treating part revisions as part of the part number. Shifting focus to dataset revisions enhances clarity, reduces errors, and streamlines processes within organizations, driving down costs and improving quality in product development.

How Do YOU CM2?

How Do YOU CM2? – Part 2

In case you missed them, you can find the following How do YOU CM2? posts in the 44th edition of the Future of CM newsletter:

🚫 Stop Calling Product Changes: “Engineering Changes”!
🤫Impact Analysis: The Secret Ingredient No One Wants To Do!
🚀CM2 Baseline: how to make Impact Analysis easy!

Fragmented Change Management leads to misalignment.

The #1 Constraint on Innovation Isn’t Technology, It’s Fragmented Change Management.

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!  Change is the heartbeat of innovation. Yet, in many enterprises, change is still treated as a reactive… Read More »The #1 Constraint on Innovation Isn’t Technology, It’s Fragmented Change Management.

How Do YOU CM2?

How Do YOU CM2?

In case you missed them, you can find the following How do YOU CM2? posts in the 42nd edition of the Future of CM newsletter:

📄 CM2 is not just about documentation!
⚙️ Configuration Management is not only for Engineers!
🪄 The Magic of a Closed-Loop Change Process

Open Data Platform with connected applications and agentic AI

How the CM Baseline and Agentic AI enables the future of Enterprise applications.

Rob Ferrone’s and Oleg Shilovitsky’s LinkedIn bromance 😉 has resulted in an interesting post by Oleg: How to Build PLM Applications We Love Using AI. His premise (my interpretation) is to build Minimum Loveable PLM applications as small applications supported by AI that fulfill a specific purpose using data from a shared data platform. No MVPs, but MLPs! Around the same time, Michael Finocchario published The Agentic AI Revolution: Reimagining PLM as… Read More »How the CM Baseline and Agentic AI enables the future of Enterprise applications.

Configuration Management is… Part 2

This months newsletter is a collection of posts from the Configuration Management is… series I have posted on LinkedIn. These posts are not intended to limit the scope of Configuration Management, but to create awareness of the breadth of CM. Configuration Management is… #Baselines! Let’s talk about Baselines. Imagine building a house without a blueprint. Each contractor works from their own notes, making changes as they see fit. The result? A… Read More »Configuration Management is… Part 2

Collaborative workspace

Managing Change Successfully in a Collaborative Workspace

The article critiques traditional change management methods, emphasizing the advantages of collaborative workspaces over classic file check-in/check-out systems. It discusses challenges such as data consistency, real-time collaboration, and workflow traceability while advocating for flexible data models and robust integration. Successful implementation requires a supportive mindset and proper tools.