Robert States | How Engineers Can Thrive in Corporate R&D の全文書き起こし

grows a company, then sells it 00:04:53.129 --> 00:05:06.949 It makes sense that a startup might not be, um, immediately effective at taking something across the finish line, especially at scale and at a high level of, of quality and consistency just by the nature of what a startup is. 00:05:06.949 --> 00:05:13.949 But why, why do you think corporations, larger companies out there, why can't they be innovative like startups? 00:05:15.937 --> 00:05:20.437 Um, because they're busy following a process, you know. 00:05:20.437 --> 00:05:24.687 And I-- And that may-- That's not good or bad, that's just who they are. 00:05:24.728 --> 00:05:28.668 You know, there was, um-- I'm just taking some lessons from the services world and reapplying it. 00:05:28.677 --> 00:05:35.228 So there was, there was these, these books out here, and they talk about like services firms, and there's three kinds of services firms generally. 00:05:35.228 --> 00:05:39.557 It's like expertise, gray hairs, and process-oriented, right? 00:05:39.918 --> 00:05:46.958 So firms, you know, that are expertise in gray hair offer something different than firms that are process-oriented. 00:05:48.038 --> 00:05:50.098 Organizations follow process. 00:05:50.098 --> 00:05:52.168 They value process a lot. 00:05:52.757 --> 00:05:55.927 And when you value process, it sort of cuts off the tails. 00:05:56.028 --> 00:05:58.538 When you cut off the tails, that's where the innovation is, right? 00:06:00.057 --> 00:06:11.387 It-- That's not perfectly true a hundred percent of the time, but I'm gonna say companies are more likely to give you another flavor of what they do or another s- or another revision of what they do than they are to create something new. 00:06:11.387 --> 00:06:12.987 It's very hard to create something new. 00:06:13.718 --> 00:06:26.267 And so just have the horsepower to get it across the finish line, really understand reliability, really under supply-- understand supply chain, know how to sell it, know how to get it to volume, know how to get it through the regulatory pathways. 00:06:27.278 --> 00:06:28.418 where they're strong. 00:06:29.067 --> 00:06:32.778 Innovation, they wanna do it, but I mean, they struggle 00:06:34.440 --> 00:06:43.701 You mentioned earlier that, uh, a lot of these corporations, no matter what it says on the door, they're, they're really risk mitigation companies, which is an interesting way to, to think about it. 00:06:44.071 --> 00:06:46.461 And you have an interesting way of thinking about a lot of things. 00:06:46.540 --> 00:06:59.870 Uh, another idea that you have or, or a principle is the idea of this, the quote unquote real contract between an employee and, and the company, uh, especially in an R&D environment. 00:06:59.880 --> 00:07:04.920 What, what do you mean when you say the real contract between the company and the employee? 00:07:06.480 --> 00:07:21.519 Well, you see it, you know, in the layoffs, and I've seen it throughout my career, and I've been trying to understand, um, you know, 'cause you value individuals and you, you go to work for these big corporations, and I've done it and, you know, and I've enjoyed it and I've got a lot out of it. 00:07:23.180 --> 00:07:27.379 They are super focused on the process, whether they tell you that or not. 00:07:27.620 --> 00:07:32.250 Your managers may be super focused on you, but the company's focused on the process. 00:07:32.740 --> 00:07:35.670 And so when they're focused on the process, they're gonna get that through. 00:07:35.699 --> 00:07:53.901 They're bringing people in and running them through that process and developing over a, a period of time If you think they're hiring you because you stand out technically or you're smart, you're gonna be disappointed because they are-- the ability to hire smart people is common. 00:07:53.971 --> 00:07:55.161 They are all over the place. 00:07:55.161 --> 00:07:56.721 I run across them all the time. 00:07:57.002 --> 00:07:58.922 There's so much wonderful talent out there. 00:08:00.701 --> 00:08:08.281 And so they, they really value people they can put in their system and run it through, and they're gonna manage those costs accordingly. 00:08:08.291 --> 00:08:13.432 And then once you've been there long enough, they're gonna say,"Hey, we've had enough," and they're gonna bring in people behind that. 00:08:15.201 --> 00:08:16.271 That's not a bad thing. 00:08:17.062 --> 00:08:19.172 you know that, you should act accordingly. 00:08:19.242 --> 00:08:21.122 I think there's a real opportunity. 00:08:21.512 --> 00:08:32.371 If you wanna stand out in an organization, you need to develop your own brand in parallel, and your brand has to be able to ha-- go after the same thing that the company's going after. 00:08:32.402 --> 00:08:41.011 So if you're gonna go be, you know, an expert in robotics, go tell the world, go get on committees that are gonna work on the controls. 00:08:41.022 --> 00:08:46.761 Go on committees that are gonna work on human factors, whatever it is, and start developing your brand simultaneously. 00:08:46.761 --> 00:08:59.792 The c-company wants you to do it because they need to be involved, but also build your brand simultaneously that you are now insulated from any decision that that company ever makes because you have now developed a brand that has value. 00:09:00.522 --> 00:09:03.351 so if you go into your employment doing that, you're gonna be great. 00:09:03.351 --> 00:09:05.272 If you go in and just ask them, "What should I do next? 00:09:05.272 --> 00:09:06.172 What should I do next? 00:09:06.182 --> 00:09:07.912 You know, how do I get to the next level? 00:09:07.922 --> 00:09:14.662 How do I get to the next level?" You can have a long, wonderful career, but the odds are not in your favor you get to choose the end 00:09:56.298 --> 00:09:58.288 That's really smart advice. 00:09:58.339 --> 00:10:14.979 I know as, uh, a small business owner myself, when I see that a team member at

