Category: design leadership

That Vision Thing

About a year ago, I distilled the conversations Jesse and I had been having with design executives on our podcast Finding Our Way into a post titled, “Design leadership is change management.” And the first element needed to drive change? Vision, which I defined as “an orientation, pointing the team in the right direction. Even better, it’s a destination to which people are being led.”

Over this past year, in working with design leaders who have found articulating a vision to be challenging, I’ve put more shape around my thinking, and found myself repeatedly returning to an example, which I thought I’d share here.

Vision or Agenda?

Before getting to the example, a quick nomenclature check.

I think a stumbling block for design leaders when it comes to “vision” is that “vision” often means something very specific in design: a north-star-style depiction of a future state experience. But the change that a design leader seeks can incorporate so much more—it could involve new ways of working (double diamond; embracing product discovery), or the desired impact on the business and their customers. So instead of “vision,” I advocate for the word “agenda.” It doesn’t have the baggage of “vision,” and it also makes clear that, as a leader, it’s incumbent that you have a (dare I say) political point of view, a cause for which you’re advocating.

An Example of an Agenda

Among the design executives Jesse and I interviewed was Kaaren Hanson, Chief Design Officer of Chase Bank. Early in our discussion, when defining her role, she identified four initiatives: building a senior team, nurturing executive relationships, establishing UX metrics, and evolving product development processes. Later in our discussion, which sharing how she would align the efforts of her 800+-person team, she emphasized how they’re all creating “one freaking experience.”

As I sought to put shape on the ideas of agenda and vision, I realized I could use what Kaaren shared. In a company as complex as Chase Bank, achieving “one freaking experience” could take 10, even 20 years (because it requires not just internal alignment, but may need regulatory change as well). It makes for a powerful long-term agenda (and, in this case, is also a vision). The four initiatives she outlined could be grouped in a near-term agenda of “Design as strategic contributor,” a 3-5 year program (my estimate) that, by establishing Design as a credible business partner, sets the company on the course of delivering on “one freaking experience.”      

Diagram showing one horizon-line curve, underneath reads 10-20 years, underneath that reads "One Freaking Experience". Then another horizon line curve, underneath that reads "3-5 years", underneath that reads "Design as strategic contributor" and then four bullet points beneath: Build senior team Nurture exec relationships Establish UX Metrics Evolve product practice

Take the time to do this for yourself

As I write this, it’s the start of the new year. A worthwhile activity for any design leader would be to sit down, even for just 30 minutes or so, and write down their agenda. Have both a long-term agenda (though 10-20 years is probably excessive for most folks) and a nearer-term one that ladders up to it. This agenda may be something you share with your team (to drive alignment) or it may be personal (perhaps about your career goals). Making this concrete will enable you to make better decisions throughout the year, as you’ll have a clear organizing principle to go by. 

Thesis

Design maturity models are oversimplified frameworks that mask the necessary nuance to understand and develop an organization’s ability to get the most out of a Design function. That said, used responsibly, they can be a helpful heuristic, particularly early on, for orienting yourself in an organization. 

The futility of maturity models

Hang Xu has identified design maturity as a frame for better understanding the challenges the UX/Design community has been expressing. As a recruiter, he’s attuned to the impact of an organization’s maturity on a practitioner’s ability to succeed. He’s been writing a bunch on LinkedIn on this subject, including this recent post on probing and assessing an organization’s maturity. In direct communications with me, he’s asked for my take on the subject, and, as I see the concept of maturity come up more and more often in my work with design leaders, I figured I’d publish my thoughts. 

When we were writing Org Design for Design Orgs, I researched UX/Design Maturity models, as I thought they’d be helpful for grounding our discussion. What I found then (and still, largely, see now) is that these maturity models are too simplistic, reducing a bunch of factors into a single-number linear framework. Through my experience, I knew that a single organization may be at multiple places along the maturity line, which suggested that it wasn’t a useful tool for diagnosis.

My frustration proved fruitful, as it lead to writing chapter 3: The 12 Qualities of Effective Design Organizations, which is probably the single best chapter in the book. Instead of a single overarching maturity model, I believe it better to rate a set of qualities independent of one another, coming up with a kind of ‘report card’ for the organization. This specificity and nuance allows people to zero in on specific issues worth addressing. 

Erika Hall shared with me (in a direct message) her frustration with UX/Design maturity models as being “nonsense because they’re overly simplistic, linear, and…absolutely ignores the business model.” She then expanded on this on LinkedIn:  

Step 0 of “design maturity” is aligning the fundamental business model with the wellbeing of *all* users of and stakeholders affected by the systems being designed. This includes workers, communities, and ecosystems.
Otherwise, it’s just increasing levels of acontextual organizational proficiency in candy-coating extraction and exploitation. And then, what’s the point?

The utility of maturity models

