One Manager’s Personal History
Imagine you are a freshly minted graduate student from one of Northwestern University’s old cinder block buildings with the pale green paint on the walls, the smell of years of classes, and the beat-up furniture in the lab and the graduate student offices. In a blink of an eye, you are transported to a glass box building designed by Eero Saarinen, walking down a hall lined with private offices to talk with your new boss (see
Figure 1.1). You have just been transferred to her team and you are about to have your first meeting. She has a big reputation, both in your field as well as among the human factors community at AT&T Bell Labs where you have just landed a job. As she sits behind the desk, it seems a lot larger than it probably is. You ease into the guest chair, anxious about this conversation and wanting to make a good impression. She turns to you and asks “So when do you want to sit in
my chair?” What a question! It not only changes the way you have thought about your career, but the way you see yourself. Up until then you have been defining yourself as a researcher who only recently was planning to be a professor, and she is asking if you want to become corporate. One day you are happy as a member of the technical staff studying people, designing things, and solving problems, and the next day you are wondering what it would mean to lead a team and make big things happen.
This particular boss, Judy Olson, was my third boss in two years, and in many ways I was still finding my place within what was then considered the biggest company on Earth (
Kleinfield, 1981). It was thrilling to be one of the “wizards” of Bell Labs (home of the transistor, the laser, fiber optics, the solar cell, speech synthesis, radio astronomy, and the Princess Phone) and speculating about the mark I would make at this company. Judy is now the Donald Bren Professor of Information and Computer Sciences at UC Irvine, but at that point had recently arrived at Bell Labs from the University of Michigan.
Her question had more impact than she realized. Earlier in my life I had been a manager trainee, but had explicitly given that path up when I entered graduate school where I focused on teaching and research. The last thing on my mind was managing people. Judy’s question opened another possible path and raised the questions: “Do I have the skills and the desire to manage? What would I want to accomplish if I was managing? Do others see something I don’t yet see in myself? Do I want to do it?”
At that time within Bell Labs, many managers became managers not because they had management skills but because they had demonstrated great skill as individual contributors. Typically they had reached a level where if you wanted to make the next major jump in pay you needed to move into management. While there were efforts within the company to grow a few individuals based on their management talent, the experience of many employees was that often we were surrounded by management that were classic examples of the Peter Principle, because they had already risen to their level of incompetence. For me, management was not attractive because of the pay (after all, I was still fresh from reconciling myself to the expectation of an academic’s salary and the long pursuit of tenure); it was about the opportunity to influence and in some way change the world.
As rumors started that a more senior colleague of mine was a candidate for taking Judy’s place when she went back to academia, Judy’s question regarding management and rethinking my own path led to the question: “Why not me?”
With a new found perspective, I have to admit I could not help feeling a little jealous (fed in part by comments from some of my peers). But I turned the jealousy into motivation. To help get an independent view, I began to build more formal mentoring relationships with managers I admired, and to think about and discuss questions that went beyond the immediate designs on which we were working. These questions became more strategic and were about defining the direction for the work. Many of those conversations happened over beer after racquetball with several of those mentors.
Moving into a lead role at Bell Labs was an opportunity to practice managerial skills. The joy was in the responsibility and the chance to think bigger. With the role the problems were more challenging. Because one person alone could not solve them, a team had to be created. My second manager gave me a piece of advice that I still follow. His recommendation was based on where he saw my strengths and where I was energized. He argued that I should get in the middle of apparently impossible problems, figure out how to make sense of them, come up with creative solutions, and drive them to closure. The most interesting problems often require being a lead or a manager in order to solve them. You need to assemble, grow, and leverage the talent that enables you to rise to the occasion. Furthermore, it is simply fun to work together to come up with and flesh out innovative ideas in the course of solving a problem.
When speaking to students as part of career panels, one of the top questions asked is some variation of whether to pursue an academic career versus a career in a corporation. Once students start their career in a corporation, their next question is usually whether they should try to become a manager. Recently at a retreat for the DUB group at the University of Washington (this group works in the area of human computer interaction), the question about becoming a manager came up again. In one of the breakouts, a graduate student asked what it means to be a manager of a user experience (UX) team in a large corporation, especially an engineering organization with all of the implied cultural tensions.
For many of us the joy of being a manager is not about power. It is not about money. It is not about the politics. I find it is about impact. It is about solving problems and accomplishing things that you cannot do by yourself. It is about having partners in achieving something important that you believe in. It is about working with great people who share a vision and passion for reaching the goal and helping enroll them in that vision and stimulating that passion. It is about playing in the creative world of design, as well as in the domain of emerging technology where everything seems possible. It is about being the person who reaches across roles and boundaries and makes the idea work.
Since starting my career, I have had many management roles. At Bell Labs, after moving from researcher to manager of a small human factors team, I was eventually asked to manage a broader set of responsibilities. At that time, to move up the management ladder you needed to demonstrate generic management skills and prove you could manage any discipline. The career path I was encouraged to pursue by more senior managers was managing a human factors department. To show I could do the job, I accepted an offer to manage the systems engineering and project management work for the 800 and 900 families of
services at AT&T. This included project managing the human factors work from the team that I had previously been responsible for, which was directly managed by Mary Carol Day. As both a friend and a colleague from when we worked together on a project a few years before, I was looking forward to working with her and making even better things happen for this critical part of AT&T’s business. The 800 and 900 families of services accounted for a major portion of AT&T revenue at the time, and they had just lost much of it to MCI. Unfortunately, after a few months in my new role (and despite having very talented engineers on my team) I discovered I was not exactly bounding out of bed looking forward to working on systems requirements and communications protocols. I was most excited creating and facilitating new feature ideas and visiting Mary Carol and hearing about what her team was doing with the user experience. This lack of excitement at work was one of the things that caused me to search for a challenge that was closer to my heart. My wife and I had a baby on the way, and I realized that I was not all that excited about raising a child in a town that raffled off Jaguars to raise funds for the local high school. It was time to re-center myself and my family.
The next opportunity came from Joel Engel at Ameritech (one of the Baby Bells emerging from Divestiture and covering the Midwest). He was charged with forming Ameritech’s version of Bell Labs, since Bellcore — the research lab created to serve all the Baby Bells — was not able to meet Ameritech’s unique needs. Joel, while an engineer, had managed a human factors department at one point in his career. He was an amazing man who held patents on some of the basic technologies that enabled the modern cellular network. He visualized a science and technology department with senior directors for each of the technologies that represented the future of the business. Because of his background, however, he also believed that user issues and needs were as critical to the future of the business as the technologies, so he was looking to hire a Senior Director of Human Factors. In
Chapter 3, I will talk about the importance of champions. Joel was clearly one of those champions who created an environment that allowed our group to impact the transformation of a major corporation.
I accepted Joel’s offer. This position allowed me to hire anyone I wanted, I had a virtually unlimited budget, and I could define the work plan for the organization. Since then, I have never been in another position with such an opportunity to demonstrate what user experience can deliver. Over time, we became so successful that when one of the senior directors who had engineers working on several of the emerging technologies most related to creating new user experiences (e.g., AI, speech processing, and image and video processing) left, his team was combined with mine. With the added engineers, we were in a position to research and uncover new applications, incubate them, and then deploy them — even as we continued to support a variety of new Ameritech products. When the general manager was moved into the emerging cable business, I served as acting general manager of the product development organization until a new permanent general manager was hired. This spoke volumes about the excellence of the UX team’s work, the impact it was
having on the business, and how the business came to see the skills of the team as being a core competency enabling the business to compete.
Good things have a way of ending, however, and as the direction of the company changed (later to be taken over by SBC), I moved to US West Advanced Technologies. I became a distinguished member of the technical staff — an individual contributor responsible for helping US West move into the e-commerce area. In
Chapter 7 I will talk about the importance of keeping yourself fresh, and while it was exciting to manage the corporate move into the Internet and interactive television at Ameritech, I found I did not have the skills that my team members had who were working on the projects directly. I wanted to get hands-on experience with the Web so I could provide meaningful coaching and advice as a manager. Not long after, however, I was asked to take over management of one of the human factors groups, and shortly after that to become the acting senior director over the exploratory development team (including my former human factors team). When a new head for US West Advanced Technologies was found, I went back to managing the new media design and usability team.
Once Qwest acquired US West and the handwriting was on the wall for the eventual demise of Advanced Technologies, I left to become a Director of Information Architecture for Sapient. This was during the explosion of the Web and Sapient had a unique user experience culture, with a Chief Experience Officer (Rick Robinson) and a Chief Creative Officer (Clement Mok) advising the CEOs. It is one thing to have a champion for user experience, but when you have executive UX people whispering into the ear of the CEO, and driving their experiences and perspectives into the strategic conversations that happen at the most senior levels of the company, you are really in a position to change company culture.
At US West, one of the exercises I ran to grow my team’s skills was to search the Web for great sites and to share their analyses of what made them great. Sapient was the company producing most of those sites, so it was particularly exciting to join that team. Sapient had attracted some of the best talent in the industry and was producing many of the most innovative and effective Web sites among the Fortune 500 companies. Within Sapient I looked after information architects who were distributed across the western United States in a matrixed reporting organization (the individual information architects reported directly to the projects on which they were working), as well as helping develop business and providing creative director-level oversight for specific projects.
Part of the role of a manager within a consulting firm like Sapient was to help grow the business. The reason the Sapient office had been set up in Denver was to go after business with SUN, IBM, HP, AT&T, Qwest, Lucent, and other technology companies with major offices in the area. Unfortunately, shortly after joining Sapient the Internet bubble burst and business was hard to come by in Colorado. I began to manage Sapient’s global R&D effort, including developing new practices (e.g., for mobility and speech). Additional reorganizations in response to the economic climate resulted in my becoming a Director of Research as we began to chart a new course for research within Sapient. Eventually, there was not enough business to sustain the kind of office we were trying to build in Denver. I was caught in the
third wave of Sapient layoffs. Through both the experiences of laying off and being laid off, however, I acquired a sensitivity that has made me a better and more compassionate manager.
Through an introduction by a colleague, I was hired by Microsoft. This again demonstrated the importance of a vibrant network of professional colleagues. Initially the role at Microsoft was to manage a team of usability researchers, but before the interviews were over the general manager reorganized the user experience team so that I would become its director. In this position, I had several user experience managers reporting to me and the department was organized based on discipline (design and user research). The challenge was to deal with a variety of personnel issues, and to rethink how the team was supporting a very diverse business. The team was redesigned so there were managers focused on each product area. The user experience team was inside a larger organization that focused on writing and editing technical documentation for servers, rather than positioned in engineering teams, as most of my previous roles had been. After I moved into my next position at Microsoft, one of the talented people who worked for me stepped into my position. Eventually the entire organization was restructured and the teams supporting the product groups were absorbed into those groups.
From servers I moved over to manage user experience for the Tablet PC area, and the notebook computer user experience team was placed under my direction as well. At that point I had a design team, a user research team, a content team (writers and editors), and a team of technical writers and developers creating software development toolkits. I also had a former peer who expected that I would be reporting to him, who was now reporting to me. That led to issues long after the merger of the teams. This experience convinced me that when this happens the most senior manager over the merger needs to take steps to clearly define the new situation and support the healing process.
The Tablet UX team worked on a major release of Windows and also did research to help drive a new form factor of personal computing devices. Once the target version of Windows was released, the Tablet team was largely absorbed into the Windows team and its related projects. A user experience general manager who had a background in industrial design was brought in to lead the new team. The general manager and I agreed that it was time for me to find a new gig, because someone more senior was now sitting in what had been my chair.
I moved into the Microsoft IT organization as a user experience architect. The goal was to begin transforming IT to be more user-experience oriented (
Lund, 2010). As it happened, a designer from my server team (Pam) persuaded the organization to hire her, and she became my “team” even before I arrived. She has continued to be a critical source of energy for the team, as well as consistently winning great reviews and helping us grow demand through her design work. Since then I have built a larger team, gone through downsizing, re-grown the team with a different mix of skills, and worked closely with the other major user experience team and individual user experience professionals scattered across IT as a UX community lead.
As I write this, I am in an IT organization whose goals have changed significantly from those that first attracted me. A key champion at the vice president level has moved on, and I have my fifth boss in three years. We are yet again trying to educate an organization about where user experience value is delivered and to speak to people who are mostly focused on scorecards and who view user experience as nice to have but not necessarily critical to business success.
I have invested the time to share my history in part because it illustrates the diverse paths a career in management can take as well as the need to grow a toolkit of skills that can be drawn on as work contexts change. I have been fortunate to work at a series of great companies, in a wide variety of roles — sometimes starting new groups, and sometimes finding new and better directions for the groups I was given. As one of my earlier managers coached, I find myself energized by jumping into difficult situations and turning them around. I also continue to fight for my vision of excellence and for advancing the UX field even when it conflicts with some of my managers. Sometimes it works out and sometimes it does not, but it definitely adds spice to life, and each context has had its own unique characteristics.
It is worth looking at the history of different teams for the lessons that can be applied in a new role.
Israelski and Lund (2002) wrote a history of user experience in the telecommunications industry that captured many types of groups and their fates. One older book edited by Michael Wiklund is still a great source that illustrates how major companies built their user experience programs (
Wiklund, 1994). The story of how the program at Ameritech was grown is one of the chapters in that book. It is telling and sad that only a couple of those programs still exist, although the lessons have a way of continuing to be relevant. More interesting is that many of the managers who wrote chapters in Wiklund’s book have continued to grow new groups or improve programs as they have moved from company to company. Some have moved very high in the companies they have joined, transforming the focus of those companies in ways that were important in growing their business.
Intended Audience
The audience for this book includes anyone who is leading or managing user experience groups or who may want to lead in the future. People involved in creating user experiences may wear many titles (as shown in
Figure 1.2). They share the
responsibility, however, for designing the experiences people have with hardware and software systems and products.
In the early 1980s, people working on creating user experiences were typically known as human factors professionals. They often became affiliated with a group known as the Human Factors Society. Reflecting the changing times and a more global perspective, in 1992 the Society changed its name to the Human Factors and Ergonomics Society (
HFES, 2010). The Board of Certification in Professional Ergonomics that certifies people in the field offered alternative titles for the certification; you could either be a Certified Professional Ergonomist or a Certified Human Factors Professional. Recently, however, the board has introduced a third alternative, the Certified User Experience Professional.
ACM SIGCHI (Association for Computing Machinery Special Interest Group on Computer Human Interaction) was formed in 1982 to serve the needs of those specializing in computing systems (
Grudin, 2005), and subsequently the UPA (Usability Professionals’ Association) was formed in 1991 for usability professionals. To create a user experience, however, requires a variety of skills. When UX work is discussed, people are typically thinking of designers and user researchers, but writers and editors also are critical to creating great experiences. The field may also involve specialists in interface development and testing, producers, and others. Even within each area there are specialist skills (summarized nicely in
Figure 1.2, which was created by
Clement Mok, 2000 and published in
Gain). This book is intended to be useful for
leads and managers of teams made of any combination of these skills and titles, but the focus is on the general challenges posed by teams designing user experiences.
This book is not filled with generic management advice. There are many books published regularly on how to be an effective manager. This is a book about the specific issues associated with managing the diversity of UX skills, typically in corporations that have a largely engineering culture. Managing UX teams brings unique challenges. The process of creating great user experiences involves working with both business and engineering. It requires partnering with engineering, and the kind of rigor associated with many development processes and the engineering culture is often at odds with what may appear to be more art than science, the apparent ambiguity in dealing with human feelings and needs, and the uncertainty of the creative process. Many of the challenges faced by UX managers involve creating a vibrant and effective design environment and enabling it to function within an engineering culture. It often involves working with personalities that chose a creative and user-centered path, rather than a more technical path, and yet serving as a bridge to support effective collaboration across the different cultures.
In addition, this book is not a how-to book of UX work. There will be some discussion of process, and how to sell the concepts of UX and deal with the politics as well as other topics, but again there are many excellent books that concentrate on the individual topics of practicing as a UX professional. The focus here will be on what it means to lead a UX team and the management issues faced in that position.
Two questions that you may be asking are: “Do I need to be a UX person myself?” “Do I need to have a degree in design or HCI or a related discipline?” The answer is generally no, but there are a few caveats. Most of what is described throughout this book does not require a formal background in any of the various aspects of UX. My formal training, after all, is in chemistry and psychology. There are talented designers working for me whose educational background is computer science and brilliant researchers who entered the field from business, counseling, and other areas; all could be effective managers. There are strong managers of UX who came from project management. One of the most effective evangelists and thinkers about UX topics in Microsoft’s IT organization who managed a UX team and led virtual teams on user experience topics came from field sales and support.
UX professionals do best when they feel their manager understands what they do, and can evaluate their work fairly. They often want a manager from whom they can learn more about user experience and who can contribute to the quality of their work. In general, they want to work for a manager who understands their job and advocates for it effectively and passionately. When they feel they are misunderstood, these professionals will complain they are assigned to tasks they do not particularly want to do and/or that do not make the best use of their skills. At other times, as individuals they may indeed be successful in turning their boss into a champion, but in some cases it is clear that they are rewarded more highly than user experience professionals at the same level but who report to a manager who understands their work. At some point individuals who complain are likely to run into difficulties when they try to move into another job.
Since even those trained in different areas of UX generally do not excel in every part of the user experience profession, it is clear that the knowledge and experience needed is not necessarily identical to the deep knowledge acquired by individual members of the team. Indeed, even trained UX managers are trying to hire people who are better than themselves. You should show up with passion for the user experience, and articulate an effective vision. If you are coming into the field to manage UX your goal should be to grow your own design thinking skills. Growth will come from creating a personal training program through reading, formal training, immersing yourself in the world of UX, and mentoring and coaching from professionals in the area. You will be rolling up your sleeves and taking on UX jobs, getting critiqued, and seeing the feedback of your work as it goes into practice. You will learn by doing.
Finally, one excellent point that
Dan Rosenberg (2007) made is “There are no ‘one-size-fits-all’ recommendations that can be made, because every management situation varies by company culture, product domain, competitive market place, and international location.”