Episode 2

full
Published on:

18th Mar 2026

Why the Worst Thing You Can Do Is Be the Designer Everyone Wants You to Be | Dan Salisbury, Automata

What does it take to walk into a deep tech startup as the only industrial designer... Earn the trust of thirty engineers, and...

Build a design identity so thoroughly baked into the product that no one can ever cost-optimise it out?

In this episode of Why Design, Dan Salisbury shares the belief that sits at the heart of his work: that design isn't a layer you apply at the end, it's the structure you build from the inside, or it's nothing at all.

Rather than staying in consultancy, Dan chose to go in-house at Automata with no design team, no established language, and no precedent for what industrial design should mean in a lab automation company.

That decision led to three years of proof.

This conversation isn't about having the right portfolio.

It's about having the conviction to demonstrate value when no one has thought to ask for it.

It's about the specific decisions, a shade of pink, a custom extrusion, a studio photography budget, that turn a product into a statement.

This time we go beyond the fancy gadgets

Join the Why Design community โ†’ teamkodu.com/whydesign

What You'll Learn

  1. Why industrial design in deep tech isn't about aesthetics, it's about trust, proof, and permanence
  2. How Dan survived almost failing probation by doubling down on his actual strengths instead of copying others
  3. What presenting to Dieter Rams at 25 taught him about confidence, preparation, and the value of being in the room
  4. Why form following function is a design philosophy and a strategy for making your work impossible to remove
  5. How to build a design language when your manufacturing constraints are brutal and your volumes are low
  6. What a properly considered product launch looks like, and why most B2B companies never bother to try

Memorable Quotes

"Any advice I'd give to anyone is just: stick to your strengths. Don't try and be like other designers because everyone's different in how they approach problems."

"The felt, tip fairy thing, I've heard it more times than I can count. And the answer is always the same: show them. Don't explain. Show them."

"I built the design identity into the extrusion itself. The horizontal lines, the light gap, they're functional. You can't remove them without removing the product."

"The job advert said 'industrial design' in the title. It talked about the impact. I applied within about five minutes of reading it."

"The V2 launch was the proudest moment of my career. I sat there surrounded by studio shots and render posters and I thought, yeah. That's it. That's what this was for."

Resources & Links

๐ŸŽง Listen on Spotify, Apple Podcasts, YouTube & Amazon โ†’ whydesign.club

๐Ÿ‘ฅ Join the Why Design community โ†’ teamkodu.com/whydesign

๐Ÿ“ธ Follow @whydesignxkodu on Instagram

๐ŸŽฅ Watch full episodes โ†’ www.youtube.com/@whydesignpod

๐Ÿ”— Follow Chris Whyte โ†’ linkedin.com/in/mrchriswhyte

๐Ÿ”— Explore Automata โ†’ automata.tech

๐Ÿ”— Connect with Dan on LinkedIn โ†’ Dan Salisbury

About the Episode

Why Design is powered by Kodu, a specialist recruitment partner for the hardware and physical product development industry.

Through honest conversations with designers, engineers, and creative leaders, we explore not just what they build, but why they build it; the beliefs, decisions and responsibility behind meaningful work.

About Kodu

Kodu is a specialist recruitment partner dedicated to physical product development. We connect hardware brands and design consultancies with the very best design and engineering talent, from Industrial Designers and Mechanical Engineers to senior leaders across Product, Technology, and Design.

Our clients range from well-funded start-ups and scale-ups under investor pressure to deliver, through to mature enterprises building new innovation teams. They often face the same challenges: scaling beyond generalists, attracting talent without a recognised employer brand, or struggling with slow, inconsistent hiring processes.

We solve these hiring problems with a proven 7-stage recruitment framework, a proprietary hardware network, and storytelling that builds trust with candidates. This results in a faster, smoother, and more engaging hiring experience.

Kodu consistently delivers results that exceed expectations, with an average time-to-offer of 6 weeks, 97% retention after 12 months, and an all-time NPS of +91 (versus the recruitment industry average of +30).

We act as trusted partners, helping hardware innovators hire better, scale faster, and bring groundbreaking products to market.

๐Ÿ”— Learn more - teamkodu.com

Transcript
Speaker:

(Transcribed by TurboScribe. Go Unlimited to remove this message.) Picture walking into a room full of engineers

Speaker:

on your first day.

Speaker:

Nobody knows what you do, nobody's worked with

Speaker:

someone like you before, and the first thing

Speaker:

someone asks you to do is pick a

Speaker:

colour.

Speaker:

I'm just here to pick the colour of

Speaker:

whatever material you're trying to use on the

Speaker:

prototype.

Speaker:

In this episode I sit down with Dan

Speaker:

Salisbury, someone who's spent over a decade at

Speaker:

some of the most respected design consultancies in

Speaker:

the country, then walked away from all of

Speaker:

it to become the only industrial designer inside

Speaker:

a startup building robotic lab systems.

Speaker:

Recruit really good people and then trust them

Speaker:

to do their job.

Speaker:

Systems that are currently being used to profile

Speaker:

cancer biopsies, accelerate drug discovery, and compress testing

Speaker:

timelines that used to take weeks down to

Speaker:

days.

Speaker:

There's like 100% intent, like this has

Speaker:

to launch, otherwise we collapse as a business

Speaker:

kind of thing.

Speaker:

That's design that isn't decorative, that's design that's

Speaker:

consequential.

Speaker:

He had to earn his place from day

Speaker:

one, not with a portfolio, not with a

Speaker:

pitch, just by doing the work and waiting

Speaker:

for people to get it.

Speaker:

Most of them didn't, until they did.

Speaker:

Yeah it was like, I can have it,

Speaker:

I can see the impact I can have

Speaker:

