How to Listen to the Customer, and Designing a Business That Breaks Bias｜First-Principles Thinking, Bias Break, and Market-Out

Hello, this is Ryuta Hamamoto from TIMEWELL.

When you run a business, you always hit this question somewhere along the way. How do you find the thing you should build? The textbooks tell you to listen to the customer. That is correct, but once you actually start gathering voices, a different wall appears. You built exactly what you were told, and yet it does not land at all. Or you pack in every request you collected, and what comes out is mediocre for everyone.

I have watched this play out many times myself. And where I arrived is the belief that business design needs two capabilities. One is the ability to listen to the customer correctly. The other is the ability to not be dragged along by those voices, or by your own assumptions, but to doubt the premises themselves and rebuild from there. In this article, the first half organises how to listen to the customer at a practical level, and the second half traces the ways of thinking that break premises apart, first-principles thinking, bias break, and market-out, in a way that makes sense even to a beginner. If you are curious about where you, or your company, stand right now on using AI and on your own thinking, it helps to first check your position with our free AI literacy self-check. The later part of this piece will feel more concrete once you have.

Why growing a business through customer feedback is the basic stance

Let me start from the foundation. If this shakes, everything built on top of it floats free.

A business, at its root, is the work of solving someone's trouble and receiving payment in return. The one who is troubled is the customer, not the maker. Yet makers tend to overvalue what they themselves think is good. Inside your own head the logic runs perfectly, and then you release it into the world and there is no reaction. This gap opens up when the maker charges ahead without knowing the customer's reality.

That is exactly why the basic stance is to treat a business not as something you land on the first try, but as something you gradually reshape by receiving customer feedback. You form a hypothesis, put it in front of a customer, and fix it based on the reaction that comes back. The person who runs this back-and-forth quickly and many times is the one who, in the end, reaches something that works. Put the other way round, the more you try to complete it at your desk, the higher the odds you have missed.

Steve Blank, who advocated the idea of customer development, expressed this with the line "there are no facts inside your building, so get outside." The gist is that a startup's hypothesis can never be known to be right until you go to real customers and test it. He laid out four stages, customer discovery, customer validation, customer creation, and company building, and systematised a way of moving forward while repeating hypothesis and verification. This is said to be one of the sources of what later became the Lean Startup¹.

In other words, getting feedback and improving is not "something to do if you have spare capacity." It is the work that sits at the centre of business design. Everything from here builds on this foundation.

There are many established forms for listening to the customer

So, concretely, how do you gather the voice? This is where many people stumble. Just going around asking "what do you think?" tends to collect nothing but unreliable impressions. There are several forms for listening that predecessors have refined.

Grasp demand from the job to be done

The first is Jobs to be Done, the idea that a customer has a "job" they want to get done. It is widely attributed to Clayton Christensen². The point is to grasp demand not by the customer's attributes but by the situation. Not "because she is a woman in her thirties," but "because she wants to fill her stomach easily, with one hand, on the morning commute." In this view, a customer does not so much buy a product as hire it to get a certain job done.

The famous milkshake example makes it clear. When a fast-food chain surveyed how to raise shake sales, they found, surprisingly, that many shakes were bought in the morning by solo customers on their commute. The job they wanted done was "a one-handed breakfast that keeps a long drive from being boring and holds off hunger until lunch." Seen through this job, the real competitor of the shake was not rival shakes but bananas, bagels, and doughnuts². Understand the job the customer wants done at the root, rather than the visible competition. This is where the true nature of demand hides.

Ask in a way that does not draw out flattery

The second is the interview craft called The Mom Test. It became widely known through Rob Fitzpatrick's book³. The name comes from the premise that if you ask directly whether your idea is good, a kind listener, like your mother, will offer flattery. Being told "I think that's nice" is not a reason for anyone to buy.

By the widely settled summary, the crux of this craft is three points. One, talk about the other person's life and work, not about your idea. Two, ask about concrete past events, how they actually behaved before, rather than future opinions or generalities. Three, do not talk too much yourself; let the other person talk³. Not "would you use our app?" but "how did you handle that task last time?" This difference separates flattery from fact. That said, these three principles are a settled summary derived from the book; for the exact wording, it is safest to go to the original.

See the gap between what people say and what they do

The third is behavioural observation. It derives from ethnography (a method of cultural anthropology) and is said to have been established in the field of human-centred design. Rather than only the voices put into words in an interview, you observe up close how the customer actually behaves on the ground. The aim is to pick up inconveniences the person is not even aware of, and unconscious workaround behaviour.

People cannot put everything they do into words. It is not rare for someone to say "nothing in particular is inconvenient" while, in fact, unconsciously going through a tedious sequence of steps every single time. In this gap between what they say and what they do lies the real problem that never surfaces as a voice. So you do not only ask; you watch. This observation is often used alongside JTBD and customer development as a way of gathering information.

