2020
What is it?
Hetchr was a centralized, bi-directional dashboard designed for developers, aiming to reduce the number of tools a developer uses alongside coding ones. By integrating popular tool APIs, we offered a dashboard that simplified actions and provided a comprehensive overview with ease, significantly reducing daily back-and-forth.
Problem to be solved
In leading the UX approach for the development of Hetchr, I initiated a deep dive into the daily challenges faced by developers. Through extensive user research, including surveys and interviews, I uncovered a critical need for a tool that consolidates various development tools into one efficient dashboard.
Unique Experience: ATOMs
We have created a variation on widgets/micro-apps called ATOMs (short for Aggregated Tech Operations Module). ATOMs were bi-directional micro-apps that can both read and write engineering data. With these building blocks, we consolidate the features most used by software engineering teams into a centralized dashboard. Teams simply connected their existing tools and selected the ATOMs to interact with.
Encouraging feedback
Few months after launch we reeached encouraging numbers with almost 500 active users, mainly connecting their git and kanban tools such as Jira and Trello. The problem we had and why we were forced to pivot to Ninefive was API bi-directional connectors. We would eventually need to sustain technically those connectors while expanding our catalog of conected tools and this was too much workload for our team at this time. This is why we decided to picot, byt we understood the need for centralization.
