1
00:00:08,510 --> 00:00:14,500
So what we're going to do now is take the designs that we've created and point them over to envision

2
00:00:14,510 --> 00:00:20,680
and envision is basically a platform that allows you to rapidly prototype your designs.

3
00:00:21,020 --> 00:00:25,910
So you might be thinking why on earth do we need to prototype things out.

4
00:00:26,120 --> 00:00:27,240
And we have redesigns.

5
00:00:27,260 --> 00:00:31,550
Why don't we just go ahead ghostwritten the X code and start building this thing.

6
00:00:31,590 --> 00:00:38,780
So I believe that was a couple really really big reasons that I want to stress to you especially if

7
00:00:38,780 --> 00:00:44,110
you are looking to create your own product or star.

8
00:00:44,390 --> 00:00:51,260
So the first reason is it's really going to help you as a designer but more importantly as the products

9
00:00:51,320 --> 00:00:58,490
owner so by rapid prototyping you're able to see the end goal the tunnel at the end and the end of the

10
00:00:58,490 --> 00:00:59,480
tunnel.

11
00:00:59,600 --> 00:01:04,930
And as your product should be and as it should appear without writing any code.

12
00:01:04,970 --> 00:01:12,950
And what's really cool is that if you get a feel for it in your hand on a device by being prototyped

13
00:01:13,010 --> 00:01:16,550
and you realize that you know maybe this isn't the right place to put this button.

14
00:01:16,670 --> 00:01:23,720
This function is maybe not doesn't feel right or it's not the way it wants to be.

15
00:01:23,720 --> 00:01:29,440
You can always go back to your designs swish things around and wait 15 or 20 minutes.

16
00:01:29,460 --> 00:01:37,880
How in your hand envision or any other around prototyping tool and you can adjust on the fly without

17
00:01:37,880 --> 00:01:39,320
having to write any code.

18
00:01:39,320 --> 00:01:45,350
The second reason which is super important is it gives the feedback you go in for your product much

19
00:01:45,350 --> 00:01:51,620
much quicker and much more efficiently and what I mean by that is you're getting it in the hands of

20
00:01:51,620 --> 00:01:53,960
users in the hands of your target audience.

21
00:01:54,170 --> 00:01:58,720
And they're going to give you some feedback which you can go ahead and just on the fly.

22
00:01:59,330 --> 00:02:05,570
You're always always going to be getting feedback from your product from the day that it is an idea

23
00:02:05,660 --> 00:02:13,360
on a napkin at a restaurant till the day that you either sell your product you know closed doors or

24
00:02:13,370 --> 00:02:17,630
it flops you know whatever whatever it is may be could be an acquisition.

25
00:02:17,630 --> 00:02:21,950
Who knows right from inception all the way to the very end.

26
00:02:21,950 --> 00:02:26,320
You're always going to be getting these feedback loops and you're going to be adjusting on the fly.

27
00:02:26,630 --> 00:02:33,550
And the sooner you start that process the faster you're going to be to a successful product.

28
00:02:33,560 --> 00:02:37,340
So I'll give you an example a quick example.

29
00:02:37,940 --> 00:02:44,950
I know a lot of companies that can skew the rapid prototyping phase or are they just kind of always

30
00:02:44,960 --> 00:02:50,700
over and they don't really take a deep dive into the product and they just start writing code and start

31
00:02:50,710 --> 00:02:57,180
writing code and then the first time that it's in the hands of an actual user it's already fully fresh

32
00:02:57,440 --> 00:03:03,350
fleshed out it's this shiny new product that they've spent six months nine months creating without any

33
00:03:03,350 --> 00:03:04,340
feedback.

34
00:03:04,340 --> 00:03:08,190
And the user will look at it and say why did you do this and why did you do this.

35
00:03:08,180 --> 00:03:15,170
And did you think about this and I've seen the faces of people who spent the better half of a year working

36
00:03:15,170 --> 00:03:18,840
on something and they go wow that's that's a brilliant idea.

37
00:03:19,010 --> 00:03:21,140
When I think of that and here's what happens.

38
00:03:21,140 --> 00:03:27,450
They get stuck in a situation where they can unravel what they've been working on for the past six to

39
00:03:27,450 --> 00:03:34,060
nine months even a year to accommodate something that is clearly a better idea.

40
00:03:34,330 --> 00:03:40,350
All because they skipped the rapid prototyping phase and they jump straight into the code.

41
00:03:40,370 --> 00:03:48,550
I see this happen all the time and they end up putting themselves in an area in a position where they're

42
00:03:48,560 --> 00:03:58,400
choosing the the better of two mediocre decisions and especially if you're building your own product.

43
00:03:58,490 --> 00:04:04,760
You have to start out you're going to want to find the most efficient path will save you the most time

44
00:04:04,760 --> 00:04:10,200
save the most money and put you on the right track as fast as possible for product market fit.

45
00:04:10,220 --> 00:04:18,800
So get the feedback loop started this really is possible really really you know go hard in the paint

46
00:04:20,130 --> 00:04:26,150
house to put it go hard and pay with your rapid prototyping phase with your design phase because once

47
00:04:26,150 --> 00:04:32,240
you start writing code it gets a lot harder to unwire things put them back together and make changes

48
00:04:32,240 --> 00:04:32,880
on the fly.

49
00:04:32,960 --> 00:04:38,090
So the rapid prototyping super important do not skip it.

50
00:04:38,330 --> 00:04:42,100
It's going to be the most efficient in the long run.

51
00:04:46,770 --> 00:04:47,620
What.
