Skip to content
Artwork for Finding Our Way
ArtsDesignTechnologyBusinessManagementExplicit

Finding Our Way

Jesse James Garrett and Peter Merholz

UX design pioneers and Adaptive Path co-founders Peter Merholz and Jesse James Garrett discuss the evolving challenges and opportunities for design leaders.

Play
  • 24 episodes
  • fortnightly
  • Avg 52 min
  • English
Counted on this page — what you have heard stays on this device, so it is not something the list can be paged by.
  • Jun 6, 2025 · 53 min

    59: Design Isn’t Dead, But It’s Seen Better Days (ft. John Gleason)

    Show Notes Help Jesse and Peter better serve you by sharing a bit more about who you are, what you’re into, and what you’d like to hear from us in this listener survey which should just a few minutes to complete. Thank you! Summary: Peter and Jesse are joined by design and business consultant John Gleason. Coming up through P&G’s famous design initiative, we get his perspective on design beyond digital products, such as consumer packaged goods, we explore some significant parallels across industries and design domains with important lessons on the pitfalls that lead to diminishing influence for design leaders, and share what they should advocate in order to break the downward spiral. Help UX and Get a Chance to receive $100! Peter is conducting a global UX and Design Organizational Health survey to better understand the state of our practice and industry. 5 respondents will receive either a $100 gift card or 1 hr of consulting/coaching with Peter. It takes about 10 minutes to complete. Thank you! Transcript Jesse: I’m Jesse James Garrett, Peter: and I’m Peter Merholz. Jesse: And we’re finding our way, Peter: Navigating the opportunities Jesse: and challenges Peter: of design and design leadership, Jesse: On today’s show, is design dead? That’s the question strategy consultant John Gleason asked at a recent design conference panel. The ensuing discussion struck some familiar notes for digital product design leaders, but John Gleason doesn’t come from digital product design. Today, we’ll get his perspective on design beyond digital products, such as consumer packaged goods, the stuff you find on the shelves in grocery and drugstore. We’ll explore some significant parallels across industries and design domains with important lessons on the pitfalls that lead to diminishing influence for design leaders, what they should advocate for, and how to break the downward spiral. Peter: Hi John. Thank you for joining us. John: Delighted to be here, Peter. Thank you. Peter: So you and I met on the internet, specifically LinkedIn, around a discussion that was happening based on an article written in Fast Company that was explaining what this journalist had witnessed at a panel of design leaders that you helped moderate. And the title of the article had the provocative statement: Is Design Dead? So that’s how I’d like to start this conversation with you. Maybe we’re starting at the end, and then this can be a very brief conversation… John: What if I said the answer is yes, end of story? Peter: Then, then, then we wrap up the podcast. Jesse: Thanks everybody for listening. You can find us at findingourway.design. Peter: But seriously, I do want to ask, it is meant to be a provocative, obviously there were discussions happening on that panel and in that room that led to this question. So when you’re faced with a question is design dead, how do you respond? John: Well, we respond by creating a conference to talk about it. So my conference partners and I, David Butler, who was the first head of design at Coca-Cola and Fred Richards, who’s a long time ECD, CCO -type person in the brand design space at big agencies. The three of us came together just simply to talk about the industry itself. And as we compared notes, I have started to see that design is in decline, particularly in the consumer facing space, probably starting eight or nine years ago, kind of as evidenced by shrinking budgets and shrinking organizations and diminishing the reporting structure of design into leadership in those companies. And a lot of the people that I’ve talked to kind of chalk it up to, oh, well that’s the economy. Oh, we’re gonna cut budgets, it’s belt tightening, it’s these things. But I’ve had the chance to peek inside more than a hundred big corporations and a couple thousand design agencies. And so I see patterns that emerged. Jesse: Mm-hmm. John: And that led to the provocation of “Is design dead?” And I think we inherently knew that the answer was no, but I don’t think the rest of the room…so we had about a hundred people design leaders from various companies, mostly consumer facing corporations, but we had telecom, we had financial services, we had healthcare, we had core tech there in the room represented as well. I don’t think most of the people in the room saw the patterns because they only see what’s happening in their company, or the one or two companies they may have been a part of. And so there was certainly evidence, as we started to unfold some of the things, people were, “Oh, just thought that was belt tightening. I just thought that was seasonal. I just thought that was post pandemic economy.” That started the conversation. Jesse: So tell us a little bit about these design teams that you were studying and what was the change that you noticed over time? What was happening with these teams? John: So a, few things that I’ve had the chance to see. I’ve tracked about 200, almost 250 companies since about 2016, 2017. Jesse: Mm-hmm. John: And it’s things like, what agencies do they work with? Have they built in-house teams? What’s the reporting structure of the organizations? And some of the patterns that I’ve seen, Jesse, are 39% of those companies, so 95 companies of the 243, have cut the top one or two levels of their design function… Jesse: mm-hmm. John: … or they’ve downgraded the title to some lower title in the company, or they’ve downgraded the boss, the reporting title of the boss of those organizations. Conversely, only 6%, only 15 of those companies have done the opposite, have elevated design with a higher title or a higher reporting status in the company. 9% of them, 22 companies have eliminated more than half of their entire design function in a single year. Jesse: Wow. John: 84% of them, this one shouldn’t be a surprise to people. 84% of the design leaders or the heads of design reports to a specific function in the company… Jesse: hmm John: Marketing, innovation product. To me, the troubling part of that is 75% of them don’t report to the head of that function. Jesse: hmm. John: They report to somebody lower in that functional hierarchy, which again, to me, signals a deemphasis of design, as a more of a service organization than a beacon for the future. Almost half, 47% of these companies, the head of design is at a senior director or lower. Jesse: Hmm. John: They’re not even in the executive community inside of those companies, nor do they have a career opportunity to grow beyond that director, senior director, some are even senior manager. Jesse: That’s as far as the design ladder reaches in those organizations. John: Right, right. Yeah. Jesse: So I find myself curious about the mandates of these teams and what these teams are being asked to deliver, and whether those mandates are shrinking as the teams scale down and move downstream as you’re describing in these very large organizations. So what kind of design are we talking about here? John: They certainly are diminishing in the scope of influence inside of those companies. So many of them, the design organization in a lot of consumer goods companies is really a packaging function. And it ends up being a decoration function for packaging. Jesse: Okay. John: In some cases, they might be able to influence a better consumer experience, but, in many cases, especially in the, present economic circumstance, it’s cost cut, diminished, streamlined. Jesse: Right. We’re basically talking about boxes and bottles on retail shelves. John: Yeah. Yeah. And, there are some where design sits in an R and D or innovation organization… Jesse: mm-hmm. John: … where design influences, again, the structural component of packaging. Occasionally they’ll influence the juice and the powders and the things that are inside the boxes and bottles. But mostly more powerful R and D organization says, Hey, design, we’ve got that. We’ll take care of that. Jesse: Right. John: And they tend to be looking at very narrow components inside the company. The other interesting thing, particularly as it relates to a more digital component, is many of these companies have assigned a chief digital officer in charge of the digital transformation and digital pathway for those big companies, building their own design teams, largely UX, UI and some development, although development tends to be outsourced and offshored. And they’re not connected to the other design capabilities inside the company. Jesse: Right. Yeah. John: And in fact they sometimes compete. I did some consulting work for a couple of companies where there was somewhat of a bitter, antagonistic relationship between the head of design and the head of digital. Jesse: Yeah. Well this is, I laugh because this is a regular pattern that we saw in our consulting work going back 20 years. That if the digital product design team was more closely aligned with digital than with design, sometimes that created a conflict and that created friction internally in terms of how things got done. I’m curious about the evolution that you’ve seen in these mandates. So in what ways have these design teams had to refocus their efforts as they’ve scaled down? John: I spent 20 years at Procter and Gamble. I was a part of the very earliest portions of P and G’s journey to elevate design. Jesse: Hmm. John: When I joined the design function, there were 60 people in the design function at P and G. When I left, about five years later, there were 350. It was all around strategic design, leadership, the head of design, Claudia Kotchka at the time, and the CEO AG Lafley had a vision for design. So, why I believe design is in decline is most of the design responsibilities that I see today are nowhere close to what I experienced at P and G. Peter: Hmm. Jesse: Hmm John: That’s the decline part, but you know, there are one or two work generations that have come in and out of the workforce since the early two thousands. I’m often brought into corporate organizations either by the head of design who wants to try to figure out how to articulate up to the C-suite about how design is more important, how it should be invited earlier, how it should be organized and not just touching an artifact, you know, a package or a website or a banner or something, but influence the entire enterprise. Jesse: Mm-hmm. John: The C-suite often has no clue what design would do with the rest of the enterprise other than the thing that they had been doing… Jesse: mm-hmm. John: … in the company. And so there’s often that disconnect. Jesse: right John: One of the things that I often see, first of all, there is no school largely for design leaders to step in and talk business. Jesse: Right. John: Very, very few programs. IIT does a nice job. SCAD is beginning to do things like that by building a business innovation component. But largely it’s teaching the tools of the industry. So when somebody lands in one of these important jobs, they speak the language that they know, whatever it is: UX, UI, digital, color theory, communication theory, whatever those things are. And the thing that I have seen is, when they are under duress, when the business pressures start to pile up, most design leaders recess back into becoming uber project managers for the design activities, rather than leaning into the organizational component of influencing structure in humans and leadership. Jesse: Mm-hmm. John: If it gets to that, it begins to spiral. And within two years, that person is often gone because they’re micromanaging their team, and they’re trying to deliver great outputs, but not really influencing… Jesse: Right. John: …where design can influence. Design has a superpower of seeing things that other people can’t see, but often can’t articulate that in the context of the business language. Jesse: It almost suggests that, there’s, like, this gravitational force that pulls leaders down toward this sort of operational value proposition, as opposed to a more strategic value proposition for design as a function, for themselves as leaders, that takes active, ongoing energy to resist for leaders, yeah? John: One of the things I observed at P and G was when design was added as this new strategic capability for the company at the request of the CEO AG Lafley, the other functions felt like they had to defend themselves against design taking the fun stuff away from them. And part of it was, it isn’t trying to take things away. There was a component of let’s make sure the right people are with the right skills, are working on the right things at the right time. The influence of design was intended to try to make everything else better. Jesse: Mm-hmm. John: The ability to step back and really advocate for the user, in our case, the consumer. You know, P&G was pretty well known for consumer research and brand management and marketing, a lot of other things. So the idea that design could step in and knew better than these things that have been in place for 50 or a hundred years, some people kind of took it personally. I earn a lot of enemies in the design space when I say this. I say if a company really wants to elevate design in a truly strategic way for the entire enterprise, it’s my opinion, the first head of design probably should not be somebody with a portfolio. Jesse: Hmm. Who should they be instead? John: It should be somebody that might have come out of the business, might have been a marketer, might have been an innovator, might have been a strategist, but has a high IQ for design because those people know how to have the battles with other people with more stripes. They know how to, play the political game. They know how to influence. And I’m gonna be horrendously unfair and I’m probably gonna get a lot of mail from your listeners. Designers index introvert. Jesse: Mm-hmm. Peter: Yeah. You’re not gonna get any pushback on that. John: Which means I don’t want conflict. I’m gonna run away from conflict and I’m not gonna address it. Whereas Claudia was an accountant by education and a marketer by training. And she had no fear walking into people that had more stripes than her to say, you’re not doing it right. I mean, she threatened a few business unit presidents to say, I’m taking your whole design team because you haven’t treated them well. You don’t respect them, and they all wanna quit, so I’m gonna take them. And of course, you can’t do that. And, you know, then the tete-a-tete occurred, and those are extreme examples, but part of this is, unless a business leader, whatever function you’re in, and I’ll highlight design in particular, unless you’re willing to fall on the sword for some things… Jesse: mm. John: … then, you can expect that the pressures of the business environment and the politics has the risk of crumbling your status in the enterprise. Peter: A couple of thoughts. The first, it’s interesting to hear you say that about that idea of your first head of design not necessarily being someone who came up through the practice. It sounds like Claudia was like that. Jesse and I have had that experience, him more directly than I, with the head of design at Capital One, which was the company that acquired Adaptive Path, was Scott Zimmer, who… his background was in brand and marketing. But he was design mature. He understood the opportunity that design delivered, and this was, you know, over a decade ago, better than almost any design executive I ever met, he knew how to communicate up. He knew how to get senior leadership excited about what designers could do in a way that designers often struggle articulating their own value. So I’ve seen that. I wanna go back though to the design in decline conversation. ‘Cause in order to decline it had to have risen… John: yep. Peter: …before then. And you explain the P and G story where a very savvy CEO invests in this function, makes it strategic. Like AG Lafley clearly had a plan. With Claudia had a kind of lieutenant who could realize that plan. But that’s likely an outlier, Right. Whereas in these other organizations where design was elevated, I’m curious what you see. ‘Cause you know, you’re, coming at us from a consumer packaged goods, maybe more in the advertising, marketing side compared to where Jesse and I live. But my concern for those design leaders who were elevated is that they had not been set up for success by their leadership. Their leadership didn’t know what they were doing, elevating them into those roles. Say we’ve taken a director or senior director of packaging design, we promoted that person into a VP role that had broader design mandate. But this person with a packaging design background knows packaging design. They don’t understand design for innovation, design for new product experience, all of those things. Maybe they tried, maybe they didn’t, doesn’t matter. But at some point, like, because this person hadn’t been set up for success, it would almost be inevitable that there would be a decline, regardless of broader economic conditions. I’m seeing you nod your head. So I’m curious how this could have been handled better by everybody, you know 10 to 15 years ago instead of like, oh, you have a title with the word design in it, so we’re gonna give you more authority, but we’re not gonna necessarily understand the implications of what it means for you to be an executive. We’re just gonna all of a sudden give you that title. it just feels like, this was bound to happen. John: You’re exactly right that it is in fact bound to happen because the vast majority of the companies that I’ve worked with and or studied, where the company chose to make a deliberate attempt to elevate design with a higher title, a new person that they perhaps brought from outside. The first observation I’ve made is most of the senior leaders, the C-suite leaders in those companies they don’t think somebody at a VP, SVP, EVP or Chief title needs to have somebody around them to protect them. Jesse: Mm. John: No other chief or SVP in the company, you know, they’re navigating the politics themselves. The head of R&D, the head of finance, the head of marketing. The most successful of those, where it was elevated, Proctor is one where AG Lafley was, in essence, the protector for Claudia. When Indra Nooyi at PepsiCo, she also was the inventor that design was gonna make a difference at PepsiCo. First elevated somebody internally. Didn’t work so well. There was a big packaging fiasco with Tropicana. But, I give her a lot of credit by not walking away from it after that fiasco and she continued to lean into it. Ultimately hired Mauro Porcini. Peter: Mm. John: David Butler, when he was brought into Coke, there was an influencer behind him that planted the seed that design could be more strategic. Mark Mathieu, who went on to Unilever, then Samsung but in those organizations there were people that were aligned with and connected to those people to help provide some business interference. Jesse: Mm-hmm. John: And in those organizations, they had a longer run and a more strategic run for design. Where the newly appointed head of design steps in, I’ve seen 10 or 15 of these where they were promised access to the CEO and the CMO but that access turned into, oh, I need to prepare three weeks ahead of time and send the deck one week ahead of time in order to have a meeting with the CEO. Whereas the example, and again, I’m super spoiled by this AG Lafley role model. Claudia had a design board on which Ivy Ross was on the board at the time. She was at the Gap or Old Navy. She’s now at Google. Tim Brown was on that board. AG never missed a board meeting. So the relationship that design had with the CEO at P and G was a casual one. Jesse: Right. John: It wasn’t surrounded by formalities and PowerPoint decks and, you know, six weeks lead time. McKinsey did an amazing study on the business value of design in 2018. DMI did something where they created a design value index with 16 or 18 companies, although I think they cherry picked 16 companies that were performing well so that they could track the commercial value. The UK Design Council did it before DMI and then my own observations, I’ve kind of developed this notion of six attributes of what I call design engaged companies, one of which is advocacy. That the senior most people in the company see that design is a critical component of the company and they support it appropriately. There’s access, there’s meetings, there’s, you know, public recognition you know, titles and all those other things that come with advocacy. But it’s just not the two humans. It’s just not a CEO and the head of design. it’s advocating that design needs to touch other parts of the company. Jesse: Mm. John: You know, when I step into a C-suite conversation, I often say, so, you know, how does design play a role in your company? Oh, you know, packaging or product or innovation. and I often touch on things, well, do you have any design talent looking after employee engagement, trying to create a place that more and more people have a passion for wanting to work here? Oh, well, that’s our HR organization. It’s like, you know, with all due respect to the talented human resources people, most of human resources is built to protect the corporation. Peter: Right. Jesse: Indeed. Yeah. John: … to inspire more loyalty to the enterprise. Jesse: So I find myself curious about this notion that there’s a skillset that is needed in order to really drive design at this executive level, that these design leaders have not been able to cultivate within themselves. I work as a coach with lots of design leaders at different stages in this process. And for some folks, they get to that executive level and they realize that like, oh, everything that I’ve learned up to this point is almost completely irrelevant now. John: Right. Jesse: And so I’m curious about like, what are the corners that you’ve seen leaders have to turn as they kind of ascend out of simply overseeing design as a function to actually being an active participant in executive level leadership? John: Well, design leaders recognize that virtually everything they do is part of a team sport. Jesse: Hmm. John: And, it inhibits their ability to articulate what it is we’ve contributed to the enterprise… Jesse: mm-hmm. John: … because it involves so many other people to get a product to market or to create a new experience or whatever those things are. And in most cases, rather than trying to step up and say, we had this impact, they often acquiesce and say nothing. Jesse: Mm. John: And so somebody else often steps in, you know, the ad agency is notorious for stepping in to say, Hey, we, completely repositioned this brand and we did this. We created new experiences, but it was the ad campaign that helped drive a 40% lift in sales. And part of it is, he or she who has data, has power. And design, there’s so much that design does that isn’t measured by data. And so it’s super hard… Jesse: yeah. John: … and to me one of the abilities is, how do I talk about impact? It doesn’t have to be a mathematical calculation or effectiveness. And then the other is, creating a vision. As much as one of design’s superpowers, in my opinion, is creating the future for a product or service or experience. We do a terrible job doing it for ourself and our own organization and how we’re gonna fit in, in an organizational context. Jesse: Mm-hmm. Peter: Yeah. In my coaching and in my masterclass I stress the importance of, I call it having an agenda, just because the word vision can mean multiple things. And so I call it having an agenda, and it’s something that so many design leaders, yeah, lack, like, they don’t realize they need to have their own point of view. Jesse: Point of view, right. Peter: Their own perspective, their own change that they seek, or if they don’t, they end up just getting in a reactive mode. They end up simply responding to whatever’s coming at them because there’s nothing that they’re trying to drive. One of the reasons Jesse and I were interested in having you join us is your background is consumer packaged goods, P and G, more on the marketing, brand, quote unquote consumer side. Our experience is more on the digital side. And I think it’s interesting to consider what’s different, what’s the same. Something that you’ve been touching on, A designer’s and design leader’s ability to connect their work with value and feeling like they need to have every link in the chain specified or they can’t commit to any ownership of it. But I think related to that, you’ve touched on this, but I’m curious what you see in your world, Jesse and I have talked a lot about the primary value of design is in facilitating or multiplying other functions’ ability to succeed as opposed to design delivering direct value. Jesse: Yeah. Peter: You’re nodding your head. So it sounds like you’ve seen something similar, but how do you counsel those leaders to navigate that conversation when their leadership is like, well, what has design done for me lately, and design can’t say I shipped this thing. ‘Cause they didn’t, but they worked with these groups, and through that work, they helped those groups improve what it is they’re doing. What is your approach to telling those stories better? John: I think you’ve struck a nerve on one of the big opportunities for design, because design often is a curious source of questions. What if, how might we, did we look into that,who said that? You know, who are we trying to reach for what purpose? And the business is about, let’s go, I don’t have time for these questions. You know, we gotta get something out the door. And especially in tough economic circumstances, the planning horizon becomes this quarter, next quarter, which isn’t a boundary space that design is very good at. Design is much better… they want to talk about the future of the brand, the consumer, the experience. And somebody at the conference used this rubric of the now, the near, and the far. Design tends to want to talk about the far. The capacity of the business leaders and the business, especially, the more dire the circumstance, the more they want to talk about the now. Jesse: Right. John: And so a CEO might only have capacity for 1% of their time on the far, even though that should be a part of what he or she is really thinking about for the corporation. But design wants to spend their time beyond the near and into the far, and so there’s, a misalignment of planning horizons. Jesse: Well, it’s a tricky place that design leaders find themselves in, too, because I think that often they feel like they are like standing on the dock with a stack of life preservers, watching these executives flail in the water, going, “Hey, I can, I can throw you this thing at any time. And you’ll be good.” And they’re like, “No, no. Focus on your current work.” Right? And so like, how do, how do you strike that balance of actually activating the real value proposition of design as a function, actually, you know, maybe rescuing some of these C-levels out of the water before they drown, while also making them feel like they’re getting what they want from you. John: Well, let me, continue your metaphor of the executives flailing in the bay. Jesse: Mm-hmm. John: When an an executive is in that circumstance, who are the likely people or the likely functions they are likely to go to first… Jesse: mm-hmm. John: … in the attempt of trying to save the ship or save themselves? Design is often the last one, Peter: They will go to marketing, they’ll go to sales, they’ll go to whomever. Yeah. John: They’ll go finance, they’ll go to supply chain, they’ll go to regulatory, you know, depending on the business and where the stress is. and that’s where I think design needs to learn how to lean in to show that they’re a business solver, not a creator of an artifact… Jesse: mm-hmm. John: …you know, code or a device or something. One of the best examples, and I use this example all over the place, is Logitech. Bracken Darrell, the former CEO hires Alistair Curtis. And everywhere Bracken went internally and externally, he said, I hired Alistair to help create Logitech 3.0. And so advocacy. Bracken set the vision for Alistair, and much of that continues now under Haneke Faber and Molin. Peter: Hmm. John: And, to me, part of it is, how do you empower the design lead so that the rest of the business expects you to be invited to the important business stuff. Jesse: Right. John: And in fact, lead some of the important business stuff. If the senior most people continue to see design as a creator of artifacts and implementer of execution, then it’s super hard for that person leading that function to elevate beyond. Peter: Well, this begs a question that I have been asked for 25 years, So we know that design seems to need executive sponsors. You’ve stated that your research has shown it, in a way that other functions don’t need executive sponsors, right? You mentioned that advocacy role is one of your six indicators of a kind of a design mature, design ready environment. That begs a question, how do you realize that executive sponsorship, someone like Bracken, someone like AG Lafley, someone like Ginny Rometti at IBM, someone like Carl Bass at Autodesk, these CEOs knew that design could help solve their problems, so they didn’t need anyone to educate or evangelize. Jesse and I, and I’m sure you do as well, but Jesse and I, the vast majority of the design leaders we talk to or work with, their leadership are not advocates. They might not be hostile… Jesse: yeah. Peter: … right? They might be even curious, but they’re not advocates. And so the challenge that, so many design leaders face is how do they turn those executives into advocates? Can you even do that, right? There’s some commentary over the last 15 or so years that, like, if an executive doesn’t get it, there’s very little you can do to help them get it. Like, it’s not like it’s a hidden mystery. It’s not that no one knows that design can help business. McKinsey’s written about it. HBR has written about it. Roger Martin wrote about it like AG Lafley proved it through the P and G success. And so is it a fool’s errand to try to convince or persuade that executive to advocate for you? Or is that worthwhile? And if it is, what have you seen, at least in the organizations that you’re looking at, that starts turning that tide so that executives who may have been, again, not hostile– if they’re against design, there’s almost nothing you can do–but, are you aware of mechanisms that, have helped turn that corner. John: There are some things that I’ve seen. There are some things I recommend. One of the underlying reasons that I believe design is being dismantled and diminishing, is what I call C-Suite ignorance. Part of that is there are new C-suite members being minted every week. Many of them have never been exposed to the idea that design could be anything but… Jesse: right. John: …a decoration station. So they just don’t know. And, the other reality that often occurs is the genetic makeup of people that reach C-suite status or senior executive status, they get to a point where they can no longer admit they don’t know something. So they can’t admit that they don’t know that design is or isn’t something. So they lean in to whatever they believe or perceive or have experienced design to be in their past. Jesse: Yeah. John: I mentioned earlier that I’m often hired by heads of design trying to articulate up. The other group that hires me are the C-Suite people who want a discreet advisor who’s gonna whisper in their ear about, tell me the things I should know about design. Jesse: Mm-hmm. John: They’re not gonna publicize broadly that they don’t know, then, and, you know, they ask me to be discreet about the relationship. And it’s a Cyrano de Bergerac kind of thing. I try to tell them what they ought to know, and how they ought to play that out to their organization. And some of it is just purely an exploration. Why should I care? I keep reading that design is something I should know about, you know, why don’t I know more about it? Why isn’t it more prevalent? And I think part of it is, nobody questions the existence of a chief marketing officer. No one questions the existence of a chief financial officer. But design is a confusing word. It’s a confusing concept. It’s a noun, it’s a verb, it’s an outcome. It’s an organization. And most people in the business context see it as the participation or creation of an artifact, not necessarily a way of thinking or a mindset so to your question, Peter, small wins is a big successful pathway. But oftentimes, if you read marketing publications, the typical CMO has an 18 to 22 month time window of their credibility and existence in a company. Jesse: Mm-hmm. Right. Peter: That’s it. Not even two years. Jesse: Yeah. John: Not even two years. So they’re not looking at things that are gonna be three years from now. They need to go prove and deliver now… Jesse: mm-hmm. John: … which again impacts the ability for design to help influence and be a partner in that, delivery. Something we did at P and G, Claudia Kotchka, in the very early stages, brought in IDEO to run a hands-on work session for the top 50 executives in the company. And it was very much a hands-on exercise, that had nothing to do with P&G products, but more about how do you rethink and re-see, and how do you stay focused on the user and the consumer, and how do you build better experiences? It was a half day workshop and, you know, imagine 50 high performing type A’s sitting in a room being led through a workshop, but there were varying degrees of impatience, I would imagine. But a part of it was, then they translated it to a business opportunity for each of the businesses that were in the room. So, okay, we did this generic thing altogether. Here’s how we do this. Focus on the consumer, how might you create something. Now, and they literally handed things out to say, we’ve looked into most of your other businesses, and here are some things that could be, as we look at consumer behavior, things you might be interested in looking at. Now it probably was a great commercial for IDEO, too, inside of this group to say we’ve already thought about some opportunities. But, the economic circumstances were more positive. They weren’t belt tightening times like they are now or 2009. Capital was very cheap to acquire. So there were circumstances that I think accelerated our ability to do things like that. Jesse: Right. I feel like all of this connects to a question that I often ask my leadership coaching clients when they are stepping into a role for the first time, which is, what are you inheriting? And yes, you’re inheriting a team and you’re, yes, you’re inheriting a product and you’re, yes, you’re inheriting a legacy, but you’re also inheriting a whole bunch of expectations. Expectations that maybe were set by the leader before you, maybe were set by leaders that these executives, to your point, had other exposure to, that may have nothing to do with what you think the value proposition of you and your team and design as a function actually is. And so it then becomes this game of resetting expectations, and in a lot of ways listening. Just simply listening for what these executives think you’re there to provide and figuring out how to start to lay out the stones on the path that will take them to the value proposition that you actually feel like your team has to offer. But that’s a time consuming process. It is not something that happens overnight. And to your point, in a lot of these cases, 21 months is the horizon. So how do you balance those things? John: I think you touched on something really important, Jesse, is the idea of, a design leader that might be interviewing for a gig inside of a company, are they asking the right questions about what does it look like today… Jesse: mm-hmm. John: …because one of the things that I’ve seen is most internal talent acquisition teams inside of companies have no clue how to hire for this role or even for the whole function. Jesse: Mm-hmm. John: They think they need a portfolio, they think they need, you know, these things. And if they’re not getting help from a recruiter who knows this space, especially for a critically important role like the head of design or a VP of design. One of the things that I coach the design leaders is, every meeting you have with your colleagues and counterparts in the company, you should be planting the “what if” seed somewhere in the organization to say, What if it looked different? What if it could be here? It’s a super inexpensive way to try to get them to bite, you know, to lean in and say, you know, why would you say that that’s something we should look at? Then you can lean in with consumer data, or you can lean in with trend data, or you can lean in with economic circumstances. The other thing that I advise every design leader I coach with is, put a gigantic bogey in the ears and the minds of your senior leaders. You know, hey, I think I could help get us a billion dollars of incremental revenue if, you know, and then lay out, have your hostage list there. I need a team of this size. I need budgets. I need, you know, advice, I need your advocacy. I need these things, but I think I could help lead us toward an incremental billion dollars in revenue. And, almost none of them actually do it because they’re scared to death to be accountable for a number that they don’t have full responsibility of, How do you go deliver it? Jesse: The big, hairy, audacious goal. John: Yeah, exactly. Part of it, Jesse, to your question, keep planting seeds, keep leaning in, keep pushing, keep challenging, keep questioning, so that the business eventually sees… One of the things I often see, especially in consumer goods, is the business leader saying, we don’t have the time and we don’t have the budget to go do that ethnography study. Jesse: Right. John: We already know what we need to know about the consumer. And, here’s the idea that we’re gonna launch. And oftentimes it’s not a bad idea, but it’s not gonna be the disruptive category-changing domain-creating idea. It’s gonna be a conservative… in most cases, consumer goods companies are notorious for calling flavored line extensions, a massive new innovation. Jesse: Hmm. John: And it’s like, I don’t think the consumer thinks cinnamon is particularly innovative. Peter: The time dimension’s an interesting one. And I had a realization as you were talking about the 21 months, as you’re talking about how design often succeeds when it’s able to look far, and the results of truly impactful design take more than 21 months to be realized. But on the flip side, what I also see with design leaders is an impatience that things aren’t as they should be now. Like, they know what that change should be. They know we should be doing more ethnographic interviews. They know we should be running projects in this different way. They have a sense of, it’s evident how this should be all operating, why aren’t we just doing it that way? And so in some areas there’s this impatience that gets in their own way. You know, you’re talking about every conversation, move things a little bit, a little bit, a little bit. Design leaders are like, why? We know what we should be doing. Why aren’t we just doing the thing? And so I’m curious your thoughts on squaring that designerly impatience and frustration that we’re not doing the thing that is evidently the right thing to do now, with this kind of two- to three- or however many -year time horizon for design to actually be realizing an impact and what you see in your world. John: Well, if I use the concept of A/B testing Peter: Sure. John: out of the UX/UI space… Jesse: hm. John: … if a courageous, and maybe insane, design leader would say, okay, we’ll do it your way and not do this research, but I’m gonna secretly go figure out a way to get the funding to go do the research and I’m gonna create a parallel project and then compare the outcomes of what it is that is created, or envisioned, from it, to begin to show the business. Because the astonishing thing that I see from more and more big consumer goods companies is they spend a lot of time doing what I call the CYA research. “I’m gonna do a test of the package just before I launch it. Not to say we’re gonna kill the project or change the project, but I just wanna make sure I don’t get fired if it goes south.” Whereas if they just spent half that money on the upfront curiosity side, the impatience of the business to go deliver something this quarter, next quarter, now, doesn’t provide the ability for design to go do the alternative explorations. Which is why, the safe flavored line extension and those things become kind of the standard fare of consumer goods companies, and not terribly different than the software digital space where, you know, I’m gonna do a live A/B test. And the user of this travel website’s not gonna know that this set of people are gonna have these buttons in this place and this set are gonna have this button. But part of that gets to, how do you truly affect change? And I, think there needs to be a, if we do it this way, here’s the outcome, here’s the likely outcome. If we do it this way, it can be a bigger payout. The challenge is, if I’m a marketing director or a CMO, am I really gonna fund something that isn’t gonna launch for three years? Jesse: Mm-hmm. John: It might cost me $5 million between now and then to launch it and have no results and it could die along the way. Or am I safer delivering that line extension that is good. It, you know, it’s gonna, it’s gonna drive something… Peter: 10% improvement is better than zero. John: Correct. Jesse: You mentioned affecting change and change is something that we talk a lot about over here on the digital side and design’s responsibility for and toward change, and I’m curious about your point of view on design and its relationship to change. John: I believe design should be a catalyst for change. I believe that design should be an arbiter of culture inside of companies. One of the other of the six attributes I talk about is, Is the enterprise people-centered? Because one of the things I often see is most designers and, even UXers talk about being centered around the user… Jesse: mm-hmm. John: …and having an empathy for the people that are gonna buy my product, use my product, you know, use my service, experience the thing I’m creating. But then they say, oh man, but John over in supply chain, that guy’s a jerk. He’s a barrier to me. He’s always getting in the way. So the idea of empathy only seems to apply to the work you’re doing for the thing you’re creating. Peter: Right. Yep. Jesse: Right, right. Right. John: One of the big opportunities for design is having empathy for the senior most leaders in the company. Do I understand the pressure they’re under, and what they have to deliver? As opposed to feeling like they don’t understand me and they’re just laying unreasonable mandates on me. So a part of it is, this idea of change, this idea of culture, I think a lot of designers, when they’re creating that vision for the future and, potentially that next big thing, they’re not really thinking about what has to change to drive it. Jesse: Yeah, yeah, absolutely. It puts the design leader in such an interesting place too, because especially if you’re fortunate enough to be at an executive level, at a C level or a VP level, when you’re closely engaged with a larger executive team around the executive level decisions that drive an organization, it can often feel like your job is to create alignment, right? Your job is to align and be aligned, and find the alignment somehow in the room to create the harmony and the unity across the executive team, to genuinely deliver on a strategy for the organization. But if your mandate is to be the one person in the room who is like, ” Hmm. The way that we’re doing things is not good enough,” your strategy needs something more. It can feel like it really puts you in an awkward position, right? As an executive level leader, how do these leaders deal with that? John: Using the life raft example of the executives flailing in the harbor: is design the voice in that room that people are gonna listen to and believe? Jesse: Right, right, right, right. John: When they say something has to change. Jesse: Mm-hmm. John: You know, there’s a gentleman that I count as a friend in the design industry, Chuck Jones, who is a multiple-time chief design officer. And he’s very candid about the things that design doesn’t do very well, but he’s also very candid about, you know, when you walk into that new job as the head of design, you need to walk in with a point of view and a vision. And he told a story at the conference where he walked into one of his roles and he said, within some short period of time, four, six weeks, he said, I think I’m reporting to the wrong place. Jesse: Mm. Mm-hmm. John: And he made the case to say, this is the outcome if design continues to report as current, here’s the opportunity by changing it. And of course he had to have a few other meetings with important people to go make that change. The challenge is, if you can state the need for the change in the context of the business, not, not just an opinion, critically helps your case. If you can bring a champion or an advocate along with you, ideally a peer that’s in another function, Jesse: Yeah. John: ” Hey, I agree because this needs to change.” Otherwise people are gonna take the path of least resistance. I mean, human nature is to avoid conflict, avoid change, complain about change, especially if it’s difficult. It’s like the old adage. Practice how you play. And if you can’t practice in difficult circumstances when it’s game time, you’re not gonna play in them. Jesse: Right, right. Peter: So Jesse and I, and it sounds like you as well, John, think about this idea of design as an organizational function. it provides clarity into the real role of design. Not to make things, not to artifact, whatever, but, like, it is a function that engages in a set of activities to realize some value to the business. The challenge is design, as the three of us would like it to be understood, conflicts with the quarterly culture, quarterly requirements, needing to report to Wall Street, all the things we’ve been saying, right? That quarterly mindset that so many companies embrace constricts design, so that it’s no longer design, it’s basically production. Someone else has told you what to do and you’re executing on it. That makes me wonder, is that true of other functions as well, or are other functions perfectly happy operating in a quarterly mode, and design is different? And, I think it very well could be. But then, in that quarterly culture, things become more acute depending on the health of that business. And so the next thought is, is design only available as a kind of luxury function for those businesses that have already realized some success and some stability and don’t have to be as quarterly minded, and can have a longer term point of view? Are they the only organizations that are really able to embrace design, ’cause they’re the ones who can allow design the space it needs to succeed. But then that kind of conflicts with, again, what the three of us know that design could be doing to help struggling companies, right? Like it’s a set of tools that can be useful in a lot of different contexts. The interesting story is how can design help a company that’s struggling, succeed? But those companies aren’t willing to spend the time to allow design to have that change. So the only companies that are really embracing design as fully as they could are those that were probably doing okay already. Jesse: You need to be successful to have design, and you need to have design to be successful. John: Well, you’ve got it, podcast over. Thank you, Pete. Thank you, Jesse. Peter: As someone who’s, you know, more of a business background than Jesse or I, operating perhaps at an altitude or with a set of companies that are different than the ones that Jesse and I, more traditional organizations say, how do we change the conversation then, so that design is not simply seen as a luxury? Jesse: Where is the traction for design leaders within this context? John: One of the interesting corollaries to what you laid out, Peter, is a design community inside a corporation, if they can create a cadence of a longer term pipeline, then it makes it easier to accelerate things inside the quarterly dynamic. Jesse: Mm-hmm. John: So, if I do have the luxury of having a very small portion of my portfolio that’s a five or 10 year lighthouse project to say, you know, where could this company go in the future and have a, you know, a slightly larger one that’s five years and a slightly larger one that’s three. And then the majority of the things we’re working on are inside of two years, then it becomes, you can play to the acceleration needs of the business to play the quarterly game. The challenge is there isn’t often appetite at the C level to suddenly create that pipeline if it didn’t exist.. Jesse: Mm-hmm. John: …before and the monthly, quarterly, you know, this quarter, this year, kind of dynamic. If that becomes the exclusive of the portfolio I’m working on, you can almost never get to that longer term. ‘Cause somebody above you has to approve the budget and the time and the resources to focus on this thing. I’ve taught a four-day design thinking class in an MBA program in a university. And I bring a brand partner in. I get the students into a consumer’s home based on the product. And the dynamic when I’m selling this to potential brand partners, the way I sell it is, I want the project that you think is important, but you haven’t been able to fund it for the last three years. The company hasn’t seen it important enough to put official funding behind it. And I’m gonna show you how design thinking can help you accelerate an opportunity. And of course, they’re, you know, what can you do in four days and, you know, all these other things. We show them that, hey, two consumer visits can be better than none. And two consumer visits can be better than all of the quantitative survey data that you might collect that isn’t watching a human do something or not do something. Jesse: Right. So, you know, I feel like there’s a lot within the stories that you’ve shared with us and the research that you’ve done that suggests diminishing opportunity for design and for design leaders, in a lot of ways, and increasing obstacles. And I find myself wondering, where is the bright spark within all of this, and where is the opportunity that maybe design leaders ought to be giving more attention to right now? John: Coming out of the conference event that we held, we had three kind of principles that founded. The first was the question, Is design dead? The second was, you’re not alone and you don’t have to do this alone. The third was, “so what.” We wanted to have a “so what” component to every session. You don’t have to do it alone is an observation that I’ve had, and no doubt you all have seen it as you’ve poked into different companies and met with a myriad of leaders. Everybody thinks they’re fighting a historically unique battle because they don’t get out and talk to their peers. As a result, they end up fighting it themselves without a roadmap. And almost everybody that attended the conference used the term therapy. This was great. I realized I’m not alone. But then the, “so what” thing kicked in? And we said, okay, so what are we gonna do about this? And so I do think that letting people learn from each other, not just from people like the two of you and I that might drop in for a period of time, and then we drop out, and get people comfortable with: What have you done? What have you tried? And use the massive community of design as a way of trying to help revive and resuscitate the opportunity to carry it forward. I’ve got a great deal of passion for trying to see design change the trajectory and try to help drive that. And I do think that we need more examples of where design created an unexpected outcome. Jesse: Fantastic. I love that vision. I love the call to design leaders to be those examples and provide those examples that inspire the community. John Gleason, thank you so much for being with us. John: Jesse, Peter, thank you so much for the invitation. A amazing conversation, and obviously we could talk for three or four more days. Jesse: Yeah, absolutely. Peter: Yes. Thank you so much. Jesse: Where can people find you on the internet if they want to track you down and learn more about what you’re up to? John: Well, my LinkedIn profile is there to find me or John at GetaBetterView.com. Jesse: Fantastic. John, thank you so much. John: I enjoyed this. Thank you. Jesse: For more Finding Our Way, visit findingourway.design for past episodes and transcripts. You can now follow Finding Our Way on LinkedIn as well. For more about your hosts, visit our websites, petermerholz.com and jessejamesgarrett.com. If you’re curious about working with me as your coach, book your free introductory session at JesseJamesGarrett.com slash free coaching. If you’ve found value in something you’ve heard here today, we hope you’ll pass this episode along to someone else who can use it. Thanks for everything you do for others, and thanks so much for listening.

  • May 2, 2025 · 52 min

    58: AI is a Stress Test for Your UX: What Cracks Will It Show?

    Show Notes Jesse and Peter explore how AI is revealing the true value proposition of design teams. They discuss why “whoever controls the prompt controls the product” and why design leaders must understand their organization’s expectations before embracing AI. The more things change, the more they stay the same—AI may be new, but the fundamentals of design leadership remain critical. Jesse’s presentation “The Elements of UX in the Age of AI” is now available as a digital download. Get your copy today. Peter has just launched his masterclass “UX/Design Leadership Demystified” in two formats—self-study and cohort course. Learn more here. Transcript Peter: Make sure to stick around to the end of the episode to hear a couple of new offerings from Peter and Jesse. Jesse: I’m Jesse James Garrett, Peter: and I’m Peter Merholz. Jesse: And we’re finding our way, Peter: Navigating the opportunities Jesse: and challenges Peter: of design and design leadership, Jesse: On today’s show, reflecting on my talk: The Elements of UX in the Age of AI, Peter and I sit down one-on-one to talk about AI and its implications for design roles, design processes, and design leaders. We’ll talk about the new skills teams will need, the old skills that won’t be going away, and why. In an AI-enabled world, whoever controls the prompt, controls the product. Peter: So, a few weeks ago now, you gave a talk on the Elements of User Experience in the Age of AI. And that’s where I want to start. As a UX guy, when I see commentary about the intersection of UX and AI, or rather, primarily, design and AI… Jesse: mm-hmm. Peter: …it typically focuses on the top two layers of the elements diagram, the surface layer and the skeleton layer. And really the surface layer. I don’t even know if we’re getting much from a workflow standpoint. I’m just seeing screen design… Jesse: mm-hmm. Peter: …being what’s being discussed. And I’m wondering, am I missing something? Where is the conversation happening about AI and how it’s affecting the lower levels of the diagram? The structural concerns, the scope concerns, the strategic concerns? ’cause that for me, given my background in strategic design, is where my focus is at. And it also feels like, well, that’s the kind of thing AI can’t do. It requires my human brain. But I also don’t want to be that guy and be ignorant of the possibility that these tools are able to have a more kind of foundational… Jesse: mm-hmm. Mm-hmm. Peter: impact on the practice of developing user experiences. AI’s Strengths: Analysis and Synthesis Jesse: Yeah. Yeah. So the way that I tend to think about this technology is in terms of what I see as its two strengths, which are analysis and synthesis. Which is to say, finding patterns within a data set, and then extrapolating from those patterns something broader, right? So the pattern finding is the analysis part, and analysis is the stuff that’s gonna kick in when you’re down at those lower levels on the elements of user experience, where you’re talking about strategy, where you’re talking about scope, where you’re talking about user needs, where you’re talking about business requirements, where you’re talking about business models, where you’re talking about functional requirements, content requirements, all of those kinds of things. So this is where getting a whole bunch of data together and feeding it to the machine can help surface patterns that you might not otherwise see. And this analysis value proposition for the LLM is where I see it coming into play in these more kind of strategic and product strategy, scope oriented domains. Then when you get toward the top layers of the elements, then you start to get into these areas where the synthesis matters more. Where it’s more about what can you create, what can you generate out of the insights that you’ve created, out of the, really, the constraints that you’ve identified on your design problem. Because if we think about the double diamond, this is where divergent thinking comes in, where you are generating possibilities, creating ideas, and then convergent thinking comes in where you are refining those ideas based on criteria that you’ve developed. And so these are both areas where an LLM can potentially play a role in a user experience design process. What we see though, is that in these analysis oriented areas, where you are turning user needs into insights, turning those insights into requirements where you are evaluating and refining possible strategic directions, these tend to be processes that are owned by people outside of design. They may be owned by people in a UX research role. They may be owned by people in a product leadership role. They may be owned by people who are in a business leadership role. But often the direct purview of a design leader doesn’t actually extend all the way down the stack of the elements of user experience. And so what you see is a lot of the things that end up influencing user experience outcomes are actually owned by other roles in organizations. So I think part of what you’re seeing is that what design leaders feel like they can authentically control is the stuff that’s closer to the top of the stack, whereas the activity that’s happening at the bottom of the stack is happening in other parts of the organization, or that design leaders are ceding their influence over those areas out of a sense that that’s somebody else’s job, and my product person is gonna handle the AI that generates requirements, and I’m not gonna try to handle that myself. Peter: Weird that you say some of this, in part because I tend to think of the user needs part, the user research part is very much within the realm of design, typically. Jesse: It depends on the organization. In some organizations, the people who actually own that stuff don’t report into a design leader. Peter: That’s increasingly true, but not historically true, at least when it comes to UX research. There’s other forms of research. Jesse: Yes. Yeah. Yeah. Design leaders telling on themselves Peter: As you’re saying this, I’m thinking about something I saw a day or two ago on LinkedIn where a design leader was saying that unless you know code or are some Jony Ive-level brand craft wizard… Jesse: mm. Peter: that AI is going to take everything in in the middle or AI is going to subsume the work you do. Jesse: Mm-hmm. Peter: And I responded, well, maybe, if all your leading is production, but that’s not design, right? And so one of the things that’s been clear to me is design leaders telling on themselves about how they have led design and how they have abandoned those lower levels of the diagram. Jesse: Yes. Peter: And I say abandoned. It was not taken from them. If they knew what they were doing, it was there for them to lead. In my role as a design leader, I led folks doing the research. I led folks figuring out organizational models. I led folks developing the insights coming outta research that drove, that informed, I should say, product requirements. There were other means of informing product requirements… Jesse: mm-hmm. Peter: …certain kinds of customer conversations or whatever. But, maybe the conversation about AI and UX is really just a conversation about UX and design. It’s casting a light on just all the different ways, the varieties of ways that this has been led, this has been practiced in organizations, because, my point of view, both having led teams and working with design leaders of teams, is most of the teams I’m involved with have some responsibility all the way up and down the stack. You know, they maybe have more responsibility the higher up the diagram you get, sure. And the lower down the diagram, there’s a conversation to be had, but it’s a conversation. They’re not simply taking user needs from someone or the strategic objectives from someone. I guess, if as a designer and design leader, all you did was executing on the synthesis parts as you were calling them, the upper levels of the diagram, yes, it does appear that much of that work can be done by machines… Jesse: mm-hmm. Peter: …and that, for me seems like an opportunity for design. But it’s, intriguing how many people see it as a threat. Jesse: Right. Well, so, as you know, this talk came out of the work that I’ve been doing with design leaders for the last several years as a leadership coach. And in working with design leaders on their leadership challenge, it was this recurring theme that kept coming up of like, I’ve gotta figure out what I’m gonna do about AI. And what I found in those conversations is the value that AI potentially can deliver to your team depends a lot on the value that your team is seen as delivering to the larger organization. So if the value proposition of your team is narrowly focused on quality and speed of delivery of design assets, the value proposition of AI for your team is very different than it would be for a team where your value prop is more rooted in product strategy, user research, driving requirements, that kind of thing. And that kind of thing is gonna be highly variable because we’ve seen, as we’ve talked about with the variety of design leaders that we’ve talked with on this show over the last few years, we’ve seen a wide range of different frames for the value proposition of design as a function. And so where AI fits in, I think really relies on the leader clearly understanding what the organization thinks design is there to do for them. Peter: I had a similar conversation with some folks probably two years ago now about design systems, and the rise of design systems. And these folks were thinking of putting together an assessment of your design system situation. And as they were sharing this with me, what I realized is that that assessment had very little to do with the design system. Rather, that assessment was a probe on the organizational maturity when it came to matters of design and user experience. That, what you got out of that assessment was going to more be an indicator of what you were just talking about in terms of how the organizations that these leaders are in, understand design. And I think this is something we’ve talked a lot about, but I don’t know if we’ve talked about it on the podcast. And I wrote a little bit about it a couple weeks ago, which is the benefit for design leaders in considering their team, as a function, as an organizational function of the firm. Jesse: Yes. Peter: … not as a set of practices or activities. Jesse: Yes. Or as a group of people to defend or protect, right? Design is a symbiote Peter: Yeah. It’s more than just a group of people. There’s lots of ways you can slice these companies. You can have departments, you can have business units, you can have functions. And when you think of design as a function, it gets very simple in terms of what others expect of your team. You mentioned the word value proposition, right? What is the value proposition of your team? And, when you think of the value proposition of your team, as if it were a function, you can start looking at analogies of, well, what are the value propositions of product management, of engineering, of marketing, of sales? And how do you line up with that? And design has a really hard time lining up with that. That value proposition is different across different companies because design as a function is like a, um, a symbiote, I was gonna say parasite, but let me, let me say symbiote… Jesse: [Laughter] better. Peter: …design as a function is a symbiote in that it ends up taking on the shape of the organization it’s part of in a way that other functions I don’t think do, right? Marketing is gonna kind of look the same wherever it is. Sales is gonna look the same wherever it is. Engineering’s gonna mostly look the same wherever it is. Design is going to have to take on the shape of the organization that it’s part of in order for it to deliver its value, because design’s value is, much more about multiplying the success of other functions than delivering something straight on its own, right? And so, maybe before people start getting caught up in, how am I going to be disrupted by AI… Jesse: mm-hmm. Peter: … to do some groundwork in thinking about, how is my team showing up as a function of the firm? What is our value proposition? What do people expect of us? How satisfied are we with those expectations? Or do we need to change those expectations? Are people thinking of us primarily as UI production, or are people coming to us for the full stack of user experience delivery? And then once you have a sense of what your value proposition is, what people’s expectations are of you, now I’m wondering, how AI can be a tool to enable you to realize your objective in terms of how you want the rest of the organization to see your team. Jesse: Right. So there is delivering within your existing mandate, so to speak. Like, we’re gonna leverage this technology to better meet the expectations that have already been set, right? And then there’s the question of, well, can we push the boundaries of those expectations? Can we make a play for a broader value proposition for design in the product development process, for design in the product strategy process, to have more of a voice, to have more of a point of view that it brings to the table on where all of this is going. Whomever controls the prompt controls the product Jesse: One of the things that I mentioned in the talk that I think is a really important piece for design leaders is, in an AI-enabled digital product development workflow, whoever controls the prompt controls the product. Whoever is talking to the robot that makes the thing is the person with the power. And so your choice as a design leader is to figure out which things do you want control of the prompt over. Which areas of the product do you want your people to be the most prominent voice around, and building processes that support that voice and that engagement with the technology to elevate that value proposition. So it may well be that you’ve got, as we were talking about, product and maybe even research, people who are nominally owners of the lower planes on the stack who don’t have a strong point of view, who don’t have, you know, a facility with the technology or an ability to wrangle it toward those objectives. If you can step into that void, if your people can do that better than their people can do that, you can make a play for a wider value proposition for your team and for design as a function. But you gotta master the prompt craft first. The Role of Power Peter: This is interesting. I’m glad we’re getting to prompts and, I suspected we would get there. This ties into something else that I don’t think you and I have discussed on the podcast, but have discussed outside of it, which is the three types of power. This is something that I was introduced to about a month and a half ago at the Advancing Research Conference in a talk given by Robert Fabricant. And it’s a model where within any group of people, but let’s think about it within organizations, there are three distinct types of power that show up in these organizations. What most people think of when they think of power is positional power, right? The senior most person in their ability to tell other people what to do. The second type of power that comes up is expertise power, that someone has special knowledge of a thing, and because of that, other people will listen to them because they don’t have that knowledge. So this person might not be particularly senior, but they’ve, to use the example you just shared, they’ve mastered prompt craft. They know prompts better than anybody else. The third type of power is relational power. and that’s how people, it’s gonna sound mercenary when I say it, use relationships to make those connections with others within the organization to then realize their power for getting things done, getting the things they want done. And what’s interesting is, as you’re talking to me about prompt craft, that suggests a kind of expertise power, right? I know how to wield this tool better than anyone else, and this tool is super important, and so you’re all gonna listen to me because of that. In these analyses of power, far and away, what is considered most important is relational power. Jesse: Right. Peter: What often comes out are people say, well, what about positional power where you can just tell people what to do? If you think about. how people in higher positions tend to wield their power, they rarely do it by fiat. Yes, in the public consciousness, that’s what we see. But look around, even if you are a design leader, you’re not just telling your team what to do. You’re inspiring them, you’re engaging them, you’re making them want to do that thing. Not because you told them to, but because even if you’re senior to them, you’re wielding relational power to bring them along. Jesse: Yes. Peter: And so I, find myself getting maybe a little stuck on this idea of the person who controls the prompt controls the product, because that is this demonstration of expertise power, which UXers often fall back on as why they should be listened to, because they’ve done the research, they’ve talked to the users, they’ve generated the insights. We’ve observed the tests. We know what is going to be the best experience, so we should be in charge. And that never works or rarely works. So there’s clearly some value in expertise power. It gives you your credibility that you’re someone to listen to and engage with, but it feels like there’s something missing in that equation that you’ve been shaping. Jesse: Yeah. Well, so two things come to mind for me around this. First of all, I definitely do not mean to leave relational power out of the equation. You’re not gonna get anything done just by having. a phalanx of the most expert prompt crafters in the room. You get your hundred monkeys in there, and demanding that you be handed the authority over the entire product. But the other part of it that I think makes this craft expertise different from other craft expertises, is that it is manifestly an accelerant for creative processes, for product development processes for product delivery processes, where your expertise doesn’t just make you an expert. It makes you the person who can deliver a better thing faster. And so in these areas where, again, if there is a power void in the organization where somebody else hasn’t figured out how to close the gap around, let’s say, using AI to create really robust PRDs, if you’re able to take the junk that comes outta your PMs and turn it into really robust PRDs, you become the center of that expertise. You become the center of that influence, if you’ve mastered the technology that can bridge those gaps for the organization. I’m not saying that that doesn’t come with a lot of political scaffolding to create that opportunity for the team. So the leader has still got to be engaging with and negotiating with all of their cross-functional partners, all of their executive stakeholders, to be able to make the case for why we should do things following all of this stuff that their team is producing with AI support. But if they are able to do that, it starts to create a leverage point for more human-centered influence in product development. And so that’s, I think, the really interesting opportunity. Peter: In your talk, you mentioned that you created the elements of user experience diagram because no one knew why you were there, like, why you were in the room. Why would I work with this information architect slash user experience person… Jesse: He doesn’t even draw. Why is he here? Peter: Yeah, how are you helping us develop products? And the diagram was a means to answer at least parts of that question. And so thus people knew, to bring you into the conversation. Jesse: Right. Peter: And that still feels in many ways, like, the circumstance today, like, UX is not eagerly sought after. There might have been a period where it was, but even at its most eagerly sought after, it was still relatively minor. Jesse: Mm-hmm. Peter: People recognize its value, people understand its importance, et cetera. Another way to say it is there was never a UX gold rush. There’s never been a design gold rush. Jesse: Right. Peter: There’s an AI gold rush going on right now. Jesse: Yeah. Peter: And, there was something about when you were talking about the elements of, user experience as, this thing you needed to bring people along who could barely be bothered to understand why you were in the room. And now with AI you have to kind of beat them away, and many of them don’t even really wanna understand it, right? They just want to do it. It’s, I gotta get on the AI thing. There’s something about this dynamic between UX still trying to pull people in, and AI being this gravity well. AI in 2025 is like The Web in 1997 Jesse: Right. Well, so you may recall from our early years in this industry in the late 1990s, this brand new technology called the World Wide Web came along, and it was gonna transform everything, and they were wiring everything to be webby in one way or another. And nobody really knew why. Everybody just knew it was important and many of those things did not work, right? Many of the projects and experiments and attempts to integrate web technology into enterprises around, you know, in that sort of 1995 to 2005 kind of timeframe, just plain didn’t work because they were bad ideas. We are in the bad ideas phase of this technology right now for sure. I feel that what UX design was able to do for the web 20 years ago was provide some filters, provide some frameworks, provide some ways of thinking about these challenges that helped people separate good ideas from bad ideas. And I think that there’s a similar role for design to play now, in continuing to bring the human expertise to separate good uses of the technology from bad uses of the technology. You know when we talk about use of research, one of the big things that comes up with AI is the concept of synthetic users. The idea of doing user research by basically asking LLMs to pretend to be users. This is a bad idea. This is not a good use of the technology. It is not a substitute for actual data. Again, if you want to do some analysis down there at the bottom of the stack, then you’re gonna get some high value use cases. So separating the high value use cases from the low value use cases is part of the work that has to happen here. And I think that work is mostly going to fall, honestly, on design leaders even more than some of their cross-functional partners because, as you pointed out, the territory of design is so vague that if your goal is to drive human-centered process, drive human-centered outcomes, you might need to be piecing together a much more diverse portfolio of AI support tools than somebody whose narrow focus is just, get the code out faster, as might be the case with your engineering partner. Earn Trust First Peter: This is putting me in mind…. our conversation with Amy Lokey, Chief Experience Officer at ServiceNow, where, as she told it, her team has for a couple years now, really been at the vanguard internally within ServiceNow in figuring out how to best take advantage of AI tooling and AI opportunities, largely in service of creating highly usable and effective experiences, right? They’re kind of the most boring of enterprise software, and I mean that with love, but very, very pragmatic enterprise software. It’s a lot about data-driven or data experiences. Lots of cutting and pasting from one thing into another thing, et cetera. And recognizing that AI can play a role in automating a lot of this labor. And the value that they were able to articulate, that she was able to articulate from a user experience standpoint, was kind of classic 1994-era cost-justifying usability of time on task and how long it took people to do a thing. And what was interesting about her story, I think in this regard… One, she and her team, she had the credibility such that others were listening to her, and that credibility had been built up over time by demonstrating that value proposition such that when she steps up to help the company figure out how to make the best use of this technology, people aren’t looking at her like, but you’re just the box-drawer, what do you know about AI? But instead, oh, your prior work in helping us adopt the System Usability Score allowed us to see how, when we improved System Usability Score, we improved customer outcomes, which led to greater customer satisfaction on various metrics that we track, led to greater retention and, you know, business success. So if, you’re coming up and saying, Hey, let’s let my team get out in front of this AI thing, we’re gonna listen to you because we know that you drive value. Jesse: Right. Peter: I think for me, I guess a lot of it is this functional concern. If you’re feeling fear as a design leader about AI, the solution isn’t to AI at it more. The solution is to identify how you can raise the level of trust that others have with you in your organization, such that when you now want to engage with AI, they will listen to you. Jesse: Yeah. Yeah. I think that AI is similar to UX in this regard, in that what it really has organizationally is a multiplier effect, but that multiplier effect depends on what’s already there to multiply. So, if you’ve already built the bridges, if you’ve already gained the trust, if you’ve already built the value proposition, AI will let you activate and multiply that value proposition. If you haven’t already done that, if you’re dealing with a pretty scant value proposition, you’re not going to be able to multiply that very much with AI. So I think you’re absolutely right. The political groundwork has to be there. The operational groundwork has to be there. The cross-functional trust has to be there. The team engagement and commitment has to be there. You know, there’s a lot of resistance on the part of design teams to engaging with these tools for the fear that that is going to take something away from them. It does absolutely depend on how the organization is approaching it, and if you are approaching it with thoughtfulness and sensitivity to where that multiplier effect can be applied, then you’re going to reap that effect more quickly. And if you’re just throwing stuff against the wall, you know, the spaghetti phase of AI development, trying to see what sticks, then yeah, things are gonna get messy. So I think it is about being strategic. It’s about leaders being strategic about the value propositions of their teams. It’s about leaders being strategic about where that value proposition intersects with the larger ecosystem that they’re a part of, and where there is an opportunity to amplify that existing value proposition or build upon it. Peter: Right, right. And I guess one of the things that we’ve talked about in the past is maturity, organizational maturity, design maturity. And one of the risks that many design leaders unknowingly kind of engage in is that, when it comes to design maturity, they are often way more mature than the organization that they’re part of. Jesse: Yes. Peter: And they tried to show up as this very mature person and the organization’s not ready for them. This is something going back, when we spoke with Jehad Affoneh he talked about how he’d had jobs in the past where he couldn’t talk impact because the people around him wouldn’t know what do with an impact story. He had to talk about internal collaboration, ’cause that’s what they valued at that organization, was, did other teams like working with his team? And so I guess on that note, in thinking about accelerants, about this situation, right? The risk here is that design leaders embrace AI in a way that misses, is not aligned with, is not able to be taken up by the organization that they’re in. Right. It might be amazing. It might be, something that could very likely drive tons of value for this organization, but this organization is just not ready for it. And so it frankly gonna be wasted time and effort. And so design leaders needing to figure out where to pitch themselves, such that the AI- driven interventions that they are proposing are ones that can be taken up. And, when you meet your broader organization where they’re at, not where you are at, but where they’re at, click in with that and then over time bring the people around you along. Jesse: Right. So, it’s about understanding the expectations being placed upon design as a function. It’s about being clear on what you see as your own value proposition, and the difference between those things and creating the space, if necessary, to expand how that value proposition is perceived by the organization or how that mandate is construed by the organization, yeah. Practical Tactical Peter: Let’s get a little practical, tactical. Jesse: Yeah. Sure. Peter: You talk about prompt craft and… Jesse: mm-hmm. Peter: …the person who controls the prompt controls the product. What is your understanding of the mechanism, of the process, by which that might actually happen? If you were to coach somebody, an interested design leader around getting control of that prompt, and then driving the direction of the product towards these human-centered ends, what would you coach them to do? Jesse: Right. The first part is about just finding your opportunity. Finding the place where you can accelerate some part of the value that your team is there to create. So from organization to organization that might vary. Identifying the use cases within your workflow, your broader workflow, not just your design workflow, but the broader workflow of everything that you do together as a team to bring a digital product to market. And looking at that through the lens of acceleration, and honestly, the lens of human expertise and figuring out where the human expertise is most valuable and preserving that, so that what you’ve got is AI not supplanting human expertise, but augmenting human expertise. Often in digital product development there are these steps of translation. Translation of a strategy into requirements, translation of requirements into design specs, translation of design specs into actual design artifacts, translation of design artifacts into production code. Wherever you’ve got these stages of translation, those are places where the AI is gonna be a super valuable sort of an accelerant there. So in different organizations, there are gonna be different specific use cases within their workflows based on, again, what the team’s mandate is, as well as what the capabilities are that the team brings to bear. But ideally what you’re gonna do is you’re gonna get your most nimble, abstract thinkers, and you’re gonna get your best writers together, and you’re gonna talk about how we use language to define what we do. And start to develop shared language, common vocabulary, controlled vocabulary that enables you to have a shared knowledge base of repeatable stuff that works. You know from the work that you’ve seen me do with the prompt craft that I’ve been able to develop some highly reliable, repeatable tools for myself in supporting some of the work that I do. I can see that being scalable beyond an individual to an entire team, where you are collaborating on a knowledge base of reliable language, reliable, literally grammatical structures, that people can take and adapt and reapply in new contexts to create new solutions. And so it’s that shared understanding that ends up being really the collective source of value that a team ultimately ends up developing through this work. Peter: Shared understanding of what, and when you say team, which team? Jesse: I think you can define the boundaries of a team as broadly as you want to invite people into your prompting circle, and shared understanding of what creates consistent results. So this is the big challenge with these technologies, is that by their nature they are probabilistic. We want them to be a little bit inventive and be a little bit creative and come up with things that we don’t expect. The trouble is that sometimes we really need to control how much the machine is giving us things that we don’t expect, and so the ability for the team collectively to understand, here’s how we constrain the framing of a problem so as to produce a consistent result, ends up being the shared craft of the team itself. Peter: Apart from accelerating, and maybe automating, these interpretive breakpoints in the process, how do you imagine AI tools changing how we develop products? You know, we’ve got some fairly well worn, at least digital product design processes, not that everybody follows them. Are we just doing our process a little better, a little faster, or do you foresee real shifts in how we work? For example, with the rise of design systems, some people thought that, oh, we should just start with high fidelity comps in our design process. Now, I actually think most of the time that’s a bad idea. But, you know, an argument can be made. And so like what is being enabled that might shift the order of things, or the responsibility of things within a product development process? Jesse: So I think it does depend on where you are in your product development process. Early stages, AI is gonna be great for rapid prototyping, right? We’ve already seen so many examples of this where, there’s enough in the training data sets out there that if you sketch out a general sense of the functionality that you’re looking for, it can create something that looks like it does that thing. It won’t actually do that thing, it’ll just be a prototype, but it’ll be a pretty good prototype and maybe even a testable prototype with some additional layers of prompt craft behind it. You could probably create some pretty robust, fully instrumented prototypes of different product features and functionality and put out into the world. Once you get into later stages of development, I think that it becomes more about refinement and alignment, making sure that you are integrating features and functionality in consistent ways. In the talk, I talk about the prospect of human and machine readable documentation, the idea of creating product documentation that a person could read and understand what you’re doing together, and a machine could read and actually be able to take action on because it would have a fully formed understanding of what you were trying to create. I can see organizations moving toward that as a means of activating this kind of potential. You know, you touched on design systems. I think this is one of the huge things where, as I see it, it doesn’t make sense to me for design systems not to have an LLM interface. To my mind, the future of the design system is that it’s a robot that you talk to, that you feed it requirements and it matches those requirements with the system that it’s learned and generates product for you, right? The idea that humans would continue to kind of like spelunk into design system documentation in order to cobble together bits and pieces of UI kind of doesn’t make any sense anymore in that world to me. The Importance of Discernment Peter: One of the things you mentioned in your talk that’s related to this is how LLMs and any tool built on LLMs will kind of regress to mediocrity. Jesse: Yes. Mm-hmm. Peter: And the role of the human is to help get the solutions past mediocrity. Jesse: Right. Peter: Right. And so something I’ve been hearing about the role of not just designers, but anyone involved in product development, but primarily, say, designers and product managers, or at least people doing the work, there’s gonna be perhaps even greater importance in that idea of discernment. Jesse: Mm-hmm. Peter: Taste as it’s sometimes called. Jesse: Mm-hmm. Peter: Talk a little bit about that, and what the implications are, that it’s less about just turning the crank and getting something out the other end, but this application of discernment. Jesse: Yeah. yeah. So there was a slide in the talk that just says B-Y-O-B-S-D. Right? Bring your own bullshit detector, because the AI won’t be that for you. You have to be the one who knows more. So if you are working with the AI in a space that you are unfamiliar with, it is your responsibility to know more than the AI does, in order to be able to know when it’s feeding you something valid and when it’s not. And so maybe that’s about choosing your use cases, and maybe that’s about developing more robust validation processes around the output that you get. But what we see over and over again, is where people go wrong with this technology, is when you tried to design a submarine, and you knew nothing about fluid dynamics and you knew nothing about, you know, the structural factors involved in submarine design. And so it gave you something that looked like a submarine but didn’t function like a submarine and, surprise, you drowned, right? So this is the kind of thing that we’re seeing out there. Whereas, if someone with that taste, with that discernment, with that expertise, is able to leverage the tool and screen what comes out of the tool and say, this is valid, this is not valid, I’m gonna pay attention to this. I’m not gonna pay attention to that, that’s where you get the multiplier effect. But what gets multiplied is human expertise. Human capability. Peter: And that leads to something that I wrote just this past weekend. I was trying to figure out what I wanted to write for my newsletter, and I ended up writing about something that you and I had spoken about a few days prior, which is the definition of skills when it comes to design. So in my org design work, particularly when I create career frameworks for design organizations, at the heart of those career frameworks is a taxonomy of skills, interaction design, visual design, information architecture, et cetera. And I looked at my skill rubrics to try to get a sense of, what does AI do to these definitions of skills? What does it mean to be an interaction designer in an AI world? And as I looked at my rubric, I pleasantly realized that rubric as I had defined, it was already tool agnostic. Jesse: Mm-hmm. Peter: It didn’t say anything about OmniGraffle, Vizio, Figma, that’s not what the skill is. The skill of interaction design is, are you able to design a system that allows people to interact with the system to accomplish their goals… Jesse: mm-hmm. Peter: …probably feel some sense of satisfaction, maybe even delight in doing so, and that is tool agnostic. Humans have been designing all kinds of stuff that provide that kind of sense for decades, if not millennia. As you were talking about kind of enhancing these abilities though, or this concept of discernment, one of the challenges that comes with skills definitions is, skills are often about aptitude, but aptitude is different than taste. It’s hard to measure someone’s discernment ability. Jesse: Yes. Peter: I can say that, as you become more senior as an interaction designer, more advanced and developed as an interaction designer, you can design more and more kind of complicated and complex systems, wiring together different technological platforms, maybe online and offline platforms, like you can handle that complexity. That’s usually what you think of when it comes to scale. And that’s typically what the definition of the skill involves. And so I’m, thinking about how discernment’s gonna become way more important, right? So much of the value that people are currently delivering is their ability to, themselves, do the task… Jesse: mm-hmm. Peter: …just get it done. If we can delegate much of that “getting it done” to a tool such that our job is to now shape it, mold it as you, I think you said in the talk, think about it like, you’re throwing clay, right? You throw the clay on the wheel and now you’re, spinning it and you could make an ashtray like I’ve tried in the past, that looks like ass, or you can make something beautiful. For me, it raises this interesting question, which I don’t really grapple with, with my career frameworks and career architectures, which is assessing discernment ability, assessing taste, not that that’s not important, but it hasn’t been very important in UX design, right? In UX design, what’s been more important is the ability to create something that works, that’s usable. I think we’re gonna be shining lights on different parts of the work than maybe has been shining on it before. We were so focused on someone’s ability to grapple with tools, right? The number of resumes in the past that talked about, I can use Photoshop, or I can use Illustrator, and now I can use Figma. That’s all going away. And so what’s left as we consider candidates… Jesse: right. Peter: …as we build teams, as we think about the folks that we’re bringing together to do this work. Jesse: Yeah. So to my mind, it comes back to really what designers have always done, with an important twist to it, which is, can you visualize the experience that you can see someone having? How fully can you visualize that experience that someone is going to have with your product? How fully detailed is that vision? How many of the different parts of it can you really see in your head? And then having visualized that, can you conceptualize what it would take, architecturally, to create that as a digital product? Can you conceptualize the breakdown of screens and components and in some cases data structures and other things that are necessary in order to realize that vision? And then the third part, and this is where it gets tricky for a lot of designers, can you express that in language? Can you linearize that in a way that an LLM can ingest and interpret and make sense of and move toward, and then can you take that result and iterate upon that, and build upon what it creates? Peter: So I have three things that I wanna make sure we get to before we go. The first you talked about, can you express it in language and linearize it? I’m wondering when you say language, do you mean specifically words or could it be words and pictures? Jesse: It absolutely could be words and pictures, yes. Peter: Okay. Because, thinking of designers, right? Designers are visual people, but with pictures you can communicate multiple streams of information that the LLM could be taking in to better understand what it is that is being asked of it. Jesse: Yes. Yes. Multimodal is what they call it. Mm-hmm. Peter: And, I think when people think of prompts, they think of typing lots of words. And so it’ll be interesting to see how prompts evolve to accommodate multiple modalities of input. My second question, in the talk, you mentioned how, back in the day, 2004, 2005, you were giving a talk around, websites that evolve based on use, that can adapt to use. And this is something you and I have in common. This is something we both pursued a long time ago, and we’ve seen bits and pieces of it, right? If you look at any page on Amazon, that’s actually a demonstration of an emergent information architecture. The things that you are shown are based on prior behavior. But one of the things that people keep talking about, at least in the design space, is kind of emergent UIs and how the UI can shape itself to what you need, not the content that it’s giving, but literally the tooling, the interface elements that you’re exposed to. And I’m wondering, what do you think of that? Because this is something we’ve also been talking about for 25 years, and I keep not seeing. Jesse: Well, I’ve never been into this vision to begin with. There’s not a lot of precedent for humans preferring infinitely customizable tools. Humans would much rather use a larger set of more narrowly focused tools than one big, giant Swiss army knife with 1700 blades on it that’s gonna flip different blades out depending on the context. The various attempts at this, you know, just straight up haven’t worked. The closest thing that we’ve seen, I would say, have to do with more sort of task- or context-focused workspaces in UIs, where you can flip between modes, where I think about something like Photoshop, where you can just like really dive in and just do, like, pixel-level editing and like push all of the other stuff out of the way, and then when you’ve got to do some big kind of document stuff, you can bring the tools back in and do other kinds of things with it. So I don’t see AI creating infinitely variable tools because humans don’t like infinitely variable tools. Humans like tools that they can habituate to. And that’s not to say that there isn’t a place for AI in creating other kinds of dynamism within these environments, but I think that that probably is going a step too far for human brains. Peter: And one last thing kind of drafting on this, or maybe a different way at it, and something I’ve been suspecting, is how the development of these AI tools and the accessibility that they give so many people in now building their own software is… Are we going to see more and more products for, I don’t wanna say smaller and smaller audiences, but for a bunch of audiences, every, every audience, whatever it might be, can get its own product because with these tools, you can spin up something that really serves that particular segment. This might not be a tool that you know, gets to a billion dollars ARR, maybe it only gets to $50 million in ARR, but $50 million isn’t nothing. And are we gonna see more and more folks creating tools that generate a $100,000 to $10 million in revenue and be fine with that? And it’s not quite artisanal. I don’t know if you can call something that’s created with AI artisanal… Jesse: that’s an interesting question. Peter: …that’s a whole different conversation about craft and the role of craft in this. But, that mindset of smaller… I. Jesse: Yeah. Peter: … special purpose, you know, kind of Kevin Kelly’s “thousand true fans” oriented software, instead of what always feels like everybody around us is trying to do, which is create something that goes big. Jesse: Right? Yeah, I think so. I think there’s absolutely an opportunity there. Honestly, I think that’s a part of the larger thing that we’re likely to see, which, when I hear about vibe coding these days and people generating apps out of nothing, what they’re mostly making are tools for themselves to fill some gap, to fill some hole in their own workflow. And so I could definitely see a lot of creative professionals out there potentially creating tools to support their own workflow in different ways out of this technology. What it takes to scale that, to be a commercial product, to give it the stability and the security and the reliability necessary to be a thing that you could sell to somebody is maybe a different level that a lot of people aren’t gonna get to. But to make something that can run on your machine, that can help you quickly, you know, organize your task list or prioritize features or whatever the particular thing is, I can absolutely see a lot of that going on. Peter: So just last question for you. What are we not talking about? What have I not asked about? Or what are you not seeing in the discourse that you think is important and worth exploration? Language Matters Jesse: Hmm. It’s hard to think of what’s not in the discourse because there’s so much discourse. I’m gonna come back to the emphasis on language actually, because I think that there is not enough talk about the linguistic craft here, and the ways in which small changes in grammatical structures in word choice, in the way that you phrase and frame problems– because that’s what the work is, prompt work is problem framing for a machine to generate a response to the problem, and the more effectively you can use the mechanics of language to frame a problem in a way that the machine can understand, for you to have your own sort of theory of mind in the way that we use that phrase in philosophy and psychology to describe how we respond to the internal mental state of another entity in the world, the extent you can develop your own theory of mind about the AI and your own linguistic approach to engaging with it, that’s the skillset across the board, regardless of the problem that you’re trying to solve. Peter: Sounds good. Let’s end there. Jesse: Peter, thank you so much. This has been fun. The Elements of UX in the Age of AI is now available as a digital download. Get your copy today at JesseJamesGarrett.com/ai. Peter: Peter here. I’ve just launched two new formats of my Design Leadership Demystified Masterclass. You can take it either self-paced or with a cohort. For more information, visit petermerholz.com/masterclass. Jesse: For more Finding Our Way, visit findingourway.design for past episodes and transcripts. You can now follow Finding Our Way on LinkedIn as well. For more about your hosts, visit our websites, petermerholz.com and jessejamesgarrett.com. If you’re curious about working with me as your coach, book your free introductory session at JesseJamesGarrett. com slash free coaching. If you’ve found value in something you’ve heard here today, we hope you’ll pass this episode along to someone else who can use it. Thanks for everything you do for others, and thanks so much for listening.

  • Apr 13, 2025 · 53 min

    57: On Being a Chief Experience Officer (ft. Amy Lokey)

    Transcript Jesse: I’m Jesse James Garrett, Peter: and I’m Peter Merholz. Jesse: And we’re finding our way, Peter: Navigating the opportunities Jesse: and challenges Peter: of design and design leadership, Jesse: Welcome to the next phase. Joining us today to talk about what’s next for design is Amy Lokey, Chief Experience Officer for the enterprise software platform, ServiceNow. We’ll be talking about building a team that unifies product experience with customer experience, defining experience metrics that actually matter, investing in her own growth as a leader, and the real implications of AI for digital product design. Peter: Amy, thank you so much for joining us. Amy: You’re so welcome. I’m happy to be here. What does a Chief Experience Officer do? Peter: So, in the introduction that Jesse will have recorded before people hear us talk, he will mention that you are a CXO, Chief Experience Officer at ServiceNow. What is a Chief Experience Officer? Amy: Well, Chief Experience Officer, I’ll say first is importantly not a CEO, because you can only have one of those. So that’s why I’m A CXO. But I run product experience and also customer experience at ServiceNow. My wheelhouse, my background, is primarily in product user experience design. My team includes all of the functions that you would expect in user experience design team. So we have a large research organization. We have a large design organization. We have design operations and various operational functions that keep us kind of working together smoothly and things running. And then additionally, I have a large content team as well, too, that produces content for our technical documentation, best practices content, and is really the engine behind a lot of the content that helps our customers be successful with our products. And as part of that, we’re also responsible for a lot of the digital experiences that our customers use to be successful. So everything from… We have a learning experience where our customers and developers can get credentialed on ServiceNow. We have our customer support site. We have a product called Impact where our customers get kind of white glove customer support and work with squads of people that help them get up and running. So there’s a number of digital experiences. Those are just a few that my team also is responsible for. And so that’s the customer experience side of it. And then our product suite includes customer support software. So, there’s an intersection of our own product, is what we use for those experiences, so a lot of what we build to support our customers is the same thing that we’re building as a product that we sell to customers too. So there’s kind of an interplay in how all of that product experience design works and how we’re using it. Peter: And just to kind of establish some boundaries here, when you’re talking about customer experience, what is your relationship to marketing and kind of that front end of the funnel? And do you do any design or research work on that side? And then on the other side, more kind of typical customer service and even maybe even customer success. It sounds like those are outside your purview… Amy: Those are outside of my… yeah, yeah. From an organizational standpoint, so, we have a great CMO Colin, he leads our marketing organization. They do have a couple creative teams within that organization that work on various parts and pieces. And so our corporate website, for example, his team drives that. The digital experience, that we work really closely to bring those together in one unified navigation. So we want, from a brand and from a user experience design standpoint, we want it to be really seamless. So whether you’re looking on what might the corporate site, meaning, like, you’re looking at our products, you’re looking at our marketing communications, you’re evaluating the company, or you move into, Hey, I need to deploy this new thing that I got and I need some detailed information on that. You move more into the customer experience side of it. That’s my team. But we want those, you know, boundaries to be invisible to our customers. So we do have kind of an architecture that we work on from an information architecture standpoint, even like a universal login standpoint. So that’s, hopefully, not visible to customers, even though we have two different teams working on those parts. Peter: Sometimes customer experience means customer service. Do you have a relationship there? Amy: Absolutely, I don’t run customer service. So there’s another leader that runs customer service in terms of our support organization. But my team does work on the digital experience. So we design that entry point, right? And that’s, again, using our own product and then building it out to fit the needs of our particular customer service experience. So the digital experience we are responsible for, we support that. But the team of people that are behind that support system, like they’re managed by a different person. Yeah. Jesse: Within your team, you have an unusually broad mandate. In terms of bringing together both product experience and customer experience capabilities, and content as well. And I find myself curious about the organizational impetus to unify these functions. What’s the value of having a unified team with such a broad mandate that in most organizations is kept separate? Amy: Yeah. it’s not all organizations that are separate. I will say, like reflecting back at my time at Google, when I led user experience for G Suite, I was also responsible for the technical documentation. So, I think there are cases where you might have one org leader over both. The reason why I think it makes sense here is, the documentation of, like, how the product works is in many ways just this foundational piece that all of our other marketing and other content pieces are built from. We’re kind of the source of truth, and the people who write that content really sit side by side with the designers and the engineers building the products. So they are very much integrated into the product development process. And I think that’s an important part of why this all works. So, you know, my peer groups in my organization are, you know, product management and engineering, just to like very general terms, right? And then I have kind of the everything else bucket of user experience plus product, content and research and so on. But all the functions within my team are very, very close and tight with the product development process. So they’re working with product management, engineering. We are part of that release cycle. We’re part of, like, QE processes. So I think that’s why it all makes sense. It’s just fundamentally, I’m part of an R and D org and all of the experts within my team are part of that process that deploys software and then builds the things on top of it that help our customers be successful with that software. But we have to have that subject matter expertise of really understanding what it was designed to do and what it was built to do, and how it really, really works to be that source of truth. So we’re, you know, the customers that come to our documentation, they see it as very objective. It’s intentionally not positioned in a marketing type of framing. It is just factual because then it’s very, very trustworthy and seen as like this is the absolute source of truth of how something works. Peter: On your LinkedIn profile, when you define yourself as a CXO, you mentioned design and research, product content, design operations, but then there’s this phrase, information strategy. What is that? Amy: It’s how we deliver the right information to our customers. And so we are doing a lot of work to think about the best way to deliver vast amounts of information and what that strategy is. So it’s very much information architecture. We have a team internally, we call it Lexicon, which is just how we actually name our products, how they’re actually affiliated into our customer support experience, right? So if you file a ticket about our software, you’re gonna say what product you’re using, what functionality you’re using, that all has a data architecture in the backend that helps us tag it to particular products. So then we can kind of document the throughput of information back to the product team. So that information strategy and information architecture, it’s not only how we externally organize the content, it’s also how we internally tag it and map the data basically. So we have that throughput of information. The Holy Grail of Information Architecture Peter: This is like a holy grail. Well, so Jesse and I came up as information architects, and I think one of the challenges that I’ve seen UX teams face is, when they want to get to data models and content models, who owns those relationships with engineering, a lack of broad horizontal view of a company’s information standards and platforms and, and practices, and so it gets in the way when you’re trying to create, say, a unified navigation across a multi-product suite when every team has kind of done things their own way. And I guess usually this is solved by enterprise architecture or something, but it feels like your team has a bigger voice in this conversation, I guess recognizing there’s a user experience component to it, not just a technology platform kind of component. Amy: Completely. And, the team that does this work did actually have roots in engineering. So it started out as part of our engineering team. Hence, the affiliation to the data modeling and how we track that throughput of, you know, someone logs an issue in a customer support case, what part of the product is it actually affiliated to, and then can we even tie that to an epic and a record to show that we fixed the thing in the product, right. So, because a lot of that information architecture team had roots in engineering, it moved to my organization about a year or so ago. It did move because there is an implication on the user experience and there’s this relationship to our content and product content and so on. There was a natural time and place to move them to my team, but we have this great history and this great foundation of the data architecture underlying it. And then the other piece is just… ServiceNow is built as one unified platform with one data model. And so that’s just in our DNA here of like how we do things. So we continue to build on that. We have an internal tool like I just mentioned, where we can track our research insights and connect them into design records that connect into the epics and stories. And like I said, we could even connect that to user experience, customer service issues that we see. So the fact that we can have all of that data in one system of record is pretty powerful because we’re getting to a place now where we can track our user insights, we can tie them to design artifacts that show that we’re fixing the thing. We can then attach that to a PRD and then the, you know, epics and stories and we can show this connective tissue of, Hey, when we release the thing that solved that user insight, we actually saw a decrease in customer service issues related to that particular thing, which is pretty powerful to be able to draw that story together using data and show that that investment in user experience actually lowered the cost of customer support on the other end. Jesse: So with all of this interconnectivity between your group and its work and the work of all of these adjacent groups that you’re intertwined with, it actually gets me wondering about the discussions that go on at the top level of the organization and you know, you are a chief experience officer. A lot of organizations don’t even have a C-level person with your purview, and I’m curious how that changes things for you to be in a C-level role, speaking to experience issues. Being in the C-Suite Amy: Yeah, that’s a great question. I mean, I have to change altitudes quite a bit. I mean, I still, like I said, my roots are of being a product designer, so there’s nothing I love more than being in a design review, looking at the you know, product taking shape, giving feedback, working with the team to ideate on things. Like, for me, that gives me energy. But I do spend a lot of time thinking about our broader experience strategy in the ecosystem of our product, right? Which is, we have an enterprise software product. We design out of the box software products, right, that we sell to customers, but they’re on a very configurable platform. So we also have to make sure that we’re continually training our customers and our implementation partners on how to use our best practices to design and build the right experiences on top of our product. So it’s sometimes, I joke, it’s like the movie Inception where you don’t know which level of the dream you’re in because there’s kind of the root of it, which are our components, and then we’ve got our out of the box products. And then on top of that, our customers might configure and extend them. They might theme them. And we have a partner ecosystem as well too. So the role that I play now is much more externally facing, much more customer facing and much more involved in our partner ecosystem and the enablement focus. It’s one thing to have a great internal product user experience team. A lot of my journey here has been growing and developing and maturing that. Now I need to mature the user experience practices outside of the walls of this company to make sure that our customers are successful with the product and have all the best tools, resources, and talent to build on our platform in a way that delivers the potential that it has to deliver a great user experience. So a lot of the work and the strategy that I do is focused on that outbound work to enable the ecosystem. And then secondly, of course, I spend probably the largest majority of my time at the executive level on our product and business strategy, right? And the focus that we have on experience there is all around the transformation with AI, generative AI, agent AI, and so on. And that’s gonna be a massive shift in how people interact with technology. So my team has to be ahead of that curve and also helping the executives understand where that’s going. So those are the two pieces that I would say are outside and beyond maybe the typical UX leaders remit. But that’s not to say I don’t love doing that core part of my job, which is helping shape the product design. Peter: You just said the trigger word, or trigger letters, of AI, and it sounds like so much of what we’re seeing when it comes to AI in user experiences is some kind of, not quite shovelware, but it’s just being kind of spaghettiware. They’re just throwing AI at you in hopes that they’ll find some application that sticks. And given what you’ve been saying and the connectivity that you referred to, right, and there’s like a, detailed understanding of how user experience connects with these other kind of aspects of the business and, how value is realized in the business, I’m assuming that you are approaching AI with a different kind of consideration, and I’m wondering, what role is your team playing in contributing to that product strategy around AI, distinct from, or in partnership with product management, engineering, I’m assuming the typical function, sales, since you’re an enterprise software firm, I’m sure they’re getting involved. Like, what is the chief experience officer’s team bringing to that conversation to ensure that it’s not spaghettiware AI, but, really things that your end users will find value in? Designing with, and for, AI Amy: I’d say there’s been multiple phases of this and it keeps evolving. But I think one of the most interesting phases was at the very beginning, right? So generative AI hit the market. Everyone’s trying to figure out what to do with it. And our research team played a really key role in looking at where we might find the most value and deliver the most value, and using a System Usability Score kind of usability testing methodology. And so, you know, like everybody else, we’re wondering, well, where is the most valuable place to insert this technology? Right? And for what, what user, what persona, and in what parts of our software? And then obviously you’re looking at the business value that that might deliver and how you might monetize it, but also how you communicate that value to the customer. And largely the benefit of this technology is all around productivity and time savings, right? So how do you save time? And fortunately for us, our software is very much productivity software that’s typically used at scale by teams of people doing pretty predictable and often repetitive tasks, right? And so our roots are all in like workflow and process automation and so on, where you can say, okay, given any enterprise or business, if they have a particular workflow, we can start to digitize that. We can start to automate it where possible. You can start to enable humans to be able to do more versus doing whatever that activity was before, right? So instead of copy-pasting data from one system to another, we can automate that, right? So they can do more intelligent work. So AI was like a perfect fit to what we already did, but we had to figure out like, where are we gonna invest? Because you can’t just put it everywhere. There’s a cost to that. And so we used research and data and analytics to say, okay, what kinds of activities are most repetitive and happening in at volume and at scale, you know, so they happen over and over again. So they’re fairly predictable. They happen at a lot of our customers and they’re happening at scale where many, many people, our hands have to touch that thing. And so it was just basically a simple equation where we could say, if we put AI in this particular place, then how much time does it save? So we used a usability assessment to say, how much time did it previously take someone to accomplish this? So say that’s summarizing a case or writing resolution notes when something’s been closed. If that previously took them an hour and you can summarize it in five seconds with generative AI and they can edit it and complete that task. Now in a number of minutes, you can multiply that time savings across how many people, how many times a day at what scale in our customers, and you can start to extrapolate true value. And that even helped us figure out, How do we price this? So, so we were really formative at the very beginning, just trying to figure out where would it have the most value, how do we articulate it to customers and how do we price it? And that was very much based in those roots of just a before and after picture of time on task. That was two years ago now, but it did help us invest in the right places. Now, you know, fast forward, we’re more strategic, too, in how we measure the quality of the output and the value before we take something to market. And that’s been a learning process as well, too, because as you’re working with LLMs and they have degrees of unpredictability and variability, we’ve had to work really closely with our QE team to come up with both automated and also observational ways of testing the value of what’s delivered. And that’s been an interesting challenge. And, have to do with the pace that’s needed as well too. Generally working with internal simulated datasets before it gets into the hands of your customers. So that’s still a work in progress and something that we’re evolving, but we’re getting to a place where we have a pretty clear metric-based evaluation, too, of assessing the quality of the product before it goes out in market. But that’s been a multi-pronged effort as well in terms of getting like data to work with and all that. Jesse: What do you think designers and design leaders often miss about AI and how it fits into everything these days? Amy: I think it just depends. I’d say like in the last year or two I’ve been able to participate in various like panels and discussions and summits about AI. And I think I’ve been lucky to be working so firsthand with it all along the way. And so I feel grateful that I am part of these meetings, whether they’re at the executive level or the team level to really understand from like our research scientists how things are working and evolving and our engineering team, how things are working and what we’re learning. I think the most important part for any designer now is to truly understand how the prompting work, how orchestration works, what the variability is, and to get ahead of the quality in a way that’s harder to do than ever before. Because I think what’s really tricky with AI is to get the quality right, and to really understand what the end user experience is gonna be before you ship it. And that I think is the new science and expertise that we’re all kinda still figuring out as we go along, because it evolves so quickly. So you’re designing for hypotheticals and you can’t predict the hypotheticals necessarily, so you have to find quick ways to assess and, modify and change. Wielding UX Metrics Peter: When you mention getting the quality right, and the quality of experience, and, earlier you’ve referred to some UX metrics. You’ve referred to some usability assessments that you all conducted. I’m actually curious of the story of UX metrics at ServiceNow. Maybe it’s at least since you’ve been there and, when you joined, was there some UX metrics in place that you were able to kind of start with and then build? Or is this something that you brought in, in terms of how UX metrics are used? Not just, it sounds like within your team, but how your team uses these metrics to communicate outside of UX or CX and like, what that journey of metrics… It’s literally probably the most common question I get from design leaders is how to measure, how to value, how to define quality. And it feels like you’ve got your hands around this a bit more than perhaps most do, so I’d be curious what that story is. Amy: Yeah, really proud of that. Thank you. And huge credit to the research team and their leadership on this. But I would say when I joined, our, our research culture at that time was much more on the foundational research side, which is great and super valuable. But at that point in ServiceNow’s growth, we were expanding into a lot of different products. So we’d started as kind of IT service delivery, and we were expanding into customer service. We were expanding into HR, we were expanding to all these different verticals throughout the business. So the research team, and rightfully so at that time, was very focused on foundational research. What product should we develop? What would be the right product market fit. Almost a little bit more like market research than product user experience research. So when I joined, I had been at Google when a similar methodology had been formed. I think it started within the YouTube team, and then kind of grew across Google. And now the name that they called is kind of escaping me, but it was based on something like called Toothbrush Journeys, which are like, you brush your teeth every day. So look at the most, oh, CUJs, Critical User Journeys is the acronym Google, I believe. So you look at the most critical user journeys that people take, and usually there’s data that you can look at in terms of what are people, where do they start, where do they end, what are they trying to do? And I remember when YouTube first started forming this approach, they were just looking at uploading a video, what does it take, right? And they assumed, of course people are using YouTube, they must be having no problems uploading videos. There’s actually all of this drop off happening where people could not figure out how to upload a video. And so that was just like a critical user journey for the product to be successful. So the methodology is simple. You just establish what those 10 to 20 activities are and you measure the usability of them. And that is based on that SUS score, right? Which is like time on task, I think, you know, level of correctness, in terms of do you get through it appropriately, do you make mistakes, do things break along the way, or do you do the task correctly? There’s some qualitative in that as well too. How do you feel about it? And so you’re looking at both like the success rate as well as the time on task and then how, you know, do people feel like it was a good experience? And so you can kind of triangulate all that together. So we based what we call internally here now, UX quality, on that same approach, right? So determine what the most important things are that you’re hoping people can accomplish with the product. What are those journeys? And then you measure how effective they are and how long it takes and then qualitative, how do they feel about it. So we’ve kind of expanded that system into a benchmarking study that we try to run at least semi-annually on a product. We do semi-annual big family releases. So ideally at least twice a year we’re kind of looking at, you know, a new version of the software and reassessing based on that same evaluation. And we’ve had products where we’ve been doing this now, I’d say, over about six or seven releases, and we’ve seen tremendous improvements. The score ends up netting out to a percentage score on a hundred percent scale. And I believe in the industry, 80% and above is typically a considered a consumer grade usability score, where people can generally get in there, they can use a product. They don’t need tutorials. They don’t need documentation. It’s approachable, and it’s usable and simple, and they can be successful with it. So in enterprise software, the scores are typically in the fifties and sixties, right? Like typically much harder to use, more complicated, not as easy. So in the products that we’ve been running this methodology on, and addressing the feedback, ’cause it delivers really clear actionable feedback, we’ve had products that have moved from the 50 percentile up to some of our products are scoring in the 95th percentile, which is incredible for enterprise software that’s quite complicated. So it’s just been a great tool in the toolbox and we’re actually now using these in our executive product reviews. So we do quarterly product reviews and now we’re bringing what we’re calling overall this UX health scorecard to the mix that includes this UX quality benchmarking where we can investigate, you know, is there a usability problem here at the product or is that fine, and actually there’s an adoption problem, where there’s something else working here that we could apply over there. So it’s been great to see that continue to get momentum here and continue to add value in how we look at our products objectively and make sure that we’re fundamentally delivering a product that people can use and enjoy using and they get value from. Jesse: What do you think are some of the larger cultural factors that support that work in being successful? Because, like, I hear from leaders that they all say, well, our executive leadership absolutely wants to be research driven, data driven until they get data that they don’t like. And then, the data goes out the window, the process goes out the window, and executive fiat takes over. And I’m curious about the decision making environment that enables this more, you know, rational decision making. When UX is aligned with corporate values Amy: I think what helps is this kind of data is what our customers value as well, too, right? So again, like the fundamental value of our software is to deliver on business and end user productivity, right? So the fact that we have a methodology that shows very concretely improvements in user productivity and using the software, there’s no argument there, right, because that’s what we’re committed to do for our customers. And we can also show our customers like, Hey, look at the improvements we’re making. You know, your users are gonna get through their work x amount of time faster because now all these hurdles are taken outta the way, or we can generate these things much faster for them. So I think it’s just so well aligned with the value of our product, how we sell it, how we talk about it, that there’s never been an argument against it. There’s just been a hunger for more. I think in the consumer world it might be different, right? Like I’ve worked in consumer products quite a bit as well too, and in those cases, you’re not necessarily creating product that helps people be more productive. A lot of times you’re creating product where you want people to spend more time. Jesse: Right, Peter: right, right. “Engagement.” Amy: And so very, very different very different motivations, very different design measurements, right? And so usability, it’s probably still important, especially when you’re looking at, can they sign up for it? Can I get them registered? Can they subscribe? Can they pay, put in their credit card information or whatever it is. So, however that business model thrives, typically those usability scores will be very important. But in other cases, I mean, YouTube went for a really long time where people had a really horrible time uploading videos. It didn’t matter ’cause some people were figuring it out some way or another, you know, they were getting their videos up there. And the product was successful, but it probably became a lot more successful when you kind of streamline that process. So I think it just depends, like, how the product business works, and can you align metrics that are both in good service of your end user, as well as that are helping demonstrate how you can deliver more business value. Peter: It sounds like your team has generated some of these various UX metrics, but they’re now being placed on product team dashboards. And I’m wondering, where accountability lies now, right? is your team primarily held accountable for this, or is there joint accountability? And then, how is accountability handled, particularly for your CX team? I’m curious if you are somehow expected to deliver a distinct kind of value within ServiceNow, or if it’s just broadly recognized that CX is valuable, like these other functions, and your contribution is not isolated necessarily. Amy: Yeah. I mean, I think in terms of accountability, it’s definitely a shared accountability. So when we present these metrics, even though my team is helping produce the studies and create the dashboard and create the measurements and all that, we are making a hundred percent sure that we’re not blindsiding anyone with that, right? Like, we don’t wanna go into an executive review and be like, ah, gotcha. See this thing’s in the red. What are you gonna do, right? so we’re very much in lockstep with our product and engineering leadership team. So everyone understands how the study was conducted. They understand the data, they trust it, but they also feel aligned on what they’re doing about it, right? And so that accountability is definitely shared. It’s not just on us to fix it. And there’s also times where you might say, Hey, it looks like this is actually in a pretty good state, so as a cross-functional leadership team, maybe we need to invest in something else, right? Like, so I think it’s also how you’re making your investment decisions in terms of what needs the most right now. And in some cases you might have a product that’s very new, and you really wanna get it adopted, you wanna get it out and, you know, getting traction. Well then probably a big investment in UX is really good. You might have another product that’s actually quite mature and successful, maybe there’s another area of the business that needs that investment. So I think it helps us make like more thoughtful decisions across the board about what to invest in. Peter: Is there accountability specific to your team or is accountability shared…? Amy: It’s shared. Yeah, it’s shared across the product team. Yeah, absolutely. How to know to grow Peter: How has your team known, for example, how to grow, you know, you have hundreds, if not close to a thousand people in your organization. That’s expensive. What is the investment calculus in growing your team as opposed to hiring another product manager, hiring another engineer? ‘Cause clearly your team’s delivering value, but what is that conversation in terms of, like, the money, the funding that you get to grow your team, versus maybe other places where that money could be spent? Amy: Yeah. I mean, every company has different funding models. It’s a cross-functional conversation, absolutely. But ultimately the way that ServiceNow works is there’s a GM that at the end of the day makes those calls, right? So, they will get investment, they can choose to invest in sales, they could invest in engineering, they could invest in QE, they could invest in product content, there’s many competing areas that you can invest in. We use a ratio based model to just have some form of a guideline of what a healthy team looks like. And then cross-functional leadership gets together and we have interlock meetings where we’re looking at what the investment plan is, making sure that we can deliver on that investment plan. Making sure even the quarterization looks good, right? Like, are you hiring the right people in the right order? You don’t necessarily wanna hire engineering first and research last, you know, so things like that. But it’s a cross-functional conversation, which is really healthy. And, I think it’s rare to find that kind of operational health in terms of how things are funded. But like I mentioned, there may be times as a leadership team where like, the number one thing we need is actually like translation services for this particular product, or it’s, we need more QE for this particular product. So I think we do a good job of putting on objective hats around, like, what will truly make this business successful, and making the right investment decisions. Not just fighting for, like, we need more design. You know, I don’t approach it in that, way, but ServiceNow has grown tremendously over the past few years. So the team has grown tremendously during that time. I do think it’s an interesting advent with AI coming into the mix a lot more. Like, I think we’re all looking at how do we adopt AI to increase efficiency and potentially decrease the need to continue to expand at the same rates, you know? So, I think that’ll be an interesting shift as well too, because we just wanna make sure that we’re enabling our teams that we have to be really, really successful. And continuing to add at the same rate may, like, probably is diminishing returns at a certain point once you get to a certain scale. Jesse: So if you’re not in there advocating for more design, more design, more design, what do you see it as your role to advocate for on behalf of your team? Amy: I’m not saying I don’t do that. There’s definitely times where I do that again, like we look at the makeup of the entire team and decide what we need, right? So there’s, plenty of times where we’re saying, Hey, we need more designers or more writers, or more researchers, and I, here’s, here’s what won’t happen if we can’t get those folks. So trust me, like I have to advocate, but I think that just the culture here is one where there’s also times where I’m like, you know what? Instead of research, really what we need is more QE because, we do these interlocks, we’re looking at the bigger picture. So I just think that is a great business practice so that you are looking at objectively how is the team shaping up and how is it growing together, and that you’ve got everything you need to make the entire business successful. And so having that visibility, I think is really great for the cross-functional leadership team as we do those interlocks, because then you can see the perspective of, okay, I understand we didn’t get a researcher this time, but I can now tell my team why, and that I understand that it was in service of a bigger picture need. Jesse: What do you think is it that makes those interlocks successful, as opposed to simply being the recurring, repeating the same argument every meeting between the same people over and over again, over the same things. Amy: Well, I think naturally we see people respond to those conversations, so, you know, maybe culturally that’s different at this company than others. But I think the transparency in having the conversation is the important part. And then I see people make accommodations, you know. So we have a GM and we’re like, Hey, we really do need a researcher for this, or we’re totally understaffed on this other thing. Like, generally they’ll do what they can do, you know? So I think just hearing that and actually trying to make adjustments based on those needs and feeling that there’s always this give and take and level of understanding to try to do the right thing is most important. Then it doesn’t devolve into just a battle. Jesse: Mm-hmm. Peter: When you’re saying GM, I’m assuming there are multiple GMs. You have different business units. But design or CX is centralized, it sounds like it’s organized to align with those business units. Amy: Correct. Centralized vs decentralized Peter: Um, You are getting to a size where, in many companies, there would be a discussion of decentralizing, and I actually see it in much smaller companies where when they go to a GM model, the designers report up through that GM. And I’m wondering if that conversation has taken place at ServiceNow. And what are the, considerations around when does it make sense to maybe no longer be centralized as a function… Amy: mm-hmm. Peter: And yeah, just how is that discussion going? if it’s even going at all? Or maybe you’ll say, no one said it. Amy: No one said it to me yet. I am very cognizant of that. I’m very cognizant of that. Peter: I mean, Google, Amy: Microsoft, Google, I think Salesforce, like most other companies, at a particular scale, you fork the teams. The reason why I don’t know if it’ll ever make sense at ServiceNow is again, it goes back to like our core, core value of our technology is it’s one platform, one data model, one architecture, one front end. So we’ve been able to hold that together and no other company has, right? If you look at Salesforce, they’re all separate clouds, right? If you look at Google, all those products are different data models, different front ends, different back ends. The data won’t talk to each other. And that’s problematic when you wanna create cohesive experiences. So, one of the reasons that I was drawn to ServiceNow is I was like, this is pretty unique. You know, like the front end component system truly powers every product. So do that, you have to have strong horizontal connectivity, right? And so I do believe that makes a lot of sense when it comes to our engineering and all of our EX. We are centralized under functional leaders. Our product management teams not quite as much, but again, they’re kind of oriented around big areas of the business. So my team does serve as that glue that holds a lot of it together and make sure that, you know, experiences are cohesive, we’re taking systematic approaches to things, and there’s a lot of leverage and efficiencies that come from that as well too. Could it be decentralized? I mean sure there’s, and never say never, right, but at this point I think there’s a lot of value in having it together. Jesse: Speaking of the value in having things together there are lots of design organizations that find themselves kind of caught between a value proposition that is very much oriented toward the delivery of great design work, right, and we’re gonna be an awesome design factory, versus a value proposition that is not as delivery oriented and is much more sort of forward looking and innovation or product strategy. Amy: Mm-hmm. Mm-hmm. Jesse: I wonder how you balance and reconcile those things across your teams as you are wielding this cross-functional influence. Amy: Yeah. So are you, talking about kind of like the dichotomy between like craft or design with a capital D in terms of like creating something that is so beautiful and amazing and gorgeous and all that versus product strategy and business value and like are we actually delivering the thing that’s driving the… yeah, you know, that’s a, good question. I would say on the spectrum of things, ServiceNow is probably a little bit more skewed toward driving business value, which is I think, the right thing for us. That being said, we’ve invested a lot on the aesthetics and are focusing a lot more on getting those details to a point of polish and beauty and, you know, brand finesse that we’re known just as much for that as we are for the foundational value that the product gives. But our roots are really in value, right? Like, so again, that ability to automate and streamline businesses and, you know, we have a product called process optimization, for example, where when you’ve digitize processes on our platform, we can show you exactly where there’s bottlenecks, where maybe like an approval process is slowing something down or a lack of some particular thing is, and then we can help you automate that piece or streamline it. So our software, like fundamentally helps businesses run more efficiently and effectively, which means better customer service, better employee engagement, better, you know, productivity with their products. So that is, I think, just core to what makes us successful. So I do think like the UX leaders on my team are very strategic, very much thinking about product strategy and influencing product strategy. But we are also getting like much and much better at the beautiful aesthetics of it too. We launched a horizon design system this past year and it’s just absolutely gorgeous cutting edge design. We published principles around designing ethical AI. We’ve published all of our accessibility approaches as well, too. So that work I think is very much in that category of a capital D where like, if you look at the motion and the interactions and the visual aesthetics and all of those things that I think designers just love, there’s a lot to be proud of there as well too. Peter: When you mentioned publishing ethical AI and your accessibility standards, is that, I’m assuming by publishing you mean make public, like we, any… Amy: Yeah. Yeah. They’re public. Peter: What was the motivation behind publishing that? Amy: Great question. I think it’s just kind of intrinsic to ServiceNow’s values. We knew that, obviously there’s a lot of nervousness and trepidation around AI, and we wanted our customers to feel really confident that we were doing this in the right way for people. And so even our marketing language anchors on that, which is you know, make AI work for people, right. Put AI to work for people. And so people is always part of the statement and everything that we’ve done in our user experience design is to make sure that there’s humans in the loop at any kind of important juncture. You know, we’ve launched Agentic AI. Now we make sure that Agentic AI can work on all of the kind of research functions, but if it comes to, you know, like read versus write, it can do all the read stuff, it can pull things together for you. It can tell you all the things that it has done. But when it comes to like write something, meaning make a change or click submit or take action on that information, there’s a human in the loop. So it’s important to us, ’cause it’s the right thing to do and it’s important to us ’cause it’s the right thing for business, right? We need our customers to know that we’ve done this in a responsible way. And the reason we publish them externally is it’s literally a guidebook for customers and product development teams to use to make sure that every step of the product development cycle, they’re asking the right questions. They have the right representation in the mix and their counteracting the bias and their thinking ahead around where things might hallucinate and how to continually make sure that there are the right guardrails and checks in place so that their business isn’t compromised, or high stakes things are not at risk, right? Because using AI in an enterprise context, and especially as we move into Agentic AI, you’ve got businesses with very, very high stakes things that could be at risk if you’re not handling it in a responsible way. So we have to be very, very transparent about that, to keep that trust with our customer and not lose it and make sure that they have full transparency into how our models are built, how we built our own software, and then we can guide them, too. It’s available on the Horizon website. So if you search for Horizon design system, those HCAI guidelines are all published there as well, too. And, you know, it’s, one part thought leadership as well too, right? Like ServiceNow, a big part of our brand evolution is that we’re now perceived at the forefront of AI and that’s been something we’ve worked very hard at the past couple years. So all of these things, both in what we’ve delivered and shipped within our product and the success our customers are seeing with it, as well as these publications are important part of that whole story. Amy’s journey Peter: I wanna go back to when you started at ServiceNow, which I think was about five years ago. Amy: Yep. Correct. Peter: You started as a simple VP and global head of Design. And I’m wondering, when you joined ServiceNow about five years ago, how much of the path that you were on, did you foresee, like, did you have an agenda? Amy: Such a good question. Peter: Did you have a sense of, you know, what the next three to five years would be? Or, and how much of it has been a response to how things have unfolded and how have you figured out when were appropriate points of growth to, you know, ’cause your mandate has expanded over time, like, given that growth that you’ve had in your role, how much of that was planned and how much of that was realized? How was it known that that was the right thing to do? Amy: So did I see this coming? I got an inclination that it might happen, but I was also skeptical. I am a, pretty healthy, you know, cautiously optimistic, somewhat skeptical type person by nature. So when I interviewed here, there were a number of things that drew me to the company. It was not necessarily this promise of, oh, the company is gonna scale tremendously and you’re gonna scale the team tremendously and your career might grow along with that. I joined here more because I really like the culture, I like the leadership team, and I saw a big opportunity with the product that I thought was really interesting. And so that’s what drew me here. And the culture was very much hungry and humble. And I like that because I worked at LinkedIn previously through kind of that formative growth time at LinkedIn and that was one of my favorite kind of experiences in my career. So I wanted that, again, I wanted to be part of a company that was still shaping where I could have influence, that was malleable and that was on a growth path because, you know, growing is fun. And I do like scaling UX practices and maturing teams and finding great talent and figuring out how to expand on product experiences. So, that part definitely drew me in. When I interviewed, I remember being asked like, well, can you scale a team? And I thought, well, sure, I can scale a team. And when I was at LinkedIn, I think I joined and there was like six people on the whole user experience team and it grew to like 120. I’m like, that’s pretty big, you know? I can scale. And I think here the team when I joined was probably over a hundred people, but under 200 maybe, let’s so call it 150. So I was kind of coming into a team that was equivalent to say the size of the LinkedIn user experience team or even the team at Google that worked on G Suite. So I thought, yeah, like it was already a pretty big team. Can I scale it bigger? Sure. Did I think it would scale to over a thousand people in five years? I wouldn’t have believed that at that point, if you would tell me, and I remember the person interviewing me kind of said, yeah, well if you look at the growth rate of the company and what we plan to do, like, and you extrapolate the growth of your team, you’ll be at like over a thousand people in five years. I remember being told that and I was like, nah. I was like, sure. I nodded. Oh, okay. Yeah, no problem. And I remember thinking in my head like, that’ll never happen. But here it did. So I mean, yes, was, I told that this could happen? Yes. Did I believe it a hundred percent? Not entirely, but but it’s tremendous that it did play out that way, and we’re continuing to grow and expand. And it’s been a huge privilege. And, actually some of the best advice I got on this came from a engineering leader I work with. We were having dinner recently and they’ve been here longer than me, and I said, well, what has it been like? You were here, like, really early days of the company. And now you know, you’re managing, I think he’s got like a, say a 4,000 person engineering team. It’s like, well, every year the team’s grown like 20 to 30%. So every year I think about how do I get 20 to 30% better at what I do? How do I become that much better as a leader? And I was like, oh, that is so just resonated with me. Like that’s what you have to do. You have to challenge yourself to grow, to meet the needs of your team and the business. And if you can’t grow at that same rate as you’re developing as a leader and someone who’s bringing strategic ideas to the table and making a difference, then probably you should bow out at a certain point and let someone else come in who can work at that scale, you know? So it is been a privilege, but it’s definitely kept me on my toes and challenged me tremendously to lead at this scale and to continue growing along with the team at that rate. Jesse: In what ways are you challenging yourself as a leader these days? Amy: Getting much more involved in the business side of the house is a continual area of growth and challenge for me. So whether that is getting involved in really tricky customer negotiations or escalations and helping turn things around in a positive way that’s been a real good area for me to get comfortable with so much more of kind of an outbound role than internally facing, you know, and I, as someone who started out as a designer who really just wanted to put headphones on and hang out behind my monitor and design things, like becoming more outbound facing and extroverted in those kinds of types of roles are definitely a growth opportunity. And then I think continuing to advocate for what my team needs. I mean, we talked about like, you know, needing to say, I need more designers. It’s kind of bigger than that now in terms of the story that I need to tell. And being also expected to deliver a future vision continually when technology is changing so fast and helping people understand how the ways that humans interact with technology will evolve and what it would be like two years from now, four years from now, that’s getting increasingly more challenging because of how quickly the technology is moving. But that’s a big part of the job and how I have to keep challenging myself too. Growing as a design leader Peter: I’m curious what the mechanisms have been for you to figure out the nature of your growth. As in, trial by fire, you’re just thrown into a customer facing conversation and you have to make it work? Or are you getting mentorship? Are you getting formal coaching? And not just with that, but generally, like what are the resources that you turn to, to help you as, you’re trying to figure out what’s the next 20%, to use that conversation you had with your engineering partner. Like, how are you figuring out what it means to be better? What are the resources you’re drawing from to unpack that? Because this all new to you. Amy: Yes. Yeah, no, every day is new in some ways. Lots of resources. So I definitely, I definitely don’t sit back and just expect it’s all to come, you know intrinsically. So obviously feedback. I do welcome and, you know, get feedback from various different avenues to figure out like, how am I showing up? How can I improve? What does my team need? What are their expectations? What are leadership’s expectations? So I do welcome that and focus on that, certainly as one avenue. I have absolutely engaged with professional coaching all along the way, so that’s really important for me too, in various formats, different people. And I’m actually working with a coach right now that coaches a bunch of professional athletes, and that’s been really interesting too, because I do find, especially in these outbound facing roles, representing the company on stage or going into a high stakes meeting, like it’s very much a performance athlete kind of role, right? Like you’re under pressure. And you’re getting evaluated continually. It’s competitive. And the psychology behind all of that is really important, right? Like what are the head games that you’re playing with yourself that might be setting you up for success or not. So that’s been really, really valuable recently. And then I’ve got, you know an advisory board and friend group of a lot of other you know, UX leaders, design leaders and so on, that I continually nurture those relationships and friendships and their incredible sounding boards. And you know frequently in these roles, you’re the only one in this role, right? When you get to a certain point where you kind of the head of a function, it gets lonely real quick because no one else does what you do. And if they do, they’re probably at a different company. So you can’t necessarily like, disclose everything, but you can certainly talk about the leadership challenges you’re facing or best practices you might be using or what you’ve tried, things like that. So that advisory group of, other professionals in this space is incredibly important for me to continually nurture and learn from. Jesse: Amy, what conversations are you most looking forward to as we move into this next phase for design? Amy: I think what will be interesting is I do think the ability to design things will continually get more democratized, right? Like I’m sure you’ve seen things around generative UI, right? So anyone could describe an interface and it could be produced. You don’t necessarily need to know the tools, right? The Figma or the Photoshops of the world. With that though becomes obviously a lot of room for error for those who maybe don’t have the same design principles or fundamentals or understanding or gut instincts, for maybe things to happen that are again, like not usable or not great product experiences. So. I do think it’ll be interesting to see, like, do our roles shift from being doers to being those who design the experiences that shape good experiences, right? Which is kind of like the role my team is in. We create building environments like developer tooling, and we have a product called UI Builder, right? Where it’s the place where you can build user interfaces on our product. So how do we build the right expertise into those products or into the models that are producing the generative UIs to still guide and deliver great experiences. If I put it into a metaphor of like an orchestra. You’re moving more and more people out of the roles of playing the instruments into being the orchestra conductors, but they have to know how to bring all those things together and make music. So how do you train someone about what good music is and how do you teach that? So I think that’s like probably where it’s headed, where we’re gonna have more and more people that ultimately become the creative directors, the art directors, and they might have an idea and a vision. They may not have the classical art and design training. So how can you train that on the fly or provide that right guardrails? Amy: And maybe that’s where design expertise sits in the future. Peter: Hmm. Amy: What do you guys think? Jesse: I love that vision. I think it speaks to an evolution of design’s value proposition that potentially is a leveling up. Peter: Well, it, starts to beg questions. I mean, that kind of orchestration or coordination type mindset is how product management is often categorized, as kind of the chief corraller of cats, depending on the organization, the people don’t report into the product manager, but the product manager has some decision-making authority, but they’re there to really try to get the most out of their team. And so it starts begging the question, well, where does design and user experience end and product management begin? I don’t know if you have thoughts on that. Amy: I would say I think there’s places where those lines are blurring more and more, maybe more so than you might say between UX and engineering. Although I think those lines will blur too. This tooling is getting so powerful that given it’s all conversationally based and we all have conversation, right? We all have the power of language. We can all describe things. That becomes, again, a very like democratizing skillset. And the artifact that gets created, whether it’s code, whether it’s UI, whether it’s a product requirement document, matters less now. You don’t necessarily need the skills to create the artifact, you just need the skills to describe what you want. It’s gonna turn us all more into those visionary roles where you have to understand what the need is. I think there’s still tons of need for research and psychology and understanding how to empower humans, but bridging that, how to empower humans with the technology. The pieces that are in the middle of that, I think are gonna kind of merge together a little bit more, and there’ll be less distinction over the subject matter expertise of each part of that development process. Jesse: Amy Lokey, thank you so much for being with us. Amy: You’re welcome. It was nice to be here. So great to chat with you both. Peter: This has been fantastic. Do you like to be found, and if so, where can people find you? Amy: You know, I have to say I’m not a prolific poster of things aside for LinkedIn is kind of the main place I go. I worked there for a number of years. I love the product. I think it still provides a lot of value. So I would say anyone wants to reach out to me. A message on LinkedIn is always welcome. I am not so much on the X type of platforms these days, so I think LinkedIn’s a a nice place to converse. So I’d say find me there. Jesse: Terrific. Thank you so much. For more Finding Our Way, visit findingourway. design for past episodes and transcripts. You can now follow Finding Our Way on LinkedIn as well. For more about your hosts, visit our websites, petermerholtz. com and jessejamesgarrett. com. Peter recently launched The Merholz Agenda, his semi weekly newsletter. Find it at buttondown.com slash petermerholz. And if you’re curious about working with me as your coach, book your free introductory session at JesseJamesGarrett. com slash free coaching. If you’ve found value in something you’ve heard here today, we hope you’ll pass this episode along to someone else who can use it. Thanks for everything you do for others, and thanks so much for listening.

  • Mar 23, 2025 · 57 min

    56: Design’s Role in the Evolution of Product Management (ft. Sara Beckman)

    Transcript Jesse: Hey everybody, it’s Jesse James Garrett here. I wanted to let you know before we get into the show, we’ve got a special event coming up this week on Friday, March 28th, we are celebrating the 25th anniversary of the elements of user experience with a live 90 minute virtual seminar at 8:00 AM Pacific, 11:00 AM Eastern. I will be talking about the elements of UX in the age of AI. We’ll be looking at the connections between the history of user experience design, and the future of artificial intelligence. You do not wanna miss it. Peter Merholz will be there conducting live q and a. So please join us on Friday, March 28th. Get your tickets now at jessejamesgarrett.com. Stay tuned for another special announcement at the end of this show, but now on with the show. I’m Jesse James Garrett, Peter: and I’m Peter Merholz. Jesse: And we’re finding our way, Peter: Navigating the opportunities Jesse: and challenges Peter: of design and design leadership, Jesse: Welcome to the next phase. Joining us today to talk about what’s next for design is Dr. Sara Beckman, Professor at Berkeley’s Haas School of Business and longtime observer and commentator of the dynamic between design and business. We’ll be talking more about the legacy and impact, for better or worse, of design thinking, how design leaders should talk about metrics and how they shouldn’t, and what she’s learning from educating the next generation of product managers. Peter: Hi, Sara. Thank you so much for joining us. Sara: It’s a pleasure to be here, Peter. Peter: To start off, while I’ve known you for over 20 years, our audience doesn’t. And so I’m curious how you introduce yourself these days. Sara: It’s always a good question. I’m on the faculty at the business school at UC Berkeley, where I have, for multiple decades now, been teaching topics in design, innovation, product development, product management et cetera. I kind of hang out between two worlds there, between the College of Engineering and the business school. I was involved in starting up the Jacobs Institute of Design Innovation. So a lot of focus, I guess, broadly speaking, on cross-disciplinary work in the university, particularly as it relates to design. The ability to create new stuff, I guess. The Intersection of Business and Design Peter: Excellent. I’m going to dive right in to something I was thinking about literally yesterday, where I was attending a session, it was a webinar given by a design leader talking about the intersection, wait for it, of business and design… Jesse: ooh, Peter: And how it’s important for designers to understand, and to be able to speak in terms of metrics and stuff like that. And as he was talking, I was reflecting on work we did together over 20 years ago. So for Adaptive Path, you were kind of an advisor when we did a report on, at the time we called it, like, the working title was The ROI of UX, the official publication title is Leveraging Business Value: How ROI Changes User Experience. And the question I have is, why is it 20 years later we’re having the same conversation about how you connect design and business? Why doesn’t it feel like it has progressed? , Sara: Well, can I say something maybe a little provocative and say, Peter: Yes! Sara: Design Thinking got in the way. Jesse: mm-hmm Sara: So, 20 years ago, we were talking about, I’m going to call it real design. So, whether it’s UX designers, industrial designers, graphic designers, there was work that they did that we were trying to put value on. We were trying to say, if I make this product more usable, I can sell more of it, for example. So how do I make a connection between the deep work that designers are trained to do in design school, and the outcomes I can achieve with a product or service in the marketplace? Design thinking came along, and, in my opinion, it trivialized the work of real designers, I’ll call them, and we said everybody can do design and we had all these things going on that we turned design into, frankly, to some extent, soundbites. Oh, go talk to a customer and then design something cool and new. Nothing wrong with going to go talk to a customer. We kind of skip over a lot in design thinking the idea of actually getting insights out of talking to real customers and then designing to those insights. I’m put in mind of Barry Katz’ book on the history of design in Silicon Valley and how it evolved. First, started at Hewlett Packard, where I happened to work way back when, as really usability or user interface, right, design. And then as we moved into wrapping services around things, as we moved into software being the core of the delivery of capability, we migrated what design did, but design thinking was a whole different thing. And so was looking through your recent interview with Roger Martin and, thinking about what is design thinking relative to what design was about. Sometimes they call them little d and big D design. That implies one is bigger, better than the other. But we used to do that in manufacturing. It was big M manufacturing, which we thought of as manufacturing strategy and sort of the wrapper that went around manufacturing. And I think that was different than the actual execution of manufacturing processes. Somehow de-linked with design thinking, sort of the big D design stuff, we de-linked it from the actual actions of real designers. And that’s part of why people like Lucy Kimball talk about designerly thinking, as opposed to design thinking, because design thinking was a broader mindset and it left behind some of the roll-up-your-sleeves, we have real work to do here, because it made it seem like I could just draw a journey map and then design something, or I could just brainstorm for a bit, diverge, converge, and come up with something. No design process is that easy, right? I mean, you both know this from… Jesse: Right. Yeah. Sara: And so we left all that behind. Well, what’s the ROI of design thinking? First of all, nobody even knew what it was, right. I mean, you look at the academic literature on design thinking. I always felt like this was a bit of a tautological. Oh, well, let me go study companies that say they do design thinking and then I’ll define design thinking and then sort of over time we defined this thing called design thinking, but then next thing you know, design thinking isn’t just design. Oh, it’s also teaming. Oh, so design thinking is going to resolve all the teaming challenges. Like we, it just kept getting bigger and bigger without an anchor around what is this thing. It became bigger and undefined, but we also lost track of… design thinking, which is different than the practice of design, is not the only way to frame and solve a problem. And Roger talked about, well, scientific method is another way to frame and solve problems. Critical thinking is another way to frame and solve problems. Total quality management or DMAIC or Six Sigma, whatever you wanted to package all that stuff in, that was another way to frame and solve problems. Systems thinking is another way to frame and solve problems. And the design thinking proponents came along and said, this is the way to frame and solve problems. And it became, therefore, a fad, right? Because, because you can’t say there’s only one way to frame and solve problems. This is one of my great frustrations, honestly. So that’s what led me to the model that I’ve been using almost 20 years now, which is this experiential learning based model that basically says problem framing and solving is a process of sense making, toggling between the concrete and the abstract world, observing and noticing, framing and reframing the problem, and solution making, agains toggling between concrete and abstract worlds. Sara: I have a great idea in my head. I go try it out. I can put all of those other problem framing and solving methods into that model, which then led me to say, well, then shouldn’t we be teaching students, at a generic level, the core capabilities of problem framing and solving, and then have them say, ah, this problem could use scientific method approaches. It’s hypothesis-driven, right? I observe customers or users and I create a hypothesis about a problem they have. And then I go test that hypothesis by playing around with different solutions and prototypes. Scientists observe nature, maybe. We observe people in the design world, but they’re observing something and then forming a question about how it could be different. So, Sal Khan, in his book, One World Schoolhouse, his last chapter says, What if the university were a place in Silicon Valley that companies threw problems into and kids solved them for four years? And it took me a while to really kind of digest that notion, but I think, and by the way, it doesn’t have to be in Silicon Valley, and it doesn’t have to be corporate problems, but a general notion that education would really be about iteratively framing and solving problems of different types of different magnitudes over time with different methodologies. I think of different mindsets, different skill sets, different tool sets, right, that students would then learn in this setting. A systems thinking mindset, skill set, tool set is a better way to tackle this problem than in this other situation over here, where scientific method might be more applicable set of mindset, skill sets, tool sets. Taking The Time to Get It Right Peter: So you’re laying out a robust, detailed, savvy framework for approaching, tackling problems. What I’m wondering is, I don’t think I have ever been exposed to a company that would engage in the kind of rigor that you are proposing as they work through their challenges, and so, what’s the misfit there, right? There’s a misfit, I mean, you’re a B school teacher, I know you do exec ed. So you’re talking to people, not just students who’ve not necessarily had real jobs before, but people who are in the working world who are trying to get better at it, you’re engaging with folks with real world challenges. Square this, you know, thousand points of light, very robust framing of all the ways an organization can consider how to best tackle the problem in front of them. One of the reasons I think design thinking became popular is, in part, because by underselling design, it could be done quickly. And these companies just want anything that can be done quickly. They don’t want to spend a lot of time thinking upfront. You might not be familiar with this. There’s this saying “big design upfront,” which is like a bad thing, right? You’re going to spend three months doing all this work and designing, and then we’re going to get to start building it. So square the rigor and robustness that you’re discussing with what we witness every day with companies who are barely able to tie their shoes, much less engage in any meaningful research to inform how they solve problems. Sara: Yeah. I mean, I think that’s that’s a fair judgment. I teach hundreds of product managers every year. So I watch a lot of this. Clearly time matters, but there’s a couple of things that I try to do here. One is, you know, I used to teach design for manufacturability forever ago, my industrial engineer side of me used to teach operations management, and we taught a case study about a disk drive company. These are commercial disk drives, right? So they’re very, very high volume, low cost product, right? And this company was working in a partnership with Japanese company that was doing the manufacturing. And the engineers at the Japanese company would say, We need you to properly spec this product. And the engineers in the U. S. company would say, We don’t have time to properly spec this product. And the Japanese engineers ultimately won. They won over the ongoing complaints on the part of the U. S. product development team who they said they just want us to be able to put the parts on the table and hit the table and the parts will jump together. Like that’s ridiculous. But in the end they spec’d this product and they were able to ramp to volume manufacturing in way less time, way faster ramp to very high quality levels, because they had done some amount of initial investment. The parallel I draw to that in the design and product management world is that having some degree of clarity around what problem you want to solve for the customer or user up front will buy you a whole bunch of time in the long run, because you won’t keep putting the wrong thing into the market. Now, I’m not suggesting that I sit around and look at my belly button all day to do that. That’s where the innovation cycle comes in, right? I talk to a few customers. I take a step back. I go from dance floor to balcony. I get in the balcony. I say, what problem do I think the customer’s trying to solve here? Then I say, well, if that’s the problem, here’s three ways I could solve it. And I take those three ways back out, and I find out they don’t really have that problem. So I pivot, right? Or alternatively, I could say, I observe three critical problems that the customer has. I’m going to then generate ideas for each of those three problems, take them out, and figure out the customer’s going to say, I want to take that one home. Then I know I’m solving a problem the customer cares about. So the whole notion of rapid cycle prototyping is super critical here. But to frame it in terms of, I’m not just rapid prototyping to create the best product, I’m rapid prototyping to make sure I’m solving a problem that someone cares about, and there’s huge value in that, right? Jesse: What I hear from many of the design leaders in my leadership coaching practice is that their leadership is on board with many of the ideas that you’re describing. They are on board with being customer centered, with really listening for the right signals and tuning the product to the market in these ways. They just don’t see design as necessarily a partner in making that happen. And I wonder about design’s value proposition as it relates to this value that you’re describing because, you know, as you mentioned, you teach product managers how to do product management. And there are many, many people who see all of these things that you’re describing as being fundamental to the product management role, much more than to the design role in the organization. And so I wonder your thoughts on design, where design plays in these spaces. Sara: So that’s where I have to go back to this question of so-called little d design, right? I mean, product managers are generally not experienced or not taught or trained in doing UX design, right? So who is their partner, to be able to say, put this kind of curve on the product and this will happen. This goes back then to Peter’s original question of, you know, back 20 years ago, we were trying to characterize those kinds of connections, not this meta design thinking thing, right. We could have a long talk about customer centricity and whether companies really are or whether it’s just a lot of words and right, so, there’s a whole problem in companies. The Folly of Net Promoter Score Sara: I use net promoter score as my sort of measure of that. It has nothing to do with customer satisfaction. In fact, there’s no correlation between customer satisfaction or increased profit and net promoter score for any number of reasons. First, it’s ill constructed from a statistical point of view. It randomly eliminates 2 of the measures. It’s not even a proper average. I look at mine, I go, it got better and I think I’m good, but I don’t know that my competitors is 2 points higher than mine. In which case, getting better wasn’t really relevant. Peter: I like how for you, net promoter score, what it indicates, isn’t customer satisfaction, but a company that is kind of foolishly trying to engage in the idea of customer satisfaction. Sara: I mean, they think it’s an appropriate proxy, right? And I think that’s, well, it’s not an appropriate proxy for really understanding, are my customers now able to achieve an outcome better than they could before? Now, you might have a proxy for that outcome, right? But I want to have a way to know, have I actually helped my customer execute the jobs to be done that I intended them to execute. As long as you have these broader metrics, it’s very hard to connect what a UX designer does, right? I mean, I think it was an Adaptive Path conference where I put a DuPont chart up there. This is very old stuff. DuPont charts. Accountants would know what a DuPont chart is. Like, It starts over here with profit, which is made up of revenue versus cost. Revenue is price versus volume. So it basically backs all the way through financial metrics. And I put that out there and I said, “So where do designers affect this?” Jesse: Right. Sara: It could be at any of those levels. Remember Sam Lucente at Hewlett Packard. He had these multiple layers when he went in as the head of design. He said, well, it was clear that I had to do cost reduction stuff to prove my value. So I standardized the logos on all the pieces of equipment that HP sold at the time. Saved a boatload of money. Also, by the way, created sort of a standard brand identity in the marketplace. So he had, at one end, let me save cost, right, by good design, and the other end, he was working on revenue growth opportunities, right? If I can identify an interesting new need in the marketplace, then I’ll be able to grow revenue. Connecting Design to Business Value Sara: So to me, we have opportunities to make very explicit connections between what designers are doing. We had a discussion about the DuPont chart. And I was trying to get the designers in the room to think about the CMO, the chief marketing officer as their customer. And I said, what outcomes is the CMO trying to achieve and how are you going to connect the design you’ve made over here to helping them achieve those outcomes? And it was really hard to get them to do that. I can’t remember exactly the details now or I would tell the whole story, but, in effect the person said, yeah, but it’s Claudia Kotchka’s, you know, put a gold rim around the top of a face cream so I can put it in CVS or Walgreens and have it look more upscale, and everything, there. And the executive saying that cost two cents per jar, take it off. And her having to say, but then it won’t say that it’s… Peter: Premium. Sara: Premium, right? Jesse: Right. So, in some ways what you’re talking about are really qualitative outcomes that design creates in this increasingly, as Roger pointed out, as has frequently been a theme on this show, in an increasingly metrics-driven world. And I wonder what you see as design’s relationship to business metrics. Get Your Proxy Metrics Right Sara: So when we teach product managers, we try to have conversations about this. There’s a great case study, and this is kind of the classic case of Kodak. What was Kodak selling? Memories, and they knew that. What was their proxy measure for you to capture and share memories? Two core jobs to be done. Capture and share memories, right? Proxy measure, how much film and paper do we sell? So what happened to Kodak? They got too hung up on film and paper sales as the proxy metric, and when we shifted to digital, they didn’t shift their internal proxy metrics. They knew they were in the business of memories, right? They invented one of the first, if not the first, digital camera. they were on top of all these things, but when it came to execute, the metrics they had in place, they needed to be changed as a proxy for that. So mostly we use proxies, right? Like monthly average users. Well, you know, monthly average users is just a number that customers don’t care about. What did they care about: learning from the site, or getting a job, or whatever it is. So, how do I get proxy metrics? I’ve always hated sort of measuring everything myself, like it frustrated me when I worked in business, so I’m not not here to say, I think you have to be able to measure everything. But if you’re going to measure, then for heaven’s sakes, don’t use net promoter score, at least try to use something that gives you some information about the customers and whether they’re achieving something they want to achieve. And I think the Kodak story is a great example of knowing what you want to help, but not migrating or connecting metrics over time to the outcome. Peter: So you say, don’t use net promoter score. I agree. Many UX types agree. Jesse: I also agree. Peter: A few weeks ago a head of design shared with me that their boss, in an effort to give design some accountability, “We’re going to have you held accountable for net promoter score.” And this design leader was uncomfortable about that. I’m wondering what you would counsel someone, ’cause I can point to dozens of design leaders who are in a similar situation, what have you seen, if anything, that works to start changing that conversation? Shifting it, when you are also not the one in power, right? This is your boss saying this. Jesse: Right. Peter: You might be new. This person’s relatively new in the organization, right? Like, so they’re still earning trust, building credibility, like, there’s some things working against them to be able to just say, no, that’s not the right way to do it. It should be X. Any thoughts on how you turn that ship, to start advocating for what you do believe is right? Sara: Yeah. Many years ago when I worked at Hewlett Packard, HP at the time was divisionalized, had 50 or 60 manufacturing sites globally, which was a lot, and they were all very small, and so we were trying to provide some evidence that consolidation of those sites might be useful, so we made a cost volume curve. And where was HP? Above the curve, on the steep portion of the curve. So we start showing this to people and we say, hmm, opportunity, right? Increase volume, reduce costs. Oh, no, we do better quality work than that. Okay, how many quality engineers would you like me to add to the curve? Jesse: Hmm. Sara: And it would move up, you know, a teeny, teeny, tiny amount and we’d go at it again. For a year, we had these conversations. Until one of the very senior, senior guys said, wait a second, how many engineers do we have working in each of those sites? I said, well, it’s like two per site. You’ve got a hundred across the company, but the two, whoa, if we put them all together, we’d have an awesome printed circuit board assembly site. Like, okay. So it took me a year to get there. Two morals of that story for this conversation. You’re not going to change the boss’s mind overnight. But you keep bringing this up. So there’s a whole bunch, there’s articles–the wallet allocation rule. There’s a whole bunch of articles out there, first of all. So I would start with, there’s evidence of the problems of using net promoter score, right? So I can put some of those out there. But probably more importantly, I would start trying to build up some understanding of how I can create a metric that connects more closely to what the customers and users are trying to achieve. So I would start thinking about, is it weekly active users in the example views, or is it weekly learning users? Ah, well then if it’s weekly learning, what do I actually watch people doing? Do they scroll more? Do they post more? What evidence would I have that they’re actually on the site learning something? So I would start to build up a conversation around what can we replace this with. If you’ve got to have a metric other than revenue, right? If you’ve got to have a metric, then what metric might I have that would allow me to connect to something that is the agenda that I think I have for helping customers and users. Jesse: And it takes time. So part of this is patience. I’m new here. I’m not going to walk into my boss’s office, although I’ve been known to do stuff like that, walk into my boss’s office and say, you know, this is dumb. You should think differently. But, you know, building up a case. Maybe being able to collect some of that data, maybe talking to the data scientists and saying, if I wanted to construct a metric that evaluates memories, whether they’re shared and whether they’re captured, do you have data that could help me do that? So why don’t the designers make friends with the data scientists and say, you know, if this is something I would like to be able to evaluate, do you have a way to help me do that evaluation? So we begin to get little better integration. You talk about organizations basically falling in love with their proxies and becoming so attached to their quantitative measures that they forget what those quantitative measures were intended to stand for, which had to do with some sort of different kind of qualitative impact. Jesse: I work with lot of design leaders who are basically trying to break that spell of having fallen in love with those specific quantitative proxies. The challenge with that is, and I love your suggestion that like, don’t try to convince them to become a qualitatively driven organization, just give them different proxies, better proxies makes a lot of sense. The attachment that happens in these organizations is often connected to financial incentives. It’s often connected to power. And design leaders often find themselves literally the least powerful person in the room when having these conversations about how we measure the value of the work that we’re doing together. And I wonder about your perspective on the arguments that are going to hold water in a situation where you are the least powerful person in the room, arguing for everybody else in the room to change the way they measure their success. How do you do that? Find Your “Trojan Horse” Move Sara: It’s hard. There’s no… it goes back to my HP story, like, I couldn’t change the whole company. Jesse: Right. Sara: I could only change it one person, one division at a time. And so we used to talk a lot about, what’s our Trojan horse move, what’s our subliminal messaging, like how do we create shifts in thinking over time. And the kinds of things I use with product managers are, I can’t implement a big thing all at once. I have to often start small. So what if I open every meeting with a customer story? Oh, I was talking to a customer the other day. You know what they were doing with our product? What if every time somebody came to me with a feature they want me to build, I said, cool, happy to consider it, what’s the customer going to do with it? What problem are they going to solve with it? So there’s a whole lot of really simple little things, and design thinking did contribute a whole lot of these, but I can change my own behavior, and then what happens, you start to hear other people starting their meetings with customer stories, or you start to hear other people saying, but what problem is this solving. But we have, to your point, incredibly entrenched behaviors in organizations. And I’m going to take that all the way back to where we started this conversation, standardized testing and the way we structure our school systems has caused us to reward people for quickly having the answer to a question rather than saying, wait, is that the right question? Or rather than saying, is there more than one answer? We’ve got behaviors like that, that have been entrenched since middle school? Before? You’re not going to change those overnight, right? This is the whole thing I have about problem framing and solving, right? And, Roger sort of describes it as scientific method, analytical, but we’ve trained a generation of people and then we rewarded them for those behaviors. It’s not going to change if we’re just talking at this big level about everything. It’s going to change because we model behavior changes ourselves. So when I teach not just product managers, but executives, this is what I talk about. Say, you can’t ask the people in your organization to do ABC if you’re not acting that way yourself. But they don’t even know that they’re acting that way. So they need to be, in effect, called out on it in a nice way, right? So I would literally, at HP, my boss would do stuff in a meeting and I would walk up to him afterwards and I’d say, don’t ever say those words again, because here’s how they are heard. Don’t ask people to do X. Suggest that they do Y. Or, right, like I was trying to do literal behavior change work with him in order to get some of these changes in behavior, so it’s, you know, it takes systems thinking. It’s a big systems problem. This is not going to get undone overnight. I’m sure you’ve done this in your coaching. How many times do you have somebody, you know, you say, oh, well, you should be customer centric about that. And three seconds later, they’re telling you what feature they want to put in the product, Jesse: Right. Sara: And you go, what problem is that solving? And they’re like, Oh, it’s hard. It’s hard. Jesse: Yeah, so it’s interesting because it suggests there are several layers of the kind of culture change that’s really needed in organizations in order for design to genuinely deliver on its value proposition, because you’ve got to evolve the way that the culture engages with decision making. But you also have to evolve the way that the culture engages with problem framing and problem solving… On Being Customer-Centric Sara: And measuring itself. And, right? The reward systems. It all has to align around achieving… That’s why the customer centricity thing, there’s actually not as much academic literature on that as you might think. It’s kind of surprising. If you say, Oh, are you a customer centric CEO? Well, of course I am. I talk to customers all the time. Like about what? Oh, well, that do they like the curvature of this or did they like this feature? No, I don’t want you to talk to them about that. I want you to talk to them about their lives, about the problems they have about, right? We don’t have those kinds of conversations, but we think that because we shared a roadmap with the customer that we’re customer centric, right? It’s not. It’s not. But if you don’t get down to that level, and they’re just going to go, well, we are customer centric. And I work with some large companies where they’ll, “Oh, we’re customer centric.” I go, okay, write an interview guide to go learn something about your customer. And we’ll get specific about X kind of problem. And what do they write? “What’s the last product you bought from us? Did you like that product?” “What do you…” right? Like they’re not able to get into a mindset of learning, not selling. Of being present with a problem as opposed to with the solution, so it’s incredibly hard for them, but they think that because they’re talking, I mean, particularly in a complex B2B large technology kind of company, they are out talking to customers all the time, but they’re mostly talking about the features they’re developing. Not about the problems those features are aiming to solve. Peter: More proxies. Sara: Right. you know, to Jesse’s point, why is it so important that this change now? And you probably read Experience Economy… Jesse: mm-hmm. Sara: Pine and Gilmore stuff. Jesse: Mm-hmm. Sara: I really like the trajectory it lays out, which is to say, Commodities, the only differentiation is price, right? So coffee beans the value is can I get them at the lowest cost? Then I make goods, grind up the coffee beans, put them in a can. I’ve added some value to the end customer. Services, I’ll make the coffee for you and serve it to you at Denny’s. Now I’ve added more value to the customer. Staging customer experiences. Now I’m, you know, at the Starbucks level of coffee where it’s the third place, there’s more going on than the coffee. They’re now writing another book on guiding transformations. It used to be that most of the companies I taught were somewhere between goods and services. Now, most of them are trying to migrate to designing experiences. And very recently, people are starting to talk about guiding transformations. I cannot do experiences and transformations well, unless I truly understand what I’m trying to help my customers accomplish. Jesse: Mm. Sara: So, the trajectory we’re on, that trajectory is true. That increases differentiation and personalization, therefore increasing my opportunity to capture value, right? So there’s an economic return to increasing the value I provide to the customer. Then we have no choice but to go through the cultural shift that you’re suggesting, Jesse. And that’s kind of the broader argument that I’m trying to get people into, like, where do you want to be on this spectrum? You know, companies also talk about, well, hmm, sometimes we went to goods and then they got commoditized. So we went backwards. Oh, huh. I don’t know that I want to do that very often. Sometimes I might have to. But how do I always have my eye on the possibility that I might add additional value and differentiate in some way. Embracing AI Sara: Now, why is that being driven so fast? Because AI creates all this possibility to create, to stage experiences, to guide transformations. But if I’m looking at it totally internally, I’m just going, how do I get AI into my product? So what’s everybody flocking to these days? Courses on how to put AI into their product. Rather than asking the question, how do I augment my ability to stage customer experiences or guide transformations? AI will spit out a customer journey map for you, which, this is another place we talked earlier about, how do I get people to do this? I don’t have to spend time on this. It used to be I had to go interview a bunch of people. By the way, I’m not saying not to spend time with real customers. That’s a whole other conversation. But, but it used to be that I had to spend months to get an as is customer journey map, and now I can get one in less than a minute. Are they always right? Are they always complete? No, they’re not. But in my experience in the last year or two, they’re pretty good, and that means I’ve had a lot of people try out prompts to get a customer journey map, and they can get a pretty good starting point. Ah, if I can start there, now I’m playing a whole different game, because I don’t have to say, I don’t have time to blah, blah, blah, blah, right? I can start somewhere. I can get a list of jobs to be done. What’s the customer support engineer trying to get done when resolving a customer issue? Here’s all the personal jobs to be done. Here’s all the professional jobs to be done. Do I still have to go play with that and say which of those jobs to be done would I like to support? What does my product support now? What are my competitive products support? Yes. But now I can do it with, more real detail. Now, none of that is quantitative, right? You’re talking about a qualitative list of jobs to be done. I might try to do a quant evaluation, like how do I match up to my competitors on the ability to do those jobs for customers. That’s why I want a partnership with data science people. Now I’ve got to get creative. And how do I take that existing experience and make it a whole lot better? So you’ve also got a whole bunch of questions about what are the roles of designers in a world when some of the artifacts that they’ve created historically, I can create pretty quickly now a first draft of. But now, now you’re in a cycle. Now I can go in with a first draft, I can say, you don’t have to pay me for six months of work… Jesse: Well, there’s a catch in there though, right? Because the AI can make the journey map for you, but it can’t sell it to the executives for you. You’ve got to be the one to make the case and to frame the deliverable in some larger meaning, which comes back to this quant versus qual thing that we’ve been talking about. But it also comes back to the notion of culture change, and the notion of organizational evolution that is a part of this. It is very common for design leaders to see themselves as organizational changemakers, as champions of a different way of thinking about decisions, a different way of thinking about prioritization, a different way of thinking about how you go to market as a business. And you know, what I’m hearing reinforced in what you’re saying is that, like, you’ve got to really not just bring the data, but you’ve also got to bring the persuasion on a human level, to bring people around to this mindset as you describe it. The challenge that I hear from my clients is they feel like as design leaders, they are not sufficiently empowered to actually drive the mindset that is required to create design success. And again, coming back to the fact that you are not a design professor. You are teaching product managers. I find myself wondering about those design leaders who are asking, Am I even in the right place to create what I see myself creating in this organization as a design leader, or do I need to be somewhere else in order to actually accomplish these outcomes? Create Your Own Power Sara: Let me first say it is not just designers who say that. Product managers say that, you know, lots of people, so that’s not an uncommon concern. Part of the challenge we have is that the world is moving way faster, particularly since COVID, and we hit the knee of the technology change curve. The world has been upended. The people who are running the companies today have no experience in this new world. I would guess if you talk to some number of them, they’re terrified because… Jesse: hmm. Sara: …they don’t have the tools, the sense of what can happen. And so we’ve got real conflicts between the top of the organization and the people doing the work. And the people who are doing the work often know more, but are feeling disempowered and I think part of it is this challenge of things are moving so fast, you can kind of get it. Even at HP when things weren’t moving that fast, you know, those of us more junior grew up with more technology then the people running the company, and so for them to be making judgments, they actually didn’t have that empathy, if you will, for what was happening out in their customer’s world. So, so this kind of goes back to, create the power for yourself. I mean, no-, nobody’s going to come to you and say, I empower you to change how I think, right? It just isn’t that way. Now, you could be in an organization that you should leave. And I assume that you coaches help people figure that out. Like if you’re pushing rope uphill, you know, there’s a point at which, don’t do that anymore. But I ran the change management team at Hewlett Packard, right? Nobody said you’re empowered to help the company improve its teaming, change its product development process, improve supply chain management. I figured out that those were things that needed to happen, and went around and found places that would experiment with me. I don’t have to change the whole company at once. I just have to redesign one product, and show that redesigning one product increased acceptance, adoption, whatever it is, right. So change doesn’t have to be, oh, they don’t understand me. No, they’re probably not going to, until you find that– I’m gonna go back to my thing. I didn’t get that they cared a lot about consolidating engineers, not about consolidating production, right? Boom, I was telling the wrong story because I wasn’t listening to my senior management team. That’s the same thing at the Adaptive Path conference where, you know, we were having somebody pretend to be the CMO. The designers who were sitting in my group weren’t listening to what the CMO cared about and creating a connection, right? it also goes to the whole storytelling thing, right? We teach storytelling a lot in product management. Why? Because, as our storytelling faculty member says, when you open with data, people receive it with their dukes up. Where’d you get the data? How’d you analyze it? Why are you sure that’s the average? Start with the Story, Then the Data Sara: If you open with a story and then provide the data, it’s heard in a different way. Even in companies that have very data driven focus, and I think, increasingly, in the product management space, I was just with a bunch of them this morning on storytelling, and one of them said, when we have a product that’s languishing, I use storytelling to figure out whether I should just kill it or what I need to do to fix it. Because you can’t tell a good story if you don’t have a good story to tell. Peter: Hm. Sara: So it’s in the structuring of the story that I’m testing… “Once upon a time, there was a customer who really wanted to and could not do so because…” If I can’t tell a compelling, right, problem, then I don’t have something. So I would link these things together, right? Like, how do I bring the qualitative side? And I’ll come with data. “Once upon a time, there was a customer who really wanted to do this, couldn’t do so because, and by the way, there’s 400, 000 of those… Peter: right. Sara: in the United States alone.” Okay, now I’ve got my data. But you can’t expect it to happen overnight. I mean, that’s thing that I think is so… it just doesn’t, it just doesn’t. Peter: Right. Sara: So I’m a big “guide on the side” rather than “sage on the stage” as an educational concept. And so to do guide on the side work, you’re gonna have a classroom that has tables and chairs, not the amphitheater style, right? And so I used to go to these meetings about our new buildings and I’d be like, no, we’ve got to have flat classrooms. And it got to the point where I was in some meeting and it’s like 10 minutes into the meeting. So he goes, “Sara, you haven’t brought up the space problem yet.” So that’s what happens, right? Mean, to me, that’s what you have to sort of, with humor, be a bit of a pain in the neck, you know? Oh yeah, what problem is that solving? Oh yeah, what problem? Pretty soon you start to hear it back again and they’re not even attributing it to you, which is the other part. You can’t take credit for it, right? Because, you’re just trying to get them to understand something and eventually it’ll click and then they’ll say it in their own terms and you’ll hear it come back. You go, well, I’ve said that. That’s right. Peter: You’ve mentioned your work with product managers. Sounds like you’re teaching them working with maybe dozens, if not hundreds of them over the course of year. And I want to take advantage of your distinct kind of opportunity and perspective that that gives you, and I have a question which is, What are you hearing from them? What are the patterns you’re seeing in product management and with product managers? What are the things that are keeping them up at night or what stage are we at with product management? I’m, just kind of curious as you look at the world of product management from your point of view across dozens if not hundreds of people from a lot of different enterprises. What have you witnessed? What insights do you have that could be of interest to people who are working with product managers and who don’t necessarily understand the challenges that they’re facing? Sara: By the way, we have some number of designers who show up for the product management program. So it isn’t just product managers, we have fair number of technical or, engineering managers who show up as well. And I think it’s in part because they would like to understand a little bit better how business cases are being made for this. So, first, let me say, because I’ve always been in this boat as long as you’ve known me, or maybe even before, I’ve always taught human centered or customer centered development, right? That’s what we taught at Berkeley in the MBA programs. And that’s really how we anchor the product management program. So, yes, we teach segmentation, targeting, positioning, pricing strategy. But the Trojan horse, if you will, is it’s all customer centric. So the first thing I would say is that companies used to push back heavily on that, let’s say, 15, 20 years ago. A lot of the stuff you’re saying, Oh, no, we can’t do that. My boss would never let me do that, etc. There’s a lot less of that now. In fact, it’s pretty rare. I can credit design thinking with that, if you like, that there’s been enough conversation and agenda around some of these first principles of customer centric work, and adoption of things like rapid prototyping, although aside, we teach risky assumption testing rather than minimum viable product, because there are often assumptions you can test without a minimum viable product. So rapid prototyping has become minimum viable product instead of risky assumption testing. Jesse: Right. Sara: So being clear about what are the risks associated with the idea that I have for creating a new customer experience, and how might I test them, could lead you to, I’ll test them through a minimum viable product, but it doesn’t have to lead you there. But most companies don’t get that until you really push them. This is another one of those things where you can push them at a micro level. It’s like, what do you want to learn from making that minimum viable product? And often they can’t even tell you, because it’s just built into their agile process that they all spit out minimum viable products. These are all the little things that, if you could get that mindset to shift, then you end up in a different place. So that has definitely changed. And there’s a lot more acceptance of customer centric thinking on the part of product managers. The second thing that’s really big is that, of course, the field of product management, as you probably well known, has grown significantly. So there are a lot of product managers now. I don’t remember the numbers on LinkedIn, but it’s grown significantly. That includes not only the classic externally facing product manager, but it also includes a lot of internally facing product managers. So they might manage a platform on which products are built for that external customers or users. So, product management is sort of propagated in a lot of ways, which is probably why you see it encroaching more and more on what designers do, because, theoretically anyway, the product manager’s job is to bring together the customer with the engineering community, to make stuff happen, right? It’s more complex than that, but they’re supposed to be a representation of the customer. I would say in big companies, most of them have CX/UX design group, but it’s not always accessible. So you can’t get your project in there unless it’s prioritized in some way. So not everybody in the organization feels like they can get to those capabilities. B, very often what is produced is a bullet point list of things to build. So it’s not bringing alive the existing customer experience or the experience they want to build. Dorothy Leonard at Harvard used to call this empathic design. That I have in the guts of the engineers empathy for the customer. Well, if the CX design group is doing all that, but it’s not presented to the product manager in a form that allows them to use it to create that empathy, right, then we’re missing a connection. So the product managers are not really doing that kind of design work. Like many of them don’t interview customers. Somebody else does that. Which is too bad because they should be out in front of customers themselves. So this becomes the place where your question gets messy in the sense of, first of all, who does what, but then, where’s the connection between the two? I had a PhD student write an entire thesis about this question of how I present the results of design research to the people that will execute the product and not lose something in the process. So this could be another reason why designers feel left out, because maybe the bridge, there’s a gap, like something’s jumping across from the customer experience group into the PMs, but it’s not really a connected thing, like, could they bring the PMs on interviews with them? They probably should once in a while, right? So the PMs can actually see the customers. Do they help digest the data with the PMs? Probably not, right? What’s Next for Design Jesse: So, I wonder what all of this suggests for the future of design. And I’m curious what you think and what you see from your vantage point, in terms of what’s next for where design is going in organizations. Sara: Yeah, designers have very particular skill sets that are not generally present in the rest of the organization. For example, the ability to conduct a good ethnographic interview with a customer or user. The ability to create representations of an offering, whether it’s an experience, a service, whatever. There are capabilities that don’t exist elsewhere in the organization. Jesse: So what you’re saying is they have a very particular set of skills. Peter: Ha! Sara: That are important, and the question is, how do they get embedded in the organization, right? How and where? So, do product managers really understand… And this goes back to, in 1993, a woman who was a fashion designer in New York came to get her MBA, and after she took my operations class, she came to me, and she said, shouldn’t business people know more about design? And I said, sure, start a class. So she started a full on three unit class called Design as a Strategic Business Issue. And, Davis Masten, Jerry Hirshberg, Sara Little Turnbull, Bill Moggridge, right? Like, name people in that world. They came with their 35mm slide trays, and they showed what designers do. And it was eye opening and mind blowing for the MBA students. That class isn’t taught anymore. Partly because Design thinking came along, and so we started teaching design thinking, and now we’re not teaching what those critical skills that designers bring are and what they produce, right? I mean, there’s all kinds of stuff that we talk, oh, in design thinking, we do visualization because we put post its on the wall. Well, that’s not the same as, you know, my friend Michael Berry sketching what a new drive-through would be for a fast food company while everybody’s talking about it, right? And so part of the challenge then becomes, how do I make clear what those unique skills of designers bring to an organization. Then I would also ask the question, if I centralize something, then it’s not part of the fabric of the organization. So do I need a UX designer on every single team? Like does every product manager need one? I don’t know. Do they need at least consulting with one once a week? Maybe? I’m throwing this out there because I don’t know if anybody’s even asking those questions, probably the two of you. But, how do I bring that skill set to bear when it’s most valuable and needed? Right now, my sense is that it’s separate out there for a lot of big companies. It’s somewhere up here and maybe I’ll get access to it, right. And by the way, rapid testing of things is primarily A/B testing that’s owned by engineers, or MVPs that are owned by engineers. So this capability to do early testing is not embedded in the organization. But the agile feature mill is a fast cycle, but I lose the front end then. Like, product managers works gotten sucked into the agile feature mill. Well, ditto with any front end design work, right? So the question is, where do you want to embed those capabilities, as opposed to thinking of them as people? I know they’re people and they’re wonderful people, but really thinking about what is the capability set? What are the jobs they can help with? And where do I need to have those jobs done in an organization? And then how do I make that happen on the front lines, as opposed to in a big, you know, hand wavy way, which we kind of get stuck in, don’t we, when we talk about design? Jesse: Dr. Sara Beckman. Thank you so much for being with us. Sara: It has been my pleasure. Sara where can people find you? I’m reachable on LinkedIn. I just would ask if somebody reaches out on LinkedIn that they tell me why they know me. Peter: Not just a message that says hello. Jesse: Mention the podcast. Mention the podcast. Sara: Mention the podcast. There you go. and I’m also available by email, which is just Beckman at Berkeley dot edu. Peter: Awesome. Thank you so much. For those who have stuck around, we have a special treat for you. We have revamped our website at Finding Our Way dot Design, and we have also launched a new online community through Discord called The Way Station. So go to Finding Our Way dot Design. Click on the link that says The Way Station, and you’ll see a link to our new Discord server. Hope to see you there. Jesse: For more Finding Our Way, visit findingourway. design for past episodes and transcripts. You can now follow Finding Our Way on LinkedIn as well. For more about your hosts, visit our websites, petermerholtz. com and jessejamesgarrett. com. Peter recently launched The Merholz Agenda, his semi weekly newsletter. Find it at buttondown.com slash petermerholz. And if you’re curious about working with me as your coach, book your free introductory session at JesseJamesGarrett. com slash free coaching. If you’ve found value in something you’ve heard here today, we hope you’ll pass this episode along to someone Else who can use it. Thanks for everything you do for others, and thanks so much for listening.

Showing 21–24 of 24 episodes