Saleos
Team Vision
At Saleos, we’re all about giving businesses the tools they need to truly understand their sales performance. Our goal is to create a sales dashboard which helps companies of all sizes turn their data into clear, actionable insights so they can make smart decisions and drive their growth
The Process
Empathize
client feedback and interviews
competitor analysis
Persona
Define
Define the Problem and User Needs
Ideat
prioritize and Brainstorming Sessions
Create flows
Prototype
Low-Fidelity Prototypes
High-Fidelity Prototypes
Test
A/B testing
usability testing
How did we figure out that we need these features?
Empathize, Client feedback and interview
Why Interview?
Interviews are effective for a sale dashboard user research because they provide detailed insights into clients needs and pain points.
Purpose:We want to better understand your experience with the current dashboard, the challenges you face, and how we can make the new features more useful for you.
Participants: 6 employees of the sales companies.
Questions: Current Dashboard Usage,Needs and Pain Points, Improvements and feature requests
Duration: 40-50 minutes per interview.
Tools: Zoom
Some of the questions:
Can you walk me through how you typically make decisions based on the sales data you see in the dashboard?
How do you analyze sales trends, and what do you find most difficult about identifying future opportunities?
When reviewing your sales data, how do you anticipate future changes or shifts in your performance?
Is there any information you feel is missing or that you have to go elsewhere to find when using the current dashboard?
How do you set sales targets or goals for your team, and what tools do you use to monitor progress?
what improvements would make that process easier?
Findings from user research:
Common Challenges with Current Tools:
Empathize, create a Persona
To understand our users better, we gathered feedback from people in various sales and financial roles. From this, we created five different personas, each representing a unique role within companies that use sales dashboards. These personas include a Sales Manager, a Financial Analyst, a Marketing Specialist, a Sales Coordinator, and a Chief Revenue Officer. Each one has specific challenges and needs
Empathize, Competitor Analysis
Features
HubSpot Sales
Sales pipeline management and tracking
Reporting and analytics
ntegration with HubSpot’s CRM and marketing tools
Strength
User-friendly interface
Strong integration with HubSpot’s marketing platform
Weakness
Limited advanced analytics compared to more specialized tools
Less customization for reporting and forecasting
Zoho CRM
Sales forecasting and analytics
Customizable dashboards and reports
Good customization and automation capabilities
Occasional performance issues with large datasets
Interface can be less intuitive for some users
Microsoft Dynamic
Sales forcasting
Customizable dashboards and reporting
Highly customizable to fit various business needs
Complexity in setup
Salesforce
Comprehensive CRM with sales forecasting and analytics
Customizable dashboards and reports
Robust reporting and analytics tools
Complexity of features can be overwhelming for new users
Customization requires a steep learning curve
Define, user needs
Ideat, Prioritize and brainstorming
In the Prioritize phase, we ranked features based on their importance and value to users. Features like sales growth forecasting and customer acquisition cost forecasting were prioritized first because they addressed the most critical user needs, while more complex features were planned for later.
Ideat, user flow and user story
In the Ideate phase, after several brainstorming sessions, we identified the key features needed to address user challenges.
The main challenge:we discovered that each feature required its own specialized machine learning or AI model to function effectively.
with the help of the product owner, we provided user flows and user stories based on each feature and solution.I want to mention that this state and design state was on the same time and developed base on each other.
Design and prototype
Test - useability testing and A/B testing
we conducted useability testing and A/B testing during the process as well
in useability testing, we evaluated different scenarios:
such as:
-
Find the forecasting of a sale for a specific product in a given region.
Purpose: Evaluate the ease of using filters (product and region) and reading forecasting data.
-
Compare sales growth between two products.
Purpose: Assess how intuitive it is for users to compare data across multiple products.
-
Analyze the CAC for the last quarter.
Purpose: Check how quickly users can find and interpret CAC data
.
Task Completion Rate for most of the tasks was 80%. (it had more details per task)
we also gathered information like Common pain points and user feedback.
we iterated and re-designed some of the items and then we had a plan for the next round of testing.
Results and outcomes from this project:
