Episode

Book cover and a diagram of the VUCA Volatility, Uncertainty, Complexity & Ambiguity diagram - Author Jeremy Miller Beyond UX Design

Episode 40: Beyond UX Design Master Your Craft Beyond Pixels & Prototypes with Jeremy Miller

Jeremy Miller is a well-respected veteran Design leader many know from the popular podcast “Beyond UX Design”. He is continuously empowering UX professionals with the soft skills that make them more effective. In this episode we are discussing his book Beyond UX Design – Master Your Craft Beyond Pixels & Prototypes.

Jeremy’s impact on individuals, organizations, and field of UX more broadly is increasingly impactful. He continues to inspire and educate through his podcast, consultancy work, and mentorship. This book is essential for all UX designers because, like Jeremy says, “you can’t build great software without great relationships.” In each chapter, experts also shared meaningful, real-world perspectives and valuable insights.

Gift this book to every member of your team and join the conversation we recorded about the book.

Related interesting reads or resources

Full Transcript of this Podcast Episode

Transcript

Cathi I did bookmark a few things here that I'd like you to speak a little bit more about The book. I hope that's okay.

Jeremy Please. Yeah, whatever, I'm gonna follow you, wherever you go, I will follow.

Cathi Oh, you're the best. Welcome, Jeremy,

Cathi Hey everybody, it's Cathi Bosco from rethink.fm. The forward thinking podcast about experience design. Join me and special guests to discuss effective design technology and the intersection of helping people in entrepreneurship, from user experience research to product roadmaps. We've got you covered. We've all got questions, so let's get started. I really appreciate you joining us today Jeremy. Could you tell us a little bit about yourself and your work before we dive into this great book.

Jeremy Yeah, absolutely. So my name is Jeremy. I have been doing UX design, or design actually, for a long time, since the early 2000s started doing traditional print graphic design, self taught back when I was in college, started doing that. That kind of evolved over time to doing more advertising work. So obviously that led to web design. Web Design ultimately led to UX design, which I think many of us of a certain age probably followed a very similar path. So I started doing UX design. 2011 self taught, never, never taken a class or anything like that. So kind of learned the school of UX hard knocks, I guess coming up that way. So started doing working for startups for a little while, four years or so, at a consultancy that built, you know, basically, software for startups. And then I moved over to GE General Electric and worked for a giant multinational conglomerate, which is the exact opposite of startup world. And so I did that for a long time. Finally left that December 2023 and did consulting. And did that for a month, for a little while, for over the last year. So still doing consulting. And yeah, so that's that's basically been my journey, the abridged journey. But along the way, I kind of, I started, you know, experiencing the fact that, your hard skills. I don't want to call it craft, because I think the soft skills are actually part of craft, which is sort of the subtitle of the book, you know, Master Your Craft Beyond Pixels and Prototypes -those things, because the hard skills get you so far. And when you're in consulting, maybe hard skills a little more important, because people are paying you for the very specific thing. But especially when you're working on internal teams, the soft skills actually would help move your work forward. And so anyway, that's kind of how the books sort of evolved. We could dig into that a little bit if you want, but yeah, so that's, that's kind of me. I feel like there's a lot of people that that that sort of know these things intuitively, or they sort of feel it in their bones, but I think it was nice to just have a platform to sort of speak to them very specifically and call it some examples of how this thing works. And it's been really great to hear how it's resonated with a lot of people, because I feel like a lot of people knew this. It wasn't like this is groundbreaking, new things no one's ever talked about before. But I think it's just refreshing to sort of get a chance to chat with people who have sort of, you know, experienced similar things, and realize, like, hey, you know, like, I can design the best thing in the world, but if I'm not really, if I'm not working closely with the right people, it doesn't matter. Yeah, yeah, that's kind of how the book came out. But we can do that. I don't know how deep you want to get, but that's it. That's me, that's me, that's the book, that's all that stuff.