So, if maturity models are so dumb, why do they persist, and why can’t even I shut up about them? In my work with design leaders, I’ve found that there is some value in the abstract concept of maturity as a guide for how to engage with their organization. This came up in the most recent episode if Finding Our Way, where Jesse and I circled the subject, and I reflected on Jehad’s comment that some design leaders shouldn’t go to the lengths of trying to ‘demonstrate impact,’ because the company might not be ready for that, but to instead to tune your message to the company’s maturity, which may involve a different means of ‘showing your worth.’ I then dug into this thinking on the intersection of UX Metrics and Maturity.

Jesse, in his work with his coaching clients, has developed a framing of ‘three trajectories’: organizational maturity, design maturity, and leadership, and how navigating the intersection of these trajectories is crucial for any leader wanting to operate at their fullest potential. (It’s worth reading his post, so go there and do that now.)

(Welcome back.) 

As long as you don’t take a maturity model to be prescriptive, but instead a tool for initial orientation, they can be a useful heuristic. If you have to use one the Nielsen Norman Group one is probably best, and appears to have become the standard. Interestingly, if you strip away oversimplified linearity, and look at the constituent factors (Strategy, Culture, Process, Outcomes), it’s even more useful, as it affords some nuance, akin to the 12 Qualities.  

UX/Design leaders often get caught up in their personal missions, their narratives of change and impact, and believe they just need to “educate”, “persuade,” “evangelize” their point of view, typically one of customer-centricity and the importance of quality, in order to influence those around them. This proves ironic, as these UX/Designers who espouse ‘outside-in’ when it comes to delivering customer experiences, now practice “inside-out” when trying to get what they want.

In my work with leaders, I counsel them to “connect the work of UX/Design to what the Business values,” and to meet their leaders where they are on their maturity curve. This means listening to them and their concerns and responding to that, not foisting your desires upon them. 

This came to mind as I read Janice Fraser and Jason Fraser’s recent book, Farther, Faster, and Far Less Drama, a practical guidebook to lower-stress leadership. It features a sidebar from Hannah Jones, now the CEO of the Earthshot Prize, and formerly Nike’s first Chief Sustainability Officer (a role she had for 16 years). She shares how she practiced change, and features this bit of wisdom:

“The advice I would give people undertaking to change an organization is to understand motivation… Motivation is at the root of most human behavior—and most people are pretty entrenched in what their motivations are…If…you’re not critical or judgmental of them, then you can start to meet people where they are and bring them with as you allies.”

She then shares what that meant practically:

“So sustainability as ‘hug a tree’ wasn’t getting us anywhere. But once we framed it as a risk mitigation effort for the board, a financial benefit to the CFO, and a growth opportunity to the innovator and the CEO, we could start to pull levers with far greater power than when I had remained entrenched in my own language…

“…Know your place in the system, but know other people’s places and benefits and why they…[are] doing what they do. Then figure out how to make their worlds feel better to them. ‘Make everybody else the hero in the story” was one of my mantras.”  

This resonated with something I posted a while back, how Billie Jean King got women paid the same as men for professional tennis, the heart of which was: “Just understand their side, so when you sit down to speak, and have dialogue, you actually have some understanding and empathy for them. And, if you can show that, I think they’ll start to think about you in a different way as well.”

In my experience, UX/Design types do more to constrain their ability to make an impact than anyone else. Rein in that missionary zeal in favor of making a connection. This doesn’t mean you shouldn’t have an idealistic agenda, but don’t assume what motivates you motivates others. Does this mean you’re playing politics? Yep. That’s the job.

Over the holiday break, I reviewed the 5 conversations that Jesse and I have conducted with truly senior design executives for our podcast Finding Our Way, looking for lessons that could be distilled and imparted for those who aspire to such roles. As I pored over the transcripts, an overarching theme emerged:
Design leadership is change management. 

This was actually stated in the first interview, by Katrina Alcorn, GM of Design for IBM:

“Well, I think if design was fully understood and recognized and invested in and respected, the way, for example, development is, we would not need to be change agents. We would need to be good stewards… I think we’re change agents because all of us doing this are still part of a movement to change how businesses work, how they run.”

In my thought partnership work with design leaders, I’ve at times encouraged ‘change management’ tactics to help them with specific initiatives. What reviewing these discussions with successful leaders made clear is that change management isn’t a tactic—it’s the job. And that other leaders would realize greater success if they framed their efforts with this perspective.

Thankfully, these leaders also shared the mechanisms by which they’ve enacted change. Analyzing these discussions, I distilled a set of practices and a mindsets that should help anyone trying to establish design as an active participant within their organizations. While I won’t claim this as some kind of magic key to unlock success, I would encourage using it as a playbook that scaffolds your efforts.

A. Shape a vision

B. Adopt a portfolio approach

C. Manage the relationships

D. Communicate with intent

E. Maintain patience and perspective

A. Shape a vision

To lead requires vision. At minimum it’s an orientation, pointing the team in the right direction. Even better, it’s a destination to which people are being led. Visions come in many forms. They could be mindset shifts (becoming more “customer-centered” or “experience-led”), process evolution (adopting dual-track agile, user-centered and inclusive design methods), or outcomes that show impact (adopting metrics like Google’s HEART framework).

