7 ms·
> And you can understand why it happens! Developers love to develop; marketers want new stuff to market. Adding new features, shipping new code, is fun and exci
by crazygringo 4y ago
> And you can understand why it happens! Developers love to develop; marketers want new stuff to market. Adding new features, shipping new code, is fun and exciting. Merely maintaining a successful app? Bleah. So dull. That drives a lot of feature creep, right there.
> The thing is, we can usefully flip this concept on its head! What if more developers developed a sense for the “maximum” number of things a product should do — and stopped there?
I'm sorry, but the author misunderstands entirely the reason for feature creep. It generally has nothing whatsoever to do with "fun" or developers "wanting to develop" or marketers "wanting to stuff to market".
Rather it has to do with segments of customers genuinely needing a given feature, and they won't buy the product unless it has the feature.
There's the old quote about how 80% of the people only use 20% of the features -- but then the punchline is that they're all using a different 20%.
That screenshot of all the Word toolbars? Guess what. There are different user segments that actually use each one of those toolbars. Yup.
So the idea that there is a "maximum" number of things a product should do, that can be known in advance, is sheer rubbish. If you're a business and you want to make money and you'll profitably sell to more customers if you can build in a new feature, then you do it.
Why would any company restrict itself to an arbitrary "maximum" and leave money on the table...?
- coder-3 4y agoYep came here to say this. The article is incorrect in the diagnostic and thus the prescription
- lukemercado 4y agoI've been exploring this concept a bit at my startup for our B2B offerings. Where I've landed is a robust set of feature toggles that Sales and Account Management configure. Within the confines of your Microsoft Word toolbars analogy; since the software we offer is similar to SaaS and delivered via a web browser this effectively means we can "hide" the toolbars that the client isn't interested in. This is all pretty early days, but my hope is that we can iterate the core "have feature toggles" concept to the point where we have the ability to turn functionality and function accessibility on across many verticals. I hope that one day internally we can configure things a per-customer and per-user-persona basis. I also hope that one day we can expose some of those switches to admins and/or everyday users, possibly with paywalls or other strictures. We'll see where it all lands :D
- ako 4y agoHow does that scale for enablement, training materials and documentation? Will be very confusing for users if the material shows things that are not in his UI.
- danielmarkbruce 4y agoIt's not just about the users. As the software becomes more complex it's hard to change/iterate on, hard to find bugs/fix things, hard to reason about etc. And the difficulty seems to rise non-linearly.
- mcbishop 4y agotl;dr: giving users the ability to show / hide some features.
- bruce511 4y agoWe've been doing this for 25 years in our desktop software. Every new feature is behind a checkbox on a "features" screen. This screen is in the program, so users can turn things on and off, but typically its set by one of our staff during the installation phase [1]. The upside is a clean interface which helps during training, support, and day to day use. The primary downside is discoverability. Occasionally customer needs change and some assume "the software doesn't have that feature" rather than call us, or check online. That's a problem best solved with good communication, but that can never be perfect. [1] this is in the B2B space, and has a proper sales, install, support cycle.
- notjoemama 4y agoHow about maximum viable product definitions for go to market? I've worked with PMs that have engineering build-build-and-rebuild delaying release until they feel it is "good enough", or what I think is really going on, "perfect". Then it gets into the hands of users who don't care about most of what the PM felt was important or necessary. In those cases (what I call "Steve Jobs syndrome) it would've been nice to say the product was limited to doing x, y, and z for the release.
- notjoemama 4y agoI forgot to mention, the point is to limit the cost of the product before getting valuable feedback that ought to direct the future of the software. It's also not fun toiling away on a product the end users never use because it only made sense in the PM's mind.
- kneebonian 4y ago> So the idea that there is a "maximum" number of things a product should do, that can be known in advance, is sheer rubbish I disagree, I think the Unix philosiphy solves the problem. You build simple tools that do one thing, and do that one thing well, but you make it easy for the tools to work together and then you can have pieces that do one simple thing while still serving needs. When new needs come up that aren't addressed by current tools you simply put together another simple tool that does that.
- wildrhythms 4y agoI don't think this adequately addresses the counterexample of the Word toolbars. Sure, there's Excel, but what if I want the tabular data to live in my Word document? Now the Microsoft engineers are building a whole secondary table editing system into a word processor...
- shakna 4y agoIf everything is modular, you can copy any feature between the various parts of your office applications. You've got a plugin doing one thing, and a host whose one thing is bundling all of those one things together.
- jimmaswell 4y agoThis could just call Excel with COM
- kevingadd 4y agoThis is one of the things that motivated the creation of OLE and COM, so that you could embed an entire Excel spreadsheet into a Word document.
- invalidname 4y agoThat's also how Word solved the problem with the toolbars. It hid the functionality using the ribbon and added plugins. Unix is a monster in terms of features if you look at it as a whole. It's just modular so it can solve all problems.
- 4y ago
- LAC-Tech 4y agoAlso wouldn't most devs much rather fix bugs in an existing app than add features? Piling more chairs on top of each other to get features out the door can be demoralizing. You know it's going to collapse under its weight eventually, and you're just speeding the company along to The Big Expensive Rewrite. But fixing bugs? An actual chance to make things better? That is satisfying.
- emodendroket 4y ago> Also wouldn't most devs much rather fix bugs in an existing app than add features? No, for a few reasons: 1) it's often tedious work 2) often the bug has been around a long time and nobody's really noticed or cared, so how important could it be? 3) organizations rarely reward this work.
- bruce511 4y agoI quite like fixing bugs. It's a different mental challenge to truly understand what is going wrong, often something that's really subtle. While individual fixes are often unnoticed, the overall effect is profound. Users are happier, support staff are more confident, and programmers are able to build the next layer on a firm foundation. I agree bug fixing my code is more enjoyable to bug fixing other people's code, and I agree that most programmers resist the former and hate the latter. But for me, bug-fixing foreign code, is one of the truest tests of skill.
- squeaky-clean 4y agoI love bug-fixing other people's code for some reason. I often get nerd-sniped by another team in our slack talking about some bug they've encountered in their project(s). I kind of wish that could be my full-time job. I suppose that's what some fields of consulting are.
- OJFord 4y agoIt's only tedious work if what you enjoy is cranking out another CRUD feature. Personally I prefer the thinking, reasoning, tracking down, supposed 'tedium' that comes with bug fixing.
- usea 4y agoScope and feature creep has nothing to do with customers. It happens in all creative endeavors, most of which do not have anything like customers. It happens in art, music, hobby programming, event planning, etc etc. Everything. If you sit down to try to write a program that no one will ever see but yourself, you will have to fight against feature creep. It comes from the creators themselves. It's basic human nature to find it easier to desire things than to restrain oneself.
- fncivivue7 4y agoIt's not the only cause but empire building[1] is a very real phenomenon. Maximum viable features is a very interesting concept but it's just that, a concept, nobody says you have to stick to it, it can just be a tool in your toolbox to limit scope creep. One thing I don't have too many of is tools to limit scope. > the punchline is that they're all using a different 20%. You could try creating different products. 1. https://www.investopedia.com/terms/e/empirebuilding.asp https://www.investopedia.com/terms/e/empirebuilding.asp
- rapnie 4y agoI liked some of the takes on building Minimum Lovable Product (MLP) instead. Retaining the focus on why people would want to use it, and with your vision for the product central. https://news.ycombinator.com/item?id=30799083 https://news.ycombinator.com/item?id=30799083
- bruce511 4y agoAs an example I offer up a review of an Open Source Word-Alternative back in the early 2000's. The reviewer liked the product enough, but slated the fact it didn't have a word counter. Now, I for one, have never cared about the number-of-words in a document. But, it turns out, journalists tasked with writing a 2000 word review _really_ care. With great popularity comes great variability, and more "corner cases" matter. Incidentally the solution is not fewer features, but better UI. Notice thats a very old screenshot of Word. Whereas Word to day looks very different, has the same (or greater) feature set, and a much more streamlined interface. The much-hated-on ribbon bar is actually a better interface than endlessly-deep menus and a million toolbars.
- amadeuspagel 4y agoIt's not only a very old screenshot, it's also a screenshot you'd never get by default, you'd have to manually activate all these toolbars.
- vanviegen 4y agoHow can you claim a user interface is 'better' while in the same sentence referring to the fact that most people hate it? People don't know what's good for them? I'll have my Word with endlessly-deep menus, combined with discoverable keyboard shortcut and Ctrl-shift-p please!
- anonymous_sorry 4y agoI suspect people hated the ribbon when it was introduced because it was an unexpected change, forcing users to learn something new when they just wanted to be doing actual work. I don't think most people hate it any more.
- tartoran 4y agoIm surprised my passion with witch im hating it hasn’t ceased a bit though it’s only when I use Word and I forget about it when I close it. Some things don’t make sense to me still, it feels dumbed down and more inefficient.
- bryanrasmussen 4y ago>Rather it has to do with segments of customers genuinely needing a given feature, and they won't buy the product unless it has the feature. there is another reason feature creep happens for certain categories of products, which is regulation. If a law is passed mandating industry X needs to support Y that feature will be added for any product wanting to sell to the market that has mandated the feature. any analysis that misses these kinds of real world scenarios is not that interesting.
- Sevii 4y agoThe problem is that each additional features imposes costs on those users who don't need it. An example would be JIRA. JIRA is designed to have every feature possible. But as a cost it is hellishly slow and is hard to find anything in. Each additional 20% of the features you support cuts the UI and technical effort that can be put into the other 20%s of features. The end result is the standard big corporate apps that feel heavy weight despite doing what feels like a pretty simple thing. It makes sense for companies to do it. Because the cost is born by the consumers.
- FpUser 4y ago>"But as a cost it is hellishly slow and is hard to find anything in" There are examples to the contrary. CAD products I think are way more complex than this JIRA abomination but are not slow at all. And for what it worth I went from knowing nothing to producing complete design of a relatively complex piece of equipment (main assembly, all individual parts etc in a form accepted by factory) in less than a month using Solidworks. This says something about quality of this piece of software. Out of fun when I had nothing to do I tried to repeat the design in FreeCAD - never fucking again. So I think the problem is not the amount of features (the more the better). It is just very hard to design proper ergonomic GUI and workflow.
- 7952 4y agoThis definitely applies to autocad though! A lot of the better products are perhaps a reaction to the bloat of older products.
- tsimionescu 4y ago> JIRA is designed to have every feature possible. If only that were true. There are several long-requested features that they refuse to implement on "agile purity" grounds (such as the ability to split a story while also distributing points, so you can mark it as partially complete in a sprint, or at least leave behind completed subtasks in the old sprint).
- xwolfi 4y agoCounterpoint is IntelliJ, a pleasure to use, more feature than Eclipse.
- sriku 4y ago(unsarcastically) I'd be pissed if a computer manufacturer placed an arbitrary limit on what I should be able to do with my computer.
- continuational 4y agoBecause they might get outcompeted by 5 different products that aren't 80% bloat?
- rwmj 4y ago"Bloat" means what exactly: Download size? Slowness to start? I suspect you really mean complexity of the interface, but with careful design its possible to hide the complexity and provide various easy entry modes. Anyway no one uses an alternative to MS Word / Office 365 because the alternative has fewer features.
- shadowfoxx 4y agoI agree with you on your points but the quote even contradicts itself here. Adding new features is fun and exciting but feature creep is bad? What is feature creep if not new features? (Well new features + the idea that we're adding more features than we're thinking about their implementation and/or before the app does what it set out to do in the first place)
- epolanski 4y ago> Why would any company restrict itself to an arbitrary "maximum" and leave money on the table...? Because when there's too much options and features users are going to be overwhelmed. Also, feature creep has nothing to do with developers wanting or not wanting, those are product decisions. I saw that in the past with an ecommerce, we had a good portal, then stakeholders in corporate that need to justify their salary started shoving more and more stuff, now what was a simple search-find-pay has become interrupted and overwhelmed with features and information.