17. WHAT THIS HAS LED TO
• Mutual-dependent relationships
• Insulated from competitive pressure
• Adversity to change (aka “innovation”)
• “Jack of All Trades.. Master of None”
• Platforms and products that mirror the
complexity of the organization(s)
• Challenges of compliance, governance, scale,
security and access
• Later adoption of consumer-grade experiences
• Struggle between “power” user efficiency vs. new
user simplicity
19. WHAT IS ENTERPRISE
SOFTWARE?
• “..software used to satisfy the needs of an
organization rather than individual users..”
• ..The software is intended to solve an enterprise-
wideproblem, rather than a departmental
problem..”
Buyer = Organization
24. WHAT THIS CAN LEAD TO
• Multiple role-based UI
• Visual “Eye Candy” Dashboards
• Usable/functional products that aren’t
marketable
• Over support of too many device platforms vs.
majority of users
• Features that sell the product but aren’t used
• Burden of legacy versions and users
27. ACCORDING TO WIKIPEDIA
• “..a control panel..”
• ..page which collates information about a
business..”
• “..a management tool used to get an overview..”
• ”..system for hosting mini-applications known as
widgets..”
• “..a tool for displaying complex sets of indicators
in a user-friendly format..”
46. TO MAKE PHONE CALLS
WE NEEDED DASHBOARDS
TO MANAGE PROJECTS
WE NEED DASHBOARDS
47. TO GO TO ANOTHER PLANET
WE WILL NEED DASHBOARDS
48. CORE TENANTS OF
DASHBOARDS
• Centralized Control
• Monitoring “At a Glance”
• Analysis & Correlation
• Alert and Notify
• One-click (touch) away
49. COMMON UI MODELS
• Layout: Modular (Widgets)
• Navigation: Drill to Detail
• Navigation: Quick Links
• Visuals: System Status & Stats
• Visuals: Charts and Graphs
COMMON TYPES
• Operational
• Strategic (Executive)
• Analytical
• Hybrid
50. DASHBOARD DESIGN TIPS
• Simpler the better
• Tabs and cards are key
• Think gateway rather than destination
• Visualize something beyond eye candy
• Choose space wisely
• Modularity can lead to mediocrity