Cathi That's awesome. I definitely relate to your journey. We're in a parallel universe of I actually bridge the gap, before the digital evolution. I came of age in analog time, but was able to bridge and move forward into graphic design and digital illustration and web design, so I really relate to your journey. When I read the book over the holiday break, which I really enjoyed and really needed at this time, I was like, Okay, I'm getting a lot of affirmation. I'm going down the right path. I'm going down the right path. Oh yes, this is such a concise way to articulate something. So I loved a lot of the concise definitions. And this is what UX design is in this context. And if you take one thing away from this book. This is what it is. It was just so refreshing to read the concise aspect of what you're talking about in the book. I will also say I do see myself doing these soft skills at work, but I definitely did not have my pencil sharp enough. So reading this book helped me evaluate my own performance at work in terms of relationships and communication, and I need to improve in that area. There are definitely ways for even seasoned pros to improve in that area, and it just improves your quality and the meaningful nature of your work. You can make a difference for end users, better, faster, together with others, quicker. So I contacted you. I gotta, I gotta meet you. I want to talk about this book. I think it is really important. It just something that kind of gets overlooked. A lot of us have a lot of side hustles, and it's hard to keep up those relationships and side hustles and your main gig and your changing roles and things like that. So, yeah, I have a lot of bookmarks in the book, and if you don't mind, I'll guide the conversation a little bit by asking you to speak a little bit more to a few aspects of what you included. Okay, so I love the structure of the book too. I'm slightly dyslexic, so having those big, bold pages that have those call outs, those really helped me. Thank you.

Jeremy You know, it's funny that actually came about because, if you I don't know, you might know this, but other people without having a graphic design background, but other people don't. You have to have a certain number of pages in a book because of the way the pages are folded, and you have to get goes by fours and stuff. And so you have to have, you know, if you want, if you want the pages to lay out a certain order, you have to have a certain amount of pages before it right? And so I had to have pages where I'm like, well, I need extra content, but I don't have enough, so, so I started to use those, like pull quotes, just really as a way to get the page to line up. So the chapter always started on the website. So anyway, but I love that you, you found this useful. I was having a hard, really hard time, like narrowing down what to put in those pull quotes, because I wanted to put, like, everything.

Jeremy But anyway, yeah, anyway, I'm glad you liked them.

Cathi Yeah, you solved two problems by accident!

Cathi Well, I love how you define UX about creating meaningful outcomes for users, which increase revenue for our business. And it's crucial to always keep the users goals in mind, no matter how good the other parts of the software are, if the user doesn't get what they expected, it won't result in positive outcome or experience. I think that you're getting at feature bloat and things like that... Can talk a little bit more about that.

Jeremy Yeah, absolutely.

Jeremy Well, I think the thing there is, is this idea, though, that, you know, as designers, we care about users, obviously, and you know, user experience. It's right there in the name. I think this is sort of probably where some of the shift towards product design, growth design, some of the other type, whatever design you want to put in your title. It's that sort of perception that we care more about users than we care about the business, right? And I think again, if you've got, you know, a designer who is laser focused on users, but can't take into account the needs of the business, you know, you're not going to be successful in your role, right? And so you have got to understand the business priorities, right? And in reality, though, right? When I talk about positive outcomes, I don't mean just positive outcomes for users. I mean positive outcomes for the business as well, because if the user is happy, they pay, and if they pay, the business is happy. So there, you know, we talk about user taking user account, user needs and business needs into account. Those things, in theory, should not really be too far off, right? I mean, maybe you you change how you present a thing to a user, because it helps push a business metric one way or another. But at the end of the day, if you're sacrificing the business goals to make something better for the user, you're not going to have a positive outcome, because the business will suffer. And at the end of the day, if the business suffers, you don't have a job, right? So, so that's really what I'm getting at there, is, you know, you got to understand how the user goals align to business goals, and how improving the business goals should, in theory, improve the user goals. Otherwise, what's the point? Like the business isn't going to take off. Yet, it's a failed business. If you're taking advantage of users at a certain point, you might make some money in the short term, but long term, that business is going to fail, because people are going to realize they're being taken advantage of, and they're going to go somewhere else. And so there's, there has to be a balance there. I think, ultimately, I believe what's good for users is ultimately good for the business. It's just a matter of, you know, the rest of the part of the book is talking about how to, how to, how to get that message across to the right people, and that's where the relationships come in, right? So I don't want to go too far to that. And then you asked about specifically that quote, but that's, that's summing that up.

