change-management

A project manager's authority rests on being believed, and generated artefacts can erode that quickly. This lesson covers disclosure with stakeholders and teams, how the tooling interacts with different methodologies, measuring whether it helped when your own metrics are the ones in question, and the failure modes specific to this function.

A redesign has to be introduced into a process that is still running and still has customers. This lesson covers sequencing, running the old and new paths together, the counterweight metrics that catch a hollow win, the failure modes that end these efforts, and how to know when not to redesign at all.

When one step becomes cheap, the optimal shape of the whole process changes. This lesson covers the six moves that follow, why the review stage almost always needs relocating, what business process reengineering actually taught, and the honest state of the evidence on how often these efforts succeed.

Mandated adoption produces compliance behaviour and licence-seat metrics that measure nothing. This lesson covers why mandates fail, what resistance is actually telling you, measuring adoption in a way that survives scrutiny, the equity problems that appear inside a team, and how to run the change without losing the people carrying it.

Most CRM projects fail, and almost never because of the software. This lesson covers the real reasons: poor user adoption, bad data, and weak change management, why the people-and-process problem dominates, how to design a CRM people actually use, and how CRM skill translates into a career.

The model is the least of your problems. This lesson examines how to structure the AI function (centralised, federated, hub-and-spoke), make defensible build-vs-buy decisions, design for actual adoption, and understand why change management — not the model — is the dominant failure mode in enterprise AI programs.