Our mission is to create a borderless world where the barriers of trade have been removed and the frictions of fulfillment overcome. In that world, a product will be able to seamlessly move from where it is to where it needs to be — no matter how it needs to get there. We achieve this mission by empowering the world’s merchants with an intelligent platform where they can curate and optimize delivery experiences to overcome fulfillment challenges in commerce.
We had a problem
I was using manual “chips” exercises to help stakeholders visualize level of effort for requirements against our available capacity. As you might imagine, this was far from efficient. It entailed a lot of hours that I could have spent on high level planning.
This was compounded by the fact that reports were being emailed out week to week – separately — by department. The result? Stakeholders did not have a consolidated view of our product roadmap. All of our product management activities — from feature scoring to roadmapping — were spread across various Google docs. This made it impossible to know who was working on what and which stage of development we were at.
Aha! as a solution
The Features board with capacity planning bars has been the feature of Aha! that our stakeholders love most. Dropping in cards, seeing capacity fill up in real time, and shuffling cards based on priority has helped expedite decisions. Our Google docs are things of the past; now, we use Aha! notebooks to help stakeholders view product updates via the Web whenever they want. These reports also consolidate our carrier, feature, connector, and even marketing roadmaps in a timeline view. This means that stakeholders don’t have to manually connect dates in order to make decisions.
Most importantly, Aha! provides a framework that gives structure to feature assessment activities. Having them consolidated within one tool is a huge benefit. It offers visibility that we could have only dreamt of in the past.
Life is good
Due to the stakeholder collaboration that Aha! facilitates, engineers are more confident that the features given for development have been thoroughly defined, vetted and prioritized. They have more confidence than ever that what they are building matters for the product, business, and end users.
This is due in large part to the reporting options that Aha! enables. It is very rare to see a tool place such focus on robust reporting. 90% of the reporting views and formats that stakeholders have asked for have been completely possible in Aha! We now have one place where everyone can see ideation engagement levels via the Web-based Ideas portal and the Aha! integration with Slack — our internal comms tool.