The design of DevOps
summary
A GitLab navigation redesign goes from a rushed sidebar-to-hamburger change that provokes instant backlash to an evidence-driven fix: three rounds of moderated testing, two prototype variants built in Framer prototype, 24 participants total (24 users), prioritized issue-by-issue work, then a staged rollout behind a feature flag in 9.4 and full switch to the new UI in 10.0 default. Results show clearer location, faster icon discovery after tooltips, lots of purple hate, and overall user acceptance.
AI-written summary · about
chapters (14)
- 0:00Start
- 1:43The Goal of Devops
- 3:06Skills Needed To Be a Devops Engineer and the Skills Needed To Be a Ux Designer
- 3:55The Problem Maintaining Simple Intuitive Navigation
- 12:20Moderated User Testing
- 12:35Icon Recognition
- 13:16High Level Issues
- 20:35Theme Options
- 21:18Important Takeaways
- 27:19Version Control
- 32:16User Testing
- 33:14Surveys
- 33:45Customer Advisory Boards
- 34:38Tools or Techniques You Use for Ui Design Can Be Used for Cli Design
related talks
27mFrom Waterfall to Agile to DevOps with GitLab
19mCrossing the Divide: How GitOps Brought AppDev & Platform Teams Together!
19mAll-Remote UX at Scale
21mDriving Cultural Change to Improve Software Development and CI/CD
31mGitOps, the Final Frontier: Proposing, Promoting, and Reverting
46mFrom 1,000 to 5,000 Users: Scaling GitLab Without (Too Much) Pain
31mDevOps 2.0 - Bigger, Badder with More Automation
22mHow Customers Helped Shape the Future of Slack