Quotes About Problem

The common tendency of product development is to skip straight to the fourth question and build a solution before confirming that customers have the problem.

1. Do consumers recognize that they have the problem you are trying to solve? 2. If there was a solution, would they buy it? 3. Would they buy it from us? 4. Can we build a solution for that problem?

As Cook says, "Success is not delivering a feature; success is learning how to solve the customer's problem."4

At the root of every seemingly technical problem is a human problem. Five Whys provides an opportunity to discover what that human problem might be.

Those who have sat in a meeting debating the units of measurement in a report will recognize this problem.

Do consumers recognize that they have the problem you are trying to solve? If there was a solution, would they buy it? Would they buy it from us? Can we build a solution for that problem?

first answer four questions: Do consumers recognize that they have the problem you are trying to solve? If there was a solution, would they buy it? Would they buy it from us? Can we build a solution for that problem?

Dropbox needed to test its leap-of-faith question: if we can provide a superior customer experience, will people give our product a try? They believed—rightly, as it turned out—that file synchronization was a problem that most people didn't know they had. Once you experience the solution, you can't imagine how you ever lived without it.

if management is the problem, chaos is the answer.

Success is not delivering a feature; success is learning how to solve the customer's problem."4

Mark explained, "Traditionally, the product manager says, 'I just want this.' In response, the engineer says, 'I'm going to build it.' Instead, I try to push my team to first answer four questions: Do consumers recognize that they have the problem you are trying to solve? If there was a solution, would they buy it? Would they buy it from us? Can we build a solution for that problem?

Traditionally, the product manager says, 'I just want this.' In response, the engineer says, 'I'm going to build it.' Instead, I try to push my team to first answer four questions: 1. Do consumers recognize that they have the problem you are trying to solve? 2. If there was a solution, would they buy it? 3. Would they buy it from us? 4. Can we build a solution for that problem?

Isn't that the problem? That women have been swindled for centuries into substituting adornment for love, fashion (as it were) for passion?

In the nineteenth century the problem was that God is dead. In the twentieth century the problem is that man is dead.

Man is the only animal for whom his own existence is a problem which he has to solve.

Love is the only sane and satisfactory answer to the problem of human existence.

Each pattern describes a problem which occurs over and over again in our environment, and then describes the core of the solution to that problem, in such a way that you can use this solution a million times over, without ever doing it the same way twice

Claro es que para trazar un círculo hay que hay que empezar por algún lado, pero una vez cerrado deja de plantearse el problema de su principio.

Divide 10 by 1/2 and add ten. What is the answer?

The problem with troubleshooting is that trouble shoots back.

Or as my dad always says: it only becomes a social problem when the working man joins in.

I walked away with the cheerful step of a police officer who's just made a tricky ethical question somebody else's problem.

says: it only becomes a social problem when the working man joins in.

colloquialism for the affliction that strikes a certain