Shadow Design Teams with Audrey Crane, Partner at DesignMap

Inside Outside Innovation

​On this week's episode of Inside Outside Innovation, we welcome back Audrey Crane, partner at DesignMap. Audrey and I talk about the challenges and costs of shadow design teams and the impact of having non designers do design work. Let's get started.

Inside Outside Innovation is the podcast to help new innovators navigate what's next. Each week, we'll give you a front row seat into what it takes to learn, grow and thrive in today's world of accelerating change and uncertainty. Join us as we explore, engage, and experiment with the best and the brightest, innovators, entrepreneurs, and pioneering businesses. It's time to get started.

Interview Transcript with Audrey Crane, Partner at DesignMap

Brian Ardinger: Welcome to another episode of Inside Outside Innovation. I'm your host, Brian Ardinger, and as always, we have another amazing guest. Today we have Audrey Crane. She is a partner at Design Map, Author of What CEOs Need to Know About Design and also now a second time guest. Welcome, Audrey.

Audrey Crane: Yeah, thank you, Brian. Thanks so much for having me back.

Brian Ardinger: I'm excited to have you back because it's been a while. You know, you're a long time Silicon Valley design leader and you're now resident back here in the Silicon Prairie here in Nebraska. I think you came right back right before COVID hit. So probably a lot to discuss about that but wanted to welcome you back on the show.

One of the reasons I wanted to have you back is I've been following you and you've been writing about some new interesting topics in and around this world of design and one of the most recent pieces I saw was a post about the cost of what you're calling shadow design teams. So, I wanted to kind of kick off the podcast with a little talk about what do you mean by shadow design teams and what's the implications of that?

Audrey Crane: It's interesting right now there's a lot of conversation about like the value of design, the ROI of design. I don't know if you've heard all the chatter about that. It seems like impossible to avoid. Recently, there's a very popular blog post about the sort of gaslighting of designers with this whole value of design thing.

You know, when we first started talking about it a couple of years ago, I was like, great, you know, designers should talk business. That's part of the bounded problem solving that makes design fun and interesting. And I was all in on that conversation for a long time and I still am. It's the first chapter of my book actually is ROI of Design.

And it's hard to feel like that conversation is getting us where we want to go. It's hard to feel like it's getting us very far. What has been interesting to me is to look, instead of saying to organizations like, hey, you should invest more in design. Like because of the ROI, let's look at what you're spending on design today.

And if that's the most effective spend that you could possibly make. And especially right now, the economy isn't great, especially in the tech industry, like let's look more at operational efficiency. So, with some of our clients and friends, we're running a survey to understand who is doing design outside of the design team.

So, we're asking product managers, engineers, QA people, business analysts, executives, anybody you can get to take the survey, how much time they're spending alone doing design. So, if they're in a room with somebody else, a designer talking about something that doesn't count. We're not worried about that. But we're just measuring, like I'm doing solo work that a designer might normally do.

And the numbers that are coming back are astonishing, like flabbergast. So one client that we did it with, she has a design team of like a dozen. There are 150 engineers. So already you're like, hmm, I don't know if the ratio is quite going to hold up there. But when we ran the survey, there were 22 full time employees worth of design being done by non-designers. Which is crazy. And every time we've run this survey, it's just a shocking number.

Brian Ardinger: And you talked a little bit about the fact that it seems weird because you wouldn't unknowingly pay designers to code or things along those lines. So why are we paying folks that necessarily don't have the background or expertise of what a true designer could bring to the table? And that is costing companies money, time, resources, things along those lines. Is that the premise?

Audrey Crane: Absolutely. Yeah. And morale, honestly, it's been interesting. I mean, I certainly have worked with plenty of organizations where there's a front-end engineer, there's a product manager that's doing a lot of design work and they like it.

And when we started running this survey, I expected a lot of the answers to be, yeah, well I do design, but I do it because I like to do it. I think my work is as good as a designer, but most of the time what we're hearing back is, I wish a designer could do it. They're faster than me. I don't feel competent at this.

I am not enjoying it. I have other stuff that I need to do and this is slowing me down, but there weren't designers available to work on this project or more frightening even is I didn't know how to work with the design team that we have internally. The costs are some engineers and some product managers are probably great designers.

I'm sure there are some out there. But generally, if we look across the board, it's probably lower quality design. It's probably slower design. It's also probably taking away from all the work that only an engineer can do or only a product manager could do. So, it's slowing down velocity on other fronts as well.

And it's a morale hit for the people who don't want to be doing it and are frustrated by it and the designers who are on the one hand trying to make a case for investing when this huge investment is already happening in design just like in a different part of their work.

Brian Ardinger: Obviously organizations probably either maybe don't know this is happening or aren't actively trying to use additional resources on projects and that. What are some of the kinds of drivers that you think are causing companies to put the design effort onto other people's backs versus hiring designers or focusing on the right mix of talent?

Audrey Crane: That's a good question. I mean, I think part of it is that they just don't realize how much design work there is to do. And so that's the big part of this is like, who knew that in this organization, there was 34 people's worth of design to do, to be done. I wouldn't have guessed that, right. So, it's like kind of that old trope of the alternative to good design isn't no design, it's bad design. Like it's just not happening, right? It can't be happening. That can't be happening.

So, I think that that's part of it. I do feel like design teams are often perceived just as cost centers. And that's why we're having these conversations about the ROI of design and the value of design. And we do hear some pushback from designers saying, is there an ROI of engineering, is that being calculated?

I'm sure it is in some organizations, but. It's such a prevalent conversation. I do think that people like to do it. I also do think some people, not most people, as it turns out, interestingly, and I also do think that there's the, the Dunning Kru...