Long deliverables

I was about to launch into my normal rant about how 30-page research presentations and enormous PowerPoint decks full of qualitative data are horrible wastes of time and how they must be avoided at all costs, but I’m tired of giving that speech. Instead, I sat down with the person and started asking questions. What I came up with was this framework.

At the start of any project, or when entering a new project, I always spend a considerable amount of time on some kind of research. Whether that is combing the internet for related research (mining data from documents), reading blogs, articles, case studies, becoming familiar with the full range of competitors products or more formal methods like interviewing users. I attempt as quickly as possible to become as much of an expert as I can be within this new realm — this way I feel I can give a greater contribution and perhaps use this data to inform design. But most companies I have worked with don’t have a robust system for sharing this knowledge and it seems selfish to keep it all to myself (and rather selfishly I also want to give teammates some indication that I did this work in the first place), so I end up writing long briefs with all the accumulated knowledge. I’m received some push back to this habit, as many people don’t have the time to read pages of briefs.

I feel that combining illustration with hyper-summaries would help but my poor illustration ability would only make the results less clear. I’m still working on an ideal solution that works for me and the people I work with.

Laura Klein has some ideas on how to organize your ideas on the topic in her article Creating effective UX research deliverables.