A step-by-step guide with some key concepts explained

*I believe that doing an affinity diagram exercise is more efficient in a physical space with teammates scribbling notes, thinking out loud and engaging in discussions. Therefore, unless Sketch provides the ability to share/edit a file with multiple people at once, I would suggest to use the template to digitally store written Post-it notes or to showcase the process/result somewhere (i.e portfolio).

At the end of this article, there is a link to download a Free Sketch Template to create a digital version of an affinity diagram with explanations 😎

What is an Affinity Diagram?

In short, the affinity diagram shows the common issues, themes, and scope of the customer problems and needs in one place. By hierarchically grouping the data, or affinity notes that reveal the problems and needs, it acts as the voice of the customer and the issues become the basis for user requirements. With just a few tools, you can create a visual representation of large amounts of data that will help to inform your future strategy.

Throughout the research process, the team have the opportunity to learn about user pain points, motivations, and preferences in a very personal way. However, it could be difficult to track all of that data and finding patterns, especially when trying to navigate a long text document or pages of handwritten notes. This is where creating an affinity diagram helps. It allows you and your team to develop innovative solutions, drive group consensus and to organize insights.

Photo Credit: NNGROUP

“The affinity diagram is built from the bottom up, grouping individual notes that reveal key themes in your data. We let the data suggest the labels for these groups rather than starting with predefined categories. Groups are then labeled using the voice of the customer- saying what they do and how they think. This process exposes and makes concrete common issues, distinctions, work patterns, and needs without losing individual variation.”

— Karen Holtzblatt on “Rapid Contextual Design”

Do’s and Don’ts of Affinity Diagram

Do’s ✅

  • Give yourself and your team enough space and time to build a wall, filled with notes — Try to wrap up the activity in one day to allow your energy and effort to maintain critical thinking while the information and your memory are still fresh
  • Make sure everyone in the room are contributing with excitement and motivation — Don’t let an individual take control of positioning and removing notes either. Encourage your teammates to make this time worthwhile
  • Write down clear, easy-to-read notes to help understand what they mean — Provide adequate amount of information with clear direction to anyone who read the notes
  • Vote for most important/valuable/wild information or even when there are disagreements, confusions, etc— This gives you a hierarchy of importance for key notes when addressing them in the next phase of the process

Don’ts ❌

  • Don’t force the groups/categories to form unnaturally — Try to explore more and move the notes around multiple times to spark ideas
  • Don’t try to structure notes into a final form of hierarchy just yet — You might be tempted to try to make sense of the notes and how they relate to each other to picture the user’s journey. But, this should actually be done in iterations as you think and discuss amongst your team members
  • Don’t be intimidated with so much data in front of you — You don’t have to know everything just now because you and your team will start to uncover the important stuff together

Affinity Labels / Notes

Process: Yellow > Blue > Pink > Green

⚠️ Before we take a look at the Affinity Building Process and the Sketch Template for creating a digital version of the affinity diagram, let’s remember these key labels (or Post-it notes) by their colors and what they resemble.

#1. Yellow labels / notes

First, the Yellow labels are used to write down things such as:statistics, key facts, personal observations, insights from interviews, user quotesand more. Things that jumped out at you during research sessions, the “aha” moments and the stories that customers tell you are all very important to start out this process.

For the Yellow labels, it’s very important to indicate which interviewee the notes are from. For example, if there are a total of 10 interviewees who participated in your research, tag the notes (i.e U1, U2, U3…) so that it’s easily identifiable for each interviewees.

*If all the notes underneath the Blue labels are from the same interviewee (i.e U1), then it might carry less weight or it could be a chance to investigate their personal thoughts and ideas further.

#2. Blue labels / notes

Blue labels collect coherent set of notes representing a theme or work distinction. They are super important because the process of combining several Yellow labels drives the initial design thinking process. They are written in the first person as though the customer was directly talking to you.

#3. Pink labels / notes

For a set of few related Blue labels, there is one Pink label that combine the data and insights found from them. You should not have to read the Blue labels under the Pink label to figure out the key theme of the section; it should be clear in the Pink label. The language of Pink labels should also be in the voice of the customer.

#4. Green labels / notes

Green labels are the highest level of affinity label and basically, they summarize the Pink labels under them. While they can also be written in the voice of the customer but, could be more general in nature. Each Green label denotes a big piece of the user story. Most good affinity diagrams have five to eight Green labels which help chunk the information so you can find the information you are interested in quickly.

Affinity Building Process

Beginning > End
Yellow > Blue > Pink > Green

Step #1: Prepare for affinity building

Write things on the yellow labels before grouping them

Your affinity building team can include your team members, stakeholders, and anyone who understands the project focus and is interested in the data. Also, you could invite people from Marketing, Management, Business Analysts, Developers, People on related projects and more. Once you assemble the team, start writing notes down on the yellow labels silently before putting them on the wall.

Step #2: Build the affinity with yellow labels

The first thing to do is to get all the yellow labels / notes up on the wall in loose groupings. Then, by going around the room, each team member reads them find any other notes that go with ones that are already up on the wall (this is only for the initial phase). If related notes are found, put each underneath or beside each other to create a category.

Remember to not let people to randomly put stuff without reading them aloud or without appropriate groupings in the beginning. If someone disagrees, let them express themselves and discuss rather than argue. No one should be moving notes without actually saying why they would like them to be moved to a different group.

Every affinity note is supposed to contain just one idea. If an affinity note needs to be broken up because it contains more than one idea, handwrite a new affinity note on a yellow Post-it for the second idea and cross out the duplicate information on the first one. If some are tough to categorize, make use of the “junk” category to later revisit if they help in anyway.

— Karen Holtzblatt on “Rapid Contextual Design”

Step #3: Add Blue labels

The goal is to create an affinity where you never have to read the individual affinity notes underneath to understand what the columns mean. A good Blue label will both characterize the work of the users and motivate to come up with ideas around the solutions for the problems. Therefore, the Blue label is the most important drive of design thinking.

These are some of the tips that you need to follow for a good Blue label and beyond (Pink and Green).

  • Write labels as though the user is speaking to you
  • A good label captures what is group is saying in detail
  • Write clearly so that everyone can understand
  • Let the data tell the story, don’t assume
  • Reorganize the group if it’s tough to come up with a good label

Step #4: Add Pink labels

A good Pink label tells you what matters about the Blue labels underneath it. It reveals key issues in the data and should be able to tell a strong story at a glance. Therefore, Pink label should provide enough information to understand the issue.

Step #5: Add Green labels

Green label groups together Pink labels and all other notes underneath to form a coherent piece of story which is important to the project focus. While it can be more abstract and categorical (unlike Blue or Pink labels), the goal is to provide you with an overview of the key issues. Later, Green labels help chunk the information so that you can find the information you are interested in much more quickly.

Sketch Template for Building an Affinity Diagram

💾 Download the Sketch file here (Click! 👆🏻) to start building it!

The file includes…

#1. Sketch File Overview — Basic Information, Process & Explanations

#2. Symbol(Style) Guide and a Starting Point

Thank you so much for reading and if you have any questions or feedback, please comment below or reach out to me on LinkedIn. Also, follow me on Dribbble for my work.

This project was inspired “Rapid Contextual Design” which was written by Karen Holtzblatt. If you wish to know more about the idea behind this article, please read Chapter 8: Building an Affinity Diagram of the book.

https://medium.com/media/96d08ab34921bdd17986cb5c0396842f/href

Free Sketch Template for building a meaningful “Affinity Diagram” during the UX Process was originally published in UX Planet on Medium, where people are continuing the conversation by highlighting and responding to this story.

Original Sources