Designing a consistent profile experience across all of User Interviews
Overview
In this project, I audited an inconsistent profile experience across 9 different product locations and implemented a consistent interaction and visual design structure. I designed a modular profile component to be used across the entire product for accessing attributes associated with participant accounts. I conducted 5 rounds of research and design iteration. Finally, I led the final development QA with our engineering team, and we shipped a universal profile view across our application.
Project collaborators
Luke Friedman
Product Manager
Kyle Shike
Senior Engineer
Rachel Roppolo
Engineering Manager
Sav Phillips
Product Designer
Key metrics
Metric 1
Metric 2
Timeframe
Fall 2023
Overview
In this project, I audited an inconsistent profile experience across 9 different product locations and implemented a consistent interaction and visual design structure. I designed a modular profile component to be used across the entire product for accessing attributes associated with participant accounts. I conducted 5 rounds of research and design iteration. Finally, I led the final development QA with our engineering team, and we shipped a universal profile view across our application.
Project collaborators
Luke Friedman
Product Manager
Kyle Shike
Senior Engineer
Rachel Roppolo
Engineering Manager
Sav Phillips
Product Designer
Key metrics
Metric 1
Metric 2
Timeframe
Fall 2023
Overview
In this project, I audited an inconsistent profile experience across 9 different product locations and implemented a consistent interaction and visual design structure. I designed a modular profile component to be used across the entire product for accessing attributes associated with participant accounts. I conducted 5 rounds of research and design iteration. Finally, I led the final development QA with our engineering team, and we shipped a universal profile view across our application.
Project collaborators
Luke Friedman
Product Manager
Kyle Shike
Senior Engineer
Rachel Roppolo
Engineering Manager
Sav Phillips
Product Designer
Key metrics
Metric 1
Metric 2
Timeframe
Fall 2023
Understanding the problem space
Prior ecosystem
Before the profile component updates, the researcher experience of reviewing participant data was inconsistent across multiple contexts. Our project workspace context offered one view of a participant, while our CRM experience presented another.
In the previous ecosystem, there were significant discrepancies in the data shown across these two contexts. Data display also varied dynamically depending on the type of project—moderated or unmoderated—that a researcher was running.
Many users reported frustration with not being able to access the right data at the right time, often needing to toggle between views to piece together a complete participant profile. Inconsistencies in components and review workflows added further friction, underscoring the need for a more unified and coherent profile system.
Snapshot of previous profile experiences (Project workspace). The context of this profile is a participant from our external audience ("Recruit audience"), in a Moderated Project template
Snapshot of previous profile experiences (Research Hub CRM)
Understanding the problem space
Prior ecosystem
Before the profile component updates, the researcher experience of reviewing participant data was inconsistent across multiple contexts. Our project workspace context offered one view of a participant, while our CRM experience presented another.
In the previous ecosystem, there were significant discrepancies in the data shown across these two contexts. Data display also varied dynamically depending on the type of project—moderated or unmoderated—that a researcher was running.
Many users reported frustration with not being able to access the right data at the right time, often needing to toggle between views to piece together a complete participant profile. Inconsistencies in components and review workflows added further friction, underscoring the need for a more unified and coherent profile system.
Snapshot of previous profile experiences (Project workspace). The context of this profile is a participant from our external audience ("Recruit audience"), in a Moderated Project template
Snapshot of previous profile experiences (Research Hub CRM)
Understanding the problem space
Prior ecosystem
Before the profile component updates, the researcher experience of reviewing participant data was inconsistent across multiple contexts. Our project workspace context offered one view of a participant, while our CRM experience presented another.
In the previous ecosystem, there were significant discrepancies in the data shown across these two contexts. Data display also varied dynamically depending on the type of project—moderated or unmoderated—that a researcher was running.
Many users reported frustration with not being able to access the right data at the right time, often needing to toggle between views to piece together a complete participant profile. Inconsistencies in components and review workflows added further friction, underscoring the need for a more unified and coherent profile system.
Snapshot of previous profile experiences (Project workspace). The context of this profile is a participant from our external audience ("Recruit audience"), in a Moderated Project template
Snapshot of previous profile experiences (Research Hub CRM)
Design approach
Audit the existing experience
First, I audited the existing experience, the understand how existing data attributes lived across our product. I looked into EnjoyHQ our feedback database to understand current customer pain points and how that relates to the current structure.
Comparitive analysis
Next I conducted a comparative analysis of other leading products, and how the visualized the profile experience. I paid close attention to information architecture of the profile within tables, and how the profile interactively opened and closed.
Create hypothesis wireframes
Last, I framed design requirements internally with team based on audits, customer feedback, and comparative analysis. Then I created hypothesis wireframes, synthesizing design requirements into an artifact.
Design approach
Audit the existing experience
First, I audited the existing experience, the understand how existing data attributes lived across our product. I looked into EnjoyHQ our feedback database to understand current customer pain points and how that relates to the current structure.
Comparitive analysis
Next I conducted a comparative analysis of other leading products, and how the visualized the profile experience. I paid close attention to information architecture of the profile within tables, and how the profile interactively opened and closed.
Create hypothesis wireframes
Last, I framed design requirements internally with team based on audits, customer feedback, and comparative analysis. Then I created hypothesis wireframes, synthesizing design requirements into an artifact.
Design approach
Audit the existing experience
First, I audited the existing experience, the understand how existing data attributes lived across our product. I looked into EnjoyHQ our feedback database to understand current customer pain points and how that relates to the current structure.
Comparitive analysis
Next I conducted a comparative analysis of other leading products, and how the visualized the profile experience. I paid close attention to information architecture of the profile within tables, and how the profile interactively opened and closed.
Create hypothesis wireframes
Last, I framed design requirements internally with team based on audits, customer feedback, and comparative analysis. Then I created hypothesis wireframes, synthesizing design requirements into an artifact.
Research approach
Some text about this project etc
Outcomes
Some text about this project etc
