Growing Pains: Fixing Evolving Userflows
Streamlining navigation for a rapidly evolving CRM platform
2025
Year
2025
Year
2025
Year
2025
Year
3 weeks
Duration
3 weeks
Duration
3 weeks
Duration
3 weeks
Duration
Figma
Stack
Figma
Stack
Figma
Stack
Figma
Stack
2-5 minutes
Reading Time
2-5 minutes
Reading Time
2-5 minutes
Reading Time
2-5 minutes
Reading Time
Quick Summary
Problem
What began as a simple internal sales campaign tool rapidly scaled into Mobi, a complex CRM platform. This swift expansion, however, created a significant challenge: cluttered and confusing navigation. Users found themselves unable to efficiently locate critical information, leading to frustrating detours and wasted time.
Problem
What began as a simple internal sales campaign tool rapidly scaled into Mobi, a complex CRM platform. This swift expansion, however, created a significant challenge: cluttered and confusing navigation. Users found themselves unable to efficiently locate critical information, leading to frustrating detours and wasted time.
Problem
What began as a simple internal sales campaign tool rapidly scaled into Mobi, a complex CRM platform. This swift expansion, however, created a significant challenge: cluttered and confusing navigation. Users found themselves unable to efficiently locate critical information, leading to frustrating detours and wasted time.
Problem
What began as a simple internal sales campaign tool rapidly scaled into Mobi, a complex CRM platform. This swift expansion, however, created a significant challenge: cluttered and confusing navigation. Users found themselves unable to efficiently locate critical information, leading to frustrating detours and wasted time.
Solution
I redesigned Mobi's navigation by introducing a centralized landing page, categorized page types, and standardized layouts. These enhancements significantly improved discoverability for new users while retaining efficiency for expert users through familiar shortcuts, all while documenting the system for future scalability and growth.
Solution
I redesigned Mobi's navigation by introducing a centralized landing page, categorized page types, and standardized layouts. These enhancements significantly improved discoverability for new users while retaining efficiency for expert users through familiar shortcuts, all while documenting the system for future scalability and growth.
Solution
I redesigned Mobi's navigation by introducing a centralized landing page, categorized page types, and standardized layouts. These enhancements significantly improved discoverability for new users while retaining efficiency for expert users through familiar shortcuts, all while documenting the system for future scalability and growth.
Solution
I redesigned Mobi's navigation by introducing a centralized landing page, categorized page types, and standardized layouts. These enhancements significantly improved discoverability for new users while retaining efficiency for expert users through familiar shortcuts, all while documenting the system for future scalability and growth.
My Role
I led the end-to-end UX design process, spanning from initial user research (usability tests, interviews) and interactive prototyping to final development handoff. Throughout, I closely coordinated with engineering teams to ensure seamless alignment and smooth implementation.
My Role
I led the end-to-end UX design process, spanning from initial user research (usability tests, interviews) and interactive prototyping to final development handoff. Throughout, I closely coordinated with engineering teams to ensure seamless alignment and smooth implementation.
My Role
I led the end-to-end UX design process, spanning from initial user research (usability tests, interviews) and interactive prototyping to final development handoff. Throughout, I closely coordinated with engineering teams to ensure seamless alignment and smooth implementation.
My Role
I led the end-to-end UX design process, spanning from initial user research (usability tests, interviews) and interactive prototyping to final development handoff. Throughout, I closely coordinated with engineering teams to ensure seamless alignment and smooth implementation.
Challenges
Key challenges included balancing the diverse needs of a wide user base, designing a system flexible enough to accommodate ongoing platform growth, and ensuring a smooth handoff for future development without requiring continuous UX involvement.
Challenges
Key challenges included balancing the diverse needs of a wide user base, designing a system flexible enough to accommodate ongoing platform growth, and ensuring a smooth handoff for future development without requiring continuous UX involvement.
Challenges
Key challenges included balancing the diverse needs of a wide user base, designing a system flexible enough to accommodate ongoing platform growth, and ensuring a smooth handoff for future development without requiring continuous UX involvement.
Challenges
Key challenges included balancing the diverse needs of a wide user base, designing a system flexible enough to accommodate ongoing platform growth, and ensuring a smooth handoff for future development without requiring continuous UX involvement.
Complete Process
Step 0: Context
A Platform Outgrowing Itself
Step 0: Context
A Platform Outgrowing Itself
Step 0: Context
A Platform Outgrowing Itself
Step 0: Context
A Platform Outgrowing Itself
When Simple Becomes Complicated
Following my successful work on Mobi, I was brought back to address broader usability challenges. What began as a simple campaign tracker had rapidly evolved into a sprawling CRM, exceeding its initial scope with increased features, users, and complexity. This rapid growth led to unclear navigation, particularly for new or less tech-savvy users, who frequently struggled with lookalike pages and overlapping functionality.
Different functions, same look. Often, users input or collected data in the wrong places, thinking they were right all along.
When Simple Becomes Complicated
Following my successful work on Mobi, I was brought back to address broader usability challenges. What began as a simple campaign tracker had rapidly evolved into a sprawling CRM, exceeding its initial scope with increased features, users, and complexity. This rapid growth led to unclear navigation, particularly for new or less tech-savvy users, who frequently struggled with lookalike pages and overlapping functionality.
Different functions, same look. Often, users input or collected data in the wrong places, thinking they were right all along.
When Simple Becomes Complicated
Following my successful work on Mobi, I was brought back to address broader usability challenges. What began as a simple campaign tracker had rapidly evolved into a sprawling CRM, exceeding its initial scope with increased features, users, and complexity. This rapid growth led to unclear navigation, particularly for new or less tech-savvy users, who frequently struggled with lookalike pages and overlapping functionality.
Different functions, same look. Often, users input or collected data in the wrong places, thinking they were right all along.
When Simple Becomes Complicated
Following my successful work on Mobi, I was brought back to address broader usability challenges. What began as a simple campaign tracker had rapidly evolved into a sprawling CRM, exceeding its initial scope with increased features, users, and complexity. This rapid growth led to unclear navigation, particularly for new or less tech-savvy users, who frequently struggled with lookalike pages and overlapping functionality.
Different functions, same look. Often, users input or collected data in the wrong places, thinking they were right all along.
What is Alta Genetics and Mobi?
Alta, a global leader in livestock genetics, provides advanced breeding solutions worldwide. They developed Mobi, an internal CRM platform that began as a lightweight campaign tracker for field and sales teams. Over time, Mobi evolved into a comprehensive tool, managing client relationships, monitoring regional activity, and coordinating field operations across diverse teams.
What is Alta Genetics and Mobi?
Alta, a global leader in livestock genetics, provides advanced breeding solutions worldwide. They developed Mobi, an internal CRM platform that began as a lightweight campaign tracker for field and sales teams. Over time, Mobi evolved into a comprehensive tool, managing client relationships, monitoring regional activity, and coordinating field operations across diverse teams.
What is Alta Genetics and Mobi?
Alta, a global leader in livestock genetics, provides advanced breeding solutions worldwide. They developed Mobi, an internal CRM platform that began as a lightweight campaign tracker for field and sales teams. Over time, Mobi evolved into a comprehensive tool, managing client relationships, monitoring regional activity, and coordinating field operations across diverse teams.
What is Alta Genetics and Mobi?
Alta, a global leader in livestock genetics, provides advanced breeding solutions worldwide. They developed Mobi, an internal CRM platform that began as a lightweight campaign tracker for field and sales teams. Over time, Mobi evolved into a comprehensive tool, managing client relationships, monitoring regional activity, and coordinating field operations across diverse teams.
Step 1: Defining
Finding the Gaps
Step 1: Defining
Finding the Gaps
Step 1: Defining
Finding the Gaps
Step 1: Defining
Finding the Gaps
Listening to Users
Before diving into design, I conducted a thorough investigation using usability tests, stakeholder interviews, and web analytics analysis to pinpoint user challenges. A critical discovery was the existence of distinct user personas: sales reps, managers, and support teams each had unique habits, expectations, and pain points. This meant a solution that intuitively worked for one group could be entirely confusing for another.
Listening to Users
Before diving into design, I conducted a thorough investigation using usability tests, stakeholder interviews, and web analytics analysis to pinpoint user challenges. A critical discovery was the existence of distinct user personas: sales reps, managers, and support teams each had unique habits, expectations, and pain points. This meant a solution that intuitively worked for one group could be entirely confusing for another.
That fading tattoo on the bull's leg? Is how we identify them, and this is a good case
Listening to Users
Before diving into design, I conducted a thorough investigation using usability tests, stakeholder interviews, and web analytics analysis to pinpoint user challenges. A critical discovery was the existence of distinct user personas: sales reps, managers, and support teams each had unique habits, expectations, and pain points. This meant a solution that intuitively worked for one group could be entirely confusing for another.
That fading tattoo on the bull's leg? Is how we identify them, and this is a good case
Listening to Users
Before diving into design, I conducted a thorough investigation using usability tests, stakeholder interviews, and web analytics analysis to pinpoint user challenges. A critical discovery was the existence of distinct user personas: sales reps, managers, and support teams each had unique habits, expectations, and pain points. This meant a solution that intuitively worked for one group could be entirely confusing for another.
Navigating the Maze
The original user flow and pages
Hide Overlay
Endless Loops: Almost every page is linked to every other, making it easy to get lost.
Identical Headers: Navigation menus and headers looked the same across sections, blurring the lines between pages.
Mixed Navigation: Dropdowns, buttons, and links were used interchangeably and often styled like non-interactive elements.
Navigating the Maze
The original user flow and pages
Hide Overlay
Endless Loops: Almost every page is linked to every other, making it easy to get lost.
Identical Headers: Navigation menus and headers looked the same across sections, blurring the lines between pages.
Mixed Navigation: Dropdowns, buttons, and links were used interchangeably and often styled like non-interactive elements.
Navigating the Maze
The original user flow and pages
Hide Overlay
Endless Loops: Almost every page is linked to every other, making it easy to get lost.
Identical Headers: Navigation menus and headers looked the same across sections, blurring the lines between pages.
Mixed Navigation: Dropdowns, buttons, and links were used interchangeably and often styled like non-interactive elements.
Navigating the Maze
The original user flow and pages
Hide Overlay
Endless Loops: Almost every page is linked to every other, making it easy to get lost.
Identical Headers: Navigation menus and headers looked the same across sections, blurring the lines between pages.
Mixed Navigation: Dropdowns, buttons, and links were used interchangeably and often styled like non-interactive elements.
No NDAs Were Harmed
Everything shown here is based on real project material, with a few adjustments for translation, privacy, or clarity. All content was approved before publishing.
No NDAs Were Harmed
Everything shown here is based on real project material, with a few adjustments for translation, privacy, or clarity. All content was approved before publishing.
No NDAs Were Harmed
Everything shown here is based on real project material, with a few adjustments for translation, privacy, or clarity. All content was approved before publishing.
No NDAs Were Harmed
Everything shown here is based on real project material, with a few adjustments for translation, privacy, or clarity. All content was approved before publishing.
Exploring Hypotheses
With the main issues mapped out, the next step was to test two key ideas:
A central hub could reduce friction. Turning the landing page into a true starting point, both a dashboard and a navigation hub, would reduce backtracking and help users orient themselves more quickly.
Grouping pages by user behaviour would improve clarity. People used the platform differently. By analyzing usage patterns and segmenting page types by function and user role, navigation could be structured to match how different teams actually worked.
This wasn't just a design shift but a continuation of my previous work on Mobi's dashboard. Expanding that role made the landing page more meaningful and gave users a natural anchor.
The landing page evolved into a central hub, organizing information and navigation in one place.
Exploring Hypotheses
With the main issues mapped out, the next step was to test two key ideas:
A central hub could reduce friction. Turning the landing page into a true starting point, both a dashboard and a navigation hub, would reduce backtracking and help users orient themselves more quickly.
Grouping pages by user behaviour would improve clarity. People used the platform differently. By analyzing usage patterns and segmenting page types by function and user role, navigation could be structured to match how different teams actually worked.
This wasn't just a design shift but a continuation of my previous work on Mobi's dashboard. Expanding that role made the landing page more meaningful and gave users a natural anchor.
The landing page evolved into a central hub, organizing information and navigation in one place.
Exploring Hypotheses
With the main issues mapped out, the next step was to test two key ideas:
A central hub could reduce friction. Turning the landing page into a true starting point, both a dashboard and a navigation hub, would reduce backtracking and help users orient themselves more quickly.
Grouping pages by user behaviour would improve clarity. People used the platform differently. By analyzing usage patterns and segmenting page types by function and user role, navigation could be structured to match how different teams actually worked.
This wasn't just a design shift but a continuation of my previous work on Mobi's dashboard. Expanding that role made the landing page more meaningful and gave users a natural anchor.
The landing page evolved into a central hub, organizing information and navigation in one place.
Exploring Hypotheses
With the main issues mapped out, the next step was to test two key ideas:
A central hub could reduce friction. Turning the landing page into a true starting point, both a dashboard and a navigation hub, would reduce backtracking and help users orient themselves more quickly.
Grouping pages by user behaviour would improve clarity. People used the platform differently. By analyzing usage patterns and segmenting page types by function and user role, navigation could be structured to match how different teams actually worked.
This wasn't just a design shift but a continuation of my previous work on Mobi's dashboard. Expanding that role made the landing page more meaningful and gave users a natural anchor.
The landing page evolved into a central hub, organizing information and navigation in one place.
Preliminary Results
The results were highly promising: users experienced reduced backtracking and improved task completion times across all identified personas. Experienced users continued to benefit from familiar navigation bars, while new users discovered more intuitive and clearly marked paths.
Preliminary Results
The results were highly promising: users experienced reduced backtracking and improved task completion times across all identified personas. Experienced users continued to benefit from familiar navigation bars, while new users discovered more intuitive and clearly marked paths.
Preliminary Results
The results were highly promising: users experienced reduced backtracking and improved task completion times across all identified personas. Experienced users continued to benefit from familiar navigation bars, while new users discovered more intuitive and clearly marked paths.
Preliminary Results
The results were highly promising: users experienced reduced backtracking and improved task completion times across all identified personas. Experienced users continued to benefit from familiar navigation bars, while new users discovered more intuitive and clearly marked paths.
Step 2: Design
Solution for Navigation
Step 2: Design
Solution for Navigation
Step 2: Design
Solution for Navigation
Step 2: Design
Solution for Navigation
Building for Clarity
With our hypothesis validated, I started translating those insights into design. The priorities were clear: establish a central hub, group content by behaviour, and create consistent patterns to reduce confusion and build user confidence.
Building for Clarity
With our hypothesis validated, I started translating those insights into design. The priorities were clear: establish a central hub, group content by behaviour, and create consistent patterns to reduce confusion and build user confidence.
Building for Clarity
With our hypothesis validated, I started translating those insights into design. The priorities were clear: establish a central hub, group content by behaviour, and create consistent patterns to reduce confusion and build user confidence.
Building for Clarity
With our hypothesis validated, I started translating those insights into design. The priorities were clear: establish a central hub, group content by behaviour, and create consistent patterns to reduce confusion and build user confidence.
The New Landing Page
Detailed view of the landing page layout
Overlay & Specs
Clear Category Distinctions: Each section is visually grouped, eliminating previous guesswork.
Behaviour-Driven Layout: Pages are organized by usage patterns tied to specific user roles.
New Standards: Consistent styling and layout across components improve usability and visuals.
The New Landing Page
Detailed view of the landing page layout
Overlay & Specs
Clear Category Distinctions: Each section is visually grouped, eliminating previous guesswork.
Behaviour-Driven Layout: Pages are organized by usage patterns tied to specific user roles.
New Standards: Consistent styling and layout across components improve usability and visuals.
The New Landing Page
Detailed view of the landing page layout
Overlay & Specs
Clear Category Distinctions: Each section is visually grouped, eliminating previous guesswork.
Behaviour-Driven Layout: Pages are organized by usage patterns tied to specific user roles.
New Standards: Consistent styling and layout across components improve usability and visuals.
The New Landing Page
Detailed view of the landing page layout
Overlay & Specs
Clear Category Distinctions: Each section is visually grouped, eliminating previous guesswork.
Behaviour-Driven Layout: Pages are organized by usage patterns tied to specific user roles.
New Standards: Consistent styling and layout across components improve usability and visuals.
The Team Behind Mobi
Mobi was a unique project at Alta. Following a fast-paced iterative development process, the main developers were not from the company's software team but people with coding skills already in the teams that needed Mobi the most. For this reason, much of the design was simplified to facilitate development.
The Team Behind Mobi
Mobi was a unique project at Alta. Following a fast-paced iterative development process, the main developers were not from the company's software team but people with coding skills already in the teams that needed Mobi the most. For this reason, much of the design was simplified to facilitate development.
The Team Behind Mobi
Mobi was a unique project at Alta. Following a fast-paced iterative development process, the main developers were not from the company's software team but people with coding skills already in the teams that needed Mobi the most. For this reason, much of the design was simplified to facilitate development.
The Team Behind Mobi
Mobi was a unique project at Alta. Following a fast-paced iterative development process, the main developers were not from the company's software team but people with coding skills already in the teams that needed Mobi the most. For this reason, much of the design was simplified to facilitate development.
The New Pages
Example of Updated Pages
Show Old Pages
Breadcrumb Navigation: A clear back-to-landing button helps users retrace their steps and re-anchor navigation.
Simplified Header: Headers now display only relevant content, reducing distractions.
Visual Differentiation: Distinct styles help users recognize where they are at a glance.
The New Pages
Example of Updated Pages
Show Old Pages
Breadcrumb Navigation: A clear back-to-landing button helps users retrace their steps and re-anchor navigation.
Simplified Header: Headers now display only relevant content, reducing distractions.
Visual Differentiation: Distinct styles help users recognize where they are at a glance.
The New Pages
Example of Updated Pages
Show Old Pages
Breadcrumb Navigation: A clear back-to-landing button helps users retrace their steps and re-anchor navigation.
Simplified Header: Headers now display only relevant content, reducing distractions.
Visual Differentiation: Distinct styles help users recognize where they are at a glance.
The New Pages
Example of Updated Pages
Show Old Pages
Breadcrumb Navigation: A clear back-to-landing button helps users retrace their steps and re-anchor navigation.
Simplified Header: Headers now display only relevant content, reducing distractions.
Visual Differentiation: Distinct styles help users recognize where they are at a glance.
Step 3: Results
Outcomes
Step 3: Results
Outcomes
Step 3: Results
Outcomes
Step 3: Results
Outcomes
Built to Scale
The improvements made to Mobi were designed with scalability in mind. Navigation was rebuilt from the ground up, page types were categorized for clarity, and layout components were standardized for future consistency. Each element was documented, from user flow diagrams to design specs, ensuring the development team could confidently carry the work forward even after I left the company.
Built to Scale
The improvements made to Mobi were designed with scalability in mind. Navigation was rebuilt from the ground up, page types were categorized for clarity, and layout components were standardized for future consistency. Each element was documented, from user flow diagrams to design specs, ensuring the development team could confidently carry the work forward even after I left the company.
Built to Scale
The improvements made to Mobi were designed with scalability in mind. Navigation was rebuilt from the ground up, page types were categorized for clarity, and layout components were standardized for future consistency. Each element was documented, from user flow diagrams to design specs, ensuring the development team could confidently carry the work forward even after I left the company.
Built to Scale
The improvements made to Mobi were designed with scalability in mind. Navigation was rebuilt from the ground up, page types were categorized for clarity, and layout components were standardized for future consistency. Each element was documented, from user flow diagrams to design specs, ensuring the development team could confidently carry the work forward even after I left the company.
The Impact
28% Faster Task Completion. Usability tests showed users completed core tasks significantly faster.
28% Faster Task Completion. Usability tests showed users completed core tasks significantly faster.
28% Faster Task Completion. Usability tests showed users completed core tasks significantly faster.
28% Faster Task Completion. Usability tests showed users completed core tasks significantly faster.
41% Fewer Navigation Errors. Consistent layouts and clear pathways reduced misclicks and mistakes.
41% Fewer Navigation Errors. Consistent layouts and clear pathways reduced misclicks and mistakes.
41% Fewer Navigation Errors. Consistent layouts and clear pathways reduced misclicks and mistakes.
41% Fewer Navigation Errors. Consistent layouts and clear pathways reduced misclicks and mistakes.
Positive Feedback. Users across experience levels found the interface easier to understand and use.
Positive Feedback. Users across experience levels found the interface easier to understand and use.
Positive Feedback. Users across experience levels found the interface easier to understand and use.
Positive Feedback. Users across experience levels found the interface easier to understand and use.
Building on Stronger Foundations
What began as a minor navigation fix evolved into a significant rethinking of Mobi's core structure. The redesigned system empowered users with clarity and control, simultaneously providing Alta with a reliable foundation for continued growth. While centered on navigation, this project also revealed deeper insights into team workflows, invaluable for guiding future platform enhancements.
Building on Stronger Foundations
What began as a minor navigation fix evolved into a significant rethinking of Mobi's core structure. The redesigned system empowered users with clarity and control, simultaneously providing Alta with a reliable foundation for continued growth. While centered on navigation, this project also revealed deeper insights into team workflows, invaluable for guiding future platform enhancements.
Building on Stronger Foundations
What began as a minor navigation fix evolved into a significant rethinking of Mobi's core structure. The redesigned system empowered users with clarity and control, simultaneously providing Alta with a reliable foundation for continued growth. While centered on navigation, this project also revealed deeper insights into team workflows, invaluable for guiding future platform enhancements.
Building on Stronger Foundations
What began as a minor navigation fix evolved into a significant rethinking of Mobi's core structure. The redesigned system empowered users with clarity and control, simultaneously providing Alta with a reliable foundation for continued growth. While centered on navigation, this project also revealed deeper insights into team workflows, invaluable for guiding future platform enhancements.
Reflections
Looking Back
Reflections
Looking Back
Reflections
Looking Back
Reflections
Looking Back
What I Took With Me
Sometimes, more clicks are better. At first, adding extra steps to the flow felt wrong. But watching users navigate made it clear that what I thought would bring frustration brought clarity instead. Even if it took longer, they preferred more steps over getting lost.
Sometimes, more clicks are better. At first, adding extra steps to the flow felt wrong. But watching users navigate made it clear that what I thought would bring frustration brought clarity instead. Even if it took longer, they preferred more steps over getting lost.
Sometimes, more clicks are better. At first, adding extra steps to the flow felt wrong. But watching users navigate made it clear that what I thought would bring frustration brought clarity instead. Even if it took longer, they preferred more steps over getting lost.
Sometimes, more clicks are better. At first, adding extra steps to the flow felt wrong. But watching users navigate made it clear that what I thought would bring frustration brought clarity instead. Even if it took longer, they preferred more steps over getting lost.
Redundancy isn't always a problem. During testing, I watched experienced users constantly rely on the nav bar. It acted as a shortcut that kept them moving quickly, even if it didn't fit the new hierarchical structure. It wasn't getting in the way of new users, so instead of removing it, we kept it; sometimes, familiarity is its own kind of efficiency.
Redundancy isn't always a problem. During testing, I watched experienced users constantly rely on the nav bar. It acted as a shortcut that kept them moving quickly, even if it didn't fit the new hierarchical structure. It wasn't getting in the way of new users, so instead of removing it, we kept it; sometimes, familiarity is its own kind of efficiency.
Redundancy isn't always a problem. During testing, I watched experienced users constantly rely on the nav bar. It acted as a shortcut that kept them moving quickly, even if it didn't fit the new hierarchical structure. It wasn't getting in the way of new users, so instead of removing it, we kept it; sometimes, familiarity is its own kind of efficiency.
Redundancy isn't always a problem. During testing, I watched experienced users constantly rely on the nav bar. It acted as a shortcut that kept them moving quickly, even if it didn't fit the new hierarchical structure. It wasn't getting in the way of new users, so instead of removing it, we kept it; sometimes, familiarity is its own kind of efficiency.
Real data reveals real problems. Seeing the broader data in Google Analytics was a wake-up call. Test sessions had shown me where some users thought they were getting stuck, but analytics showed me where the user base at large actually was. It was my first time using real-world navigation data, which changed how I looked at testing.
Real data reveals real problems. Seeing the broader data in Google Analytics was a wake-up call. Test sessions had shown me where some users thought they were getting stuck, but analytics showed me where the user base at large actually was. It was my first time using real-world navigation data, which changed how I looked at testing.
Real data reveals real problems. Seeing the broader data in Google Analytics was a wake-up call. Test sessions had shown me where some users thought they were getting stuck, but analytics showed me where the user base at large actually was. It was my first time using real-world navigation data, which changed how I looked at testing.
Real data reveals real problems. Seeing the broader data in Google Analytics was a wake-up call. Test sessions had shown me where some users thought they were getting stuck, but analytics showed me where the user base at large actually was. It was my first time using real-world navigation data, which changed how I looked at testing.
The right people bring out the right problems. Early on, it was easy to think that just getting enough people for testing would be enough. But when I started testing with real sales reps, support teams, and managers, it became apparent how crucial role-specific feedback was. A manager's workflow was nothing like a sales rep's, and it showed me problems I wouldn't have seen otherwise.
The right people bring out the right problems. Early on, it was easy to think that just getting enough people for testing would be enough. But when I started testing with real sales reps, support teams, and managers, it became apparent how crucial role-specific feedback was. A manager's workflow was nothing like a sales rep's, and it showed me problems I wouldn't have seen otherwise.
The right people bring out the right problems. Early on, it was easy to think that just getting enough people for testing would be enough. But when I started testing with real sales reps, support teams, and managers, it became apparent how crucial role-specific feedback was. A manager's workflow was nothing like a sales rep's, and it showed me problems I wouldn't have seen otherwise.
The right people bring out the right problems. Early on, it was easy to think that just getting enough people for testing would be enough. But when I started testing with real sales reps, support teams, and managers, it became apparent how crucial role-specific feedback was. A manager's workflow was nothing like a sales rep's, and it showed me problems I wouldn't have seen otherwise.