1 00:00:00,000 --> 00:00:09,140 Kevin Mako: Hello, product innovators. Today we learn from one of the biggest CAD software CEOs in the industry on how new 3D design tools are improving hardware startup success. 2 00:00:12,470 --> 00:00:21,510 Narrator: You're listening to the Product Startup Podcast, the show that helps bring your product idea to life by chatting with successful inventors, 3 00:00:21,910 --> 00:00:30,170 Narrator: product developers, and hardware industry professionals. Our goal here is to get to the bottom of what makes a product successful, from initial 4 00:00:30,170 --> 00:00:38,650 Narrator: idea to getting your product on store, shelves. We're taking you step by step to build a functional product and scale your product 5 00:00:38,650 --> 00:00:44,350 Narrator: business. Hosted by Kevin Mako, one of North America's leading experts on hardware development 6 00:00:44,350 --> 00:00:46,050 Kevin Mako: for small product businesses. 7 00:00:46,750 --> 00:00:48,150 Kevin Mako: Now, onto the show. 8 00:00:49,470 --> 00:00:56,870 Kevin Mako: Welcome back, everyone. Today I'm very excited to introduce John McEleney to the show. John is the co-founder of Onshape, a leading cloud-based 9 00:00:56,870 --> 00:01:01,050 Kevin Mako: 3D CAD design software used by almost 2 million product designers worldwide. 10 00:01:02,740 --> 00:01:09,860 Kevin Mako: He was one of the the early innovators at SolidWorks and ended up being CEO there for seven years before eventually founding OnShame. 11 00:01:10,180 --> 00:01:17,820 Kevin Mako: Today, John is going to share some valuable knowledge on what inventors, startups, and small manufacturers can look forward to in modern CAD design tools. 12 00:01:19,420 --> 00:01:28,680 Kevin Mako: And how to best use those tools to get new innovative products to market in an agile way, learning from customers and thus best ensuring product market fit. 13 00:01:28,920 --> 00:01:30,080 Kevin Mako: Now on to the episode. 14 00:01:31,490 --> 00:01:35,090 Kevin Mako: Hey, John, welcome to the show. Great. Thanks for having me. I really appreciate it, Kevin. 15 00:01:35,090 --> 00:01:43,290 Kevin Mako: I'm excited to have you on today to talk about the modern tools of software today, specifically around CAD design and designing new hardware products. 16 00:01:43,710 --> 00:01:48,250 Kevin Mako: I got the chance to meet some of your team members, actually, just a couple of weekends ago at the Make 48 record. 17 00:01:48,370 --> 00:01:54,770 John McEleney: You've got a phenomenal team there. There was just at the event, let alone everything I heard going on at Onshape back home. Yeah, thank you. 18 00:01:54,910 --> 00:01:59,070 John McEleney: You know, as you know, being involved in helping startups and yourself with your 19 00:01:59,070 --> 00:02:02,350 John McEleney: experience, it's really all about the people that you surround yourself when you're building the company 20 00:02:02,350 --> 00:02:07,670 Kevin Mako: because you can't do everything yourself. So building your team and that's wonderful to hear. And I know they had a wonderful time as well. 21 00:02:08,910 --> 00:02:16,330 Kevin Mako: Well, it's great to see you there and supporting the competition. It's on PBS and Amazon Prime and we're a huge fan to make 48 and that whole movement. 22 00:02:16,470 --> 00:02:24,010 Kevin Mako: They actually had me on as a judge for this season five. So I'm very excited for the show to come out in September and we'll see how it goes. Some of your team will be in it too. 23 00:02:24,450 --> 00:02:27,190 Kevin Mako: I'll look forward to seeing it. Great. Give us a bit of a background. 24 00:02:27,410 --> 00:02:37,030 John McEleney: You've got an extensive and incredible history in the CAD design space. How did it all start? And what was the journey along the way? Well, you're very kind. 25 00:02:37,470 --> 00:02:46,090 John McEleney: Well, my background, I'm a mechanical engineer by training. It started at the University of Rochester. One summer, I had an internship at the laboratory for laser energetics. 26 00:02:46,230 --> 00:02:53,830 John McEleney: This is a trillion-watt laser. To give you a perspective, it's about three football fields long. And it's funded by Department of Energy, and it's really about nuclear fusion 27 00:02:53,830 --> 00:03:01,930 John McEleney: research. Vision is splitting atoms, fusion's trying to use the creation of energy through fusing a deterrent tablet with high amounts of energy. 28 00:03:02,370 --> 00:03:07,250 John McEleney: I'm not a high-energy physicist, but that summer I did some design work from beam splitters to 29 00:03:07,250 --> 00:03:11,490 John McEleney: mounts to just standard targeting equipment and stuff like that for all the physicists and optics 30 00:03:11,490 --> 00:03:17,750 John McEleney: people. And the guy I worked for, I think gave me a backhanded compliment. He said, you're kind of better at computers than you are design, aren't you? 31 00:03:17,850 --> 00:03:25,050 John McEleney: And this was sort of circa 1983 where we're still using drawing boards. And so he said, can you help me find a CAD system? 32 00:03:25,230 --> 00:03:31,170 John McEleney: So that summer, I went and researched basically different CAD systems. At the time, PC-based CAD systems were 33 00:03:31,170 --> 00:03:38,510 John McEleney: just starting. And there was literally, in our office, I think we had about 8,000 drawings that were rolled up and laid out and it was kind of a mess. 34 00:03:38,810 --> 00:03:46,030 John McEleney: And so that summer, basically, I helped find a CAD system. I helped find a physical way to store the drawings, put this almost like 3M tape on the top 35 00:03:46,030 --> 00:03:53,470 John McEleney: of the C size, D size, and E size drawings. And then at the same time, there was a product called D-Base, which was the first sort of PC-based database software. 36 00:03:53,510 --> 00:03:59,170 John McEleney: And I wrote an application on top of that. And he came up with a numbering system to figure out the capacitor bay, the targeting area, and kind of 37 00:03:59,170 --> 00:04:05,970 John McEleney: got it organized. So I helped them find a CAD system. organize the drawings and organize the process of how you design. And 40 years later, I'm helping people 38 00:04:05,970 --> 00:04:10,650 John McEleney: find a CAD system, organize the process and change, and make it reduce the kind of heat loss due to friction along the way. 39 00:04:10,830 --> 00:04:19,470 John McEleney: My background from there, I worked as a design engineer at Raytheon, which is a large defense equipment manufacturer here in Boston area. And then I ended up going to 40 00:04:19,470 --> 00:04:24,230 John McEleney: computer vision, which is one of the early CAD pioneers, and was at Computer Vision for many years, 41 00:04:24,330 --> 00:04:32,930 John McEleney: and then ended up joining SolidWorks when we were just about to bring the product to market. We hadn't sold any software yet. No users of. into commercial users of SolidWorks. 42 00:04:33,430 --> 00:04:41,470 John McEleney: In my journey at SolidWorks, I had multiple roles, everything from sales and marketing to building out the whole partner sort of ecosystem, and then ultimately 43 00:04:41,470 --> 00:04:47,270 John McEleney: was the CEO for the last seven years. I took some time off after my father was ill, and I saw 44 00:04:47,270 --> 00:04:54,950 John McEleney: this thing called the Cloud, and it was very fascinating to be early on, this idea that you could get access to computers and rent them at a short time basis. 45 00:04:54,950 --> 00:05:01,110 John McEleney: And I went to the first meet up in Boston. This is when Werner Vogels, the CTO of Amazon, came, and there was probably 30 of us in the room. 46 00:05:01,470 --> 00:05:09,470 John McEleney: And I was amazed at discussions and met a bunch of people. Now, if he was to give a conference in Boston, there'd be 20,000 people there. So it was just sort of very, very early 47 00:05:09,470 --> 00:05:16,750 John McEleney: days. And I realized that's where I wanted to plant my flag and learn about how the computing platforms could change how and what people were doing. 48 00:05:17,110 --> 00:05:24,330 John McEleney: When was this? Around what time? That was around 2007. And so ultimately, I found a couple of people who were working on a very 49 00:05:24,330 --> 00:05:28,830 John McEleney: interesting idea, and join them as a CEO, and the company was called Cloud Switch. And ultimately, 50 00:05:29,530 --> 00:05:33,450 John McEleney: Verizon acquired the company to use it as sort of their platform to get people into their enterprise cloud. 51 00:05:33,710 --> 00:05:41,370 John McEleney: And then after getting the team settled, I ended up very good friends with John Herschick, who I'd met at Computer Vision. John was the founder of SolidWorks. 52 00:05:41,390 --> 00:05:48,150 John McEleney: We had a long history together, and he and our close personal friends. And we were talking about how the world had evolved in product design 53 00:05:48,150 --> 00:05:53,370 John McEleney: and that some of the fundamental problems really need to be re-looked at and addressed. We realized 54 00:05:53,370 --> 00:05:58,290 John McEleney: the care and feeding of these systems was becoming disproportionately kind of more of the effort 55 00:05:58,290 --> 00:06:06,850 John McEleney: of engineers. So people were wasting a lot of time and energy and money, doing things that, quite frankly, with the advent of mobile devices and web browsers, it would 56 00:06:06,850 --> 00:06:12,310 John McEleney: allow us to rethink the whole problem. So John and I, along with some of the original Solworks team, ended up starting 57 00:06:12,310 --> 00:06:17,390 John McEleney: Onshape in the beginning of, I guess it was November 1st, 2012. With the idea that basically we're going 58 00:06:17,390 --> 00:06:20,790 John McEleney: to take everything that we had learned in the past, but take all the current systems that were installed 59 00:06:20,790 --> 00:06:25,950 John McEleney: software and sort of swipe them off the table and start with a clean sheet and say, if you had smart people 60 00:06:25,950 --> 00:06:30,130 John McEleney: who were highly motivated because we wanted to really put a dent in the universe, change how people 61 00:06:30,130 --> 00:06:38,770 John McEleney: worked and could attract the venture capital to be able to fund what we were doing. That's why we started Onshape. And it's motivated by kind of a demographic shift as well. 62 00:06:38,890 --> 00:06:44,710 John McEleney: If you look around most companies, you know, people with hair at my color, which is skin tone or what's left up there, 63 00:06:45,010 --> 00:06:50,770 John McEleney: those types of people are not sort of cloud and digital native. But yet the people in their third 64 00:06:50,790 --> 00:07:00,010 John McEleney: and certainly young engineers coming out of college, you know, this idea of installing software, this idea of kind of, you know, the way in which it currently works with 65 00:07:00,010 --> 00:07:08,790 John McEleney: how people manage information, kind of like a bank bank vault metaphor. Let me check this in and let me check this out. You know, their whole world has been about Google Docs. 66 00:07:08,830 --> 00:07:15,150 John McEleney: Let me shut down my laptop. I don't worry about saving. And I just, you know, really have the freedom to collaborate and share real time with people. 67 00:07:15,170 --> 00:07:25,010 John McEleney: And so we wanted to bring that to the product design space. Because people like you and many of the people that you work with, in the 68 00:07:25,010 --> 00:07:31,770 John McEleney: early days of, you know, when you're, when you're starting a new hardware startup or building new products, it's all about iteration. 69 00:07:32,210 --> 00:07:39,970 John McEleney: It's all about trying to get an iteration of the new device or the new product out so you can get market feedback and you can do mid-course corrections. 70 00:07:40,090 --> 00:07:48,890 John McEleney: So everything we can do to sort of make it faster and easier for people to get that thing, that object in the ultimate 71 00:07:48,890 --> 00:07:56,770 John McEleney: customer's hands and see how. how they use it. See what they like, what the aha moment is, and all of the things that they 72 00:07:56,770 --> 00:08:01,730 Kevin Mako: don't like. They may not tell you, but you have to observe them. So the sooner you can get that 73 00:08:01,730 --> 00:08:07,890 Kevin Mako: in people's hands, the quicker you can go and iterate and make sure that your product actually kind of hits the mark when you ultimately release it. 74 00:08:08,090 --> 00:08:14,650 Kevin Mako: So that's really our motivation for creating Onshape. That's so valuable. And that whole motivation behind it is really key. I can tell you from 75 00:08:14,650 --> 00:08:23,470 Kevin Mako: running a 30-person design firm targeted to hardware startups. It's all about time to market, efficiency, quality of specifications, testing, tweaking, refinement, that 76 00:08:23,470 --> 00:08:29,370 Kevin Mako: whole concept is essentially the software world of agile development brought into the hardware world. I think that's what's changed 77 00:08:29,370 --> 00:08:34,130 Kevin Mako: a lot in design, especially to hardware startups, is the fact that we are looking at product 78 00:08:34,130 --> 00:08:43,410 Kevin Mako: development, not as in hitting the holy grail on the first run, tooling up, getting that production run and sitting on it for 10 years to collect in the money for the sales of it. 79 00:08:43,450 --> 00:08:50,310 Kevin Mako: It's saying let's get a few units to market, test, tweak, and refine. So on that thread, especially with what Onshape's doing 80 00:08:50,310 --> 00:08:59,190 John McEleney: in modern CAD software, I want to go back to that concept that you mentioned in terms of that iteration. How is the software today making that easier for 81 00:08:59,190 --> 00:09:05,150 John McEleney: design firms like ourselves or for designers that are coming up with their own products or just for the industry in general? 82 00:09:05,230 --> 00:09:11,950 John McEleney: There's some very practical things that happen when you're using a cloud native sort of platform 83 00:09:12,750 --> 00:09:13,870 John McEleney: and mobile native. 84 00:09:15,410 --> 00:09:22,130 John McEleney: But to do that, you kind of have to look at the current state of the world. The current state of the world is that people are sending files around to everybody. 85 00:09:22,490 --> 00:09:31,950 John McEleney: And the problem is when you're sending files around to people, and by the way, CAD files are inherently a little more complex than just simple a word document or a simple PDF. 86 00:09:32,630 --> 00:09:40,430 John McEleney: Because many of them have nested files and they're just very fragile. And you have to worry about does the person who's receiving this file that I'm sending them, 87 00:09:40,430 --> 00:09:43,970 John McEleney: are they using the same revision of the software? Are they using the same software as I'm 88 00:09:43,970 --> 00:09:49,430 John McEleney: doing? So it could be that I'm using the same brand of software, but it might not be the same revision. So they might not be able to open it up. 89 00:09:49,550 --> 00:09:55,930 John McEleney: So there's kind of all this overhead that, that quite frankly, when I was in SolidWorks and we did it, we didn't do this intentional. It's 90 00:09:55,930 --> 00:10:04,430 John McEleney: just the only way we could build software, but it's an artifact kind of the platform. And when you have new platforms, it allows you to think differently. So one of the concrete 91 00:10:04,430 --> 00:10:11,850 John McEleney: examples is when a designer's working on something, rather than sending the file to somebody, what you're actually doing is much like in Google Docs, you're sharing a link. 92 00:10:12,770 --> 00:10:18,690 John McEleney: You don't have to worry whether or not the person has a CAD system. They've got the link. They click on it. And there's no software installed. 93 00:10:18,890 --> 00:10:26,330 John McEleney: You literally click on that link and you are actually, whatever your permissions might be that the person is granted to you, you have access to that model. 94 00:10:26,590 --> 00:10:34,090 John McEleney: You might be able to make edits. You might be able to make comments. And if you, the owner, who shared it with somebody, you can change those permissions as time goes on. 95 00:10:34,510 --> 00:10:40,430 John McEleney: So first, you're not worrying about whether they can open it or work with it. Two, you you can control what they can do with. 96 00:10:40,510 --> 00:10:45,690 John McEleney: They may not be able to make changes or they may only be able to edit, comment, and mark up, or they might have full access to it. 97 00:10:46,050 --> 00:10:54,850 John McEleney: And the beauty of these systems is that there is literally no save button in any of these systems because everything is saved as a transaction, which means you 98 00:10:54,850 --> 00:11:03,870 John McEleney: can literally go back to, you know, T0 when you started the design. So the idea of feeling like I'm walking on this 99 00:11:03,870 --> 00:11:10,850 John McEleney: very fine edge and I don't want to break something and you become very cautious and you become a slave to the system. This idea allows you to 100 00:11:10,850 --> 00:11:17,750 John McEleney: radically change things and check things and try things. And so, you know, one of the other benefits, so that's one is sharing. 101 00:11:18,190 --> 00:11:27,190 John McEleney: Two is collaboration how people can comment in real time. I can share a link with you and we both can work on the same model together. And the system will hold together. 102 00:11:27,290 --> 00:11:31,410 John McEleney: You don't have to worry about who can override each other person. And you can see those changes. 103 00:11:32,220 --> 00:11:38,200 John McEleney: The other thing is, you know, I'll just bring up my phone. So I have a regular iPhone. My wife, you know, she likes a bigger phone. 104 00:11:38,600 --> 00:11:45,760 John McEleney: Well, if you were designing in classical systems today, you'd kind of take that design and you'd work on that small phone. 105 00:11:45,920 --> 00:11:52,100 John McEleney: And then if you wanted a bigger version, you'd copy all those files and somebody and start another version of that. And you'd go ahead and make it. 106 00:11:52,280 --> 00:11:56,960 John McEleney: And then all of a sudden you realize with the larger phone, oh, I like this enhancement, you make a modification. 107 00:11:57,000 --> 00:12:02,080 John McEleney: If you want to add that to the small version, you have to go back and redesign it into the smaller version to make the changes. 108 00:12:02,880 --> 00:12:12,020 John McEleney: Much inspired by the software world, the idea. of being able to go and create branches and explore and go and try things, and it doesn't affect 109 00:12:12,020 --> 00:12:16,560 John McEleney: necessarily that main branch. So it allows people literally to start working in parallel. 110 00:12:17,180 --> 00:12:26,680 John McEleney: And if there are things that you like that they've done in the branch, you can merge them in. So it's a really powerful way of getting and breaking down this serial process. 111 00:12:26,960 --> 00:12:33,860 John McEleney: I send you the file, you have the master, make the changes to it, then send it back to me and I'll make changes to it where it's this sort of ping pong back and forth. 112 00:12:34,280 --> 00:12:41,260 John McEleney: Now, people can literally work, and it's almost like a subway map. You can work in parallel, and you can take the things that you want and merge them together. 113 00:12:41,720 --> 00:12:48,400 John McEleney: So very, very powerful of taking serial processes and turning them into powerful parallel processes. 114 00:12:48,800 --> 00:12:57,300 John McEleney: And again, it's all about how do you take that time of design and manufacturing? Because remember, some of these things you want to send out to manufacture right away, you 115 00:12:57,300 --> 00:13:06,000 John McEleney: know, where you want a quick mold or you want a quick prototype, you want to be able to do these things and not work. worry about what happened with the design. 116 00:13:06,100 --> 00:13:11,680 John McEleney: So it's really about being fearless, being agile, making changes, and taking that time 117 00:13:11,680 --> 00:13:16,520 John McEleney: and compressing it so that you can do the most important thing, which is for a startup. 118 00:13:17,000 --> 00:13:25,020 John McEleney: For hardware startups, just like software startups, and trust me, I've lived this, you want to figure out the product market fit. 119 00:13:25,620 --> 00:13:31,160 Kevin Mako: That is to say, whether your product is a software product, a service, or actually a physical 120 00:13:31,820 --> 00:13:37,760 Kevin Mako: device, a physical piece of hardware, what you want to make sure is that when it gets to your 121 00:13:37,760 --> 00:13:42,700 Kevin Mako: intended customer, as they use it, you want to be able to observe them, you want to see what is 122 00:13:42,700 --> 00:13:48,960 Kevin Mako: the aha moment, what is it that they love, what is it that they don't love, so that you can take that and iterate that back into future designs. 123 00:13:49,440 --> 00:13:51,400 Kevin Mako: And so to the extent you can iterate 124 00:13:52,200 --> 00:13:59,040 Kevin Mako: early on, the better chance you are of making sure that the product is the right product for the market when you actually release it for production. 125 00:13:59,420 --> 00:14:04,800 Kevin Mako: This is so powerful. There's a couple big things that come to mind from somebody who runs a design for doing this. First of all, 126 00:14:05,180 --> 00:14:13,500 Kevin Mako: especially for people who are new to the hardware development world, they don't realize how extremely complex all of the different stakeholders pieces 127 00:14:13,500 --> 00:14:21,060 Kevin Mako: are to building a CAD file, doing the initial concepting, then design and engineering, prototyping, subsequent rounds of prototyping, 128 00:14:21,440 --> 00:14:26,460 Kevin Mako: pre-production, production, then as you're saying, continuing to tweak as you get feedback along 129 00:14:26,460 --> 00:14:34,500 Kevin Mako: the way. There are numerous different stakeholders, numerous different designers, numerous, see customers, clients, investors, et cetera, all weighing in on this. 130 00:14:34,820 --> 00:14:38,940 Kevin Mako: So if you can centralize it into one space, which has all of these features that you're 131 00:14:38,940 --> 00:14:43,120 Kevin Mako: mentioning, including tracking revision history and being able to tweak on different branches, 132 00:14:43,640 --> 00:14:47,660 Kevin Mako: it makes the job so much easier for all of the different stakeholders within the design field 133 00:14:47,660 --> 00:14:52,120 John McEleney: to quickly get to market, test, tweak, and refine, which brings me to the second point, 134 00:14:52,380 --> 00:14:57,220 John McEleney: which is so powerful from what you're saying, something that we're a big advocate for on the show, which is the feedback loop. 135 00:14:57,620 --> 00:15:04,440 John McEleney: And that's where we're talking about getting to market, small amount of users, getting that feedback loop and then kicking it back into the system, bringing back in those 136 00:15:04,440 --> 00:15:13,600 John McEleney: stakeholders again to continue to tweak and refine, not just to solve problems, not just to fix issues, but also have to find opportunities because the feedback is 137 00:15:13,600 --> 00:15:22,820 John McEleney: in both directions there, opportunities and problem solving. And if you can do both of those well, that's what creates not just a great product, but a big product brand behind it. 138 00:15:23,200 --> 00:15:30,360 John McEleney: For sure. You know, one of the things I talk about when I talk to people who are in startups 139 00:15:30,360 --> 00:15:39,960 John McEleney: And this applies to people who are doing a service, people who are building software. Most importantly, people who are building things, physically building things, is this idea 140 00:15:39,960 --> 00:15:49,140 John McEleney: of, you know, that iteration, but also the idea of getting it into people's hands so you can observe. Because observation is such an empowering and powerful concept. 141 00:15:49,480 --> 00:15:54,680 John McEleney: So what I often describe is, for those that may have young children in your audience, 142 00:15:55,440 --> 00:15:59,900 John McEleney: and those that don't, they may be able to, they may be, you know, able to reflect back when 143 00:15:59,900 --> 00:16:03,920 John McEleney: they were a child. There was a, there's a children's book that's called, Are You My Mother? 144 00:16:04,420 --> 00:16:10,360 John McEleney: You know, it's about this little bird that falls out of a nest and it goes around in this farmhouse and it goes up to the chicken and says, are you my mother? 145 00:16:10,480 --> 00:16:15,240 John McEleney: And it goes up to the cow and says, are you my mother? And it keeps going around and sort of saying, are you my mother? Are you my mother? 146 00:16:15,660 --> 00:16:25,620 John McEleney: Well, and finally a steam shovel, you know, brings it and puts it back in its nest. Beautiful little story. But product market fit, I break it down into, and 147 00:16:25,620 --> 00:16:32,820 John McEleney: that's really the essence. Does your product solve a problem, delight a user in terms of that person in the market? 148 00:16:33,580 --> 00:16:41,360 John McEleney: That is ultimately what you want to figure out in your product development phase. And so I call it, you know, the kind of that, are you my mother sort of moment? 149 00:16:41,460 --> 00:16:48,940 John McEleney: It's really about shoe leather and observation going around and meeting prospects, meeting people who are potential users of your product and observing how they do it. 150 00:16:48,980 --> 00:16:57,660 John McEleney: So the more you can do that early on, the more you can get those iterations, it's going to allow you. because people are never going to say, oh, I want this. 151 00:16:57,880 --> 00:17:05,860 John McEleney: They're going to talk about the problem they're trying to solve or what they're trying to what they need, not necessarily how to do it. 152 00:17:06,080 --> 00:17:14,460 John McEleney: And that's the role of an entrepreneur and innovator is to be able to translate kind of the observations of what they want back into what the product can do. 153 00:17:14,520 --> 00:17:22,180 John McEleney: I mean, that is how we came up early on. If you go look at the patent for the feature manager, every CAD system today has a feature manager. Okay. 154 00:17:22,380 --> 00:17:30,620 John McEleney: And the left-hand side, it sort of orders the future. It's kind of recipe generator. That was started by Bob Zafonte, John Herschstick, and 155 00:17:30,620 --> 00:17:39,820 John McEleney: Steve Krug. And Steve Krug, you know, he spells CAD with a K. You know, he's a product design, really an observation person. And they 156 00:17:39,820 --> 00:17:44,820 John McEleney: actually went to a person out of Nichols Aircraft that makes manifolds. And they noticed the person 157 00:17:44,820 --> 00:17:49,520 John McEleney: kind of, this may be interesting to your users, but I'll show the story, because every CAD system 158 00:17:49,520 --> 00:17:54,640 John McEleney: uses this. The first thing they noticed is the person, they said, oh, use this, the system at the time 159 00:17:54,640 --> 00:17:59,340 John McEleney: was pro engineer and just model something and just tell us what you're doing. And they were watching this person model. 160 00:18:00,000 --> 00:18:08,520 John McEleney: And the first thing they noticed, they had this big silicon graphics kind of, which was a Unix workstation for those people that don't even know what that is. And they had a big 161 00:18:08,520 --> 00:18:16,160 John McEleney: monitor and they kind of had a big space between kind of where he was sitting and where his monitor was. And the next thing they noticed is he had a big stack of these things. 162 00:18:16,440 --> 00:18:25,120 John McEleney: And what the guy was doing was actually modeling, writing down the feature number because in the early days, and he was laying out these 3M notes in kind of a hierarchical format. 163 00:18:26,100 --> 00:18:35,480 John McEleney: And when he needed to change something and change the structure, he would lift up the 3M note pad and change it around. And afterwards, John, Bob, and Steve were discussing it. 164 00:18:35,620 --> 00:18:43,100 John McEleney: And Steve said, well, it seems to me what the person wants to do is interact with the graphics, but also have some kind of hierarchy to understand how these things 165 00:18:43,100 --> 00:18:49,440 John McEleney: interrelate. And that literally is what came up with the idea of what the feature manager was, Now every CAD system uses. 166 00:18:50,800 --> 00:18:54,380 John McEleney: And nobody would have ever told you, I need a feature manager that does this. 167 00:18:54,720 --> 00:19:01,480 Kevin Mako: And of course, they had many enhancements they wanted afterwards once they understood what it could do. But the original concept and innovation came through observation. 168 00:19:02,140 --> 00:19:09,220 Kevin Mako: And the quicker you can do that, the better. And in the startup world, which is the world I live in and love, you 169 00:19:09,220 --> 00:19:16,560 Kevin Mako: know, when we built our mobile device, we never wrote an ounce of code. We had literally a camera and we had taken some icons that we had printed out. 170 00:19:16,560 --> 00:19:23,540 Kevin Mako: and we had a person sit there and move the little pieces, a paper prototype to move the pieces around to show the actions they'd want to go and do. 171 00:19:24,040 --> 00:19:31,560 Kevin Mako: Our investment was minimal, but it allowed us to see and understand how they wanted to interact with it. And so in the hardware world where all 172 00:19:31,560 --> 00:19:35,780 Kevin Mako: of your users are trying to get things done, the sooner they can get it, even if it's the 173 00:19:35,780 --> 00:19:42,980 Kevin Mako: ugliest prototype ever, but they can get into people's hands to understand the functional part of it, that's valuable for customers. So powerful. 174 00:19:43,300 --> 00:19:46,300 Kevin Mako: Getting units into users' hands. And 175 00:19:46,980 --> 00:19:51,840 Kevin Mako: especially if you can use the software to do this, not only can you do a better job of it because 176 00:19:51,840 --> 00:19:55,480 Kevin Mako: you have more stakeholders collaborating properly, not only do they have all these more advanced 177 00:19:55,480 --> 00:19:57,300 John McEleney: tools, but it's cheaper. 178 00:19:58,120 --> 00:20:06,820 John McEleney: It's simply cheaper to do this now than it was even a few years ago and then exponentially cheaper than it was before that. And you guys were the guys. 179 00:20:06,960 --> 00:20:12,620 John McEleney: That's what's so amazing about having you on the show. You were the guys that came up with some of the early CAD software. 180 00:20:12,740 --> 00:20:15,680 John McEleney: And you created some of the most powerful software on Earth. 181 00:20:16,460 --> 00:20:23,040 John McEleney: Over the last almost 10 years now, you've now created the next evolution of that in Onshape, which is so powerful. 182 00:20:23,200 --> 00:20:28,240 John McEleney: Basically, taking a lot of those tools, making it now enabled on the cloud, which we all love. 183 00:20:28,340 --> 00:20:33,860 John McEleney: We're all big fans of Google Docs and the simple reversion history and all those sorts of things that we've come to know. 184 00:20:34,240 --> 00:20:41,880 John McEleney: And yet it's built into CAD software, which is much more complex, but requires many more stakeholders and a huge degree of complexity in design. 185 00:20:41,880 --> 00:20:47,890 John McEleney: So all of that leads to better products being developed out of the gate and faster, thus cheaper. 186 00:20:48,710 --> 00:20:56,690 John McEleney: Exactly. And oftentimes people say, well, have you just taken kind of what you guys did before and kind of just moved into the cloud? And the short answer is no. 187 00:20:57,590 --> 00:21:05,590 John McEleney: We actually rethought sort of the fundamentals. It's sort of like we understood the language of how people wanted to work is the idea of feature-based modeling. 188 00:21:05,750 --> 00:21:11,830 John McEleney: Why? Because it works. You know, the concept of features makes sense. And that's a lingua franca in the industry. 189 00:21:11,910 --> 00:21:18,570 John McEleney: It doesn't matter which CAD system you use, the idea of extruding and kind of how you make things. These are all things that all engineers understand. 190 00:21:18,970 --> 00:21:24,130 John McEleney: But what we decided to do was to use that as sort of the language or the framework, if you will, 191 00:21:24,470 --> 00:21:34,110 John McEleney: but we rethought how you did it, how you work with people, the concept of multi-body parts and all the fundamentals we ultimately really rethought and redid. 192 00:21:34,530 --> 00:21:40,390 John McEleney: And so, yeah, it's single goal, as we call it agile product design. 193 00:21:40,390 --> 00:21:44,670 John McEleney: That's really what we built this from the beginning to do, is to enable, and you know, 194 00:21:45,150 --> 00:21:49,430 John McEleney: here's the thing, people, people don't understand in the software world, and it's probably true, I 195 00:21:49,430 --> 00:21:59,150 John McEleney: think, a little bit in the hardware world too, which is when you have platform shifts, they enable new levels of innovation that were never possible before. 196 00:21:59,730 --> 00:22:02,790 John McEleney: And I'll take it in the software world, but I'm going to tie it back to the hardware world in a second. 197 00:22:03,350 --> 00:22:12,390 John McEleney: So in the software world, we used to have, you know, main frames and mini computers, and then PCs came out, right? And that's when I started. my career actually is in the PC world. 198 00:22:12,770 --> 00:22:14,690 John McEleney: And it allowed people to do things very differently. 199 00:22:15,350 --> 00:22:20,350 John McEleney: And then all of a sudden you had kind of high-end Unix workstations that allowed you to do really practical solid modeling. 200 00:22:20,750 --> 00:22:29,050 John McEleney: And then you had powerful PCs and windows with a Pentium chip coming out. And that's when we created SolidWorks. And then the next platform shift is Cloud Web and 201 00:22:29,050 --> 00:22:34,850 John McEleney: mobile. And it allows you to do collaboration better. It allows you to share better on permissions, how you manage data. 202 00:22:35,450 --> 00:22:42,590 John McEleney: And interestingly enough that the CAD system in the past used to be just the CAD system was a platform. They were individual productivity tools. 203 00:22:43,090 --> 00:22:47,810 John McEleney: And if people needed the work together, you kind of put this layer of what was called PDM software on top. 204 00:22:48,470 --> 00:22:54,090 John McEleney: And that was sort of the bank metaphor of kind of checking something in, checking something out so people don't step on each other's toes. 205 00:22:54,630 --> 00:23:02,150 John McEleney: And like most good innovations, we kind of inverted that thinking. And we took that management control layer, if you will, and we built it at the core. 206 00:23:02,310 --> 00:23:09,210 Kevin Mako: We built a collaboration and sharing engine, much like Google Docs. And metaphorically, we wrapped the CAD system around it. so we inverted it. 207 00:23:09,960 --> 00:23:18,820 Kevin Mako: Now, why do I say there's a platform shift in the hardware world? Find a piece of hardware today that doesn't have some kind of connected device 208 00:23:18,820 --> 00:23:25,880 Kevin Mako: to it. I mean, sure, there's, of course, physical devices that don't have hardware connected to it. But more and more people are 209 00:23:25,880 --> 00:23:31,400 Kevin Mako: embedding electronics into the hardware and they're building connected devices for all of the obvious reasons. 210 00:23:31,660 --> 00:23:40,920 Kevin Mako: So I would argue that connected devices, smart devices, even what might seem like mundane products, in fact, can benefit by being connected. 211 00:23:41,820 --> 00:23:48,080 Kevin Mako: And that's a new way of thinking about sort of hardware, if you will, because the world is going to expect it. You know, tell me a device 212 00:23:48,080 --> 00:23:51,740 Kevin Mako: that you're going to install that you don't think that should be connected in your household. Like, it's like, hello. 213 00:23:52,520 --> 00:23:58,500 Kevin Mako: You know, yes, there's a whole generation of people that will never connect any of their light switches or the music. And there's a whole other generation that will 214 00:23:58,500 --> 00:24:08,400 Kevin Mako: never have hardware switches without them being connected. Like, and that's, you know, and the connectedness favors sort of the demographics moving forward. Yep, absolutely. 215 00:24:08,520 --> 00:24:15,980 Kevin Mako: I've said it on the show before. I said, look around your room in the next 20 to 30 years. Every single object you see in one way or another is going to have a computer chip in it. 216 00:24:16,060 --> 00:24:22,540 Kevin Mako: It could be very small and light, like telling you when your couch cushion needs to be replaced, or it could be much more extensive like a nest thermostat. 217 00:24:23,040 --> 00:24:28,320 Kevin Mako: But the reality is connected devices are becoming easier and cheaper to work with. Software is merging with hardware. 218 00:24:28,660 --> 00:24:34,100 Kevin Mako: Our physical presence is migrating with the metaverse and digital world more and more frequently, 219 00:24:34,100 --> 00:24:43,960 John McEleney: as we're seeing now in mainstream media. So the reality is hardware and software have to join forces. You need one to have the other and vice versa as we migrate through 220 00:24:43,960 --> 00:24:51,040 John McEleney: this, you know, next arguably kind of industrial revolution or the next product revolution. And that's going to be connected devices. It's already started. 221 00:24:51,240 --> 00:24:58,860 John McEleney: It's already all around us. For sure. It's happening at a rapid rate. And that's why software like Onshape really helps bring all of those pieces together. 222 00:24:59,140 --> 00:25:03,680 John McEleney: I had the pleasure of meeting Greg Brown. I believe he's one of the heads of your product. 223 00:25:04,100 --> 00:25:08,620 John McEleney: There at Onshape, one of the things that I was quite blown away with about the software when I was 224 00:25:08,620 --> 00:25:17,060 John McEleney: learning about it is the fact that you've got all these different plugins and modules that both you're creating internally, but also that users can create. 225 00:25:17,360 --> 00:25:22,780 John McEleney: They can use it internally with their team or they can share it with this global library. So you're almost creating 226 00:25:22,780 --> 00:25:31,840 John McEleney: like a quasi open source platform as well to have all these different unique innovative features that you crowdsource brought into the software and usable by everybody. 227 00:25:31,880 --> 00:25:37,240 John McEleney: That to me is phenomenal because that's the tip of the iceberg of what could potentially expand into thousands and thousands 228 00:25:37,240 --> 00:25:43,120 John McEleney: of options that you didn't even have to think up in the first place. You know, one thing that's, yeah, so thank you. 229 00:25:43,400 --> 00:25:48,580 John McEleney: And you're hinting or you're sort of talking about a fundamental concept called feature script. 230 00:25:49,260 --> 00:25:53,480 John McEleney: And feature script essentially is our language at the core that we built Onshape with. 231 00:25:54,020 --> 00:26:00,500 John McEleney: You know, when we were building Onshape in the very beginning, we had built a prototype and we were sort of kind of growing off of that prototype. 232 00:26:00,500 --> 00:26:09,930 John McEleney: And a brilliant engineer who's part of our team came to us, I'd say about a month after we built 233 00:26:09,930 --> 00:26:14,710 John McEleney: a prototype and we were sort of starting to do some more things with it. And he came to us and he said, I have an idea. 234 00:26:15,010 --> 00:26:19,510 John McEleney: And he came in and sort of laid out his vision of what feature script could be. And that required us. 235 00:26:19,530 --> 00:26:22,290 John McEleney: You know, now it was two months into a three months into kind of this prototype. 236 00:26:23,370 --> 00:26:31,610 John McEleney: And it required us basically to hit the pause button and rewrite the whole core because it's a day zero decision. This is not something you retrofit in. 237 00:26:31,710 --> 00:26:38,650 John McEleney: It's sort of at the core you're going through and saying, okay, this language is how the system is going to be built. 238 00:26:39,090 --> 00:26:46,230 John McEleney: And so it turns out inside of Onshape, all the features that we build are built using FeatureScript. And we publish it. It's open. 239 00:26:46,770 --> 00:26:55,050 John McEleney: And so people can then take the code that we've written and modified it if they want. And it'll be guaranteed to work each revision because FeatureScript is part of the core of 240 00:26:55,050 --> 00:27:03,690 John McEleney: how we built it. This is not like macros or automated features that people have built, which creates sort of geometry in an automated fashion. 241 00:27:04,090 --> 00:27:10,470 John McEleney: This is at the core, you can write your own custom essentially programs and routines. Why did we do that? Well, we did that for a couple of reasons. 242 00:27:11,130 --> 00:27:15,790 John McEleney: In the end, people have a CAD system, but people tend, 243 00:27:15,990 --> 00:27:21,130 John McEleney: it's a general purpose platform, but in general, people tend to have very specific things they're doing. 244 00:27:21,450 --> 00:27:27,610 John McEleney: And if they're doing it over and over again, they might want to automate it. they might want to sort of make things that make sense for their world, 245 00:27:27,730 --> 00:27:35,290 John McEleney: but may not make sense for the world at large and stuff that we would never write ourselves. And so what we've done is built this extensible platform. 246 00:27:35,770 --> 00:27:44,350 John McEleney: And we've extended also to prepackaged applications, much like, you know, these guys have taught us kind of how people deal with apps, right? 247 00:27:44,690 --> 00:27:48,350 John McEleney: You know, the whole app store of view. So our view is that we're building this core platform. 248 00:27:48,470 --> 00:27:57,290 John McEleney: We're making it extensible so you can make your adjustments and modifications that you want for, you know, kind of personalization in terms of automation and modification. 249 00:27:57,710 --> 00:28:04,050 John McEleney: And then on top of that, we have other application partners that work in our ecosystem that people are going to take advantage 250 00:28:04,050 --> 00:28:12,430 John McEleney: of that are, you know, very specific, whether it might be, you know, analysis or manufacturing or a whole host of other kind of applications. 251 00:28:13,110 --> 00:28:21,760 John McEleney: So we think this is sort of the way in which, you know, the next generation and the whole industry is shifting. It's one of these things, and it's my experience 252 00:28:21,760 --> 00:28:24,960 John McEleney: in the software world, but also in just the startup world in general. 253 00:28:25,830 --> 00:28:28,630 John McEleney: Very hard to prove that you're right until you're right. 254 00:28:29,390 --> 00:28:36,870 John McEleney: And there's an element to trust me and you can get some validation, but in the end, you know, it gets proven with adoption. 255 00:28:37,470 --> 00:28:40,190 Kevin Mako: And, you know, we saw it right now. I'm working from my home office today. 256 00:28:41,350 --> 00:28:49,930 Kevin Mako: With COVID, you know, all of a sudden the dedicated hardware that people had, the labs in education space and certainly some large organizations, they had, you know, 257 00:28:49,930 --> 00:28:54,990 Kevin Mako: kind of desktop workstations that had specific graphics cards to run whatever Cad Packers are working on. 258 00:28:55,310 --> 00:29:00,630 John McEleney: People had to try and do remote logins because they couldn't go to the office because of COVID. And it was kind of a disaster. 259 00:29:01,290 --> 00:29:07,690 John McEleney: And certainly in the education space, it was a disaster. They could not get access to the CAD Lab. The CAD Lab had a lock on it and it was shut. 260 00:29:08,450 --> 00:29:15,590 John McEleney: So, you know, we went from, I think, pre-pandemic, around 75, 80,000 educational users to today 261 00:29:15,590 --> 00:29:19,450 John McEleney: we have about 1.7, 1.8 million users. So it was sort of like this. 262 00:29:20,590 --> 00:29:28,030 John McEleney: And, you know, it's obvious why this is beneficial. And by the way, the people are using now, they're not surprised that you can work in a web 263 00:29:28,030 --> 00:29:35,050 John McEleney: browse and it works on mobile because they expect that's the way it should work. So it's very interesting to look at the demographics and look at the perspectives. 264 00:29:35,890 --> 00:29:41,670 John McEleney: So we're excited about what we can do because if in the end we can remove a lot of the friction 265 00:29:41,670 --> 00:29:47,870 John McEleney: about how people design and how they can build things, we know in the end that's going to create value for all of our users. 266 00:29:47,870 --> 00:29:54,870 John McEleney: And if it creates value for people, we'll be rewarded over the long term in terms of kind of the adoption of the user base and growth. 267 00:29:55,270 --> 00:29:59,250 John McEleney: And I think that's a fundamental philosophy that we have, which is, you know, create value 268 00:30:00,030 --> 00:30:03,090 John McEleney: and at the end, you'll be rewarded for the value that you create. 269 00:30:03,830 --> 00:30:09,610 John McEleney: John, much appreciated for all the insight in behind Onshape. How can people find out more about Onshape? 270 00:30:10,070 --> 00:30:16,410 John McEleney: Just given the website, for those that are listening, of course, as always, I'll put all the links in the show notes. But give everyone to wrap up. 271 00:30:16,410 --> 00:30:20,570 John McEleney: And if you have any last minute kind of tips or tricks, then we'll say goodbye. Great. 272 00:30:21,310 --> 00:30:28,650 John McEleney: So go to Onshape.com. There's access to people who can get, you can get access to Onshape. There's all kinds of tutorials, YouTube videos, et cetera, et cetera, et cetera. 273 00:30:29,070 --> 00:30:34,270 John McEleney: For people who are building hardware, I'll give you one startup advice. I'm going to hold this up to my wallet. I'm not saying I'm going to give you money. 274 00:30:35,030 --> 00:30:39,710 John McEleney: But I would say that oftentimes people go and beta test their product and they give it to people 275 00:30:39,710 --> 00:30:45,170 John McEleney: and they say try this, try this to see their observation of how they're going to use it. And that's a good thing to do. 276 00:30:46,540 --> 00:30:52,120 John McEleney: also beta test the wallet see if they're willing to spend money for your for your product and if they 277 00:30:52,120 --> 00:30:56,800 John McEleney: spend money for your product it's important for two reasons you know I'm not saying you can lose money 278 00:30:56,800 --> 00:31:04,780 John McEleney: in the first couple of them that you may have people pay for what you want to see will they open their wallet will they create a PO will they go through and actually 279 00:31:04,780 --> 00:31:12,000 John McEleney: sort of purchase something that's a you know one dollar versus zero dollars versus free is a very different thing so beta test 280 00:31:12,000 --> 00:31:18,620 John McEleney: the wallet as well but make sure iterate and observe that's the key thing in the in the entrepreneur world. I love what you're doing. Keep going. 281 00:31:19,380 --> 00:31:24,820 John McEleney: And thanks for having us. Unshaped wants to be part of this journey as well. And we're here. If you're users have questions, 282 00:31:25,000 --> 00:31:30,540 John McEleney: they can reach out through the links that you're going to provide. John, much appreciate it. Thanks again for joining the show. Great. Have a great day. 283 00:31:31,080 --> 00:31:40,380 Narrator: Thanks for tuning in to this episode of the Product Startup Podcast. The show that teaches you what it really takes to bring your product to market and turn it 284 00:31:40,380 --> 00:31:45,360 Narrator: into a big success. This podcast series is brought to you by Mako Design. 285 00:31:45,840 --> 00:31:50,640 Narrator: and invent, the original and leading firm in North America to provide global caliber 286 00:31:50,640 --> 00:31:57,300 Narrator: in-to-end physical consumer product development to startups, inventors, and small product business clients. 287 00:31:57,540 --> 00:32:03,140 Narrator: If you're looking for product development help on your invention, head over to Mako -design.com. 288 00:32:03,300 --> 00:32:12,260 Narrator: That's M-A-K-O Design dot com for a free consultation from one of Mako Design's four design studios from coast to coast. 289 00:32:12,540 --> 00:32:14,620 Narrator: Thanks for listening and see you next time.