Successfully reported this slideshow.
Your SlideShare is downloading. ×

Designing Mature Products

Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad

Check these out next

1 of 29 Ad

Designing Mature Products

Download to read offline

Changing even the smallest of design features on a highly technical mature product that has millions of users can be a huge challenge. In this talk, Janina will share her journey of changing a simple UI component in Codewise's navigation bar, the challenges she encountered and lessons learned for future 'simple' design changes. She will talk about:
- The maturity of Codewise, highlighting its design & technical legacy
- The changes she proposed to the UI design
- The challenges faced, and
- Lessons learned throughout her journey

Changing even the smallest of design features on a highly technical mature product that has millions of users can be a huge challenge. In this talk, Janina will share her journey of changing a simple UI component in Codewise's navigation bar, the challenges she encountered and lessons learned for future 'simple' design changes. She will talk about:
- The maturity of Codewise, highlighting its design & technical legacy
- The changes she proposed to the UI design
- The challenges faced, and
- Lessons learned throughout her journey

Advertisement
Advertisement

More Related Content

Similar to Designing Mature Products (20)

More from UXDXConf (20)

Advertisement

Recently uploaded (20)

Designing Mature Products

  1. 1. DESIGNING A MATURE PRODUCT ...and the importance of finding UX advocates.
  2. 2. An analytical SaaS solution that allows for tracking, optimizing & automating advertising campaigns.
  3. 3. Voluum’s history ● 8 years (2013 - now) ● different design approaches ● design debt Source: pexels.com
  4. 4. Voluum is a tool centered around data.
  5. 5. Screen height: 640px Everything above the table: 264px (41%) Report table: 368px (57%)
  6. 6. Screen height: 640px Everything above the table: 310px (48%) Report table: 330px (51%)
  7. 7. Redesign? ● Not enough of a priority ● Developer resources were always spread rather thin Source: pexels.com
  8. 8. Redesign? ● Not enough of a priority ● Development resources were always spread rather thin “Users are not complaining that much, they are using the product so maybe it’s not bad enough to be worth fixing? “ Source: pexels.com
  9. 9. Product Designer that became a Product Manager Source: flaticon.com
  10. 10. A green light! Source: pexels.com
  11. 11. What data did I look for? ● How often users click on each report button ● How often users click on each button in the navigation above the report table ● The most popular screen resolutions Source: pexels.com
  12. 12. Redesign: report buttons
  13. 13. Redesign: navigation buttons
  14. 14. Redesign
  15. 15. Reports buttons + navigation buttons: 214px (33%) Report table: 420px (67%) Screen height: 640px
  16. 16. No more screen jumping!
  17. 17. Slack community called Voluum Lab
  18. 18. Almost no users complained about the change! Learnings: The biggest surprise? Source: pexels.com
  19. 19. Learnings: Find UX advocates! Product Manager Front-end Developer Source: flaticon.com
  20. 20. Learnings: Find UX advocates! PM FE “Every day is an opportunity to invite your non-UX colleagues into the world of UX. (...) Invite them into the conversation and the community, and treat them as partners in the ongoing project of making your products as user-friendly as possible.”
  21. 21. Summary Source: pexels.com
  22. 22. Summary ● Find UX advocates Source: pexels.com
  23. 23. Summary ● Find UX advocates ● Get the necessary data (when available) Source: pexels.com
  24. 24. Summary ● Find UX advocates ● Get the necessary data (when available) ● Trust your instincts! Source: pexels.com
  25. 25. Thank you!

×