👷♂️📈 Rebuilding Our Reporting Feature: Launch
This story follows on from: https://medium.com/bad-practice/rebuilding-our-reporting-feature-the-design-sprint-ebdfc482bbee where we defined the JTBD and iterated on a couple of concepts based on feedback.
Here’s what we came up with:
There were a few differences between the concept and the implementation:
- Colour-coded attribute selection: We needed a way to see the difference between the attributes on the chart, so the attribute selection would act as the legend
- Uniform chart: The chart would be bar, rather than line. This would allow for easier comparison over time
- Introduction of filter bar: Rather than having a card per date per group, the view would show only one date and the filter bar would allow selection of the time period and unit of time. The options would be to show 1 year, month or week; with the data broken down to show 12 months, 4 weeks and 7 days.
Once we had pushed this feature through staging to production, we reconnected with the users who had given us feedback by writing personal emails. We wanted to talk about the feature from the context of the previous conversations so that they remember what they said and what we did based on that.
For other users, we wrote an email message via Intercom that showed the vision that the feature hopes to fulfil; seeing the impact of their hard work!
To see the impact of our hard work, we needed to track how many people opened our Intercom email (how many people care) and who used the feature and which part. Fortunately, Intercom allows us to do this via event tracking.
The main environment we expected this feature to be used was offline and off-the-system (in meetings and emailed). So we needed to connect with the managers who should interact with this feature at the appropriate time.
Next, we would need to figure out whether this feature should be killed or kept.