here, and I really believe in what the

Speaker:

product has the potential to do.

Speaker:

And before any of that, there's the story

Speaker:

of standing on a stage in front of

Speaker:

one of the most iconic figures in design

Speaker:

history, a project he'd rehearsed hundreds of times.

Speaker:

Did it go the way he planned?

Speaker:

Not quite.

Speaker:

But what came next is something he hasn't

Speaker:

forgotten.

Speaker:

This is a conversation about belief, impact, and

Speaker:

what it actually means to do design that

Speaker:

matters.

Speaker:

This is Y-Design.

Speaker:

Dan Salisbury, welcome to Y-Design.

Speaker:

Great to have you on the show.

Speaker:

So you've spent over a decade working in

Speaker:

consultancy at DCA and then Layer, before making

Speaker:

the move over to, I'm going to get

Speaker:

this wrong, automata or automator?

Speaker:

Yeah, I got it wrong as well when

Speaker:

I first joined.

Speaker:

It's automata, it comes from automaton, some sort

Speaker:

of Latin reference, I think.

Speaker:

Automata, right.

Speaker:

Okay, so I'm probably going to say that,

Speaker:

you know, five different ways throughout this interview,

Speaker:

but please do correct me.

Speaker:

So automata, you spent just over three years

Speaker:

there now.

Speaker:

Before we kind of dive into how you've

Speaker:

built out automata's hardware function from scratch, let's,

Speaker:

you know, go back to a moment where

Speaker:

everything shifted for you.

Speaker:

You know, ten years in consultancy to then

Speaker:

in-house.

Speaker:

Was there a moment where you realized, automata,

Speaker:

that this is going to be different from

Speaker:

consultancy life?

Speaker:

Yeah, I'd always had in the back of

Speaker:

my mind about going in-house at some

Speaker:

point.

Speaker:

I think it kind of just depended on

Speaker:

what it was that the company did, so

Speaker:

it had to be something that I'd be

Speaker:

interested in, that would excite me.

Speaker:

Obviously, being a consultancy, you get exposed a

Speaker:

lot to the ways of working with in

Speaker:

-house companies.

Speaker:

A lot of the clients with having consultancy

Speaker:

will often have their own design teams, but

Speaker:

they would tend to onboard agencies when they

Speaker:

didn't have the bandwidth or they wanted to

Speaker:

explore something about the kind of like red

Speaker:

tape of a bigger in-house company.

Speaker:

But I didn't want to be kind of

Speaker:

like a cog in the machine, you know,

Speaker:

just being part of a design team in

Speaker:

some sort of like mega corporation.

Speaker:

I think it was just timing, really, like

Speaker:

the automata job, I saw it on LinkedIn.

Speaker:

And the remit was, you know, we have

Speaker:

this hardware product, but we don't have any

Speaker:

industrial design.

Speaker:

So the early remit was to basically come

Speaker:

in, define a design language, define design principles,

Speaker:

and then implement that in the product and

Speaker:

get that product rolled out.

Speaker:

And it was very rapid, like automata was

Speaker:

a startup.

Speaker:

So I think like the opportunity to fit

Speaker:

impact was what attracted me.

Speaker:

So yeah, I was like about three years

Speaker:

into my time at Layer, and the job

Speaker:

came up, saw the description, reasonably, you know,

Speaker:

excited by it.

Speaker:

So I just went for it.

Speaker:

Because generally, I've always kind of followed my

Speaker:

gut, what feels right, and what excites me.

Speaker:

And it did.

Speaker:

But there was other opportunities I was exploring

Speaker:

there at the time that didn't quite feel

Speaker:

right.

Speaker:

So this one did.

Speaker:

So yeah, a long way around of saying

Speaker:

that's kind of, it just excited me when

Speaker:

I saw the job description, really.

Speaker:

We'll dive into that a little bit later,

Speaker:

because I have a terrible habit of going

Speaker:

completely off script after the first question.

Speaker:

So we'll dive into that.

Speaker:

But what did it feel like, you know,

Speaker:

joining automata and to be the only designer

Speaker:

in a deep tech lab surrounded by engineers

Speaker:

and roboticists?

Speaker:

Yeah, it was a bit, particularly from Layer,

Speaker:

where you're going from somewhere which the entire

Speaker:

team pretty much is industrial designers.

Speaker:

I was then put into an environment where

Speaker:

at the time when I joined, there was

Speaker:

maybe about 30 people in the hardware team,

Speaker:

kind of a mix of mechanical engineers, electronics,

Speaker:

like software people.

Speaker:

And they were all put in place to

Speaker:

develop what was automata's products at the time,

Speaker:

which is a robot arm.

Speaker:

So it was all very much like, get

Speaker:

this very complex, highly engineered thing into production.

Speaker:

And nobody had ever worked with an industrial

Speaker:

designer before.

Speaker:

So there was a bit of a task

Speaker:

in terms of people understanding what I did.

Speaker:

I remember being asked in my first week

Speaker:

to pick a color for something.

Speaker:

I was like, I'm not just here to

Speaker:

pick, you know, pick the color of whatever

Speaker:

material you're trying to use on the prototype.

Speaker:

So I feel like the bigger challenge really

Speaker:

is like, trying to work and collaborate with

Speaker:

people when they don't really understand what you've

Speaker:

been born to do.

Speaker:

I think really the only way you can

Speaker:

explain it, you can describe it, you can

Speaker:

run through your past experience, but the only

Speaker:

real way is to actually just demonstrate it.

Speaker:

So now three years in, like the engineers

Speaker:

who are still here from when I first

Speaker:

joined, you know, they get it now because

Speaker:

they've seen the impact from like a prototype,

Speaker:

which was very, you know, functional.