Pipeline is aligned with helping, helping me… I guess for me it, it kind of comes down to personally me since we're such a small company. 00:10:14.979 --> 00:10:19.778 But, uh, my focus is keeping the machine going, right? 00:10:19.778 --> 00:10:21.048 Making sure the machine is fed. 00:10:21.069 --> 00:10:23.229 We have enough work for everyone to do. 00:10:23.269 --> 00:10:26.729 The, the families that, that work here are all supported and fed. 00:10:27.259 --> 00:10:30.158 At the end of the day, that's really what, what my focus is. 00:10:30.168 --> 00:10:41.649 So when I see a team member who, who gets that and is helping, not just do great engineering work, but, but helping the business perform well, I will never get rid of that team member, right? 00:10:41.699 --> 00:10:47.259 That's someone who's gonna be here for good a- a- a- as long as they're willing to be here, right? 00:10:48.349 --> 00:10:58.229 How, how often do you think engineers forget that and confuse success with, uh, simply exceptional technical performance? 00:11:01.159 --> 00:11:05.120 Uh, so I wanna compare and contrast a few things about, you know, working for, let's say, you versus a large corporation, 00:11:05.226 --> 00:11:05.617 Yeah 00:11:06.040 --> 00:11:15.279 Um, you know, I'm in the space where, where I'm in private equity, and it's very common that we buy founder-led firms, and our job is to convert them from a founder-led firm to a small cap. 00:11:15.960 --> 00:11:17.519 And that, that's a very interesting play. 00:11:17.519 --> 00:11:22.639 What I find about these people that you value, they're wonderful people, and you definitely want them part of the team. 00:11:23.830 --> 00:11:27.259 But they don't have a lot of reps maybe at making the decisions. 00:11:28.370 --> 00:11:34.350 And so sometimes they, they have a hard time in this environment where they're now part of a small cap, right? 00:11:35.110 --> 00:11:42.990 And there's nothing wrong with that, but that's, that's-- I've seen that behavior, so I spent a lot of time helping them transition through that to, to be successful. 00:11:43.409 --> 00:11:47.990 In big corporations, they might not ever experience something like that. 00:11:48.050 --> 00:11:50.000 They just would have no idea. 00:11:50.899 --> 00:11:56.639 and a lot of times they think that they're the most important part, mo-- cog in the wheel because you know what? 00:11:56.639 --> 00:11:59.800 Everything has to go through me because I'm the, the, the technical person. 00:12:01.330 --> 00:12:04.210 Um, that's not how they view it at the top. 00:12:04.340 --> 00:12:07.200 How they view it at the top is, how are you helping me get there fast? 00:12:07.200 --> 00:12:10.570 And they're-- and they actually the engineering as a given. 00:12:11.690 --> 00:12:13.300 I've seen that a lot. 00:12:13.330 --> 00:12:14.830 It's just a given that's gonna happen. 00:12:15.310 --> 00:12:22.759 And it, it's largely because the decision makers may not understand the technical aspect of it. 00:12:22.759 --> 00:12:25.300 It's, it's actually a nuance to them that they don't understand. 00:12:25.300 --> 00:12:31.450 It's hard for non-technical people to work with technical people and lead them 'cause they, they don't understand the nuance. 00:12:31.450 --> 00:12:37.950 But when you and I are in the details, right, we're paying attention to a lot of details, and we know that these small things really matter. 00:12:39.269 --> 00:12:41.870 it takes a long time to develop that perspective 00:12:42.891 --> 00:12:43.171 Yeah. 00:12:43.870 --> 00:12:52.971 Um, so in, in a, a larger corporate environment At Pipeline, again, we're very different, right? 00:12:52.971 --> 00:12:54.230 Small company here. 00:12:54.591 --> 00:12:57.760 Um, we don't have budgeting seasons, right? 00:12:57.811 --> 00:13:00.221 W- we don't really define a, an annual budget. 00:13:00.230 --> 00:13:00.980 Maybe we should. 00:13:01.021 --> 00:13:04.130 You know, that's a conversation for another time, but we really don't. 00:13:04.161 --> 00:13:06.750 I mean, loosely, of course, we have project budgets, right? 00:13:06.750 --> 00:13:11.021 When there's a project, we quote a qu- a customer, there's a specific budget in place. 00:13:11.021 --> 00:13:12.860 Of course, for a project that, that's true. 00:13:12.860 --> 00:13:17.541 But, you know, generally for the business, we don't really go through formal budgeting seasons. 00:13:17.541 --> 00:13:27.240 But larger corporations do, and you have some unique perspective and insight into what's really going on behind the scenes when, when budgeting season comes around. 00:13:27.240 --> 00:13:34.980 What are some of the decisions and conversations that leadership is having that maybe the engineers don't really see or, or, or appreciate? 00:13:35.697 --> 00:13:36.138 Yeah. 00:13:36.158 --> 00:13:44.618 I mean, I, I, I got a dose of this a few years ago when, you know, we just had this… There's been a lot of layoffs in med tech and pharma in the last, you know, couple years. 00:13:45.317 --> 00:14:02.788 And I saw something recently that just got my attention where the client's organization, say it's a larger company, they, managed, uh, their headcount reduction via-- They looked at their portfolio projects across their enterprise. 00:14:03.927 --> 00:14:14.888 And if there was, let's just say there was 15 major projects going on, they just looked at the three lagging ones, and that's-- And all those people from the VP down to the person who started two weeks ago were let go. 00:14:16.418 --> 00:14:27.028 And it was pretty indiscriminate because somewhere in that line, you could have people that were the best in the company, but it was, they really didn't care because I think the legalese gets in the way. 00:14:28.608 --> 00:14:47.128 I, I, I stepped back and looked at that and I go, "Oh my gosh, the, the, the budgeting process for projects is a zero-sum game." If you have really good people

