4 ms·
The best way to get a lean streamlined application is by eliminating features. Right, but let's be clear about one thing: If users had a say in which features
by fauigerzigerk 17y ago
The best way to get a lean streamlined application is by eliminating features.
Right, but let's be clear about one thing: If users had a say in which features were included, the number of features would be huge, and these features wouldn't all be just variants that could be educated away. They are real needs. So, not having these features means not to satisfy some user requirements.
Sometimes I get the feeling that we kid ourselves into believing that if we create a super clean, consistent UI that doesn't inundate users with features they don't use, we have somehow succeeded. Most of the time we have not, because for each individual user the application most probably lacks very important functionality.
A user who repeats the same laborious steps day in day out in order to achieve something with my software will gladly accept any number of useless features in his face just to get that one feature that makes his/her work 10 times more productive.
I'm afraid UI/feature minimalists will never understand why on earth so many people will pay $650 (or whatever) for MS Office, the mother of all feature monsters.
- TomOfTTB 17y agoRight, but let's be clear about one thing: If users had a say in which features were included, the number of features would be huge, and these features wouldn't all be just variants that could be educated away. They are real needs. So, not having these features means not to satisfy some user requirements. Not necessarily. Interaction Design has always focused on profiling users and then using those profiles to expose the functionality that user needs while obscuring the functions they don't. So "eliminating" a feature can just mean having the user set up what features they will use before hand and then using that info the streamline your UI (clearly you'd want some way to change those preferences but that's another discussion) I think a lot of UI design has gone backwards by ignoring this insight. To give one example, Toolbars have gotten a bad name because developers used them badly in the past. But they had a good purpose which was to allow users to un-clutter their interface by hiding functions they don't use. Now we have Microsoft pushing the unwieldy, homogeneous Ribbon which throws all those confusing features at the user. But the bottom line is I don't think you need to go as far as taking out a feature just to eliminate it from the sight of a user who won't use it
- fauigerzigerk 17y agoSo "eliminating" a feature can just mean having the user set up what features they will use before hand Sure, but to do that the feature must exist in the first place. The author of the original article makes a distinction between eliminating a feature and hiding it. What you suggest is a clever way of hiding a feature. I'm ambivalent about the idea of hiding a feature based on usage. Microsoft had that idea of hiding menu items that were not frequently used. I don't know anyone who liked that. I always disabled it because I didn't like my UI to change all the time. If I use a feature rarely, I still want it to be where it was last time, not move around until it's seven nested dialog boxes away.
- TomOfTTB 17y agoYou're right about the article I'm just disagreeing. Programs exist to solve user's problems, UI exists to make it easy for the user to discover how to use a program to solve their problem. So UI is supposed to serve the functionality not the other way around. Which is why I think making a program less capable of solving the user's problem based on UI consideration is backwards. As far as the hiding, I'll agree the "menu hide" trick in office sucked but that's sort of my point. Microsoft did it badly so there's this assumption it can't be done. But figuring out how to do it is what UI design is all about. At least, that's my opinion.
- rimantas 17y ago> They are real needs. So, not having these features means not to satisfy some user requirements. Not necessarily. Some are needs, some just wants. Software should offer solution to user's problem, not features. Often features are wanted just because user has a particular vision of solving his problem which requires these features, but that does not mean that there is not more elegant way to solve the problem with less features. > I'm afraid UI/feature minimalists will never understand why on earth so many people will pay $650 (or whatever) for MS Office, the mother of all feature monsters. I am afraid many who paid for MS Office won't know themselves. And I bet many of those still use spaces instead of tabs in Word :(
- ahoyhere 17y agoThe thing that people get wrong about the idea of "less is more" is that they choose the wrong features to eliminate. They don't have a strategy, except that they will do and be less. (And it's often the HARD things to design and build that they leave out.) They focus so hard on elimination, that they don't add back things that the other apps do not have. AND they think that they will still have universal appeal. They don't consciously say "OK, we are going to remove these features, because we don't want to serve this type of customer... which will make us more appealing to another type of customer." They just think that less === more, and that's it. Just like any dogma, people cargo-cult it. They use it as a mantra without understanding why. FWIW, my app was one of the ones featured -- Freckle Time Tracking (http://letsfreckle.com/ http://letsfreckle.com/). They wrote: "Freckle just makes you want to keep track of your time. The conveniently condensed interface shines with energetic color, turning a routine task into something fun." And that, in a nutshell, is much of what we tried to achieve with Freckle. Our key feature? Take away the pain. Take away the guilt. Make it effortless, and dare I say it, fun. We don't have everything, by choice. Do we have fewer features than Harvest? Damn straight. We don't do time sheet approval. We don't do pre-approved tasks. We don't do any kind of extreme permissions control.. anyone in the account can create new projects, for example. Our software is built for small teams with a flatish hierarchy, not for traditional iron-fist-control businesses. That is LESS with a purpose. For our customers, that's not a "lack of features" -- it's a downright BONUS. Because they have a small team, or are by themselves, and so having to set up tasks in advance (like in other software) actually reduces their ability to work effectively. On top of all those removals, we've added back things that nobody else does. Time entry on every page. The Pulse, which helps you identify your work patterns. Saveable reports. Even most of the people who cancel their accounts write us that they love the app and they're sorry they have to cancel. So I certainly feel we're doing something right. We don't want to be Microsoft Word. Our goal isn't just to make gobs of money, or even dominate the niche. We want to build software that fits our philosophy and makes people happy. We have a smaller audience, yes, but it's an audience who agrees with our principles.
- Pistos2 17y agoJust wanted to mention that I am a happy Freckle user. Good work. Just add in the ability to mark items paid or unpaid, and Freckle would be just about all I want out of a time tracker. (With paid/unpaid, I would be able to see what I can or want to invoice next, considering various subprojects proceed on different timelines.)