The Art of the Drop
How Great Products Make People Stop, Look again, and Change their Minds
There is a particular moment when a product stops being merely useful and becomes difficult to forget.
You open an app expecting one thing. Instead, it understands something about you that you had not quite articulated yourself. A task that normally takes six steps takes one. A decision you have been postponing becomes obvious. A problem you had quietly accepted as part of life suddenly looks like a design flaw.
You don’t necessarily think, this is an excellent product.
You think:
“Why has this always been so difficult?”
That is the moment product teams should be chasing.
Not novelty for its own sake. Not a longer feature list. Not another dashboard, notification, AI assistant or beautifully animated onboarding sequence.
Recognition.
The feeling that something has just clicked into place.
In UX writing, there is a similar moment. A copy can arrive quietly, but change the way a reader sees something they thought they already understood. It doesn’t necessarily introduce a new fact. It rearranges the facts they already have.
That is what we mean when we talk about an eureka breaking through. And there is a useful lesson here for anyone building digital products.
The strongest products often work the same way great ideas do. They don’t simply give people more. They make something suddenly make sense. And that’s UX research at its finest.
Start With What People Have Stopped Questioning
Most product opportunities are hiding in plain sight. Not because nobody has noticed the problem, but because people have become accustomed to it. They have learned the workaround.
They have memorised the sequence, built a spreadsheet. They have created a WhatsApp group, copied and pasted the same information seventeen times. They have learned that booking a particular kind of appointment requires three phone calls and an email. And have accepted that managing a small business means reconciling information across four different systems.
They have stopped asking whether the process should be this difficult. That is where interesting products begin. Not with: “What cool thing can we build?”
But: “What have people learned to tolerate?”
The distinction is enormous. If you start with technology, you tend to build around the capabilities of the technology.
If you start with an accepted frustration, you begin with the life of the person experiencing it.
That gives you somewhere much more interesting to go.
The First Job Is Not to Build
This is where product development becomes less glamorous and more intelligent. Before writing code, you need to understand the problem well enough to know whether it deserves to be solved. That sounds obvious. It is not. Teams routinely begin with a solution.
“We need an app.”
“We need AI.”
“We need a marketplace.”
“We need a dashboard.”
“We need an app with a social layer.”
Then they go looking for the problem that justifies the thing they have already decided to build.
This is backwards. The better question is: What is happening in someone’s life that is sufficiently frustrating, frequent or expensive that they have already invented a solution for themselves?
Their spreadsheet is evidence. Their workaround is evidence. The fact that they pay three different companies to do what could theoretically be one job is evidence. The fact that they complain about something every Tuesday but still return to do it every Wednesday is evidence. A product opportunity often begins where behaviour reveals a problem more clearly than language does.
People are surprisingly good at explaining what annoys them.
They are less reliable at designing the solution.
That is the product team’s job.
The Art of the Drop
This is where our metaphor becomes useful. A good drop requires judgment. You don’t just drop an app on the play store simply because you have the capacity to do it. You consider distance, timing, direction and impact. Product development is similar. You can have an extraordinary technology and still place it in the wrong platform.
You can have a brilliant feature and introduce it before the user understands why they need it.
Worse. You can have a genuinely useful product and explain it so badly that nobody gets close enough to discover its value. This is why positioning matters.
Consider the difference between:
An AI-powered personal productivity platform.
and:
Never lose an important commitment again.
The first describes a category. The second statement describes a consequence. The first one asks the user to understand your product. The second asks the user to recognise themselves.
That difference can determine whether someone scrolls past your App Store listing or taps Get.
A Product Needs a Fuse
Great products rarely reveal everything at once. They lead the user somewhere. You perform one action. The product responds. You understand something. You take another action. Then the central value becomes apparent. This is particularly important for unfamiliar products.
The first interaction should NOT feel like a tour of everything the engineering team managed to ship.
It should move the user toward the first meaningful outcome.
That outcome is the fuse. The product is essentially saying: “Give me fifteen seconds. Let me show you.” And then it has to deliver.
This is why onboarding is not primarily an opportunity to explain your product.
It is an opportunity to prove it.
A product that needs ten screens to explain why it is useful may have an explanation problem. Or, more uncomfortably, it may have a usefulness problem.
The Difference Between Surprise and Value
There is a temptation in product design to confuse surprise with delight. They are not the same. An unexpected animation can surprise me. A clever interaction can surprise me. A strange sound effect can surprise me. But if the surprise doesn’t improve my experience, it is just theatre. Real product delight is often quieter.
It is the app remembering something I would otherwise have to remember. It is a form that knows what I am likely to need. It is a search result that understands what I meant rather than what I typed. It is a workflow that removes three decisions I never wanted to make. It is the moment when the product seems to have anticipated the next thing I was going to do. The user may never describe any of this as “innovation.”
They simply keep using the product.
That is more valuable.
The Most Interesting Problems Are Often Landmines
There are problems users complain about loudly.
Then there are problems they don’t complain about at all because they don’t believe a better alternative exists.
Those are particularly interesting.
A traveller may complain that flights are expensive.
They may never complain about the cognitive burden of comparing departure times, baggage rules, airport locations, connections and cancellation conditions across twelve tabs.
A small-business owner may complain about accounting.
They may never describe the real problem as the fragmentation of operational information across multiple channels.
They just say:
“I have to check WhatsApp.”
“Then I check the spreadsheet.”
“Then I call the guy.”
“Then I update the system.”
That is where product thinking becomes valuable. The opportunity isn’t always in the complaint. Sometimes it is hidden in the sequence of behaviours surrounding the complaint.
Good product people learn to watch the whole sequence.
But Don’t Make the Product Clever for the Sake of Being Clever
This is where many teams lose their way. They discover an interesting interaction and immediately want to build around it. Then another. Then another. Soon the product is full of things users can discover, but nothing they can rely on. A product should not feel like an escape room.
Clarity is underrated.
The best interface may contain fewer surprises precisely because the important one has been designed so carefully. You want the user to know where they are. You want them to understand what happens next. You want the important moment to arrive without making them fight their way toward it.
The product should feel effortless not because nothing sophisticated is happening underneath, but because the sophistication has been absorbed by the system.
Get Tohbie Adelaja’s stories in your inbox
Join Medium for free to get updates from this writer.
The complexity belongs in the product. The simplicity belongs in the user’s experience.
The Three Ways Products Usually Miss
Ever seen a brilliant product fail…
You’ve probably used at least one product this week that *feels* like it was built by people solving a different problem than yours. Here’s what usually happened:
1. The Obvious Product
It solves a problem everybody already has ten solutions for. The team says: “Our difference is that ours is simpler.” Then you open it. It is not. There are 14 menu items.
2. The Impressive Product
It does extraordinary things nobody particularly needs. The demo is spectacular. The retention is not. This is the product equivalent of performing a magic trick for someone who asked where the bathroom is.
3. The Misunderstood Product
This one is particularly painful. The product is actually good. The market simply doesn’t understand why it should care. The team responds by adding more features. That rarely fixes the problem. Sometimes the product does not need more capability. It needs a clearer proposition.
Then There Is Product Friendly Fire
Product teams can destroy their own strongest idea.
A feature works. Users love it. The team sees the success and begins adding things around it. Soon the product is serving five different audiences, solving six adjacent problems and carrying a roadmap large enough to require its own postal address.
The original reason people loved it becomes difficult to find. This is why product strategy requires saying no. Not because additional features are inherently bad. Because every feature changes what the product means. A product is not simply the sum of its features.
It is the set of expectations those features create.
Add enough things and eventually the user no longer knows what your product is for.
A Great Product Has a Central Idea
Think about the products you remember.
Usually there is something you can say about them in one sentence. Not every capability. The idea. The reason they exist. That central idea becomes the organising principle for everything else. It influences the interface, the onboarding, the pricing, the notifications, the copy, the app store screenshots, the retention strategy, even what the team refuses to build.
This is where the metaphor of an explosive drop comes to play.
A strong product has a concentrated centre of value.
Everything else should reinforce it. If the core idea is weak, adding features spreads the weakness around. If the core idea is strong, even a small product can feel remarkably complete.
Timing Is Part of Product Design
A good idea can arrive at the wrong time.
The market may not be ready, the technology may be too expensive, the behaviour may not yet exist, or the opposite may happen.
The problem has become obvious, the technology has become cheap enough, users have developed new habits, and maybe distribution has changed.
Suddenly an idea that would have failed three years earlier becomes inevitable. This matters on the App Store because distribution creates a peculiar illusion.
We think a product “caught on” because it was good. Sometimes it was good and well-timed. Sometimes the category had just matured. Sometimes a platform change made discovery easier. Sometimes a cultural shift created a new behaviour. Sometimes a product simply arrived when millions of people had just developed the problem it solved. Product judgment includes knowing the difference.
The Test
Before you build the supposedly extraordinary thing, ask five questions.
1. Would someone recognise this problem without us explaining it?
If not, investigate further.
2. Are we solving a real problem or demonstrating an interesting technology?
If the answer is the second, be careful.
3. Can the user experience the value quickly?
If not, ask why.
4. Does the product change behaviour, or merely generate admiration?
Now we’re getting somewhere.
And finally:
5. If the product disappeared tomorrow, would anyone genuinely change their behaviour because of its absence?
That’s the test. Bookmark that!
Downloads as you would soon discover are easy to celebrate. Retention is harder. Habit is harder still. The real evidence appears when the user goes back to the old way and finds it intolerable.
That is when you know the product has crossed a line.
So How Do You Build A Great Product?
Let’s get to the ABC.
(I) First, start with something ordinary.
Watch people doing it. Look for the unnecessary steps. Look for the workarounds. Look for the information they keep copying. Look for the decisions they repeatedly have to make. Look for the places where they hesitate. Look for the things they complain about without even calling them problems.
Then ask:
What would have to be true for this entire process to become dramatically simpler?
What are we assuming has to remain manual?
What does the user actually care about at the end of this process?
What could the software understand on the user’s behalf?
What would happen if we removed rather than added?
And perhaps the most important question:
What would make the user immediately recognise that their old way was unnecessarily hard?
That is where the product begins to become interesting.
(II). Let the Product Speak
Don’t explain everything.
Don’t build a product that requires a presentation to appreciate. Don’t ask the user to imagine what the product could eventually become.
Show them.
Let them perform the action. Let the system respond. Let the value become visible. Let the user make the connection. That moment of recognition is worth more than a paragraph of marketing copy.
And it is much harder to fake. This is also why prototypes are so valuable.
A prototype can answer a question before engineering spends six months answering the wrong one.
A clickable prototype can test a workflow. A small release can test retention.A conversation can test whether the problem exists.
Good product development is not the heroic act of building everything. It is the disciplined act of learning what deserves to be built next.
One Good Thing About the Moment of Recognition
A great product does not necessarily make people’s lives more exciting. Often, it makes them quieter. It removes a thing they were constantly thinking about. It prevents an error. It shortens a process. It gives them confidence. It eliminates a decision. It makes something predictable. That is why some of the most successful products don’t feel revolutionary while you are using them. They feel obvious. Almost inevitable.
You finish using them and wonder: “Why wasn’t it always like this?”
(III) Understand the Real Goal
The goal of building an app should not be to make something people have never seen before. It is to make something people cannot imagine going back from. That’s a harder standard. It forces you to look beyond downloads. Beyond ratings. Beyond launch-day attention. Beyond the excitement of seeing your icon appear on the App Store. It asks a much more uncomfortable question:
· Did we change anything?
· Did we remove friction?
· Did we change a behaviour?
· Did we make a difficult thing easier?
· Did we help someone make a better decision?
· Did we give people a reason to return?
· Did we solve something they had simply learned to live with?
If the answer is yes, something interesting has happened. The product has moved beyond being a piece of software. It has become part of someone’s way of doing things. It has become a way of life. And that is when a product really catches on. When, somewhere in the middle of an ordinary Tuesday, looks at the old process, and says I can no longer search the internet, the way I use to. When they say, I can no longer transfer money, the way I use to.
That moment when they open the old app, and think: “Why would I ever do that again?”
That is the moment worth building for. That is the moment worth shipping for. And if you can create that moment consistently, you don’t need to convince the world that your product is extraordinary.
The users will do the announcing for you.
