I Started Writing the Support Reply Before I Wrote the Fix

by•

I had a habit of fixing the bug and then writing the reply. The reply was always short. The bug was fixed, what else was there to say.

Then I started writing the reply first. Explaining what broke, why it broke, what I was doing about it, and when they would know it was fixed.

The replies got longer. The bugs got fixed faster. Writing the explanation forced me to understand the problem before I tried to solve it. The half-formed ideas did not survive the act of putting them into words for someone else.

What would change if you had to explain the thing before you fixed it?

2 views

Add a comment

Replies

Best

One more thing the explanation can turn into: the product's own copy. We had a ticket where Google sign in failed on one iPhone. Explaining it meant finding the cause: the phone's time zone was wrong, so its idea of UTC ran nine hours ahead and the sign in library rejected a fresh token as expired. The app now recognises that exact error and shows its own message asking to set date and time automatically, instead of an unknown error. The same explanation sits in our project notes under the ticket number, so whoever sees that error code next starts from it.