Bonusly is a peer-to-peer recognition and rewards platform. Users can recognize fellow teammates by publicly recognizing them in a social feed with a message that also has an attributed value.
Getting insights into how your team, department, and company interacts can be difficult or impossible.
For the MVP we decided to focus on teams specifically.
- Increase the average amount of bonuses given to unique receivers within teams.
- Increase the number of daily impressions of combined analytics views.
Roles and responsibilities
For this project, I played the role of Researcher and Lead Designer working with 3 Engineers and a Product Manager.
Kick-off with Project Partners
For every project I work on, I like to loop in all the stakeholders and Engineers associated with the project as early as possible. Defining who these members are is crucial to a project’s success.
The research for this project included a few different steps, including:
We sent out a TypeForm survey to 2,000 of our users. The survey was ~10 questions, mostly being multiple-choice Likert scale questions and a single freeform feedback input. The response rate was decent enough to pull a few gems I didn’t think about from the project beginning stages.
Inline CTA Surveying
A tactic that has proven to be very successful is asking feedback via a CTA within the view we are thinking of recreating or altering. I went in and added this survey CTA to all of our existing Analytics views. This method is immensely valuable because we engage the user who has the proper context to provide optimal feedback.
Working with our Director of Customer Success, we targeted a few ideal customers to interview. In these calls, we discussed the current Analytics platform and how they would like to see this evolve. One customer within this process had done quite a bit of excellent research in her own time before the meeting, which was immensely helpful.
In our tool-kit, we had several analytics platforms to review including (but not limited to) Google Analytics and Fullstory. Reviewing the data allowed us to get a grasp of what types of users and devices were interacting with our current implementation.
Design & Feedback
I started off with some quick iPad sketches during brainstorming. Then working in a low-fidelity mockup form, I started to layout the specific of the UI for this new view, which would be the home of the Analytics Dashboard. While reaching milestones, I would check in with stakeholders within our company as well as fresh-eyed individuals to gather feedback and make improvements.
With time and more confidence, I switched to high-fidelity mockups to get a better sense of how this view would fit within the app. Making more iterations and doing more feedback sessions this stage would conclude with a final stakeholder presentation.
To better support the Engineering team with mockup to code conversion, I made this prototype. Spending a few extra minutes creating this allows me to show the additional interactions that should be present within the live version.
The engineering handoff went off with ease. Including participants who are working on the project at an early stage helps to promote buy-in and increases the lines of communication. During this meeting, we walk through the high-fidelity mockups and discuss what details are to be included within the initial MVP.
Doing a regular check-in meeting is vital to understand any problems that arise during the build-out.
After ~2 months, we launched an initial MVP to our customers. We measured an average increase in unique receivers of bonuses given within teams by approximately 25%. We also noticed an uptick in the number of daily impressions within our analytics views by 45%.
This initial release is just the beginning stages for our Analytics platform setting up the foundation for plenty of testing and user interviews to help inform a more refined experience for the future.