Transcript 0:01 Hello, hello and welcome to the Dear Nikki podcast, where I answer your questions about user research, strategy, impact, AI, stakeholder management, 0:13 any of the things that we get ourselves into as user researchers, which honestly feels like quite a lot. And today's question 0:22 is very meaningful to me because it's something that I've been through quite a lot, and it comes straight from a subscriber. Yay! Thank you so much for asking questions. I really appreciate it. 0:36 And when I read this, I felt all the feels. So this person is the only researcher left at their org running their own research. They have a lot of PMs and designers who they've been 0:53 tasked with training and enabling. Most of their research org was laid off. 1:01 They don't want democratization and enablement to be their full-time job, and they want to know how to position themselves as a strategist so they get more impact and more fulfillment out of their work. So 1:13 if this is you, I'm so sorry. If this is a position that you find yourself in, it does suck. Watching most of your colleagues get laid off is horrible. 1:25 And then on top of all of that, being asked to hold up the entire research function and teach everybody else to do your job does not feel good. While I have generally worked at smaller companies, so I haven't 1:41 been a part of-- [chuckles] I actually was on the other side of a mass layoff where I was the one that was laid off, but I haven't been on the side where I've watched a large portion of my colleagues get laid off. 1:55 So I can't imagine what that is like, and I'm really sorry about that. 2:01 I have been asked, however, to focus solely on research enablement and democratization, which isn't a fun feeling when you're sitting there being like, "Oh, cool. 2:12 I've spent 10 years honing this craft and building rigor and ensuring quality, and now we just want to give it all away. Yay." So that's not a good feeling, and it's okay to acknowledge that's not a good feeling. 2:30 However, the thing that we do need to understand is that research enablement and democratization have been here since the beginning of time. 2:42 I've been in the field now for 13 years, and when I came into the field, democratization was a huge topic, and it's just been that way forever. 2:52 And I think that I've had a lot of varying views on democratization, and I've gone back and forth a lot with how I feel about it. And while the underlying tone of how I feel about it, which is 3:06 a bit like, "Why do we have to do this? This is our craft," I don't necessarily see other people democratizing their expertise, which isn't necessarily true. 3:18 There i-- there are other roles that do democratize their work. So while that is the undertone, 3:26 I accept the fact that democratization of research, especially with AI, unfortunately, is going to happen whether I like it or not. It's not really about us. It's about what people think it will get them. 3:41 And now the way that I'm trying to look at it is more through that enablement and empowerment lens rather than, "Here's my craft. Take it away from me." [chuckles] And I'm trying to see this through, okay, 3:59 if people are going to do it anyway because they feel like they're going to get something out of it, 4:04 how do I understand what they think they will get, why they think without-- they will get that, how that will help them, and then how I can help them get to their goal? And really, when you think about it, 4:18 user research in general as a craft is a support system. We support teams in making decisions. We support teams in achieving their goals. We support businesses in achieving their goals. 4:31 We support users in achieving their goals. And this is another facet of that. So 4:39 I'm going to go through a few tips on how you can ensure that not all of your time goes to democratization and enablement and how to move 4:51 more into a strategist role, because I think that this is actually a great opportunity for you to do that, and I think that as researchers, we have to move into a strategy role. 5:03 So the first thing that I would recommend doing is find out where your time is going. Take a two-week time period, like a normal two weeks, and audit that. So what that essentially looks like is 5:21 you can set it up, I would set it up in three different columns based, based on what you have told me, but you could set it up into more or less depending on your particular situation. 5:33 The first one would be, like, enablement and democratization. So this is time that is going towards reviewing guides and screeners, office hours, training sessions, answering questions, fixing studies, 5:48 essentially consulting within the function of research. The second column is actually executing on research, so doing research yourself, planning running sessions, analysis, reporting, any sort of activation. 6:03 And then the third one is strategic work. So this could look like connecting insights across teams, conversations with leadership about roadmap, roadmaps, shaping which questions get asked in the first place, 6:16 making sure that research is tied back to decisions, following up on any sort of impact tracking and metrics that you're looking at, so more strategic stuff. 6:28 So at this point, what I would recommend doing is estimate for those two weeks how much time is going into each of those. What I generally find is enablement 6:44 is probably right now the highest amount of hours, and strategic work the lowest. And it's 6:56 great for you to, even if you have a hunch that this is the case, it's great for you to just see this because then you can bring it into a conversation with your manager, or it just gives you the awareness to say, "Okay, this is how many hours in this two-week period went towards these different things," and you can start being like, "Okay, how do I then get 7:16 some of those hours from enablement into strategic work?" So this kind of goes into my second tip on putting a ceiling on enablement. 7:30 So I recommend deciding how much of your week enablement is allowed to take. For most people in this particular position, I'd aim for around 20% to 30% of your time, and then you can see it and adjust it as it goes on. 7:46 This is just a baseline. That's not a lot of time, and for somebody who might feel like almost all of their time goes to enablement, like 60%, 70%, it's like, "How do I get it down to 20% to 30%?" 8:02 And what we need to do is think about enablement as a system. You have to systematize whatever your stakeholders are trying to do and the goal that they're trying to get to. 8:14 So you know how we almost systematize products based on user journeys? You have to systematize your stakeholders' enablement into a journey map, and this is actually something that I've done before, 8:31 and at each stage of the journey, you have to say essentially how they are feeling, what they are doing, what resources they have, and to the best of your ability, try to systemize, systematize it into a happy path. 8:48 So what can that look like? That's like templates with notes inside of them, so making sure that you have templates for every single thing, including examples. So we can't just give somebody a research plan template. 9:02 We need to give people a research plan template with examples so that they can model how to fill it out. Another great thing is a self-review checklist, so 9:14 something that a product manager or designer can go through of, you know, the most common mistakes that they might make, and they can review that and then review their work based on that checklist before they come to you. 9:28 You can set up one weekly office hour. This is something that I've done, especially if you find yourself with a lot of ad hoc messages. 9:36 A one or two weekly office hou- a one to two-hour weekly office hour slot can help you a lot with dealing with a lot of issues that people might have rather than you being pulled across 97 different Slack messages. 9:55 Another thing that you can do is using AI. So whenever I do enablement practices or help teams with enablement, I recommend that they create skills for their stakeholders. 10:10 So skills are just MD files that go into the various LLMs, whether that's GPT, Claude, Gemini, Copilot. Copilot has agents instead of skills, but it's the same kind of thing. And so 10:26 what that can do is let's say that you have a research plan skill for your stakeholders. It will walk them through your research plan process. You have to put a lot of context into that, 10:36 and I recommend doing that, and I have workshops and talks and all that jazz in the resources for you to do that, in the description for you to do that. 10:49 But this can really help with walking them through areas that tend to be problematic. 10:56 So I would highlight the areas that are problematic in their journey and try and create skills so that they have a hand-holded, a hand-holding guide to help them achieve whatever they're trying to achieve. You could also 11:11 make some sort of AI reviewer with your standards. So if you were to review somebody's research plan, let's say, what would you go through? What would you be looking for? What you, would you be correcting? 11:23 And you could put that into a skill or an MD file and then have your stakeholders check with the AI reviewer before coming to you. So 11:36 that's something that I would recommend thinking about is how to systematize that. And then when you start to be able to put more time into the strategy, 11:48 you want to become the person, this is my third tip, you want to become the person who connects the dots. So 11:56 if everybody is going and running their own research, this is, this tends to happen a lot, where nobody is really looking across it. So I recommend running a monthly cross-team synthesis. This could be just you. 12:09 Or it could be across multiple people, depending on how engaged they are. 12:13 But you would gather every study, report, set of notes in that past month, look for patterns that show up in more than one team or more than one study, 12:24 or places where studies contradict each other, or questions that are still left to be asked. And then what I would do is write an executive summary for leadership 12:35 on what we're learning across the company and what it means for any bigger decisions coming up. So you could do this with AI, you could do this manually, pu- pull it all in and try and find the cross themes, of course. 12:48 But what we want to do is essentially look across for bigger pictures that are relevant to the decisions that the broader organization is trying to make. So not just one team or another team, the broader organization. 13:05 And then that has you stepping outside of that enablement role and more into that strategy role. Another way to get more deeply into strategy is to decide which questions are worth answering and when. So 13:23 this could be the form of some sort of roadmap, but it's essentially just making sure that the research that is being done is the most important research, and identifying that important research as yours. 13:40 So big, high-stakes decisions, that research should still be yours. And you could do a quarterly project, that's what I recommend doing, that you keep for yourself, that's on that big, strategic, high-stakes, high-risk, 13:58 kind of... that kind of project. But I do that by sitting down with product leads and asking them things like, "What are the biggest bets you're making in the next six months? What would you change... 14:10 what would change your mind about any of them? Where do you feel least confident right now? Where are you lacking information? What gaps in knowledge do you have? 14:17 What decisions are you trying to make that you feel like you can't?" And then this really helps you with framing those really important questions that are stuck with people, and then you can own those projects. 14:32 And those projects are usually the ones that are the most impactful because they are hitting multiple teams. 14:44 So enablement and democratization, as annoying as it is, gets you away from some of the more, like, tactical stuff and allows you to focus on these bigger, juicier questions. 14:57 And then the last thing that I would say is change how you describe your role. Once you have the audit, the systems, and 15:09 an, an understanding of the questions and a roadmap, it might be time to talk to your manager about making sure that you are able to do the work that you want to do. 15:22 So that could look like something like going to your manager and saying, "Okay, here's the role that I'm looking for. Number one, research strategy, which is owning which questions matter most. It's connecting 15:38 the dots between the decisions that are being made and the research that is being done. 15:44 There's also another one, which is insight synthesis, which is connecting research across teams and turning it into some sort of bigger input, so making sure that we're looking holistically across an organization, because everything's gonna be so siloed in a democratized research environment. 16:04 And the third could go towards research quality, and this could be, like, enablement. So templates, guardrails, using AI to help keep rigor and quality up, 16:17 and mentioning how that should turn into a system rather than, like, tasks that you are doing." 16:24 So I would go to my manager saying, "These are the three areas, and this is, like, the percentage of time that I want to be doing these. How can we do that?" 16:34 Or even better, actually, is, "I think that this is how we do that." So you could say something of, "Since the team change, I've been spending 60% of my time on enablement. 16:48 I think that the company would get more value if more of my time goes into research strategy, insight, cross-team synthesis, and one strategic study a quarter, while also systematizing the enablement work so that the teams keep getting support." 17:06 So you're at least going in with a plan. And I would talk a lot about decisions and risks in that conversation instead of studies. 17:17 So it's not really about the studies that are being done, it's about the decisions that you are enabling or that the team is enabling, and the risks that you are mitigating with your work. So there's a lot there. 17:32 Don't feel like you have to do it next week [laughs] or in the next few days. 17:38 I would recommend starting with the audit, because once you understand where time is going, it's easier to then say, "Okay, I want to change these things, and here's how I'm going to change them." 17:52 And it's totally okay for you to not want enablement and democratization to be your whole job. It's actually not a fun job at all. [laughs] It's not very fulfilling and rewarding. 18:04 What should be your job is that strategist. That's where you are valuable, at enabling d- the better decisions, at mitigating risk, at helping teams reach their goals. 18:16 It's just about finding a system to get to that place. It's not gonna happen overnight. It's not gonna happen so super quickly. 18:23 But the sooner that you can understand where your time is going and how you can start to systematize that enable- enablement work, the better off you will be in moving into a more strategic role. 18:35 Anyways, thank you so much for listening. And if you have a question that you want me to answer on a future episode, please send it my way. Subscribe to my newsletter. I answer these questions every week, at least. 18:51 And I would really appreciate any sort of like, subscribe, review, yay, all of that thing, follow, all of these things, because it really helps me with just getting the stuff out there and hopefully helping others. 19:05 So thank you again so much for listening, and I look forward to talking to you next time.