UX Strategy, Creating the
Unified Developer Experience (UDE)
Internally, our developers often find themselves dedicating a significant portion of their day to searching for tools, seeking assistance, or looking for resources that could enhance their workflow. This scattered approach not only consumes valuable time but also hampers their overall productivity. The primary goal of the Unified Developer Experience (UDE) initiative is to streamline these processes by providing developers with access to a centralized, user-friendly platform. By reducing their workload and minimizing time spent on these tasks, UDE aims to foster increased productivity, ultimately saving the company money while enhancing overall operational efficiency.
Project Length
1 Year 10 Months
UX Strategist
Role
3 UX Designers
1 UX Researcher
7 Developers
Team
Kickoff
​I initiated the project by organizing a meeting with the team to clearly define our objectives and establish a shared vision for our work. During this meeting, we discussed our specific goals and milestones, allowing us to collaboratively identify the best starting point for our efforts. This collaborative approach not only ensures that everyone is aligned but also fosters an environment of open communication, enabling us to harness each team member's insights and expertise as we embark on this project together.
1st Step
Our initial research revealed several critical insights that warrant attention. One of the most significant findings was the lack of continuity between the various tools currently in use. Additionally, there were no established standards or best practices for how tasks should be executed, leading to inconsistencies and inefficiencies. Furthermore, we noted that the existing design system was not tailored to meet the needs of developers. Its bright color palette has been reported to cause eye strain and fatigue by midday, ultimately affecting productivity and overall well-being.
Roadmap
Throughout each phase of our roadmap, we implemented continuous testing and validation processes. This proactive approach allowed us to regularly assess our progress and ensure that we were on the right track. By consistently gathering feedback and analyzing the impact of our changes, we could confirm that the adjustments we were making were effectively enhancing productivity. This commitment to iterative improvement not only helped us stay aligned with our goals but also fostered a culture of accountability and excellence within the team.
We Created a Design System
The design system is set up for developers who are looking at the internal systems all day. It is easier on their eyes and causes less stress throughout the day. For the designers it was build for ease of use. Components and prototypes were all build out, all they needed to do was use them. When an update was made in the design system it reflected it on the designers work. This made maintaining the design system incredibly easy. It was also set up with documentation for the developers so that they new how to implement design and the built in code snippets made it easy for them to use.
Results
At this stage, we successfully established the design system and ensured that all relevant tools across the firm have been updated with the latest designs. This comprehensive implementation has had a significant impact, as we observed a remarkable 22% increase in overall productivity. The alignment of our tools with the new design standards not only streamlined workflows but also enhanced user experience, ultimately contributing to this substantial improvement in performance.
The Main Culprit
We identified a significant barrier that was hindering our progress. Our research revealed that the development of a single API was taking anywhere from one month to an astonishing two years to complete. Recognizing that such delays were unacceptable, I tasked one of our UX designers with addressing this issue. Together, we conducted a thorough analysis and determined that the most effective solution would be to standardize the processes for creating and storing APIs. By establishing clear guidelines and best practices, we aimed to expedite development timelines and improve overall efficiency, ensuring that our API development aligns with the demands of our fast-paced environment.
Developer Journey
We began our initiative by developing a streamlined developer journey specifically focused on the creation of a single type of API. Through rigorous testing and iterative refinement, we addressed and resolved any issues that arose throughout the process. Once we achieved a smooth workflow, we documented the entire procedure comprehensively and established a centralized repository for storing all APIs. With this foundational work completed, we systematically repeated the process for each subsequent type of API, ensuring that our approach remained consistent and effective across the board. As a result of these efforts, we successfully reduced the development time for APIs to a maximum of just two weeks upon launch, significantly enhancing our efficiency.
​
Following the successful implementation of this method, we applied the same strategy to each tool within our suite. This systematic approach aimed to minimize errors, reduce the time spent by team members utilizing the tools, and ultimately enhance overall efficiency. By standardizing processes across all tools, we fostered consistency and improved usability, allowing our team to work more effectively and focus on their core responsibilities. This continuous improvement cycle not only optimized workflows but also contributed to a greater sense of confidence in the tools at our disposal.
Creating A Hub
I selected an existing tool known as Backstage, which provided a solid foundation for our needs. I integrated our design system into this platform and developed a customizable home screen tailored specifically for developers. This home screen features all of their favorite tools and includes a streamlined search function, allowing users to effortlessly add new tools to their personal homepage. With this centralized hub established, developers now have everything they need in one place. They can begin their work, remain focused within the same environment, and complete their tasks without the need to break concentration or seek assistance. This cohesive setup has significantly improved workflow and productivity, enabling a more efficient working experience.
End Results
With the launch of the developer hub, productivity experienced an impressive surge, and developers reported increased job satisfaction. They highlighted that it is now easier to find the tools they need, further enhancing their work experience, while the time dedicated to individual projects was halved. We were able to launch the developer hub six months ahead of schedule. This extra time enabled thorough testing and the collection of key performance indicators (KPIs). During the subsequent six months, minor issues were promptly identified and resolved with ease. Over the span of one year and ten months, our enhancements in productivity and efficiency have resulted in savings of $10 million, while team morale has significantly improved.