Cathi Yeah, if you're driving value for for users or customers or whatever, then they're willing to pay for that value and and and having partner in if it's product or the business department of your organization, helping you shape that into pricing and packaging and go to market all of those pricing evaluations is, I think it really is a partnership. It can't be up to one designer or one small UX team to manage all of that, but they have to work together. So yeah, I love that. The part about it being a team sport, yeah, yeah.

Jeremy I don't know if you wanted to get into that, but that's another aspect that I think is really important that we talk about -from the first chapter. It's been a while since I've actually read what I wrote, but you know, in that chapter one, or of the first couple chapters, we talk about what UX design is. For me, it's the experience that a user has. And actually we say UX design because that's sort of the industry term, but I really like customer experience. And well, my last role was actually doing more service design work, which was thinking more holistically about the service, end to end, less about specific piece of the software. And so from that perspective, you start to think about the user's experience as they're using an app is impacted by so many things beyond the user. The UX designers explicit control, right? We can control, you know, the border radius and the position of the buttons and the color and the typography and things like that, but that's one aspect of the user experience. But then, just like you said all those other things, the marketing team promoting a feature that doesn't work the way it works in the software, even if what you've designed is a great experience, if they came there with the perception that it will function differently, what that experience is broken, right? They're not going to be happy. The pricing structure, right? How they're like, if they love it, but if it's too expensive, or they feel like it's not worth the value, right? You're not going to have a good experience. The support when it breaks, you know, how that thing, you know, if they double charge me, right? That's going to affect my experience as it relates to this product, and I'm not going to be happy. So, all of those things impact the experience that a user has, and I think that's really important for us to think about as designers, whether you call yourself a product designer, UX, designer, growth designer, designer, designer, I don't care. You know, all of that is something I think we should be understanding that we are one small cog in a larger machine that is pumping out software, hopefully good software that someone wants to pay for.

Cathi Right. One of my partners at work, says we have to play from the same score. So she understands musicianship really well. And I always, I love that, yeah, I love that one, play from the same score.

Jeremy I like that. It's funny with like, analogies, because a lot of times people use the sport analogy, team analogy, but some people don't like sports. I like the musician analogy, the same score, because I like to always use an analogy of, like, a baseball team right where you've got people in the outfield, the infield, first base, second base, survey, shortstop, all that. You can't really play baseball, if you're missing the pitcher or the catcher or the outfielder or the first base player, everybody plays a part, and everybody's as important as everyone else, even though, in sports, you know, the pitcher gets paid more than the fielder, obviously. But you know,

Cathi And where is the loyalty, where is loyalty for these professional athletes, changing teams too frequently for me. hahaha

Cathi But yeah, that's that. I love that analogy. Though that's a good one I like that. I'm going to pull another quote out of the book and ask you to talk a little bit about that, if you will. "Strategy number five, make them feel seen, heard and understood. I've already said it multiple times in this books, but book, but I'll repeat it, because I believe it's that important. You cannot build great software without great relationships." I know we're already speaking to that. How do you how do you mentor other professionals who are holding all of that up themselves?

Jeremy Oh, interesting. So they feel like they're responsible for it. Is that what you mean?

Cathi Yeah, I I've seen people struggling from burnout, trying to keep everyone playing the same score and bridging gaps across different areas of an organization,

