WEBVTT - Human Centric Design and the Mazda CX-30

0:00:04.240 --> 0:00:07.240
<v Speaker 1>Welcome to tech Stuff, a production of I Heart Radios

0:00:07.320 --> 0:00:14.080
<v Speaker 1>How Stuff Works. Hey there, and welcome to tech Stuff.

0:00:14.120 --> 0:00:17.239
<v Speaker 1>I'm your host, Jonathan Strickland, and I'm an executive producer

0:00:17.239 --> 0:00:20.239
<v Speaker 1>with I Heart Radio and I love all things tech

0:00:20.800 --> 0:00:24.279
<v Speaker 1>and today's episode is a special one. So for one thing,

0:00:24.560 --> 0:00:27.680
<v Speaker 1>you're going to get to hear that intro all over

0:00:27.800 --> 0:00:31.600
<v Speaker 1>again in just a second, because this episode is brought

0:00:31.640 --> 0:00:34.519
<v Speaker 1>to you by Mazda. The company invited me to come

0:00:34.560 --> 0:00:37.479
<v Speaker 1>out to the Los Angeles Auto Show in November two

0:00:37.520 --> 0:00:40.879
<v Speaker 1>thousand nineteen to check out their cars and specifically to

0:00:40.920 --> 0:00:43.880
<v Speaker 1>get some hands on time with the c X thirty suv,

0:00:44.400 --> 0:00:47.559
<v Speaker 1>and that included the chance to record an episode on

0:00:47.640 --> 0:00:51.520
<v Speaker 1>the show floor inside a c X thirty. And I

0:00:51.560 --> 0:00:55.600
<v Speaker 1>was talking about the concept of human centric design, specifically

0:00:55.800 --> 0:00:59.280
<v Speaker 1>within the context of designing vehicles and even more specifically

0:00:59.320 --> 0:01:01.760
<v Speaker 1>the c X there. So what you're about to hear

0:01:02.000 --> 0:01:04.959
<v Speaker 1>is the audio from that. It was recorded on Friday,

0:01:05.040 --> 0:01:08.160
<v Speaker 1>November twenty second, two thousand nineteen, from the Mazda booth

0:01:08.200 --> 0:01:11.080
<v Speaker 1>at the l A Auto Show. You will also hear

0:01:11.200 --> 0:01:14.959
<v Speaker 1>some audio from a separate conversation with Dave Coleman, who's

0:01:14.959 --> 0:01:18.880
<v Speaker 1>an engineer at Mazda. He's with their research and development division,

0:01:19.360 --> 0:01:21.760
<v Speaker 1>and he talks in more detail about the kinds of

0:01:21.760 --> 0:01:25.319
<v Speaker 1>decisions that go into creating a specific experience, which is

0:01:25.360 --> 0:01:28.200
<v Speaker 1>kind of at the heart of the philosophy of human

0:01:28.360 --> 0:01:31.039
<v Speaker 1>centric design. There are a couple of other notes I

0:01:31.040 --> 0:01:34.800
<v Speaker 1>want to mention before we jump into this. First is

0:01:34.840 --> 0:01:37.920
<v Speaker 1>that this episode was recorded live in the Los Angeles

0:01:38.000 --> 0:01:41.800
<v Speaker 1>Convention Center, and so it's not going to sound like

0:01:42.040 --> 0:01:46.520
<v Speaker 1>the studio recordings. You'll likely hear a lot of extraneous sounds.

0:01:46.880 --> 0:01:49.960
<v Speaker 1>I even comment on it at one point. Another is

0:01:50.000 --> 0:01:53.080
<v Speaker 1>that you may hear some other familiar voices when we

0:01:53.080 --> 0:01:56.800
<v Speaker 1>get to Dave's discussions because Lauren voege Obama Brain Stuff,

0:01:56.920 --> 0:02:00.240
<v Speaker 1>and and savor Uh and Jack O'Brien and Miles of

0:02:00.240 --> 0:02:03.960
<v Speaker 1>the Daily Zeitgeist we're also there at the show, so

0:02:04.160 --> 0:02:07.200
<v Speaker 1>they are occasionally chatting as well. You might hear their voices,

0:02:07.560 --> 0:02:10.399
<v Speaker 1>and I will be popping in from the studio as

0:02:10.400 --> 0:02:13.919
<v Speaker 1>in from where I'm recording right now a few times

0:02:13.919 --> 0:02:16.720
<v Speaker 1>to help kind of bridge a few gaps between Dave's

0:02:16.720 --> 0:02:20.359
<v Speaker 1>discussions and the episode I recorded. So with all that

0:02:20.560 --> 0:02:24.280
<v Speaker 1>business out of the way, let's hear that intro all

0:02:24.400 --> 0:02:28.639
<v Speaker 1>over again, So take it away past Jonathan. Hey there,

0:02:28.680 --> 0:02:32.400
<v Speaker 1>and welcome to text stuff. I'm your host, Jonathan Strickland.

0:02:32.480 --> 0:02:34.800
<v Speaker 1>I'm an executive producer with my Heart Radio and I

0:02:35.200 --> 0:02:39.400
<v Speaker 1>love all things tech and ladies and gentlemen. I am

0:02:39.520 --> 0:02:43.000
<v Speaker 1>having quite the experience right now. I know a lot

0:02:43.080 --> 0:02:45.600
<v Speaker 1>of you listeners out there. You like to listen to

0:02:45.639 --> 0:02:48.320
<v Speaker 1>me while you're in your car. Well, guess what. I'm

0:02:48.360 --> 0:02:52.079
<v Speaker 1>recording this from inside a Mazda c X thirty at

0:02:52.120 --> 0:02:54.880
<v Speaker 1>the l A Auto Show. Yeah. For once, I'm talking

0:02:54.919 --> 0:02:58.359
<v Speaker 1>to you in a car. Let's just let's just hang

0:02:58.400 --> 0:03:02.160
<v Speaker 1>out together for a while, shall we. So today I

0:03:02.280 --> 0:03:06.760
<v Speaker 1>have the incredible opportunity to talk about the philosophy behind

0:03:06.960 --> 0:03:13.520
<v Speaker 1>human centric design. This is something I've always been fascinated by.

0:03:13.960 --> 0:03:17.919
<v Speaker 1>It's something that applies to all elements of design, no

0:03:17.960 --> 0:03:21.800
<v Speaker 1>matter what you are trying to create. But I'm specifically

0:03:21.800 --> 0:03:24.320
<v Speaker 1>going to talk about it in the context of the

0:03:24.320 --> 0:03:27.320
<v Speaker 1>Masda c X thirty because I happen to be sitting

0:03:27.440 --> 0:03:30.520
<v Speaker 1>in the front seat of one, and it is also comfortable.

0:03:30.600 --> 0:03:32.960
<v Speaker 1>This is actually tri I don't know where you are

0:03:33.040 --> 0:03:35.600
<v Speaker 1>right now, but this seat is really good. So if

0:03:35.640 --> 0:03:37.480
<v Speaker 1>you can talk to Mazda and find out how to

0:03:37.680 --> 0:03:39.800
<v Speaker 1>get the seat in the studio to be just like

0:03:39.880 --> 0:03:43.520
<v Speaker 1>this one. That's great, and if you don't, you're fired. Okay,

0:03:43.560 --> 0:03:48.440
<v Speaker 1>So I want to talk about the general principles behind

0:03:48.440 --> 0:03:50.680
<v Speaker 1>design in the first place, and then we'll narrow it down.

0:03:50.720 --> 0:03:54.360
<v Speaker 1>You guys know how my show goes. So let's say

0:03:54.360 --> 0:03:59.280
<v Speaker 1>you're an engineer and you have defined what goal you're

0:03:59.320 --> 0:04:04.080
<v Speaker 1>going for. You've identified a specific goal that you want

0:04:04.120 --> 0:04:08.480
<v Speaker 1>to achieve. And beyond defining the goal, that's obviously one

0:04:08.480 --> 0:04:12.200
<v Speaker 1>of the first big parts of this process. You need

0:04:12.240 --> 0:04:14.120
<v Speaker 1>to figure out what are your objectives and what are

0:04:14.160 --> 0:04:17.680
<v Speaker 1>your challenges, what are the things standing in your way

0:04:17.720 --> 0:04:21.280
<v Speaker 1>of achieving your goal, and you start to make decisions

0:04:21.560 --> 0:04:24.800
<v Speaker 1>to try and get to your goal as best you can.

0:04:25.480 --> 0:04:29.800
<v Speaker 1>Those decisions can sometimes end up having things that conflict

0:04:29.839 --> 0:04:31.279
<v Speaker 1>with each other. You have to find a way to

0:04:31.360 --> 0:04:36.800
<v Speaker 1>resolve those conflicts and to actually achieve the goal you

0:04:36.839 --> 0:04:40.640
<v Speaker 1>have defined for yourself. This is not necessarily an easy

0:04:40.640 --> 0:04:42.680
<v Speaker 1>thing to do. It's one of the biggest challenges of engineering.

0:04:42.680 --> 0:04:44.760
<v Speaker 1>It's why a lot of the engineers I've talked to

0:04:45.360 --> 0:04:49.520
<v Speaker 1>relish their job. They love the process of sitting down

0:04:50.080 --> 0:04:54.800
<v Speaker 1>and going from concept to reality and all the processes

0:04:54.960 --> 0:04:57.440
<v Speaker 1>that go along with that. Now, some of that can

0:04:57.520 --> 0:04:59.200
<v Speaker 1>end up being a lot of trial and error. A

0:04:59.200 --> 0:05:01.359
<v Speaker 1>lot of it can end up being having to to

0:05:01.440 --> 0:05:04.760
<v Speaker 1>retrace your steps, and if we're all being honest, not

0:05:04.920 --> 0:05:08.840
<v Speaker 1>all of it is super fun. Sometimes you try out

0:05:08.880 --> 0:05:11.440
<v Speaker 1>an idea that you were convinced was going to be

0:05:11.480 --> 0:05:13.880
<v Speaker 1>perfect and then you realize that, oh, you know what,

0:05:13.960 --> 0:05:17.000
<v Speaker 1>it's good, but it just broke everything else. So it's

0:05:17.000 --> 0:05:21.040
<v Speaker 1>a very tough process to actually go through. But once

0:05:21.080 --> 0:05:24.200
<v Speaker 1>you have figured out all the different challenges, you defined

0:05:24.240 --> 0:05:27.679
<v Speaker 1>your objectives, you start to ideate your solutions. You start

0:05:27.720 --> 0:05:30.680
<v Speaker 1>to think, this is the way I think is the

0:05:30.720 --> 0:05:33.720
<v Speaker 1>best for me to achieve the goal, and then how

0:05:33.720 --> 0:05:36.320
<v Speaker 1>do I go about actually making that reality. You go

0:05:36.400 --> 0:05:40.000
<v Speaker 1>through that process, which can be laborious, and then you

0:05:40.040 --> 0:05:42.159
<v Speaker 1>test it and you find out how well you did,

0:05:42.520 --> 0:05:46.440
<v Speaker 1>and maybe it turns out that the solution you have

0:05:47.240 --> 0:05:51.200
<v Speaker 1>is incredible on paper, but in reality it turns out