but it's underfunded, you could end up one of those three out of 15 that are at the bottom and then, you know, you get cut. 00:14:48.207 --> 00:14:59.196 And you have no idea You know, from a certain level down, director level down, maybe, you know, associate director, depending on how they're structured, you have no idea. 00:14:59.196 --> 00:15:10.286 You're coming to work every day, you know, doing your best, and you just happen to be caught up in a project that just had maybe poor leadership at the top or not sufficient budget, and you're out. 00:15:11.995 --> 00:15:16.865 And so you just have to accept that that's what's gonna happen, right? 00:15:16.906 --> 00:15:22.906 And ideally, the luck of the draw, this doesn't happen to you for a long time, and you can build your brand simultaneously. 00:15:23.566 --> 00:15:28.416 But what you see with technical people, particularly engineers, the unemployment rate is like one or 2%. 00:15:29.096 --> 00:15:33.716 I've never seen any of them not land on their feet, go somewhere else, and just be successful, right? 00:15:34.235 --> 00:15:37.956 And so just know that's g- it's just a disruption in your life. 00:15:38.036 --> 00:15:46.406 Uh, but you're-- if you know it could happen and you're prepared and you're building your brand, you might be surprised what happens when you move on to the next role 00:15:47.730 --> 00:15:50.841 Let's talk about that a little more, building your personal brand. 00:15:50.841 --> 00:15:57.630 So you talked about how corporations are-- they're really misc-- risk mitigation, uh, companies or, or organizations. 00:15:57.971 --> 00:16:02.480 And I, I think the same should be true to some extent for the individual as well, right? 00:16:02.480 --> 00:16:05.141 You, you should be mitigating risk for yourself. 00:16:05.760 --> 00:16:18.740 And like you just said, there might be situations in which you just don't have visibility to what's really happening, the conversations going on at the top, and those conversations may greatly impact your, your future, right? 00:16:18.740 --> 00:16:19.801 Near term anyway. 00:16:20.130 --> 00:16:21.221 You might get let go. 00:16:21.221 --> 00:16:24.130 The whole division might get shut down. 00:16:24.661 --> 00:16:30.860 And doesn't matter how good you are or how well you're performing, y-you might just find yourself out of luck in that situation. 00:16:30.860 --> 00:16:33.341 So what can engineers can do? 00:16:33.341 --> 00:16:47.021 What are a, a few practical suggestions that you have that engineers can, can use to build their personal brand so that if the unfortunate thing should happen, they get let go, um, they can get back on their feet as quickly as possible? 00:16:47.922 --> 00:16:49.572 Yeah, I'll start with some extremes. 00:16:49.572 --> 00:16:59.002 I've seen, uh, folks that were prolific in their organization, very much the face of the organization to the rest of the world, whether in industry groups or whatever it is. 00:16:59.481 --> 00:17:06.622 You know, ISO committees, AST committees, or, you know, conferences or industry conferences, everybody knew who they were. 00:17:07.291 --> 00:17:16.311 Those people, whether they did it with intention or not, built their own brand, and I've watched them then leave or retire, and they just get sucked into all these other organizations. 00:17:17.031 --> 00:17:29.551 I talk to them, and they, they're like,"I had no idea." you know, but there's, there's a, you know, there's a basically a case study on, you know, what you should do, whatever is your lane, right? 00:17:29.831 --> 00:17:32.751 First thing, my advice to anybody is only do what you're good at. 00:17:33.291 --> 00:17:35.841 You know, you know, quit being something else. 00:17:35.882 --> 00:17:39.101 Don't emulate me or emulate you if that's not who you are. 00:17:39.541 --> 00:17:43.261 Be who you are, find your lane, and then go. 00:17:43.932 --> 00:17:48.711 And then go-- And there, and then, like, if you can't find a lane, then you picked the wrong career, right? 00:17:48.731 --> 00:17:51.661 You know, it's like just, you know, there's, there's something there for you. 00:17:52.001 --> 00:17:55.261 And then be focused on what is the value, right? 00:17:55.291 --> 00:18:02.841 I've, I've been, you know, in services a long time, had, you know, over $100 million go across my desk where people had to spend money. 00:18:02.971 --> 00:18:04.231 So I understand value, right? 00:18:04.231 --> 00:18:05.641 And you've had money come across your desk. 00:18:05.641 --> 00:18:07.111 You know where the value is, right? 00:18:08.571 --> 00:18:09.701 time on that. 00:18:10.291 --> 00:18:18.821 If you can understand the value of what's being done by your organization and what, and what the value is in the market, out there and be the leader of it. 00:18:19.041 --> 00:18:22.192 And oh, by the way, that company wants you to do it. 00:18:23.031 --> 00:18:25.442 Like, they want you to do it. 00:18:26.101 --> 00:18:27.051 Go do it 00:18:28.586 --> 00:18:33.786 It's, it's a little bit sad in a way that engineers go through all this training, right? 00:18:33.786 --> 00:18:35.256 We're excited to be technical. 00:18:35.256 --> 00:18:45.786 We're excited to be technical problem-solvers, use CAD, you know, prototype things, assemble things, test things, all these things that we, we kind of think of as being an engineer. 00:18:46.146 --> 00:18:49.346 And, and that's great and for sure necessary, right? 00:18:49.656 --> 00:18:54.186 Um, but then there's this other layer, the, the, the financial layer, the business layer. 00:18:54.586 --> 00:19:17.656 And oftentimes I think that engineers, a- and to no fault of their own, because they were never trained like this, and no one ever took them aside and said,"Hey, listen, like, at the end of the day, this is kind of what really matters." But they don't tie their efforts, their technical efforts, to the, the financial outcome, the business