Speaker:

Through to now, like we're on the second

Speaker:

generation of what that's become.

Speaker:

So I think now they definitely see like

Speaker:

results of it.

Speaker:

But yeah, it's just kind of more like

Speaker:

demonstrate by doing.

Speaker:

You can't really explain industrial design.

Speaker:

It's hard to explain it.

Speaker:

People don't quite get it.

Speaker:

Yeah, it's coming from a consultancy background, especially

Speaker:

layer where you're surrounded by design.

Speaker:

You know, there's an assumption that people know

Speaker:

what it is by osmosis, but yeah, surrounded

Speaker:

by electronics and kind of engineers.

Speaker:

But some probably don't see the point, you

Speaker:

know, a lot of the time because, you

Speaker:

know, they're the stuff that's making the magic

Speaker:

happen.

Speaker:

But was that hard, you know, those early

Speaker:

days of kind of justifying your position?

Speaker:

I think what made it easier was the

Speaker:

design team.

Speaker:

You know, like my boss who brought me

Speaker:

in, who was the head of design, she's

Speaker:

from a digital background, but she was great

Speaker:

in terms of like, just bringing me in

Speaker:

and trusting me as an expert in it,

Speaker:

just let me hit the ground running.

Speaker:

And then there was also a few of

Speaker:

the UX designers and visual designer.

Speaker:

And even though they're slightly different discipline, you

Speaker:

know, they get it.

Speaker:

So at least like I had like the

Speaker:

like minded people around me.

Speaker:

So that definitely helped.

Speaker:

But it didn't really bother me in terms

Speaker:

of, I guess, like trying to help people

Speaker:

understand the role.

Speaker:

Because like I said, like, it's a very,

Speaker:

it's a start up, it's very fast paced.

Speaker:

I just did what I do.

Speaker:

And then the results kind of speak for

Speaker:

themselves.

Speaker:

And then people get it.

Speaker:

And also, like, I've kind of, I think

Speaker:

any industrial designers had this battle like their

Speaker:

whole career with even, you know, engineers, or

Speaker:

passing comments of like, I'll just make it

Speaker:

look pretty, like that kind of thing, which

Speaker:

always like gets under the skin of not

Speaker:

just industrial designers, I guess, under the skin

Speaker:

of the digital designers over with as well.

Speaker:

And I've always had that battle.

Speaker:

I had that battle at uni when there

Speaker:

was like a BSc side of the course,

Speaker:

which they would deride the BA side of

Speaker:

the course a lot saying it's just about

Speaker:

pretty pictures.

Speaker:

I even had it, you know, a DCA

Speaker:

from more of the engineering people, they just

Speaker:

saw design as like a beautification exercise rather

Speaker:

than anything else.

Speaker:

But if you get it, you get it.

Speaker:

That's fine.

Speaker:

And it's fine if you don't get it.

Speaker:

As long as you trust people to do

Speaker:

their job.

Speaker:

Slightly contentious one here.

Speaker:

But what do you say to people who

Speaker:

might refer to industrial designers as felt tip

Speaker:

fairies?

Speaker:

Because I've heard that kind of banded around

Speaker:

many times throughout my career.

Speaker:

Yeah, yeah.

Speaker:

I mean, generally, I've always found like, if

Speaker:

someone holds that opinion, you can never really

Speaker:

change it.

Speaker:

And even if you demonstrate otherwise, you still

Speaker:

tend to get those, like sort of snippy

Speaker:

comments from time to time.

Speaker:

The way I always try and explain it,

Speaker:

like when people say, I'm making it look

Speaker:

pretty.

Speaker:

The way I talk about it is it's

Speaker:

giving something an identity.

Speaker:

You know, it's not arbitrary.

Speaker:

But it's not aesthetics for the sake of

Speaker:

aesthetics, which like something, you know, like art

Speaker:

would be, there's a meaning and a purpose

Speaker:

and a rationale behind it.

Speaker:

So, you know, I could talk for hours

Speaker:

on like, the design language and the design

Speaker:

strategy behind like automotive hardware and why everything

Speaker:

has been treated how it is.

Speaker:

And part of that design strategy is also

Speaker:

taking into account, you know, the market we're

Speaker:

in, differentiation from our competitors.

Speaker:

Where it's a lot of the space we're

Speaker:

in is like it's B2B and a lot

Speaker:

of B2B products just have no consideration for

Speaker:

like an end user and no consideration for

Speaker:

industrial design.

Speaker:

So those people working in those spaces to

Speaker:

then bring a little bit of joy, bring

Speaker:

a little bit of like, it's like higher

Speaker:

quality execution and thought to things just makes

Speaker:

their lives a bit better, even though they're

Speaker:

not the end customer.

Speaker:

And it also takes into account the manufacturing

Speaker:

process we have to use.

Speaker:

So like I've built a design language here,

Speaker:

which we are low volume.

Speaker:

So we're always driven down routes of like,

Speaker:

you know, a lot of it is just

Speaker:

anything you fabricate, CNC sheet or, you know,

Speaker:

five axis and a bit of, yeah, it's

Speaker:

basically the other, basically the two manufacturing processes

Speaker:

we can use.

Speaker:

And I've let into that for the design

Speaker:

language as well.

Speaker:

So that's kind of like the impact of

Speaker:

what industrial design does.

Speaker:

If it was felt it varies, it would

Speaker:

just be like, oh, here's like a pretty

Speaker:

picture of what a bench could be, but

Speaker:

no thought about how to actually make it

Speaker:

like on cost or deliver a good experience

Speaker:

for the person using it.

Speaker:

That's the added layer, isn't it?

Speaker:

That's the bit that adds impact and value.

Speaker:

It's the kind of the pretty bit, but