0:05:51.240 --> 0:05:53.960
<v Speaker 1>to fall short. That's something that actually does happen quite

0:05:53.960 --> 0:05:57.799
<v Speaker 1>a bit in all realms of technology, and I've seen

0:05:57.880 --> 0:06:02.480
<v Speaker 1>this a lot in my uh storied career as a

0:06:02.480 --> 0:06:07.400
<v Speaker 1>technology journalist. You see attempts to try and achieve something

0:06:07.480 --> 0:06:11.400
<v Speaker 1>really revolutionary, let's say, and in the process you might

0:06:11.560 --> 0:06:14.599
<v Speaker 1>end up losing sight of what your initial goal was

0:06:14.600 --> 0:06:16.840
<v Speaker 1>in the first place, which was to deliver something to

0:06:17.480 --> 0:06:21.440
<v Speaker 1>an end user, whoever that may be, that is meaningful

0:06:21.600 --> 0:06:25.480
<v Speaker 1>and and produces a specific result. Maybe that the thing

0:06:25.520 --> 0:06:29.400
<v Speaker 1>you've created works really well again on paper, but that

0:06:29.520 --> 0:06:32.880
<v Speaker 1>it doesn't feel like it works really well when you

0:06:32.880 --> 0:06:36.000
<v Speaker 1>get it in the hands of the end user. That

0:06:36.160 --> 0:06:39.719
<v Speaker 1>is what human centric design tries to address. It tries

0:06:39.760 --> 0:06:43.360
<v Speaker 1>to keep in mind that at the end of the day,

0:06:43.680 --> 0:06:47.480
<v Speaker 1>you are making something to create a human experience, and

0:06:47.520 --> 0:06:52.160
<v Speaker 1>that every decision you make ultimately needs to be geared

0:06:52.279 --> 0:06:55.160
<v Speaker 1>toward that. Also, I'm probably gonna be dropping a lot

0:06:55.160 --> 0:06:59.479
<v Speaker 1>of car puns unintentionally. It's just because I'm in this environment.

0:07:00.240 --> 0:07:05.840
<v Speaker 1>So we've talked about that little element of challenge, this

0:07:05.920 --> 0:07:08.800
<v Speaker 1>idea of trying to, you know, I, identify what your

0:07:08.800 --> 0:07:11.400
<v Speaker 1>goal is and to work your way to it. The

0:07:11.480 --> 0:07:14.000
<v Speaker 1>next thing you have to think about is how your

0:07:14.040 --> 0:07:18.360
<v Speaker 1>goal may end up working with, integrating with other goals

0:07:18.440 --> 0:07:22.560
<v Speaker 1>that other people have, or it may conflict with those Because,

0:07:23.000 --> 0:07:26.320
<v Speaker 1>as I'm sure you're all aware, something like a car,

0:07:26.560 --> 0:07:32.240
<v Speaker 1>a vehicle. Uh, it's actually a collection of many different systems. Now,

0:07:32.280 --> 0:07:36.440
<v Speaker 1>each system needs to contribute toward that end goal, that

0:07:36.560 --> 0:07:40.680
<v Speaker 1>human centric goal where you're creating this feeling that you

0:07:40.720 --> 0:07:45.560
<v Speaker 1>want your end user to have. But they don't necessarily

0:07:45.600 --> 0:07:51.560
<v Speaker 1>all work in harmony together natively. You can't expect that

0:07:51.680 --> 0:07:54.720
<v Speaker 1>if you're working, let's say, on a drive train system

0:07:54.800 --> 0:07:57.520
<v Speaker 1>and someone else is working on a different system, that

0:07:57.560 --> 0:08:00.360
<v Speaker 1>those two are just going to magically work together and

0:08:00.480 --> 0:08:03.800
<v Speaker 1>produce the perfect experience when it all comes out at

0:08:03.840 --> 0:08:06.520
<v Speaker 1>the end. You actually have to do a lot of collaboration,

0:08:06.920 --> 0:08:09.840
<v Speaker 1>and sometimes that means that you're having lots of complicated

0:08:09.880 --> 0:08:14.920
<v Speaker 1>conversations weighing your different goals, weighing your different priorities, and

0:08:15.000 --> 0:08:19.000
<v Speaker 1>deciding which ones are going to take priority in one

0:08:19.000 --> 0:08:21.960
<v Speaker 1>case versus another. You might be able to make some concessions.

0:08:22.040 --> 0:08:24.400
<v Speaker 1>You might be able to kind of find a middle ground.

0:08:24.400 --> 0:08:27.559
<v Speaker 1>You might be able to find use cases where one

0:08:27.760 --> 0:08:32.200
<v Speaker 1>philosophy wins out over another. For example, we had a

0:08:32.280 --> 0:08:35.920
<v Speaker 1>chance to talk with a great engineer, Dave. He talked

0:08:35.960 --> 0:08:39.360
<v Speaker 1>about how with the Masta c X thirty, there was

0:08:39.440 --> 0:08:43.120
<v Speaker 1>this balance between performance and making sure that the ride

0:08:43.160 --> 0:08:46.319
<v Speaker 1>was nice and quiet. And the problem is that as

0:08:46.360 --> 0:08:50.040
<v Speaker 1>you start to weigh one of those, the other one

0:08:50.240 --> 0:08:54.920
<v Speaker 1>begins begins to uh end up having needing more attention.

0:08:55.640 --> 0:08:57.880
<v Speaker 1>So you have to figure out, well, where's the balance here.

0:08:57.920 --> 0:08:59.920
<v Speaker 1>We want to make sure that we have all the

0:09:00.040 --> 0:09:02.640
<v Speaker 1>elements here so that we create the feeling that we

0:09:02.679 --> 0:09:06.520
<v Speaker 1>really want our end users to have. And that is

0:09:06.559 --> 0:09:09.840
<v Speaker 1>not something again that is natively obvious. It means that

0:09:09.920 --> 0:09:13.520
<v Speaker 1>you have to have a lot of conversations, a lot

0:09:13.559 --> 0:09:17.839
<v Speaker 1>of collaboration. Uh. And in the case of Mazda, as

0:09:17.880 --> 0:09:20.120
<v Speaker 1>we learned while we were here at the auto show,

0:09:20.720 --> 0:09:23.920
<v Speaker 1>that ends up being a lot easier because the teams

0:09:24.120 --> 0:09:29.320
<v Speaker 1>are more closely located to one another. They aren't spread

0:09:29.400 --> 0:09:32.720
<v Speaker 1>across the globe where you might have one team working

0:09:32.760 --> 0:09:35.440
<v Speaker 1>completely independently of the others. And then when you bring

0:09:35.480 --> 0:09:38.000
<v Speaker 1>all the systems together, only then do you realize that

0:09:38.080 --> 0:09:41.679
<v Speaker 1>you start seeing these conflicts. Hey, it's Jonathan from the

0:09:41.720 --> 0:09:44.440
<v Speaker 1>booth again. But I just wanted to tell you that

0:09:44.480 --> 0:09:46.640
<v Speaker 1>we're going to take a very quick break and come

0:09:46.800 --> 0:09:56.960
<v Speaker 1>right back to the episode, So don't go anywhere, all right, guys,

0:09:56.960 --> 0:09:59.120
<v Speaker 1>it's Jonathan from the studio again. Now I figured This

0:09:59.200 --> 0:10:01.640
<v Speaker 1>is a great spot to insert some audio that we

0:10:01.760 --> 0:10:05.640
<v Speaker 1>captured with Engineered Dave Coleman that really helps illustrate what

0:10:05.760 --> 0:10:09.959
<v Speaker 1>I was talking about earlier on. In this episode, we're

0:10:09.960 --> 0:10:12.080
<v Speaker 1>going to start with Dave giving us the sort of

0:10:12.400 --> 0:10:15.000
<v Speaker 1>mission statement his team had in mind and how they

0:10:15.000 --> 0:10:18.080
<v Speaker 1>went about trying to achieve it. So I guess at

0:10:18.200 --> 0:10:21.000
<v Speaker 1>a high level, what we're trying to do with this

0:10:21.120 --> 0:10:25.480
<v Speaker 1>car is gets something that is we'll let you do

0:10:25.559 --> 0:10:27.160
<v Speaker 1>kind of just whatever it you want to do, wherever

0:10:27.200 --> 0:10:29.760
<v Speaker 1>you want to go whatever. It's not really specifically tune

0:10:29.800 --> 0:10:32.880
<v Speaker 1>to one particular kind of driving. UM. It's supposed to

0:10:32.880 --> 0:10:36.000
<v Speaker 1>be really sort of natural and easy and capable enough

0:10:36.040 --> 0:10:39.680
<v Speaker 1>to to do whatever hurt you're interested in. UM. So

0:10:39.920 --> 0:10:42.800
<v Speaker 1>we wanted to make it so it's it's comfortable and

0:10:42.880 --> 0:10:45.839
<v Speaker 1>quiet every day, it's efficient, it's fun to drive. When

0:10:45.840 --> 0:10:48.440
<v Speaker 1>you go out on twisty road and you want to

0:10:48.480 --> 0:10:51.640
<v Speaker 1>go to some you know, rock climbing place or hiking

0:10:51.640 --> 0:10:53.760
<v Speaker 1>trail and mountain bike and that's way up some dirt

0:10:53.840 --> 0:10:56.520
<v Speaker 1>road that's really tricky. It's got to off road capability

0:10:56.640 --> 0:10:59.960
<v Speaker 1>to get you there too, and it's balancing all the

0:11:00.320 --> 0:11:03.280
<v Speaker 1>kind of the right way is a big trick. Um.

0:11:03.400 --> 0:11:05.800
<v Speaker 1>We're we've been working on some new sort of off

0:11:05.880 --> 0:11:09.960
<v Speaker 1>road capabilities. It's mostly electronic trickery. UM, and sort of

0:11:10.000 --> 0:11:11.839
<v Speaker 1>had to figure out where we draw the line on

0:11:12.120 --> 0:11:15.080
<v Speaker 1>making our cars taple on offer. We've always been a

0:11:15.120 --> 0:11:18.839
<v Speaker 1>completely on road company. Uh, and so we've we've sort

0:11:18.840 --> 0:11:21.680
<v Speaker 1>of drawn the line that, uh, well, there's a lot

0:11:21.720 --> 0:11:23.440
<v Speaker 1>of stuff you can do to make cars super capable

0:11:23.679 --> 0:11:26.000
<v Speaker 1>offer road that ruins how it drives the rest of

0:11:26.040 --> 0:11:28.720
<v Speaker 1>the time. So we've drawn the line that we won't

0:11:28.760 --> 0:11:30.439
<v Speaker 1>do anything to compromise how it drives on the road,

0:11:31.000 --> 0:11:34.480
<v Speaker 1>but we still want all the capabilities to get places. Um.

0:11:34.679 --> 0:11:37.160
<v Speaker 1>And this is the first car that we've got that's

0:11:37.160 --> 0:11:41.880
<v Speaker 1>got an offer button that changes a bunch of the settings. UM.

0:11:41.880 --> 0:11:44.440
<v Speaker 1>So some of the some of the kind of trick