performance of, of the company, right? 00:19:18.016 --> 00:19:31.886 And i- sometimes you get let go anyway, because like you talked about, you know, an entire division might get shut down no matter how good you are, no matter how well you understand the connection between your performance and the business goals. 00:19:32.226 --> 00:19:36.266 But, uh, there, there are probably other situations where you can save yourself. 00:19:36.326 --> 00:19:50.516 Do you have any advice for engineers on, on how to go about connecting those dots between what they're-- the technical problems they are solving and how they affect the bottom line of the company a- and also how to, how to market yourself, right? 00:19:50.526 --> 00:19:58.686 Y- you might, you might understand the connection and know that you understand it, but if your leadership doesn't know that you understand it, well, you might as well not understand it. 00:19:59.634 --> 00:20:17.723 So one of the things that I had to personally focus on, you know, and through the, these trials of, you know, you know, going on 20 some years tw- of consulting is that I had, uh… One day it just dawned on me, 'cause I worked for the biggest companies in the world with the biggest budget in the world, the most talented people and everything they want. 00:20:18.443 --> 00:20:24.323 100% of the clients had problems on 100% of the projects, right? 00:20:24.363 --> 00:20:26.083 And I could just tell you that's the case. 00:20:26.163 --> 00:20:35.053 And so I then viewed, I then went after what is the highest value thing I could do to help them with that? 00:20:37.873 --> 00:20:38.623 And I went after that. 00:20:38.623 --> 00:20:44.373 And I would just tell anybody they need to go after the highest value thing from the thing, the perspective that they see. 00:20:44.753 --> 00:20:58.144 So I see this, and so I then focused on big… I'm a technical person, I'm still fal- solving technical problems, but I went and focused on bigger technical problems, and I solved them. 00:20:59.613 --> 00:21:03.173 And the other thing is, here's a little secret to all of it. 00:21:03.173 --> 00:21:05.153 There's a pattern to it almost always. 00:21:06.303 --> 00:21:13.083 So if you recognize the pattern, you will see it faster than your clients will or the people around you. 00:21:13.803 --> 00:21:16.283 You can be-- You can start predicting it. 00:21:16.703 --> 00:21:23.785 You can get the nickname Nostradamus in your organization Be that person, right? 00:21:23.795 --> 00:21:24.935 That's just one lane. 00:21:24.935 --> 00:21:28.905 But, you know, it probably took me 20 years to figure that out, right? 00:21:29.465 --> 00:21:35.515 But if, if you-- I had to find it out the hard way, and I'm just bouncing off of walls, and then it dawned on me one day. 00:21:35.515 --> 00:21:39.125 But I wish I would've known what I know now, you know, 15 years ago. 00:21:39.555 --> 00:21:41.076 It would've been a lot more effective, right? 00:21:42.086 --> 00:21:50.145 But go seek out that niche-y thing allows you to be an engineer where you can monetize it and it has value in the market. 00:21:51.165 --> 00:21:53.635 And then, uh, you know, I can then tell you all about that. 00:21:53.785 --> 00:21:56.725 So I go, I just go talk to senior leadership now. 00:21:57.145 --> 00:22:02.525 You know, every-- You know, when I first started going off talking to people, I'd have a PowerPoint and this and that, and like, do that anymore. 00:22:03.365 --> 00:22:06.096 I basically tell them what's about to happen and how I know. 00:22:06.925 --> 00:22:14.245 And what the… You know, the interesting part is, is, of course, I got a lot of reps at this now, is they start telling me their stories that match what I'm telling them. 00:22:15.705 --> 00:22:20.015 And at that point, know, you are aligned with their needs. 00:22:20.375 --> 00:22:33.855 "Well, well, what would you do?" And I start making suggestions to them, and that's how you-- then you, you build this career and this demand of your own brand, whatever it happens to be, and then you go down that road 00:22:35.016 --> 00:22:48.856 I wonder, is there a specific story or example that you could share in your own life that illustrates that point where you were able to identify some kind of pattern or that, that niche thing that really moved the needle for the company? 00:22:49.411 --> 00:22:50.531 Oh, right. 00:22:50.661 --> 00:22:56.081 Uh, it-- this one is very universal, and I talk to clients about this a lot. 00:22:56.692 --> 00:23:02.391 You're gonna go endeavor to do this new whatever, and it's a big corporation, so they don't do small things. 00:23:04.101 --> 00:23:10.501 I just ask them, "How many decisions are gonna be made in this project?" You know, let's just say it's 10,000. 00:23:10.501 --> 00:23:11.841 So 10,000. 00:23:12.091 --> 00:23:13.641 How many are you gonna get right the first time? 00:23:15.793 --> 00:23:23.111 If you're really, really, really good, maybe 8,000 And most people are not that good. 00:23:24.451 --> 00:23:29.911 You got 2,000 that are not gonna be right, and that's for a variety of reasons. 00:23:29.911 --> 00:23:31.442 That's not because someone made a mistake. 00:23:31.442 --> 00:23:35.131 Maybe there's a tariff, maybe there's a hurricane, you know, maybe there's a new regulation. 00:23:35.131 --> 00:23:36.381 There's something, right? 00:23:36.531 --> 00:23:37.711 'Cause these go on over time. 00:23:38.581 --> 00:24:06.517 Of those 2,000 remaining, you know, uh, 1,000 of them you probably could solve in an hour or less But just recognize, you know, when you live in the services world, that equals a half a effort here The next 500 you could probably solve in a week or less But that's a long time The next hundred will take a month. 00:24:08.167 --> 00:24:12.817 You get down to the last fifty, and that's twenty to forty percent of your time and budget. 00:24:13.947 --> 00:24:17.947 And right there, they stop me, and

they tell me all their stories. 00:24:18.237 --> 00:24:21.087 As engineers, we go into it thinking that's never gonna happen again. 00:24:21.087 --> 00:24:22.048 That's a one-off. 00:24:23.867 --> 00:24:26.337 But I see it every day. 00:24:27.397 --> 00:24:33.357 And so the way that you impact them is that you talk to them about what is your strategy around recovery? 00:24:36.177 --> 00:24:48.669 You know, and so for the engineers that are listening to this who are thinking about their career If you turn yourself into the hero on projects, you win. 00:24:50.379 --> 00:24:51.439 Go be the hero. 00:24:52.119 --> 00:24:54.459 The hero is knowing how to recover fast. 00:24:56.089 --> 00:24:59.909 The hero is not about being the best at the design because that design will have problems. 00:25:01.389 --> 00:25:08.099 And so, you know, I might have a b-biased point of view, but I'm just telling you, like, there's an infinite appetite for that 00:25:09.866 --> 00:25:20.916 Yeah, there, there are a lot of engineers out there who are technically very good at what they do, but there are not very many engineers out there who are both technically savvy and business savvy who can do both of those things. 00:25:20.916 --> 00:25:24.646 And those people are rare and very valuable. 00:25:24.656 --> 00:25:29.106 So to the extent that you can become one of those people, you're, you're set. 00:25:29.136 --> 00:25:31.146 You're kind of set for your career. 00:25:31.456 --> 00:25:48.736 Um, going back to, to R&D, uh, especially in corporate sit- environments, you, you mentioned, uh, you know, sometimes there might be 15 different, uh, uh, programs going across, uh, a, a company's portfolio and, and maybe three are underperforming and just get cut. 00:25:49.086 --> 00:25:54.406 What, what are some of the common reasons why an R&D program might get cut? 00:25:55.245 --> 00:25:57.565 Uh, because they didn't recover fast enough. 00:25:57.565 --> 00:26:01.975 They had-- See, they, they discover problems often in a serial manner. 00:26:02.955 --> 00:26:24.985 And, you know, when I get a phone call to go help a client, you know, and they're, they're late and over budget and it's not working, you know, it's funny as I'll-- you know, you meet with the team and I ha- like, it, it's, it's sort of a trick question, not intentionally, but I'll ask them, "Well, when's the last time you discovered something new?" And they'll enthusiastically tell you, like, yesterday. 00:26:25.705 --> 00:26:29.265 Because they're like, "Oh, look what this magic engineering I did," and blah, blah, blah, right? 00:26:29.355 --> 00:26:29.985 Okay, great. 00:26:31.346 --> 00:26:38.480 And I said, "Are you done discovering problems?" And oh yeah, that's the last one. 00:26:38.819 --> 00:26:40.159 Now it's-- Right. 00:26:40.250 --> 00:26:47.819 The me- the meantime be- between discovery needs to be about this long, you know, in order to say that you're near and done. 00:26:48.429 --> 00:26:53.919 And, and

