Yesterday I was talking to an entrepreneur about their recent product launch. The application looks solid and has a minimum respectable feature set (one level above a minimum viable product). Only, he thought the product was sufficient for now and wouldn’t need as much engineering attention for a month or two.
A new product never survives contact with customers. Never. Customers always find bugs, problems, inconsistencies, and issues. In fact, it never stops, and it’s a good thing.
Here are a few thoughts on customers finding bugs:
- Acknowledge the bug when found and graciously apologize to the customer
- Allocate some amount of engineering time on a recurring basis to address bugs
- Incorporate exception handling software that automatically registers product errors in a third-party service that notifies the engineering team (e.g. Airbrake)
- Add automated tests (e.g. unit tests, integration tests, synthetic browser tests, etc.) as new issues arise to ensure core elements of the application are always working
Customers finding bugs is a normal part of the software experience. Develop a process and best practices for handling them when they occur and work hard to make customers happy.
What else? What are some other thoughts on customers finding bugs?
Leave a reply to James Cancel reply