0:00 → 0:10
In a web or mobile product, instead of building a physical prototype, you need to have a low fidelity app or website available for customer feedback.
0:10 → 0:18
What does low fidelity mean? Well, that's just kind of my description of you don't need an entire finished website, but you should at least have a wireframe.
0:18 → 0:24
And if you don't have a wireframe you should at least have a PowerPoint of mock-ups or a flash demo or something
0:24 → 0:30
so people could see not only what you're describing in words, but actually could say, oh, I get it.
0:30 → 0:36
Now remember, don't demo that first. Your goal here is to first understand the problem.
0:36 → 0:42
And I make people sometimes that would like to give demos leave all that stuff home, when you're first having the problem discussion.
0:42 → 0:48
But the minute you get into the - well, with something like this, solving your problem for a web mobile app
0:48 → 0:53
you really want to get feedback on a low fidelity app as quickly as possible.
0:53 → 0:58
And when we teach this as a class, literally, by the second week of the class,
0:58 → 1:05
if you're building a web and mobile app you have to have your site or wireframe up and running so people can actually see it and give you feedback.
1:05 → 1:12
Later on you're gonna build what I call the high fidelity app and that tests your understanding of the solution.
1:12 → 1:20
This actually has most of the features, might not have health files, the graphics might not be complete but a high fidelity app gives you more resolution.
1:20 → 1:25
And while we really didn't like the color, or you know, that button was in the wrong place etc.
1:25 → 1:29
This helps you avoid building products no one wants
1:30 → 1:36
and it maximizes the learning per time spent on the product and on customers.