I wonder of the 80% how much would they care for it if they had time to discover and learn it. And how much they really just will never care (unless their role / conpany changes).
Companies frequently moan about "re-training", but in my experience users of e.g. Word, or Excel don't need re-training, they need training. A large number of people how "Knows Word", can't use any of the feature beyond changing the font and font size, not even the "headings".
For product like Microsoft Office (or whatever it's called these days) 20% is ludicrously high. I'd guess more in the 1% - 2% range. Especially Word is way to complex for the needs of most people, Wordpad covers the needs of most home users. I also thinks that's where the recentment for the remaining features come from. It's not that there's some number of feature hiding in a corner that's the problem, it's that almost the entire application is "useless".
> A large number of people how "Knows Word", can't use any of the feature beyond changing the font and font size, not even the "headings".
“Knows Word” and “familiar with Windows” are boilerplate résumé spam to match the keyword selection. No one actually is expected to follow up on those bullets.
Users are complete human beings, and their interaction with your product is a tiny slice of their life. They use your product to solve problems that they have. If the 80% of your product that they aren't using doesn't relate to their problems, they won't use it, even if they know that it exists. For example, I've never used Microsoft Word's mail merge function, even though I've known it exists for probably twenty years, simply because I've never needed to send out a form letter to a whole bunch of people.
Sometimes, there is indeed a new feature that could solve a problem that they have, but they don't know it exists. I've seen a lot of pop-ups in software that try to tell me about new features, but I never read them, because I'm always trying to do something else when they appear. Emailed newsletters also don't work, because the marketing people who design them always make them look like advertisements.
Finally, many computer users are deeply incurious about their computers, and are often too scared of breaking something to try an unfamiliar feature.
> Instead of fighting feature bloat, you can embrace the idea that your software will be used in ways you never imagined.
Which is why interoperability is the most important feature you can embrace.
I get the abstract sense reading this article that the main problem is software and sometimes version specific file formats. I don't mind cobbling three tools together, it's just that the tools seem to mind being used as part of a pipeline.
I guess most people don't care about our applications at all. They care about how it solves a problem they want or need to have solved.
That is the starting point. You can get people to care if your application becomes a great tool for the things they want to do. And good tools don't get in your way.
> Slack works similarly with its integrations. Discord does this with bots and servers. The platform provides the foundation, but users craft their own experience on top of it.
Not really the articles core point, but to me at least, those two products are full of loads of stuff I don't want!
I thought VS code was a good example, I'm curious about if anyone has other examples that they think do modularity well?
There's a marketing corollary that is called the Modified Pareto. Briefly that it's not 80/20 but 60/20. That is 20% of the heaviest or power users will consume 60% of the product. But that means the 80% will actually consume 40%. That's no longer small enough to ignore, so you have to cater to the light or infrequent user.
This is a good argument for the Unix philosophy's "do one thing" to avoid the bloat the author describes. E.g. vi, sendmail, and some bash for Word's mail merge. Or Emacs and some lisp. But then the onus is on the user to compose these tools to something that solves their particular problem.
They also care 0% of how it was written, unless it stands on their way, hence why nowadays we have applications of various quality levels, when looking under the hood.
I didn't read the article but in my experience, 80% of the application are parts that you rarely touch, config stuff and "LEFT JOIN" stuff.
There is always one or two parts where all data comes together and that is the heart of your application. Yeah those are the parts your users care about and pay you to make.
> Kagi didn't need to beat Google for everyone; they just needed to serve that specific slice of users perfectly. They focused on being the ideal 20% for people whose 20% Google was ignoring.
Yes, this is actually a critical insight into how to find product-market fit
I like to call this approach MISS (MISS – Make It Stupid, Simple) or better:
Make
It
Stupid
Simple,
To
Experience
Revenue
= M.I.S.S.T.E.R.
i.e. keep removing features until the idea fits in your head, the value can be explained concisely to a small group of people to whom it'll just 'click'.
This is why AI development will be huge in the “Buy vs Build” space… Businesses (with a capable tech team)can build the 20% of the SaaS they need, and stop paying for the 80% every single month.
I kinda miss the unix philosophy... one tool for one job. A PDF reader should read PDFs, there's no need for it to have its own (possibly paid) cloud service and an AI chat bot.
I do get why some integrations are beneficial (eg. office software with text editing, spreadsheets and a database, so you can generate eg. letters with data from a database, etc... but every service needing its own cloud and adding a useless AI chatbot is just a useless overkill for me.
But then you start selling to Enterprise and everything changes. Because one missing "hygiene feature"* can tank the the whole deal. And every Enterprise has a different one.
*like a toilet. It needs to be there. You use it 3 minutes per day. If it is not there, the house is uninhabitable.
52 comments
[ 1.7 ms ] story [ 59.5 ms ] threadFor product like Microsoft Office (or whatever it's called these days) 20% is ludicrously high. I'd guess more in the 1% - 2% range. Especially Word is way to complex for the needs of most people, Wordpad covers the needs of most home users. I also thinks that's where the recentment for the remaining features come from. It's not that there's some number of feature hiding in a corner that's the problem, it's that almost the entire application is "useless".
“Knows Word” and “familiar with Windows” are boilerplate résumé spam to match the keyword selection. No one actually is expected to follow up on those bullets.
Sometimes, there is indeed a new feature that could solve a problem that they have, but they don't know it exists. I've seen a lot of pop-ups in software that try to tell me about new features, but I never read them, because I'm always trying to do something else when they appear. Emailed newsletters also don't work, because the marketing people who design them always make them look like advertisements.
Finally, many computer users are deeply incurious about their computers, and are often too scared of breaking something to try an unfamiliar feature.
Which is why interoperability is the most important feature you can embrace.
I get the abstract sense reading this article that the main problem is software and sometimes version specific file formats. I don't mind cobbling three tools together, it's just that the tools seem to mind being used as part of a pipeline.
The dream of Unix is a tricky thing.
[0] https://littlegreenviper.com/the-road-most-traveled-by/#pavi...
https://www.joelonsoftware.com/2001/03/23/strategy-letter-iv...
https://www.joelonsoftware.com/2006/12/09/simplicity/
That is the starting point. You can get people to care if your application becomes a great tool for the things they want to do. And good tools don't get in your way.
Not really the articles core point, but to me at least, those two products are full of loads of stuff I don't want!
I thought VS code was a good example, I'm curious about if anyone has other examples that they think do modularity well?
This is actually a lot of fun to discover.
No I didn't read the article but the punchline is trivially obvious.
https://marketingscience.info/value-paretos-bottom-80/
There is always one or two parts where all data comes together and that is the heart of your application. Yeah those are the parts your users care about and pay you to make.
Yes, this is actually a critical insight into how to find product-market fit
https://untested.sonnet.io/notes/miss-make-it-stupid-simple/
I do get why some integrations are beneficial (eg. office software with text editing, spreadsheets and a database, so you can generate eg. letters with data from a database, etc... but every service needing its own cloud and adding a useless AI chatbot is just a useless overkill for me.
But then you start selling to Enterprise and everything changes. Because one missing "hygiene feature"* can tank the the whole deal. And every Enterprise has a different one.
*like a toilet. It needs to be there. You use it 3 minutes per day. If it is not there, the house is uninhabitable.