Home Explore Blog CI



kubernetes

4th chunk of `content/en/blog/_posts/2017-01-00-Kubernetes-Ux-Survey-Infographic.md`
114f937d2e945ddb1fe10cd2aa9540ee920dd9ef6a5109d80000000100000324
![](https://1.bp.blogspot.com/-gGKQKRwgOto/WHPgEdVMqQI/AAAAAAAAA5k/MiTVQtKLuHkAMmSjpvAsmiBezAdQV4zCwCEw/s640/feature-priority.png)](https://1.bp.blogspot.com/-gGKQKRwgOto/WHPgEdVMqQI/AAAAAAAAA5k/MiTVQtKLuHkAMmSjpvAsmiBezAdQV4zCwCEw/s1600/feature-priority.png)



In building Dashboard, we want to continually make alignments between the needs of Kubernetes users and our product. Feature areas have intentionally been kept as high-level as possible, so that UX designers on the Dashboard team can creatively transform those use cases into specific features. While there’s nothing wrong with “[faster horses](http://www.goodreads.com/quotes/15297-if-i-had-asked-people-what-they-wanted-they-would)”, we want to make sure we’re creating an environment for the best possible innovation to flourish.

Title: Aligning Kubernetes Dashboard Features with User Needs
Summary
The Kubernetes Dashboard team aims to align feature development with user needs while fostering innovation. Feature areas are kept high-level to encourage UX designers to creatively translate use cases into specific features, moving beyond simply providing 'faster horses' to create truly innovative solutions.