so the, the, the problem that a lot of people do is they solve it in a serial manner. 00:26:53.939 --> 00:26:57.959 I go in assuming they're never solved, and how am I managing this risk? 00:26:58.949 --> 00:27:00.889 And then how are you pressure testing these? 00:27:00.899 --> 00:27:05.879 Because, you know, they'll go… You know, there's a lot of momentum in a project'cause they'll go sit in a design review. 00:27:05.889 --> 00:27:09.379 So, you know, you know, working in services, I think in hours, right? 00:27:09.389 --> 00:27:11.309 That's my universal currency is hours. 00:27:11.799 --> 00:27:22.389 And okay, I went and may have to do these 10,000 decisions and, um, you know, I don't know, each one took, you know, 10 hours or something. 00:27:22.389 --> 00:27:24.369 You know, so there's 100,000 hours into this, right? 00:27:24.369 --> 00:27:25.419 'Cause these are big projects. 00:27:26.219 --> 00:27:30.879 you're like-- And then you get, you know, you sit in a design review for one hour with, you know, six experts. 00:27:30.909 --> 00:27:32.839 You, you, you, you can't keep up, right? 00:27:33.439 --> 00:27:43.740 And then I-- A lot of times I'm dealing with, you know, issues in late-stage development, either pre or just immediately past launch, they start scaling up. 00:27:44.509 --> 00:27:52.899 the problems that get the clients are often three sigma and four sigma and five sigma events. 00:27:53.770 --> 00:27:55.180 These edge cases 00:27:55.500 --> 00:27:58.889 that's what grinds everything to a halt, you know. 00:28:00.129 --> 00:28:06.955 And they discover that way too late Good companies don't do that 00:28:09.842 --> 00:28:22.942 Okay, so what you're saying is that one of the primary reasons that R&D programs can get shut down is because they don't have the internal capability to recover fast enough. 00:28:23.502 --> 00:28:25.722 So if you're an engineer and 00:28:25.811 --> 00:28:26.951 often very capable. 00:28:26.961 --> 00:28:27.651 Let me interrupt you. 00:28:27.651 --> 00:28:36.621 They're very capable, the problem is they're discovering in a serial manner and they don't retire risk fast enough, and then they basically run out of time and that they just get yanked 00:28:37.226 --> 00:28:38.006 Yeah, yeah. 00:28:38.176 --> 00:28:40.106 Th-they don't recover fast enough anyway. 00:28:40.706 --> 00:28:50.576 If you're an engineer working in an R&D environment and you want to make sure you're mitigating risk for yourself and your own career, what are some of those telltale signs? 00:28:50.576 --> 00:28:54.046 You know, how do you know if you're not recovering fast enough? 00:28:54.046 --> 00:29:05.006 Or, or are there other signs or patterns that you should be looking out for as indications that, hey, this program might be in danger, and I might need to start thinking about what's next for me? 00:29:06.997 --> 00:29:07.278 Oh. 00:29:10.961 --> 00:29:14.651 If there's a lot of rework loops, a bad sign. 00:29:15.411 --> 00:29:19.821 Um, and you know, if you keep on going back, that, that's a bad sign. 00:29:20.531 --> 00:29:39.871 If you're not seeing enough risk be-- you know, you haven't-- you're not identifying the risk early on, and you're discovering, you know, the methodology is discovered in a certain manner but not try to, try to seek it out fast and have alternative pathways identified early on, it's a problem, right? 00:29:39.871 --> 00:29:41.531 You know, here's a telltale sign for me. 00:29:42.721 --> 00:29:51.692 I'll ask them, like, "What is the reliability of this device?" If they can't tell me what it is right-- If everybody in the organization can't tell me it is off the tip of their tongue, I already sort of know they're in trouble. 00:29:52.331 --> 00:29:59.621 The next thing is, is that, you know, I'm gonna just say, "Well, what is the reliability?" "Well, we'll find out when we test." Ooh, you're in trouble, right? 00:29:59.851 --> 00:30:02.051 You know, you don't hear that a lot, but on occasion, right? 00:30:02.411 --> 00:30:08.731 Or they'll tell me what it is, but they'll say, "We'll verify that in testing." Oh, that's a, that's a problem because that's-- you're getting to late stage. 00:30:08.731 --> 00:30:10.761 Everything's being built up and you're going, right? 00:30:11.841 --> 00:30:24.579 Really good people have reliability models on day one The first thing I do on a complex program is I go build a reliability model, and I then bring in people who have been there and done that 00:30:24.579 --> 00:30:26.109 What can these be? 00:30:26.980 --> 00:30:35.839 then identify those risks, and then, you know, then you send a team off to fill in the-- 'Cause at, at first it's a, you know, it's an educated guess, right? 00:30:35.889 --> 00:30:37.839 Or, you know, it's been there, done that. 00:30:39.119 --> 00:30:40.480 but then I send the team off. 00:30:40.509 --> 00:30:43.949 We need to get these numbers in a hurry, and I need to know this fast. 00:30:45.099 --> 00:30:54.039 If they come back and they can't start hitting the numbers from an engineering perspective, then advising the team, "You need to have a plan B or pivot right now," right? 00:30:54.779 --> 00:31:03.329 a lot of times they just, you know, it's like the end of the movie of "Dumb and Dumber," "So you're saying there's a chance?" So they wanna go off and go do it again, and they wanna go do it again. 00:31:04.379 --> 00:31:08.969 those, you know, maybe they can find an answer, but rarely, right? 00:31:08.980 --> 00:31:10.829 And so when they're saying,"Well, I just need one more. 00:31:10.839 --> 00:31:14.059 I just need one more." Right? 00:31:14.469 --> 00:31:20.429 If you don't know the outcome of what you're about to do, at that point, you know, it's like the odds are not in your favor. 00:31:20.938 --> 00:31:21.298 Yeah 00:31:21.359 --> 00:31:30.419 where you see things get really and specifications get tighter and, you know, there's a lot of OEE problems, you know,

