Reporting for Researchers
Product
SaaS App
Used to: Analyze survey data. Used by: People practicing market research
Team
Product design lead, product manager, full stack
This simple app emerged from a mission to innovate after several companies combined into one. With the new team in place, I was focused on the reporting segment, an important piece in the research continuum and a business ripe to grow.
I acted as a lead designer to create this 0-1 experience, We leveraged a legacy app IP and user data and aimed to simplify, get straight to insights and lay a foundation for analytics to grow.
Impact
Internal Conversion V1
14%
External Conversion
9%
Adoption
70%
Users who came back to use the tool at least 3 times in a months time.
Process
-
![]()
Competitive Analysis
From watching videos, reading docs, and actually working with various competitor tools the hunt for the best features and execution ensued.
-
![]()
Job Mapping
Workshops with stakeholders yielded job maps and information architecture to help understand this landscape. Some reporting level jobs our systems needs to handle: Inject data, create data views, and create report templates.
-
![]()
Guerilla Testing
I leveraged internal and external users and ran iterative qualitative usability studies to validate needs and interaction design
-
![]()
Survey Analysis
I built surveys, ran test panels, and used that data for the design and development process.
Deliver
Connected
A landing and projects page connected apps along the research continuum. Users can navigate between tools for sample, survey and reporting.
Topline
Researchers or programmers have the ability to watch the data come in. At this time, an intervention can occur to address problems with screening or programming.
Views
Researchers can change visual modes and calculations to help grasp the data, and then typically present the data for product and/or business changes.
Segmentation
Users can easily add columns or segments and instantly find insights via automatic statistical testing.
