Pair Design Ebook free download pdf pdf
by Gretchen Anderson and Christopher Noessel Copyright © 2017 O’Reilly Media, Inc. Printed in the United States of America.
Revision History for the First Edition
While the publisher and the authors have used good faith efforts to ensure that the information and instructions contained in this work are accurate, thepublisher and the authors disclaim all responsibility for errors or omissions, including without limitation responsibility for damages resulting from the useof or reliance on this work. Use of the information and instructions contained in this work is at your own risk.
Why Pair Design?
What Is Pair Design, and How Is It Different?
By working in pairs with partners who share a common language and passion forgiving the customer a voice, designers can develop a deeper practice, and build a stronger design culture. There have been lots of different takes on this practice, and when we talk about it around the world, there are two main tenets that can be made quickly,but that are important to establish early and firmly.
Working Together, Closely
Two Defined Stances
Pair design really means being in the same room, working on the same problem, with both brains focused on the problem simultaneously for theduration of the project. In other words, theyidentify where the proposal is strong and where it needs improvement, connecting it to the problem statement and the goals of all involved parties;connecting it to decisions that have been made before.
Additionally, the synth needs to have dialectic skills, to keep discussions focused on iterating the designs and not the designers (even to the extent ofhelping the team fall out love with an idea, helping to see it critically). The role requires the designer to be detail oriented and have a strong memory, tokeep the big picture of the system, stakeholders, and users in mind as a reference for designs on the table.
Yes, some teamsstick to their role from the beginning of the project to the end. Do you want to take the penfor a while?” Similarly, a designer doing synthesis might speak up during a pause to say, “Hey, I have an idea that might help us out.”If the designers are up for it, swapping roles can keep things feeling dynamic and ideas fresh.
Aren’t These Just Tasks?
Additionally, if someone must cross thethreshold from generation to synthesis, and that transition can carry an implication that because someone felt the need to swap, the design must be bad and need fixing. (You might be interested to know that this issue — whether roles are better if assigned or adopted on an as-needed basis — was probably the biggest pointof discussion between the authors and our reviewers. So, be aware that there are widely varying opinions on this point.) A NOTE ON COLOCATIONModern business practices include team members who might be distributed geographically but collaborate online.
As the pair researches the domain, the stakeholders, and users, the pair’s roles are quite similar. Both are there to come to a detailed and actionableunderstanding of the problems to be solved; the goals to address with the design.
Analysis and Sensemaking
After completing research, user-centered designers undertake sensemaking efforts: that is, formalizing what was learned across research, craftingcommunications of these findings back to stakeholders, and building the tools that will facilitate design in subsequent phases. They keep teams focused on the big picture of why a user would be engaged with the product and the constraints implied by the context in which they use it.
Wireframing and Sketching
Wireframing in user-centered design is acatch-all term to describe the process of iterating design ideas at increasing levels of fidelity; for example, from scenarios to loose hand drawings, tosketchy screen layouts, to rendered wireframes. The synth responds to the proposed designs, testing and challenging the design againstthe known requirements and patterns that have already been established in the design system.
Other Common Activities
(Acknowledging that it is usually a messier picture than this description presents.)Efforts in detailed design are often around making the messy designs-in- progress cleaner and clearer for quick review by stakeholders but mostlymore understandable for sharing with developers. Whendesign issues arise they will jump back into the same room and modes as during wireframing, working through the problem, and then when thequestion is answered or the issue resolved, returning to document the results.
Demos and prototypes
If both the gen and the synth are working with another team member who is doing the building, they can play the role ofsynthesizer to the prototypes. Because the creation time of working prototypes can be much more time consuming than the real-time nature ofwhiteboard wireframing, it does not make sense to have someone synthesizing during the creation phases of a prototype, unless the team canwork on it in parallel.
What are the Benefits of Pair Design?
Sometimes, the synth will lead the coordination of these efforts, but it’s important that, like user research, both in the pair conduct the Having discussed what Pair Design looks like across some general phases of user-centered design, you might wonder, what does having a close partner getyou? What benefits does it convey to the team, to the design, and to the organization to justify the additional resources needed?
It Makes for Better Design Pairing improves the quality of the design ideas. Pairing forces constant iteration: idea testing and course correction
It brings to bear two brains and two stances
By having someone committed to critiquing a shared design, the ideas are continuously challenged and stress-tested by a team who is considering thepros and cons of many approaches to the design problem. These two stances mean the choices must work strategically andtactically at every one of the thousands of interconnected decisions that make up a completed design.
It Makes for Better Designers and Better Design Organizations Pairing improves the culture of design for teams and organizations. They are happier
Our clients don’t pay for us just to have fun, but it’s a good thing to ensure designers are bringing their best to the table. Pair design makes people happier because of the higher-quality work it produces, the confidence itprovides, for the shared successes and shared frustrations, and, yes, even for the human interaction.
Pair design makes it easier to focus on core aptitudes
They cross-pollinate: a mechanism for a learning organization
Gens won’t need to worry that they find It’s rare that both members of a pair were hired on the same day and are at the same place in their careers. Then, after awhile, the pair can “break up” such that the gen joins another synth and a synth joins another gen, and they will take with them what worked and whatdidn’t work, distributing the best new practices and sloughing off those that no longer work.
Pair Design Makes for a More Effective Process Pair designers keep design moving forward. Pairing avoids the problem of dueling whiteboards
When roles are unclear, it’s tempting for designers to respond to one idea with a competing idea. By havingonly one generator at a time — even if the role swaps back and forth between the pair — it means that an idea’s strengths and weaknesses can bethoroughly explored before considering a competing idea.
Pair design encourages designers to materialize ideas early
Pair design encourages designers to vocalize their rationale
For the synth to have something to respond to, the gen must put something in the world. Because the pair begins work in low fidelity and iterates higher and higher, to engage in discussions about the design, the synth still needs to hear adescription of what is being drawn and the rationale behind it.
Four Case Studies of Pair Design in Practice
This is so true that there is a legend at Cooper of one team who found pairing with each other so powerful and fruitful that when they left that company,they sought out opportunities and even interviewed at other organizations as a pair. It involves a deep collaboration between two peopleconcerning the users, the design, the constraints, the stakeholders, and other factors that affect the solution.
Cooper: Pair-Designing an App
During this stage, the pair used a dedicated room, with Chris running the sketching on a OneNote notebook while mirroring the tablet to alarge monitor in the room, and Suzy testing ideas as they go using the personas, scenarios, business goals, and research findings (see Figure 1-2 ). With so little information management overhead to deal with, the pair instead The Kurbo app launched in 2015 and won an award at the Interactions16 conference, serving as a good example of how a very structured team can dopair design over the course of a three-month, intense project.
Pivotal Labs: Pair Design with a Client
AtPivotal Labs, the roles of generating ideas versus synthesizing information are called, respectively, “Driving” and “Navigating.” In this configuration,the designer using the computer is driving the design session, while the other is navigating — consulting notes, testing ideas, checking edge cases. It’s onlyat the end of the session that we observed when Aaron explained that Michael was actually their client who was embedded at Pivotal to guide the design,learn how to pair, and build his knowledge of the design system overall.
Beyond Pairing Two Designers
GreatSchools: The Life of the Designer–Product Manager Pair
Michael, a senior product manager, and Dustin, a senior UX designer, didn’t have a lot of experience working together, or in pairs of any kind when theystarted a project to redesign Community Reviews of schools, which are a key part of the site. Because the problem was complex, and they needed others to fully appreciate the extent of changes they were about to make, they decided to extend theirexperience of pairing together to working with other teams.
Lab Zero: The Life of the Designer–Developer Pair
As Ned put it, “I need to get a full picture of the system, and I don’t want to kill ideas about the design early on by thinking too much about feasibility.” Atthe same time, Ned felt that coming together around the implications of each of their research bore a lot of fruit. “The myth of pair programming is that you’re doingeverything in lock step, but I’ve found that when big breakthroughs happen, engineers break up and work independently on the details.” And Tracey addsthat through pairing, she’s become more technical, and there are times when“no one needs to watch me tweak CSS all day.” What’s clear is that by having the ability to work closely together, even across different skill sets,has great value at times.
Where Pair Design Lives and Thrives
What Makes a Successful Pair Design Team?
Ability to think long- and short-term A key benefit of pairing is the constant testing of solutions against edge cases and details, without losing track of the bigger vision and projectplan. Having one partner explicitly be the“navigator” (versus the “driver” in the Pivotal parlance) helps the team consistently test the system and avoid creating new design patternsunintentionally.
The Agreements That Underlie Successful Teams
For Those in the Generator Role These principles help those fearlessly generating ideas be a good partner
This includes drawings that illustrate the design, but also that illustrate theconversation around it and the decisions that the team has made. I won’t let my ego get in the wayI am putting my ideas out into the world expressly so that they can be critiqued.
For Those in the Synthesizer Role These principles help those nurturing ideas to be an empathetic skeptic
I understand that if that counterargument comes too late in the process, we might not have timeto make the implied changes in the current project or phase. I will explicate the problems that I see earnestly and clearly, and work with my pair to identify what is good about the design,and nurture a solution to identified problems.
To do great work as a pair, many of the agreements are about ensuring that both members of the pair feel psychological safety; that is, it is safe to takerisks. This includes the synth of course, but also developers, stakeholders, users, and coworkers can all have great ideas for how to We will respect the design processWhen receiving feedback, we agree not to try and solve problems that are identified, live before the stakeholder, unless explicitly asked to.
What Pair Design Needs from an Organization
Some other considerations for designers considering pairing: the teams that we spoke with all recognized that some element of the success of pair had todo with the culture of the organization as a whole. Our interviewees expressed the following as being critical to the success of pair design withinan organization: The organization must have a commitment to being a learning culture because pair design can take more resources than simply putting a solodesigner on an Agile team.
Frequently Asked Questions
But if there must be more than one person in the room, as long as everyone sticks to the agreements, has only one person generating at one time, and letsone person playing “lead” synthesizer, it can be managed. Find the “genniest” designer you can and pair her with the“synthiest,” have them work through a few projects as a pair to see how it goes, evolve a process that works for your organization, smooth out thewrinkles, and become resident experts.
How Do I Hire for Pair Design?
See if he can ask intelligent questions, articulate what’sgood and what’s problematic about a design, and guide the gen in a better direction without picking up the pen himself. Ask him to write up the designin a paragraph or two at the end, including what next steps might be.
About the Authors
The practice of user experience design is always evolving, and as we’ve shown in this report, pair design is one contribution that can yield a lot ofbenefits for teams. If you are looking to organize a team of designers for your organization, or if you’re a designer who’s feeling a bit out on a limb allalone, we hope you’ll find practical things to try.
Christopher Noessel is a veteran of more than 25 years in the interaction
Christopher would like to thank the many synthesizers with whom he worked at Cooper for deliberately discussing and evolving practice with him, butespecially Suzy Thompson, with whom he worked for many years together and developed some of these early ideas into a presentation at South bySouthwest. Four Case Studies of Pair Design in Practice Cooper: Pair-Designing an AppPivotal Labs: Pair Design with a Client GreatSchools: The Life of the Designer–Product Manager PairLab Zero: The Life of the Designer–Developer Pair Where Pair Design Lives and ThrivesWhat Makes a Successful Pair Design Team?