Developer Center - Unified Experience
Transforming fragmented developer documentation into a seamless, intuitive hub that reduced onboarding friction and improved content discoverability.
Transforming fragmented developer documentation into a seamless, intuitive hub that reduced onboarding friction and improved content discoverability.
Transforming fragmented developer documentation into a seamless, intuitive hub that reduced onboarding friction and improved content discoverability.
The Challenge
Developers faced fragmented resources across multiple domains, increasing onboarding friction - as evidenced by internal support feedback and task drop-off during early onboarding flows.
Design Goal
Unify all developer documentation and tools into a single hub that reduces time-to-successful onboarding by improving discoverability and reducing navigation pain points.
My Role
I was responsible for research synthesis, wireframing, prototyping, usability testing coordination, and contributing to final UI decisions. I collaborated closely with a Senior Designer and Product Manager and partnered with developers to support design handoff and implementation.
User Research
UX/UI
Prototyping
Wireframing
Usability Testing
Design Handoff
Challenge
Developers faced fragmented resources across multiple domains, increasing onboarding friction — as evidenced by internal support feedback and task drop-off during early onboarding flows.
Design Goal
Unify all developer documentation and tools into a single hub that reduces time-to-successful onboarding by improving discoverability and reducing navigation pain points.
My Role
I was responsible for research synthesis, wireframing, prototyping, usability testing coordination, and contributing to final UI decisions. I collaborated closely with a Senior Designer and Product Manager and partnered with developers to support design handoff and implementation.
User Research
UX/UI
Prototyping
Wireframing
Usability Testing
Design Handoff
Results
Impact and Outcomes
What the new experience delivers:
Research
Understanding the Users
How I Gathered Insights
Focus Group Interviews
I synthesized feedback from developer focus group interviews to identify recurring pain points around onboarding clarity, content organization, and differences between new and experienced users.
These insights helped prioritize which problems required design intervention and informed how content should be structured.
Questions we asked:
“What do you usually look for when starting with a new tool?”
“What makes a developer experience feel frustrating?”
📊 Maze Study
To validate and quantify qualitative themes, I ran a Maze survey with 9 participants to assess expectations, usability gaps, and content priorities.
83%
New users prioritize guided onboarding
First time users said onboarding were top-priority, confirming the need for a clear starting point
Experienced users value depth and efficiency
Advanced users focused on deeper admin and support content, signaling need for segmented pathways.
Card sorting & Information Architecture
Ran a card sorting exercise to understand how users naturally group content. This helped design the experience based on how users think, not our assumptions.
Research
Understanding the Users
How I Gathered Insights
Focus Group Interviews
I synthesized feedback from developer focus group interviews to identify recurring pain points around onboarding clarity, content organization, and differences between new and experienced users.
These insights helped prioritize which problems required design intervention and informed how content should be structured.
Questions we asked:
“What do you usually look for when starting with a new tool?”
“What makes a developer experience feel frustrating?”
Focus Group Interviews
I synthesized feedback from developer focus group interviews to identify recurring pain points around onboarding clarity, content organization, and differences between new and experienced users.
These insights helped prioritize which problems required design intervention and informed how content should be structured.
Questions we asked:
“What do you usually look for when starting with a new tool?”
“What makes a developer experience feel frustrating?”
📊 Maze Study
To validate and quantify qualitative themes, I ran a Maze survey with 9 participants to assess expectations, usability gaps, and content priorities.
83%
New users prioritize guided onboarding
First time users said onboarding were top-priority, confirming the need for a clear starting point
Experienced users value depth and efficiency
Advanced users focused on deeper admin and support content, signaling need for segmented pathways.
83%
New users prioritize guided onboarding
Experienced users value depth and efficiency
📊 Maze Study
To validate and quantify qualitative themes, I ran a Maze survey with 9 participants to assess expectations, usability gaps, and content priorities.
How I Gathered Insights
Focus Group Interviews
I synthesized feedback from developer focus group interviews to identify recurring pain points around onboarding clarity, content organization, and differences between new and experienced users.
These insights helped prioritize which problems required design intervention and informed how content should be structured.
Questions we asked:
“What do you usually look for when starting with a new tool?”
“What makes a developer experience feel frustrating?”
Card sorting & Information Architecture
Ran a card sorting exercise to understand how users naturally group content. This helped design the experience based on how users think, not our assumptions.
Design & Test
Prototypes & Validation
Site Navigation
Initially, we separated "Product Overview" and "Documentation" into different menus. Usability testing showed this caused confusion - users were unsure where to click and expected docs to live closer to the tools.
Before
After
Product Overview Page
Redesigned the product overview page to help users quickly understand what each product does and what to do next. Conducted usability testing with developers of different experience levels.
Before
After
After (light mode)
Additional Screens
Designed supporting pages including 404 Error, My Account and Welcome Email pages to ensure a consistent and polished experience across the platform.
Ideation
From Insights to Ideas
"How Might We" Framework
The team used "How Might We" questions to turn user paint points into actionable ideas. I supported the process by aligning ideas with users personas and journey maps, ensuring solutions stayed focused on real user needs.
User Flow
We created a user flow to turn research insights into a clear path through the Developer Center. It mapped how developers move from landing on the site to completing a task, helping identify friction points and key decision moments.
Accesability
Designing for Everyone
Accessibility was built into every design decision to ensure all users could navigate and use the Developer Center with confidence.
Collaboration
Working with Developers
From the start of the project, I worked closely with developers to align on technical constraints and feasibility. Regular collaboration helped reduce rework and move faster.
Reflection
What I Learned
This project significantly strengthened my ability to design for technical audiences and to build systems that balance clarity with flexibility. It reinforced how small, well-focused research insights can lead to high-impact design decisions.
Developer Center - Unified Experience
Transforming fragmented developer documentation into a seamless, intuitive hub that reduced onboarding friction and improved content discoverability.
Transforming fragmented developer documentation into a seamless, intuitive hub that reduced onboarding friction and improved content discoverability.
The Challenge
Developers faced fragmented resources across multiple domains, increasing onboarding friction - as evidenced by internal support feedback and task drop-off during early onboarding flows.
Design Goal
Unify all developer documentation and tools into a single hub that reduces time-to-successful onboarding by improving discoverability and reducing navigation pain points.
My Role
I was responsible for research synthesis, wireframing, prototyping, usability testing coordination, and contributing to final UI decisions. I collaborated closely with a Senior Designer and Product Manager and partnered with developers to support design handoff and implementation.
User Research
UX/UI
Prototyping
Wireframing
Usability Testing
Design Handoff
Challenge
Developers faced fragmented resources across multiple domains, increasing onboarding friction — as evidenced by internal support feedback and task drop-off during early onboarding flows.
Design Goal
Unify all developer documentation and tools into a single hub that reduces time-to-successful onboarding by improving discoverability and reducing navigation pain points.
My Role
I was responsible for research synthesis, wireframing, prototyping, usability testing coordination, and contributing to final UI decisions. I collaborated closely with a Senior Designer and Product Manager and partnered with developers to support design handoff and implementation.
User Research
UX/UI
Prototyping
Wireframing
Usability Testing
Design Handoff
Results
Impact and Outcomes
What the new experience delivers:
Research
Understanding the Users
How I Gathered Insights
Focus Group Interviews
I synthesized feedback from developer focus group interviews to identify recurring pain points around onboarding clarity, content organization, and differences between new and experienced users.
These insights helped prioritize which problems required design intervention and informed how content should be structured.
Questions we asked:
“What do you usually look for when starting with a new tool?”
“What makes a developer experience feel frustrating?”
📊 Maze Study
To validate and quantify qualitative themes, I ran a Maze survey with 9 participants to assess expectations, usability gaps, and content priorities.
83%
New users prioritize guided onboarding
First time users said onboarding were top-priority, confirming the need for a clear starting point
Experienced users value depth and efficiency
Advanced users focused on deeper admin and support content, signaling need for segmented pathways.
Card sorting & Information Architecture
Ran a card sorting exercise to understand how users naturally group content. This helped design the experience based on how users think, not our assumptions.
Research
Understanding the Users
How I Gathered Insights
Focus Group Interviews
I synthesized feedback from developer focus group interviews to identify recurring pain points around onboarding clarity, content organization, and differences between new and experienced users.
These insights helped prioritize which problems required design intervention and informed how content should be structured.
Questions we asked:
“What do you usually look for when starting with a new tool?”
“What makes a developer experience feel frustrating?”
Focus Group Interviews
I synthesized feedback from developer focus group interviews to identify recurring pain points around onboarding clarity, content organization, and differences between new and experienced users.
These insights helped prioritize which problems required design intervention and informed how content should be structured.
Questions we asked:
“What do you usually look for when starting with a new tool?”
“What makes a developer experience feel frustrating?”
📊 Maze Study
To validate and quantify qualitative themes, I ran a Maze survey with 9 participants to assess expectations, usability gaps, and content priorities.
83%
New users prioritize guided onboarding
Experienced users value depth and efficiency
Advanced users focused on deeper admin and support content, signaling need for segmented pathways.
83%
New users prioritize guided onboarding
Experienced users value depth and efficiency
📊 Maze Study
To validate and quantify qualitative themes, I ran a Maze survey with 9 participants to assess expectations, usability gaps, and content priorities.
How I Gathered Insights
Focus Group Interviews
I synthesized feedback from developer focus group interviews to identify recurring pain points around onboarding clarity, content organization, and differences between new and experienced users.
These insights helped prioritize which problems required design intervention and informed how content should be structured.
Questions we asked:
“What do you usually look for when starting with a new tool?”
“What makes a developer experience feel frustrating?”
Card sorting & Information Architecture
Ran a card sorting exercise to understand how users naturally group content. This helped design the experience based on how users think, not our assumptions.
Design & Test
Prototypes & Validation
Site Navigation
Initially, we separated "Product Overview" and "Documentation" into different menus. Usability testing showed this caused confusion - users were unsure where to click and expected docs to live closer to the tools.
Before
After
Product Overview Page
Redesigned the product overview page to help users quickly understand what each product does and what to do next. Conducted usability testing with developers of different experience levels.
Before
After
Additional Screens
Designed supporting pages including 404 Error, My Account and Welcome Email pages to ensure a consistent and polished experience across the platform.
Ideation
From Insights to Ideas
"How Might We" Framework
The team used "How Might We" questions to turn user paint points into actionable ideas. I supported the process by aligning ideas with users personas and journey maps, ensuring solutions stayed focused on real user needs.
User Flow
We created a user flow to turn research insights into a clear path through the Developer Center. It mapped how developers move from landing on the site to completing a task, helping identify friction points and key decision moments.
Accesability
Designing for Everyone
Accessibility was built into every design decision to ensure all users could navigate and use the Developer Center with confidence.
Collaboration
Working with Developers
From the start of the project, I worked closely with developers to align on technical constraints and feasibility. Regular collaboration helped reduce rework and move faster.
Reflection
What I Learned
This project significantly strengthened my ability to design for technical audiences and to build systems that balance clarity with flexibility. It reinforced how small, well-focused research insights can lead to high-impact design decisions.
Developer Center:
A Unified Experience
Transforming fragmented developer documentation into a seamless, intuitive hub that reduced onboarding friction and improved content discoverability.
Transforming fragmented developer documentation into a seamless, intuitive hub that reduced onboarding friction and improved content discoverability.
The Challenge
Developers faced fragmented resources across multiple domains, increasing onboarding friction - as evidenced by internal support feedback and task drop-off during early onboarding flows.
Design Goal
Unify all developer documentation and tools into a single hub that reduces time-to-successful onboarding by improving discoverability and reducing navigation pain points.
My Role
I was responsible for research synthesis, wireframing, prototyping, usability testing coordination, and contributing to final UI decisions. I collaborated closely with a Senior Designer and Product Manager and partnered with developers to support design handoff and implementation.
User Research
UX/UI
Prototyping
Wireframing
Usability Testing
Design Handoff
Challenge
Developers faced fragmented resources across multiple domains, increasing onboarding friction — as evidenced by internal support feedback and task drop-off during early onboarding flows.
Design Goal
Unify all developer documentation and tools into a single hub that reduces time-to-successful onboarding by improving discoverability and reducing navigation pain points.
My Role
I was responsible for research synthesis, wireframing, prototyping, usability testing coordination, and contributing to final UI decisions. I collaborated closely with a Senior Designer and Product Manager and partnered with developers to support design handoff and implementation.
User Research
UX/UI
Prototyping
Wireframing
Usability Testing
Design Handoff
Results
Impact and Outcomes
What the new experience delivers:
Research
Understanding the Users
How I Gathered Insights
Focus Group Interviews
I synthesized feedback from developer focus group interviews to identify recurring pain points around onboarding clarity, content organization, and differences between new and experienced users.
These insights helped prioritize which problems required design intervention and informed how content should be structured.
Questions we asked:
“What do you usually look for when starting with a new tool?”
“What makes a developer experience feel frustrating?”
📊 Maze Study
To validate and quantify qualitative themes, I ran a Maze survey with 9 participants to assess expectations, usability gaps, and content priorities.
83%
New users prioritize guided onboarding
First time users said onboarding were top-priority, confirming the need for a clear starting point
Experienced users value depth and efficiency
Advanced users focused on deeper admin and support content, signaling need for segmented pathways.
Card sorting & Information Architecture
Ran a card sorting exercise to understand how users naturally group content. This helped design the experience based on how users think, not our assumptions.
Research
Understanding the Users
How I Gathered Insights
Focus Group Interviews
I synthesized feedback from developer focus group interviews to identify recurring pain points around onboarding clarity, content organization, and differences between new and experienced users.
These insights helped prioritize which problems required design intervention and informed how content should be structured.
Questions we asked:
“What do you usually look for when starting with a new tool?”
“What makes a developer experience feel frustrating?”
Focus Group Interviews
I synthesized feedback from developer focus group interviews to identify recurring pain points around onboarding clarity, content organization, and differences between new and experienced users.
These insights helped prioritize which problems required design intervention and informed how content should be structured.
Questions we asked:
“What do you usually look for when starting with a new tool?”
“What makes a developer experience feel frustrating?”
📊 Maze Study
To validate and quantify qualitative themes, I ran a Maze survey with 9 participants to assess expectations, usability gaps, and content priorities.
83%
New users prioritize guided onboarding
First time users said onboarding were top-priority, confirming the need for a clear starting point
Experienced users value depth and efficiency
Advanced users focused on deeper admin and support content, signaling need for segmented pathways.
83%
New users prioritize guided onboarding
Experienced users value depth and efficiency
📊 Maze Study
To validate and quantify qualitative themes, I ran a Maze survey with 9 participants to assess expectations, usability gaps, and content priorities.
How I Gathered Insights
Focus Group Interviews
I synthesized feedback from developer focus group interviews to identify recurring pain points around onboarding clarity, content organization, and differences between new and experienced users.
These insights helped prioritize which problems required design intervention and informed how content should be structured.
Questions we asked:
“What do you usually look for when starting with a new tool?”
“What makes a developer experience feel frustrating?”
Card sorting & Information Architecture
Ran a card sorting exercise to understand how users naturally group content. This helped design the experience based on how users think, not our assumptions.
Design & Test
Prototypes & Validation
Site Navigation
Initially, we separated "Product Overview" and "Documentation" into different menus. Usability testing showed this caused confusion - users were unsure where to click and expected docs to live closer to the tools.
Before
After
Product Overview Page
Redesigned the product overview page to help users quickly understand what each product does and what to do next. Conducted usability testing with developers of different experience levels.
Before
After
Additional Screens
Designed supporting pages including 404 Error, My Account and Welcome Email pages to ensure a consistent and polished experience across the platform.
Ideation
From Insights to Ideas
"How Might We" Framework
The team used "How Might We" questions to turn user paint points into actionable ideas. I supported the process by aligning ideas with users personas and journey maps, ensuring solutions stayed focused on real user needs.
User Flow
We created a user flow to turn research insights into a clear path through the Developer Center. It mapped how developers move from landing on the site to completing a task, helping identify friction points and key decision moments.
Accesability
Designing for Everyone
Accessibility was built into every design decision to ensure all users could navigate and use the Developer Center with confidence.
Collaboration
Working with Developers
From the start of the project, I worked closely with developers to align on technical constraints and feasibility. Regular collaboration helped reduce rework and move faster.
Reflection
What I Learned
This project significantly strengthened my ability to design for technical audiences and to build systems that balance clarity with flexibility. It reinforced how small, well-focused research insights can lead to high-impact design decisions.
