Search Content

WhitePapers


Oracle Magazine

Oracle Magazine contains technology strategy articles, sample code, tips, Oracle and partner news, how to articles for developers and DBAs, and more. Oracle (NASDAQ: ORCL) is the world's largest...Read More


Which CMS Is Right For Me?

If you're wondering which CMS is the right one for your organization, this comprehensive guide will take you through the various options available, detailing the pros and cons of each. Download...Read More


How to Buy a Phone System

Considering a new phone system for your business? The Phone System Buyer's Guide from VoIP-News provides you with all of the information you need to make a more informed decision. The Guide helps you...Read More


Sales Force Automation Comparison Guide

Businesses of all sizes can benefit by automating all aspects of their sales processes with an SFA (Sales Force Automation) solution. But due to the sheer number of features that most SFA solutions...Read More




View All Whitepapers

Research Question Mindmap Experiment

My project team is in the beginning stages of running some in-home research interviews right now, so I’ve been preparing the questions we want to ask and the activities we might want to try. I brainstormed, wrote lots of ideas down on stickies, asked my teammates about big themes we wanted to cover, and then carefully wrote up the top questions in a nice big list. But then I realized - the list format is really pretty unhelpful. In a good research interview, you don’t follow the list from top to bottom, you jump from topic to topic as each come up. At best you use your list to refer back to in quick glances, to remind yourself of what you need to touch on.

I asked myself, what if these questions were in an easy-to-glance-at-format, with the big ideas clearly shown, and perhaps linked in an organic way? What if the questions looked like a conversation instead of a survey? So I created a branching mind map of the same concepts in my original list. After a few false starts, I focused on three things:

  1. Use one- or two-word concepts, not full sentences
  2. De-emphasize the details, since they’re there as reminders only
  3. Create a landscape with color and placement that us visual thinkers can internalize easily

Here’s (structurally) what it looks like right now:


Over the next two weeks my team will using it as a reference during our interviews. It’s definitely not meant to be a stand-alone document, but I’m interested in seeing how it helps us. It might even be good as a worksheet to jot down notes, or a review tool to document where the conversation went. What do you think?


Related Forcebook Articles

Is the Gmail Website Twice as Fast in Google Chrom


Google suggests using Google Chrome or Firefox Browser to experience Gmail twice as fast. If you open the Gmail website in Internet Explorer, you’ll see a link at the top that says "Get Faster Gmail" - it’s placed next to your Gmail user name and...

Read more about Is the Gmail Website Twice as Fast in Google Chrome??...

Practical Limits for Configurability


The last few months, my team has been working on a sample SaaS application to demonstrate the multi-tenancy concepts I’ve been describing in my papers and blog. One of the areas we spent some cycles thinking about are the aspects of...

Read more about Practical Limits for Configurability...