0:11:45.320 --> 0:11:49.720
<v Speaker 1>stuff that we're doing under the skin. UM. We've got

0:11:49.760 --> 0:11:52.200
<v Speaker 1>our new all the drive system and the G Vectorian

0:11:52.200 --> 0:11:55.720
<v Speaker 1>control system, which is a very weird, subtle thing for

0:11:56.120 --> 0:11:58.920
<v Speaker 1>making the car behave in a way that feels more

0:11:59.000 --> 0:12:03.680
<v Speaker 1>natural to people. UM. So we've I'll start with the

0:12:03.679 --> 0:12:07.400
<v Speaker 1>G factor in control. So, UM, we found that as

0:12:07.400 --> 0:12:10.960
<v Speaker 1>you're driving, the very first moment you make the steering

0:12:10.960 --> 0:12:13.319
<v Speaker 1>input The cars are a little bit Every car is

0:12:13.320 --> 0:12:15.040
<v Speaker 1>a little bit inconsistent about how it makes that first

0:12:15.080 --> 0:12:16.839
<v Speaker 1>bit of the turn. And the reason is because you're

0:12:16.840 --> 0:12:21.400
<v Speaker 1>sitting on these theneumatic tires. It's just a balloon, right Uh.

0:12:21.440 --> 0:12:25.199
<v Speaker 1>And in its straight ahead state, both sidewalls are sort

0:12:25.200 --> 0:12:29.120
<v Speaker 1>of unloaded, and when you corner, one of sidewall goes

0:12:29.160 --> 0:12:31.400
<v Speaker 1>slack and one starts pulling, and that's what's pulling the

0:12:31.440 --> 0:12:33.720
<v Speaker 1>car in the corners. So there's this transition period as

0:12:33.760 --> 0:12:37.600
<v Speaker 1>the car starts to transition into that corner, and that's

0:12:37.640 --> 0:12:40.640
<v Speaker 1>where things are kind of the most nervous for the

0:12:40.720 --> 0:12:42.800
<v Speaker 1>driver's subconscious as they kind of DESI will when do

0:12:42.880 --> 0:12:44.920
<v Speaker 1>I turn and how much do I turn? And once

0:12:44.920 --> 0:12:46.880
<v Speaker 1>you get into the corner and everything feels naturally, you

0:12:47.120 --> 0:12:50.920
<v Speaker 1>figure out what you're doing. But people aren't really consciously nervous.

0:12:51.000 --> 0:12:53.200
<v Speaker 1>But if you watch someone's steering inputs as they turn

0:12:53.240 --> 0:12:55.280
<v Speaker 1>into a corner, a lot of times they turn in

0:12:55.280 --> 0:12:57.280
<v Speaker 1>and back off and adjust a couple of times because

0:12:57.320 --> 0:13:00.439
<v Speaker 1>they get it figured out. Uh. And so designed the

0:13:00.480 --> 0:13:04.560
<v Speaker 1>system to try to attack that subtle problem that people

0:13:04.600 --> 0:13:08.319
<v Speaker 1>didn't know they were doing. Um. And what we do

0:13:08.559 --> 0:13:10.439
<v Speaker 1>is we figured out that we can we can wait,

0:13:10.960 --> 0:13:12.720
<v Speaker 1>but a little bit more weight on the front tires

0:13:12.760 --> 0:13:15.280
<v Speaker 1>just as you turn. Uh. And this is a trick

0:13:15.360 --> 0:13:19.040
<v Speaker 1>that we learned from race driving. Um I used to

0:13:19.080 --> 0:13:22.280
<v Speaker 1>race rally cars racing off road in the gravel, and

0:13:22.679 --> 0:13:24.960
<v Speaker 1>the rally drivers always using the left foot on the brakes.

0:13:25.200 --> 0:13:26.480
<v Speaker 1>You turn the wheel and put a little bit of

0:13:26.800 --> 0:13:28.640
<v Speaker 1>extra weight on the front tires and it makes them

0:13:28.679 --> 0:13:31.600
<v Speaker 1>grab into the into the grab or turn the car. UM.

0:13:31.640 --> 0:13:33.280
<v Speaker 1>A lot of broad racing guys will do this to

0:13:33.360 --> 0:13:34.840
<v Speaker 1>one foot on the gas, one foot on the brake,

0:13:35.080 --> 0:13:36.880
<v Speaker 1>unlike on the street where you're left foots on the

0:13:36.880 --> 0:13:39.920
<v Speaker 1>clutch or just resting. But you've got one on each

0:13:39.920 --> 0:13:42.440
<v Speaker 1>of you can you can constantly adjust the weight balance

0:13:42.440 --> 0:13:44.760
<v Speaker 1>of the car. So we started sort of from that

0:13:44.960 --> 0:13:47.600
<v Speaker 1>idea and tuned it and tuned it and tuned it,

0:13:48.600 --> 0:13:50.680
<v Speaker 1>trying to make it so it's so subtle. You don't

0:13:50.760 --> 0:13:53.680
<v Speaker 1>feel the car slowing down to shift weight under the front,

0:13:53.760 --> 0:13:55.800
<v Speaker 1>but you do feel the response in the way the

0:13:55.840 --> 0:14:01.679
<v Speaker 1>car turns. Um And now we've got a tune. So

0:14:01.960 --> 0:14:04.040
<v Speaker 1>there's steering system. As you turn the wheel, the electric

0:14:04.040 --> 0:14:07.000
<v Speaker 1>power steering knows exactly what the put you're giving it,

0:14:07.160 --> 0:14:10.119
<v Speaker 1>so it looks at the steering speed and that communicates

0:14:10.120 --> 0:14:11.880
<v Speaker 1>with the engine computer and it tells it to reduce

0:14:11.920 --> 0:14:15.280
<v Speaker 1>power just a hair and it dips a little bit

0:14:15.280 --> 0:14:17.120
<v Speaker 1>of extra weight onto the front tires and tightens up

0:14:17.160 --> 0:14:21.760
<v Speaker 1>the tires so they respond more directly. Um, we don't

0:14:21.760 --> 0:14:24.280
<v Speaker 1>have any on off switch for that. They'll never feel it.

0:14:24.000 --> 0:14:25.840
<v Speaker 1>It's it's soon so well that it just kind of

0:14:25.920 --> 0:14:28.960
<v Speaker 1>just feels normal all the time. Right. We've built a

0:14:28.960 --> 0:14:31.440
<v Speaker 1>couple of cars with on off switches for that, and

0:14:31.480 --> 0:14:34.800
<v Speaker 1>it's it's really funny because it's it's it's not super obvious,

0:14:35.440 --> 0:14:38.120
<v Speaker 1>but it's once you kind of pick out what it's doing,

0:14:38.600 --> 0:14:41.240
<v Speaker 1>it actually makes a difference even just driving completely straight ahead,

0:14:41.520 --> 0:14:44.040
<v Speaker 1>because you don't realize is when you're driving straight you're

0:14:44.040 --> 0:14:46.960
<v Speaker 1>making constantly making little corrections, right, and if each one

0:14:47.000 --> 0:14:48.640
<v Speaker 1>of those has a little delay, and then to catch up,

0:14:48.680 --> 0:14:51.720
<v Speaker 1>you're you're constantly overshooting and coming back. And as soon

0:14:51.760 --> 0:14:54.440
<v Speaker 1>as we turn the system on, people just just settle

0:14:54.520 --> 0:14:56.960
<v Speaker 1>up because they make repression and would stick and they

0:14:57.000 --> 0:14:58.360
<v Speaker 1>wouldn't have to make the next one of the next

0:14:58.360 --> 0:15:02.280
<v Speaker 1>one and the next one. Um. So that's in all

0:15:02.280 --> 0:15:06.400
<v Speaker 1>of our cars now. Um that that's called g Vactric control.

0:15:06.440 --> 0:15:09.640
<v Speaker 1>We just came out with the electric control plus which

0:15:09.920 --> 0:15:13.360
<v Speaker 1>helps when you start straighten the wheel back out, um,

0:15:13.440 --> 0:15:17.080
<v Speaker 1>and the the car will sometimes be a little bit

0:15:17.120 --> 0:15:18.920
<v Speaker 1>slow to kind of come backing up the pull wheel

0:15:18.920 --> 0:15:21.680
<v Speaker 1>straight and so to avoid that, we actually will drag

0:15:21.760 --> 0:15:24.600
<v Speaker 1>the outside break just a hair and it suddenly just

0:15:24.680 --> 0:15:26.960
<v Speaker 1>kind of kind of helps it straight back out. You

0:15:26.960 --> 0:15:29.040
<v Speaker 1>don't again, you don't feel a break when you can

0:15:29.040 --> 0:15:30.840
<v Speaker 1>switch it on and off. What you feel is it

0:15:30.920 --> 0:15:33.080
<v Speaker 1>feels soally normal. And then if if you were to

0:15:33.120 --> 0:15:35.800
<v Speaker 1>switch the system off, you feel like steerings kind of

0:15:35.800 --> 0:15:37.800
<v Speaker 1>going yeah, gun, yeah, gun's a good but yeah, it's

0:15:37.800 --> 0:15:39.240
<v Speaker 1>just kind of overdamped and you kind of have to

0:15:39.280 --> 0:15:43.000
<v Speaker 1>pull it back. Um. So we're really kind of down

0:15:43.000 --> 0:15:45.320
<v Speaker 1>in the weeds of these little subtle details to get

0:15:45.360 --> 0:15:49.120
<v Speaker 1>the car to feel natural and to feel totally almost

0:15:49.120 --> 0:15:50.680
<v Speaker 1>so you don't notice all the work we did, right.

0:15:52.240 --> 0:15:55.680
<v Speaker 1>Is there like a general like description drivers have that

0:15:56.040 --> 0:15:58.120
<v Speaker 1>like now that this stuff has been corrected, or do

0:15:58.240 --> 0:16:03.120
<v Speaker 1>they just like say it's smoother, like you know, we've

0:16:03.160 --> 0:16:06.200
<v Speaker 1>always had a focus on this kind of area. Um,

0:16:06.480 --> 0:16:09.120
<v Speaker 1>so we've always sort of tuned our cars to feel

0:16:09.240 --> 0:16:11.120
<v Speaker 1>just feel right and just feel until it used to

0:16:11.160 --> 0:16:13.680
<v Speaker 1>be our slogan decades ago. It just feels right right.

0:16:13.720 --> 0:16:15.760
<v Speaker 1>That's It's we've kind of always been trying to do

0:16:15.800 --> 0:16:20.400
<v Speaker 1>the same thing. Um. So I don't think adding GBC

0:16:20.640 --> 0:16:23.280
<v Speaker 1>wasn't like a dramatic change. Was another tool in our

0:16:23.320 --> 0:16:25.040
<v Speaker 1>toolbox of all these things that we're trying to do.

0:16:25.160 --> 0:16:26.600
<v Speaker 1>If we took this system and put it on the

0:16:26.600 --> 0:16:28.800
<v Speaker 1>car built by people who didn't care about this stuff,

0:16:28.800 --> 0:16:31.280
<v Speaker 1>it wouldn't be enough to pick it right, but it's