Laid out this way, you can see that every form of listening shares a single point, that you never take surface words at face value. See situation rather than attribute, behaviour rather than opinion, conduct rather than words alone. Simply holding to this basic stance changes the quality of the information you gather a great deal.

Even so, gathering voices alone is not enough

Reading this far, you might think, "So if I listen carefully, I can reach the right answer." But it is not that simple. What I find hard on the ground of business lies exactly beyond this point.

Listening to the customer correctly is a necessary condition, but not a sufficient one. There are two reasons.

One is that the customer does not necessarily know the answer. Customers are well informed about their own trouble, but they are not experts in how to solve it. So they can say "I want a faster horse," but they cannot say "I want a car." They can speak of the job they want done, but not of a solution that does not yet exist in the world. The more voices you gather, the more improvement ideas on the extension of the existing line pile up, but a discontinuous leap is hard to draw out from there.

The other is a problem on the side of the planner. A person who plans a business often holds deeper knowledge of the domain than the customer does. That is a strength in itself. Yet holding deep knowledge and holding strong assumptions are often two sides of the same coin. Premises like "this is how this industry works" and "customers will surely act this way" harden, before you notice, without ever being doubted. When things are going well, this premise functions as experiential knowledge. But when things do not go well, much of the cause, I believe, lies in this unnoticed premise, that is, in bias.

Here the problem flips. The ability to listen alone is not enough; you need the ability to doubt, for the moment, both the voices you gathered and your own assumptions. The ability to break premises. In the second half, we will look, in order, at three ways of thinking for this "breaking."

First-principles thinking: doubt the premise and build up from principle

The first is first-principles thinking. A first principle is the most basic proposition or premise, one that cannot be derived from any other proposition or premise. The origin of this concept traces back to ancient Greek philosophy, and Aristotle is known for having discussed knowledge concerning first principles⁴.

The core of the idea is simple. Stop leaning on analogy, "because everyone does it this way" or "because it has always been this way," and break the problem down to its unquestionable root elements. Then rebuild your conclusion from zero. You take the principle, not the existing answer, as your starting point.

The one who popularised this term is Elon Musk. He explains it as the physics way of doing things, building logic up from the root rather than by analogy. The battery example is often cited. At the time, there was a received view that a battery pack cost around 600 dollars per kilowatt-hour and would stay expensive. Musk set this received view aside for the moment and asked again, what are the constituent materials of a battery? He is said to have broken it down into materials such as cobalt, nickel, aluminium, carbon, and polymers, and calculated that if you bought them at the London Metal Exchange spot price, it could fall to around 80 dollars per kilowatt-hour⁵. It is told as an example of rebuilding from the principle of material cost, rather than taking the historical price as a premise. That said, this figure is a citation that has passed through secondary commentary, so if you use it verbatim it is safest to go to the original statement.

Brought closer to business, this is the work of asking again, "that premise, is it really so?" Take premises circulating as industry common sense, "the gross margin in this industry is usually around this level," "customers won't pay for this feature," and break them down, for the moment, to their materials. Often you find that it was merely an assumption handed down, never verified by anyone. When you hold this first-principles view at the same time as gathering the voice of the customer, you can sometimes see a way of solving that does not lie on the extension of those voices.

This stance of questioning premises from the root works not only for business design but also when you think about how to build AI into your work. With our service WARP, we do exactly this work of "doubting the premise and rebuilding" together with managers. I will come back to it later.

Hideshi Hamaguchi's bias break: identify the fixed assumption and break it

The second is bias break. This is known as an ideation approach advocated by the concept creator Hideshi Hamaguchi (濱口秀司).

First, about the person. According to publicly available information, Hideshi Hamaguchi is introduced on the English Wikipedia as a Japanese concept creator and business strategist (also called a business designer or innovation designer), known in the fields of concept development, strategy building, and decision-making⁶. As for his career, he is described as having become, in 1993 at Panasonic, one of the early members responsible for corporate decision-making analysis, and in 1994 as having jointly taken part in building what is said to be Japan's first corporate intranet. He is said to have later been at the US design firm Ziba Design, where he served as director of strategy, and during his time there to have created the concept of what is described as the world's first USB flash drive. As a product, the USB memory stick was launched in North America by companies including IBM around 2000, so here it is accurate to keep to the phrasing "is said to have created the concept"⁶.

Now, the idea of bias break. Hamaguchi gave a talk titled "Break the Bias" at TEDxPortland in 2012, and bias break is positioned as one of his central ideas⁶. Its outline is this: first identify the fixed assumptions that a market, or you yourself, unconsciously hold, that is, biases, and deliberately break them, so as to generate unprecedented concepts in a structured way.

