The RACI matrix almost got it right but still harbors too much ambiguity. In your team’s formal planning, govern only what is worth documenting outside email, and nothing else. Govern with just Five Verbs: Draft, Review, Revise, Approve, Distribute.

Bundling a group of highly-paid employees into a group labeled a Steering Committee fosters a culture of ambiguity, ego, exclusivity, and high cost. Assign those individuals to maximize speed, quality, inclusivity, and durability.

It’s one thing to identify what a user wants to be able to accomplish. It’s another thing to capture what they consider a chore and want to leave their scope of responsibility.

A script is a simple, raw, unambiguous format to get the sequence of actions on paper, primed for a Future State Process Flow.

Visual representation of the customer journey or employee experience - sequence of actions, primary path, and peripheral paths.

Surely some activities in your organization are important to measure. A scorecard captures the “Metrics That Matter” - Leading and Lagging. Historical, Current, and Target values.

Your colleagues, especially your manager, need to know if you’re bored, buried, or somewhere in between. Share your workload so the team can balance the workload!

Corresponding with the R of ADKAR, a Closure Report is Reinforcement for the new Customer Experience and formal declaration that the project is complete.

The big day! Showtime! Opening Night! Let your stakeholders know that the new experience is ready for them. The Go-Live Announcement fulfills the latter “A” in ADKAR.

At the start of every project, to accomplish the first “A” in ADKAR, notify your stakeholders. An Awareness Blast is a low-maintenance way to let stakeholders know they need to contribute, and they need to help to identify other stakeholders who need to contribute.

“K” - Knowledge - is the heart of ADKAR. Before you dig into detail of actual training material, put to paper all the expectations surrounding your training activities. Often, a Training Approach can apply across projects.

Some common documentation is counterproductive: meeting minutes, a public task list, a RAIL, FAQ, and more. You should know what to avoid, why to avoid them, and what to create instead.