A centralized Data Portal platform already existed, however, the Portal was created alongside an earlier generation of ADP. As such, information was outdated and did not address the capabilities and processes of current ADP offerings.
The Data Portal was managed by the Learning and Development team, but ultimately maintained by a contracted web design firm.
Card sorting exercises were conducted with a Data Engineer, Data Scientist, and Product Manager to refine an intuitive categorization schema.
The exercise refined not just taxonomy of the site, but terminology, as well.
The resulting knowledge hierarchy emphasized ADP value at the highest level, gradually funneling users into progressively technical explanation.
Lateral movement across ADP offerings allows for technical users to drill directly into the content they are searching for.
Defining the hierarchy of knowledge for the site allowed a distinction to be made between high-level ADP value (which appeals to Data Readers and Team Leads), and low-level product details (which appeal to Data Analysts, Engineers, and Scientists).
The conceptual knowledge hierarchy was operationalized into a comprehensive restructuring of the Data Portal’s information architecture.
A comprehensive mapping was created that outlined the total content required and where existing content is located.
Mockups of the Data Portal with the revised information architecture were created for the Learning and Development team to share with contractors who manage the site.
A service design blueprint synthesized research and visually represented paint points, dependencies, and areas of opportunity that exist throughout the process of using the “Data Modeling & ETL” product.
Mapping of process, pain points, dependencies, and areas of opportunity involved in the ETL process on ADP.
The exercise suggested that technical users required three distinct pieces of knowledge throughout their engagement with ADP:
An overview of the process required to use the various softwares of ADP
Detailed explanations of permissions, points of contact, and use case-dependent instructions
Notes of what works and what didn’t for teams that have gone before
Early prototypes were tested with users to refine the design of a boilerplate webpage for ADP products.
A rough prototype was created to validate if the prioritization of content was accurate and relevant to users.
Mockups of the restructured Data Portal and ADP Product page were tested with Data Engineers.
Users praised the high-level overview and guidance that the site would offer, but commented that many of the details required to actually run an ETL are not documented on any source.
A wiki rennovation was being simultaneously conducted by the Learning and Development team to address this concern, but maintenance of the technical knowledge base was acknowledged as a crticial assumption to the design’s overall success.