Speaker:

then the actual functional, what the why bit

Speaker:

and the how.

Speaker:

So fantastic.

Speaker:

Well, let's ask the podcast title question now.

Speaker:

As I said, we've flipped things around slightly

Speaker:

because we usually lead with this, but let's

Speaker:

dive into your origin story and kind of,

Speaker:

you know, why design?

Speaker:

What led you down this path of industrial

Speaker:

design in the first place?

Speaker:

Yeah, I was thinking about this this morning,

Speaker:

you know, with the podcast coming up and

Speaker:

I was trying to go back.

Speaker:

And I think it started, I remember in

Speaker:

year, probably year eight, like secondary school, I

Speaker:

don't know how old you are, like 12

Speaker:

or 13, did some sort of like questionnaire

Speaker:

about careers, you know, and I remember graphic

Speaker:

design being one of the results of that

Speaker:

questionnaire.

Speaker:

Wasn't really something I was aware of at

Speaker:

the time.

Speaker:

I think when you're 12 or 13, you

Speaker:

don't really think about the process behind that

Speaker:

goes into everyday things and objects around the

Speaker:

world.

Speaker:

But like graphic design was maybe a bit

Speaker:

more understandable.

Speaker:

You know, logos, posters, that kind of stuff.

Speaker:

So I kind of gravitate towards that initially.

Speaker:

I would say as well, it also suggested

Speaker:

like park ranger as one of the options

Speaker:

as well.

Speaker:

So I don't know how good this thing

Speaker:

was.

Speaker:

But at least I've seen the hat with

Speaker:

your beard, you know, strong look.

Speaker:

I don't know.

Speaker:

There's probably some question about working outdoors or

Speaker:

something.

Speaker:

Maybe I said I'd be slightly interested in

Speaker:

that.

Speaker:

I don't know.

Speaker:

That kind of planted the seed.

Speaker:

And then my secondary school offered graphic design

Speaker:

as a GCSE.

Speaker:

So I just took it generally at school.

Speaker:

I just took the subjects I was interested

Speaker:

in.

Speaker:

I didn't really think about it from like,

Speaker:

what I want to do and all that

Speaker:

point of view.

Speaker:

It's just that I enjoy doing design.

Speaker:

So out of like cooking and whatever the

Speaker:

DT curriculum was, graphic design was the most

Speaker:

prevalent one.

Speaker:

It was like textiles or cooking with either

Speaker:

options.

Speaker:

So I was doing that GCSE.

Speaker:

And then I just went to my local

Speaker:

state comprehensive.

Speaker:

But around that time, the school became a

Speaker:

specialist technology college, which I still don't really

Speaker:

know what it meant.

Speaker:

But I think fundamentally, they got a bit

Speaker:

more funding for design technology.

Speaker:

So they actually offered as an A-level

Speaker:

product design and technology, I think was the

Speaker:

title.

Speaker:

And this was before like UX and UI

Speaker:

designers hijacked product design as a job title

Speaker:

and job description.

Speaker:

But really that was about, it was an

Speaker:

industrial design GCSE and A-level essentially.

Speaker:

You got to pick something to design, you

Speaker:

run through that concept, you did a bit

Speaker:

of model making, you presented it, you did

Speaker:

a bit of design for manufacturing, cost analysis

Speaker:

essentially.

Speaker:

And my A-level teacher, again, I didn't

Speaker:

really realize this was a thing you can

Speaker:

do in the real world.

Speaker:

But my A-level teacher at the time,

Speaker:

Mr. Bird, he said, I think it was

Speaker:

just a chat one time.

Speaker:

I was good at it, I was getting

Speaker:

good results and good marks.

Speaker:

Then he said, you can go do this.

Speaker:

And he pushed me towards, he went to

Speaker:

Loughborough himself.

Speaker:

He said, yeah, Loughborough is one of the

Speaker:

best places.

Speaker:

I think at the time, we're talking 2007,

Speaker:

I think, around this time, 2007, 2008.

Speaker:

So Loughborough, Brunel, and Northumbria were probably the

Speaker:

three big universities at the time if you

Speaker:

were going into design.

Speaker:

I started going to open days.

Speaker:

But he was the one who really made

Speaker:

me realize that it was not just a

Speaker:

job you could go and do, but actually

Speaker:

something I was capable of going to do.

Speaker:

So for me, I just enjoyed it.

Speaker:

So I just followed it.

Speaker:

From that point, I followed it to graphic

Speaker:

design through to the design A-level, and

Speaker:

then through to going and doing industrial design

Speaker:

at Loughborough University.

Speaker:

And really, like I said, I just followed

Speaker:

what I enjoyed.

Speaker:

Yeah, I think he's probably been the most

Speaker:

impactful teaching figure, I guess, in my career

Speaker:

and that kind of thing, exactly what a

Speaker:

teacher should do.

Speaker:

And sadly, he passed away suddenly a few

Speaker:

years ago.

Speaker:

And a bit of trivia, his son is

Speaker:

Max Bird, who plays for Bristol City now.

Speaker:

He was in the Derby Academy.

Speaker:

So yeah, so his son's a championship footballer.

Speaker:

But yeah, like he was a great, great

Speaker:

source of, I guess, like helping me understand

Speaker:

and pushing me in the right direction, seeing

Speaker:

what I could do, I guess.

Speaker:

So that's why design.

Speaker:

And then from there, really, it's pretty, you

Speaker:

know, that focus is already narrowed.

Speaker:

And, you know, I went to go to

Speaker:

consultancy once I started to get towards the

Speaker:

end of the course, and just for that

Speaker:

breadth of product exposure, ended up chatting to

Speaker:

DCA folk at the degree show at Loughborough,

Speaker:

