Skip to main content
Loading...

Check whether you are ready to roll out

Most rollouts that fail do not fail on the software. They fail because nobody owned what got published and no rule was written down. This names what is missing, and can tell you to wait.

What a rollout needs in place 2 of 10

Someone who owns it

A decision written down

Rarely full-time roles — usually part of existing jobs. Tick only what is true today.

2 of 5 people in place, 0 of 5 decisions written down.

Nearly. The people everything answers to are named.

2 of 5 people in place. A rollout needs all but one of them, or an area of it has nobody keeping it current.

0 of 3 decisions written down. Until they are, everyone can send everything to everyone — which is how people learn to ignore it.

A customer success manager, a product manager and a technical account manager come with the subscription, and setting this up with you is their first job. Not having it yet is a reason to talk, not a reason to wait.

What this arithmetic ignores
  • It asks whether these exist, not whether they are any good. A sponsor who never turns up is a box ticked and a rollout in trouble.
  • None of these is a full-time job. If the answer is no because nobody has the time, the answer is still no.
  • A rollout team comes with the subscription — a customer success manager, a product manager and a technical account manager — and setting this structure up with you is their first job. Not having it yet is a reason to talk, not a reason to wait.
  • Nothing here is about the software. Every one of these would be true of any platform you bought.

You might also want What does one platform return in a year? What does another year of deciding cost?

Missing one of these?

That is the half of a rollout nobody sells you. Tell us which one and we will say how other teams covered it.