Designing interfaces that don't suck when your customers scale!
summary
Octopus Deploy evolves lessons into concrete UX fixes: a dashboard that works for ten projects becomes unusable at hundreds or thousands because of horizontal scrolling and crushed status indicators; solution paths are summarize or divide and conquer, e.g. aggregated charts, a project-variable table with search and filters and sort, and a “show” pattern that pushes data then lets users chop it. Deployments and dashboards improve but some screens remain a work in progress for very large customers.
AI-written summary · about
chapters (11)
- 0:00Intro
- 0:11Designing Interfaces That Don't Suck When Your
- 2:04Customers come in different sizes
- 2:23Small, Medium and Large
- 4:50How do you find problems in your apps
- 7:05Designing interfaces for too much data
- 7:41Dashboards
- 8:33Data visualisation
- 9:22Show pattern
- 10:32Tables
- 11:19Summary
related talks
25mJurassic UX: Design Best Practices for Legacy Software
18mBeyond the Hype: Facing Micro Frontend Challenges in Large-Scale
35mHabits for building a scalable UI
35mThe elements of scaling
41mDesignOps 2.0 – Scaling Design
31mIncremental Design - A conversation with a designer and a developer
46mDigital scale-up architectural patterns
25mFrom Scratch to Production-Ready: Creating Dashboard Visualizations