What matters here, as I take it, is the part about "in a structured way." Bias break is not an ideation approach that waits for a genius's flash of inspiration. Quite the reverse. Its feature is that it designs ideation through a set procedure, listing out the premises that an industry, or you, take as "obvious," and turning them over one by one. If first-principles thinking, just above, is about "breaking down to the principle and building up," then bias break is about "finding the assumption everyone is bound by, and daring to do the opposite." Organised this way, I think the difference is easy to see.

Brought closer to business, this idea lets you turn "industry common sense" into a weapon. For instance, if there is an industry fixed assumption that "this product is a premium item, so it should be sold face to face in a store," dare to break it and ask, what happens if we sell it unstaffed? If value is born on the other side of that break, then you have outwitted a premise that competitors are still bound by. Here too, the stance is to deliberately go after ideas that gathering voices alone cannot produce, by breaking a premise.

Misumi's market-out: question the very frame the customer is in

The third is market-out, known as part of the management thinking of Misumi (ミスミ). This was a part where a first-source definition and a definite proponent were hard to pin down, so I introduce it while placing some reservations.

By the account generally given, market-out is positioned as a third way of thinking, neither product-out, where you build to suit the maker's convenience, nor market-in, where you listen to customer requests and respond to them. Starting from demand or inconvenience the customer has not yet put into words, you define ahead of time, from the customer's standpoint, "what is the problem that should truly be solved," and provide for it. It is often spoken of as that kind of idea.

Why is it neither product-out nor market-in? It clicks when you connect it to the first-half discussion. Product-out is bound by the maker's bias, and market-in is bound by the request the customer voiced, that is, by the range of the customer's bias. Both stay inside the frame of someone's assumption. Market-out can be understood as an idea that takes off both frames for the moment and tries to descend to the layer of problems the customer is not even aware of. It can also be read as one answer to the problem, touched on in the first half, that "the customer cannot put into words what they truly want."

As an aside, on the management of Misumi (Misumi Group Inc.), its founder Hiroshi Taguchi (田口弘), and Tadashi Saegusa (三枝匡), the former president who also served as chairman and CEO and who led the company's turnaround and growth, are known as bearers of that thinking⁷. That said, the definition of the term "market-out," and who specifically proposed it, could not be pinned down from the publicly available information I could reference while preparing this article. Here I keep to an introduction within the range of "known as part of Misumi's management thinking." Those who want to know more accurately would do best to go to Tadashi Saegusa's writings and Misumi Group's official information.

What breaking really requires is the ability to put things into words

First-principles thinking, bias break, market-out. Their names and origins differ, but the three share one point in common. Each is a way of thinking that "doubts, for the moment, a premise taken as obvious." And to doubt that premise, there is a shared task you must do first. Putting the premise into words.

This is plain, but I believe it is decisively important. A bias functions as a bias precisely because it has not been put into words. An assumption soaked in like air, before it is clearly spoken as "this is how this industry works," cannot be doubted. To doubt it, you first have to drag it out onto paper and say, "right now, we are placing this premise." Only once a premise is put into words can you ask, "is that really so?" The breaking down in first-principles thinking, the identification in bias break, and the redefinition of the problem in market-out all begin from this putting-into-words. This is my own view, but the hard part is not the breaking; it is putting into words the thing to be broken.

So how do you build this into your own company? There is no need to think of it as difficult. In a meeting, once, before you make a decision, try asking this. "Right now, what premises are we treating as obvious as we discuss this?" List out the premises that come up, and examine each with "what if this were the opposite?" This small habit becomes a device for inspecting both the voice of the customer and your own assumptions. It is good to lay the customer voices you gathered in the first half onto this table too. The customer-side premises within the voices, and your own premises, come into view with surprising clarity.

Even so, your own premises are hard to see on your own. Precisely because they are soaked in like air, you cannot notice them from the inside. This is where an outside view works. WARP, the service we offer, is one in which specialists who led DX and data strategy at major companies walk alongside you month by month, thinking through the design of your business and your use of AI together with you. The work of putting premises into words and questioning them from first principles is exactly the kind of area where progress speeds up when you have a sparring partner. For those about to launch a business in particular, there is also a framework for founders called WARP Entre. The angle of how to build AI into a business is organised in this article as well, so please read it alongside. When you want an outside view rather than carrying it all alone, please talk to the WARP team.

In summary

This ran long, so let me organise the key points.