0:16:31.360 --> 0:16:34.120
<v Speaker 1>enough to sort of add in our direction of making

0:16:34.120 --> 0:16:39.400
<v Speaker 1>the car, you know, more natural. Um. Sort of our

0:16:39.480 --> 0:16:42.400
<v Speaker 1>our ind goal is to make driving a car so

0:16:43.400 --> 0:16:45.840
<v Speaker 1>naturally you don't think about it. You're just you just drive,

0:16:46.040 --> 0:16:49.080
<v Speaker 1>just do exactly what you wanted to do. Um. The

0:16:49.080 --> 0:16:54.160
<v Speaker 1>whole wheel drive system in this car we mechanically is

0:16:54.200 --> 0:16:56.640
<v Speaker 1>the same as almost everybody's. You drive the front wheels,

0:16:56.880 --> 0:16:58.720
<v Speaker 1>there's a clutch where you can connect the rear wheels

0:16:58.800 --> 0:17:01.440
<v Speaker 1>sometimes when you need it and not when you don't.

0:17:01.880 --> 0:17:03.800
<v Speaker 1>And all the magic is in the software to figure

0:17:03.800 --> 0:17:06.479
<v Speaker 1>out when you need it when you don't exactly how much, right,

0:17:06.520 --> 0:17:09.000
<v Speaker 1>because if you're always driving the rear wheels, it uses

0:17:09.000 --> 0:17:12.159
<v Speaker 1>a lot of extra fuel and it actually UM diffront

0:17:12.200 --> 0:17:13.680
<v Speaker 1>reules have to go to the same speed when they're

0:17:13.720 --> 0:17:15.600
<v Speaker 1>locked together, and so the car doesn't want to turn,

0:17:16.600 --> 0:17:18.880
<v Speaker 1>and so you're always balancing its ability to turn with

0:17:18.920 --> 0:17:23.400
<v Speaker 1>its ability to drive the rear wheels. UM. We've come

0:17:23.440 --> 0:17:26.680
<v Speaker 1>up with a system where we're running software algorithm that's

0:17:26.720 --> 0:17:29.440
<v Speaker 1>basically kind of like a video game algorithm that's looking

0:17:29.480 --> 0:17:33.400
<v Speaker 1>at the vehicle speed and cornering G acceleration G hand

0:17:33.400 --> 0:17:35.760
<v Speaker 1>calculating exactly how much loaders on each tire based on

0:17:35.800 --> 0:17:39.280
<v Speaker 1>the vehicle dynamics model of how this car behaves. And

0:17:39.320 --> 0:17:43.040
<v Speaker 1>so it's constantly calculating what load is on each tire

0:17:43.280 --> 0:17:46.680
<v Speaker 1>and then distributing torque where it's needed to take advantage

0:17:46.680 --> 0:17:50.800
<v Speaker 1>of that UM, which means that this actually can expand

0:17:50.800 --> 0:17:53.520
<v Speaker 1>the performance envelope even on dry paving, not just in

0:17:53.760 --> 0:17:57.960
<v Speaker 1>you know, wet or slippery conditions. UM. And that lets

0:17:58.040 --> 0:18:03.520
<v Speaker 1>us use the OL wild drives to an advantage without

0:18:03.880 --> 0:18:06.119
<v Speaker 1>using it in places but we don't need it waste

0:18:06.160 --> 0:18:10.680
<v Speaker 1>fuel right UM. And then there's a couple of places

0:18:10.720 --> 0:18:12.840
<v Speaker 1>where those two ideas the g vactor control trying to

0:18:12.880 --> 0:18:15.120
<v Speaker 1>get the car turning in precisely, and what the oil

0:18:15.200 --> 0:18:17.880
<v Speaker 1>drive is doing where they don't get along where we're

0:18:18.000 --> 0:18:20.360
<v Speaker 1>If we're driving the rear wheels at a certain time,

0:18:20.680 --> 0:18:23.280
<v Speaker 1>it will make the car resists turning in because they're

0:18:23.280 --> 0:18:25.440
<v Speaker 1>trying to go the same speed. And so we have

0:18:25.560 --> 0:18:27.879
<v Speaker 1>to integrate those two systems so that the g vactor

0:18:27.920 --> 0:18:30.000
<v Speaker 1>control gets the authority right at the moment that it

0:18:30.080 --> 0:18:32.480
<v Speaker 1>needs the car to turn. And then when you're steady state,

0:18:32.520 --> 0:18:34.480
<v Speaker 1>it goes back and sends more to the rear, and

0:18:34.480 --> 0:18:36.440
<v Speaker 1>then it straights back out and can even drag a

0:18:36.480 --> 0:18:38.879
<v Speaker 1>little bit more to the rear to help. So it

0:18:38.920 --> 0:18:41.680
<v Speaker 1>is a really complicated interplayoffs software to get all these

0:18:41.680 --> 0:18:44.120
<v Speaker 1>systems and the cars to talk to each other. Uh.

0:18:44.119 --> 0:18:47.439
<v Speaker 1>And it's it has to to get it to work

0:18:47.840 --> 0:18:51.879
<v Speaker 1>at the speed that our mind is processing things so

0:18:51.920 --> 0:18:55.480
<v Speaker 1>that it feels so that we were really fast in

0:18:55.880 --> 0:18:59.400
<v Speaker 1>what we can recognize, UM. So to to make it

0:18:59.440 --> 0:19:01.680
<v Speaker 1>so we don't feel that it's doing something, but it

0:19:01.760 --> 0:19:03.920
<v Speaker 1>just feels seamless, and it feels like as one unit.

0:19:04.240 --> 0:19:07.160
<v Speaker 1>We had to redo a bunch of the computer hardware

0:19:07.160 --> 0:19:10.600
<v Speaker 1>in the car to communicate faster, to get the signals

0:19:10.600 --> 0:19:13.360
<v Speaker 1>from the steering into the into the thing that makes

0:19:13.359 --> 0:19:15.280
<v Speaker 1>the decisions, and then into the into the e c

0:19:15.440 --> 0:19:18.399
<v Speaker 1>U two from the to change the engine, now putta

0:19:18.480 --> 0:19:22.240
<v Speaker 1>to change the all world drive. Um, if I remember right,

0:19:22.240 --> 0:19:24.879
<v Speaker 1>I think we've got fifty milliseconds from steering input before

0:19:25.000 --> 0:19:26.720
<v Speaker 1>something has to happen at the other end or else

0:19:26.840 --> 0:19:29.640
<v Speaker 1>people will notice. All right, Jonathan from the booth again,

0:19:29.680 --> 0:19:32.960
<v Speaker 1>we're going to rejoin Dave a little further into that

0:19:33.000 --> 0:19:35.400
<v Speaker 1>conversation he had with us. You know, we talked about

0:19:35.400 --> 0:19:37.280
<v Speaker 1>a lot of stuff in that conversation, not all of

0:19:37.320 --> 0:19:40.720
<v Speaker 1>it pertains kind of to this human centric design concept,

0:19:41.160 --> 0:19:42.920
<v Speaker 1>but he gave us a little more insight into the

0:19:43.000 --> 0:19:47.040
<v Speaker 1>challenges behind making the interior of a vehicle quiet without

0:19:47.240 --> 0:19:51.320
<v Speaker 1>making it too quiet. Again, this gets to that concept

0:19:51.440 --> 0:19:54.879
<v Speaker 1>of you want to make an experience for the end user,

0:19:55.320 --> 0:19:57.960
<v Speaker 1>but you have to make sure you're giving the right experience.

0:19:57.960 --> 0:20:01.480
<v Speaker 1>It's not just an experience, but the correct one. So

0:20:01.520 --> 0:20:04.160
<v Speaker 1>we learned there's a very delicate balance to all of that.

0:20:04.440 --> 0:20:08.080
<v Speaker 1>Here's Dave to explain a little further. Hopefully the first

0:20:08.080 --> 0:20:10.760
<v Speaker 1>thing I'll notice is that it's quiet. You know, that

0:20:11.000 --> 0:20:13.159
<v Speaker 1>used to be a weak point of ours. Because well, again,

0:20:13.720 --> 0:20:16.560
<v Speaker 1>steering handling and n VH guys are fighting each farther,

0:20:16.680 --> 0:20:18.520
<v Speaker 1>and we always wanted our cars to handle really well

0:20:18.560 --> 0:20:21.520
<v Speaker 1>and sort of trying to elevate ourselves to the point

0:20:21.560 --> 0:20:23.200
<v Speaker 1>where we can have the steering handling and have the

0:20:23.240 --> 0:20:26.080
<v Speaker 1>car drive right and still be quite uncomfortable. I'm recognizing

0:20:26.080 --> 0:20:29.399
<v Speaker 1>how important that is. UM. We've sort of expanded our

0:20:29.560 --> 0:20:34.800
<v Speaker 1>our performance envelope and a lot of looking at sort

0:20:34.800 --> 0:20:37.680
<v Speaker 1>of how people hear things, what frequency ranges matter to them,

0:20:37.680 --> 0:20:40.720
<v Speaker 1>and what how it actually affects people. Um. And one

0:20:40.720 --> 0:20:43.040
<v Speaker 1>of the things we've started figure out is that we're

0:20:43.119 --> 0:20:47.840
<v Speaker 1>super sensitive to direction of sound, which means that if

0:20:47.880 --> 0:20:50.040
<v Speaker 1>you hear, if the sound does get into the car

0:20:50.680 --> 0:20:53.240
<v Speaker 1>and then uh, you hear reflect off the other window,

0:20:53.240 --> 0:20:57.000
<v Speaker 1>you'll pick up that reflection, maybe not consciously, but it

0:20:57.080 --> 0:20:59.639
<v Speaker 1>bothers you more than that same amount of noise just

0:20:59.680 --> 0:21:03.359
<v Speaker 1>coming one high. So we put more damping into the

0:21:03.359 --> 0:21:05.639
<v Speaker 1>car so that found from do get in damp out quickly.

0:21:05.840 --> 0:21:11.480
<v Speaker 1>It should be good for recording, right right. UM. And

0:21:11.560 --> 0:21:14.760
<v Speaker 1>we've also worked really a lot on isolation from outside noises,

0:21:14.800 --> 0:21:16.480
<v Speaker 1>so you don't hear the car next to you so much,

0:21:16.800 --> 0:21:19.440
<v Speaker 1>and that We're trying to strack a balance because if

0:21:19.480 --> 0:21:24.560
<v Speaker 1>you isolate too much, it's you don't practical reason became

0:21:24.640 --> 0:21:27.280
<v Speaker 1>the Siren's But also at a more subtle level, you

0:21:27.480 --> 0:21:31.320
<v Speaker 1>don't feel connected to what you're doing well, and you

0:21:31.480 --> 0:21:33.480
<v Speaker 1>you feel like you're not really controlling the car. You're

0:21:33.520 --> 0:21:36.320
<v Speaker 1>driving a video game, like you don't feel We want

0:21:36.359 --> 0:21:39.200
<v Speaker 1>to hear the road and feel the road just enough

0:21:39.440 --> 0:21:42.560
<v Speaker 1>to feel connected and not enough to be annoyed. And

0:21:42.680 --> 0:21:45.119
<v Speaker 1>that's the same with outside noises, like you want to

