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
We developed an MVP by designing monthly summary emails for each team, providing relevant metrics and tailored recommendations to enhance the quality of their APIs.
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.
Getting into the research
The initial problem statement I received from the PM was vague and fuzzy. I organized 1:1 meetings with the Product Manager, Product Head, Design Manager, and fellow designers to better understand the problem we were addressing, why it needed to be solved, why the current design wasn't working, and what success would look like.
Analyzing current design
To better understand the issues in the current design, I analyzed recorded producer calls, developer relations, and data from social forums such as Reddit, Twitter, and Medium.
I conducted rapid affinity mapping on the collected data to identify key problems in the current system:
Research Questions
After conducting preliminary research, I developed the following research questions to guide me toward solving the problem:
What are quality APIs?
Every producer wants to build a quality API, but quality is a very ambiguous and subjective term.
What are relevant metrics for producers?
Producers need metrics to see whether their APIs are moving towards or away from Quality APIs.
How can we assist producers in building quality APIs?
Producers need our assistance in making relevant improvements in their APIs.
Strategy to answer research question
Defining quality APIs
Understanding consumers' interactions with APIs will help me uncover their pain points. Addressing these pain points from the consumers' perspective will allow me to define quality APIs, answering the first research question.
I conducted contextual inquiries with six consumers to observe how they search for the right API for their use case. This approach helped me identify their key challenges and pain points throughout the process.
I decided to present my findings in the form of consumer journey with stages, actions & pain points
Identifying relevant metrics
Customer interaction analysis and collaboration with team members helped me propose relevant metrics for mapping, which will address the second question.
Suggestions for producers to improve APIs
I also conducted a feature mapping exercise within Postman, using insights from customer analysis to propose actionable suggestions for API producers, which will help answer the third research question.
Prioritize metrics
I facilitated a workshop with my Design Manager, Senior Product Designer, Product Managers, and Developers to prioritize the key metrics for our first launch. Together, we identified which metrics to focus on initially and which to save for the next phase.
Design Opportunities
So, after rationally comparing the 2 ideas as shown above, we decided to go with idea-2. I created the high-fidelity design. I also created the mobile design of the emails.
Visualizing interactions
Visualizing change in engagement and functional metrics over time.
More customization
Giving users control on the way to see their metrics.
Assisting Producers
Providing suggestions coupled with metrics to assist producers in enhancing their API quality.
Ideation
We aimed to start small and decided to introduce it in the form of 'Monthly Summary Publisher Emails.' This approach will enable us to test the idea and iteratively enhance it over time. Consequently, I began creating various sketches to address the challenges within this problem space.
Final Design
So, after rationally comparing the 2 ideas as shown above, we decided to go with idea-2. I created the high-fidelity design.
