3 ms·
This is very relevant to my current project. We're building a dashboard that's fed with very diverse data, could allow you navigate and examine that data in ton
by mcv 7y ago
This is very relevant to my current project. We're building a dashboard that's fed with very diverse data, could allow you navigate and examine that data in tons of different ways, and we could make it incredibly configurable.
But we're also aware that our users are not power users. It first needs to be understandable to use it. If we throw a ton of features at them, because they'll drown in them and then not use it. And the prospective users are the decision makers here: we're building this for upper management, and they have no idea that they should want this, so we have to make this attractive, easy and pleasant to use. When they see it, they have to want more, not be put off by incomprehensible complexity.
So we're holding back on features. I know a million features I could add to this, and I really want to, but every time the question becomes: how will they access this? How will they understand what this does? So we're careful in adding features, and put a lot of time into getting the interface right. It doesn't yet have all the features I want it to have, but hopefully all the features it has will be features they understand and want to use. And then we'll add more based on what they need, not on what we think we can offer, because that's going to be way too much.