BEST BUY DEVELOPER PORTAL
Best Buy's developer portal hadn’t been updating in over five years, and Best Buy had a renewed interest in building relationships with potential technical partners.
Needs-Finding
After stakeholder interviews with both internal user of the API, external Affiliate partners, and internal portal curators, we developed three audiences. Task-Oriented Developers, Indie Developers, and Business Thinkers. We discovered that these audiences have some overlap in how they would use the site.
Personas
We broke down the motivation of each audience:
The Task Dev uses the site for it's API documentation to help with the project that have been assigned, usually by the Business Thinker.
The Business Thinker uses the site to decide on Best Buy as a partner. They delegate the development to the Task Dev.
The Indie Dev uses the API documentation, and use the site to inspire new product ideas and confidence in Best Buy.
Indie Devs were using the site to the fullest, and therefore their goals and needs had some overlap with the other main user groups. We decided to focus the redesign and content strategy on the Indie Dev persona, which gave our work a clear focus.
Design
We advised Best Buy and gathered feedback from the original stakeholders throughout the redesign. Deliverables I created included content strategy documentation, live clickable prototypes, and detailed annotated wireframes. The final product showcases Best Buy API's capabilities with in-depth documentation and highlights of apps and services that already connect to Best Buy.