The crux in implementing a development style for startups is the question of when to use a natural approach versus when to deploy a structured approach. From Fig. in conjunction with overall analysis of the interviews, it seems that for the first few prototypes natural PD processes is likely the best approach, as structure can bring paperwork, extra tasks, and careful evaluation which explains the much longer prototyping time. However, at a certain point in the life cycle of a company, structure can actually accelerate PD by avoiding timely and expensive distractions. Therefore, there is a balancing act that startups must perform to get through prototyping efficiently, having a natural process long enough to move quickly and creatively at first, but bringing in structure soon enough to not waste time in the long run. One CEO explained this tension and his compromise between these two extremes in a hybrid approach: Interviewee: "How important was defining requirements for you?" C.26: "It didn't happen like I sat down and I came up with the requirement. While making the thing it evolved… It's a compromise because you can perfect one design and make sure that it's going to work in [the] first shot. But the other approach is just to do it fast. Okay, let's get it, try it, fix it, fix it."