Global Leadership in Design: Mastering Execution and Team Dynamics in Truly Diverse Settings
Checking session availability…
Hang tight while we load the latest updates.
Join us for an enlightening interview with Ricardo Marquez, a seasoned design leader renowned for his ability to foster innovative solutions and drive impactful projects to completion. In this interview, Ricardo will share his unique approach to leading high-performing teams, drawing on his extensive international experience across various industries including communications, financial services, enterprise solutions, and retail. He will delve into his philosophy of being a 'leader of leaders,' working alongside VPs and other senior figures to pave new avenues for organizational success.
Ricardo will outline his strategies for unlocking the potential within UX teams and leveraging a deep understanding of design and research to create experiences that resonate with users and advance business goals. By joining, you will gain insight into how to cultivate a vision for your personal passions that encompasses the broader company context as well as internal dynamics, ensuring that the projects you work on are not only visionary but also achievable and enjoyable.
This session is designed for current and aspiring leaders who aim to blend strategic foresight with practical execution, offering a unique perspective on navigating the complexities of global markets and multicultural teams.
Discover how to position yourself as an indispensable leader and executioner, capable of guiding your team to new heights of innovation and success, with Ricardo's expert guidance.
Global Leadership in Design: Mastering Execution and Team Dynamics in Truly Diverse Settings
Ricardo Marquez at UXDX Community: Innovative Leadership and Design. Video: https://youtu.be/J0vkkRy7O-E
Readable transcript: edited from the recording's captions for readability (fillers and false starts removed, punctuation and section headings added). Wording is the speaker's own. Timestamps are positions in the video. Names marked [?] could not be verified against the audio.
Introduction and a definition of high performance
[00:00:00] Katherine: Hi everybody. Very nice to not see you all, but I hope that we're going to have a really good conversation. We're going to have a great one. Now, I purposely added you to the session to show your face, because you are one of the most humble people that I've met. Today we're going to be talking about design leadership on a global scale. You have worked for companies like Wells Fargo, Ford, gez [?], DocuSign; I could go on. On top of that, you've also worked across continents. Obviously you're from Colombia; people will start hearing the accent soon. You've worked in South America, you've worked in the US and you've worked across Europe, and what we're going to talk through today is design leadership across all of those roles. So thank you, and welcome.
[00:00:46] Ricardo: Thank you, Katherine. I'm very excited to be here. I never get opportunities to share a little bit of my experience in this format, so I'm really glad to be here. There are two things before we start that I would love to share with the audience. The first one is that this is based on my learnings. This is not based on any kind of scientific studies about diversity and doing projects across multiple continents, so I hope it's useful. I hope to write a book someday, but we're not there yet. The second one is that when you and I started talking about what it means to have a team and lead a team, especially a high-performance team, in these different contexts and different continents, I think it's useful to share with everybody my definition of high performance. A high-performance team is a team that can do their best outputs, where the leader actually opens the right space for them to solve the conflicts, overcome the obstacles and actually do the best output and the best outcome that is possible. That's a little bit of where I'm coming from.
Early influences and a different kind of leadership
[00:01:56] Katherine: I love that already. I have a few questions set, and I want to take this in a little bit of a chronological order. Can you talk about early influences, maybe pivotal moments in your career, that shaped your path, both towards where you are today in the US but also from a design and design leadership perspective?
[00:02:28] Ricardo: Let me talk about those moments in a way that reflects on how I do leadership today. One of my earliest lessons was actually to listen and be open to new paths and new ways to explore. That goes back almost to the first job that I had, really early in my career. I was planning to go to Barcelona to get my master's, and I was working for a research startup. We were developing new methods to get to customers, and that's when I fell in love with research. But that job was actually a failure at the time, and I was really down, trying to figure out what the next thing I wanted to do was going to be. I wanted to double down and move to Barcelona, and then life actually gave me the opportunity to start working here in the US. While I was still saving to go to Europe, I met my now wife. Today is our anniversary; we've been married for 25 years. That opened a whole new life for me, and that whole plan of going to Barcelona faded away, but I'm very grateful. That was an early lesson: to be open to those paths and open to new learnings, and to take those opportunities.
[00:03:52] Ricardo: If you fast forward 10 years after that, I had the opportunity to move from San Francisco to Madrid to work with an outstanding team on both sides of the Atlantic. I had actually never been to Europe before, so I got there with my visa, my laptop and my family, just to start a new life. It was actually a really great success, and a lot of my growth came from that, so I'm very grateful for it. The last thing that I wanted to share is that I'm a little bit of a history buff, but I'm also very interested in understanding where my family comes from. One of the things that I've been learning a lot about is my type of leadership, because to your point, I am not an alpha leader who just screams "charge" all the time. It's more trying to bring community and bring the best of the teams forward. That comes a little bit from my heritage, from the Native American groups that I come from culturally. It was only six months ago that I found some material that actually helped me be more comfortable with that type of leadership. It gets me excited that getting the power to lead a team is to share that power and augment everybody's skills and possibilities, not to hoard it or anything like that. I feel comfortable with that stance, and that's part of why I'm so excited to be here to share that point of view.
[00:05:22] Katherine: Amazing. Can you drill into that a little bit more, your cultural heritage and what you found out? I like where you're going with that. A lot of people listening are probably thinking, "I'm not a leader, I'm soft, I'm on the sidelines." How did that help?
[00:05:43] Ricardo: What I know so far is that there are different types of leadership. The type of leadership that I understood from reading history is what some people call servant leaders or service leaders, things like that. It's a very beautiful concept. When you put it in practice, what it means to me is asking: how can I open this space for people to use their own voice and talk straight, for example, with executive leaders, with the right setup? That means it's more of a collaboration, almost jamming together as if it were a jazz band, let's put it that way, rather than having a solo leader doing all the music while the orchestra is in the background. It's a different stance, and it has worked so well so far. It's not for everybody, but I think most of the teams have appreciated that, and I have appreciated it as a leader, for sure.
What leaders bring: assumptions, values and biases
[00:06:47] Katherine: Love it. At the very beginning, you mentioned leadership in terms of how you lead, and that the success of the outcome is based on the leader versus the team. How much am I getting that right? It was such a small point that you made, but how much influence, as a percentage, do you think is on the leader versus the team? What's the dynamic there?
[00:07:11] Ricardo: I'd say it's an art and not a science to answer that question. One of the things that I have learned in the past couple of years is that one person, specifically executive leaders and leaders that are very senior, can have a lot of influence on how the team, and it could be a project team or a function team like a UX team, can take things and move forward. It all comes down to three things that matter a lot. One is assumptions about what can and cannot be done. The second is values: is the leader trying to be very close to the work, or trying to be more of a strategic leader, very much on top? The third one is biases, and biases could be positive and negative. Those are assumptions that don't get checked, or understandings that might not drive the team the right way. In terms of biases, one that comes to mind is in Silicon Valley, for example. There is a bias, or a very strong trend, towards having projects, especially at startups, that have to have very strong growth. That actually decides a lot for a leader: what kind of innovation they're going to take and what kind of innovation they're going to kill. Teams get affected by it, because they can have good ideas that maybe don't match that type of growth. Even if they're quality ideas that could create a good product, it's not the right time or the context to move them forward. The leader has to manage how to keep the team engaged on the right ideas and direct them towards those kinds of outcomes, understanding the context really well.
Moving between countries, and what culture brings
[00:09:13] Katherine: I love it. It is interesting: everyone's focused on growth, but at what cost? Can I switch over to the global perspective? Taking your background there, moving, taking opportunities almost based on personal opportunities, so personal opportunities came first, and then work opportunities... [?]
[00:09:49] Ricardo: Can you repeat the question? I'm sorry, I think I'm losing you.
[00:09:53] Katherine: You mentioned all these opportunities. When you took opportunities in your career, were they because of personal choices, or were they because of professional choices? Did they move together?
[00:10:14] Ricardo: I think at first it was more personal choices and personal interests. For example, when I started my career in product design at Intuit [?], I had a deep passion for things like mobile and mobility, and that got me involved in projects that were super interesting to me. Fast forward a year and a half later, without knowing or wanting it, I became a point of reference for all the design teams developing their own designs for mobile experiences in the company. It was really rewarding, because I got to look at different types of products across the company. Then, as I mentioned before, going to Spain was also a personal choice. I wanted to work more deeply on innovation, but also work closely with markets at home in South America and in Spanish-speaking Europe, and I ended up working with other markets in Germany and England. That was first a personal motivation to get there, but then it became more of a professional driver. That's when I realized that having the opportunity to lead the practice, I could create a much wider impact. That was almost a pivot in my mid-career, I think eight years ago or something like that, where I was much more focused on developing that type of leadership. To your point, in the first part of my career I was thinking, "I don't know if I want to be a big leader at scale," but then I realized that I could find my own voice. That was actually really rewarding and really positive for me.
[00:12:04] Katherine: Amazing. And working in all of those countries, with different languages and different cultures, how has that influenced your approach to both leadership and design?
[00:12:17] Ricardo: I wasn't prepared for that when I first got exposed to it. My lesson is that culture does not define a person's behavior or a team's behavior, but it does bring a lot of color to what the assumptions are and the decisions that they make. Some cultures, and I'm talking maybe about some places in Europe, are very focused on the structure and rigor that they bring, for example, to research or to the execution of design. Some other cultures are more flexible in terms of how they pivot quickly and improvise and iterate. All teams can do that, but they bring these assumptions from their own perspective, and that's why I talk about these trends, but also biases, things that you don't check. But there are also cultural traits that are really positive. When I was thinking about my experience internationally, one thing that I remember my friends from Spain shared was this notion, and I'm sorry because I'm not translating it right, of something like "run away forward." When you hit a point where there's a lot of ambiguity, or things feel very adverse in a project or in a conversation, sometimes it's good to just press through to see how you get through. You are running away as fast as you can, but you're going forward instead of backwards. That has actually helped me a lot in some cases where things are adverse, and it has helped my teams push forward too.
Creating space inside the team and translating for executives
[00:13:56] Katherine: I love that so much. I'm going to use that tomorrow. So good. And what's the goal with teams when it comes to facilitating them? From your perspective, what's the ultimate goal with building out your team?
[00:14:18] Ricardo: There are two things that I would share with the audience. One is internal, the team makeup. The idea is to create a space where, when conflict or adversity comes, and that's when you know whether the makeup and the dynamics of the team are able to withstand that pressure, the team can hold. For a leader, that means creating the space of slowing down and understanding people's cultural backgrounds, understanding their own needs when they're joining a project and understanding their skills when they're trying to apply them to that challenge. Not everybody deals well with the ambiguity of a pure greenfield project, and those same people can be really good at making a product perform in market. Understanding those kinds of traits, from the psychology of the person and the team as well as from the skills and experience, is a task that we sometimes overlook as leaders because we don't have time, but we should oversee it. If you take the time to do that, you can then create the space to facilitate conversations. For example, I remember one of my managers always started a brainstorm with silent contribution, and then it went to discussion. That bypassed a lot of the initial team dynamics of different cultures. For example, in Bogotá, in Colombia, we are more subtle [?] in terms of feedback, Americans are way more straightforward, and Europeans are more diplomatic about stuff. These kinds of changes in the dynamics create that space, and that space is one of the goals: to create, for a team that can be high performing, the space to take risks, to challenge each other in a very constructive way, and that kind of stuff.
[00:16:16] Ricardo: The second part is the external forces that come to it: working with other VPs and executive leaders. It's really hard for a team to present to these people and get approval on budgets or plans or things like that. But what I have learned is that the team should also understand that these people have a lot of pressure. They are as interested and as invested as they can be in the project, but they are looking at 50 or 25 of those conversations, and they have less time. So you help the team get to the point and share the information that really matters. And one thing that people don't do very often is come very straight and say, "Please help me with this, please help me with the budget, please help me with the plan." That focuses the team much more on having a good conversation with the executive in the very short time that they have, 10 minutes, 15 minutes, things like that. So as a leader you work to prepare the information and the data, so that when the team comes they can have a conversation. It's a little bit of those two dynamics that are very positive for a leader to have as an end goal.
[00:17:32] Ricardo: The thing that I would share, which I think people don't go deep into as often, is understanding the context of the organization in those two conversations. Sometimes the ideas are really strong, but the organization is not ready to deliver, or it's not the right time for a product to introduce that idea. Being aware of that context, and being aware of what I call the readiness of the organization to deliver what the team is proposing, is very important to be successful in those two contexts.
[00:18:07] Katherine: How dependent is the decision on whether to go with something on whoever pitches that proposal, the team or the individual? It could be the right option, but maybe they don't have confidence in the individual or the team. Or it could be the wrong one, but they have overconfidence in the team.
[00:18:30] Ricardo: I think it goes case by case. I don't think I can say that it's one person versus the team. Usually my experience is that the teams are really good at performing and creating solutions, but there is a task of translation, a last step that needs to be taken in order to get there. The leader should look at both questions. For the translation, for example, the question is: are the team's outputs and goals aligned with the organization? That includes metrics, and it also includes differentiating what the company, or the client, or the project, or the division is asking for versus what they need to have. Sometimes they need clarity on their scope in order to get to the ask that they want. That translation is something the leader needs to look at, for example, when the project is being scoped. On the flip side, a leader, as a person leading a team, has these other conversations with the leaders. I mentioned to you in one of our conversations how looking for a new way of working with other VPs required us to leverage some of the assets that we had already, but translate them. For example, translating the outcomes that we understood customers wanted. This was at DocuSign. Understanding those outcomes needed a translation to make them actionable for the other VPs of product and engineering, so they could understand how those outcomes frame really well some of the capabilities and features that they wanted to have. That was part of the journey of finding a new way of working together, keeping researchers and designers really close to that conversation, but knowing that the leader is going to take some of those conversations into a different context. That's very important. So more than thinking "is it a person, is it a team," it's understanding that it's a two-sided conversation, and the dynamics that go on on both sides of it, in order to be successful.
Becoming a leader of leaders
[00:20:40] Katherine: Love it. Looking at leadership evolution, you talked about psychology and understanding how individuals work. You get to be a team lead, but then you start leading those team leads, so you become a leader of leaders. Can you describe a significant transition in your career of taking that jump from being a team leader to a leader of leaders?
[00:21:11] Ricardo: I think it happened as new opportunities came by. I mentioned before that I had the opportunity to lead the design practice when I was in Spain. Then I came back, and I had the opportunity to lead smaller teams at big scale, and now more recently, at DocuSign, to lead bigger teams, looking at a whole portfolio. As you assume more of these roles, leading the practice or leading a big team, and you look at multiple streams of work or sectors of the industry, for example the innovation we were doing in Spain or different products here at DocuSign, you start understanding a little bit of that need to be a leader of leaders. That's why I mentioned the pressures that a VP, or a senior VP, or an executive has. The asks for performance maybe come at a quarter, and not the six months that a project can take. The number of projects that an executive is looking at is 50, and not one like a team can focus on. For me, understanding that second context was what helped me the most to adapt my style of communication, the team's guidance, and the outputs in terms of the artifacts: maybe creating a much higher-level artifact to have conversations with executives, and something much deeper that would help the product teams act upon those things.
[00:22:43] Ricardo: For example, with customer profiles at DocuSign, the team did an excellent job of developing a metaphor to explain them, and reduced the profiles from, I think, 60 to just less than 10. That actually accelerated a lot of that conversation. It's the same with other little artifacts that make a lot of difference. On other projects that I have worked on, sometimes a little Mad Libs [?] template to help teams create the same format for describing the outcome of a customer, or a simple, quickly sketched storyboard to bring the humanity of the customer to engineering and product, and of course to designers, makes a lot of difference, and it can be done really quickly. Those artifacts help you speak the same language and at the same altitude as other leaders, while at the same time staying aligned with the teams doing the more in-depth work.
How DocuSign reduced its customer profiles
[00:23:44] Katherine: I love it, and that speaks to collaborative dynamics. You've gone through a lot of pieces there. Can you tell us more about the DocuSign methodology for reducing those profiles from 60 to 10?
[00:24:04] Ricardo: I'm going to give kudos to my peers Morgan and Mar [?], who presented the process of reducing those profiles in Ireland at UXDX last year, so it's worth the audience taking a look if they haven't. From my perspective, because I was playing the role of acting VP, the mandate, or the guidance, from the executives was: can we focus more and be more explicit about the outcomes for the customers and the outcomes for the business, and see how they connect to each other? That created a kind of traceability for the teams to understand the two sides of that. It was possible, as I mentioned before, because research at different levels, not only UX research but other partners, had gone deeply into what the customer outcomes are and how we can summarize and synthesize them, and bring something that can be 300 tasks into umbrella jobs that are just eight or 10, and then put the capabilities under that. We did a little bit of finishing the synthesis for those jobs, connecting it to storyboards to bring in the human story and the context of use. We called it moments of use. After that, now that the teams were a little bit more familiar with the human context of use and the outcomes, it was much easier for leadership as well as for the teams to start classifying the capabilities underneath those moments.
[00:25:43] Ricardo: These are no rocket science methods; we all use them very often. It was more about the moment and the combination of those, the translation and the synthesis, and the openness in communication, which of course could have been better. But we tried to share as much of the evolution of the steps as we could from the UX leadership. That got us to a point where we could understand, for example, that a single capability could be present in three or four moments of the experience. That means the requirements would change for the roadmap, and that created a sequence for that capability to move forward over time, on a roadmap of a year, a year and a half. It was an iterative process. The VPs, my peers in product and operations and engineering, were engaged as they understood these things better, and the product directors and their teams actually felt that they were more in sync with other divisions and other areas of DocuSign product development when they were thinking about these roadmaps. That was very rewarding. But of course this is a long process. In order to fulfill those OKRs, we're talking about not only the quarters we're planning for, but also responding to executives with years of roadmapping, and they're still on that journey, let's put it that way.
Lessons about building UX teams
[00:27:08] Katherine: Fantastic. I'm going to wrap up with two questions. One is a reflection on your journey. What has been the most important lesson you've learned about building and nurturing UX?
[00:27:22] Ricardo: I think there are two lessons. The basic one is that we're all people, and it's important to create the space to connect at the most basic level, person to person. That becomes very salient when conflict comes. It becomes very important, for example, to set and declare a common purpose for the team and make sure that the team is aligned and understands that purpose. That also includes aligning the values, or maybe sharing the values that each one of these people has, especially if they come from different backgrounds, even within the same company, and different domains. That's very important. The second one I think I've mentioned already: to nurture the team and set them up for success. That means doing a little bit of digging, being aware of what the agenda is for each one of the professionals coming in, what the agenda of the project is, which has to do with purpose, and what the agenda of the executives and the other leaders around is, including the leader from design. That starts you understanding how to translate the work into these other ways of measuring success, let's put it that way, because that comes with metrics. And it starts mapping and creating a rationale for how this project and its solutions are in line with the readiness the organization has to deliver, like I was mentioning before with creating these moments of use and realigning the roadmaps to accelerate delivery. That awareness is the second lesson that I would like the audience to take into account.
[00:29:07] Katherine: Great. One thing that I've learned from talking to you and meeting your team, I've met Marin and Morgan, and I've also met P [?] on a completely different team, is that you treat people equally. I don't believe that you put in levels. You empower your team at any level, and they've been empowered, which I think is really important to reflect on as well, so they can have their own voice.
[00:29:34] Ricardo: Totally. That's one of my tenets, and I try to do it as much as possible.
Greatest achievements
[00:29:37] Katherine: You can really see that. Now I'm going to end on your greatest achievements, because I don't think you talk about them enough. Focusing on a project, what do you consider your greatest achievement, and tell us why.
[00:30:00] Ricardo: All right. In terms of projects, I think a project has success at a point in time, so let me bring two that are close to my heart. One was a video service that we created in Spain and launched as the first solution for people to get access to all the videos that are available on all channels: TV, theaters, streaming, cable. What was so rewarding about it is that it was an excellent team, a very, very small team. We got to create a different brand from Telefónica, which was a first at the time. When the service had run its arc and went down, I think it was five or six years later, the product manager was telling me that we got hundreds of emails and communications from customers saying, "How am I going to find out what I want to watch if I don't have you?" That type of feedback goes beyond customer satisfaction, because it's not prompted, it's not research. It's actually people coming back and saying, "We want to continue using your stuff," even if the company and organization has moved on.
[00:31:19] Ricardo: The second one: I was part of a small startup for several years, and we had a product that went into pilot. It was about sharing medical research with different markets around the world, and we had good growth, even though the product never went beyond pilot. When we did field research, we discovered the depth of the need that the industry had for bringing in different voices, voices that were not only related to the main pharmaceutical companies, on very important research that would help other communities, let's say, for example, in Colombia or in places in Asia. Understanding that need, and knowing that we were answering that need and that it was working as a pilot, was really, really rewarding. And in terms of leadership, of course, I'm very honored to have led the team at DocuSign for several months through so many of the changes that we went through: changing the way of working, including other teams, starting new disciplines within the team, that kind of stuff.
[00:32:26] Katherine: It really is phenomenal. Thank you so much, Ricardo. That was really insightful, and I really appreciate it. I think people will get a lot of value there. There have been a few questions. I might message you; if you could do a Q&A on LinkedIn, that would be really super, because I think we missed out on a bit. Thank you. I will talk to you soon; I'll see you in New York.
[00:32:50] Ricardo: Thank you, yes, and thanks everybody. I really appreciate the opportunity to share my experience.