North Stars

And, being designers, a common type of vision is the North Star, a concrete depiction of an improved future-state offering. As Greg Petroff stated, “You use a north star to drive the art of the possible…, to scratch the itch on tough questions… Artifacts are … tangible and easier for people to…identify with.” For Daniela Jorge, North Stars “make it feel real so that everyone can get aligned around that same outcome and that same end state.” The thing to keep in mind (and communicate to others) is that North Stars are not execution plans, and, as Greg says, should be done “in a way where people have permission to break them and change them, and challenge them.”

B. Adopt a portfolio approach

For Design organizations, there will always be more work to do than people to do it. So the trick is to figure out how best to focus efforts. 

Kaaren Hanson cautioned against trying to do All The Things at once. “If you come in and you say, ‘We’re just going to do everything, we’re going to slow everything down,’ you are going to fail. But you can…look at this portfolio of initiatives, and say, ‘These two seem ripe for really having a bigger impact… And so we’re gonna put our points here’… and hope like hell at least one of them works.” 

Or, as Katrina Alcorn said, “If you say yes to everything, nothing gets done.”

But then, how do you assemble this portfolio?

Choosing who you work with

When Greg Petroff was building the Design capability at GE, in order to focus their limited capacity on that which would have impact, his org would only work with two kinds of teams: “either they totally got us and they totally understood design, and they were all in, or they had tried everything and were failing and the business was about to die…And if you’re in the middle, we didn’t have the time for you. We were sorry.” The logic being, “if we could take a business that was struggling and make it successful, that had currency in that culture… And then the net promoters, …they were the ones who, if things were kind of tough, they could kind of support us in a moment.”

Rachel Kobetz had a similar approach: “It was a mix of finding … those people that could be champions with me, those people that could be the beacons. It’s really important to find, not just the individuals, but the projects or programs that can be the beacons to showcase how a new way of working yields better outcomes.” 

Short-term gains within a long-term frame

Key to change management success is showing progress early. As Greg Petroff shared, “Senior executive attention span can be quite short. And so you have to find ways to show demonstrable quick wins and benefit, while leaving room for the things that are actually more substantive and impact-driven, that are going to take more time.” Rachel Kobetz cautioned that, “Sometimes, you know, leaders, they are charting the vision for tomorrow without delivering for today.” You need to balance, “be able to go deep, to be able to make sure that we’re building for today.” 

Operating Mechanisms

For that longer-term frame, output (like launching a new product or service, or overhauling something in sore need of improvement), even with successful outcomes (more sign-ups, happier users) is insufficient. As Kaaren Hanson stresses, “Those operating mechanisms count so damn much.” By operating mechanisms she means evolving processes to account for customer-centered concerns, such as making sure customer experience measurements are part of business reviews. It also means “working with leaders across the business, including the CEO of consumer bank or the CEO of connected commerce or the CEO of wealth management, to ensure that design is sitting at their table,” making it a default expectation that design is included in the senior-most business conversations. She continues, “you have to get into the operations of the company, and companies have like a, heartbeat, which goes back to, what are the expectations for designers? What are the expectations for product managers? How are we bonusing people on this stuff? Like, those are all the operating mechanisms you have to infiltrate.”

C. Manage the relationships

Infiltrating operations requires working the relationships necessary to make change happen. And while it’s important to develop good relationships with the people within your organization, what these leaders stressed was how crucial it was to establish relationships with your cross-functional peers in product, engineering, marketing, and with executives and other stakeholders.

Cross-functional relationships

Kaaren Hanson has staffed her leadership team such that “every design leader that sits within a line of business sits at that [line of business’] CEO table.” She also expects that her design leaders are spending more time messaging and in meetings with their “product, engingeering, and data partners” than any other people. 

And Rachel Kobetz, with whom we went quite deep on relationships, shared, “when I’m talking about the importance of the relationships, it’s where I spend a lot of my time. …Working across and working up…the whole company to make sure that there’s clear communication, there’s trust and we’re building relationships so that people understand what we’re doing.”

Make your partners successful

A recurring theme was to focus not on your own organization’s success, but, as Kaaren Hanson points out, “my job is to make you [my partner] more successful.” Greg Petroff echoed this, “you always wanna make sure that the, your partner is the one who gets the attention…We celebrated the wins, but the win was not us. The win was the business unit.”

Co-create outcomes before starting the work

A means for strengthening relationships, and to ensure your partners’ success is to co-create outcomes before doing the work. As Greg Petroff put it, “I’m all about co-defining outcomes. I think that’s a missing gap in software development. And I think a lot of product teams start without actually having a lot of clarity about what they’re trying to accomplish and they feel like the agile process will help them get there and it’s just nuts. And so you know, I am, I’m all about working with product teams early on to do things like Lean UX canvas work.”