Jeremy yeah, so at first, I just want to give a shout out to Kate and Damiano that feel seen, heard and understood, that that was from a conversation that we had. And actually I rewrote that chapter after we had that interview, because I felt like that was such a powerful, powerful line. You know, stakeholders, product, people, anybody in meetings, I mean, anybody. We all, all of us. We want to feel seen, heard and understood. And I think that goes back to the core aspect of building relationships, it's trust. And you can't build trust if you don't feel seen, heard and understood. I mean, we talk about professional relationships, it. They're very closely tied with personal relationships, too, whether that's friends or partners or whatever, right? You can't really have a one sided relationship outside of work. You can't have a one sided relationship in work. I mean, I think it goes the same way. So that's it. I think that's I just want to give a shout out there. The second part, build great we can't build great software without great relationships. You can build software without great relationships, right? It's just probably going to be crap. And so for me, I think this is important, and this is something I want to stress in the book. I stress this I think several times is this is not your job as a UX designer to do these things. I strongly believe it is not your job that said, I think you have more control as a designer, an individual contributor, to influence how your at least core team works for the better. I believe that very strongly. Now that said, obviously we work on some teams that people are going to be sexist, misogynist, racist, these kinds of things. Awful people are going to exist, and we will at some point run into them in our career. But I believe for the most part, most people want to build good stuff. They don't want to build crap. I think, I think some of them just don't know how to do it. And so I think there's an opportunity for us to help our team understand maybe better ways of working. And I think you can't do that by beating them over the head. I've heard so many times, "Oh, we need to educate our team on how to do UX." No, you don't educate anybody. Nobody wants to be educated. Nobody wants to be talked down to you, help them get there, right? So that said, I also think at a certain point there's nothing wrong with just saying, screw it. I'm gonna get paid, right? And I think I would call this on the book, like there's nothing wrong with that. I mean, you could, you know, try and try and try, and if your team is not going to change. There's only so much you can control, and I don't think it's worth burning yourself out. I think this is probably maybe not sustainable long term for your career, but if you have to just say, "To hell with it, I'm just gonna do what you asked me to do", and we're gonna build junk, and I'm getting paid every two weeks. Is that so bad? I don't that's so bad. I mean, you know, have if you want to find a job, fine, use that crappy company to finance your job search, find a better job, or just say, You know what, I'm gonna just do the bare minimum, get paid and learn a new language or learn a new skill, or learn how to play guitar or whatever it is, right? So I don't think you have to feel like you're responsible for it. And I think UX designers often, you know, designers, we tend to be very empathetic towards users, and we just, Oh, I gotta do this. I gotta change the world. I'm gonna change the world with design and bubble. But I think that's the load of crap. And I think some people certainly can, but I don't think we need to take that on ourselves and do that ourselves. So I don't know if that answers your question.

Cathi I think it sort of does. I think of continuous learning, sort of like, I get on these jags where I'm on, a really steep learning binge and I'm, like, learning all this cool stuff, and I'm growing, I'm going through a professional growth spurt, and then I'll kind of ebb and flow where I'm less doing that, and I'm comfortable with that as my professional growth pattern. I think it's okay to be have a similar pattern in your impact at work too, where sometimes you just need to just get the work done that's assigned to you, as opposed to reshape the whole organization.

Cathi Again. You know, this is something I talk about this when I have a chapter on low maturity and how you can not change the work, but I think you can still deliver great work, and I think that you can do those things. But I think it's also important to understand what you can control, what you can control, and figuring out what you can control and working to fix that or enhance that or change that, but then also at the same time recognizing that you will not be able to control some things, and there is just no point in in stressing out about it. You know, you could beat your head against the wall all day. It's not going to move the needle. Did you really achieve anything? Right? Is it worth it? I don't think it is. It's yeah,

Cathi It is a waste to over-spend energy on the things you have no control over. Yeah, it's hard. That's a hard skill to develop, but really important, and staying curious is a helpful alternative to that.

Jeremy Oh, that's great.

Cathi In your book, you have five or six guest writers talking about their specific areas, and that's actually how I discovered the book, because, yeah, Tom Greever, he writes the is that hey, pronounce his last name. Tom Griever, Yep, yeah. He promoted the book on LinkedIn or something, and I follow him.

Jeremy Awesome.

Cathi Yeah. So, I really enjoyed those expert excerpts from different perspectives throughout the book too. The structure and different perspectives really resonated with me and kept me going. I guess I'd love to talk more about V, U, C, A, and do you say the term "Vuca"?

Jeremy yeah. I say, Vuca.

