“User-first” is an easy phrase to place on a homepage. It is harder to keep when the dashboard rewards growth, a deadline is close, or the most respectful choice adds another week of work.
For us, the phrase is useful only as a constraint. It should rule out some otherwise tempting decisions. It should force a conversation when a metric improves but the experience becomes less honest. And it should remain understandable to the person whose interests it claims to protect.
The test is not whether a product feels friendly. A cheerful interface can still obscure a subscription, over-collect data, or turn anxiety into retention. The real test is whether the product increases the user's ability to understand, choose, and leave.
Start with the job, not the session
Every Busted Minds product serves a different activity. A chess player wants a good game or a useful lesson. A search user wants a route to information. A sports fan wants to know what is happening now. A person opening Minds Feed wants a clearer view of a story. Someone working with BM AI wants help thinking or making.
Those jobs do not naturally end in the longest possible session. Search succeeds when the right exit appears. Sports can succeed with a score checked in ten seconds. AI can succeed by making the next prompt unnecessary. If we measure only time spent, we can easily optimize against the reason the person arrived.
So the first question is deliberately plain: did the product help someone do what they came to do? Engagement can tell us whether an experience is alive. It cannot tell us whether that experience is on the user's side.
Make the important state visible
Interfaces often hide consequential choices behind their cleanest surfaces. A recommendation appears without a reason. A setting is technically available but practically undiscoverable. An account connects several products without showing what crosses between them.
User-first design brings important state into view. People should be able to see why a result is present, which product holds their activity, what a feature will change, and how to reverse it. That does not mean covering every screen with legal language. It means designing clarity with the same care as speed and polish.
The Busted Minds Account principle—one identity, separate activity—is one example. Shared sign-in is useful. A hidden organization-wide dossier is not required to provide it. The boundary should be structural, and the interface should make that boundary legible.
Preserve a real choice
A choice is not meaningful if one path is brightly lit and the other is buried under friction. Declining a prompt, exporting information, disconnecting a product, or closing an account should not feel like winning an argument with the interface.
This standard also applies beyond settings. Alternatives matter because defaults accumulate power. We want Busted Minds products to be credible choices, but we do not want credibility to depend on trapping anyone who tries them. A product should earn continued use from present value.
That is why portability, clear permissions, and straightforward exits belong to product quality. They are not concessions offered after the “real” features are finished.
Be candid about capability
Useful technology has limits. Search can miss the best page. AI can be fluent and wrong. Live data can arrive late. Chess analysis can identify a stronger move without teaching the pattern. Pretending otherwise may make a demo feel magical, but it transfers uncertainty to the user while hiding the information they need to judge it.
We would rather make a limit actionable. Show the source. Mark the delay. Explain the confidence. Give the player the critical position instead of an unexplained score. Honesty is not a warning label attached to the experience; it is part of how the experience works.
Choose the relationship
Products teach people what relationship to expect from technology. They can teach that every quiet moment should be filled, every action should feed a profile, and every attempt to leave should meet resistance. Or they can be capable tools that arrive when useful and recede when the job is done.
We will not get every decision right. “User-first” is not a claim of purity. It is the direction in which we correct. When business pressure and user agency conflict, the phrase tells us what must remain in the room.
The shortest version is this: build something worth choosing, make the choice informed, and keep it reversible. Everything else is implementation.
Loading the conversation…