0:21:45.119 --> 0:21:47.520
<v Speaker 1>know that car is there, but you don't want to

0:21:47.840 --> 0:21:50.440
<v Speaker 1>know exactly what's wrong with his brakes. Jonathan, run the

0:21:50.440 --> 0:21:53.080
<v Speaker 1>boot one more time. Another thing that Dave said that

0:21:53.119 --> 0:21:55.919
<v Speaker 1>I wanted to share was about how the team worked

0:21:56.320 --> 0:21:58.600
<v Speaker 1>on the sound system for the Maths to See X

0:21:58.640 --> 0:22:03.080
<v Speaker 1>thirty and they did to put the sub whiffers in

0:22:03.119 --> 0:22:06.680
<v Speaker 1>a very special section of the vehicle and move it

0:22:06.720 --> 0:22:09.479
<v Speaker 1>away from the traditional place, which is within the doors.

0:22:09.960 --> 0:22:12.280
<v Speaker 1>And in order to do that, they had to communicate

0:22:12.320 --> 0:22:16.040
<v Speaker 1>and collaborate with the safety team to make sure that

0:22:16.080 --> 0:22:18.880
<v Speaker 1>this design element they wanted to include would be factored

0:22:18.880 --> 0:22:21.720
<v Speaker 1>into the structure of the vehicle from the very beginning.

0:22:21.960 --> 0:22:25.080
<v Speaker 1>Here's what Dave had to say. One of the kind

0:22:25.080 --> 0:22:28.919
<v Speaker 1>of trick ways that we improve the noise, the outside

0:22:28.960 --> 0:22:32.000
<v Speaker 1>noise isolation in this car and improved the audio quality

0:22:32.080 --> 0:22:34.639
<v Speaker 1>in the car was taking the big speakers out of

0:22:34.640 --> 0:22:38.600
<v Speaker 1>the doors. Everyone has their their subs in the door, right,

0:22:38.640 --> 0:22:42.320
<v Speaker 1>because that's whether you have enough room for Um, that's

0:22:42.320 --> 0:22:47.200
<v Speaker 1>a really inefficient place for a driver. Uh, in terms

0:22:47.200 --> 0:22:49.480
<v Speaker 1>of the space of the car. It's it's driving the

0:22:49.760 --> 0:22:52.840
<v Speaker 1>sounding that volume in the long spot. Um. And it

0:22:52.880 --> 0:22:56.560
<v Speaker 1>also is a noise path from the outside, right. So um,

0:22:56.720 --> 0:23:00.320
<v Speaker 1>we moved them up into the under the dash in

0:23:00.480 --> 0:23:03.760
<v Speaker 1>sort of in the corner of the room. Because anytime

0:23:03.800 --> 0:23:05.359
<v Speaker 1>you corner a load of speaker, the sound quality is

0:23:05.359 --> 0:23:07.520
<v Speaker 1>a lot better, right. Um. So it's a much more

0:23:07.560 --> 0:23:09.159
<v Speaker 1>efficient way to get sound in the car. So if

0:23:09.160 --> 0:23:11.080
<v Speaker 1>we don't have to put as much power in to

0:23:11.240 --> 0:23:15.200
<v Speaker 1>get a better sound quality at the people's ears. Um.

0:23:15.240 --> 0:23:19.479
<v Speaker 1>But also let's to steal off those doors. Um. This

0:23:19.560 --> 0:23:22.120
<v Speaker 1>is something I think everybody understood should be done. It's

0:23:22.119 --> 0:23:24.720
<v Speaker 1>incredibly hard to do because the corners of the of

0:23:24.840 --> 0:23:29.080
<v Speaker 1>the interior are actually a really critical crash structure and

0:23:29.119 --> 0:23:32.000
<v Speaker 1>there's a lot of there's a lot of other departments

0:23:33.080 --> 0:23:36.000
<v Speaker 1>buying for for real estate there right, Because the if

0:23:36.040 --> 0:23:38.760
<v Speaker 1>you crash into something, the load from the bumper goes

0:23:38.800 --> 0:23:40.720
<v Speaker 1>into the frame rails, which go right back into that

0:23:40.760 --> 0:23:42.600
<v Speaker 1>corner of the car, and that's where the load has

0:23:42.640 --> 0:23:45.159
<v Speaker 1>to stop crumpling things. We want everything in front of

0:23:45.160 --> 0:23:47.960
<v Speaker 1>the windshield to crumple and everything inside not too. And

0:23:48.000 --> 0:23:52.679
<v Speaker 1>so that's a really strong structural corner. So normally you

0:23:52.720 --> 0:23:55.240
<v Speaker 1>develop a car, you develt a crash structure first and

0:23:55.240 --> 0:23:58.239
<v Speaker 1>then everybody gets to work on after those. And we

0:23:58.280 --> 0:24:00.879
<v Speaker 1>had to get this concept of trying to move the

0:24:00.880 --> 0:24:04.640
<v Speaker 1>speakers up into the corners before we started the platform development,

0:24:05.119 --> 0:24:07.679
<v Speaker 1>to say, hey, crash guys, you have a space for

0:24:07.680 --> 0:24:10.240
<v Speaker 1>the speaker while you're doing that, and build that concept

0:24:10.320 --> 0:24:13.160
<v Speaker 1>in all right, and and so it was a really

0:24:13.680 --> 0:24:16.680
<v Speaker 1>sort of big accomplishment for us to pull off logistically.

0:24:17.480 --> 0:24:19.400
<v Speaker 1>Dave was a lot of fun to talk to, and

0:24:19.480 --> 0:24:22.639
<v Speaker 1>he helped us understand how these decisions to craft a

0:24:22.680 --> 0:24:29.479
<v Speaker 1>specific experience manifest in actual real world decisions and engineering choices. Now,

0:24:29.560 --> 0:24:32.679
<v Speaker 1>these are things I typically take for granted. Whenever I

0:24:32.800 --> 0:24:36.639
<v Speaker 1>use a product, I generally only think, you know, something like, wow,

0:24:36.720 --> 0:24:39.360
<v Speaker 1>this thing is really easy to use or wow, this

0:24:39.440 --> 0:24:42.080
<v Speaker 1>is a lot of fun, or sometimes on the flip side,

0:24:42.119 --> 0:24:45.520
<v Speaker 1>because not everything is positive. Sometimes I think, who the

0:24:45.520 --> 0:24:47.920
<v Speaker 1>heck thought this was a good design choice? Is so

0:24:48.000 --> 0:24:51.600
<v Speaker 1>inconvenient it's hard to get to. If you ever had

0:24:51.600 --> 0:24:54.919
<v Speaker 1>a user interface where you've had to navigate, you know,

0:24:55.040 --> 0:24:58.080
<v Speaker 1>five steps beyond what you thought would be necessary, you

0:24:58.119 --> 0:25:00.280
<v Speaker 1>know what I'm talking about. It's it ends up being

0:25:00.680 --> 0:25:05.520
<v Speaker 1>so frustrating that it actually creates a disincentive for you

0:25:05.640 --> 0:25:09.640
<v Speaker 1>to use the technology. But I rarely give it much

0:25:09.680 --> 0:25:13.399
<v Speaker 1>more consideration than that sort of surface level. But talking

0:25:13.400 --> 0:25:16.200
<v Speaker 1>with engineers really reveals how much thought has to go

0:25:16.280 --> 0:25:19.480
<v Speaker 1>into this, and it also explains that sometimes it goes

0:25:19.520 --> 0:25:23.240
<v Speaker 1>wrong because you have multiple groups all trying to get

0:25:23.280 --> 0:25:27.240
<v Speaker 1>their various pieces of the puzzle into place, and sometimes

0:25:27.280 --> 0:25:31.280
<v Speaker 1>that means that their peace and someone else's piece, while

0:25:31.320 --> 0:25:34.679
<v Speaker 1>they were meant to fit together, don't. They might overlap,

0:25:34.920 --> 0:25:38.080
<v Speaker 1>they might conflict, they might be a gap between them.

0:25:38.080 --> 0:25:40.600
<v Speaker 1>Those sort of things can happen when things don't go well.

0:25:41.119 --> 0:25:43.399
<v Speaker 1>Now we're going to take another quick break, but when

0:25:43.480 --> 0:25:46.520
<v Speaker 1>we come back, will rejoin me in the Mazda c

0:25:46.880 --> 0:25:57.200
<v Speaker 1>X thirty. All right, So now we're gonna pick back

0:25:57.320 --> 0:26:00.000
<v Speaker 1>up with me at the auto show, So you're gonna

0:26:00.080 --> 0:26:02.840
<v Speaker 1>hear the audio audio quality change again, and I'll be

0:26:02.880 --> 0:26:06.440
<v Speaker 1>talking about the importance of collaboration and communication, and away

0:26:06.880 --> 0:26:09.040
<v Speaker 1>we go. That ends up saving a lot of time

0:26:09.359 --> 0:26:12.239
<v Speaker 1>in the design process there. I've seen a lot of

0:26:12.240 --> 0:26:14.800
<v Speaker 1>different products come out where it was only in the

0:26:14.800 --> 0:26:17.960
<v Speaker 1>testing phase that they realized that there were these sort

0:26:18.000 --> 0:26:20.479
<v Speaker 1>of issues, and then it just meant having to go

0:26:20.520 --> 0:26:23.359
<v Speaker 1>back through a redesign process, and typically it tends to

0:26:23.400 --> 0:26:25.800
<v Speaker 1>be very similar to the first design process, which means

0:26:26.080 --> 0:26:29.640
<v Speaker 1>you still have that problem of these isolated silos, these

0:26:29.680 --> 0:26:33.440
<v Speaker 1>isolated departments that are each working towards their own goal

0:26:34.040 --> 0:26:38.399
<v Speaker 1>and not collaborating closely enough to get the end result

0:26:38.440 --> 0:26:42.400
<v Speaker 1>they want. So that's a huge challenge in design in general.

0:26:43.200 --> 0:26:46.440
<v Speaker 1>So you get to the point where you've built your solution,

0:26:46.600 --> 0:26:51.119
<v Speaker 1>you've tested your solution, Uh, your systems are not in isolation,

0:26:51.160 --> 0:26:53.320
<v Speaker 1>You've figured that part out, You've got your systems all

0:26:53.320 --> 0:26:57.200
<v Speaker 1>working together, and then you see how well it works

0:26:57.200 --> 0:26:59.800
<v Speaker 1>on paper, and then you throw people into it and

0:27:00.040 --> 0:27:03.040
<v Speaker 1>eyes you know technology. I've I've often told this to

0:27:03.320 --> 0:27:09.000
<v Speaker 1>people when I talk about my role at the podcast Realm.

0:27:09.320 --> 0:27:11.159
<v Speaker 1>You know, I've got a lot of podcast friends, a

0:27:11.200 --> 0:27:14.639
<v Speaker 1>lot of coworkers who do great work in all sorts

0:27:14.640 --> 0:27:18.040
<v Speaker 1>of fields. But they're talking about stuff like, you know,

0:27:18.720 --> 0:27:22.960
<v Speaker 1>society and culture and and and money and stuff. What

