Choosing which process to structure next is a balance of three things: how much pain it causes, how feasible it is, and whether it shares data with what you have already built. Why the obvious choice is often wrong The most broken process is frequently the hardest to fix first.
To sustain a process after launch, someone has to keep watching it. Processes do not decay suddenly; they drift, and drift is invisible unless somebody is looking. How decay begins The signs are small and individually unremarkable. * A field left blank more often than before * A phase passed through without
To manage expectations with leadership, be specific about timing. Most disappointment in operations projects comes from a sequence that was never stated, not from a result that was never achieved. What causes the gap Nobody promises the wrong thing deliberately. * A demo suggesting everything is available immediately * No distinction between
To handle a failed rollout, establish what actually happened before deciding what to do. The three possible causes — wrong process, wrong build, wrong timing — lead to different responses. The three causes They look similar from the outside and require opposite responses. * Wrong process — the design did not match how the
To build internal champions, find the people whose opinion others already check, and make sure the system works well for their specific case first. Why champions matter more than mandates Adoption follows social proof more reliably than instruction. * A mandate produces compliance, not use * Colleagues trust a peer's
To report operational results to leadership, present the same measurements before and after. A result described rather than measured is a result that will be questioned. Why results get discounted Leadership has heard improvement claimed before. * Percentages with no stated source * Comparisons against a baseline nobody captured * Improvement claimed during
To keep momentum after the first process, the second one has to start before the first stops feeling new. Implementations usually stall not from failure but from the absence of a next step. Why momentum is lost The first success removes the urgency that created it. * The original pain solved,
To handle feedback during a rollout, separate three kinds: things that are broken, things that are harder than before, and things people would prefer differently. Each deserves a different response. Why feedback becomes noise Everything arrives through the same channel with the same urgency. * Preferences presented as blockers * Real blockers
To choose who should be in your pilot, pick people whose experience will generalize. A pilot run entirely by enthusiasts tells you how enthusiasts behave. Selection mistakes that mislead Each produces a result that does not survive contact with the wider team. * Only volunteers, who were going to adopt anything
To communicate a process change effectively, lead with what the reader has to do differently. Most announcements lead with context nobody needs and bury the instruction. Why announcements get ignored They are written from the perspective of the person making the change. * Opening with background rather than with the action
Handling someone bypassing the new process starts with a question most rollouts skip: what does the old way still do better? The answer is often specific and fixable. Why the assumption of resistance is usually wrong Bypassing takes effort. People do it for a reason. * The new process is slower
To run training people retain, reduce how much of it is needed. Most training on internal systems exists to compensate for interfaces showing people more than their job requires. Why sessions do not stick They are delivered once, in advance, covering things people will not use for weeks. * A tour