رونوشت 🔗
WEBVTT
00:00:03.833 --> 00:00:10.250
Welcome back everyone, to Seriously Curious, a podcast about all things experience for business strategy and design.
00:00:10.458 --> 00:00:18.166
I'm Chris Rockwell, I'm president and founder of Lextant, where we put all things human at the center of innovation and design.
00:00:18.375 --> 00:00:21.916
I'm super excited today to have Carly Price with us.
00:00:22.250 --> 00:00:37.707
Carly is an industrial designer by training, has her MBA from Wharton, and she's a strategic thought leader and entrepreneur who's led the UX in all different kinds of companies, including IDO, JP Morgan Chase, Walmart, and Ford Motor Company.
00:00:38.082 --> 00:00:44.207
And I'm super excited today because Carly recently penned a paper on design thinking.
00:00:44.207 --> 00:00:49.790
And really, what makes it effective in businesses and especially from a practitioning standpoint.
00:00:49.790 --> 00:00:55.540
So I'm super excited to get into it today and really answer the question, is design thinking still relevant?
00:00:55.540 --> 00:00:58.625
You know, there's word on the street that design thinking is dead.
00:00:58.665 --> 00:00:59.625
Is that really true?
00:00:59.625 --> 00:01:03.832
So I'm super excited to have Carly here today to help us discuss that.
00:01:03.832 --> 00:01:06.750
Carly, welcome to Seriously Curious.
00:01:06.750 --> 00:01:08.540
Thank you so much for having me.
00:01:08.540 --> 00:01:09.790
Let's start with you.
00:01:09.790 --> 00:01:13.457
Like how did you what was your professional career like?
00:01:13.457 --> 00:01:14.290
How did you get here?
00:01:15.665 --> 00:01:16.125
Wonderful.
00:01:16.125 --> 00:01:20.040
So I started out as an industrial designer in New York.
00:01:20.082 --> 00:01:24.625
I landed an internship at Smart Design while I was still in school at Pratt Institute.
00:01:24.625 --> 00:01:27.500
And that really paved the path for my career.
00:01:27.500 --> 00:01:36.290
After about ten years at Smart, I moved to IDO And between Smart and IDO you know, the design world was evolving quite a bit.
00:01:36.707 --> 00:01:43.000
The beginning of my career, it was pretty straightforward, like we would get a brief from a client to design a product.
00:01:43.250 --> 00:01:50.332
We thought a lot about ergonomics and human factors, especially with products like OXO, Good Grips kitchen tools.
00:01:50.625 --> 00:02:01.415
So that was really the training I had, developing, you know, the perfect physical object that really met human needs from a usability point of view.
00:02:01.915 --> 00:02:06.332
What was wonderful in that first part of my career is that design was evolving.
00:02:07.250 --> 00:02:17.207
We started focusing on ergonomics, but we really shifted to focus on behavior in addition to ergonomics with in context, ethnographic research.
00:02:17.500 --> 00:02:37.665
And that really changed my career trajectory from really thinking about atoms and designing, you know, perfect, beautiful forms to thinking about human needs and how the products we're developing can suit human needs and address unmet needs, but also embody and express a brand for our clients.
00:02:38.457 --> 00:02:44.957
So that's when I started to see the intersection of design and business and became really excited about that.
00:02:44.957 --> 00:02:51.165
After consulting for a number of years, I wanted to move in-house to have more accountability to deliver.
00:02:51.790 --> 00:02:59.375
We did a lot of beautiful, thoughtful work in IDO but so much of it was front end and conceptual and didn't always make it to market.
00:02:59.375 --> 00:03:05.290
So by moving in-house, I wanted to see that impact and have that accountability all the way through.
00:03:05.415 --> 00:03:08.957
So my first step after consulting was to join a startup.
00:03:09.500 --> 00:03:11.540
I was an early employee with Casper.
00:03:11.540 --> 00:03:20.250
We launched five products in two years, built a team there from scratch with one of the co-founders, so learned a ton during that time.
00:03:20.665 --> 00:03:26.375
And that really gave me the confidence to launch my own startup, which I worked on full time for a year.
00:03:26.375 --> 00:03:27.707
Still working on it.
00:03:27.707 --> 00:03:30.707
Were planning to launch our Kickstarter soon.
00:03:30.832 --> 00:03:40.332
And at that point after the year in the startup, I wanted to go back into the into the design world, with a full time role.
00:03:40.332 --> 00:03:46.332
And that's when I went in-house on the corporate side, first with Chase, followed by Ford, and most recently, Walmart.
00:03:47.332 --> 00:03:50.082
Wow. That's a that's an amazing career arc.
00:03:50.082 --> 00:04:01.957
It's interesting that you gained all that experience kind of, as a consultant with the outside kind of looking in and then were able to also impact it on the inside.
00:04:02.375 --> 00:04:16.125
Tell me a little bit about, I noticed that you got your MBA from Wharton somewhere in the, in this journey, which I think is a really important, path for many of us that are trying to understand business better.
00:04:16.165 --> 00:04:22.250
Tell me about why you made that decision to get your MBA and how it impacted your career trajectory.
00:04:22.250 --> 00:04:22.458
Yeah.
00:04:22.458 --> 00:04:25.540
So I, I've received my MBA fairly recently.
00:04:25.540 --> 00:04:42.375
So later in my career I'd thought about it since, you know, my early 20s, since my first couple of years of working, I realized that we could put forth the most compelling, beautiful, you know, human centered solutions, but the business wouldn't necessarily adopt them.
00:04:42.875 --> 00:04:47.165
And that many of the people making decisions about my work had a business background.
00:04:47.500 --> 00:04:54.250
So I thought, you know, periodically I thought about moving to the product side, or the brand side.
00:04:54.625 --> 00:04:57.625
And getting an MBA was something
Load full transcript
I always wanted to do.
00:04:57.625 --> 00:04:59.415
But the timing was difficult.
00:04:59.415 --> 00:05:04.040
It was either, you know, expensive when we were trying to buy a home or I'd had small children.
00:05:04.665 --> 00:05:12.625
And when I joined Ford Motor Company, they were supportive of me earning my MBA while working full time.
00:05:12.625 --> 00:05:17.290
I had the support of my manager and my manager's manager, so that's what made it all possible.
00:05:17.375 --> 00:05:19.915
And it was an incredible amount of work.
00:05:19.915 --> 00:05:23.000
It really stretched me outside my comfort zone.
00:05:23.000 --> 00:05:27.208
I had to learn math all over again, learned calculus.
00:05:27.208 --> 00:05:28.665
But it was incredible.
00:05:28.665 --> 00:05:31.333
And I'm I'm really thankful that I did it.
00:05:31.333 --> 00:05:31.790
Yeah.
00:05:31.790 --> 00:05:34.790
What kind of doors did it open for you?
00:05:34.833 --> 00:05:53.040
I noticed in your recent article on design Thinking, you talk a lot about being able to speak the language of business and business sensitivity in general, I think is a huge opportunity for folks in our space, you know, career professionals and peers in this user experience or human centered space.
00:05:53.333 --> 00:05:59.040
How how did it change your, ability to operate in a large company like Ford?
00:06:00.583 --> 00:06:04.875
So I, I feel I was always a business oriented designer.
00:06:05.290 --> 00:06:27.540
So I had I think I had a pretty good grasp of speaking business language, but I what I lacked with some of that sort of intrinsic confidence and knowledge, like I, I learned kind of on the job and I really wanted the sort of credentials so that I felt, I think, more confident and just embodying it.
00:06:28.458 --> 00:06:40.750
It also, it also really helped me understand what drives business, taking courses around, like I'd never taken an economics course, so I had to take macroeconomics and microeconomics.
00:06:40.750 --> 00:06:42.000
We had to take accounting.
00:06:42.000 --> 00:06:49.165
And, you know, I, I didn't really know how to read a 10-K document before, but going through business school, that was part of that process.
00:06:49.290 --> 00:06:59.540
A lot of, courses on strategy marketing I was always interested in so really learned about all of these different areas of business in a much deeper way.
00:07:00.040 --> 00:07:08.540
So then when I was, you know, in those large corporate environments, I just understood the language more and really started to see my peers.
00:07:08.540 --> 00:07:11.665
I mean, I've always seen my cross-functional colleagues as people.
00:07:11.665 --> 00:07:13.000
I think that's essential.
00:07:13.000 --> 00:07:25.958
There shouldn't be a creative community and then the business or engineering or product community, being being at business school with people from all different backgrounds, we all did so much collaborative work together.
00:07:26.333 --> 00:07:34.458
It just even reinforced for me more that we're all one team working together to benefit the customer, to benefit the business.
00:07:35.040 --> 00:07:47.290
So I felt a little bit less like I didn't understand or I was outside of the business side, and just felt like, you know, a full member with a seat at the table.
00:07:47.290 --> 00:07:48.458
Yeah, yeah.
00:07:48.458 --> 00:07:49.790
I'd like to circle back to that.
00:07:49.790 --> 00:08:00.833
That idea of sort of business sensitivity and the ability to align, you know, organizations with a better understanding of business when we kind of get into your, your new article.
00:08:00.833 --> 00:08:08.750
But maybe before we do that, I was thinking about all the varied experiences you've had across different kinds of companies.
00:08:08.750 --> 00:08:13.583
I mean, service design companies, retail companies, product companies.
00:08:13.958 --> 00:08:22.250
You've seen UX and human centered design, outside and inside in all these different environments.
00:08:22.790 --> 00:08:36.291
What's unique and different about, you know, the way that human centered design is practiced in those areas, or is it more common than different or more alike than different in those different kind of contexts.
00:08:37.457 --> 00:08:39.791
So I see more similarities than differences.
00:08:39.791 --> 00:08:51.750
I feel that the design process or, you know, human centered design is one approach, it's not the only approach, but that process can be applied to all different types of challenges.
00:08:51.750 --> 00:08:58.666
It's really about, you know, we often start with a hypothesis, or a problem we want to solve.
00:08:58.666 --> 00:09:01.666
Often there's a business oriented problem.
00:09:01.666 --> 00:09:09.916
We try to reframe it as something around what is consumer focused so that we're solving a real human need and not just, hey, the business wants to grow in this way.
00:09:10.625 --> 00:09:23.750
Started to understand people, people's needs, ideating new solutions, prototyping those processes or tools can be applied to consumer physical products.
00:09:23.750 --> 00:09:28.916
They can be applied to operational processes in a service environment.
00:09:29.291 --> 00:09:46.832
They can be applied to designing a website or an app that's more of the output, which you know, most of the design teams I've worked with are multi-disciplinary, so not exclusively digital product or UX, or not exclusively physical product.
00:09:47.166 --> 00:09:53.000
And frequently when we're working on experiences that includes multiple types of design.
00:09:53.000 --> 00:09:59.541
So we might be, for example, some of the work I did at Walmart was looking at omnichannel service experiences.
00:09:59.541 --> 00:10:10.791
So someone might be starting their journey on their phone, browsing a product selection, purchasing a product, booking a service, going into the store and fulfilling that service.
00:10:10.791 --> 00:10:20.707
So that involves both physical design and digital design, similar with Chase and Ford, where there was always an element of a digital component and physical.
00:10:20.707 --> 00:10:27.082
So I see whether you're working on enterprise software or consumer facing apps, the same process would apply.
00:10:27.500 --> 00:10:29.791
Yeah, yeah, yeah, B2B or B2C.
00:10:29.791 --> 00:10:41.957
I think that's one of the things I, I feel most grateful about in my career is we can work in all different types of domains, all different, whether you know, business to business or business to consumer.
00:10:42.291 --> 00:10:44.541
It's really a set of principles.
00:10:44.541 --> 00:10:47.416
When I teach, sometimes I talk about big D design.
00:10:47.416 --> 00:10:50.750
You know, it's like everything is a design problem, you know?
00:10:51.582 --> 00:10:57.625
And you never need, like, really human, real human centered design unless you have a design problem and everything's a design problem.
00:10:57.625 --> 00:11:11.041
So I think too that a certain principles or the way that, human centered designers talk, using experience as a language is a common language that everybody can understand.
00:11:11.041 --> 00:11:13.875
Everybody. We're natural storytellers, right?
00:11:13.875 --> 00:11:26.541
So we can tell stories about today's experience and what people need from tomorrow's experiences and, and align a multidisciplinary team, regardless of the kind of backgrounds or contexts we're, we're working in.
00:11:26.541 --> 00:11:39.457
And I think it's it's one of the, one of the I think, most surprising and, and unique things about, you know, being in this human centered design business.
00:11:39.457 --> 00:11:45.041
So tell me about some of the pivotal, maybe moments in your career.
00:11:45.041 --> 00:11:55.875
I think you mentioned some of the work that you did at JPMorgan Chase, really, really kind of transformed the way you thought about your work and how you interface with leadership teams.
00:11:56.082 --> 00:11:56.291
Yeah.
00:11:56.291 --> 00:12:05.291
So, at you know, in a consultancy like IDO we would have a brief and we would sort of go off on our own and do the work and have presentations and hand-offs.
00:12:05.291 --> 00:12:08.416
Sometimes we would have our clients more involved in their work.
00:12:08.416 --> 00:12:17.707
And I felt like those were really the most impactful, engagements that we had because we were bringing we were all going along the same journey.
00:12:17.707 --> 00:12:27.166
And our partners, you know, on the client side, really internalized and believed in the work and could champion it inside the company.
00:12:27.707 --> 00:12:35.291
When I joined Chase, I joined the digital design team, and I was asked to focus on innovating the branch experience.
00:12:35.707 --> 00:12:52.916
And I realized pretty quickly that, you know, as a sort of senior individual contributor, there was only so much impact I could make working from, you know, San Francisco when all of the decision makers on what happened in a branch were based in New York or Columbus, Ohio.
00:12:54.041 --> 00:13:06.416
So I, I spent the first few months of that job really on a listening tour, getting to know all the leaders in the space, the challenges, the current work, the projects that were in flight.
00:13:06.416 --> 00:13:10.082
The business at that time was undergoing a transformation.
00:13:10.082 --> 00:13:13.916
They were had a big initiative around transforming the branch experience.
00:13:14.957 --> 00:13:27.416
And I could see that there were a lot of ideas that we were pushing forward, but there was a disconnect between some elements of the strategy and the ideas that were being executed.
00:13:27.957 --> 00:13:43.457
So in a in a sort of skunkworks way, I introduced human centered design into the process where I put together some materials and documents and workshops to say, like, hey, if we if we do truly want to innovate the experience, let's think about the physical environment a new way.
00:13:43.500 --> 00:13:46.250
Let's think about the digital tools in a new way.
00:13:46.250 --> 00:13:56.541
Let's think about how we bring the customer's experience with, you know, the online experience with Chase or the app into the branch, because at the time they were quite disconnected.
00:13:56.832 --> 00:14:06.000
I organized ethnographic research in a few cities around the country and we didn't, you know, we tried to do this in a scrappy way.
00:14:07.082 --> 00:14:22.125
And this gave us, not only the quantitative insights that we had from past work with in Chase, but it supplemented it with some, real quotes, real insights and real examples.
00:14:22.125 --> 00:14:29.041
We also did some facilitated sort of co-creation tools, where we got the customer's input into what a solution might be.
00:14:29.416 --> 00:14:29.666
Yeah.
00:14:29.666 --> 00:14:49.375
And so working through that process and workshopping with those executives, ultimately I was offered a new role in the company as head of Branch Innovation, where we took all of the the ideas generated from our human centered design process, and we set out to build what we called a beta branch, where we could test and learn with customers and bankers.
00:14:50.250 --> 00:14:56.250
So you moved from the design practice to the business delivery practice?
00:14:56.250 --> 00:15:08.000
Yes. So I when I started my time at Chase in the digital customer Experience team, as a designer, I moved over to be head of Branch Innovation in what was called the chief administrative office.
00:15:08.000 --> 00:15:16.082
Okay, so that role had been in the past, led by someone with, you know, either a product or market research or technical background.
00:15:16.082 --> 00:15:18.541
They had not had a designer in that role before.
00:15:18.541 --> 00:15:37.500
So tell me then the the branch that you developed, the pilot branch, tell
me about, you know, at the time, I think, there was a lot of, I would say kind of superficial, treatments about way people were handling branch banking.
00:15:37.500 --> 00:15:48.875
It was like, well, you know, we'll put it in a coffee shop and we'll make lattes or, you know, and it was like this way to try to transform banking in this, you know, this kind of place you would hang out.
00:15:49.125 --> 00:15:51.832
But in your case, it was really quite different.
00:15:51.832 --> 00:15:58.375
How did you use the ethnography and the co-creation to stand up a branch that could really move the needle for the community?
00:15:59.500 --> 00:15:59.666
Yeah.
00:15:59.666 --> 00:16:02.457
So a few things that we had done early on.
00:16:02.457 --> 00:16:15.375
I had organized some co-creation sessions with some students from CCA, California College of Art, and we began with having them bring like bring their pain points.
00:16:15.375 --> 00:16:23.791
So I had asked them all to go to a bank, document the experience, come back, debrief on it.
00:16:24.000 --> 00:16:25.832
They shared experiences that they had had.
00:16:25.832 --> 00:16:27.250
Many were international students.
00:16:27.250 --> 00:16:32.500
So like authentication and bringing their identification was a major pain point.
00:16:33.125 --> 00:16:38.707
Just the environments themselves weren't always conducive to a place you would want to spend time.
00:16:38.707 --> 00:16:40.041
They could be intimidating.
00:16:40.041 --> 00:16:42.041
They could be overly formal.
00:16:42.041 --> 00:16:50.832
And then, you know, on the other hand, there were, spaces like the Capital One cafe, which were kind of a gathering place where you could get great coffee.
00:16:50.832 --> 00:16:55.666
And they had some financial wellness classes, but those were not full service branches.
00:16:55.666 --> 00:17:02.916
They had brand ambassadors, and you can get information on opening an account, but you couldn't actually do any transactions in those spaces.
00:17:02.916 --> 00:17:03.541
Yeah.
00:17:03.541 --> 00:17:18.750
And so what we wanted to do in innovating the branch experience was how do we take what we offer in a full service branch and bring it, you know, modernize it with all of the tools and experiences that would really help people on their financial journeys.
00:17:18.750 --> 00:17:43.583
Because I know many of us growing up in the US, we weren't really educated on financial wellness when we were young, so we've had to sort of learn it on our own and through our research, we learned that people are often asking a friend or family member for advice or going to like a mom and pop financial advisor and major institutions really are only serving people with a higher net worth.
00:17:43.583 --> 00:17:48.583
You need a certain amount to invest to get the attention and time from a financial advisor.
00:17:49.083 --> 00:17:57.958
So there is a whole underserved community of people who were just starting out or lower net worth that weren't didn't have a place to go for financial advice. Yet.
00:17:58.250 --> 00:18:03.750
Chase had 5000 branches and wanted those branches to be advice centers.
00:18:03.750 --> 00:18:14.165
So there was a real opportunity I saw to connect those and do it in a way where we could offer those banking services and create that welcoming third place.
00:18:14.290 --> 00:18:20.750
Yeah, so many of the ideas that we had coming out of our work together, we could test out in this beta branch.
00:18:20.750 --> 00:18:32.708
So one of the things that was impactful for me, moving from the design team to the business team, was I was reporting to a decision maker who could decide, like, we're going to open this beta branch.
00:18:32.708 --> 00:18:34.583
Here's what we're going to build it.
00:18:34.583 --> 00:18:45.708
So since I moved over to the business team, I had much more agency and ability to make those ideas real, including working with the real estate team to scout out a location.
00:18:46.040 --> 00:18:48.625
We decided to build this beta branch in New York.
00:18:48.625 --> 00:18:51.375
There were a number of sites that we could have chosen.
00:18:51.375 --> 00:18:55.583
We looked in some places like Lower Manhattan, close to NYU.
00:18:55.833 --> 00:18:59.665
You could make a case, but that would have been a great location to test new technologies.
00:19:00.083 --> 00:19:08.040
Ultimately, we decided to build this beta branch in Harlem so that we could really meet underserved communities.
00:19:08.040 --> 00:19:13.415
At the time, Chase had an initiative called Advancing Black Pathways.
00:19:13.415 --> 00:19:23.790
There was a lot of interest within within the bank, with our CEO, with my leader, to really address those underserved needs.
00:19:24.208 --> 00:19:30.415
So we felt that building this test branch in Harlem would give us an opportunity to really connect and do that.
00:19:31.083 --> 00:19:37.083
So in addition to finding a space and revamping it, we worked with Google.
00:19:37.083 --> 00:19:40.375
We had courses at Google provided we had small business pop ups.
00:19:40.375 --> 00:19:46.083
So we had a new role called a community manager, and we tested all of those things in a real space.
00:19:46.375 --> 00:19:49.040
And to me, that is like true prototyping.
00:19:49.040 --> 00:19:51.165
It wasn't purely a simulation.
00:19:51.165 --> 00:19:54.958
It was real new services interacting with real customers.
00:19:55.083 --> 00:20:14.250
Yeah, I love the blending of, design practice, like in-situ prototyping with real listening to what the bank, cares about, not only from a business standpoint and the need to reach the underbanked, for example, but but to provide really communal value.
00:20:14.540 --> 00:20:29.458
And then also, I think one of the things I thought was really powerful in our work with, Chase in the past was this idea, of more consultative types of relationships.
00:20:29.458 --> 00:20:33.125
You
know, money's a highly emotional thing for people, right?
00:20:33.500 --> 00:20:38.665
And it's, a scary and intimidating space, and people don't want to make mistakes.
00:20:38.665 --> 00:20:49.040
So the idea of sort of a more professional, consultative relationship with, with bankers, I think, puts humans in the right spot to help customers.
00:20:49.208 --> 00:20:57.708
I think the other the other pressure that of course, branch banks have faced forever is how do we do it with fewer people and more technology.
00:20:57.708 --> 00:21:14.458
So how did you sort of blend the the, you know, need for the business to have less expense related to branch banking but still be able to add, sort of the the key touch points for, for humans in the, in the community when you were doing this pilot program.
00:21:15.665 --> 00:21:20.875
So the branch that we renovated and had it had not been touched in decades.
00:21:20.875 --> 00:21:27.875
So it was quite antiquated and had many, many teller stations that were under utilized. Yeah.
00:21:27.875 --> 00:21:32.625
So we didn't replace human labor with a lot of ATMs.
00:21:32.625 --> 00:21:36.250
We did have some of our newer, more modern ATMs in the space.
00:21:36.583 --> 00:21:44.790
We rightsize the number of teller stations, but we also added different types of, you know, interaction zones.
00:21:44.790 --> 00:21:47.208
We had booths, we had comfortable couches.
00:21:47.208 --> 00:21:55.833
We actually had to we converted what was the safe deposit box room into a community room that anyone in the community could use for a meeting.
00:21:56.250 --> 00:21:59.790
You know, our bankers were more casually dressed.
00:21:59.790 --> 00:22:06.165
We had, new services and new types of checking accounts that were being offered.
00:22:06.375 --> 00:22:10.290
And this community manager role was also essential.
00:22:10.290 --> 00:22:16.290
So part of opening up this beta branch site was making a case for this new role.
00:22:16.708 --> 00:22:47.458
And to me, one of the the great successes of this, you know, Chase published a paper last year on the five year anniversary of opening our beta branch around, you know, the increase in number of checking accounts, in the community branches relative to traditional branches, the increase in savings account balances in these community branches, and then, The number of courses or financial health classes that have been hosted on these sites.
00:22:48.000 --> 00:22:48.915
That's great.
00:22:48.915 --> 00:22:51.540
That's amazing.
00:22:48.915 --> 00:22:51.540
Carly. Congratulations on that.
00:22:51.540 --> 00:22:54.165
I think, you know, it's it's a great case study.
00:22:54.165 --> 00:23:24.583
I hope that it gets, you know, written up and shared more broadly because I think it's a great example of how you can bring design thinking, types of approach, business sensitivity, looking at the customer journey and putting the right touchpoint in at the right place, you know, whether that's the technology implementation or human type of touchpoint can really kind of maximize, the opportunity for both the community and for the and for the business, right.
00:23:24.583 --> 00:23:26.665
For, for the bank in this case.
00:23:26.665 --> 00:23:38.375
If I think about the the success of our test site and our beta branch, what we were really building there was our first, community center branch.
00:23:38.375 --> 00:23:54.040
So while initially we thought about it as the Harlem Innovation Branch, where we would test and learn on all of our new products and services, we quickly landed on this idea of this is a the first community center branch, which has since been scaled across the country.
00:23:54.040 --> 00:23:57.375
So now there are 19 of these community centers.
00:23:57.375 --> 00:24:03.583
And that role to, to me, like establishing a new role in the branch environment, which was a huge win. Yeah.
00:24:03.583 --> 00:24:12.208
So not only do we have community managers at all of those branches across the country, we have community managers and traditional bank branches too.
00:24:12.208 --> 00:24:16.790
And the goal by 2030 is to have 75 hired across the US.
00:24:17.165 --> 00:24:19.000
Nice. That's that's amazing.
00:24:19.000 --> 00:24:22.415
And this, branch concept has won some awards as well.
00:24:22.415 --> 00:24:22.958
Right.
00:24:22.958 --> 00:24:25.958
And recognized nationally or internationally.
00:24:25.958 --> 00:24:31.125
Yes. In 2021 we want to fast Company Innovation by Design award Fantastic that's great.
00:24:31.125 --> 00:24:33.250
I mean all of us think about that.
00:24:33.250 --> 00:24:37.958
You know, the ability to, say that you, you know, contributed to that is amazing.
00:24:37.958 --> 00:24:45.958
I love the idea, you know, everything that you've been talking about, this is, I think, what most would consider design thinking.
00:24:45.958 --> 00:24:48.665
And you and I know design thinking isn't a new concept.
00:24:48.665 --> 00:25:05.625
It's the idea of, of of blending sort of creative practices and behavioral, understanding of people and design and business processes and strategy into really create something of value to identify what that value is and bring it to life and new products and services.
00:25:06.000 --> 00:25:20.083
So it's not a new idea, but design thinking, brought those concepts to a much wider audience beyond sort of, you know, typical, folks who are using those in professional practice.
00:25:20.083 --> 00:25:22.583
Right? So that was a good thing, right?
00:25:22.583 --> 00:25:35.458
That, now, more people knew about design thinking, but but what's what's kind of happened, since the advent of design thinking and the popularization of it in your mind, what have you seen happen?
00:25:38.665 --> 00:25:48.250
You know, I think when we were doing it in the agency setting, often clients would bring, you know, us as an expert team to facilitate and lead through this process.
00:25:48.458 --> 00:25:58.415
And I think in many instances, teams could be quite dogmatic that we had to follow a specific process or specific people had to do it in a certain way.
00:25:59.415 --> 00:26:16.208
Somewhere along the journey, it became very democratized so that it almost became too much of a like an easy paint by numbers where people felt like, oh, if I go talk to somebody, then I'm doing human centered design, and there is a lot of work that we would do as designers.
00:26:16.208 --> 00:26:22.833
You know, it wasn't just around talking to a person, having an insight and then making that into an idea.
00:26:22.833 --> 00:26:24.625
We would do a lot of rigorous.
00:26:24.625 --> 00:26:36.708
So synthesis and develop insights and translate those insights into opportunity spaces and do broad ideation and prototyping before narrowing in on the best solution.
00:26:36.708 --> 00:26:44.500
So I feel that the process was quite simplified. And, you know, in that article I wrote, I use the term design thinking.
00:26:44.500 --> 00:26:46.665
I mean, somewhat reluctantly.
00:26:46.665 --> 00:26:48.708
I'd never been a super fan of that term.
00:26:48.708 --> 00:26:53.208
To me, it's human centered design, design thinking kind of.
00:26:53.415 --> 00:26:55.500
It feels a little bit pithy.
00:26:55.500 --> 00:26:57.458
And it feels like.
00:26:57.458 --> 00:27:06.375
I don't want to say that, it's wrong to think that anyone can do human centered design or design thinking.
00:27:06.375 --> 00:27:13.958
It just is a very, very diluted version of the robust and rigorous process we would do as designers.
00:27:13.958 --> 00:27:21.665
So the reason I'm not giving up on it is I still think there's true value in the rigorous, true work that we would do.
00:27:22.083 --> 00:27:42.040
And what I see since especially going from different within different organizations, I mean, I think my experience at Chase, when I was sort of, you know, in the business team as a designer, we did human centered design, but we we kind of did it in our scrappy way because we, we really wanted to see through some business impact.
00:27:42.583 --> 00:27:55.208
You know, at Ford, I led a human centered design team called D-Ford in Palo Alto, which was really borne more out of the consultancy model, where, we did more independent projects.
00:27:58.208 --> 00:28:10.875
The issue that we would have there is that sometimes we were too isolated and there wasn't necessarily a clear line between our, our concepts and our prototypes to production.
00:28:11.290 --> 00:28:19.125
Sometimes these internal design teams are given like quite pie in the sky briefs, things that might not ever see the light of day.
00:28:19.125 --> 00:28:23.500
And then there were more questions around what value is this team providing?
00:28:24.040 --> 00:28:34.500
I feel that, you know, there was a pretty successful version of this with Walmart, where the design team was responsible for both the North Star
Vision and the delivery.
00:28:34.500 --> 00:28:42.290
I think that's a good balance of designers being able to foresee, you know, or not foresee.
00:28:42.333 --> 00:28:51.500
Designers are able to put pen to paper and really articulate what a future great customer experience can be and have the responsibility to deliver that.
00:28:52.040 --> 00:29:07.875
Where I've seen design thinking fall short is almost when there's a team doing ideation and then a separate team doing delivering, and there's often like a valley or gap in between those where things can either fall apart or end up not actually getting through to production.
00:29:07.958 --> 00:29:10.000
Yeah.
00:29:07.958 --> 00:29:10.000
So I guess I'm hearing a couple things.
00:29:10.000 --> 00:29:14.708
One is the the democratization of the idea wasn't a bad thing.
00:29:14.708 --> 00:29:22.665
I remember, you know, we used to have to go up on the mountain and shout, hey, this is really, you know, this experience centers stuff is important.
00:29:22.665 --> 00:29:25.415
You know, we should do it and it'll deliver great results.
00:29:25.415 --> 00:29:28.415
And we could demonstrate how it would deliver results.
00:29:28.458 --> 00:29:32.958
Well, then that idea caught on and somehow got watered down in the process.
00:29:33.333 --> 00:29:45.665
And in the meanwhile, we found ourselves in positions where maybe we were doing really far out upfront stuff that was kind of disconnected from the business pipeline and business delivery.
00:29:46.290 --> 00:29:54.915
So we sort of, found ourselves doing work that wasn't directly impacting the business and kind of put us in maybe, a bit of a rear seat.
00:29:54.915 --> 00:29:59.083
I'm generalizing, of course, but but, but the idea is that there were a couple of things.
00:29:59.083 --> 00:30:10.708
I think that kind of put us in a position where we weren't being as impactful, and we were letting some of the core kinds of work, the idea, identifying and delivering value.
00:30:10.833 --> 00:30:19.583
We were kind of leaving it maybe to other parts of the business, and we kind of lost a seat at the table, I think is some of what I've seen happen in an industry.
00:30:19.583 --> 00:30:29.125
Now, that pendulum, I think, is swinging back because they're realizing you need insights and you need people who are skilled at this to do the work as part of the team.
00:30:29.165 --> 00:30:33.915
It doesn't mean that any, you know, you know, you or I don't own customer experience.
00:30:33.915 --> 00:30:41.375
Everybody owns customer experience, everybody owns human centricity and whatever role ours is to play in that process.
00:30:41.625 --> 00:30:48.165
But it it does require some expertise to do it well, to translate insights, to build strategy.
00:30:48.165 --> 00:30:50.790
But there are ways that we can be way more effective.
00:30:50.790 --> 00:31:10.083
One of the things I think I liked in your article is you, you talked about sort of three key focal
areas, users, which of course is something that we would be focused on, and technologies how we apply technologies, but also business sort of back to where we started the conversation about business sensitivity.
00:31:10.208 --> 00:31:18.290
I think your example of the branch banking to me is a great example of, a clear business sensitivity.
00:31:18.625 --> 00:31:21.665
A clear, human centered design process.
00:31:21.665 --> 00:31:40.000
It's really design thinking, which, you know, we've talked about is not a new idea, but in, in the democratization of design thinking, you know, the fact that that we don't have to now sort of preach the importance of human centered design, but that organizations know about it.
00:31:40.958 --> 00:31:42.790
Has it been diluted in some way?
00:31:42.790 --> 00:31:45.750
I mean, what have designers missed along the way?
00:31:45.750 --> 00:31:54.583
As more and more people have become to know about design thinking, but somehow we've gotten less effective as practitioners, maybe.
00:31:54.583 --> 00:31:56.708
How how is that happened, do you think?
00:31:56.708 --> 00:32:01.750
Yes. So back in, you know, my earlier days, an IDO.
00:32:01.750 --> 00:32:04.625
That's when we started talking about design thinking.
00:32:04.625 --> 00:32:12.333
And I think the term is a it's like an elevated or diluted version of what we actually did in practice.
00:32:12.958 --> 00:32:25.625
So design designers going through that process of research of, you know, defining insights and opportunities, developing the strategy to lead to the best, you know, concepts.
00:32:26.458 --> 00:32:30.708
It would take time, and it does take some level of expertise and creativity.
00:32:31.290 --> 00:32:39.125
And one of the most important parts of it is going from insight to concept and tying those really closely together.
00:32:39.540 --> 00:32:53.208
I think as design thinking proliferated and became a little bit pithier and more lightweight, taught in a day in a workshop, it almost felt like something that would be kind of like just a checklist that someone could go through.
00:32:53.500 --> 00:32:54.875
Oh, I talked to a person.
00:32:54.875 --> 00:32:56.000
I had an idea.
00:32:56.000 --> 00:33:03.875
I made a concept that's such a like a, a watered down version of the rigorous work we would do.
00:33:04.208 --> 00:33:06.790
I feel like that's one of the one of the pieces.
00:33:06.790 --> 00:33:13.750
Also, the just the naming of design thinking to me never really felt quite right because it's only part of the process.
00:33:13.958 --> 00:33:14.165
Right?
00:33:14.165 --> 00:33:18.540
I mean, as designers, you need to do the thinking part and the doing part.
00:33:18.875 --> 00:33:23.290
In four years of thinking, even going a few years back, I'd see debates on LinkedIn.
00:33:23.833 --> 00:33:29.165
It's not about design thinking, it's about design doing, and it's not an either or.
00:33:29.165 --> 00:33:30.415
It's really a both.
00:33:30.415 --> 00:33:38.915
You need to put the thought into it and you need to build like without the prototyping, without making it real.
00:33:39.458 --> 00:33:40.708
It's just ideas.
00:33:40.708 --> 00:33:52.250
And that's that's where I've seen some of the shortcomings in these embedded teams and companies, where they become more like idea factories or teams.
00:33:52.250 --> 00:33:57.875
They come up with a bunch of concepts, and there's such a disconnect between having that idea and making it real.
00:33:57.875 --> 00:34:00.875
Like ideas are actually relatively cheap.
00:34:00.958 --> 00:34:03.458
Making things real is the hard part.
00:34:03.458 --> 00:34:03.790
Yeah.
00:34:03.790 --> 00:34:06.790
I mean, even if I think about my startup, I had an idea.
00:34:06.790 --> 00:34:09.375
I percolated on it for about six months.
00:34:09.375 --> 00:34:15.875
I spent a year on it full time, and there were still many years to go to bring that idea to market and make it real.
00:34:16.000 --> 00:34:17.833
It's really where the rubber hits the road.
00:34:17.833 --> 00:34:30.958
So as I was putting together that that article I wrote on LinkedIn, you know, I thought about, you know what, What are the areas where I'm seeing us fall short internally in some of these large companies because we need to move quickly.
00:34:31.333 --> 00:34:47.166
You know, we don't have the luxury of time that we had back in my consulting days, or we'd have, you know, dedicated teams for ten, 12, 16 weeks on a single problem, sort of working in a bubble, like working in a close knit environment.
00:34:47.208 --> 00:34:49.708
We were totally focused on that challenge.
00:34:49.708 --> 00:34:55.500
You know, the teams I've been working on in-house, we don't have everyone working on one project at a time, right?
00:34:55.750 --> 00:35:02.916
Everyone struggling multiple things, and we don't necessarily have as much time to do research, but that doesn't mean we shouldn't do it.
00:35:02.916 --> 00:35:13.541
Like, for example, with Casper, we were quite scrappy and getting our insights, learning quickly and combining qual and quant and then making things real in a relatively quick way as well.
00:35:13.916 --> 00:35:18.458
Yeah, yeah, well, I love that idea, that, ideas aren't the problem.
00:35:18.458 --> 00:35:20.458
I agree with that. Ideas are kind of.
00:35:20.458 --> 00:35:27.041
Every organization has hundreds or thousands of ideas that they could move with, you know, forward with.
00:35:27.041 --> 00:35:33.208
But the question is which ideas really meet needs of the customers which add value?
00:35:33.208 --> 00:36:05.041
And as you say, you know, we all own responsibility for delivering a great experience, but there's real, you know, skill in identifying the right insights and then activating those in strategy and design and then working to align a large organization around that, I think I do think, the, the sort of design thinking idea and companies were doing
training, right, where everybody could get design thinking in a day.
00:36:05.291 --> 00:36:11.375
And in one on one hand, it provided the principles to a wider audience, which was a good thing.
00:36:11.375 --> 00:36:20.583
What it misled people in is that they were able to do it, with, you know, with one day of training without any support or help.
00:36:20.583 --> 00:36:32.333
So I think it's good that that, you know, everyone understands the principles around human centered design or why they should be doing it, but hopefully it arms designers to be more effective in the work that they do.
00:36:32.583 --> 00:36:42.083
The other the other thing that was happening, I think, at the same time is if you remember, maybe 5 or 7 years ago, every large organization was standing up an innovation center.
00:36:42.750 --> 00:36:55.125
And the innovation center was going to go think about big ideas, and, explore potential directions that it was very far out looking and it was very design thinking, but it wasn't a lot of design doing.
00:36:55.416 --> 00:37:06.791
And I think business leaders, tired of that because they couldn't connect the ideas and the millions and millions of dollars that were being spent, you know, to explore this stuff.
00:37:06.791 --> 00:37:16.083
They couldn't connect it to the products and services that they had to get to market to stay alive and add shareholder value and all the things that are important for businesses to do.
00:37:16.458 --> 00:37:19.375
So they consequently all kind of went away.
00:37:19.375 --> 00:37:23.375
There aren't many of those innovation centers around anymore.
00:37:23.375 --> 00:37:31.291
So I really like your idea too of you have to be design doing as well as design thinking or you will not be.
00:37:31.291 --> 00:37:35.250
We, we won't be seen as relevant in an organizations you know.
00:37:35.250 --> 00:37:36.791
Yeah. To add to that.
00:37:36.791 --> 00:37:39.708
So I've led two of those kind of innovation teams.
00:37:39.708 --> 00:37:42.708
One was at Chase and one was at Ford.
00:37:42.833 --> 00:37:48.333
And in both instances I had embedded software engineers on the team.
00:37:48.833 --> 00:37:54.666
In some case a Chase, they reported into engineering, at Ford, they were part of my direct team.
00:37:54.666 --> 00:37:59.708
And with those software engineers, we could help convert and make things real relatively quickly.
00:37:59.708 --> 00:38:07.750
Like one example, there was a pain point in some of the new branches that Chase was opening of wait time, where there was no way to manage the queue.
00:38:08.250 --> 00:38:12.708
And we had it was to me like a relatively low hanging fruit idea.
00:38:12.708 --> 00:38:19.958
We should digitize this queue so people are in the line and not have it just like, we literally had a piece of paper on a clipboard.
00:38:20.291 --> 00:38:31.708
So with our design technologists or our software engineers on our team, we built a standalone app where we could check people in, and we put this in a few of the branches where that pain point was particularly high.
00:38:32.041 --> 00:38:39.625
And we had an improvement in NPS or what we called at chase, our OSat score, overall satisfaction.
00:38:39.625 --> 00:38:42.125
And when it went up by 10% relatively quickly.
00:38:42.125 --> 00:38:48.833
So that that proved to us that this was a product or feature that we needed to incorporate into the roadmap quickly.
00:38:49.125 --> 00:38:49.541
Right.
00:38:49.541 --> 00:39:05.083
Similarly, at Ford, we had ideas around in-vehicle experiences, and our software engineers made those like prototype in a tangible way so that we actually tested some services, we tested experiences in drivable vehicles.
00:39:05.500 --> 00:39:23.125
That to me really helped bridge the divide between just the idea, like in a deck or in a video or some illustrative format and something that people could actually interact with to me, like design thinking in isolation is really only a portion of it.
00:39:23.333 --> 00:39:31.541
It's really the making it real, being in in situ with customers and experiencing it with them, or having them do it on their own.
00:39:31.541 --> 00:39:34.791
And that's when we really that's the that's the really the design part.
00:39:35.166 --> 00:39:36.166
Yeah. Yeah.
00:39:36.166 --> 00:39:44.666
I think organizations I found throughout my whole career, organizations are very impatient for the thing they want to see the thing, quickly.
00:39:45.291 --> 00:39:58.541
And so the more that we can paint the picture of the future or show them how the, insights will be embodied in New products and services, then the organization can rally around that.
00:39:59.041 --> 00:39:59.958
Remember the Doblin group?
00:40:00.958 --> 00:40:03.916
Used to talk about business concept illustration, which I love.
00:40:03.916 --> 00:40:08.750
That idea was a way to align a large organization around what a future could be like.
00:40:08.833 --> 00:40:25.458
And, and I think the more we can show the organization what problem needs to be solved and what success looks like in the future, then everybody can march towards that with their respective responsibilities, whether it be manufacturing or design or marketing or whatever it is.
00:40:26.375 --> 00:40:32.000
But I think organizations are businesses are impatient, to see the results.
00:40:32.000 --> 00:40:35.750
You know, they don't want to they don't want to spend two years doing research.
00:40:35.750 --> 00:40:38.750
They want they know they need to be making things, you know.
00:40:39.125 --> 00:40:40.458
So I think that's something.
00:40:40.458 --> 00:40:56.416
So you mentioned in your article, I like that you had sort of three, foundational pillars, you know, including users, which we've talked about technology, the technology sensitivity and business sensitivity to in order to be effective practitioners.
00:40:56.416 --> 00:41:06.625
So you mentioned sort of the
first the business go go beyond business or design thinking to design, doing right, making, making sure we're always doing we're always delivering a value.
00:41:06.916 --> 00:41:23.875
And and in your JPMorgan Chase, banking branch example being very sensitive to the goals of the business, being able to speak the language of the business so that all of the ways that we activate insights and ideas resonate with business leadership.
00:41:24.125 --> 00:41:27.916
I think that's one of the ways we can get out of this sort of order taking role.
00:41:27.916 --> 00:41:45.958
Many, many of the designers that I talk to in design organizations, big companies, big design organizations, they're relegated to like, order taking, you know, they're going to be told what the next feature is and not even where that, what matters about that feature, but they have to just execute it.
00:41:47.208 --> 00:41:52.791
So you say, say more if you can about what makes us more effective from a business standpoint.
00:41:52.791 --> 00:41:55.791
And then I want to talk about technology and the user standpoint as well.
00:41:56.125 --> 00:41:56.750
Sure, sure.
00:41:56.750 --> 00:41:59.041
So yes. In that article I pointed out three things.
00:41:59.041 --> 00:42:07.458
One was designer speaking the language of the business, having a point of view and expressing it the second most like walking the walk of being really user centered.
00:42:07.666 --> 00:42:17.666
And the third was thinking about the whole customer journey and experience and not just slicing it into a small, feature driven, approach to product development.
00:42:18.000 --> 00:42:19.625
For the first one.
00:42:19.625 --> 00:42:25.375
I think this is part of what I really gained in business school was when we're working cross-functionally, we're all as one team.
00:42:25.791 --> 00:42:32.916
So I think sometimes designers don't necessarily understand everything that's factoring into decisions.
00:42:33.166 --> 00:42:42.166
Maybe not as tuned into data and looking at, you know, big data sets or even, you know, understanding some of the diagrams or the language that's used.
00:42:42.166 --> 00:42:56.958
I think the more that we as designers can ask questions like integrate ourselves into the team, not seeing ourselves as just like having our role like having a specific role that's just around the creative side.
00:42:56.958 --> 00:43:01.041
Like designers really need to actually understand the full context and be a part of it.
00:43:01.041 --> 00:43:11.000
And if they don't understand like ask questions and be comfortable doing that, you know, around understanding users, you know, you mentioned time for research.
00:43:11.000 --> 00:43:17.000
I mean, in house, I've been in projects where we don't have even a month for research.
00:43:17.000 --> 00:43:25.333
And I would I would just, you know, try to encourage all of my teams to, you know, we can put forth concepts.
00:43:25.333 --> 00:43:27.833
We do have some tacit knowledge of the customer.
00:43:27.833 --> 00:43:29.958
We do have a starting point.
00:43:29.958 --> 00:43:34.666
So we can certainly begin with ideas, but we should really test our hypotheses.
00:43:35.041 --> 00:43:41.666
And I've seen all too often where we just get really, really far down a path because we think we already know what the user needs.
00:43:41.958 --> 00:43:43.916
And it's always good.
00:43:43.916 --> 00:43:53.083
Sometimes, you know, we we, we, we do a lot of testing on our feature level, like, oh, this one moment in our UX journey, we see a drop off.
00:43:53.083 --> 00:43:56.041
So let's like redesign this moment or this page.
00:43:56.041 --> 00:44:05.208
But if you're just looking at that out of the full context or sort of missing, what is the reason why we're getting drop off there, and is there another way we can approach it?
00:44:05.875 --> 00:44:19.958
I think more than just being an order taker, designers can develop multiple approaches are present, multiple options, and not just kind of do as they're asked, but think beyond like, well, what's the reason why we're experiencing this?
00:44:19.958 --> 00:44:22.083
How do we address that?
00:44:22.083 --> 00:44:26.666
What are other creative solutions to instead of just sort of doing what we're asked?
00:44:26.708 --> 00:44:39.333
Yeah, I think, you know, we always try to ladder up to the emotional and functional benefits, and then ladder down from a feature into sort of the way you might bring it to life from a experience standpoint.
00:44:39.625 --> 00:44:46.375
But if we don't aren't speaking the language of value, I think that's one of the mistakes.
00:44:46.375 --> 00:44:54.375
I think we made with design thinking is this idea that it starts with empathy, like empathy is not really the right word from a business standpoint.
00:44:54.375 --> 00:44:56.416
I think it's about value. It's like what?
00:44:56.416 --> 00:45:00.833
Where is what's the value proposition from a customer standpoint?
00:45:00.833 --> 00:45:05.416
What are the emotional and functional benefits that they seek from experiences?
00:45:05.750 --> 00:45:11.875
And then how do those translate to the ways we might deliver those with new kinds of features, for example?
00:45:11.875 --> 00:45:19.041
And then how might we bring those to life in a multisensory way with how those experiences look, feel, speak and act?
00:45:19.041 --> 00:45:22.958
I think you need to have all of that to have it really make sense.
00:45:22.958 --> 00:45:33.250
So whenever I am in a meeting and somebody is talking about a feature, I immediately try to get the conversation to the the, emotional and functional benefit level, right?
00:45:33.250 --> 00:45:40.583
So we can make sure we're aligned on that, because there might be all different ways we can deliver that through different kinds of features.
00:45:40.583 --> 00:45:41.166
So you're right.
00:45:41.166 --> 00:45:45.625
But the I mean, there's time for all these
things within the development process.
00:45:45.625 --> 00:45:50.125
For me, it starts with the questions, what do we need to learn to take the next step?
00:45:50.125 --> 00:45:57.666
And then we use our our ability to be curious and to and to get structured information in a way that's valid.
00:45:57.916 --> 00:46:04.416
We use that as a way then to focus our creativity, to focus our, against business results.
00:46:04.416 --> 00:46:12.666
I think the other thing we miss is the opportunity to connect our work in a measurable way to business KPIs and to business outcomes.
00:46:12.916 --> 00:46:22.791
You mentioned, you know, OSat or CSat or Net Promoter Score, which I think is something that almost all organizations I know are using.
00:46:23.333 --> 00:46:32.375
And the challenge I have with that is that if you're a 40 on Net Promoter Score and you want to be an 80, you have no information about how to get there.
00:46:32.375 --> 00:46:44.833
But I think as as human centered designers, we know the value drivers and we know the levers and dials we can move in order to to move the needle for a higher net promoter score.
00:46:45.083 --> 00:46:58.458
So I think measurability, we've been doing a lot of work in this area of experience metrics, which I think is really critical to the success, or the continued leadership of, of, human centered design in business processes.
00:46:58.458 --> 00:47:05.583
We have to be able to show measurable results or we'll lose or see that the table, you know, again.
00:47:05.875 --> 00:47:06.833
Yes. Agreed.
00:47:06.833 --> 00:47:14.416
I've been in organizations where there's a lot of emphasis on NPS, and it's it's more of a lagging indicator than a leading indicator.
00:47:14.416 --> 00:47:21.291
And very true that we don't know what caused that. And sometimes there's things that are actually out of our control.
00:47:21.291 --> 00:47:29.125
Like for example, with Casper, we had a lot of focus on NPS, but someone might give us a low score because the box arrived damaged from UPS.
00:47:29.500 --> 00:47:33.250
And it wasn't really something that we I mean, we worked on improving our boxes.
00:47:33.250 --> 00:47:45.666
In that case, I think it's important for designers to understand why this metric is important to the business, not to sort of discount it, but really, really understand why.
00:47:45.666 --> 00:47:48.250
And, you know, embrace that and add to it.
00:47:48.250 --> 00:47:50.500
So it's more of a yes. And yeah.
00:47:50.500 --> 00:47:56.000
I think understanding what metrics are important to the business is essential.
00:47:56.000 --> 00:47:59.583
And then thinking about creative ways we can help address that.
00:48:00.291 --> 00:48:05.000
So in an organization it might there might be a focus on NPS.
00:48:05.000 --> 00:48:09.708
Are there other things that we can bring in and demonstrate that those are also important?
00:48:09.708 --> 00:48:10.875
Like, yeah.
00:48:10.875 --> 00:48:16.541
You know, in
digital product development, we think about can like conversion and click through rate and overall sales.
00:48:16.791 --> 00:48:22.583
So is someone I think I've seen too often that we're doing usability testing.
00:48:22.583 --> 00:48:26.875
You know can somebody complete a task to get them to do what we want them to do?
00:48:27.083 --> 00:48:35.875
It's really important to understand, like what the customer is trying to get out of it. And are we enabling them to get what they want or what they need out of it? Not?
00:48:35.875 --> 00:48:39.583
Are they simply making the purchase or clicking through the whole flow?
00:48:40.166 --> 00:48:51.666
Yeah, there was a, a company we were working with that did, sort of ambient climate control, like thermostats for in-home residential experiences.
00:48:51.666 --> 00:48:57.958
And, and one of the things that they mentioned in the brief was that they had a very high return, not defective rate.
00:48:58.166 --> 00:49:04.083
So, in other words, products were bought from Lowe's and they were returned like eight out of ten times.
00:49:04.083 --> 00:49:05.875
These products would come back not defective.
00:49:05.875 --> 00:49:07.583
I've just returned.
00:49:07.583 --> 00:49:11.458
And when we did the research, we found that people didn't know how to program.
00:49:11.458 --> 00:49:15.916
The thermostat couldn't do simple things like hang it on their wall square, right?
00:49:15.916 --> 00:49:47.250
These were like basic things that the product needed to provide in order to be effective and to be adopted and used and through, just some simple observation and co-creation research, we were able to help them design not only simple things like add a level to the mounting bracket so you could mount at square or easy ways to quick program, but some new advanced energy features that resulted in, a way lower return, not defective rate, which was huge for them because that was all cost.
00:49:47.250 --> 00:49:56.041
But then they were able to get, store exclusives in a really crowded, commoditized kind of market, for replacement thermostats.
00:49:56.208 --> 00:50:11.500
So it's an it's exactly what you're saying, which is if we can connect our work to business KPIs, where the pain is from a business standpoint, you know, KPIs, key performance indicators, then then we know that we're moving the needle for the business.
00:50:11.666 --> 00:50:18.208
I think sometimes, this is what I'm calling experience value management, which we're not going to get into too much today.
00:50:18.208 --> 00:50:45.791
But the idea here is that not every designers can't fall on their sword for every idea, you know, like, you know, they we have to decide where it's important for us to really, you know, insist on, design innovation from a human standpoint and where tradeoffs can be made because businesses there always be trade offs and there may be lower cost ways to implement ideas in equally effective ways.
00:50:46.250 --> 00:50:51.916
So I think back to your point about business sensitivity and speaking the language of the business.
00:50:51.916 --> 00:50:53.583
That's part of the business, right?
00:50:53.583 --> 00:50:55.083
Where's the cost?
00:50:55.083 --> 00:50:58.791
Where's the cost to deliver this product or service, and how do we lower it?
00:50:59.291 --> 00:51:02.125
You know, businesses are profitable in one of two ways, right?
00:51:02.125 --> 00:51:06.958
They either can charge more or they can take costs off the off the bottom line.
00:51:06.958 --> 00:51:17.875
So how do we, as designers help businesses do that in ways that still deliver on the promise of the value for and the brands for consumers or communities in your case.
00:51:17.875 --> 00:51:20.500
So, JP Morgan Chase, yeah.
00:51:20.500 --> 00:51:27.500
The other thing that, resonates just around this whole topic is the, you know, focusing energy on the most important things.
00:51:27.708 --> 00:51:37.583
Yeah, that I've seen in innovation teams, sometimes we have many ideas that can be pursued and we try to make everyone happy.
00:51:37.583 --> 00:51:40.583
Like throw spaghetti at the wall, like one of these will hit, right.
00:51:41.750 --> 00:51:48.708
There was a leader I worked for who talked about having the to do list and the not to do list, and I thought that was quite inspiring.
00:51:48.708 --> 00:51:53.625
You know, we should really focus our talent and energies on the things that could make the biggest impact.
00:51:54.083 --> 00:51:54.291
Yeah.
00:51:54.291 --> 00:52:08.625
There was a moment where we reorganized our team and in one of my roles to focus on key business areas and just allow those teams to go really deep and focus on the specific business problems in those areas.
00:52:08.916 --> 00:52:17.208
And they also built deeper relationships with those partners and delivered more like meatier, more meaningful, more tangible results.
00:52:17.625 --> 00:52:18.833
I think that also helped.
00:52:18.833 --> 00:52:38.625
Like not just on a project basis, aligning to the business needs, but really orienting the team around them so that they have those deep relationships, they have those longer term engagements, and they're building more like a thoughtful and meaningful solutions as opposed to thinking about it as sort of on a project basis.
00:52:38.625 --> 00:52:40.458
Yeah, yeah, I love that.
00:52:40.458 --> 00:52:44.958
You know, aspirations, customer aspirations don't change right?
00:52:44.958 --> 00:52:45.708
On a dime.
00:52:45.708 --> 00:53:02.958
So the more we can build a foundational understanding of the customers that we serve and, and the things that they value, the more we can build a portfolio, right of services, a long lived ability to deliver, which I think is another thing that many organizations are struggling with.
00:53:02.958 --> 00:53:12.750
Where designers can help is how do we create a practice or an ethos or, a habit of of delivering on customer
needs all the time.
00:53:12.750 --> 00:53:20.875
Design thinking, promise that, you know, we're oh, now we all know We all know design thinking so we can just do it right.
00:53:20.875 --> 00:53:42.458
So it it kind of promise that it lulled us into this idea that it was easy when really, it was about learning a language to create a habit or a discipline around how to do this, which I think is still, a big opportunity for designers to lead help organizations, you know, reach the promise of design thinking.
00:53:43.125 --> 00:53:44.708
So I don't think it's dead.
00:53:44.708 --> 00:53:47.166
Design thinking isn't dead. It's a great idea.
00:53:47.166 --> 00:53:49.916
It, we still practice it every day.
00:53:49.916 --> 00:53:55.041
You do an idea, whether you call it human centered design or whatever we want to call it.
00:53:55.041 --> 00:54:00.500
It's, It's such an important part of the future of, business.
00:54:00.500 --> 00:54:09.125
The future of adding, you know, meaning to people's lives through new products and service innovation, which I think is part of what motivates us, gets us up in the morning.
00:54:11.000 --> 00:54:14.875
So it's not dead, but we have to be better at how we do it, for sure.
00:54:14.875 --> 00:54:15.625
100%.
00:54:15.625 --> 00:54:35.625
So what I would I guess my advice to anyone who's a designer in whether you're in a large team, small team, start up, large company, or think about how you can implement the process in the way of working in, you know, the most scrappy, efficient, but thoughtful way for your context.
00:54:35.625 --> 00:54:47.208
So there was an initiative that I was working on at Walmart around driving digital adoption, and we just did this really scrappy in-store test to understand the users mindset.
00:54:47.541 --> 00:54:50.250
So we picked a few really busy days in a store.
00:54:50.250 --> 00:55:01.041
I went there with a few of my design colleagues and we we talked to people and we we set it up in a way so that we could gather some data around, like app downloads and app usage.
00:55:01.625 --> 00:55:07.041
And we just really wanted to understand, like what's holding people back from digitally engaging while they're shopping.
00:55:07.625 --> 00:55:10.250
We organize this in a relatively short amount of time.
00:55:10.250 --> 00:55:12.500
We spent three days there.
00:55:10.250 --> 00:55:12.500
We got some data.
00:55:12.500 --> 00:55:26.000
The whole thing end to end, was maybe 4 to 6 weeks, and it was incredibly enlightening because we were just in the world with people talking to them and really understanding, that was a scrappy approach.
00:55:26.000 --> 00:55:32.416
I think a lot of the things that we did at Chase, like with our self check in, that was also scrappy.
00:55:32.541 --> 00:55:39.291
Is there a way where you can impart some of that way of working in a nimble, thoughtful way?
00:55:39.625 --> 00:55:46.375
So whether it's around understanding the user, whether it's around
like digging in and understanding the business context more, or is it prototyping?
00:55:46.750 --> 00:55:53.833
Is there a way to test and learn from our prototype beyond just sort of online click through panel based research?
00:55:54.833 --> 00:56:01.166
How do we how do we keep those aspects of the process alive, like take the time to really synthesize and understand?
00:56:01.666 --> 00:56:07.708
It doesn't have to be a long, exhaustive, luxurious process.
00:56:07.708 --> 00:56:22.666
We can bring these these bits and ways of working, you know, into what we're doing day to day to make sure that we're actually, you know, truly, authentically understanding users, creating really human centered solutions and things like that.
00:56:23.000 --> 00:56:27.250
Yeah, I agree, I think, you know, a we have to do it.
00:56:27.291 --> 00:56:28.750
We have to do it well.
00:56:28.750 --> 00:56:51.250
But I also think the way we communicate those insights to the organization, the way we bring those stories back to the organization, I sometimes the people who get most excited about design research that I've found, are the marketing people and the executives, they finally are hearing the stories of what customers are actually experiencing or want to experience.
00:56:51.250 --> 00:57:08.791
And it's incredibly empowering for an organization and, and we can be the catalyst for that, right, by immersing ourselves in current experiences or or co-creating with them to understand desired experiences, bring that information back and activate that in an organization.
00:57:09.083 --> 00:57:17.416
Use that to align a team and translate it into new kind of products and services, and that those are, I think, ways that the organization can go fast.
00:57:17.750 --> 00:57:29.541
The things that I see, what keeps an organization from going fast is guessing because you you wind up being uncertain at all points in the process about whether you're doing the right thing.
00:57:29.541 --> 00:57:32.291
Right. And that trips organizations up.
00:57:32.291 --> 00:57:39.208
So just getting these insights and built and starting with a foundation is a great it's a great design thinking principle.
00:57:39.208 --> 00:57:41.416
Right? It's a design doing principle.
00:57:41.416 --> 00:57:45.916
How would you ever solve a problem if you don't even have any idea of what it is?
00:57:45.916 --> 00:57:52.666
You know, it's times like when we teach, we talk about designing as being problem solving or innovation being problem solving.
00:57:53.125 --> 00:57:57.333
Well, this kind of work that we're talking about here is like problem seeking or opportunity seeking.
00:57:57.833 --> 00:58:05.125
And if you're not, dialed in on the right kinds of things to go solve, then are you really adding value?
00:58:05.125 --> 00:58:12.083
And the problem sometimes with features is, first of all, we may have made them up, and then you wind up designing just around that feature, right?
00:58:12.083 -->
00:58:26.208
It's like staring at your shoelaces, walking around the room like, you know, you only kind of are innovating whatever is right there in front of your toes rather than maybe finding the true opportunity to transform the business.
00:58:26.208 --> 00:58:34.541
And so, I, you know, this is thing I know this gets you up in the morning and gets you excited about the kind of work you do, and it does us as well.
00:58:35.166 --> 00:58:38.541
I think there are tremendous opportunities for designers.
00:58:38.541 --> 00:58:43.041
I think design thinking is something that's really, required.
00:58:43.041 --> 00:58:45.500
It's mandatory.
00:58:43.041 --> 00:58:45.500
We need to be better at it.
00:58:46.708 --> 00:59:05.208
And I think to do that, we need to be more sensitive, as you say, to businesses, we need to be, understanding going beyond the feature to really the value that it provides and how to deliver it in a way that people will adopt and use it, and then ultimately understanding all the points on the journey, as you mentioned.
00:59:05.208 --> 00:59:19.833
So I thought your article is really well done, So, maybe just to wrap up, if, if there's any want, you know, one thing you can provide to practitioners that you would give them, like, what do you think?
00:59:20.208 --> 00:59:21.208
Or maybe let's do this.
00:59:21.208 --> 00:59:32.250
What do you think the biggest challenge is facing, UX and CX and human centered design leaders in an industry today that we can now take and go work on.
00:59:34.250 --> 00:59:37.750
Well, what I've seen is, you know, there's been a lot of just evolution in the space.
00:59:37.750 --> 00:59:40.958
There have been some teams are growing, some teams are shrinking.
00:59:40.958 --> 00:59:43.041
They're more people who are practitioners.
00:59:43.041 --> 00:59:45.791
And there are roles available right now.
00:59:45.791 --> 00:59:52.541
So I think understanding like really understanding like what what the world needs from design.
00:59:52.541 --> 00:59:56.541
And I think we need to potentially recalibrate a bit.
00:59:57.500 --> 01:00:06.708
I think the more we understand, like design is different than art and that it is part of, it's part of our business world.
01:00:06.708 --> 01:00:13.083
Like we're, we're creating solutions that can be monetized as can be sold, can be used by customers.
01:00:13.083 --> 01:00:21.333
So we really need to understand that part of it, like what is best for working for any company, like what is what is that company aiming to do.
01:00:21.833 --> 01:00:27.375
how did we get to this point where we have more practitioners than we do have positions?
01:00:27.375 --> 01:00:42.333
There was a, you know, during Covid, there was a a huge, swing towards digital transformation and how human centered designers or designers needed to participate in that.
01:00:42.333 --> 01:00:46.583
And there was a, you know, everybody made a large design organization.
01:00:47.291 --> 01:00:53.333
And now five years from that, we're seeing them pare those organizations down like something didn't work.
01:00:53.333 --> 01:00:55.791
You know, what was it that didn't work?
01:00:55.791 --> 01:01:10.916
I think it it, goes to your point about recalibrating, like, okay, you know, if people are passing on designers, it means we haven't been as effective, as we could have been.
01:01:10.916 --> 01:01:13.000
How do we become more effective? You know?
01:01:13.000 --> 01:01:21.125
Yeah, I think for recalibration, some organizations are right sizing where maybe they had grown beyond what they needed to be.
01:01:21.125 --> 01:01:25.041
And, you know, I guess design has has always evolved.
01:01:25.125 --> 01:01:34.833
I think about my, my whole career arc and how, you know, there used to be many more jobs for industrial designers and other, you know, other types of practices.
01:01:34.833 --> 01:01:38.291
And we've really there's so much work now in the digital space.
01:01:38.833 --> 01:01:52.250
I think the more that designers in digital understand the business context can work really well with product, can wear multiple hats, can be scrappy, can make things real.
01:01:52.291 --> 01:01:59.250
Essentially, the more tools you have in your toolbox, the greater, you know, greater resource you can be to any organization.
01:01:59.250 --> 01:02:07.875
So I'm a strong believer in designers being capable of doing research as well, being able to prototype, being able to speak the language of business.
01:02:08.291 --> 01:02:13.958
The more that designers can bridge all of those things, the more value they can provide to a business.
01:02:13.958 --> 01:02:17.791
And, the that will just enhance their career longevity.
01:02:18.125 --> 01:02:18.958
Yeah, yeah.
01:02:18.958 --> 01:02:29.791
No, I agree, so let's talk about, how AI is impacting our ability to be effective, as I think we're making some mistakes with AI.
01:02:29.833 --> 01:02:34.375
You know, when we hear about people substituting or using AI for research.
01:02:34.458 --> 01:02:37.458
Oh, yes. Or instead of research, maybe.
01:02:37.541 --> 01:02:44.208
But tell me a little bit about how things like I can impact our ability to be effective as designers.
01:02:44.541 --> 01:02:49.166
And so I think we, we as designers can use AI to speed up some of our processes.
01:02:49.625 --> 01:02:56.208
I know we used to spend many, many hours and days on synthesizing insights from research.
01:02:56.541 --> 01:03:02.375
AI tools can certainly help speed up those steps in the process.
01:03:03.416 --> 01:03:11.125
I think there's a future where AI can take some work off designers plates by doing some more of the repetitive, sort of production oriented tasks.
01:03:11.416 --> 01:03:11.708
Yeah.
01:03:11.708 --> 01:03:15.208
I think there is a potential, there's definitely an upside to that.
01:03:15.208 --> 01:03:20.416
And speeding up our ability to design quickly and bring things to market faster.
01:03:20.458 --> 01:03:38.000
One of the drawbacks I potentially see is that those are often the tasks that younger designers are trained on, and we want to make sure that as people are entering the profession, they are building those those hard skills as well as the the higher level, you know, strategic skills and soft skills.
01:03:39.125 --> 01:03:48.416
I've heard about some AI engines being used instead of user research recently, which has made me just pause and reflect a bit.
01:03:49.083 --> 01:03:56.375
In one case, I had heard about a certain user group being sort of difficult to access or difficult to schedule.
01:03:56.375 --> 01:04:12.250
So there was an offering where they could take past knowledge of this user group and use it, as a basically large language model with machine learning to, you know, input questions to that group about a particular solution.
01:04:12.666 --> 01:04:15.666
And it would kind of come up with AI driven answers.
01:04:15.958 --> 01:04:28.208
I think that is risky and that that is giving us information about what people might have said in the past, but isn't necessarily helping us understand what people will want in the future.
01:04:28.541 --> 01:04:29.208
Yeah.
01:04:29.208 --> 01:04:36.125
So AI can certainly speed up and make many of our day to day tasks more efficient.
01:04:36.125 --> 01:04:42.041
I know I certainly use it to support, many of my workflows in the day to day.
01:04:43.166 --> 01:04:52.416
I think we want to balance making sure that we're not losing out on like the skills that young practitioners need to build, because a machine can do it faster or easier.
01:04:52.416 --> 01:04:59.583
Yeah, I see it as a copilot, you know, it's something that that can work with us, can accelerate our work, but it can't replace our work.
01:05:00.375 --> 01:05:14.500
I think about when I see young designers using AI, instead of novel research, to me it reminds me of, like, big data or things like that where it might feel good.
01:05:15.166 --> 01:05:17.500
In the short term, you know, it's like fast food.
01:05:17.500 --> 01:05:22.791
It might like, might taste good in the short term, but in the long term, you're going to pay for it, you know?
01:05:22.791 --> 01:05:28.791
So I see that there's real value in using AI as a sort of an assistive tool.
01:05:28.833 --> 01:05:34.458
And I also think the same way on the design side, you know, I can't design for us, right?
01:05:34.458 --> 01:05:37.791
It can it can help us consider possibilities.
01:05:37.791 --> 01:05:44.166
It can help us shape our ideas, maybe in a rapid way, but but it can't design for us.
01:05:44.166 --> 01:05:45.833
You know, I do like it.
01:05:45.833 --> 01:05:49.000
I think I can be an incredible workflow tool.
01:05:49.166 --> 01:05:54.708
And so we've seen value and just, you know, more effective writing, for example, or something.
01:05:54.708 --> 01:05:58.875
I think that, you know, I can help, help us with, you know.
01:05:59.333
--> 01:05:59.500
Yeah.
01:05:59.500 --> 01:06:05.708
Not to write not to write the ideas, find the ideas for us, but to help us express the ideas, you know?
01:06:05.875 --> 01:06:08.333
Yes, I think it can certainly help.
01:06:08.333 --> 01:06:12.791
Help be an editor and copilot in the writing process.
01:06:13.458 --> 01:06:18.958
Actually, one of my friends who's an industrial designer uses AI in very creative ways.
01:06:18.958 --> 01:06:32.291
Actually, a few of the industrial designers I know, they help speed up their concept generation process, using AI prompts to basically build quick iterations that might take them many hours to sort of sketch or render.
01:06:32.833 --> 01:06:33.083
Yeah.
01:06:33.083 --> 01:06:41.333
Which is to me, fascinating, a little, a little bit scary because it takes some of that, again, the human element out of it.
01:06:41.666 --> 01:06:41.916
Yeah.
01:06:41.916 --> 01:06:51.541
But every time that there's been a new emerging technology that people have sort of scared and questioned, we've ultimately found that there are more high value things that humans can add.
01:06:52.041 --> 01:07:00.750
So I like to embrace it and think about all the potential for what it could do for us more than, more than stepping back from it.
01:07:00.750 --> 01:07:17.750
Certainly, in terms of the I've my teams, I've worked on many AI driven, personalized experiences and e-commerce shopping flows, which can be extremely impactful, like making sure that the the user sees the right next product for them.
01:07:17.916 --> 01:07:21.375
They can take the next best action very easily.
01:07:21.708 --> 01:07:28.458
Where I can take some of the drudgery out of things like customer service experiences.
01:07:28.458 --> 01:07:29.875
I mean, that's phenomenal.
01:07:29.875 --> 01:07:37.666
We can we can take some jobs that are fairly mundane and automate them so that we can have humans do higher value things.
01:07:38.250 --> 01:07:41.833
I think we're still figuring out in design, like what actually that will mean.
01:07:41.833 --> 01:07:46.458
And as much as we can, I think all designers should go along for this learning journey.
01:07:46.458 --> 01:07:54.625
Like learn about the visualization prompts, understand what design tools, how they're integrating AI, and how we can use them to our benefit.
01:07:54.833 --> 01:07:57.791
Yeah, yeah, I love that idea of thinking about it.
01:07:57.791 --> 01:08:01.125
In a lot of ways, AI is just another technology.
01:08:01.125 --> 01:08:05.791
And we've we you know, we've experienced all types of new technology in our career.
01:08:05.791 --> 01:08:10.333
And it was about sort of like what are the attributes of the technology and how can they be leveraged.
01:08:10.333 --> 01:08:15.708
You know, I think about AI can help us create knowledge or mass personalization or all these sort of things.
01:08:15.708 --> 01:08:33.000
Think about how we can use the attributes to either improve our service design or product delivery, or how we can structure insights and tell stories and align the organization, you know, the things that we need to do, as designers in, in organizations to be effective.
01:08:33.000 --> 01:08:36.082
So, yeah, I love that perspective.
01:08:36.250 --> 01:08:37.041
Yeah.
01:08:37.041 --> 01:08:43.291
One more thing to just to think about, you know, we've had expertise and human computer interaction for decades.
01:08:43.291 --> 01:08:45.000
Just one thing designers have brought.
01:08:45.000 --> 01:08:49.125
So AI is just another form of human computer interaction.
01:08:49.291 --> 01:08:58.416
So I see design playing an essential role in helping to make the human interface with all of these new technologies more seamless, understandable, delightful.
01:08:59.000 --> 01:09:00.916
Yeah, yeah.
01:08:59.000 --> 01:09:00.916
What's the design language of AI?
01:09:00.916 --> 01:09:04.375
That's a great problem to go solve, you know, with the design principles.
01:09:04.375 --> 01:09:11.166
For AI think is another one, you know, how do you deliver it in a way that, people can trust it and be confident with it and use it?
01:09:11.832 --> 01:09:28.375
It is interesting how fast humans will, cede control to automation so that there's, I think also a certain amount of ethical practice that we need to be aware of when we're using it as well. But so great discussion.
01:09:28.375 --> 01:09:31.000
Carly, I really appreciate the time you spent with us today.
01:09:31.000 --> 01:09:33.582
I know you're super busy, so thank you for that.
01:09:33.582 --> 01:09:37.791
And thanks for bringing your insights to the Seriously Curious audience.
01:09:38.207 --> 01:09:40.916
Thanks again for being here and I hope you will come back.
01:09:40.916 --> 01:09:43.500
Yes, I'd be happy to. Thank you.
01:09:43.500 --> 01:09:44.416
Great, everyone.
01:09:44.416 --> 01:09:51.082
Thanks for joining us again today for Seriously Curious podcast on all things the experience for business strategy and design.
01:09:51.166 --> 01:09:55.291
We've got more great speakers lined up and coming, so stay tuned for future episodes.
01:09:55.791 --> 01:10:10.207
We'll be talking about, the future of connected and autonomous vehicles, the future of, mobility in general for air mobility, and AG super excited about what we have on store for, seriously curious.
01:10:10.500 --> 01:10:14.666
Again, if you want to reach Carly, you can reach her, on LinkedIn.
01:10:14.666 --> 01:10:16.166
That's probably the best way.
01:10:16.166 --> 01:10:21.207
Definitely check out her most recent, work and comment and and share that out.
01:10:21.625 --> 01:10:24.166
And, I know she would love to hear from you on LinkedIn.
01:10:24.166 --> 01:10:28.541
So again, Carly, thanks for being here today and we look forward to seeing you soon.
01:10:28.541 --> 01:10:30.457
Thank you so much. Thanks, everybody.