0:27:23.119 --> 0:27:26.520
<v Speaker 1>don't make sense, y'all. Technology, it makes sense. It either

0:27:26.560 --> 0:27:28.960
<v Speaker 1>works or it doesn't. I have the easiest job, don't

0:27:29.040 --> 0:27:34.080
<v Speaker 1>tell anyone. But when you throw people into things, it

0:27:34.119 --> 0:27:39.440
<v Speaker 1>gets messy because people they have expectations, they have desires,

0:27:39.440 --> 0:27:42.960
<v Speaker 1>they have motivations, they have things that technology on its

0:27:42.960 --> 0:27:45.560
<v Speaker 1>own does not have. As long as sky net has

0:27:45.600 --> 0:27:51.000
<v Speaker 1>not yet gone you know completely, you know, self aware.

0:27:52.640 --> 0:27:55.960
<v Speaker 1>I'm assuming that we're okay at the moment, but yeah,

0:27:56.000 --> 0:28:00.600
<v Speaker 1>people make things complicated. When people are involved, you then

0:28:00.680 --> 0:28:05.159
<v Speaker 1>have to really evaluate what your work actually means in

0:28:05.240 --> 0:28:07.879
<v Speaker 1>the real world. I want to give you, guys an

0:28:07.920 --> 0:28:11.760
<v Speaker 1>example that's unrelated to vehicles for a moment to kind

0:28:11.760 --> 0:28:14.840
<v Speaker 1>of explain what I'm thinking about here. I once intended

0:28:14.880 --> 0:28:18.159
<v Speaker 1>to talk with some roboticists who were talking about the

0:28:18.240 --> 0:28:20.480
<v Speaker 1>challenges they faced when they were trying to design a

0:28:20.600 --> 0:28:24.359
<v Speaker 1>robot that would that would interact with humans within a

0:28:24.440 --> 0:28:31.080
<v Speaker 1>human space, and that is a difficult thing to really engineer.

0:28:31.440 --> 0:28:36.280
<v Speaker 1>To create a robot that can seamlessly interact with humans.

0:28:36.320 --> 0:28:40.040
<v Speaker 1>So they sat down and they identified their various goals

0:28:40.040 --> 0:28:42.320
<v Speaker 1>and objectives. They sat down and said, all right, these

0:28:42.320 --> 0:28:44.960
<v Speaker 1>are the things that are important to us. We need

0:28:45.000 --> 0:28:47.040
<v Speaker 1>to make sure that our robot does these things. And

0:28:47.080 --> 0:28:50.480
<v Speaker 1>they were parameters like this is how close a robot

0:28:50.520 --> 0:28:53.720
<v Speaker 1>can get to another human being before it has to

0:28:53.760 --> 0:28:56.160
<v Speaker 1>stop because otherwise it's going to be crowding someone. Or

0:28:56.520 --> 0:28:59.120
<v Speaker 1>this is how close a robot can get to a

0:28:59.320 --> 0:29:02.720
<v Speaker 1>stationary object. This is how fast the robots should move

0:29:02.720 --> 0:29:06.160
<v Speaker 1>through the environment. This is how the robot should respond

0:29:06.320 --> 0:29:10.360
<v Speaker 1>if someone were to address it. So a whole list

0:29:10.400 --> 0:29:14.400
<v Speaker 1>of rules that they had to figure out and then design,

0:29:14.920 --> 0:29:17.440
<v Speaker 1>and this took months and months and months of testing.

0:29:18.160 --> 0:29:20.120
<v Speaker 1>There was a point where a robot was staring at

0:29:20.120 --> 0:29:21.760
<v Speaker 1>a door for two hours trying to figure out how

0:29:21.800 --> 0:29:24.000
<v Speaker 1>to open it. That's the sort of stuff we're talking about.

0:29:25.160 --> 0:29:27.320
<v Speaker 1>They solve all these problems and then they put the

0:29:27.400 --> 0:29:31.080
<v Speaker 1>robot into an actual human environment, and that's when everything

0:29:31.120 --> 0:29:35.560
<v Speaker 1>went pear shaped, I guess we could say, because they

0:29:35.720 --> 0:29:40.040
<v Speaker 1>realized that the human beings in that particular environment had

0:29:40.080 --> 0:29:43.000
<v Speaker 1>an expectation of how the robot was supposed to behave.

0:29:43.080 --> 0:29:45.880
<v Speaker 1>It was a robot, but the robot wasn't behaving the

0:29:45.880 --> 0:29:49.880
<v Speaker 1>way they thought a robot should behave. The robot was

0:29:49.920 --> 0:29:52.160
<v Speaker 1>behaving the way the engineers had thought the robots should

0:29:52.160 --> 0:29:54.600
<v Speaker 1>behave based on the way humans behave within the same

0:29:54.680 --> 0:29:58.160
<v Speaker 1>sort of social space. Now that meant that the people

0:29:58.160 --> 0:30:02.400
<v Speaker 1>who were actually encountering the robot, we're uncomfortable around the robot.

0:30:02.600 --> 0:30:06.040
<v Speaker 1>It felt weird. It was the sort of Uncanny Valley,

0:30:06.080 --> 0:30:10.400
<v Speaker 1>except instead of appearance, it was in behavior. So uncanny valley,

0:30:10.400 --> 0:30:14.040
<v Speaker 1>for those who are not familiar, is this gap when

0:30:14.080 --> 0:30:19.080
<v Speaker 1>you start to approach something that appears to be alive

0:30:19.480 --> 0:30:22.920
<v Speaker 1>but still has certain elements that indicate it is not

0:30:23.000 --> 0:30:25.480
<v Speaker 1>truly alive. We usually use it to describe things like

0:30:25.560 --> 0:30:27.680
<v Speaker 1>c G I characters, where a c G I character

0:30:27.720 --> 0:30:32.480
<v Speaker 1>looks almost but not quite real. The same thing is

0:30:32.480 --> 0:30:37.320
<v Speaker 1>true with behaviors. So the roboticists discovered that these robots

0:30:37.800 --> 0:30:40.600
<v Speaker 1>were not performing the way they needed to, that people

0:30:40.600 --> 0:30:43.280
<v Speaker 1>were not responding to them the way that they had

0:30:43.320 --> 0:30:46.920
<v Speaker 1>anticipated because it wasn't robotic enough. They actually had to

0:30:46.920 --> 0:30:49.560
<v Speaker 1>go back to the drawing board and go through and

0:30:49.640 --> 0:30:54.480
<v Speaker 1>start rethinking their whole process of creating robots that could

0:30:54.520 --> 0:30:58.920
<v Speaker 1>interact in social spaces and make them more robotic. That

0:30:59.080 --> 0:31:01.480
<v Speaker 1>was a fail. You're of an approach of a human

0:31:01.480 --> 0:31:04.440
<v Speaker 1>centric design in the sense that the people creating the

0:31:04.520 --> 0:31:10.320
<v Speaker 1>robots had not anticipated that human reaction, and it shows

0:31:10.640 --> 0:31:13.600
<v Speaker 1>that when you throw humans into an equation, things get

0:31:13.640 --> 0:31:17.680
<v Speaker 1>a little more complicated. It's not as straightforward as saying

0:31:18.320 --> 0:31:24.120
<v Speaker 1>this particular piece of technology needs to do task in

0:31:24.320 --> 0:31:26.880
<v Speaker 1>why amount of time and it has to have a

0:31:26.880 --> 0:31:31.400
<v Speaker 1>certain level of reliability. It means more than that. It

0:31:31.440 --> 0:31:37.760
<v Speaker 1>means defining things like a feeling, intention, defining how a

0:31:37.840 --> 0:31:44.360
<v Speaker 1>person should experience the technology. And this goes well beyond technology. Obviously,

0:31:44.400 --> 0:31:47.040
<v Speaker 1>it goes to everything that we ever designed. But really

0:31:47.040 --> 0:31:49.640
<v Speaker 1>in tech, it's something that you either get or you don't,

0:31:49.840 --> 0:31:53.000
<v Speaker 1>and if you get it when you're designing, you can

0:31:53.040 --> 0:31:58.960
<v Speaker 1>create something that actually has a legit special feeling when

0:31:59.000 --> 0:32:03.760
<v Speaker 1>you experience it. It's a very tough challenge because obviously,

0:32:03.800 --> 0:32:06.240
<v Speaker 1>the other big issue you have is that people are different.

0:32:06.320 --> 0:32:09.080
<v Speaker 1>You know, we have general things that kind of unite us,

0:32:09.080 --> 0:32:14.600
<v Speaker 1>but we're all individuals. We all have our own preferences,

0:32:14.720 --> 0:32:17.640
<v Speaker 1>our own things that that maybe annoy us, uh and

0:32:17.680 --> 0:32:20.920
<v Speaker 1>our own expectations, so it also means having to identify

0:32:21.000 --> 0:32:26.440
<v Speaker 1>which ones are the most important to whatever end result

0:32:26.480 --> 0:32:30.720
<v Speaker 1>you're looking for. So one of the things that really

0:32:30.800 --> 0:32:34.040
<v Speaker 1>we heard a lot when we were here over in

0:32:34.080 --> 0:32:37.520
<v Speaker 1>the auto show over at Mazda's this this concept of

0:32:37.640 --> 0:32:41.480
<v Speaker 1>feel alive, that you want to feel alive when you're

0:32:41.520 --> 0:32:46.320
<v Speaker 1>actually using the vehicle, and vehicles are such an important

0:32:46.480 --> 0:32:49.960
<v Speaker 1>central piece of technology in our lives. That is not

0:32:50.040 --> 0:32:53.320
<v Speaker 1>a small task, and it's not lips service. It's not

0:32:53.480 --> 0:32:58.480
<v Speaker 1>something that is just a tagline. It's a guiding philosophy.

0:32:58.520 --> 0:33:02.360
<v Speaker 1>That's the philosophy that guides the decisions that the engineers

0:33:02.360 --> 0:33:04.320
<v Speaker 1>are making in order to make a vehicle that is

0:33:05.360 --> 0:33:08.480
<v Speaker 1>fun to drive, that it's safe, that's efficient, that it

0:33:08.520 --> 0:33:10.400
<v Speaker 1>has all the things you expect a vehicle to have,

0:33:10.800 --> 0:33:12.800
<v Speaker 1>but that when you are behind the wheel and you're

0:33:12.840 --> 0:33:18.160
<v Speaker 1>actually driving it, you have the sensation of feeling alive.

0:33:18.280 --> 0:33:22.480
<v Speaker 1>That's sort of exhilarating feeling, and that it's something that

0:33:22.520 --> 0:33:25.320
<v Speaker 1>goes beyond just your experience behind the wheel. It's something

0:33:25.360 --> 0:33:28.240
<v Speaker 1>that is actually integrated into your experience of moving through

0:33:28.320 --> 0:33:31.720
<v Speaker 1>an environment. So when you start thinking about that, you're

0:33:31.760 --> 0:33:36.400
<v Speaker 1>thinking not just trying to define everything that's on a

0:33:36.560 --> 0:33:40.640
<v Speaker 1>dashboard or just an easy reach of the driver. You're

0:33:40.680 --> 0:33:43.400
<v Speaker 1>thinking about an experience that goes well beyond that, as

