A product isn’t just functional, it’s felt. The brain runs on logic and emotion together — stimulate both or you’re only half selling it. quote
Frustration is opportunity: whatever’s annoying the user is the void you get to fill. Connect with them the Lean startup way, or just build for the need you share yourself. Just don’t build what already exists. People want comfort, not more worry.
But comfort alone isn’t enough — people also want to feel empowered, not handled. A story is a deal says the same thing from the other side.
Exceed expectations. Users can’t always tell you what they need though — The mom test is the whole method for getting past what they say to what they mean. Chrome’s a good example of this done right.
And godamnit, don’t try to extract every penny out of people. They feel it, and once they feel it the delight’s gone.
Product delight is close to the most important thing about an app — not the features. Delighted users stay, they share it themselves. Just don’t chase visual effect for its own sake, most of the app still has to work.
So how do you actually build that connection?
Motivational segmentation first: split users by what actually drives them. Hard to find without watching and talking to them, but mostly — try shit. Lean startup
Personal motivators: pride, accomplishment, control.
Social: admiration, connection, validation.
Every app answers some need — know which one (job to be done framework, competing against luck, what customers want). Then find the ups and downs of your product and put the effort exactly there: raise the downs or at least acknowledge them, celebrate the highs properly.
Brainwriting: ten minutes of writing ideas alone, then share.
The test that cuts through all of it: if my product was replaced by a real person, how would they do it better? That gap is the delight.
Linked to:
ai coding