Developers spent excessive time adapting code and resolving compatibility issues rather than focusing on innovation or user impacting improvements
Here is how we bridge the gap!
Outcomes!
Research helps informed product and delivered an AI solution that guided developers during the development cycle!
25%
By implementing an AI-powered onboarding feature for internal products, our development team is now equipped with guided assistance that streamlines their workflows and enhances efficiency, resulting in a 25% increase in code production speed.
35%
By streamlining the user journey to require only a single login, we simplified access and reduced friction, resulting in a 35% increase in product usage.
15%
By accelerating the code development process and addressing consistency issues in production, the team was able to deliver higher quality releases more efficiently, reducing errors and improving the overall reliability of the product.
Project Overview
Research Categories
Studies Type
Role/Contribution
Time line
Relevant Tools
Cross-F. Team
Stakeholder Teams
Users
Evaluative Interviews, Usability testing and Competitive Analysis.
Research Lead, UX Strategist.
5-months Usability testing through out internal systems.
UserTesting, Miro, Zoom meeting, team meeting.
UX Researcher, UX Manager, UX Designer.
Development Product, Product Managers.
3 Users developers (UserTesting), interviews15 users (devs)
Brief
Problem statement
We need to understand how best to help developers accelerate the life cycle and migrating code.
Approximate 3k users across the organization, try to get value from products, unfortunately the tool are fragmented, incrementing time for production, making developers login several times and get frustrated.
Business objectives
Increase internal access by reducing the number of steps and creating an intuitive system.
- Prioritize employee engagement and accelerate code to production.
- Reduce the time employees spend searching for and fixing code in a fragmented system
Research Overview
I led research, conducting interviews and usability testing for 5 months through an internal system with developers, We focused on new hires and medium level developers.
Methodology
-
what steps I take. what questions and what kind of developers I have interview it.
-
what another products offering that we can learn from it and validating capabilities products.
-
documenting developers In real life going through the system, I noticed the issues they faced during development cycle.
-
Tracking usage of internal products after iteration.
Artifacts
Persona
Primary Users:
Our main users were mid-level developers with 3–5 years of experience. While highly skilled, many of them were navigating growing responsibilities and complex workflows that often stretched their time and focus.
Over a five-month period, we partnered directly with these developers, observing their daily challenges and listening to their perspectives. Through continuous dialogue and iterative feedback, we uncovered pain points that had previously gone unnoticed.
These insights did more than streamline processes—they saved the company valuable resources and gave developers a smoother, more supportive work environment. By reducing friction in their workflows, we helped unlock more time for problem-solving, creativity, and impact.
Please read about our Main User:
Journey Map
In our usability testing study, we created a journey map to capture developers’ experiences onboarding to the internal tool, highlighting touchpoints from initial access to completing a first task. The map revealed key moments of friction, such as unclear documentation and navigation challenges, as well as areas of success where intuitive workflows supported quick learning. By visualizing pain points alongside positive interactions, the journey map provided a shared resource for stakeholders to align on priorities, guiding improvements that streamline onboarding and increase developer confidence in adopting the tool.
From onboard products to migrating code!
Ethnographic
I gather all the frictions high level from usability testing to communicate effective to stakeholders
These infographic was a great well to communicate insights seeing the developers going to a shopping store and start getting tools they will need to produce code.
The Challenge
Aimed to help stakeholders understand our data!
As a UX Researcher, I faced the challenge of helping stakeholders—many of whom had no prior experience with our team’s studies—understand and connect with the data. To bridge this gap, I prioritized collaboration through early and frequent communication. I invited stakeholders to observe usability testing sessions using simple tools that revealed real-life frictions, making the findings more tangible. After each session, we captured their insights and reflections in Mural, ensuring their perspectives were integrated into iteration and helping them engage more deeply with the research process.
Key Points:
Foster collaboration through early and frequent communication.
Invite stakeholders to watch usability testing with minimal tools to observe real-life frictions.
After each session, we use Mural to capture stakeholders ideas and frictions for iteration.
( Graphic) explain How I connected two rooms and open Mural for collaboration.
The Solution
By collaborating with stakeholders, 14 internal product teams, and leadership, we successfully built an ecosystem that avoids multiple logins, organizes documentation, and provides a single unified resource.
( Graphic explain How may we build an ecosystem where any developer is able to easy learn and guide their own through the system).
What we achieve!
We’ve got a new library updates system that’s a game-changer! It’s got an audit feature that checks the code monthly, so developers can quickly find and fix any issues. This has boosted our productivity and saved our business a whopping 20,000 dollars each month.
Added an Al feature to help our developers get onboarded with our products. This has increased usage by a whopping 25%.
Made it super easy for developers to find what they need by streamlining the steps and providing clear instructions. This has resulted in an even bigger increase in usage, with a whopping 35% boost!
The Prototype
Here is the prototype after several iterations, including retrospectives and collaborations with internal products.
We were able to quickly identify obstacles and fine-tune it on the fly through lean usability testing sessions, which were observable to PMs and stakeholders.”
