15 | Understanding Prototyping to Learn
Metadata
- Author: The Circuit Breaker
- Full Title: 15 | Understanding Prototyping to Learn
- URL: https://share.snipd.com/episode/aa25f3b7-a76d-42c8-a752-c96067d6fc54
Highlights
The Rolls of Prototypes Summary: There’s different ways in which i like so for example, a milestone prototype is the number one mistakes ha a lot of people make. They go build something and they try to bring it back to management to show them where they’re at. And all they know is how far away they are, nd not how much progress they made. The other part is u start to realize there’s there’s what i call the rolls of prototypes. Transcript: Speaker 1 The other part is u start to realize there’s there’s what i call the rolls of prototypes. In others, a learning prototype, there’s a communication prototype, there’s a milestone prototype. There’s different ways in which i like so for example, a milestone prototype is the number one mistakes ha a lot of people make. They go build something and they try to bring it back to management to show them where they’re at, is they never bring the old prototype and the new prototype to the table to say, here’s the progress we made. They just bring the new one. So nobody and all they know is how far away they are, nd not how much progress they made. (Time 0:00:00)review
Prototyping to Learn Summary: i want to take a deeper dive into one of the skills that you wrote about in your book. prototyping and prototyping to learn is really about this aspect of, like i think ryan singer talks about spiking. Right? So prototyping andotyping to learn connected in the context like, i’m going to build something, or make some or think through something so i can find out what i don’t know right? Transcript: Speaker 2 What i want to do is i want to take a deeper dive into one of the skills that you wrote about in your book. I know we covered in an earlier episode, kind of the broad all of them, but i want to take a deeper dive into one. And i want to take a deeper dive into prototyping to learn. Speaker 1 Ok ibe, one of my favorite topics. Speaker 2 So first, can you just give a, give a brief description of what, what do you mean by prototype? Wa, what does prototyping mean to you? Right? Speaker 1 So prototyping and prototyping to learn connected in the context like, i’m going to build something, or make some or think through something so i can find out what i don’t know, right? And so prototyping to learn is really about this aspect of, like i think ryan singer talks about spiking. (Time 0:01:37)review
Soft Wear Is Very Quick Transcript: Speaker 2 And and what we’d say is, if you’retalkig about one prototype, that’s not prototyping. That’s right. That is very man. That’s manufacturing. That’s right. Tee nothing. That’s not that’s not prototyping. Prototyping should be multiple things, andding, as you have to learn and and very different things, where manufactories building one thing, and mi go to build the same thing. And even with pickles, that still takes a long time, because it’s food, right? But think about soft ware. Soft ware is very quick. I it’s relatively easy with little regulation. So prototyping in that a lot of people just fly by it. Speaker 1 But think of all the mistakes people have made because of so this is where my belief is that if you look at the amount of code that’s generated, so demming would always say, the quality, like, how do we understand the quality of the code? And you start to realize that o night, 80 % of the code that’s generated doesn’t actually end up in the product because nobody’s tot through it. And so thereare, therere very good, some softwer comes were, i’ll say, 80 % of the code ends up in it. And they actually give their engineers way more time to think about what they’re building and why, and they break things down into smaller scopes very, very easily. And so part of this is, right now, you know, soft wear seems easy, but i actually think it’s more of a, a maturity problem of that it’s just easier to build it and try it than actually think about it, because they don’t know how to think much about it. (Time 0:20:37)review
Soft Wear Is Very Quick Transcript: Speaker 2 And and what we’d say is, if you’retalkig about one prototype, that’s not prototyping. That’s right. That is very man. That’s manufacturing. That’s right. Tee nothing. That’s not that’s not prototyping. Prototyping should be multiple things, andding, as you have to learn and and very different things, where manufactories building one thing, and mi go to build the same thing. And even with pickles, that still takes a long time, because it’s food, right? But think about soft ware. Soft ware is very quick. I it’s relatively easy with little regulation. So prototyping in that a lot of people just fly by it. Speaker 1 But think of all the mistakes people have made because of so this is where my belief is that if you look at the amount of code that’s generated, so demming would always say, the quality, like, how do we understand the quality of the code? And you start to realize that o night, 80 % of the code that’s generated doesn’t actually end up in the product because nobody’s tot through it. And so thereare, therere very good, some softwer comes were, i’ll say, 80 % of the code ends up in it. And they actually give their engineers way more time to think about what they’re building and why, and they break things down into smaller scopes very, very easily. And so part of this is, right now, you know, soft wear seems easy, but i actually think it’s more of a, a maturity problem of that it’s just easier to build it and try it than actually think about it, because they don’t know how to think much about it. Speaker 2 So we’re almost up on the listener fatigue timing wichis about 20 minutes. So i want to give you one thing, and it’s gond cand if pish you off a little biim, give you a question that’ going to take yous, it should take you 20 minutes to answer. (Time 0:20:37)review
Prototyping Is More Than Just One Thing, Right? Transcript: Speaker 1 But think of all the mistakes people have made because of so this is where my belief is that if you look at the amount of code that’s generated, so demming would always say, the quality, like, how do we understand the quality of the code? And you start to realize that o night, 80 % of the code that’s generated doesn’t actually end up in the product because nobody’s tot through it. And so thereare, therere very good, some softwer comes were, i’ll say, 80 % of the code ends up in it. And they actually give their engineers way more time to think about what they’re building and why, and they break things down into smaller scopes very, very easily. And so part of this is, right now, you know, soft wear seems easy, but i actually think it’s more of a, a maturity problem of that it’s just easier to build it and try it than actually think about it, because they don’t know how to think much about it. Speaker 2 So we’re almost up on the listener fatigue timing wichis about 20 minutes. So i want to give you one thing, and it’s gond cand if pish you off a little biim, give you a question that’ going to take yous, it should take you 20 minutes to answer. I untill you have to answer it in like, a minute and a half. Got is aumius is a b testing prototyping. Speaker 1 So a b testing is is er. And in te the world i grew up in, a b testing was known as as the theworst way in which to test anything. I think of it is like kindergardeners use a b testing because they don’t actually know how to frame the system. They don’t actually know what else jus. (Time 0:21:12)review