Ask Why - How not to do “theoretical” research
Let’s clarify one thing - theoretical research is not always a bad thing. Sometimes the timing is off, or a team may not be ready to implement things found from research. In this article, I’m going to talk about how I avoid research insights being shelved or having limited impact. Photo by Nadir sYzYgY on Unsplash1. Go for the long term instead of short term (or a combination of both) - this ensures that it’s evergreenWhen something is evergreen, it has multiple applications. It can be used by many teams or different teams. The effort to return ratio is higher. That’s not to say make everything big and broad for the sake of doing so. Figure out other use-cases for the data you are collecting. For example, at Zendesk, I needed to help a team figure out appropriate terminology and labelling. Due to the visibility of the project and the research method used, it was important to have a large sample of responses. This was done via a survey emailed to many customers. At Zendesk, we want to ensure a good experience and not bother customers unnecessarily. Since we were already sending out a survey, we included some additional questions. The responses would help us inform other broader initiatives and the product roadmap. It was piggybacking on something short term, while also servicing our longer-term needs. This bonus research can be used when teams are kicking off projects and need a general sense of our users. 2. Have a hypothesis to give direction to the projectAvoid doing endless research with no goal in mind. Ultimately your research should help to answer a short term or long term business question. It begins with turning it into a hypothesis. An example of a hypothesis might be "what needs do agents have when they are handling multiple types of customer support channels at once". It is slightly scientific in nature, but you'll notice it's not a thesis hypothesis.We used this hypothesis to design early versions of the agent experience. It helps to guide the research along. Ultimately it doesn’t always have to be a positive outcome. If research helps to determine that something is not actually a problem, it is valuable as long as it is early enough. 3. Timing is keyIdeally, you want your research to be timely so it’s not delivered too late for decisions or course corrections to be made. Sit in on planning meetings, get a good sense of long-range planning, look at trends and other sources of data (link article) so you have an idea of what direction the industry is heading. It helps teams avoid doing validation during discovery and discovery during validation. There’s a 9 month planning period that happens at Zendesk, I make sure that teams know there are researchers at hand to help them with their area and researchers get a sense of assumptions made to push that planning ahead. 4. Getting stakeholders involved early and figuring out “what keeps them up at night”Half a researcher's job is to help with the interpretation of what questions a team might need. There’s what people ask, and then the surrounding areas of that topic. A good researcher doesn’t only think about execution but also about providing value. It’s a bit meta but it’s not solely external user needs you need to discover but internal ones too. We use a planning document to outline project goals. We also conduct stakeholder interviews to find out all the context and concerns. For the research that we did to inform designing the agent experience, a lot of time was spent on speaking to multiple stakeholders and identifying them. Here are some example questions we would ask:
Also critical is using these interviews to identify an early advocate for the project and work with them closely. They should be someone who is keen on research and is more likely to put in place the findings. 5. Writing it with your audience in mindFirstly start with an executive summary. You want to summarise the essence of the project for those who are time-poor and then the details for those who want to dig in. From your stakeholder interviews, you can understand the business context also. Use the same terminology as your stakeholders. Align your findings to what they measure e.g. new users, user engagement, reduction in churn, increase in spending. One mistake I’ve learned is careful labelling your report by the temporary internal project name. It makes it harder to find later, and less likely to be referred to again by other teams. It dates the work much faster. You might want to include the feature or something more evergreen in the title itself. 6. Make sure that research is everywhereIf a tree falls and no one is around to hear it, has it fallen? By having research everywhere and it’s easy for teams to share ensures that it’s circulated widely. The more often and wide your work is circulated it’s easier to refer to and use. Consider different formats depending on how information is consumed. Present the work, record the presentation. Bring up your team members work if relevant in those early context meetings. Have those stakeholders interviewed earlier on to advocate that work. Later on, look at tying the research work to something that was released or improved. 7. Treat research as something to be continuously iterated uponFollow up with them on how they used the research, what was useful, what missed the mark. This could be done as a feedback form sent to those who got sent the research outcomes. If asking for feedback, be prepared to take it on board or experiment. Update those stakeholders on what was implemented or changed so people can believe in the process. How do you ensure your research is less theoretical and more implementable?👋 We’re trying to improve our content. Please give us one-click feedback.Did you learn something new? 🤔 Some new things, I already knew some 🤯 Totally new information to me 🗓 EventsConferencesUX Strat Online - 1-2 December 2021 QRCA 2022 Annual Conference - 12-13 January 2022 UXDX USA West 2022 - 27 January 2022 UX360 Research Summit - 8-9 February 2022 If you liked this post all about UX Research, Product, Design, career, why not share it? |
Older messages
What I wish I knew starting out as a Product Manager (PM)
Tuesday, October 26, 2021
A perspective from someone who's been doing this for some time
What our peers are focusing on in 2021
Monday, October 18, 2021
Top focus for professional development this year - public speaking
What I wish I knew starting out as a UX Researcher
Sunday, October 3, 2021
They don't teach you this in school
Template: Discovery research interview questions for B2B or SaaS customers
Wednesday, September 22, 2021
Questions to kick off your B2B or SaaS research
Running effective remote meetings
Wednesday, September 15, 2021
We're all dialling in, now what?
You Might Also Like
Pierce & Ward’s Secret Sources, Business Advice You Can’t Afford to Miss, and More
Friday, April 19, 2024
View in your browser | Update your preferences ADPro “Minimalism is not my strong suit.” So says Emma Roberts, the muse behind AD's May cover story. (Celebrities—they're just like us!)
World Press Photo Contest, Speedometer 3.0, Anchor Position, Sliding Frame, Meta Llama 3
Friday, April 19, 2024
The 5 best design links, every day. Curated by a selection of great editors. Email not displaying properly? View browser version. Sidebar April 19 2024 The World Press Photo Contest Documents War,
Car UX, DevTools Tips, CSS Patterns, iOS404, Internet Cables
Thursday, April 18, 2024
The 5 best design links, every day. Curated by a selection of great editors. Email not displaying properly? View browser version. Sidebar April 18 2024 Steering the future: a new vision for car UX
Big Tents, Pistachio Palettes, and Other Late-Breaking Milan Discoveries
Wednesday, April 17, 2024
View in your browser | Update your preferences We've had a remodel! From now on, you'll be hearing from AD PRO in your inbox twice a week—once with a deep dive into trends to watch and subjects
163 / Dieter Rams inspired Framer components, America's national parks and more free resources…
Wednesday, April 17, 2024
Product Disrupt Logo Product Disrupt Half-Monthly Apr 2024 • Part 1 View in browser Welcome to Issue 163! I'm comfortable talking to a human on camera, but talking at the camera, not so much. The
Logo System, BCWA Identity, War Robots, 84—24, 19th-Century Atlas
Wednesday, April 17, 2024
The 5 best design links, every day. Curated by a selection of great editors. Email not displaying properly? View browser version. Sidebar April 17 2024 Logo System: Explore 400+ logo designs logosystem
Emma Roberts's Home: AD100 Firm Pierce & Ward Share Their Secret Sources
Tuesday, April 16, 2024
Plus, the best exterior house colors View in your browser | Update your preferences Architectural Digest AD PRO Logo exterior of two residential buildings painted with blue trim with a brick patio and
#452: Design Workflow
Tuesday, April 16, 2024
How to choose the right idea, navigate difficult conversations and communicate design. Issue #452 • Apr 16, 2024 • View in the browser Smashing Newsletter Iyi akşamlar Smashing Friends, Design workflow
Mario & Pareto, faces.js, Sleep vs Blog, Dark Mode, DOM Folding
Tuesday, April 16, 2024
The 5 best design links, every day. Curated by a selection of great editors. Email not displaying properly? View browser version. Sidebar April 16 2024 Mario meets Pareto mayerowitz.io Discover how to
Gap, Teenagers, Artistic Intelligence, Should Designers Code, CSS in RSCs
Tuesday, April 16, 2024
The 5 best design links, every day. Curated by a selection of great editors. Email not displaying properly? View browser version. Sidebar April 15 2024 Gap is the new Margin frontendmasters.com In 2020