After conducting a survey with your analytics dashboard user groups and interviewing all of your key dashboard stakeholders, next look for themes.<\/p>\n\n\n\n\n\n\n
This is the third post in a blog series about redesigning your analytics dashboard. Start from the beginning.<\/a><\/p>\n After\u00a0interviewing your stakeholders, you will likely walk away with dozens of questions and concerns. It’s important to first understand the big picture before diving into solutions. What did you hear? What were the themes? As you redesign your analytics dashboard, ongoing\u00a0communication is critical to this process to ensure buy-in from your leadership team and stakeholders. Research<\/a> shows that 70% of all organizational change efforts fail due to lack of buy-in. Organize your findings into themes, and then present them back to the team\u00a0to ensure\u00a0your stakeholders feel heard and validated.<\/p>\n There are at least 2 approaches you can take to identify and organize all of the interview and survey findings into themes. Below are 2 example approaches you can take. Choose whichever method you or your team prefers. There’s no set target number of groups or themes. Create as many themes as it makes sense (and can reasonably manage\u2014maybe 7-10). Later, you will prioritize the themes and findings.<\/p>\n Either working alone or in a small group, record each finding in a new row in a\u00a0spreadsheet. Flag duplicates as you go, and then edit them out (now or later). Taking note of duplicates now will help with prioritization later. (What were the most common findings?) Create additional columns for other types of information, such as:<\/p>\n This information can make it easier to sort your findings to find patterns and themes. Don\u2019t worry about categorizing each finding as you type. It\u2019s important to get everything documented clearly and in one place first. When that\u2019s finished, now it\u2019s time to organize. Read each finding, then create a theme or category for it. This process will take a bit of trial-and-error, as it will take a little while to find the right label and system.<\/p>\n Creating a mind map uses the reverse process as above. The biggest benefit of a mind map over a spreadsheet is the visualization aspect. My favorite mind mapping tool is MindMeister.com. The first 3 maps are free, plus,\u00a0you can collaborate with others on the same map. To get started, it\u2019s best not to over-analyze and just jump in.<\/p>\n You will want to retain as much\u00a0detail as possible in order to hold onto the underlying intent or meaning. As you start to see patterns, it’ll be easy to group smaller themes into larger themes. Examples of themes \/ buckets:<\/p>\n When I went through this same process recently, I discovered several insights that fell outside of what would appear on a dashboard \u2014 but were very real stakeholder pain points. Outlier topics included:<\/p>\n Save these for discussion later.<\/p>\n Lead a workshop with your stakeholders to communicate all of the findings, and then prioritize them. These will become the requirements for your new dashboard.<\/p>\n\n\nWhy organize into themes<\/strong><\/h2>\n
2 ways to organize findings<\/strong><\/h2>\n
Option 1: Organize findings\u00a0in a\u00a0spreadsheet<\/strong><\/h3>\n
\n
Option 2: Organize findings\u00a0in a mind map<\/strong><\/h3>\n
\n
\n
Bucket the outliers<\/strong><\/h2>\n
\n
Next: Prioritize findings into requirements <\/strong><\/h2>\n
Related Articles<\/h2>\n\n\n