Case study context
Enhancing Creation, Response, and Post-Incident Management
End-to-End Incident Optimization.
Company context
Ambient.ai analyzes camera footage to filter out irrelevant content, allowing security professionals to focus on critical incidents.
Enterprise SaaS, Physical Security, Computer Vision
Project overview
——
RESULTS
33% increase in incident creations.
TEAM SIZE
7
TIMELINE
5 months
Problem context
Customers must complete 7 key steps before receiving their first alert.
1
Create an account
2
Add
a site
3
Add an appliance
4
Discover cameras
5
Paint
streams
6
Select
alerts
7
Receive first alert!
Design objective
Currently, onboarding is external, disparate, & time consuming.
Four key onboarding steps were scattered across three different platforms, leading to inefficiencies and user frustration.
Creating an account
Adding cameras
Annotating streams
Review & scheduling alerts
OBJECTIVE
Unify onboarding steps into 1 product platform.
The design process
Iteration Highlights
Improving batch task usability
Before
The current process is repetitive, time-consuming, and lacks considerations that make batch tasks manageable at scale.
—repetitive modal workflows led to fatigue after annotating ~10-15 streams.
After
impact
Alert accuracy improved by 24%.
impact
78% task completion rate.
solution HIGHLIGHTS
A visual progress indicator.
Dynamically updated configuration statuses.
Adding an instructional video.
Navigation
Before
While the menu is collapsible, it would be at the cost of users losing overall context, specifically around which step they were currently on and what steps remained.
After
A persistent navigation experience without losing context.
solution HIGHLIGHT
Updated navigation component
Design solution
A standardized data collection experience with step-by-step guidane that introduces real-time visibility into various steps of the onboarding process.
Impact
78% reduction in onboarding time.
Weeks-month long process.
1
Create an account
2
Add
a site
3
Add an appliance
4
Discover cameras
5
Paint
streams
6
Select
alerts
7
Receive first alert!
Days-week
Customers can start using the product in a matter of
days instead of weeks.
Learnings & takeaways
The importance of designing for scale and usage beyond first-time setup.
Breaking designs into crawl, walk, run paradigms.
ie: manual → automatic & internal tool → self-service