The Go-Live Date Was Never the Point
Every transformation program I’ve sat inside — as implementer, rescuer, or the second set of eyes brought in to see what the sponsor can’t — has the same reward list on the wall, even when nobody writes it down. The on-time go-live. The cost savings in the board pack. The dashboard that goes green in Q3. The recognition that comes when you’re the executive who finally got the ERP program across the line. The next role that opens up because you delivered.
None of that is dishonest. It’s what the mind fixes on. But it ignores something structural: those rewards are not something you produce directly. They are the downstream result of character, of work, and — however uncomfortable this is to admit in a board pack — of luck.
The work is what’s actually inside your circle of influence: the discipline to hold a steering committee to honest reporting instead of comfortable reporting. The consistency to keep testing data quality when everyone else wants to call it done. The integrity to escalate a red flag before it becomes unrecoverable. The relationships with the vendor’s delivery team that let you get a straight answer instead of a status-report answer.
Luck is the part nobody puts in the business case. Whether the vendor’s best consultant stays on your account or gets pulled onto a bigger client. Whether the finance system upgrade lands before or after a machinery-of-government change. Whether the one person on your team who actually understands the legacy data doesn’t resign in month four. I’ve watched two near-identical local government ERP programs run the same rigor, the same governance discipline, the same sponsor attention — and land different outcomes, because one kept its key vendor resource and the other didn’t. That wasn’t a failure of work. That was luck declining to cooperate.
The correlation between the work and the reward is real, but it’s uneven. Not guaranteed, not linear, not something you shortcut by wanting the outcome harder.
Here’s where most executives lose the thread. When the mind stays fixed on the reward — the go-live date, the number in the board pack, the promotion — it starts protecting the appearance of that reward instead of doing the work that might produce it. A status report gets softened so the date doesn’t slip on paper. A known data issue gets deferred instead of escalated, because surfacing it now threatens the milestone. The steering committee stops asking hard questions because hard questions threaten the story everyone has already told upward. Most ERP programs don’t fail suddenly — they drift quietly while every report stays green. This is the mechanism underneath that drift. The reward became the point, and the work — the only thing actually inside anyone’s control — got quietly abandoned to protect it.
The alternative isn’t complicated, even if it’s uncomfortable. Do the work. Hold the discipline. Tell the truth about status even when it costs you the appearance of being on track. Build the relationships and the integrity that are actually yours to build. Let luck do whatever luck is going to do with the rest.
If you’re sponsoring a transformation program right now, it’s worth asking yourself plainly: when you look at your own attention this week, was it on the work, or was it on the reward? Most of us already know the answer. We just don’t like sitting with it.
