MVP for Postman's Authorization
Sending successful API requests posed a significant challenge for developers on Postman. The main obstacle was the complex and time-consuming nature of the authorization process. The documentation provided by API producers were unclear, creating a barrier to efficient API usage. We decided to create a MVP focused on simplifying and expediting the authorization process. I led the design of MVP and also conducted usability testing to validate the idea. As a result, successful API request percentage increased by 21.2%.
DURATION
12 months
MY ROLE
Product Designer at Postman
METHODS
Semi-structured User Interviews, Wireframing, Rapid Prototyping, High-Fidelity Prototyping, Usability Testing
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:
Goal
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
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.
Complex & Daunting
OAuth 2.0 authentication seems complex due to many complicated requirements.
Ideation
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
Below is a step-by-step breakdown of the final solution we arrived at through a series of iterations:
Step 1: Opening new authorization experience
A contextual nudge in the existing authorization tab directs users to the new, streamlined authorization experience.
Step 2: Sending API request
Users no longer need to select an authorization type manually; automatic mapping and assistive text make it easy to find and add credentials.
Step 3: Saving API request
Upon a successful authorization (200OK), users can save credentials as variables for future requests, eliminating the need to re-enter information.
Reflections
Designing the MVP for Postman’s authorization feature was a transformative experience for me. It was the first time I worked on such an impactful and influential feature, and it taught me invaluable lessons about the power of collaboration and iteration.
Throughout the process, I learned the importance of quick iterations and open discussions with the team. Testing ideas rapidly helped us refine concepts, accept promising ones, and discard those that didn’t work, leading to significant improvements in the design.
A key realization from this experience was the critical role of selecting the right medium for testing ideas. For this MVP, we developed a beta version to test with users, allowing us to validate hypotheses and evaluate our design decisions effectively.
OTHER PROJECTS
Out of all the pixels in all the screens, you ended up here. Grateful for your visit!
2024 Ravi Jangir. All Rights Reserved.
Let’s connect