After launch1 min read

What to ask before a software update reaches your customers

Someone tells you the update is ready and it's only a small change. Usually that's fine. But small changes are how a lot of bad days start: a tweak to the checkout stops the confirmation email, or a new price shows on the site but not on the invoice. Here's what any owner can ask.

Was it tried the way a customer would use it?

Ask for more than "it looks right". Someone should have gone through a real order, on a real phone, from start to finish, including the email at the end.

What else could this touch?

The answer shouldn't be "nothing". A good answer names the two or three places worth a look.

Can we go back?

If it goes wrong, how fast can you return to how things were, and what happens to anything customers did in between?

When is it going out?

Pick a quiet time, and avoid the hour before everyone leaves for the weekend. Moving it usually costs nothing.

Who's watching afterwards?

Plenty of problems show up in the first hour, but a nightly job or weekly invoice run won't fail until it next runs. Ask who's watching at both times.

Will customers notice?

If they will, tell them beforehand, and tell your staff before that so they can answer questions.

Have you seen it yourself?

Look at it yourself before it reaches customers. You know your business, and you'll spot a wrong word or an odd step that nobody else would.

You don't need all of these for a spelling fix. You want most of them when a change touches money, bookings or customer details. If you're making the change yourself with an AI tool, ask yourself the same questions.

What should exist?

Tell us what you need, and a person will reply. Talk to us