got the job at DCA, before I'd been

Speaker:

there for a couple of years and had

Speaker:

been there for seven years.

Speaker:

But I moved down to London and joined

Speaker:

Layer.

Speaker:

And then, yeah, now three years at Layer,

Speaker:

I hopped to Automata, where now I'm in

Speaker:

for another three years.

Speaker:

So yeah, it moved back.

Speaker:

I guess you would have been a year

Speaker:

or two behind Benjamin Hubert at Loughborough.

Speaker:

Yeah, I think then I remember seeing his

Speaker:

sketches for his final year project up around

Speaker:

what was the Bridgman Centre at the time.

Speaker:

That's not there anymore.

Speaker:

Yeah, he was probably, I think he graduated

Speaker:

in 2008, maybe.

Speaker:

I think he might graduate the year I

Speaker:

started potentially.

Speaker:

He's probably about 40 now.

Speaker:

So yeah, he'll be maybe four or five

Speaker:

years ahead of me.

Speaker:

But yeah, I guess I was like, kind

Speaker:

of aware of him from a very early

Speaker:

point.

Speaker:

And I'll be able to go to Loughborough

Speaker:

as well.

Speaker:

Did you work together at DCA or had

Speaker:

he left by that point?

Speaker:

No, he left before I started.

Speaker:

But again, he'd definitely left his mark at

Speaker:

DCA on some of the projects.

Speaker:

Yeah.

Speaker:

That's cool.

Speaker:

It's interesting how these things overlap.

Speaker:

I've got a friend who studied in the

Speaker:

same cohort as Benjamin and they've gone in

Speaker:

completely different paths.

Speaker:

Paul's gone down more of a manufacturing route

Speaker:

in the Midlands.

Speaker:

And then Benjamin's obviously doing this very exciting

Speaker:

projects down in London.

Speaker:

Let me pause here for a moment.

Speaker:

Most of the leaders on this podcast did

Speaker:

not grow because they hired quickly.

Speaker:

They grew because they hired well.

Speaker:

The right senior engineer can accelerate a hardware

Speaker:

roadmap by a year.

Speaker:

The wrong one can stall it.

Speaker:

At KODU, we help physical product teams make

Speaker:

that hire with clarity and precision.

Speaker:

If you're about to make a key design

Speaker:

or engineering hire or thinking about your own

Speaker:

next move, reach out to me on LinkedIn.

Speaker:

Let's talk before you commit.

Speaker:

When you look back, Dan, at your early

Speaker:

years at DCA, what kind of designer were

Speaker:

you then?

Speaker:

I'll be honest, I wasn't very good.

Speaker:

In terms of, I often joke, I did

Speaker:

a lot of recruitment.

Speaker:

Like a bit later on at DCA, I

Speaker:

did a lot of recruitment.

Speaker:

I did a lot of recruitment at Layer

Speaker:

as well.

Speaker:

So seeing lots of portfolios.

Speaker:

The bit I always took in the back

Speaker:

of my mind was I was dismissing portfolios

Speaker:

or rejecting them and stuff when they were

Speaker:

far better than what I was doing at

Speaker:

that age.

Speaker:

But I think also, I think the tool

Speaker:

sets changed and I think the bar has

Speaker:

just risen.

Speaker:

I think particularly, there was no real rendering

Speaker:

when I was around the time of graduation.

Speaker:

KeyShot didn't exist.

Speaker:

And I think that and some of the

Speaker:

CAD tools have gotten way easier to use.

Speaker:

So now you are seeing much more polished,

Speaker:

refined designs.

Speaker:

I think also where you can see inspiration

Speaker:

has changed.

Speaker:

There was no Pinterest and that kind of

Speaker:

stuff when I was doing this kind of

Speaker:

stuff.

Speaker:

But yeah, my portfolio was quite weak looking

Speaker:

back at what it was when I graduated.

Speaker:

But I think it was more from how

Speaker:

I was presenting the work and the things

Speaker:

I was talking about.

Speaker:

And also just my approach to styling.

Speaker:

I think I used to overcomplicate the way

Speaker:

I was approaching form and detailing.

Speaker:

It was too complex.

Speaker:

I think the hardest thing to do as

Speaker:

an illustrator is kind of restraint, but restraint

Speaker:

in a compelling way without it looking basic

Speaker:

or simple.

Speaker:

But I think there was enough there that

Speaker:

they saw, I guess, potential.

Speaker:

I did my placement year at Diageo.

Speaker:

So Umbrella Corporation, you were in lots, you

Speaker:

know, Smirnoff, Ginnett, Johnnie Walker.

Speaker:

So there was a lot of like primary

Speaker:

packaging and one-off like airport duty-free

Speaker:

type things I was working on there for

Speaker:

like Johnnie Walker and that kind of stuff.

Speaker:

So there was a bit of FMCG packaging.

Speaker:

So coming out of uni, I remember like

Speaker:

the packaging department at Seymour Powell, I interviewed

Speaker:

there.

Speaker:

They made it very clear that if you

Speaker:

join the packaging team, it's not a shortcut

Speaker:

to joining their like ID team because they

Speaker:

had different teams.

Speaker:

But then also GCA, you know, with their

Speaker:

clients, a lot of their clients being like

Speaker:

GSK and Reckitt Benckiser and a few of

Speaker:

the FMCG brands.

Speaker:

I think they saw that and were like,

Speaker:

okay, that could be useful.

Speaker:

And Tip Sharp was the head of design

Speaker:

at GCA at the time and he brought

Speaker:

me in.

Speaker:

I think like to answer your initial question,

Speaker:

I think I was probably not confident enough

Speaker:

to stick to what I felt comfortable with.

Speaker:

So I was trying to be the kind

