The writing tool with the most features is rarely the writing tool that produces the most writing. There's research behind this — decades of work on decision fatigue, response time, and cognitive load — but most people discover it through frustration. Hick's law (1952) established that decision time grows logarithmically with the number of options. The more a tool offers, the more cognitive cost it imposes simply by existing on your screen. And cognitive cost is paid out of the same budget you were going to spend on the writing.
You wanted a writing tool. You ended up with a productivity platform. The app has 350 features. It has databases, kanban boards, AI assistants, calendar views, formula syntax, embedded widgets, three kinds of templates, and a graph view that you've never used.
Most of these features are technically useful. Each one was added for a reason. But the cumulative effect is that the moment you open the app, you're not writing. You're orienting. You're remembering where things are. You're considering whether you should restructure your workspace. You're being a project manager, briefly, before being a writer.
By the time you actually start writing, the energy you brought to the session has been quietly taxed. You don't notice the tax, because no single feature is costing you very much. But forty small taxes adds up to a real bill, and you pay it every session.
Hick's law (1952) shows decision time grows with the number of options. Schwartz (2004) found more choices reduce satisfaction and increase paralysis. Every unnecessary feature costs you cognitive budget — the same budget you need for writing.
What does the research actually say?
In 1952, the British psychologist William Hick published a paper that introduced what's now called Hick's law. It established a simple but durable principle: the time it takes a person to make a decision increases logarithmically with the number of choices available. More options means slower decisions, every time.
Hick's law has been applied to everything from menu design to airline cockpits. Its implication for software is sharp. A tool with 350 features doesn't just have 350 features. It has, at every moment, a decision space that your brain has to scan, weigh, and dismiss. That scanning costs working memory — the same working memory you needed for writing.
A second body of research comes from the psychologist Barry Schwartz, whose 2004 book The Paradox of Choice synthesized decades of findings on decision-making and well-being. Schwartz's argument was that beyond a small number of options, additional choices reduce satisfaction and increase paralysis. People with more options often make worse decisions and feel worse about them. The optimal number of choices for any given decision is small.
A third strand is John Sweller's cognitive load theory. Sweller distinguished between intrinsic load (the difficulty of the task itself) and extraneous load (the cognitive cost of how the task is presented). Every unnecessary feature, button, or menu adds extraneous load. Writing already has plenty of intrinsic load. Adding extraneous load on top is paying twice.
The combined picture is uncomfortable for the dominant trend in productivity software. The more a tool offers, the more it costs you. Not in subscription dollars — in cognitive budget. And the cognitive budget is the one you can't refill by paying more.
Why can't you just ignore the features you don't use?
The standard defense of feature-rich software is that you don't have to use everything. Just stick to the features you need. The rest will sit there harmlessly.
This isn't quite right, and the research is why. Features you don't use still occupy visual real estate. They appear in menus. They occupy your peripheral vision. They appear in onboarding flows, settings, and notifications. Your brain has to actively not pay attention to them, which itself is a small but ongoing cognitive task.
There's also the deeper problem of opportunity recognition. Every feature you've ever seen in the app is a possible answer to a problem you might encounter. When you hit a moment of difficulty in your writing, part of you is now thinking about whether one of those features could help. That micro-deliberation is the tax — and it happens whether or not you actually use the feature.
This is why minimalist tools often outperform feature-rich ones for actual writing. Not because they do more, but because they ask less of you.
What actually helps?
The principle is straightforward: choose tools that have the smallest number of features compatible with the work you actually do.
In practical terms, this means writing software that decides what it's for and excludes what it isn't. That treats every feature as a cost as well as a benefit. That removes interface elements rather than adding them. That uses keyboard shortcuts to make essential actions invisible at the surface. That doesn't try to be every other category of tool.
There's a related design heritage worth knowing. The German industrial designer Dieter Rams, who shaped Braun's design language in the 1960s and 70s, articulated a principle he called less, but better. Apple's design culture absorbed it. The Japanese aesthetic tradition has called it various names. The throughline is the same: the goal isn't to add features. The goal is to remove what isn't essential, so what remains can be excellent.
This is harder than adding features. Adding is a checkbox; removing is a judgment call. But the judgment call is what produces tools that disappear, leaving only the work.
How Wretify approaches this
Wretify has eight features. Not eighty. Not three hundred and fifty. Eight, chosen carefully, refined obsessively.
This wasn't a marketing decision. It was an architectural one. Each feature was added because the absence of it was producing a measurable cognitive cost. None of them was added because it would make the app comparable to a competitor.
There's a section on the Wretify pricing page that lists what other tools we're replacing — ChatGPT Plus, Scrivener, Readwise Reader, Day One, Notion. The list is misleading in one way: Wretify doesn't replace those tools by matching their features. It replaces them by recognizing that the features were never the point. The point was the work the writer was trying to do. Eight rooms, designed well, do more for that work than three hundred rooms designed adequately.
I built it this way because every productivity app I'd tried had eventually become a job in itself. I didn't want another job. I wanted a tool that would shrink to fit the writing.
You don't notice the tax, because no single feature is costing you very much. But forty small taxes adds up to a real bill, and you pay it every session.
- Hick's law (1952): decision time grows logarithmically with the number of options available.
- Barry Schwartz (2004): beyond a small number of options, additional choices reduce satisfaction and increase paralysis.
- Cognitive load theory: every unnecessary feature adds extraneous load on top of the intrinsic difficulty of writing.
- Features you don't use still impose a cognitive cost — your brain has to actively not pay attention to them.
- Wretify has eight carefully chosen features rather than hundreds, by design — less, but better.
This article was written in Wretify. Try it free →
Frequently asked questions
No. More functionality is better only up to the point where the cost of finding, learning, and remembering features starts to outweigh their benefit. Most productivity tools have crossed that point.
Because feature lists are easy to compare and marketing-friendly. "350 features" is easier to advertise than "the right eight features." But the buying decision and the using experience are different. You buy on features; you live with cognitive cost.
Partially. You can't easily un-see them. They occupy visual real estate, appear in menus, and offer themselves as possible solutions when you're stuck. The act of ignoring them is itself a small cost.
Sometimes. The question is whether the features removed were doing work you actually needed. A well-designed minimalist tool removes what was incidental, not what was essential. The judgment of what's essential is the whole craft.
Yes — for users whose work genuinely demands range. A power user editing video, designing architecture, or building software wants and needs the long menu. For nonfiction writing, the menu is usually overkill.