Problem Statement
After conducting 1:1 meetings with key stakeholders and performing preliminary research, I refined the problem statement and reframed it using the extended Jobs to Be Done framework:
Goals
Solution
After several round of iterations and testing, we finalized the design for MVP of new authorization experience. Following is the before and after comparison:
Before
After
A contextual nudge in the existing authorization tab directs users to the new, streamlined authorization experience.
Users no longer need to select an authorization type manually; automatic mapping and assistive text make it easy to find and add credentials.
Upon a successful authorization (200OK), users can save credentials as variables for future requests, eliminating the need to re-enter information.
Impact
We received positive feedback from the producers on how these summary emails are beneficial for them to understand and measure their consumer’s interaction with their APIs.
Our design approach
Research
I started by learning how to send API calls for the Top 20 teams. This hands-on experience helped me understand what our developers go through. I wrote down what I learned and checked what users were saying on various platforms. Then, I went a step further and interviewed Postman developers to understand their challenges better.
Findings
I analyzed all the data collected during my research. This data not only helped me comprehend the key goals of producers but also enabled me to identify the key parameters necessary to achieve these goals.
Long & time consuming
Developers struggle with long and time-consuming authentication instructions.
Missing key steps
Sometimes, the provided instructions leave out important authentication steps, leaving developers confused.
Complex & Daunting
OAuth 2.0 authentication seems complex due to many complicated requirements.
Confusing field names
Different teams use inconsistent field names, causing confusion when mapping them with Postman's fields.
Annoyed by redoing
Users find it annoying to repeatedly authenticate.
Let's get on it
After brainstorming with engineers, developers, & our chief engineering architect, we crafted following idea:
Layout of new authorization experience
'Save Credentials' Interaction
Preserving old authorization experience
Contextual nudge for the new authorization experience
Usability Testing
Issues highlighted by users
After conducting usability testing, I analyzed all the data and did the affinity mapping to highlight the following issues in the key flows:
Improvements in the design
After identifying the issues in the design, I did the brainstorming with my team and came up with the following changes in the key flows:
Final Design
After several round of iterations and testing, we finalized the following designs for the MVP of new authorization experience:
In the above video, I have walked you through the flow of authorizing an API request on Postman via Bearer Token Authorization.
Reflections
