The business case for change
Nobody approves a platform because it is modern. They approve it because someone put a number in front of them they could defend. Here is how to build that number.
Most internal cases for modernization are not rejected because the idea is wrong. They are rejected because they are unfalsifiable. A case built on efficiency and future readiness gives a committee nothing to test, so it competes badly against a smaller proposal whose author did the arithmetic.
This guide walks through separating fires from priorities, the five numbers that carry a case, how to present three options honestly, and how to write the document for the room it will actually be read in. It also covers how the case will be attacked and what the answers are.
There are no Vero figures in it. Every number is one you generate from your own operation, which is the only kind that survives scrutiny.
- An impact against effort method for choosing what to solve
- The five numbers, and which four form your defensible floor
- How to present the status quo fairly, and why that matters
- The three most common attacks on a case, and the answers
The download starts straight away. We will also send you the occasional thing worth reading, and you can unsubscribe from any email.
Thanks. Your download is ready.
Bring us the workflow that hurts most
Thirty minutes, one workflow, no slides. We will tell you where the time is going and whether it is worth changing.
' d='M11.04 19.32Q12 21.51 12 24q0-2.49.93-4.68.96-2.19 2.58-3.81t3.81-2.55Q21.51 12 24 12q-2.49 0-4.68-.93a12.3 12.3 0 0 1-3.81-2.58 12.3 12.3 0 0 1-2.58-3.81Q12 2.49 12 0q0 2.49-.96 4.68-.93 2.19-2.55 3.81a12.3 12.3 0 0 1-3.81 2.58Q2.49 12 0 12q2.49 0 4.68.96 2.19.93 3.81 2.55t2.55 3.81'/%3E%3C/svg%3E){kind=small}
.svg)