• A business is not something you land on the first try; the basic stance is to improve it by receiving customer feedback. The stance of "there are no facts inside your building, so get outside and verify" is the foundation
• There are established forms for listening to the customer. JTBD, which grasps demand by the job to be done; The Mom Test, which avoids flattery; behavioural observation, which sees the gap between words and deeds. All share the point of not taking surface words at face value
• But gathering voices alone is not enough. Customers cannot speak the answer, and planners tend to harden their assumptions precisely because of their own knowledge. Much of the cause, when things do not go well, lies in unnoticed premises, that is, in bias
• There are three ways of thinking that break premises. First-principles thinking, which breaks down to the principle and builds back up; bias break, which identifies a fixed assumption and deliberately breaks it; and market-out, which takes off both the maker's frame and the customer's frame
• What you first need in order to break is to put the premise into words. The small habit of asking, in a meeting, "what premises are we treating as obvious right now?" becomes a device for inspecting both the voices and your own assumptions

Listening sincerely to the voice of the customer. And, without being bound by those voices or by your own assumptions, doubting the premise and rebuilding. When you can move back and forth between these two, business design, I think, deepens by a level. Starting from today's meeting, try beginning with just one thing, putting an "obvious" into words.

References and primary sources

Footnotes

1. Steve Blank / Customer Development. Built around "there are no facts inside your building, so get outside," it is a method that verifies hypotheses with customers across the four stages of customer discovery, customer validation, customer creation, and company building. Books: "The Four Steps to the Epiphany" and, co-authored, "The Startup Owner's Manual." Regarded as one of the sources of the Lean Startup. Confirmed via Wikipedia, "Customer development" https://en.wikipedia.org/wiki/Customer_development ↩

2. Jobs to be Done. A way of grasping demand by situation and job rather than by customer attribute, treating the product as something you "hire." Widely attributed to Clayton Christensen (Harvard); in the milkshake example, the true competitor for the job of a morning-commute breakfast was shown to be bananas, bagels, and the like. A derivative is Tony Ulwick's Outcome-Driven Innovation. Published and confirmed as theory at the Christensen Institute https://www.christenseninstitute.org/theory/jobs-to-be-done/ ↩ ↩²

3. The Mom Test. By Rob Fitzpatrick. An interview craft for asking in a way that forces the other person to speak their real thoughts. The three widely cited principles are: talk about the other person's life and work, not your idea; ask about concrete past behaviour and events, not future opinions or generalities; do not talk too much and let the other person talk. Author and gist confirmed at the book's official site https://www.momtestbook.com/ . Note, however, that the wording of the three principles is a widely settled summary derived from the book; refer to the original for the exact text. ↩ ↩²

4. First principle. The most basic proposition or premise, one that cannot be derived from others. A way of thinking that breaks down to root elements without leaning on convention or analogy and rebuilds the conclusion from zero. Its origin lies in ancient Greek philosophy (Aristotle discussed knowledge of first principles and first causes). Confirmed via Wikipedia, "First principle" https://en.wikipedia.org/wiki/First_principle ↩

5. Elon Musk's explanation of first-principles thinking and the battery example (against the received view of around 600 dollars per kilowatt-hour, he showed that building up the constituent materials at London Metal Exchange spot prices could fall to around 80 dollars). Confirmed at the fs.blog (Farnam Street) explainer https://fs.blog/first-principles/ . As this is a citation via secondary commentary, refer to the original statement (around 2012) when quoting verbatim. ↩

6. Hideshi Hamaguchi (濱口秀司). Introduced on the English Wikipedia as a "Japanese concept creator and business strategist" (also called a business designer / innovation designer), known for concept development, strategy building, and decision-making management. He is described as having become, in 1993 at Panasonic, one of the early corporate decision-making analysts, in 1994 as having jointly built what is said to be Japan's first corporate intranet, as having been at Ziba Design (later Director of Strategy), as having created during his time there the concept of what is said to be the world's first USB flash drive, and as having given the "Break the Bias" talk at TEDxPortland in 2012. Confirmed via Wikipedia, "Hideshi Hamaguchi" https://en.wikipedia.org/wiki/Hideshi_Hamaguchi . The USB memory stick was commercialised and launched in North America by companies including IBM in 2000, so the body text keeps to the phrasing "is said to have created the concept." ↩ ↩² ↩³

7. "Market-out," known as part of Misumi's management thinking. Generally introduced as a third way of thinking, neither the maker-convenient product-out nor the request-responsive market-in, that defines and provides ahead of time the demand and problems the customer has not put into words. Misumi Group Inc.'s founder is Hiroshi Taguchi (田口弘), and the one who led the turnaround and growth is Tadashi Saegusa (三枝匡), a former president who also served as chairman and CEO. Titles confirmed via Wikipedia, "三枝匡" https://ja.wikipedia.org/wiki/三枝匡 . However, the definition of the term "market-out," its proponent, and the attribution of the contrast with product-out / market-in could not be pinned down from the publicly available information referenced, so the body text keeps to the range of "known as part of Misumi's management thinking." Confirming the definition and attribution requires additional verification via Tadashi Saegusa's writings and Misumi's official information. ↩