Speaker:

of designer that I was seeing the other

Speaker:

designers at GCA being, which was like a

Speaker:

lot of, you know, everyone at GCA at

Speaker:

that time had a giant Wacom tablet.

Speaker:

So a lot of the work would be

Speaker:

in the early, like the first stages of

Speaker:

work would be really beautiful, like Wacom digital

Speaker:

sketches.

Speaker:

But I've never really been that strong at

Speaker:

sketching, not from a presentation point of view,

Speaker:

like I'll sketch rough and dirty.

Speaker:

But I've always been really strong and really

Speaker:

quick in CAD.

Speaker:

So I can visualize head very well in

Speaker:

3D.

Speaker:

And I would just like, now, I just

Speaker:

jump into CAD, I can mock something in

Speaker:

CAD and render it quicker than I could

Speaker:

like do layers and layers of sketching.

Speaker:

And I think the industry has now shifted

Speaker:

towards that.

Speaker:

But at the time, it was still a

Speaker:

bit more traditional focus where you would present

Speaker:

sketches in like a first phase.

Speaker:

And I was struggling with that.

Speaker:

And like the feedback I would get would

Speaker:

be like, yeah, I was on, I almost

Speaker:

didn't pass my probation period.

Speaker:

Oh, really?

Speaker:

Yeah, there was a bit of debate around

Speaker:

the time.

Speaker:

You know, again, I was showing promise, but

Speaker:

not quite enough.

Speaker:

And then I really hit the ground running

Speaker:

at DCA when I kind of ignored the

Speaker:

feedback around, don't go into CAD too early.

Speaker:

And all this kind of stuff.

Speaker:

So I decided, okay, I'm going to go

Speaker:

into CAD.

Speaker:

And then I'll sketch over it.

Speaker:

You know, I then just like use my

Speaker:

skill set to then help support the projects.

Speaker:

So that took a couple of years like

Speaker:

to kind of get to that level of

Speaker:

confidence.

Speaker:

But once I kind of embraced, like I

Speaker:

just played to my strengths.

Speaker:

I think eventually the feedback of like, oh,

Speaker:

Dan jumps into CAD too early and like

Speaker:

my performance reviews and stuff that stopped coming

Speaker:

because they realized that actually, that's like how

Speaker:

I work.

Speaker:

And then for the end of everyone, I

Speaker:

would have to take a layer, like the

Speaker:

first phases of, even towards the end of

Speaker:

DCA, like first phase presentations would be like

Speaker:

photo realistic renders of like the perfect detail

Speaker:

CAD and everything.

Speaker:

That's just like the way it's moved to

Speaker:

now.

Speaker:

So yeah, any advice I'd give to anyone

Speaker:

is just like stick to your strengths.

Speaker:

Don't try and be like other designers because

Speaker:

everyone's different and how they approach problems.

Speaker:

Yeah, absolutely.

Speaker:

I mean, I've agonized over this over the

Speaker:

years when you're building teams and everyone's got

Speaker:

their own strengths, but as a consequence, they've

Speaker:

got gaps.

Speaker:

They've got weak areas that they're not so

Speaker:

strong in.

Speaker:

And when I was kind of a young

Speaker:

manager trying to train someone on something that

Speaker:

they weren't particularly good at all, probably weren't

Speaker:

that bothered about really.

Speaker:

They didn't see the point of it because

Speaker:

they were really good in other areas.

Speaker:

And as soon as I started, someone said

Speaker:

to me, why are you wasting so much

Speaker:

energy trying to force this person to be

Speaker:

someone that they don't want to be?

Speaker:

If I just make the most out of

Speaker:

what they're really good at, if they're good

Speaker:

for the business, and then you can find

Speaker:

other people or you can compensate in other

Speaker:

areas because you've got a good blend in

Speaker:

the team.

Speaker:

So as soon as I realized that, it

Speaker:

reduced a lot of stress for me personally

Speaker:

because it's like, well, that person is going

Speaker:

to be less annoyed because they're doing something

Speaker:

they don't enjoy that they're all good at

Speaker:

and they're going to be happy doing the

Speaker:

things that they're good at.

Speaker:

And I can turn my attention to encouraging

Speaker:

that and getting them better at the things

Speaker:

they're good at.

Speaker:

So yeah, I love that.

Speaker:

You mentioned that you met Dieter Rams.

Speaker:

Yes.

Speaker:

In your career as well.

Speaker:

How did meeting him kind of shape your

Speaker:

idea of what good design means?

Speaker:

Um, yeah, even now, it was like I

Speaker:

realized it's actually 10 years ago.

Speaker:

Yeah, it was 2015.

Speaker:

So there was something called, I can't remember

Speaker:

the order of these things, but I think

Speaker:

something that DCA worked quite good at was

Speaker:

if people had ideas, they'd let them explore

Speaker:

concepts.

Speaker:

And if those concepts were kind of like

Speaker:

compelling, they would fund like submissions to design

Speaker:

awards.

Speaker:

So, you know, I did get a couple

Speaker:

of IFs and red dots for concepts we

Speaker:

worked up.

Speaker:

And, you know, they're not cheap, but, you

Speaker:

know, DCA were good at investing in that.

Speaker:

And, you know, for me to go to

Speaker:

the awards ceremony sometimes and that kind of

Speaker:

thing.

Speaker:

But like, I think this one came about

Speaker:

was there's a guy called James May.

Speaker:

He's still at DCA now, and he predominantly

Speaker:

works in, like, I can't see, forgot.

Speaker:

It's like basically B2B, side of the business,

Speaker:

I think it's called now.

Speaker:

He had this idea to do a fuse

Speaker:

box.

Speaker:

I think his idea was, why can't the

Speaker:

