Signs it is time to revisit post-launch support

There is no clever trick in this one, just a handful of decisions worth making deliberately. A few signals that post-launch support is due some attention.

Strategy work is mostly deciding what not to do, and writing it down so it stays decided. Write the reasoning down alongside the decision, because the reasoning is what changes first.

The signals

• Nobody can say when it was last reviewed
• The answer depends on who you ask
• Launch is the beginning of the maintenance period
• Decide who owns fixes before you need them

The practical version

Budget for it or it comes out of goodwill. Small and consistent beats large and occasional here. If it only works because one person remembers to do something, it does not work yet.

How to tell if yours is fine

The projects that go badly are rarely the ones with the hardest technical problems. Three things worth confirming about post-launch support before you move on:

• Someone can say what the current setup is without going to look
• Decide who owns fixes before you need them — and you know whether that is true here
• There is a way to tell whether the last change to this helped

Worth checking on your own setup before it becomes someone else's problem to fix.