{"id":216,"date":"2018-02-27T03:56:02","date_gmt":"2018-02-27T03:56:02","guid":{"rendered":"https:\/\/portfolio.cherylplatz.com\/?p=216"},"modified":"2021-05-18T23:00:30","modified_gmt":"2021-05-18T23:00:30","slug":"azure-marketplace-gallery-filter","status":"publish","type":"post","link":"https:\/\/portfolio.cherylplatz.com\/?p=216","title":{"rendered":"Azure Marketplace Gallery Filter"},"content":{"rendered":"

When we launched the new Azure Marketplace in January of 2017, we initially adopted the category control from AppSource.com, both for consistency and expediency on our tight timeline.<\/p>\n

After launch, however, customer feedback via verbatims and quantitative data began to suggest that our customers had a problem with wayfinding. The issue largely stemmed from the difference in information architecture between the sites. AppSource categories correspond to products and were more rigidly hierarchical, while Azure Marketplace categories had overlap and a less rigid hierarchy. <\/p>\n

I proposed to the team that we begin an exploration of alternate filtering models, and the team agreed. However, the general desire was to explore broadly in hopes of finding a single control pattern that worked for both AppSource and Azure Marketplace, since both shared the same root code. Because the usability of filtering controls is heavily influenced by factors like response time, page animation, and usefulness of results, we felt it important to prototype heavily for this project.<\/p>\n

MY ROLE: Solo designer.
\nTEAM: 1 design prototyper, 1 researcher, and 2 product managers.<\/p>\n

Problem Statement<\/h2>\n