Designers often like to talk process, but Rachel Kobetz suggests, “don’t harp on the process itself. Actually focus on the outcomes, and when you have shared outcomes together, you’re going to be set up for success.” By starting with shared outcomes, you can then engage in process discussions, because if “you’re aligned on shared outcomes, they’re going to be much more receptive and open to a new way of working, versus you just come in and say, ‘Everything you’re doing is wrong, and this is how we’re gonna do it.'”

Mixed maturity means varying reactions

One of the specific challenges of managing change, particularly in sizable organizations, is that you’ll have a different degrees of maturity in the different parts of the organization, and that leads to a range of reactions to that change. As Greg Petroff said, “it depends on the culture of the organization and it’s maturity and sometimes parts of the organization are great and others aren’t.”

Rachel Kobetz shared, “People handle change or evolution much differently. You have some people that are, like, ‘This feels awesome. I love it.’ You have other people…that say ‘change is the only thing that’s constant.’ And then you have other people that are like, ‘Wait, hold on, you moved my cheese, what happened here?'”

No judgment, maintain positivity, avoid toxicity

At the heart of change management is a recognition that things today aren’t as good as they could or should be (or why bother changing). TSo his leads to an unfortunate tendency to criticize the current state, but, as Kaaren Hanson learned, “Being judgmental is toxic…As someone who’s been in this field, we are incredibly critical of things. That’s our job is to be critical, right? But that’s not helpful when you’re working with other people, and you’re trying to drive change in an organization, because if you’re judgemental, it’s almost like you’re adding toxicity to relationship. So I’ve had to rein that way back.”

D. Communicate with intent

Every leader we spoke with addressed the importance of communications, and having a strategy, a plan. It’s not enough to do the work, it’s even not enough to make an impact. If you don’t make the effort to let others know about that impact, it might as well not have happened.

Katrina Alcorn shared how she’d been publicly blogging about the ongoing evolution of design at IBM. 

Kaaren Hanson stressed how much time she’s spent with her leaders, having them share their stories with her initially, so she can provide feedback on the most salient points to then communicate out, “they’ll have those short stories and snippets that they can share with their executives in the elevator.”

Greg Petroff has built “shadow comms teams,” writing a monthly newsletter about all the things his team was doing. Tying to the prior theme, these newsletters showcased partners, “always a story about someone else in the organization that we promoted, ‘the SVP of product does this, and here’s the decisions that they made that were great around design work,’ because you want to celebrate them, too.”

Rachel Kobetz has found that the “the essence of it is just overcommunication.” She exploits a number of channels in getting her message out, “whether that is in a conversation with another executive in a meeting, and being able to have that moment to talk about the great work that the team is doing, or that our two teams are doing together. Creating a newsletter. Doing my own writing and pushing it out across the company. Whether it’s in town halls or, showcases, quarterly events, all of the different avenues you can take, you have to use those as opportunities to get the word out.” She concludes,  you’re never done with that communication.”

Transparency

A judgment call that’s difficult for some leaders is knowing what to say to whom. As leaders, you have access to potentially sensitive information. That said, Kaaren Hanson stresses the importance of transparency: “if you’re not transparent about what you’re doing and why you’re doing it, it’s easy for people to read all kinds of other things into what you’re doing.” Daniela Jorge concurs, “something that I always aim to do as a leader, is providing as much transparency and context… I think it’s very easy when you’re in a leadership position to forget that you have access to a lot more information and context that a designer on the team might not.”

This transparency is essential for working with other functions, particularly when working toward shared outcomes. Rachel Kobetz proposes, “you instead open up that box and you create transparency in the process. You bring people in, you make them part of that process from day one, but then when you’re telling the story of it, you’re starting off on the foot of, we’re all aligned to shared outcomes.”

E. Maintain patience and perspective

As design leaders, we often have a clear view of where we want to go, and what it will take to get there, and the time it takes to make progress can prove quite frustrating. When I asked Daniela Jorge about how she helps her leaders who may be operating at a new level of seniority, she shared, “a lot of it is that we talk about perspective, patience, right? Figuring out how you’re influencing, figuring out how you can sometimes measure progress in small increments. Because the job that we do is hard, right? And especially because I think we are able to see what it should be and what it could be. And that isn’t always what is happening in that moment or in the short term. So, a lot of the time that we spend is just talking, regaining perspective so that folks don’t get discouraged.” 

So get out there, and make some change!

If I were to assess the ‘vibes’ at the outset of 2023, it’s that there is a potential for fundamental shifts in the ways that businesses are working. This provides an opportunity for Design Leaders to proactively insert themselves into those ‘operating mechanisms’ (as Kaaren Hanson put it), and make some real change. 

As this post suggests, change is hard. Its taxing, frustrating, and time consuming. But it’s also how we can make things better, for us, our teams, our colleagues, and our customers. If you’re signing up to be a design leader, you are signing up to make change.

(And if you’re interested in pursuing this theme further, I wholeheartedly recommend the new book Changemakers by Maria Giudice and Christopher Ireland. It provides clear actions you can take to realize the change you seek.)