Cathi Great, okay, but let's talk about that, because I think the diagrams in here are very, very helpful, and something that you know, UX ers use all the time for synthesizing and prioritizing where to focus work on it you say, VUCA is not one thing, V, U, C and A are All different scenarios, and how to chart through that. Would you talk a little bit more about that? Yeah,

Jeremy Yeah absolutely. So VUCA is something that I have never heard anyone on the UX designer for this one net new, maybe not even new, I guess, because I didn't come up with this. But I've never heard another designer talk about this. And it's interesting, I talk about this in the book, how I actually found out about this concept. But I was working at GE General Electric, and they had this awesome program where you get to go up to upstate New York for a week, and it's like beautiful resort off site, and do training, right, corporate training and leadership training. And we did an entire week where it was focusing on this concept of volatility, or actually this concept was Managing volatility, uncertainty, complexity and ambiguity. And I mean, if you type in VUCA, you're going to find 1000 resources online, but they're all kind of focused on CEOs and executive leaders and how they can run a business and things like that, but I've never actually seen anybody talk about it from the lens of software team, right? And so I thought this was really powerful for me, because it changed my perspective, especially, like we just talked a minute about the things you can control, things you can't control, right? You talk about, you know, volatility, being things that are just constantly changing. And I talk, you know, examples about how my team bounced around. I had 15 bosses in like, seven years, you know, and everybody had different priorities. And so things are constantly changing. Uncertainty where, you know, we something's gonna happen, we aren't exactly sure what, you know, complexity with, like, just all of these, you know, systems in the background that have to connect, and third party APIs and legacy systems and all these things, and then ambiguity, which is the one almost every software team is probably familiar with, especially work at startups. You know, when you hear this one, a lot thrive in ambiguity. But like, what does that actually mean? You know? Like, I don't think anybody actually can define what that means, but it's saying we got to build something, but we don't know what you know. And so all of these things or challenges that you face, but I think naming them helps us to frame them, identify them, and then figure out how to move forward. So, you know, the way that something is constantly working when it's the way that we might work when it's constantly changing is very different from how it might work or we might proceed if it's just an ambiguous situation. And you know, again, this is where, I think, very similar to this concept of relationships. We all kind of know it intuitively. And you mentioned, you know, your pencil wasn't sharpened. This hopefully helps you, sort of sharpen the pencil does to identify those things to you, so that you can be better prepared. Because I can tell you right now, we're all we haven't already and you're starting out in your career, you will, we will run into volatility, you will run into uncertainty, you will run into complexity, and you will run into ambiguity. And if you try to, you know, just sort of blindly go into this, you're going to be much less, you know, productive, or the outcome is much less certain than if you go into it with a clear plan. And so that's, that's sort of the idea behind VUCA volatility and certain people's gonna be good. I try to actually not say VUCA because it's just a weird word. Yeah, I wasn't sure if I was even pronounced. Yeah, exactly. So yeah, actually I should have like, pronunciation key or something, or something. But yeah, that's because I VUCA that sounds weird, yeah? But yeah, it's, it's, it's definitely something that I think is just so beneficial for software teams, people on software teams to think about especially startups, I mean, but even then, it's like you think about startups and the chance to change. You think about large enterprise orgs as being steady and consistent, and you know, still they're not, not at all. You just you face a different type of challenge, right? And so, you know, trying to go into a large enterprise org with a startup mindset, you're not going to be successful. Trying to go to a startup with an enterprise mindset, you're not going to be successful. You have to know those challenges that you're facing and how to move forward. So does that answer your question? Hopefully.

Cathi Yeah, it does. When I see V, U, C, A, I see, oh, opportunity to make impact. I can make things less complex, like I have a few tools and I go towards those things to make impact, but earlier in my career, it would have been maybe a little bit more overwhelming, I know now, to run towards that river with someone else. So when we jump in holding hands and get through it, laugh, yeah, but yeah, I think it's a great call out in the book, and the diagramming of it was very, very helpful. So, thank you. I appreciate those diagrams.

