The Go-Live Surprise: When “Go-Live” Isn’t Actually “Go-Live”
Over the course of the past year, I’ve run into an interesting and somewhat amusing—though admittedly frustrating—situation that I feel is worth sharing.
While working with another partner company, we had an ongoing discussion about the go-live date for a project. After months of planning and conversations, that day came and went, and I was left scratching my head. It turns out that their version of “go-live” was something I’d never encountered before: an internal “go-live live” moment. For them, go-live meant it was live within their system, but not necessarily for the client or the public. I was stunned.
We had thought we were on the same page the whole time, but this additional step they had internally wasn’t clear to me at all. Suddenly, I realized that “go-live” could mean entirely different things depending on who you’re talking to, and it wasn’t just me who had misunderstood the meaning.
A Similar Situation, Same Year: The Development Team’s “Go-Live”
Fast forward a few months, and I’m working with my own development team, preparing for another “go-live” date. The day arrives, and I’m finally handed the credentials, URL, and all the access I need. I’m ready to go live! But… no, not quite. It turns out that despite being handed everything, the site wasn’t truly live just yet. It was “live,” but not “live live.”
Wait a minute. Did the world just decide to add a “live” in front of “go-live” for fun? Twice in one year, with two different teams, I ran into this situation. And that’s when it hit me: Was I the only one who didn’t get the memo? This whole idea of a “live” and “live live” moment seems to have become the new standard, and honestly, I’m a bit behind the curve.
Clarifying Expectations is a Must
I have to admit, this whole experience was a wake-up call for me. It seems like the idea of go-live has changed, and I now have to ask—do I need to clarify this every time? With every team I work with? The short answer: probably yes.
In fact, I’m beginning to think that any project I start from here on out needs a very specific discussion around what “go-live” actually means for the client, the team, and everyone involved. Setting clear expectations about when the project is truly live and when it’s “live live” can save a lot of confusion and avoid surprises.