Design as an executive function is new, so Heads of Design are typically lonelier than their peer leadership positions. Your boss may have never had a truly senior Design leader report to them, and doesn’t really understand all that a Design team can deliver. You’re only Design leader on executive team, whereas there are multiple Product Management and Engineering leads.

This means that there’s no one to turn to internally as you try to figure out how to best lead your Design organization.

This is where I come in. I support executive Heads of Design in a mode I call “Thought Partnership.” I work with design leaders to accelerate thinking through their trickiest challenges, leveraging my experience (20+ years leading design teams; 5 years as a management consultant across all kinds of design organizations) to identify paths forward, enabling Heads of Design to make important, impactful decisions with confidence. Recent work with design leaders addressed such matters as:

  • Scaling from 30 to 100 team members
  • What their job actually is, where they should focus (and what they need to delegate)
  • Building career architectures and leveling frameworks
  • Improving recruiting and hiring practices
  • Establishing Design Operations
  • Elevating Design’s impact in the company
  • Evolving product development practices to better incorporate design throughout the process
  • Articulate a strategic vision to align product efforts

I’ve done this work ad hoc, in response to design leaders reaching out to see if I could support them. It has been some of my favorite work, capitalizing on my distinct vantage point to help leaders go from uncertain to confident, and see real impact in short time frames. 

As such, I’m now setting aside more time for this kind of work, and, well, telling the world that this is a service I’m happy to offer. 

It’s a small investment of time: the work is typically structured as one or two 1-hour sessions a month. In each session the Design Leader shares with me their topmost challenge, and we work together to figure out the best way forward. 

If this is something you’d like to take part in, please reach out through email, and we can then set up follow-up discussions.

On a recent episode of Finding Our Way, Jesse and I spoke with Tim Kieschnick. I worked with Tim for about a year, and learned a ton from our collaboration. He’s an interesting cat—he worked at Kaiser Permanente for 30 years (until retirement), and in that time helped establish their web presence, UX as a practice, service design, and HCD/Design Thinking/Design Sprints. He’s a reflective practitioner, and through his experience developed two frameworks which I have in turn used in my thought partnership practice with design leaders. I was eager for him to share his wisdom on our podcast.

The 3Ps of the Leadership Ceiling

A little over a year ago, at my urging (so I could refer to it without feeling like I was plagiarizing), Tim posted an introduction to The Leadership Ceiling. (some of what I write here will repeat what’s over there, but in my words.) At heart, it’s a simple construct: Leaders create a conceptual ceiling above which their organization cannot rise. Tim identifies three ceilings:

Purpose

Why does this organization exist? How is that purpose articulated? Are we driving toward output, or outcomes? How does our purpose inspire, connecting people with their higher, better selves?

People

Who is in this organization? What is the caliber of contributor? And, are we creating a truly people-centered organization that enables those folks to deliver at their best? 

Process

How is the work getting done? Does our process bog us down, or lift us up? How are we coordinating across functions? Are people spread too thin, across too many initiatives, or are they able to maintain focus and commitment? Are teams empowered to practice a process that is ‘fit for purpose,’ or is there an imposed standard way of doing things that cannot be deviated from?

(This is reminiscent of what Daniel Pink identified in Drive, in terms of what it takes to motivate people: provide them Autonomy (process), Mastery (people), and Purpose.)

In my experience, I don’t see three ceilings, rather one ceiling that is a product of how these three factors intersect. In my work with design leaders, looking at the intersection has proven helpful, because it illuminates why there’s cognitive dissonance between the message they’re getting from their leadership, and why the work doesn’t meet their expectations. 

The diagram to the right shows my take on this aspect, which is that the Leadership Ceiling is set by which ever factor is lowest. 

For instance, I’ve supported a number of banks and insurance services firms. And nearly all of them have high-minded aspirations for their business, with mission statements about empowering people’s financial wellbeing, or improving the health of all Americans. And these firms will also have committed to providing a much more conscientious work environment that encourages bringing your whole self, and stresses values of psychological safety and vulnerability.

But these large legacy organizations are bogged down in process, for reasons including bureaucracy, poor organization design, unwillingness to truly empower teams, people spread too thin across too many workstreams, etc. 

And so, the Leadership Ceiling is established by that lowest factor. And the design leaders I work with, who may have been sold on a company’s vision and culture, then struggle when they realize that for all that high-and-mighty talk, their ability to deliver is severely hamstrung by a lack of attention to process. 

The ABC’s of The Leadership Ceiling

Once you understand the height of a Leadership Ceiling, then you have to figure out your relationship to it. Tim uses an ABC mnemonic to think through what you can do:

 

Diagram of the ABC of The Leadership Ceiling from Tim’s website.

You can try to work Above the ceiling

This approach is pretty common for designers, particularly new to an organization, who see their job as to ‘fix’ whatever came before, or to realize a bold new innovative vision. And they may see their leader’s Ceiling, and perhaps engaged in some effort where they bumped their head on the ceiling, and then see their job as the innovative iconoclast to work above the ceiling, to show to the rest of the org just how great it can be. 