Jeremy I also have to give a shout out. Those are from an article that Bennett & Lemoine wrote, and they produced those originally, and I just sort of took and, you know, pretty them up a bit and matched the style of the book and the fonts and stuff I can't remember the top of my head. It's in the book. It's in the book.

Cathi We'll put it in the show notes too. There you go. Okay, great, great. Great designers. Give credit. That's awesome. Thank you for that.

Jeremy Yeah, of course.

Cathi I also think in terms of collaboration, see, I'm an experience researcher, so I come through design and product design into research. So I've specialized in research, and I'm always advocating the most successful organizations are research-led. So for me, a big collaborator on our team is the end user, and we're working really closely with prospective and existing customers to see what problems we're solving, what areas are opportunities, risks, and that sort of thing. So how do you feel about interviewing people, and field research and that in terms of design and Master Your Craft Beyond Pixels & Prototypes, because I feel like that's outside of pixels and prototypes.

Jeremy Yeah, you know, it's, yeah, I could have probably added 1000 other things to that list, but you're right. I think it's critically important. I think a relationship with users is hugely beneficial, and maybe not even like relationship with specific users. We're gonna start up. You know, how do you, how do you build a relationship? Build a relationship with 1000s of users? You don't, but I think there's aspects of building a relationship small talk, for instance, trust. How do you do that in a very short amount of time in a user interview, so that someone opens up, right? That I think that's a huge, a huge thing. And I we had Tim Yeo on my podcast he's going to be on in the next few weeks, actually, but he helped write that one of the blurbs about small talk. And how do you identify quickly, you know, things you have in common, so that you can actually build small talk, because that small talk is the tiny little seed that that eventually grows into a larger relationship, right? And so for researchers, you know, you I used to work with this with with somebody at GE Stephon Tyler, and this guy was just like, amazing at opening, getting users to open up, and that, that ability to just interact with them, find commonality, get them, and the insights that we gained from those people were just amazing, right? And so I don't know if this like answers your question, necessarily, but I do believe that those aspects of building great relationships are critical, especially as it relates to research. But then maybe even the more important part, maybe not important, more important, the just as important part, is the ability for a researcher to get the rest of the team to empathize like you do, right? And that's just as critical, right? Getting the insights is fine, but if you can't get the rest of the team to understand the importance of the insight, or get them to feel that in their bones that pain point like you do, you're not gonna, you're not gonna really affect change, I don't think. And so I think that's just as important from a research perspective as well. You know, presenting, I've been, I've sat in a research output meeting once a debrief, and it was like 150 pages, right? And I'm just like, who thought this would influence anyone, right? Like, like Ari Zelman, now he's on LinkedIn, talks a lot about, you know, the short impact of insights, treating your your research team like a newsroom, and sharing those things and stuff. And you know, this goes beyond some of the stuff in the book, but, but I think that, you know, you've got to understand, though, this goes back to the relationship. Who's on your team, how do they like to be talked to, right? How do they like to communicate and what, what types of presentation will it will will have the greatest impact on the people that you're presented to, and you can't do that if you haven't had relationship with the stakeholders to understand the stuff that they care about. You know, because you might have, there might be people on team who actually find those 100 page decks acceptable and wonderful, and they like that data. And then you're going to have you on the team who want the five minute synthesis. What do you want me to do? Tell us what we should focus on. And if you don't understand your team well enough to know who wants what and how they want it, you're not going to be impactful as a researcher. And I think that goes back to the larger part of the relationships pieces, building empathy for those people, understanding how they like to communicate, so that you can communicate to them the most effective way possible, right?

Cathi Make it actionable for them - and meaningful. That's right, we do. We've come a long way in UX research. I think we can share little video clips, 32nd clips, and build up insights and make them actionable quickly for our team members and exposing, I think the key to a good research interview is having the opportunity for them to show you how they're doing things and observing them and being able to ask them questions During that time, they're happy to show and tell you that you learn, you learn more from them, showing you, oh, yeah, yeah. I think that that relationship's really important, and making that work actionable is really challenging for UX researchers, and important. Thank you so much.

