Defining new profile components
Problem
User profiles are often missing professional details that helps Autodesk tailor their experience.
Approach
How might we encourage users to progressively share more information about themselves?
Sector
Technology
Client
Autodesk
Team
2 Designers
1 PM
Tools
Mural, Figma
Timeline
8 weeks
Defining new profile components
Problem
User profiles are often missing professional details that helps Autodesk tailor their experience.
Approach
How might we encourage users to progressively share more information about themselves?
Sector
Technology
Client
Autodesk
Team
2 Designers
1 PM
Tools
Mural, Figma
Timeline
8 weeks
Defining new profile components
Problem
User profiles are often missing professional details that helps Autodesk tailor their experience.
Approach
How might we encourage users to progressively share more information about themselves?
Sector
Technology
Client
Autodesk
Team
4 Designers, 1 Developer,
1 PM / 1 PO
Tools
Mural, Figma
Timeline
8 weeks



Impact at a glance
~5.4M
Monthly visits to Profile landing page and subpages
10+
Component use cases proposed
+2M
Users with completed Job Title or Industry fields month-over-month
View the live site
Developing use cases
Developing use cases
The Identity & Licensing team wanted to deliver a proof of concept: users will disclose data as needed to improve their Autodesk experience.
I proposed card shortcuts to various profile actions that provided value to users through:
Increased account security:
Setting up 2-step verification
Updating your password after 6 months
Personalized communications:
Adding or updating your industry or role
Transparency:
Opting in to email or phone communications

Gathering user feedback
Gathering user feedback

After brainstorming an extensive list of use cases, we wanted to determine how to prioritize release.
We added a feedback survey FAB to understand why users visited the site, and whether they could complete that task from the Profile page.
I helped to refine the organization and language of the questions so that the responses could be assessed against the use cases we developed.
Improving metrics reporting
Improving metrics reporting
To ensure user behaviour around these new components was effectively captured, I worked closely with my Product Manager and data engineers to improve our Adobe Analytics dashboard.
I also contributed to our PRD by identifying important metrics, establishing related KPIs, and describing what they would tell us about the performance of this feature.
For example, I proposed tracking the distribution of clicks on the main Profile page. A larger share of clicks on the card components compared to the sidebar menu items would indicate success.

My biggest takeaway
Designing a great product or feature is just one part of the puzzle — you also need to be able to determine whether or not it's meeting your goals. That starts with knowing what metrics matter. The previous dashboard was rife with visualizations, many of which were redundant or trivial. While the numbers were there, it wasn't clear what they meant for us. We knew there was an opportunity to work with our data partners to better identify opportunities for iteration and improvement.
This is an industry project. Information has been purposefully obfuscated to maintain confidentiality agreements.