fuse box be used to like actually monitor

Speaker:

your energy consumption?

Speaker:

I think that was kind of like the,

Speaker:

like I said, the light bulb, the light

Speaker:

bulb he had.

Speaker:

And when I heard this, it was one

Speaker:

of those ones where just the idea of

Speaker:

like how to do that almost just came

Speaker:

fully formed into my head.

Speaker:

Like I barely did any, you know, I'll

Speaker:

talk about jumping into CAD.

Speaker:

I pretty much like jumped into CAD.

Speaker:

I think I did two options and I

Speaker:

just went with one of them.

Speaker:

And that one was the one that I

Speaker:

visualized pulled together into like the submission.

Speaker:

And I think originally I was just pulling

Speaker:

it together to sort of submit to a

Speaker:

Red Dot concept or something.

Speaker:

And, you know, I went with James on

Speaker:

that and there was a couple of other

Speaker:

guys who supported from electronics point of view,

Speaker:

like some of the electronics engineers, a chap

Speaker:

called Charles Sparrow.

Speaker:

Worked it up.

Speaker:

And then I think at the time, I

Speaker:

just saw, you know, there was the Braun

Speaker:

Prize, 2015 Braun Prize.

Speaker:

I think the Braun Prize, they only do

Speaker:

it every three years, I think.

Speaker:

It's not like an annual thing.

Speaker:

And it's also, you don't pay to play,

Speaker:

you know, like Red Dot and IF, you

Speaker:

know, you pay to enter that you pay

Speaker:

even more if you win.

Speaker:

This one was, they pick just three, like

Speaker:

out of the submissions, they pick the top

Speaker:

three.

Speaker:

And then you get to go, you'd go

Speaker:

to Germany, go to the Braun HQ and

Speaker:

then present.

Speaker:

And then the audience then votes for gold,

Speaker:

silver, bronze, essentially.

Speaker:

And they have like, there's a professional category,

Speaker:

a student category and like a hobbyist enthusiast

Speaker:

category, something like that.

Speaker:

And the Braun Prize came active.

Speaker:

And the theme for that year was the

Speaker:

extra in the ordinary.

Speaker:

So ordinary objects, which maybe have become maligned,

Speaker:

not really thought about too much.

Speaker:

Like the fuse box was just like perfect

Speaker:

for it.

Speaker:

Like something that's never really been thought about

Speaker:

in terms of how it's designed.

Speaker:

So we submitted it, waited a few minutes

Speaker:

and then yeah, got an email, came through

Speaker:

saying like, you know, congratulations, you're in the

Speaker:

last three.

Speaker:

So I think it was something that has

Speaker:

like, there's maybe 3,000 submissions or something.

Speaker:

We've got the last three for the concept.

Speaker:

Um, so then yeah, we made a model

Speaker:

of it, did some animations to like take

Speaker:

to the show.

Speaker:

And then Dieter Rams was there, you know,

Speaker:

he was part of the audience, he was

Speaker:

part of the jury, not for the actual

Speaker:

deciding the last three, but he was there

Speaker:

to like vote on it on the last

Speaker:

day.

Speaker:

And he was like sat in front row.

Speaker:

And again, credit to DCA, you know, I

Speaker:

was 25 at the time, I was a

Speaker:

mid weight designer.

Speaker:

And Nick Bible, who's the director at DCA,

Speaker:

he let me present.

Speaker:

I think like, but the companies may be

Speaker:

like, you know, this, you know, the creative

Speaker:

director or someone senior or lead would then

Speaker:

take that responsibility.

Speaker:

But they let me present the project to,

Speaker:

you know, Dieter Rams and an auditorium of

Speaker:

around, I don't know, 200 odd people, which

Speaker:

was a very interesting experience.

Speaker:

It's probably the most practiced I've ever been.

Speaker:

Normally my presentation starts, I don't rehearse, I

Speaker:

don't script it, because then it feels forced.

Speaker:

But this one we ran through hundreds of

Speaker:

times before the show.

Speaker:

And yeah, when I did the presentation, we

Speaker:

came second.

Speaker:

The thing that won was a life jacket.

Speaker:

So I think like monitoring energy versus saving

Speaker:

someone's life, you know, that's always going to

Speaker:

win that kind of thing.

Speaker:

And then yeah, in the after party, I

Speaker:

think at the time Dieter would have been

Speaker:

maybe 85, something like that.

Speaker:

And he had this like really beautifully made

Speaker:

walking stick, which apparently people always ask him

Speaker:

where he got it, but apparently someone made

Speaker:

it for him.

Speaker:

And he was like joining in in the

Speaker:

party essentially, you know, he was stopping for

Speaker:

photos and there was lots of like students

Speaker:

there and younger designers all having photos with

Speaker:

him.

Speaker:

He shook my hand, he said congratulations.

Speaker:

We had a brief chat.

Speaker:

And yeah, it's one of those things where

Speaker:

it's just the end, even now it just

Speaker:

feels a bit surreal that I met him.

Speaker:

But also one of the jury was Benjamin

Speaker:

Hubert.

Speaker:

So that was my first exposure, like direct

Speaker:

exposure with him.

Speaker:

So I met him then.

Speaker:

So at least he was, when I did

Speaker:

actually approach Lair eventually, he was already aware

Speaker:

of me.

Speaker:

So it was quite a few years that

Speaker:

I actually made the move to Lair after

Speaker:

that.

Speaker:

But yeah, it was just, I still don't

Speaker:

think there's ever going to be something in

Speaker:

my career that would top that in terms

Speaker:

of when else do you ever get to

Speaker:

meet Dieter Rams.

Speaker:

It was like the point of it.

Speaker:

So yeah, it was, and you also presented