0:33:43.440 --> 0:33:47.400
<v Speaker 1>the driver's maneuvering through different environments. That ends up being

0:33:47.400 --> 0:33:53.160
<v Speaker 1>a very important concept to guide all of your design philosophies.

0:33:53.840 --> 0:33:56.800
<v Speaker 1>And I was really impressed with the passion that I

0:33:56.960 --> 0:34:00.680
<v Speaker 1>encountered when I talked with people from Mazda. All shared

0:34:00.800 --> 0:34:06.040
<v Speaker 1>that same sort of uh, deep desire to create that

0:34:06.160 --> 0:34:10.000
<v Speaker 1>kind of experience. And this is not something that is

0:34:10.080 --> 0:34:15.080
<v Speaker 1>easy to engineer. It's not something you typically hear from engineers. Uh.

0:34:15.160 --> 0:34:18.759
<v Speaker 1>This also kind of brings us to a dichotomy I

0:34:18.880 --> 0:34:23.240
<v Speaker 1>tend to encounter in the field of technology. Broadly speaking,

0:34:23.600 --> 0:34:27.239
<v Speaker 1>there are two major camps I tend to encounter when

0:34:27.280 --> 0:34:31.680
<v Speaker 1>I'm looking at different types of gadgets and vehicles and

0:34:31.719 --> 0:34:34.760
<v Speaker 1>things like that. One is that I see a camp

0:34:34.880 --> 0:34:40.560
<v Speaker 1>that really emphasizes esthetic over everything else, so that the

0:34:40.640 --> 0:34:44.120
<v Speaker 1>look of it is supposed to be extremely evocative and

0:34:44.239 --> 0:34:48.360
<v Speaker 1>that it makes you want to use it in some way,

0:34:48.400 --> 0:34:52.080
<v Speaker 1>but that is the guiding principle behind the design. The

0:34:52.120 --> 0:34:55.360
<v Speaker 1>other I've seen is a more I think of it

0:34:55.400 --> 0:34:58.319
<v Speaker 1>as the engineering approach in the sense that it needs

0:34:58.400 --> 0:34:59.960
<v Speaker 1>to work, it needs to be able to do the

0:35:00.080 --> 0:35:02.560
<v Speaker 1>things that it was supposed to do. Uh, And that

0:35:02.680 --> 0:35:07.440
<v Speaker 1>becomes primary and aesthetic is is secondary, or maybe tertiary,

0:35:07.520 --> 0:35:11.160
<v Speaker 1>or maybe for some companies, not really a thing that

0:35:11.200 --> 0:35:14.520
<v Speaker 1>anyone thinks about. Uh. I'm sure many of you have

0:35:14.680 --> 0:35:17.399
<v Speaker 1>owned gadgets out there that fall into that category where

0:35:17.440 --> 0:35:19.480
<v Speaker 1>you think this thing is ugly as sin. It does

0:35:19.520 --> 0:35:21.160
<v Speaker 1>what it's supposed to do, but I don't like to

0:35:21.160 --> 0:35:25.000
<v Speaker 1>look at it. The real goal, I think, is trying

0:35:25.040 --> 0:35:30.760
<v Speaker 1>to bridge the gap between those two different philosophies, bringing

0:35:30.760 --> 0:35:34.640
<v Speaker 1>together the aesthetic and the desire to get the engineering

0:35:34.719 --> 0:35:38.879
<v Speaker 1>just right. Uh. I think a lot about my experience

0:35:38.920 --> 0:35:41.880
<v Speaker 1>with different things like mobile devices. That's the one that

0:35:41.920 --> 0:35:45.160
<v Speaker 1>I always think about about how I've had experiences with

0:35:45.239 --> 0:35:48.720
<v Speaker 1>ones where it looks really nice, it looks really sexy,

0:35:49.239 --> 0:35:52.920
<v Speaker 1>looks like it would go fast just standing still, and

0:35:53.000 --> 0:35:55.160
<v Speaker 1>others that it doesn't look so good, but you can

0:35:55.320 --> 0:35:58.560
<v Speaker 1>definitely see how everything works. Uh. And maybe you have

0:35:58.640 --> 0:36:02.919
<v Speaker 1>to learn the peculiarities of that particular system in order

0:36:02.920 --> 0:36:05.040
<v Speaker 1>for you to have a deeper appreciation, but you once

0:36:05.080 --> 0:36:09.040
<v Speaker 1>you do, it works just fine. Marrying those two is

0:36:09.120 --> 0:36:13.040
<v Speaker 1>really challenging, but it's also a very important part of

0:36:13.040 --> 0:36:18.600
<v Speaker 1>this human centric focus. Knowing that people do value both

0:36:18.680 --> 0:36:23.000
<v Speaker 1>the aesthetic and the function of a device, and again

0:36:23.040 --> 0:36:26.160
<v Speaker 1>for something as important as a vehicle, it becomes even

0:36:26.440 --> 0:36:31.040
<v Speaker 1>more imperative that you get that just right. So to

0:36:31.160 --> 0:36:34.880
<v Speaker 1>achieve this, it's all the all these different processes, all

0:36:34.880 --> 0:36:37.440
<v Speaker 1>these different philosophies I've talked about, have to come together.

0:36:38.320 --> 0:36:43.080
<v Speaker 1>We heard about how at Mazda they are still very

0:36:43.640 --> 0:36:47.960
<v Speaker 1>focused on very traditional ways of modeling, say the exterior

0:36:47.960 --> 0:36:50.960
<v Speaker 1>of a car, doing it through clay first and sculpting

0:36:51.040 --> 0:36:54.760
<v Speaker 1>it so that you can get exactly the right feel.

0:36:55.239 --> 0:36:59.440
<v Speaker 1>You know, you can very carefully shave away a tiny

0:36:59.640 --> 0:37:02.080
<v Speaker 1>slow ver of clay in order to get just the

0:37:02.160 --> 0:37:05.439
<v Speaker 1>right shape or just the right curve, and doing all

0:37:05.480 --> 0:37:09.320
<v Speaker 1>of that to meticulous detail until you do a full

0:37:09.440 --> 0:37:11.560
<v Speaker 1>scan of it and three D and then maybe then

0:37:11.640 --> 0:37:14.080
<v Speaker 1>at that point you can go to additive manufacturing, like

0:37:14.080 --> 0:37:18.279
<v Speaker 1>a three D printing sort of approach and create your

0:37:18.320 --> 0:37:22.080
<v Speaker 1>first three D printed version of the thing that you

0:37:22.120 --> 0:37:25.800
<v Speaker 1>have sculpted out of clay. They talked about how even

0:37:25.840 --> 0:37:29.560
<v Speaker 1>getting to a point where you could build the full

0:37:29.640 --> 0:37:35.040
<v Speaker 1>sized version of uh like a door, for example, that

0:37:35.120 --> 0:37:40.520
<v Speaker 1>if it wasn't just right, their engineers would take hand

0:37:41.160 --> 0:37:47.120
<v Speaker 1>uh handcrafted approaches to making sure they got exactly the

0:37:47.160 --> 0:37:50.320
<v Speaker 1>curve that they wanted in order to achieve the result

0:37:50.360 --> 0:37:52.480
<v Speaker 1>that they were going for. And that kind of level

0:37:53.080 --> 0:37:57.520
<v Speaker 1>of attention to detail is something that I find really inspiring.

0:37:57.600 --> 0:38:01.000
<v Speaker 1>It's also kind of intimidating you think about the scale

0:38:01.239 --> 0:38:05.720
<v Speaker 1>that that requires, and uh, that's not something that's easily

0:38:05.800 --> 0:38:10.200
<v Speaker 1>tackled either. So it's I feel like this is one

0:38:10.200 --> 0:38:13.279
<v Speaker 1>of those cases where you hear about the philosophy and

0:38:13.280 --> 0:38:15.320
<v Speaker 1>then you hear the stories behind it, and you really

0:38:15.360 --> 0:38:19.560
<v Speaker 1>feel that that you're talking to a company that's that's

0:38:19.600 --> 0:38:22.080
<v Speaker 1>walking the walk. They're not just talking the talk, they

0:38:22.120 --> 0:38:25.560
<v Speaker 1>really follow through with that, uh, and that to me

0:38:25.640 --> 0:38:30.600
<v Speaker 1>is really exciting. So I hope that I'm able to

0:38:30.920 --> 0:38:36.480
<v Speaker 1>kind of illustrate to you this incredible journey the the

0:38:36.560 --> 0:38:38.719
<v Speaker 1>from the point where you actually identify what it is

0:38:38.840 --> 0:38:41.399
<v Speaker 1>you want to do to the point of seeing it

0:38:41.520 --> 0:38:44.640
<v Speaker 1>come together and all the different challenges that face you

0:38:44.800 --> 0:38:49.040
<v Speaker 1>along the way. Uh. There are so many different examples

0:38:49.040 --> 0:38:53.319
<v Speaker 1>of that with any kind of technology, including vehicles, where

0:38:53.440 --> 0:38:55.839
<v Speaker 1>you can look at this and say, like if if

0:38:55.960 --> 0:38:59.400
<v Speaker 1>one of these systems didn't work just right, then it

0:38:59.400 --> 0:39:02.640
<v Speaker 1>would affect everything else. It becomes a cascading effect, and

0:39:02.719 --> 0:39:05.840
<v Speaker 1>no matter how good the design is on other elements

0:39:05.960 --> 0:39:09.479
<v Speaker 1>of the vehicle, you would still fall short of your goal.

0:39:09.880 --> 0:39:13.320
<v Speaker 1>And it really does drive home how enormous a challenge

0:39:13.440 --> 0:39:17.480
<v Speaker 1>this is. So I think they're playing me off. No,

0:39:17.840 --> 0:39:21.719
<v Speaker 1>I think that this has been an incredible experience for me.

0:39:22.400 --> 0:39:26.000
<v Speaker 1>This is an awesome studio. I can't wait to have

0:39:26.120 --> 0:39:32.759
<v Speaker 1>it installed in Atlanta. Uh everyone's laughing. Okay, well it

0:39:32.800 --> 0:39:35.400
<v Speaker 1>would still be great. I think uh Tari would have

0:39:35.600 --> 0:39:39.000
<v Speaker 1>fewer instances of me having you know, Diva fits in

0:39:39.040 --> 0:39:41.480
<v Speaker 1>the studio if I were recording in something like this

0:39:41.560 --> 0:39:45.800
<v Speaker 1>every single episode. Uh. Plus, I mean, there's it's spacious.

0:39:45.840 --> 0:39:49.280
<v Speaker 1>I could have so many guests in a single episode

0:39:49.320 --> 0:39:51.319
<v Speaker 1>and we could all have our own, our own nice

0:39:51.360 --> 0:39:55.680
<v Speaker 1>comfortable seats. I'm just really, it's a practical thing. I'm saying,

0:39:55.719 --> 0:39:58.839
<v Speaker 1>Like my studio back in Atlanta, we can fit maybe

0:39:58.840 --> 0:40:00.879
<v Speaker 1>three people in there before we get it's crowded. This time,