Jeremy Yeah, of course.

Cathi I was wondering, what has I have a couple little wrap up questions for you. Jeremy, since I'm giving you a user research interview style session here, what surprised you, if anything, about the feedback you're getting from your work in your book at this point?

Jeremy What surprised me about the feedback? Surprise, surprised how many people that read it. I didn't expect, yeah, I really didn't expect a lot of people to really do much with it. It's funny because the book kind of came out because I got laid off in December of 2023, and I had all this extra time, and I was like, well, I could, I could, you know, I could, you know, cry about it, or I could, you know, do something with my time, actually, you know, productive, applying for jobs isn't helpful. So I was like, I'll just write a book. But no, I don't know, that's a good question. I hadn't really thought about that. I mean, it's been positive, I guess. Like, I was surprised how few people disagreed, and actually nobody, really. I haven't gotten any critical feedback, like, Oh, this is stupid. This is dumb. I was kind of expecting some of the hardcore, like craft people to push back more on it, but I actually was impressed that they actually found this to be, you know, something that they actually believe as well. So that was kind of nice to see.

Cathi I don't know, do you want me to? Do you want me to share critical feedback with you?

Jeremy you? Because I would love critical feedback. Sure, I'm down, please.

Cathi My only criticism, and it's very constructive, is "followership" as a term. Okay, I'm coming out of aschool of thinking, like there's two types of leaders through Jared Spool's teachings, or thinking, there are leaders who have role power. Doo this or and I can fire you, kind of leadership. And there's leadership where it's kind of bottoms up leadership, or it could be top down, where it's like, oh, you're generating a following through your work, through your relationships. So there's two types of leaders. And to me, that's like, Okay, I'm a leader. I can be a leader without being a role power leader, whereas "followership" feels second tier. Still, to me, that could just be my own personal language process.

Jeremy Yeah, you know, well, so the followership concept came about because I used to believe the same thing. I used to say leadership behaviors, all right, I see you, but you show leadership behaviors. And I actually, I did a, I did a podcast episode about leadership, about followership, or, sorry, about managing up, and how we can, you know, influence our team as an IC and, quote, unquote leaders. And I actually got feedback from someone that was like, I don't want to be a leader. I just want to do my job right. Like, I just want to do my job. I don't want to be a leader. I don't want to be told I have to be a leader. I don't want to be told that I'm like. My job is now to influence everyone else. I just want to do my work as best as I can, and that's it. And it got me thinking about that. And then I also had that same exact episode. I had someone tag Dr David Leitner, who I interviewed, and I did an episode with him about and he said, This sounds like fellowship. And I giggled to myself, they're like, follow sh*t. This sounds so stupid that you made that up. There's no way that's real. And as I started to kind of look into fellowship, I realized, like, this is actually a thing. This is a thing. This is something that people have done research on. Academics have been like, understanding it just like they under they, you know. But when you look at like, you go to Google, Google, what's, what's the one Google Scholar? They've got like, hundreds of 1000s of articles on leadership and research, and they've got like, 80,000 20,000 barely any on followership. And so I thought this was, like, a really important thing to kind of talk about, because not everybody can lead. Like, we can't all lead, like, if we have a group of people and like, I'm a leader, I'm a leader, I'm a leader, I'm a leader, I'm a leader. Like, you're gonna end up conflict at some point. A really good leader knows when to take a step back, and a good leader knows when it's time to follow someone else, right? And and so that's why I really like the idea of followership. And, it's interesting you mentioned that that feedback, because I kind of felt that exact same way. But I feel like there's a yin and yang thing here, and there's an opportunity for us to take a step back and follow, even if we're leaders, even if we're managers. And it's interesting, because when, when, when I talked to Dr. David Lightner, there is no ultimate leader at the top. Everybody follows somebody else, right? And even, you know, he used this great example, the president. You think the President follows, or the president is the leader, but at the end of the day, the President is following, you know, polls, they're following the concept of democracy, following the will of the people. They're following, right, exactly, but they're following. And I think that it takes a certain sense of humility for us to understand that at the end of the day, we are still following something else, right? And that's, that's where I like this idea of followership. And it does sound silly, and it does sound but I also, I made a point to try to stress that it's it doesn't mean we're robots, right? It doesn't mean we just blindly follow. We're not just sheep, but a really good courageous follower, which is what Dr. D uses, he that term quite a bit. And I use it in the book.