are very low when they're launching. 00:31:30.419 --> 00:31:32.599 It's just, it's, it's just not robust 00:31:33.044 --> 00:31:33.464 Hmm. 00:31:33.524 --> 00:31:34.044 Yes. 00:31:34.714 --> 00:31:36.544 May the odds be ever in your favor. 00:31:36.734 --> 00:31:40.024 Brings to mind a, a ominous voice from a movie. 00:31:40.774 --> 00:31:42.664 Um, uh, let's see. 00:31:42.664 --> 00:31:43.844 I had a, a thought here. 00:31:43.844 --> 00:31:44.524 What was it? 00:31:44.574 --> 00:31:45.204 Oh, right. 00:31:45.974 --> 00:31:59.804 So what, in your experience, leads a product to be a commercial success versus other projects that might be technically successful but not so commercially? 00:32:00.644 --> 00:32:02.623 Oh, it got it across the finish line. 00:32:02.634 --> 00:32:10.873 I it's the-- particularly with the big corporations, it is nobody gets across the finish line with extra gas in the tank. 00:32:10.903 --> 00:32:11.963 They're all wore out. 00:32:12.323 --> 00:32:21.173 And, know, and, and, and so I think that they, they, they basically, they-- the-- they caught lightning in a jar on a few things. 00:32:21.203 --> 00:32:26.573 They, they, they got-- they were able to recover fast enough or-- and they were able to get it to go through. 00:32:26.903 --> 00:32:36.783 But this is where the big corporations sort of shine because if you watch the pattern, all of a sudden it's gone up the ladder, right? 00:32:36.843 --> 00:32:41.203 You now there's a daily call with whoever at the, you know, the very senior level. 00:32:41.833 --> 00:32:44.943 You then see-- because the projects have project teams. 00:32:45.353 --> 00:32:56.963 Even though I work for a company ABC, I'm only… That has a hundred thousand employees, I'm on project team with thirty people, Even though there's another hundred thousand somewhere else, you only got that. 00:32:56.993 --> 00:33:07.513 But when a push comes to shove, what they can do is they can summon another two hundred people, experts in the company, and they come on that project and they get it done. 00:33:08.153 --> 00:33:09.743 That's what happens, right? 00:33:09.743 --> 00:33:11.803 I, I've seen that more often than not. 00:33:12.193 --> 00:33:15.153 In addition to that, that's when they start calling the consultants, right? 00:33:15.894 --> 00:33:16.273 right. 00:33:16.373 --> 00:33:20.923 You know, you-- they, they bring-- Because remember, you're making those ten thousand decisions. 00:33:21.313 --> 00:33:23.563 Well, every decision wasn't made by an expert. 00:33:25.343 --> 00:33:29.203 And, and if you did make every decision by an expert, the project would take too long. 00:33:30.884 --> 00:33:31.993 You just can't do it. 00:33:32.483 --> 00:33:35.693 It would-- You, you just-- It, it would never get done. 00:33:36.384 --> 00:33:40.323 so there's a lot of heuristics and things like that to go into the decision-making process. 00:34:23.023 --> 00:34:25.114 so there's a tad better luck on these. 00:34:25.123

--> 00:34:29.393 You know, there's the resources of the corporation to push these through. 00:34:29.884 --> 00:34:35.284 They start peppering talent, you know, where needed, and they just get all these things across the finish line. 00:34:35.313 --> 00:34:36.364 That's what happens 00:34:37.400 --> 00:34:54.431 So it sounds like you're saying maybe not 100% of the time, but a large portion of the time, the projects and the products that end up being commercial successes were such because the company had enough resources to just throw more people at it, throw more money at it, throw more experts at it, as opposed to, 00:34:54.837 --> 00:34:55.467 game, right? 00:34:55.518 --> 00:34:55.887 It's that 00:34:55.940 --> 00:34:56.360 yeah 00:34:56.427 --> 00:34:57.087 game, right? 00:34:57.377 --> 00:34:59.657 If your project doesn't have the money and resources 00:35:03.608 --> 00:35:03.929 Yeah. 00:35:04.308 --> 00:35:05.889 Either everyone works late or bye-bye 00:35:08.583 --> 00:35:08.873 Right. 00:35:09.333 --> 00:35:10.063 There's a lot of that 00:35:12.889 --> 00:35:19.518 For engineers listening to this who went through the, the traditional engineering, uh, education, right? 00:35:19.518 --> 00:35:41.068 Four-year university, bachelor's or a master's, or heaven forbid, a PhD in engineering, what, what are some of the things that they didn't learn at school, especially around the subjects of budget and finance and, um, uh, commercial KPIs that, that they should really go out and intentionally learn? 00:35:42.569 --> 00:35:46.069 They should know the value of their work. 00:35:48.429 --> 00:35:49.679 I'm gonna do a simple thing. 00:35:49.730 --> 00:35:55.359 I need directions from Cincinnati to where you're at in Arizona, right? 00:35:56.949 --> 00:36:10.369 If I give you turn by turn with every landmark in between, gonna be a, bigger, lar- that's a larger, um, effort compared to if I'm saying, you know, 71 to 80 to whatever, to whatever, and you get there. 00:36:10.839 --> 00:36:15.473 Both those answers are correct They're both correct. 00:36:16.943 --> 00:36:19.513 Sometimes they just need to know if I needed to turn left and right. 00:36:19.623 --> 00:36:23.753 So if you give them this whole thing here, that, that was value not, uh, realized. 00:36:24.563 --> 00:36:28.843 And so I-- with engineers, you have to understand the value of what you're doing. 00:36:29.753 --> 00:36:48.543 you know, as a service provider, what I really had to learn to get, you know, to get the clients to spend money with you and provide value to them is I had to know when did I have to go deep and when did I have to just tell them turn left or right And clients need it all, right? 00:36:48.553 --> 00:36:53.573 So if you're, if you're a highly technical person, you're going deep on these things here all the time. 00:36:54.603 --> 00:36:58.563 But the value is I just need to know left or right, gonna miss. 00:37:00.203 --> 00:37:06.153 And, and if you give them a left