0:40:01.040 --> 0:40:04.400
<v Speaker 1>I can cram a lot of folks in here, including

0:40:04.719 --> 0:40:07.719
<v Speaker 1>sound engineers. So Tary it benefits you too, is what

0:40:07.760 --> 0:40:11.160
<v Speaker 1>I'm saying, but I want to think masdo for having

0:40:11.160 --> 0:40:14.200
<v Speaker 1>me come out here and to experience this and to

0:40:14.840 --> 0:40:19.760
<v Speaker 1>get a firsthand look at the culmination of this idea.

0:40:19.880 --> 0:40:22.520
<v Speaker 1>I've heard a lot about this philosophy. I've talked to

0:40:22.560 --> 0:40:28.440
<v Speaker 1>people who have been sort of really passionate about the

0:40:28.480 --> 0:40:32.040
<v Speaker 1>concept behind human centric design, but it's rare that I

0:40:32.040 --> 0:40:35.400
<v Speaker 1>actually get an experience, a truly immersive experience, because I

0:40:35.440 --> 0:40:39.560
<v Speaker 1>am actually in it where I see the fruition of that.

0:40:39.920 --> 0:40:41.600
<v Speaker 1>And when you get a chance to see that and

0:40:41.640 --> 0:40:45.879
<v Speaker 1>you you understand the decisions that went behind all those

0:40:45.920 --> 0:40:52.280
<v Speaker 1>design choices, you get a deeper appreciation for that process

0:40:52.360 --> 0:40:55.000
<v Speaker 1>and all the work that goes into just making something

0:40:55.080 --> 0:40:59.200
<v Speaker 1>actually happen. I think we all take for granted what

0:40:59.600 --> 0:41:03.040
<v Speaker 1>it makes to create a piece of technology like this.

0:41:03.400 --> 0:41:05.960
<v Speaker 1>You know, we might think of the manufacturing process, because

0:41:06.000 --> 0:41:08.839
<v Speaker 1>that's one that is easy to illustrate. It's you see

0:41:08.880 --> 0:41:13.239
<v Speaker 1>the factory line, But it's so much more than that.

0:41:13.280 --> 0:41:18.000
<v Speaker 1>The process takes years of work, years of engineering, years

0:41:18.000 --> 0:41:23.200
<v Speaker 1>of iterating and building upon past uh learnings, and two

0:41:23.880 --> 0:41:26.480
<v Speaker 1>continue to innovate on top of that. It is a

0:41:26.560 --> 0:41:32.840
<v Speaker 1>really interesting and inspiring experience to actually see this in person.

0:41:33.760 --> 0:41:38.160
<v Speaker 1>With that, I think I'm gonna wrap up because, um,

0:41:38.200 --> 0:41:41.560
<v Speaker 1>you know, I think I think i've I've covered it

0:41:41.600 --> 0:41:43.680
<v Speaker 1>pretty well. And plus I really want to have a

0:41:43.680 --> 0:41:46.120
<v Speaker 1>little more experience jumping around in the back seat of

0:41:46.160 --> 0:41:47.920
<v Speaker 1>this thing, because I've been saying in the front the

0:41:47.920 --> 0:41:49.759
<v Speaker 1>whole time and I haven't even experienced what the back

0:41:49.760 --> 0:41:52.560
<v Speaker 1>seats like. And I don't think anyone's gonna stop me

0:41:52.600 --> 0:41:54.399
<v Speaker 1>as long as I hold a microphone in my hand.

0:41:54.960 --> 0:41:57.440
<v Speaker 1>So I'm going to sign off, but don't tell anyone

0:41:57.440 --> 0:42:00.839
<v Speaker 1>who's actually here that I've done that. I'll just I'll

0:42:00.880 --> 0:42:03.960
<v Speaker 1>pretend like I'm still point. Oh they're broadcasting the whole

0:42:04.000 --> 0:42:06.480
<v Speaker 1>thing right now. Okay, well, alright, so on that. No, guys,

0:42:07.120 --> 0:42:10.160
<v Speaker 1>we're gonna wrap up this episode. Remember if you want

0:42:10.200 --> 0:42:12.880
<v Speaker 1>to reach out to me, text stuff at how stuff

0:42:12.920 --> 0:42:15.960
<v Speaker 1>works dot com, or you can pop onto Facebook or Twitter.

0:42:16.040 --> 0:42:19.840
<v Speaker 1>That's tech stuff hs W and uh, I look forward

0:42:20.040 --> 0:42:24.560
<v Speaker 1>to talking to you again really soon. And it's Jonathan

0:42:24.600 --> 0:42:27.440
<v Speaker 1>back in the studio. So I want to thank Mazda

0:42:27.480 --> 0:42:30.280
<v Speaker 1>for having me out at the auto show and getting

0:42:30.280 --> 0:42:33.040
<v Speaker 1>a chance to experience just a tiny sliver of the

0:42:33.080 --> 0:42:36.040
<v Speaker 1>work that they put into the c x thirty. You know,

0:42:36.080 --> 0:42:38.839
<v Speaker 1>I didn't get a chance to ride in it, but

0:42:39.280 --> 0:42:42.200
<v Speaker 1>it was really cool getting to see it up close

0:42:42.239 --> 0:42:44.440
<v Speaker 1>and actually sit in it and record an episode. It

0:42:44.480 --> 0:42:49.040
<v Speaker 1>was a fun experience. And uh and everyone there, by

0:42:49.040 --> 0:42:52.640
<v Speaker 1>the way, was incredibly kind and very helpful. So I

0:42:52.680 --> 0:42:55.120
<v Speaker 1>had a really good experience with everybody over there. So

0:42:55.160 --> 0:42:57.360
<v Speaker 1>thank you guys a lot. You guys are awesome. It

0:42:57.440 --> 0:43:01.160
<v Speaker 1>also reminded me that with every piece of technology I encounter,

0:43:01.239 --> 0:43:04.160
<v Speaker 1>no matter what it might be, there typically dozens or

0:43:04.280 --> 0:43:07.720
<v Speaker 1>hundreds or maybe even thousands of people who helped shape

0:43:07.760 --> 0:43:11.239
<v Speaker 1>that technology, maybe a little bit, maybe they helped define it,

0:43:11.480 --> 0:43:15.040
<v Speaker 1>but they all had their impact on that technology before

0:43:15.080 --> 0:43:18.239
<v Speaker 1>I ever got a chance to touch it. And that

0:43:18.360 --> 0:43:21.439
<v Speaker 1>when it all goes right, when everything is falling into

0:43:21.440 --> 0:43:24.160
<v Speaker 1>place properly, when people are able to collaborate, when they're

0:43:24.200 --> 0:43:28.040
<v Speaker 1>able to communicate, then they can produce technology in turn

0:43:28.239 --> 0:43:32.560
<v Speaker 1>creates a specific experience that reflects whatever the original intent

0:43:32.920 --> 0:43:36.200
<v Speaker 1>was of the design team. That comes to the very

0:43:36.880 --> 0:43:40.680
<v Speaker 1>goal of human centric design. And again, this is not

0:43:40.920 --> 0:43:44.960
<v Speaker 1>an easy thing to achieve. It is incredibly challenging. You

0:43:45.040 --> 0:43:48.799
<v Speaker 1>might define what you want people to feel like, but

0:43:49.400 --> 0:43:52.920
<v Speaker 1>then it may turn out that when people actually experience

0:43:53.000 --> 0:43:56.360
<v Speaker 1>the product, they feel something entirely different, and that you

0:43:56.400 --> 0:43:59.279
<v Speaker 1>could argue that that represents a failure on your part

0:43:59.560 --> 0:44:02.000
<v Speaker 1>as far as the design goes, and you have to

0:44:02.080 --> 0:44:07.480
<v Speaker 1>factor in human psychology and human behaviors that aren't something

0:44:07.480 --> 0:44:10.960
<v Speaker 1>that are so easy to quantify. As you know, how

0:44:11.000 --> 0:44:14.640
<v Speaker 1>efficient an engine is running, or how long a tire

0:44:15.080 --> 0:44:18.360
<v Speaker 1>can can be in service before you need to replace it.

0:44:18.640 --> 0:44:21.080
<v Speaker 1>Those are things that you can quantify much more easily.

0:44:21.440 --> 0:44:24.160
<v Speaker 1>So this human centric design philosophy is something that I

0:44:24.160 --> 0:44:27.839
<v Speaker 1>think is really fascinating, incredibly challenging, and when you get

0:44:27.880 --> 0:44:32.279
<v Speaker 1>it right, amazingly satisfying. All right, Well, that wraps up

0:44:32.560 --> 0:44:34.720
<v Speaker 1>this episode. And I know I gave a sign off

0:44:35.120 --> 0:44:37.680
<v Speaker 1>in the live section, but you know, I I feel

0:44:37.680 --> 0:44:40.240
<v Speaker 1>like if I don't do it again, I'm not really

0:44:40.239 --> 0:44:43.480
<v Speaker 1>doing my job. If you guys have suggestions for topics

0:44:43.560 --> 0:44:45.719
<v Speaker 1>you would like me to cover in future episodes of

0:44:45.719 --> 0:44:48.240
<v Speaker 1>tech Stuff, you can reach out via email the addresses

0:44:48.320 --> 0:44:51.560
<v Speaker 1>tech stuff at how stuffworks dot com, or you can

0:44:51.680 --> 0:44:54.360
<v Speaker 1>pop onto Facebook or Twitter the handle for both of

0:44:54.360 --> 0:44:58.799
<v Speaker 1>those Text Stuff hs W. You can also pop on

0:44:58.880 --> 0:45:01.919
<v Speaker 1>over to our website that tech Stuff Podcast dot com.

0:45:01.960 --> 0:45:04.520
<v Speaker 1>You'll find an archive of every episode that we've ever

0:45:04.560 --> 0:45:08.239
<v Speaker 1>recorded and published. It's all there's searchable. So if there's

0:45:08.239 --> 0:45:10.560
<v Speaker 1>a specific topic you would you know I want to

0:45:10.600 --> 0:45:12.319
<v Speaker 1>know more about, you can search and see if I've

0:45:12.320 --> 0:45:14.680
<v Speaker 1>already done an episode on it, and if not, then

0:45:15.040 --> 0:45:16.920
<v Speaker 1>use the aforementioned ways to get in touch with me

0:45:16.920 --> 0:45:18.839
<v Speaker 1>and let me know about it and I'll get right

0:45:18.880 --> 0:45:22.120
<v Speaker 1>on it. And also there's a link to our online

0:45:22.160 --> 0:45:24.560
<v Speaker 1>store where every purchasing make goes to help the show,

0:45:24.560 --> 0:45:26.960
<v Speaker 1>and we greatly appreciate it, and I will talk to

0:45:27.000 --> 0:45:34.480
<v Speaker 1>you again and really soon. Text Stuff is a production

0:45:34.480 --> 0:45:37.480
<v Speaker 1>of I Heart Radio's How Stuff Works. For more podcasts

0:45:37.520 --> 0:45:40.280
<v Speaker 1>from I heart Radio, visit the I heart Radio app,

0:45:40.400 --> 0:45:43.560
<v Speaker 1>Apple Podcasts, or wherever you listen to your favorite shows.