What If You Stopped Designing for Who Your Customer Wants to Be?
Every product discovery session, MBA classroom, and design thinking workshop will eventually put this idea on the board: find the gap…
What If You Stopped Designing for Who Your Customer Wants to Be?

Every product discovery session, MBA classroom, and design thinking workshop will eventually put this idea on the board: find the gap between who your customer is and who they wish to be — then build the bridge across it.
This framework does not exclude the struggling customer. It starts with them. The fitness app’s primary customer is not the person who already wakes up at 5am and runs ten kilometres. It is the person on the couch — the one who skips workouts, loses streaks, and feels guilty about it. That person is not an edge case. They are the market.
The budgeting app is not built for the naturally frugal. It is built for the impulsive spender — the one who checks their account balance with a wince. The productivity tool does not target people who are already disciplined. It targets the person overwhelmed by open tabs and an inbox that never empties.
So the framework is more precise than it first appears. It says: meet the customer in their current, struggling state — and then actively engineer movement toward a better one. Streaks, badges, habit loops, social accountability, gentle nudges, friction reduction — all of these are tools for making the journey across the gap possible. The gap is not avoided. The gap is the product’s entire purpose.
And then there is the Snooze button. Which also starts with the struggling customer — and stops there. Which makes it not just unusual. It makes it the most quietly subversive product decision in the history of consumer technology.
Before we blame the lazy, let us revisit history
The difficulty of waking is not a character flaw. It is a biological fact — one that humans have been engineering around for more than a thousand years, long before anyone thought to feel ashamed about it.
- 6th century — Benedictine monks faced the earliest version of this problem. They needed to rise before dawn for Matins — the first prayer of the day. They were not lazy. They were among the most disciplined people in medieval Europe. But sleep is a biological state, not a moral one, and it does not yield to intention alone. Monasteries developed bell systems, night watchmen, and water-powered mechanical devices specifically to drag the body from sleep into wakefulness. The engineering of waking-up began in places of deep devotion, not places of sloth.
- 1800s — The knocker-upper emerged in industrial England — a paid professional whose entire job was to knock on bedroom windows with a long pole until the occupant stirred. Critically, they did not leave until they saw movement. They did not trust the sleeper’s intention. They waited for proof of waking. This was not a luxury service for the idle rich. It was used by factory workers, miners, and mill hands — people whose livelihoods depended on punctuality, and who understood that intention and biology are not the same thing.
- 1847 — The mechanical alarm clock democratised the knocker-upper. Now every household could have its own relentless nagger, ticking quietly until it screamed. It was sold as self-reliance. No more depending on a stranger. The alarm clock said: you can do this yourself. And with that, subtly, the framing shifted. The difficulty of waking became a personal responsibility — and eventually, a personal failing.
- 1956 — General Electric shipped the Snooz-Alarm — the first clock with a Snooze button, offering nine extra minutes. The nine minutes was not a design insight. It was the largest interval achievable under the gear ratios of analog clock mechanisms. Nobody had asked for it. No customer discovery session surfaced it. An engineer noticed that people were already hitting their clocks to silence them. The behaviour existed before the product. Snooze simply formalised it — without judgment, without a plan to improve you, without a streak to protect.
The through-line from medieval monks to the modern smartphone is unbroken: waking is genuinely hard. We were built to rouse gradually, with light and sound and time. The alarm clock shattered that transition and replaced it with a single violent moment of obligation — and then told us that struggling with that moment was a sign of weakness.
We turned a biological fact into a personal failing. And then we built a product that quietly refused to agree.
What the product strategy textbook would have said
Imagine presenting the Snooze button in a product discovery session circa 1954. You open with the insight: users are hitting their alarms and falling back asleep. They are not waking at their intended time.
The room nods. Then it asks the standard question: what does the customer want to become?
And the answer is obvious. They want to be the person who wakes up on time. Who rises with purpose. Who is not a slave to the pull of sleep. Every customer, when asked, will describe their aspirational self. They describe the version of themselves that succeeds.
So the room would have prescribed: better alarm tones, gradual brightness, sleep cycle tracking, commitment devices. All of these serve the gap-closing mission. All of these treat the difficult moment as a problem to engineer away.
Nobody in that room would have said: build a button that lets them delay the very thing they said they wanted to do — and make it the easiest button to press.