Speaker:

him.

Speaker:

So yeah, that was a really, really quite

Speaker:

amazing thing to do with Shaker.

Speaker:

So it just still feels bizarre.

Speaker:

Yeah.

Speaker:

I mean, it's a, it's a top recruiting

Speaker:

strategy from Benjamin as well, isn't it?

Speaker:

Set on a jury and then, you know,

Speaker:

just keep tabs on the top three.

Speaker:

But yeah, what a pivotal moment for you.

Speaker:

That's amazing.

Speaker:

So yeah, well, let's talk about the shift

Speaker:

then from consultancy to automata.

Speaker:

Told you I'd struggle with that.

Speaker:

So after spending over a decade in agency

Speaker:

and then jumping into automata, what was it

Speaker:

that kind of, that cemented that leap for

Speaker:

you?

Speaker:

You mentioned that the advert stood out.

Speaker:

You were clearly open to opportunities by the

Speaker:

kind of towards the end of your time

Speaker:

at Lair.

Speaker:

But what was it specific, specifically about automata

Speaker:

that really grabbed you?

Show artwork for WHY DESIGN?

About the Podcast

WHY DESIGN?
For people interested in physical product design and development
Why Design is a podcast exploring the stories behind hardware and physical product development. Hosted by Chris Whyte, founder of Kodu, the show dives into the journeys of founders, senior design leaders, and engineers shaping people and planet-friendly products.

Formerly "The Design Journeys Podcast", each episode uncovers pivotal career moments, lessons learned, and behind-the-scenes insights from industry experts. Whether youโ€™re a designer, engineer, or simply curious about how great hardware products come to life, Why Design offers real stories, actionable advice, and inspiration for anyone passionate about design and innovation.

Join us as we listen, learn, and connect through the stories that define the world of physical product development.

About your host

Profile picture for Chris Whyte

Chris Whyte

Hi, I'm your host of Why Design? (Formerly "The Design Journeys Podcast")

I'm also the founder of Kodu - a specialist recruitment consultancy focused exclusively on physical product development. It's the people who I've met in my years in the industry that inspired me to start this podcast.

When I'm not hosting the podcast, I help physical product brands, start-ups and design consultancies identify, attract and hire the best product design & engineering talent ahead of their competitors, across the USA, UK and Europe ๐Ÿ‡บ๐Ÿ‡ธ๐Ÿ‡ฌ๐Ÿ‡ง๐Ÿ‡ช๐Ÿ‡บ

I focus exclusively on ๐ฉ๐ก๐ฒ๐ฌ๐ข๐œ๐š๐ฅ ๐ฉ๐ซ๐จ๐๐ฎ๐œ๐ญ ๐๐ž๐ฏ๐ž๐ฅ๐จ๐ฉ๐ฆ๐ž๐ง๐ญ (๐˜ข๐˜ฏ๐˜ฅ ๐˜ฏ๐˜ฐ๐˜ต ๐˜ข๐˜ฑ๐˜ฑ๐˜ด!)

๐ƒ๐ž๐ฌ๐ข๐ ๐ง & ๐ƒ๐ž๐ฏ๐ž๐ฅ๐จ๐ฉ๐ฆ๐ž๐ง๐ญ ๐‹๐ž๐š๐๐ž๐ซ๐ฌ:
โœ… Do you have high growth plans for your physical product development and engineering division?
โœ… Would you like to engage with and source those hard-to-find Design Engineers and Industrial Designers?
โœ… Are you spending too much time in the hiring process only to find that the talent doesn't match your expectations?

๐ƒ๐ž๐ฌ๐ข๐ ๐ง ๐„๐ง๐ ๐ข๐ง๐ž๐ž๐ซ๐ฌ, ๐Œ๐ž๐œ๐ก๐š๐ง๐ข๐œ๐š๐ฅ ๐„๐ง๐ ๐ข๐ง๐ž๐ž๐ซ๐ฌ ๐š๐ง๐ ๐ˆ๐ง๐๐ฎ๐ฌ๐ญ๐ซ๐ข๐š๐ฅ ๐ƒ๐ž๐ฌ๐ข๐ ๐ง๐ž๐ซ๐ฌ:
โœ… Are you interested in joining an exciting start-up, design consultancy or technology brand?
โœ… Interested in honest, transparent advice as to which companies would be the best fit for you?

If you agree with any of the above, I know how you feel as I deal with people just like you every day.

I have successfully placed hundreds of design engineers, industrial designers, managers and directors into some of the world's most exciting technology brands, start-ups and consultancies.

My clients tell me they work with me because:

โญ I focus on long-term relationship building, not transactions
โญ I speak their language and understand their businesses and job roles
โญ Iโ€™m professional, yet friendly and very approachable
โญ My robust process significantly reduces time-to-hire

Iโ€™ve worked within consumer electronics, homewares, kitchen appliances, e-bikes, medical devices, gaming controllers, furniture, life-sciences, audio-equipment, vacuum cleaners and more!

Typically, I recruit the following roles:
๐Ÿ’ก VP Engineering
๐Ÿ’ก Engineering Director
๐Ÿ’ก Design Manager
๐Ÿ’ก Industrial Designer
๐Ÿ’ก Product Designer (products not apps!)
๐Ÿ’ก Product Design Engineer
๐Ÿ’ก Mechanical Design Engineer
๐Ÿ’ก Mechanical Engineer

Outside of work, I'm a wannabe rock star and a father to two teenagers. I support Manchester United and I'm terrible at FIFA/FC24 ๐Ÿค“

If you want to talk about my work or anything else, message me on here and I'll respond as soon as I can. Or you can reach me via:

chris@teamkodu.com

UK: +44 7538 928 518
US: +1 862 298 5088