or right and call it in, but they needed more details, you're gonna miss. 00:37:07.603 --> 00:37:11.653 Hone that skill to understand the value of the work that you're providing 00:37:14.082 --> 00:37:19.672 When it comes to things like, yeah, I don't know, y- you get an MBA and you learn about finance, right? 00:37:19.672 --> 00:37:20.722 You learn about revenue. 00:37:20.722 --> 00:37:23.952 You, you learn about gross margins and net income and things like that. 00:37:24.413 --> 00:37:38.712 Uh, are, are there some basic, um, let's, let's call them MBA principles that, that you should understand as an engineer to, to really understand what's going on with your project from, from a, a commercial success standpoint? 00:37:41.199 --> 00:37:52.969 Um, you know, if the company is on a no-fail mission, they're gonna throw all the resources at it, and so learn to be the hero because you can make it in your… You mean, 'cause winning on a big project will accelerate your career in the organization. 00:37:53.119 --> 00:37:56.230 Um, And so I, I think that's part of it. 00:37:56.230 --> 00:38:01.329 But again, go back to understand the value of the decision you're making at the time. 00:38:02.129 --> 00:38:20.379 And I think I, I've run across really talented individuals and client organizations, particularly when you're dealing with problems, and they start telling me about three layers of deep on a nuance that, I've, I've done 100 fail… or excuse me, 1,000 failure projects and it's never been the solution. 00:38:21.239 --> 00:38:22.409 It's never that deep. 00:38:22.809 --> 00:38:28.859 And, you know, and so they then are-- They get frustrated 'cause no one's listening to them. 00:38:29.689 --> 00:38:46.909 They're demonstrating technical excellence to you, but, everybody, you know, I, I'm listening to it and, you know, I'm being nice about it, but I'm like, "That's not it." And they don't understand that value, And so… But it's also hard because I, I have an unfair advantage. 00:38:46.909 --> 00:38:48.849 I, I-- and I'm sufficiently paranoid. 00:38:48.849 --> 00:38:50.279 I've seen it, right? 00:38:50.980 --> 00:38:54.089 And that's the value that I offer that they haven't seen it before. 00:38:54.089 --> 00:39:00.649 So, and then they, they go down these trails and then, you know, take it a step further about technical people. 00:39:00.759 --> 00:39:10.759 I have a problem and I take it and I set it on the table and I to my colleagues or the clients, and I talk to the design guy, and the design tell-- guy tells me it's a design problem. 00:39:11.209 --> 00:39:14.299 I talk to the materials person, and that person tells me it's a material problem. 00:39:14.299 --> 00:39:16.699 I talk to the ops person, it's being made wrong. 00:39:17.059 --> 00:39:20.009 Then you go talk to the human factors person, "Oh, they're just using it wrong," right? 00:39:20.829 --> 00:39:21.529 Who's right? 00:39:24.457 --> 00:39:24.747 Right? 00:39:25.607 --> 00:39:27.897 the