Cathi I love the use of that in the book.

Jeremy Yeah, "courageous followers" are going to say like I am following the larger ideals. And I don't believe this is the right course of action, right? And you try to do what you can to sort of steer the ship in a different direction, but at a certain point we have to agree and commit and say or disagree, but commit like, I don't like this, but for the good of the team, we decided to do it. I'm gonna do it even though I don't agree with it. And so, you know, I sort of take those two ideas that that one person that I spoke with is like, I just I don't want to be a leader. I judge. Stop telling me I need to be a leader. It's like, it's just like, frustrating to me. I want to just, like, do my work. And I think that's the sort of follower that some people just want to be some point. And we talked about ebbs and flows. Like, at some point your career, you sit back, but at some point in your career, you take, you take the next step, and you become the leader for a thing. And so anyway, I appreciate your feedback. Yeah, that's sort of my concept, and I feel you.

Cathi It's my own bias too, because, you know, it was a new word for me. So, yeah,

Jeremy Yeah, I had the same visceral reaction I did the first time. Yeah. But if you haven't yet, take a listen to the episode I did with Dr. D. I thought it was really insightful, and I learned quite a bit. But Dr D's on LinkedIn, and he posts stuff quite a bit. He's also got a YouTube channel. He posts a lot of stuff about about followership, and he's actually done, like a lot of academic research published papers and stuff on the concept of followership. And what's really interesting was this idea that, and the thing that he when he started doing his research, it was this idea that, you know, the United States was trying to, we were trying to reduce the proliferation of weapons of mass destruction. And you had this sort of idea like NATO and the West, quote, unquote, West. We're going to keep others from from creating these weapons of mass destruction. And you think like, oh, everybody's aligned, and we're all following each other, but, but what they found was like, no one is actually following, and we had the lack of followership, really, when we should have had an idea that everybody kind of gets in line and disagrees but commits, but nobody did. And sort of the inherent problem with democracies and allies and things like that, is they all kind of want to do their own thing. They all want to be leaders, but that goes back, like, everybody can't be a leader. Somebody has to take a step back and follow somebody else. So anyway, that's really it's really interesting. It's really fascinating stuff.

Cathi Yeah, I'll definitely put links to the podcast show notes, it's a great podcast. I loved the book I'm telling everyone I meet like I know there's a lot of books out there for UX ers, but this one is one you really should have. It will really help you to accelerate and simplify your professional impact. So -Thank you, I am really grateful you could join us. Jeremy.

Jeremy Absolutely.

Jeremy And I love when you mentioned this at the beginning, about sharpening the pencil. I just, I love that analogy, just like having your pencil sharpened, you know, and being ready. I just love that concept, that visual, just striking to me. I just like that a lot.

Cathi Well, thank you. Thank you for your time and generosity. Where can people find the book?

Jeremy You can find the book at beyond UX design.com/book Should we, I think if you you want to do a coupon code for anybody listening to get them, like, 10, 15% off?

Cathi Oh, that'd be huge.

Jeremy Yeah. What do you want to do? Let's see what's a rethink me and make the code RETHINK. Okay, so, yeah, beyond UX design Comm, slash book and use the code rethink at 15% off, that would be awesome. And you can find me on LinkedIn. Look for Jeremy Miller. You might need to, you might need to scroll through. It's a lot of Jeremy Miller's on LinkedIn. I might actually thinking about doing a like a LinkedIn live with all the Jeremy millers, who are also UX designers on LinkedIn, just like 45 minutes anyway, yeah, so find me on there beyond UX design.com Listen, subscribe wherever you listen to podcasts and all that stuff. And yeah, that's it. That's pretty much all my links.

Cathi All right. Well, thank you for the rethink coupon code, and for the book!

Scroll to Top