This never works. You might get some time to play in that rarefied air, but inevitably the leader’s Ceiling does its thing, often in the form of the Leader being frustrated that the designer isn’t doing what was expected of them, instead pursuing some quixotic endeavor that was bound to go nowhere.

So, most of us end up working Below the ceiling

We realize that we are constrained by the leader’s ceiling, and focus our efforts there. The dream is to have a leader with a high ceiling across all 3Ps, providing all kinds of headroom to innovate and grow. But most of us find ourselves below a ceiling lower than our liking, and so we have to make a choice:

We can Bail. We may believe that we’ll never reach our potential, or that work will be endlessly frustrating, and given our limited time on this planet, we want to focus our energies elsewhere. (This has been what I do. This model has helped me realize that I have little tolerance for working under a low, or even medium-height, ceiling.)

We can Bide our time. We make the best of the situation in front of us, delivering excellence within the leader’s constraints. Biding may sound defeatist, but it shouldn’t be perceived as settling. It can be a smart and pragmatic strategy of getting things ready for when the time comes and either our leader raises the ceiling, or is replaced by someone with a higher ceiling. In the podcast, we talked to Tim about telehealth, which Kaiser Permanente had been pursuing for 25 years. And if you were passionate about telehealth, you were likely frustrated, because it never caught on the way you felt it should—the organization wouldn’t invest in it and the membership didn’t seem to appreciate the convenience. 
And then 2020 happens, the world goes on lockdown, and that causes the Ceiling to be raised on telehealth. And all those folks who had been biding their time, waiting for the moment, are now center-stage.

Some bold souls may seek to Change the ceiling

As Tim puts it, this “is not for the faint of heart.” But if you are frustrated by the height of the ceiling, and you’re not content working Below it, and you’re committed to the organizational cause and so you won’t just Bail, you can try to change the ceiling. This requires diagnosing just what is depressing the ceiling, developing an argument and a plan for raising the ceiling, and then doing the hard work of education and evangelism to persuade leaders to change the ceiling. This is particularly tricky, because those leaders, over their career, have received a lot of confirming feedback about the rightness of their decisions, and now someone within their org is going to tell them that they’ve got it wrong? So, it requires delicate, incisive, and persistent communication to figure out what stories resonate with the leader and encourage them to evolve their view. 

I’m so grateful Tim spoke with us, and driving broader awareness of this framework. I’ve found it quite useful in my work helping design leaders succeed, and I’d love to hear (or read) how it works for you. 

From a VP of Design I work with:

“I had to have an intense conversation with someone on my team, who is struggling with the shift from Design Manager to Design Director. The Product Lead this Director works with has started reaching out to me again. When I dug into it with her, I found that she’s still doing the thing that Product Managers love, getting into the nitty-gritty details. But the Product Lead is still waiting for a vision statement, a hypothesis around where the experience could be going. She went too deep too fast, and hadn’t gotten alignment on strategic direction.”

When working with executive design leaders across organizations, I often hear something along these lines. Their Managers and Directors don’t know how to best spend their time, and where to focus their attention. Interestingly, I hear something similar from C-level people about design executives—they’re too focused on their team, and not the organization as a whole.

What many design leaders don’t understand is just how much their role changes, in particular, the relationships they need to have, as they advance in their career. 

Design Manager

A Design Manager is someone relatively new to formal leadership, and has people reporting into them, anywhere from 3 to 8 (any more than that, and the Manager will be overwhelmed). 

Diagram of how a manager spends their timeTheir primary orientation is downward. They’re focused on getting the most out of the team the manage, making sure they’re delivering on expectations in terms of addressing problems and upholding quality.

Their secondary orientation is sideways, working both with Design Manager peers to drive coherence across teams, and working with cross-functional peers (Product Management, Engineering), to coordinate and plan delivery efforts.

Design Director

When we promote a Design Manager to become Design Director, we often don’t communicate how this is a fundamentally different job than the one they had before. As the quote that started this post shows, many new Directors resort to the practices that helped them succeed as a Manager, but those will get in the way of their performance as a Director. 

Diagram of how a Design Director spends their timeA Design Director’s primary orientation is sideways, and not only that it’s mostly outside of Design. An effective Design Director should be spending more of their time and energy working with non-design peers and other stakeholders than with any other kind of colleague.

Their secondary orientation is downward, with a focus on managing their Managers. Their job isn’t to get into the nitty-gritty themselves, but to provide guidance and mentorship for their reports. Directors are also crucial for establishing the management culture and philosophy for their teams. But they shouldn’t need to spend anywhere near the time they used to in managing down, because, well, they have managers to handle that. 

Lastly, a Director will spend a small portion of their time managing up, to their VP and non-design leadership, keeping them apprised of what’s happening in their world, and learning overarching strategy and vision in order to make sure their organization is aligned with global goals. 

Design Executive (S/VP of Design)

