MENU

[Pomello] Web app redesign

6785
0

Overview


With the use of surveys and analytics, Pomello helps companies quantify and understand their culture so they can have happy employees and hire the right candidates. The goal of this project was to improve the overall user experience of the web app. The web app is where users distribute surveys, manage candidate and employee data, and digest analytics that help them evaluate candidates and understand culture, performance, and employee life-cycles.



Problem


Information architecture! Content was not structured in an organized matter which created a poor user experience. There were too many navigational choices, similar labels for different things, and relevant content was found in different parts of the application. This was the old sitemap:



The overall user experience was not intuitive and created a learning curve for the web app... I had to learn where different views were and how to do certain tasks because everything was scattered in different places. Here's a snippet:








Solution


The web app needed a major improvement in the information architecture because better organization with fewer choices and redundancies was key.

  • Dashboard: where users first land to see a high-level overview of relevant culture analytics.

  • Trends & Insights: where the detailed analytics can be viewed via data visualization.

  • Survey List: where surveys can be scheduled, viewed, and managed.

  • People List: where people data can be created, viewed, and managed.







Design Process


Who are we designing for?

Since we were a very small team, it was important that we initially worked together so I could gather the team's product expertise and the feedback they get from our customers/prospects. In the first design workshop, we worked with a design consultant to help the team create user personas based off of our existing customers and prospects. This helped us identify and prioritize pain points and user flows, and ultimately come up with goals for the different types of users:

  • Administrators: provide a clear flow to send surveys and a simple system to manage candidate and employee data

  • Executives & Managers: offer data visualization to illustrate organizational/team culture and a way to understand how it impacts employee engagement and performance

  • Recruiters: provide analytics to evaluate candidates for roles across the company and make better decisions on a faster timeline


Wireframes

These were some initial low fidelity wireframes I created based off of the final concept.





User Testing

I created a clickable prototype via InVision with these lo-fi wireframes to test different task flows with users. Some flows we focused on were "how to create and send a survey", "how to search for a candidate", and "how to add a new employee".

Together, the COO and I put the prototype in front of existing customers and users to examine their behavior and gather user feedback. Through multiple sessions, we learned what worked and what didn't. I then went through several design iterations and additional rounds of user testing before I had something that was ready for development.

From Design to Production

The first release had one major restriction: no new features (except simple ones) and keep all existing functionality. This limited the overall list of UX improvements because the updated design was based on a lot of new features.


Outcomes

There was definitely more to improve on, but this was just the beginning. With this big UX update, it definitely helped in different areas of the company.

  • Product/Design/Engineering: An improved information architecture meant new features could easily be incorporated into the new layout. This also meant the product could scale because the challenge of figuring out where something should live was eliminated.
  • Customer Success: The experience was more intuitive so there were less support tickets asking for how certain tasks can be done. Users were also please with the new UI.
  • Sales: Product demos took less time because the team didn't have to spend time explaining how certain features worked and how certain tasks could be accomplished.

Note: Pomello eventually got acquired and I don't think this would have happened if this UX redesign project did not happen.

 

Learnings

The process of getting from Point A to Point B was neither straightforward nor easy. There was a lot of back and forth, a lot of feedback, and a lot of iterations.

Key learnings:

  • Team Goals: It's important to be aligned about project goals and desired outcomes so everyone is on the same page and there is no back and forth - this saves time!
  • User Experience: If you learned how to use something, that doesn't necessarily mean it's the best user experience. You just got used to it and there should always room for improvement.
  • Product/Engineering: Large projects are harder to control because timeline and goals could become moving targets. Scaling back with smaller scopes means incremental changes that are easier to control..
  • Information Architecture: This is super important because this allows a product to scale with new features.