Overview
Team
Connect development team – SOTI
Tools
Figma, Mural, FigmJam, markers and whiteboard
Timeline
Whole design process - 4 weeks,
research - 1 week,
design and iterations - 3 weeks
Background
Advanced charts and table view of current design
SOTI Connect is a Mobile Device Management (MDM) Solution for Internet of Things (IOT) devices such as
mobile printers. It offers an advanced dashboard view allowing for quick, high level glances of all the
devices and their properties. Users may get informed about key device information by text and charts.
Users
IT Admin who needs to analyze and manage the state of a fleet of IOT devices.
Current situation
SOTI Connect is a Mobile Device Management (MDM) Solution for Internet of Things (IOT) devices such as
mobile printers. Connect offers an advanced dashboard view to users allowing for quick, high level
glances of all the devices.
Room for opportunity
The dashboard limits the ways information is presented to the user to mainly text or charts.
Problem
Connect's device dashboard is too rigid in it's layout and incapable of allowing IT Admin to separate device data into views that are organized in the best ways for them
Design Challenge
How might we allow IT Admin to analyze and manage their device fleet in a way that is easier to digest and control?
Solution
Allow users to partition device data and quickly, and efficiently switch between device views
Dashboards allows Connect Admin users the flexibility they need to create views
specific towards different use cases and around specific groups of devices. Admins are also able to
refine permissions so that they can manage who has read access and send those on the job only
dashboards that are specific to them.
Process
Stakeholder Interview
User requirements
Allow users to quickly build out dashboards depicting exactly the device data and actions the user will need to operate efficiently on the job.
Business goals
Boost revenue.
Technical constraints
Short time frame until dev done. Reframe from many new paradigms, and unique components increase costs.
Competitive Analysis
Looking at competitors to see best solutions to building dashboards and
configuring widgets. Expanding on the current acceptance criteria to consider additional
functionality that will add considerable value to users.
Builder environments have side panels to manage widgets, layers and widget properties.
Start a dashboard from scratch or use a pre-defined template.
Use of tabs to have mini dashboards inside a master.
Drag and drop, no code creation of dashboards.
Exploring User Flows
Dashboard creation
Viewing and managing dashboards
Iterate and test
Dashboard went through rounds of iterations with stakeholders to refine user experiences that were quick to build dashboards, and allows for a full range of analysis and commands to manage devices.
Development and Phase 2
During phase 1 planning, features were analyzed and those that
were of lower priority went into a phase 2. Once phase 1 was on it's way, designs for
phase 2 began.
Reflection
Working on this feature has shown me, again the importance of competitor
analysis, and brainstorming workshops.
With being given a loose acceptance criteria for this feature, pulling from other builder features
and relying on my teams opinions
and ideas all helped with the success of Dashboards.