When talking to CEOs, their primary concern about Design Executives is that they see themselves as a Design Leader first and an Organizational Leader second. CEOs expect Design Executives to see their cross-functional peers as their “first team.” with the design organization as their second.

How a VP spends their timeAnd in terms of time spent, it goes even farther than that. The Design Team should be where a Design Executive spends the least amount of time. Their primary orientation is sideways, toward their executive peers. This is about planning and strategy for the organization, identifying opportunities for the business and how their coordinated teams can realize them.

Their secondary orientation is up and out. It may seem counterintuitive that an executive would spend so much time engaging with a small number of even more senior executives, but that’s the reality. That’s your key audience. They’re the ones who are needed to support the plans of the Design Executive and their peers, to commit the resources necessary. “Out” may mean executive leaders outside your direct reporting chain, and in some environments it may mean key customers or partners. As a Design Executive, you now represent the company in a variety of contexts, both internally and externally.

A high-performing Design Executive should spend their least amount of time focused on matters within their Design Organization. It may take a while to get to this point—it requires a strong Design Leadership team, and effective operational practices around recruiting and hiring, staffing, performance management, quality standards, etc. But, really, a Design Executive shouldn’t need to spend much time orienting downward, because they should be able to rely on their org to get stuff done. 

 

 

This post builds on the Emerging Shape of Design Orgs.

As design organizations scale, I’ve worked with a number of design leaders who struggle with all that’s expected of them. Let’s look at the “HR Software” org I drew in the last post. 

No Time for Creative Leadership

The VP Design is a true design executive, and, as I wrote in The Makeup of a Design Executive, is expected to deliver on Executive, Creative, Managerial, and Operational leadership. The thing is, with a team this size, and particularly if it’s growing (as so many teams are), they simply don’t have the time to do it all (unless they work 60-, 70-, 80-hour weeks). And these VPs need to focus on what’s core to their role, which are the executive and managerial aspects, and so the creative leadership suffers.

Even the Design Director is spread thin—overseeing a team of 15-20 people, recruiting and hiring, encouraging professional development, building relationships with cross-functional peers. This takes up all your time, and, apart from weekly critique sessions, they don’t have capacity to provide creative and strategic leadership to their teams. 

Which Means No Time for Strategy

Design organizations are increasingly expected to contribute to product strategy, but these structures support little more than product delivery. If the team is asked to develop a vision for the future product experience 2-3 years out, how do they get it done? 

One way is to hire external consultancies. And that can serve as a good kickstart, but such relationships should be seen as bridges toward when the design org is able to conduct its own strategic practice. 

And as design orgs scale, and design leaders develop organizational authority, a common move is to create a Design Strategy group, a small team of senior designers to tackle wicked problems outside of the constraints of business as usual. It may look something like this (building on the depiction of the growing design org from the last post):

Scaled design organization with Strategy team tacked at the end(There’s an argument to be made that the Strategy Team could be a pillar of the Platform team. The point that follows wouldn’t really change.)

Separate Strategy Teams within Design Orgs suffer the same problem that any separated team has—getting traction. Now, looking at the diagram above, you could say the same about the Platform team, but in that case, the Applications teams all understand why integrating with Platform makes sense—the Application teams can focus on the higher order work specific to their business area, and move faster. 

Now take the perspective of an Application team. That Strategy Team gets to do fun vision stuff, play in a space with little accountability, and then what… tell us what to do? And if we try to work with the Strategy Team, we’re told that they’re looking at broader, end-to-end experiences, and don’t want to be confined to any particular business area.

And so the Strategy Team gets frustrated because while folks may get excited about their ideas, it’s not clear how they get purchase within product development.

Two Birds (Creative Leadership and Strategy) and One Stone: The Shadow Strategy Team 

So, scaling design orgs have a problem. The acknowledged leaders (executives and directors) don’t have the bandwidth to provide the strategic and creative leadership expected of them, and necessary for the optimal effectiveness of the team. Building a separate Strategy team addresses some of this, but is typically too removed from the actual work to make an impact.

A solution lurks within the Emerging Shape of Design Orgs, with the addition of Super Senior ICs . Design organizations are increasingly hiring Principal Designers and Design Architects, as shown in this diagram (click/tap to enlarge).

Scaled org with Super Senior ICs added

Design Architect. Reporting to the VP of Design, they have no managerial or operational responsibilities, and so are able to focus on creative and strategic leadership. I’ve written this job description a few times over the past couple years, and here is what the “Responsibilities include…” section looks like:

  • Provide creative and strategic leadership for design and throughout product development
  • Advocate for user-centered design best practices within product development
  • Partner with product and engineering leaders across the company
  • Spearhead the development of experience-led product vision across the entire product suite
  • Provide guidance and direction for key ‘horizontal’ activities such as Design System development
  • Create strategic design deliverables such as strategy decks, customer journeys, visions of future experiences and evangelize these cross-product “blueprints” across teams
  • Build and maintain a framework for establishing and assessing design quality
  • Connect design with business value
  • Work with design, research, program management, and product leaders on process for product development

