HP Developer Experience

This project was concepted using a Design Thinking methodology to understand the users of our product and their needs. Extensive background research was done internally to understand employee pain points, requests, and requirements to create achievable and measureable goals. I hosted multiple workshops to ideate and refine ideas. We defined goals and created "Dave Developer" as our persona, and he was divided into two sub-personas: the Consumer (content user) and the Publisher (content creator). Then I outlined a site map based on all the compiled research and brainstorming to begin prototyping.

The design for our Landing page provided all the top level content that the portal offered so users could easily be directed to the solution they were looking for. We tracked feedback and analytics to design the second iteration, which included a more prominent view of what asset types are available and a personalized homepage experience. The upgrade from the static display to a feed that pulls content relevant to that employee's role and peers made the site more important than just a place to go to find a tool. It became a hub for employees to learn about resources within the company that they might not know are available. With this change there was marked rise in homepage visits from both unique and repeat users.

Our initial Search functionality was a bare-bones relevance list with the ability to filter by category and type. The initial user interviews requested a simple scrollable list with basic data and preview information to glance through. However, after implmentation the user behavior revealed deeper insights that we could integrate into the experience. The Search experience was redesigned to include the most frequently used filtering options as top level suggestions, while the ability to expand and collapse preview data kept the interface from being too cluttered. With this change, the Search analytics reported an increase in usage, a decrease in filtering, and a decrease in time spent on the search results before navigating away. These data points indicate that users are able to more quickly and easily find the result they are looking for, accomplishing their goal and getting back to their task.

The goal for the Catalog was for users to be able to search the extensive catalog of tools and services that are internal to HP. The discovery exists in three phases: card preview, sidebar, and full view. The information that appears at each phase was tested with users to help them skim through and quickly discover the tool they are looking for without getting derailed by unnecessary information if the asset was not their solution. Each type of asset (API, pipeline, etc.) has specific filtering and sorting rules relevant to that asset type.

The main event for the hp.dev portal is the API publishing experience. The goal of the API catalog is to reduce rework within the organization, allowing the sharing of internally developed resource APIs. In order to achieve this, an API owner would need to fill out numerous data fields for users to learn about their API. The initial research included card sorting exercises with users to understand what their mental models of API information were and how to draft our initial design. This experience went through multiple iterations through testing, where we learned how to optimize and organize the pages and reduce the cognitive load for the user. A gamification element of API status was included to incentivize API owners to fill out all the input fields for a more complete API entry. Future plans for the API upload experience include batch API upload and AI assisted API upload/creation.