The precise distinction that matters
Conventional great products — fitness apps, budgeting tools, productivity software — meet the customer in their resistant, impulsive, overwhelmed state and treat that state as the starting point of a journey. The product is engineered to move them. The gap is not ignored. The gap is the mission.
Snooze met the customer in their resistant state and made that state more comfortable to remain in. It did not engineer movement. It removed the discomfort of not moving. It did not build a bridge across the gap. It furnished the gap.
This is why Snooze is genuinely subversive, and not merely clever. It is not an alternative approach to the same goal. It is a repudiation of the goal itself. It says: the customer’s aspiration is not your product’s job. Your product’s job is this moment — the one happening right now, at 6:03am, in the dark.
The knocker-upper did not try to reform the sleeper. He knocked, waited for movement, and left. He served the moment. Not the mission.
Where is the Snooze in your product?
This is not a case against aspiration-driven design. Fitness apps that build real habits, budgeting tools that change real spending behaviour, productivity software that reduces real cognitive load — these are among the most valuable products ever created. Serving the gap-closing mission is honourable and important work.
But the Snooze principle asks a different and complementary question. Not: what does my customer want to become? But: where is my customer already hitting the clock?
Where in your product, your service, your customer journey, is the customer already improvising a workaround? Where are they already doing something your product never intended — buying themselves a little more time, a little less pressure, a little more grace before they have to do the hard thing?
That workaround is not a design failure to be patched. It is data — the most honest data you will ever collect. It is the customer communicating not with their aspirational self, but with their actual body and their actual behaviour, exactly what they need at the moment of maximum friction.
The knocker-upper understood this intuitively. He did not lecture the mill worker about the importance of punctuality. He knocked, and waited, and served the moment. Over centuries, we layered guilt onto that moment — decided that needing help with the biology of waking was evidence of poor character. The Snooze button quietly, commercially, and at enormous scale, pushed back against that guilt. It did not ask you to be better. It gave you nine minutes.
The subversive lesson for strategy
Every customer journey map you will ever see has moments of friction marked on it. Places where customers hesitate, retreat, delay, or abandon. Standard product strategy says: remove the friction, or redesign the journey around it. Get the customer to the destination faster.
The Snooze insight says something different. Some friction is not a flaw in the journey. Some friction is the journey. And the customer who is sitting inside that friction — not moving, not progressing, not becoming — is still a customer. They still have a moment. That moment still has a value.
No discovery process will surface this. Because discovery asks customers about their aspirational selves, and aspirational selves do not admit to needing a Snooze button. They describe the 6am run. They describe the balanced budget. They describe the inbox at zero.
But between that description and reality, every morning, millions of people hit a button. And that button — born from a gear ratio, never requested, never imagined in any product strategy session — became one of the most-used features in human history.
Your customer’s aspirational self will tell you what they want to build. Their resistant self will tell you what they will actually use. The best products find a way to serve both. The rarest ones have the courage to serve only the second.
So the next time you are mapping a customer journey, after you have charted the aspirations and identified the desired outcomes and planned the habit loops — look for the moments where the customer is already hitting the clock.
Find that moment. Sit with it. And ask whether your job is to engineer them across it — or to give it nine minutes of grace.
메타데이터
- post_id
- 4f1b7dc4d08d
- slug
- what-if-you-stopped-designing-for-who-your-customer-wants-to-be-4f1b7dc4d08d
- url
- https://medium.com/@shahmm/what-if-you-stopped-designing-for-who-your-customer-wants-to-be-4f1b7dc4d08d
- canonical_url
- https://medium.com/@shahmm/what-if-you-stopped-designing-for-who-your-customer-wants-to-be-4f1b7dc4d08d
- author_url
- https://medium.com/@shahmm
- status
- ok
- fetched_at
- 2026-06-12 07:40:50