Beatnik,
a bug reporting tool

As usual I wanted to get a better understanding of the problem and it’s roots. So I’ve spoken to both sides of the story - business devs and engineers. A lot of frustration came out during these conversations.
‍
Engineers were frustrated because their workflow was interrupted with irrelevant bugs. Issues out of their responsibility scope and insignificant problems were piling up on them.  Also during the night hours (different timezones, remember?).
Business devs were frustrated, because of not knowing what is going to happen, who will resolve the problem and will it even resolved.

We had Slack channels, Jira and Asana but all these things didn't seem to work for us. The information noise was constant, but it didn't bring anything. Engineers were distracted and frustrated, business devs were lost and frustrated.

After all the insights I received we came up with a simple solution. For the MVP we decided to develop:
- List of raised issues, color coded for faster visual processing
- Smart process of issue reporting, where we gather data so we can automatically assign teams and individuals responsible
- Automatic evaluation of a problem based on the data collected
- Integration with Slack. A channel will be created where reporter and individuals responsible for resolving will be invited.

There are still many bugs and probably there will as many in the future. However, with this project we created a unified place and process for storing and reporting issues. Slack channels became way calmer.

In the next iterations of the project we’ll include user roles such as reporter and resolver, introduce status updates. For reporting issues we plan to add an initial step, where user can see if someone has reported this bug before.