answer is they're probably all correct. 00:39:29.217 --> 00:39:38.107 But the smart one, the one that will advance, is the one that knows h- which one to pull on that gets you to the answer the fastest with the least amount of changes to get it to market. 00:39:38.680 --> 00:39:39.050 Yeah. 00:39:39.201 --> 00:39:39.650 Right 00:39:39.807 --> 00:39:52.197 And if you can do that, you're way ahead, and you understand that there's this rest of the world working around the niche that you work in, and you understand how you fit into the ecosystem, whether it's the technical ecosystem or the business ecosystem. 00:39:53.307 --> 00:40:05.457 Because, you know, 'cause in the end, imagine you have this passion that it's this, and that answer could be true, but that creates a regulatory barrier to get it through, don't appreciate that, you're gonna end up frustrated 00:40:06.232 --> 00:40:06.572 Yeah. 00:40:06.712 --> 00:40:07.022 Yep. 00:40:07.172 --> 00:40:07.902 Great point. 00:40:09.132 --> 00:40:11.112 Okay, well, I think we'll wrap this up here. 00:40:11.152 --> 00:40:19.082 Um, what is something that you are working on, Rob, that you could use some help from the audience on? 00:40:19.122 --> 00:40:31.812 Maybe it's a, a technical question, maybe it's a, a person that you're trying to meet or, or technology that you're trying to ba- bring up, but there are, um, a lot of engineers listening to this episode right now. 00:40:31.812 --> 00:40:38.712 So what, w- uh, for, for those listening, what is something that you hope they could reach out to you and help you with? 00:40:39.727 --> 00:40:57.623 I, I have this, this vision that in the future that specifications will no longer be on a piece of paper, but a digital model And, you know, I, I talk to a lot of people about it, and there's, there's a lot of interest in it, but there are big barriers to getting it done. 00:40:58.643 --> 00:41:10.143 Most people are not willing to risk their career on it, and I get it because the, the system is built around the way it's built today, and if you were a maverick and you don't get it right, it's gonna be a problem 00:41:11.126 --> 00:41:17.547 Now, are, are you referring to what is commonly called model-based definition or something different? 00:41:18.597 --> 00:41:28.327 Uh, what I, what I would really like to see is a, a digital model is a physics-based model of whatever this device is. 00:41:28.377 --> 00:41:31.007 Let's just say, for example, I'll use an auto-injector. 00:41:31.817 --> 00:41:40.627 And everybody puts all these specifications together about how the plunger fits in the barrel and what the spring forces are and what, you know, activation forces are, and those are all fine. 00:41:42.038 --> 00:41:46.317 Um, but I have this perspective from dealing with a lot of failures. 00:41:46.337 --> 00:41:50.757 The first thing I do is I build a model, and then I figure out why it failed. 00:41:52.057 --> 00:41:54.597 And why am I waiting for it to fail to build the model? 00:41:55.717 --> 00:42:21.959 Uh, what I really like to do is have a virtual model every device that where you get the unique constituent components that you then build into a surrogate model that you fire at the end of the line virtually and know that in fact it's gonna be safe on a high reliability device So I like to-- the release criteria that it passes a digital model at the end, whether it's a physics-based model, whatever it is. 00:42:22.919 --> 00:42:24.980 That's, that's where I wanna go. 00:42:24.980 --> 00:42:29.489 And so what I'm looking for is like-minded people that are looking to accomplish that. 00:42:30.080 --> 00:42:30.480 Okay. 00:42:31.230 --> 00:42:31.929 And, 00:42:32.190 --> 00:42:32.890 like, like, 00:42:33.259 --> 00:42:33.559 around it 00:42:34.830 --> 00:42:37.090 like next level simulation. 00:42:37.100 --> 00:42:48.740 Not, not just simple FEA or CFD, but, but something a more advanced that takes into account all the different components at the same time, and maybe even assem- things like assembly. 00:42:49.160 --> 00:42:52.780 Uh, what's the word I'm looking for? 00:42:52.780 --> 00:42:55.510 Assembly process and variation in that process. 00:42:55.510 --> 00:42:57.100 Is, is that what you're referring to? 00:42:57.407 --> 00:42:58.127 Yes, right. 00:42:58.157 --> 00:43:01.777 And, and ba- basically the specification is it passes the digital model 00:43:03.000 --> 00:43:03.310 Yeah 00:43:04.329 --> 00:43:04.669 Right? 00:43:05.000 --> 00:43:06.539 And then you maintain that, right? 00:43:06.799 --> 00:43:16.500 And then there's more and more that can go from there because you can build deterministic models, and then you have things like, you know, these machine learning tools and things like that where you can start building stochastic models. 00:43:17.559 --> 00:43:20.839 And I have this desire to predict recalls. 00:43:21.789 --> 00:43:39.021 And the thesis that I will put out there is, is that when the deterministic models and the stochastic models deviate the probability of a recall goes up because the number one reason I don't know why something works is because I didn't know I needed to know that. 00:43:39.411 --> 00:43:46.431 And if I can force myself to know things There's an opportunity. 00:43:46.851 --> 00:43:54.091 And I think it'll transform, know, how companies work in these silos from oper- R&D to operations, right? 00:43:54.111 --> 00:44:01.071 And, you know, they hand stuff over, they shake hands, and then they say, "I'll see you on the next one," and then they both mumble under their breath as they walk away. 00:44:02.701 --> 00:44:07.031 you know, it doesn't need to be like that, I wanna find people that wanna change that 00:44:07.971 --> 00:44:09.330 We did a project recently. 00:44:09.330 --> 00:44:20.210 This was a, an automated machine that we built for assembly, and the company that came to us did so because there were errors in the manual process. 00:44:20.250 -->

00:44:31.580 It was, uh, it was an assembly operation with some small parts that were intricate and, and, um, and the operators, the, uh, operators' defense, difficult to work with, right? 00:44:31.580 --> 00:44:34.440 They're under a microscope looking at these things, trying to put them together. 00:44:35.190 --> 00:44:42.820 And there were problems, and they didn't catch those problems until the end of the line when all the value had been put into this product. 00:44:43.221 --> 00:44:50.210 So they came back and said, "Okay, we need to build a machine and just automate this so it happens the same way every time." Which, which we did, and it's working great. 00:44:50.560 --> 00:44:59.730 Um, but they spent, you know, whatever it was, six, eight, 10 months before they learned that it was a problem assembling these parts manually. 00:44:59.860 --> 00:45:03.640 And if they had had a model like you're telling-- talking about, right? 00:45:03.640 --> 00:45:14.750 Physics-based model that took into account operator error and process deviations, then they, they presumably could have saved whatever that time was, six, eight, 10 months. 00:45:15.100 --> 00:45:19.990 They still would have had to build an expensive machine, but they would have done it, you know, that much earlier. 00:45:19.990 --> 00:45:23.350 So I can see the value of, uh, a model like that that you're talking about. 00:45:23.620 --> 00:45:23.910 Great. 00:45:23.910 --> 00:45:31.170 Well, anyone listening to this, if you're interested in, in developing something li-like that or working with Rob on it, please reach out. 00:45:31.170 --> 00:45:34.310 Which brings me to the last question of the interview. 00:45:34.320 --> 00:45:36.951 What is the best way for people to get ahold of you, Rob? 00:45:37.745 --> 00:45:39.465 Uh, yeah, I'm prolific on LinkedIn. 00:45:39.495 --> 00:45:40.795 They can reach out to me on LinkedIn. 00:45:40.795 --> 00:45:42.455 I really appreciate the time here. 00:45:42.775 --> 00:45:52.485 And I would just point out, you fit the pattern with the description of that project, you know, and, uh, the… Yeah, it's, it's a very common problem, right? 00:45:52.495 --> 00:45:52.785 So 00:45:52.984 --> 00:45:53.314 Yeah 00:45:53.645 --> 00:45:57.705 that together and, you know, and yeah, I can be reached on LinkedIn anytime 00:45:58.274 --> 00:45:58.864 Wonderful. 00:45:58.904 --> 00:45:59.434 Wonderful. 00:45:59.634 --> 00:46:00.744 Rob, thank you so much. 00:46:00.794 --> 00:46:02.314 Uh, appreciate all the insight. 00:46:02.394 --> 00:46:04.274 Always a pleasure to talk with you. 00:46:04.564 --> 00:46:08.134 And is there anything else that you'd like to go over before we sign off today? 00:46:09.797 --> 00:46:12.247 Uh, no, let's do this again in four more years 00:46:14.410 --> 00:46:14.640 All right. 00:46:14.930 --> 00:46:17.260 Sounds, that's about the, the right cadence, yeah. 00:46:17.600 --> 00:46:19.320 Okay, Rob, thanks again so much 00:46:20.255 --> 00:46:20.905 Take care. 00:46:21.035 --> 00:46:21.495 Thank you