Principal Designer. This role is similar to the Design Architect, just within a specific business area, reporting to a Design Director. The primary difference is that they are also involved with design delivery, playing a very active role in design direction and critique, and occasionally serving as a “big project Team Lead,” spearheading important and challenging new product development.

The Shadow Strategy Team. With a Design Architect and Principal Designers in place, you now have the constituents of your Shadow Strategy Team. Instead of a separate group of strategic designers, they are woven into the fabric of the producing design organization.

The trick is, how to get them working as a team? That’s primarily the responsibility of the Design Architect, with leadership support from the VP and Design Directors to protect some of their time for organization-wide efforts. At a minimum, this team meets weekly to share what’s happening in their worlds, and to ensure efforts are connected across the end-to-end experience. Occasionally, the Design Architect may engage Principal Designers on vision and strategy work, with the benefit being that these Principal Designers ensure that the vision is grounded in the reality of the business areas.

Recapturing some of the Dream of UX

A common frustration among digital designers is how their practice has been reduced to production. I think a reason for this is that our organizations lacked creative and strategic leadership—we assumed it was coming from the executives and directors, but they were too busy just keeping things going. So it just wasn’t happening.

By having roles within this explicit focus, these super-senior practitioners provide can recapture the untapped potential of thoughtful, intentional design. 

The New Yorker just published an interview with tennis legend Billie Jean King, where she discusses establishing women’s tennis as a global money-making sport.

The whole interview is a mini-masterclass on leadership. From the recognition of the importance of relationships, to the specificity of her vision (equal pay), to the relentless politicking she did behind the scenes to get everyone on board, this interview contains more wisdom about leadership than most books. 

What spurred this post was this passage, which I’ve… slightly altered:

I feel like most of the designers do not understand the business side of things. Designers say, What should I do? What should I learn about? I go, Learn the other side of the story—learn the business side. Most designers just want more money. And I’m, like, Just understand their side, so when you sit down to speak, and have dialogue, you actually have some understanding and empathy for them. And, if you can show that, I think they’ll start to think about you in a different way as well. It’s just about relationships—everything.

(Okay. She didn’t say “designers.” She said, “athletes.” But, literally, that’s all I changed.)

This quote reveals just how universal this is. For anyone to succeed in business, they need to learn the business side. And when a non-businessperson invests some time and energy in doing that, the businessfolks will pay attention.  

Finding Our Way, the podcast Jesse and I conduct, is going on hiatus until about autumn. In our most recent episode, we reflect on the conversations we’ve had, and I thought I’d pull some key ideas from that, and dig into them here.

Perhaps the key tenet that emerged from the conversations in Finding Our Way is that “Leadership is relationship.” Even more important than having a vision is knowing how to relate to all kinds of people, getting them excited about possibilities, getting them to believe in their own capabilities, encouraging them to break down barriers between one another to achieve good things, and providing guidance for smart decision-making towards the desirable outcome.

Communication

Healthy relationships are built upon the craft of communication. Yes, it’s a craft, and one that you can develop and hone. The craft of communication encompasses

Spoken communication

Are you clear? Direct? Are you able to tailor your communication to the person(s) you’re talking to? Do you speak with confidence?

Written communication

Given the myriad places we now write, it’s crucial that you know how to shape what you write to suit the medium, the context (email vs chat vs document), the audience, and your message. 

Presentation

Leaders often have to conduct ‘one-to-many’ communication, whether in a conference room with peers, reporting out to executives, or presenting at an all-hands. How presentations are shaped drive impact, so exploit narrative and storytelling techniques, build your argument, and provide a clear rationale.   

Listening

Leaders sometimes forget that communication is two-way, particularly when practiced with the intent to build relationship. Being an active listener goes a long way to establishing bonds. 

Presence

Perhaps inferred within the prior components, but I felt it worth calling out, even if only as a reminder to myself. How do you ‘show up’ when communicating? Do you appear engaged? Are you distracted? Do you hold people’s gaze, or look away? Do you show confidence, and ‘hold the room’? Be mindful of, and intentional with, your physicality when communicating.

Information architecture

It may seem peculiar to say that a UX/content practice like information architecture is part of the craft of leadership. The logic is:

if relationship is built on communication,

that communication is very much about information (particularly in the kind of distributed, often asynchronous, reality we have found ourselves in),

and in order for that communication/information to have impact,

it must be structured and presented in a way that makes it understandable and accessible.

Such intentionality about the shape of communication suggests an architectural frame. 

When we discussed it on the podcast, Jesse extended this need for IA thinking:

[L]eaders are, of necessity, orchestrators of systems, and systems instantiate knowledge as information architecture within them. So, the IA that gets embedded and coded, baked into your systems, becomes the way that the organization understands the world. And so, it is on the leader to imbue, infuse, enrich that IA with as complex and nuanced and understanding as they possibly can.

For leaders, who seek influence and impact beyond themselves, communication is the means of wielding that influence. As such, every communication must be conducted with intent and consideration. It’s exhausting, but it’s just part of the deal.