Aha! Discovery | How to start a product discovery program that works
A repeatable product discovery program helps you understand your customers and use what you learn to build a product they love. In this 20-minute Aha! Discovery tutorial, product strategy expert James Harris shows you how to:
Recruit the right participants and schedule customer interviews
Use AI to analyze interview transcripts and identify what matters most to customers
Link customer evidence directly to your product plans
Transcript
Rose: Welcome to everyone that is joining us now. We have a quick session today, so we're just going to start diving right in. I am Rose from the Aha! product marketing team. I hope everyone that's joining us now is doing well this Thursday, and welcome to today's PM how to session. These are live sessions where our very own product managers at Aha! walk through real use cases to show you what is possible in the product and answer your questions why. So with that, I will introduce our PM host for today. James Harris, who's here with me now, is our lead product manager for Aha! Discovery and a product strategy expert with deep experience in discovery, innovation, and driving product growth.
He actually led Discovery and our early access program for Aha! Builder, which maybe some of you participated in. Builder is our newest AI product that we just launched yesterday, and he is going to share what a real customer insights program looks like in practice. So without further ado, let's dive in. I'll pass it over to you, James.
James Harris: Thanks, Rose. Hey, everybody. Thanks for joining us on your Thursday. Really happy to be here. As Rose mentioned, we launched Discovery just over a year ago now. And we did it because, you know, Discovery is one of those things that everybody agrees is important, but it's often the first thing to fall off when things get busy.
And so what I want to show you today is that research doesn't need to be this overly complicated or time consuming exercise in order for research to be effective. Rose mentioned I led the early access program for, Builder, the new tool we just launched this week. Lots of customer discovery went into that. I needed a lightweight approach that I could actually follow. So not this heavy, heavy research program that required a dedicated team. I wanted to design a repeatable customer insight process specifically for Aha! Builder, something that I could run every week without a ton of overhead, but still trust, insights, that are guiding real road map decisions for us.
So today, I'm going to show you really three things. One is, you know, how can you recruit the right participants and get interviews on the calendar as part of your research? How can you use AI to analyze, transcripts from customer conversations in order to surface, what actually matters? And then lastly, I'm going to show you how you can actually link customer evidence directly to product plans in Aha! I mean, the ultimate goal to show you today is how can you build a repeatable approach to customer discovery.
Rose: Yes. That was a big question from folks when they signed up. So thank you for those everyone.
And I also noticed looking through those questions that there are quite a few people here with us today that are brand new to Aha! Discovery. So, James, as you're transitioning and assembling the product, could you just give us, like, a high level overview of what the product does?
James Harris: Absolutely. So Aha! Discovery is, the new and innovative way to manage customer research all the way from live interviews and conversations through to adjacent research artifacts. Discovery allows you to pull all of that together and analyze that with the team centrally leveraging AI and ultimately supports the ability to visualize outputs from your research and share those with the appropriate stakeholder groups.
Rose: Excellent. Let's jump into the product.
James Harris: I'm excited to show you Aha! Discovery, particularly for those of you that are new. So welcome to Aha! Discovery. You can notice, I am in the Fredwin Cycling workspace. Fredwin Cycling is a product amongst the portfolio of products as part of Fredwin Software, the company. And you can see here each of these panels represents a research study within Discovery. You can think of a research study as a container for your research. So I mentioned the ability to import research artifacts, files, and also schedule and analyze customer conversations all under one hood.
Most of the time, you're going to do that within a study. So here, much like was the case with Aha! Builder, we're launching a new product called Fredwin Wellness, and we want to do some research to inform the road map here. So here's your study overview screen. I've got a summary overview here at the top, my research goals and assumptions, as well as a view of the pipeline of interviews that have been completed or are scheduled and are upcoming. But this begs the important question. We know that customer conversations are really important part of research. How do we target the right people? So I'm going to zoom out for just a moment and take you over to participants here.
How do you recruit participants and schedule customer interviews?
This is the global repository of participants or contacts that might be a good fit for research studies that the team is conducting now or maybe conducting in the future. And you can build this out in a variety of ways. You can create contacts pretty easily, one by one. You can import contacts in bulk via CSV. If you're using Aha! Ideas portals, any contacts that are engaging with those submitting ideas will automatically roll in to the database here. And lastly, we do also support discovery integration into Salesforce so that you can pull in contacts from there as well. Once you've done that, how do we get a little bit more pointed in targeting the right people for the right research study?
I like to use groups. So the new product that we are focused on here is around corporate wellness. So I've created groups to map each of the participants to, and I can drill down to look at who are the participants that are a good fit for research in and around corporate wellness. And I can hone that list here and easily if I, of course, do have approval to contact these folks, I have the ability to easily push them into the research study? Right? The new product for Fredwin Wellness study that we looked at briefly. So really easy to add folks into the study from the global repository. I'll take you now into the study again.
So now we pulled participants into the study that we feel are a good fit and can helpful in providing feedback through our research, how do we bring them to the table for a conversation? Well, that's easy too. Notice I've got a number of participants here that have been added to a study but have not been yet invited to an interview with us. So let's grab a few of these and I can simply click this invite CTA up here and this will pull up the invite macro or templates that I can edit and manipulate here as I see fit that does lean on some dynamic variables, the most important of which is the scheduling link.
So once I send these invite emails, the status of each participant is going to update, and they will have received this invite via email, and in the email is the scheduling link. When the invited participant clicks on the scheduling link, we're going to take them to a scheduling screen where we showcase the dates and times where folks from the research team that are part of the research study are available to meet. A participant can pick a date and time that works for them and click the schedule CTA. That is going to schedule the interview.
Rose: That's great, James. And you were using all of this for builder discovery.
Right? So you were doing a lot of those calls, but another PM or UX person could also go in there and, like, see the interviews that had been scheduled when they were happening from that shared messaging center, which is great for teams working together.
James Harris: That's exactly right. And you may be wondering, well, how can I edit and configure the scheduling screen? I'm going to take you into schedule here. This is where I can add information related to the research study? I can align the branding or the look and feel of the screen and I can also come into availability and configure exactly when the team is available week over week for meetings that we're inviting participants into.
An important call out here, I think, is integration. So discovery supports, two types of, primary integrations. One is integrations into different meeting services like Zoom and Microsoft Teams, and the other is integrations into different calendaring services like Outlook and Gmail. And the benefit of setting up those integrations is twofold. The moment if the integrations are set up, the participant clicks schedule against the date and time that works for them. The calendar invite is going to be created, added to the calendar with the participant and the researchers that are part of the study, and a meeting link from whichever service you use is going to be automatically generated, and you can use that meeting link for the meeting.
If that meeting is recorded, Aha! Discovery is actually going to fetch the recording as well as the interview transcript and pull it into the system for analysis. And so just to summarize, again, the calendar integration is going to respect all the events that are on your calendar even if they live outside of the research study. And then the meeting service integration is going to automate the meeting link creation as well as the ability to pull in assets after a conversation is completed.
Rose: Yeah. Great to touch on integration. Someone here had asked, like, how can you make, especially, the recruiting and scheduling effort way more efficient?
And you just showed how fast that process can be. And then once you've conducted and uploaded your interviews, that also can work very quickly to analyze them when you're dealing with time constraints like I know you were when working on builder discovery, and the team was moving quickly towards launch. So could you share a little more about your approach there to analyzing the conversations you were having? James Harris: Absolutely. That's a really good segue into the fun part of the demonstration, which is interviews. And so I showed you, you know, step one, how do we target the right people and pull them into a research study?
How do you analyze customer interviews with AI?
Step two, how do we schedule meetings with the right folks? Once those meetings are scheduled, then what happens? So we see an interview record has been created for each meeting that's set up with participants. After the meeting is finished, I can come in and work with Elle, our AI assistant, to analyze the conversation really, really quickly. And as Rose pointed out, this was super helpful for me. I think I did eighty to eighty five conversations with Aha! Builder early access customers, and so this saved me a ton of time. I can work with Elle to generate quickly an AI summary of the conversation.
Maybe we want to tease out some details related to sentiment. What did the participant feel good about, neutral about, negative about, or I can ask Elle to just do everything for me. This is beautiful. Elle's going to create all different types of highlights we support, summary snippets, learnings, quotes, direct question responses, and you can see just how easy it is to bring meaning to the conversation that you've had with a customer. One quick call out is you notice this is a call that was conducted via Gong. For those that don't know, Gong is actually a sales and revenue optimization platform that's quite popular.
We also do integrate into that system. The reality is meaningful product feedback can be derived from sales conversations. We heard that a lot from customers. And so for Gong, you can simply open an interview record, drop the call, link from Gong, and actually just import that call data. So similarly, the video recording as well as the transcript. I think Elle now is done helping to synthesize and extract all the important highlights from the conversation that Rose had with Jess here. I can accept or reject AI generated highlights and I can also build on them. If I want to further customize them, for example, director also mentioned this point multiple times in the conversation just to drive that home.
How do you link customer evidence to your product roadmap?
So we can edit highlights, really make them your own. And I think, you know, one of the really powerful pieces of discovery, particularly in usage alongside Aha! Roadmaps, is the ability to tie insights directly to the product roadmap, and I'm going to show you how to do that here. I'm going to click this link to Aha! Record button and I'm going to search for a feature that I think is relevant for that insight, and I'm actually going to link that insight directly to the record. Once I do that, you can see this CTA now persists on the highlight card. And if I click it, I can view the feature that I've linked the highlight to.
I can also view from within the feature where that research lives in the research tab and I see the direct quote. So I think, you know, the important call out here is the ability to make product decisions, make prioritization decisions in a way that is actually backed and directly by real customer feedback, real customer insights. So product planning meetings move from being opinion based to evidence backed. And so I think that's a really powerful piece of moving beyond, you know, just analyzing interviews and other research artifacts in discovery.
Rose: Yeah. For sure. And, you know, which James just showed us with Elle running all those AI actions, that's really great for surfacing insights at the individual interview level and then tying those to your roadmap plans.
And then once you've amassed a few interviews or maybe eighty, like James did for Builder, Can you show us what's in the works for reporting at that overall study level?
James Harris: Yeah. Great segue. So the last thing I'll show is what we're actually excited to launch next week, which is Insight Reports 2.0, kind of the next evolution of insight reports. So this is the place where teams are going to come to aggregate and summarize all of the learnings and the important insights that we've captured as part of a research study. The new reports are modular in nature, so you can add different component types that you feel are important to summarize in a report.
You can see I've got, you know, summary of our learnings here, the key challenges that we're able to tease out. Elle just makes a special appearance in each of these components. You can work with Elle to seamlessly pull in this information quickly. I've got, you know, highlights down here. I can swap and change the placement here. And so, you know, I think the real value here is not just visualizing all of your learnings in a central location, but also the ability to seamlessly share these out with different stakeholder groups. So what is also supported in this next evolution of insight reports is the ability to save multiple reports.
Maybe you want to come at the research and all the interviews that have been undertaken from a slightly different angle. Right? Maybe it's a report that you need to prepare for, you know, one stakeholder group versus another. You can do that by saving multiple reports and then easily sharing that externally in the form of a web page. So really nice way to bring all of the learnings, all the insights together under one hood and share those out easily with important stakeholders.
Rose: Yeah. Excited to get this in everyone's hands soon. Someone did just ask a question that I think is really relevant to what you're showing now, James, because it comes up with people who are transitioning to using discovery from their products or no products at all, which is what about, like, retroactively capturing customer conversations, research files, like, all of those things that have already happened but not actively captured in Aha! At the time because maybe they didn't have Aha! Discovery yet.
James Harris: Yeah. A great question. We did quite a bit of work, late last year on facilitating, a transition away from a different tool or set of tools. And so I think at the essence of, the answer is lives here. So for interviews, both interviews as well as research files, you're going to be able to bulk import conversations that have happened in the past. So old recordings, old transcripts, as well as files that are available to pull them in quickly into a research study and discovery and then take advantage of all those great analytical capabilities that we just looked at together. Rose: Yep. Exactly. We make that super efficient to do.
Alright, James. Well, great demo today. We'll cover some more questions soon. Can you share a little more than what we were just talking about internally thinking about this potentially entirely new workflow for product teams? James Harris: Yeah. So I think, you know, the relationship I mean, let's start with the excitement of Aha! Builder. I think, you know, for the first time, you know, product people with absolutely no technical background can build prototypes and real scalable business applications with no technical background. I mean, how exciting. And so I think when you look into the future and you look at the relationship between I should call it relationship potential between Aha! Discovery and Aha! Builder, it's really quite powerful because today and what I showed today is the ability to almost in a single working session move from quickly analyzing tens of interviews and hooking those into the product road map to facilitate product decision making, prioritization, and so forth.
I mean, we're moving quickly into a world where I think soon we'll be able to, in that same working session, actually move directly from insight into crafting a real prototype inside of ten minutes or building the foundation of an application that you intend to scale inside of ten minutes. And so my excitement's hard to contain there, and it's, it's definitely on our radar as we look, to strategic planning throughout the rest of the year.
Rose: Yeah. For sure. It's quite a time to work in software. So, James, I think in just about twenty minutes, you showed us a complete approach to customer discovery and a research study for a new product kind of similar to what you did for Builder.
You made it feel very doable with the help of AI, this ability to store everything in one place. We do have a few minutes left if you want to stick with us for some great questions that are coming through the Q&A. So let's get to a couple of these. I really wanted to address this one because we do hear about it occasionally, and I think have great advice here from what you've just seen. So someone here is making the business case for Aha! Discovery as a research team of one in a company with five hundred mostly technical staff. What would you advise for that person?
James Harris: Well, I have deep empathy for you because I was also a research team of one as part of the Aha! Builder early access program.
But, hopefully, you know, I answered that question throughout the demonstration. But what I would reemphasize is, you know, the simplicity of, again, moving from targeting the right people, inviting and scheduling conversations in an efficient manner all the way through to using AI or Elle to analyze findings, surface info findings at scale, and then visualizing those in an insight report. It's really easy. Hopefully, that shone through today. And I would imagine that a technical team of five hundred probably sits in a few different cohorts or groups. And so, hopefully, you can take advantage of the ability to save multiple versions of an insight report, optimize those for the different priorities across those groups.
But, yeah, that's how I'd answer that.
Rose: Thank you. Okay. One more that we didn't cover in the demo today, but maybe we have time to show it really quickly now. Someone is asking about using discovery and ideas to receive feedback and then create and manage solid customer journeys that they can share. Do you want to show off our, like, ability to add highlights to a whiteboard with that customer journey template?
James Harris: Yeah. So one of the things I didn't show today so we did look at insight report together. But within this insights tab in a study, we also have a highlight list report that basically lists all the different highlights from the various conversations that we've been having.
And I think for the use case that Rose just mentioned, right, how do we map this research and feedback directly to the different steps in the customer journey? You can actually add highlights, and I'll just add a few to a whiteboard as an object for the purposes of visual analysis. So I'm going to create a new one within our workspace, customer journey analysis. So let's push these highlights from the research study into the whiteboard so you can see these here. And I can then when I'm in the whiteboard, pull up a journey map template and add it to the whiteboard. This is really quite detailed.
And so you can start to see, you know, the power in my ability over time, right, to come and pull, you know, some of the direct points of feedback that we're receiving to the various stages, you know, which step of the customer journey is highlight x relevant for. And so this hopefully shows what's possible there.
Rose: Yeah. That's a really unique way to be able to do that. Powerful. Okay. I think let's cover one more question and one kind of related question that just came through in the chat here live. So one person is looking for ways to better align UX and product discovery through clear communication, coordination, meeting business needs for delivery.
And then on a related note to that, someone is also asking, what about the staff that isn't, say, directly involved in product management, but it's still extremely useful for them to have access to your discovery insights?
James Harris: Yeah. Okay. So the first part of that question, I think, is best or how we sort of address that use case is best shown just coming back to look at studies. So we have plenty of customers today where members of product management, members of UX make up the research team, right, for any particular research topic. It's really easy to create a new research study and then add researchers regardless of where they live in the organization to allow them to come in and collaborate on a particular research study together.
And so I think that should or, you know, I've also seen customers where, you know, the needs and preferences of the UX team as it relates to their research is slightly different to that of the PM team. Just create a separate study and optimize it for what those needs and preferences are. The second part of your question, Rose, remind me.
Rose: Yes. So someone who isn't involved directly in PM, but it's still very useful for them to have access to discovery insights. So I'm thinking like executive stakeholder, different team Yeah. Maybe. We have a lot of options to, like, share as a web page and insights report.
Share like, a highlight sharing, a highlights clip is another really awesome option we've been doing internally here from our conversations.
James Harris: Yes. Yeah. You hit the nail on the head. I mean, I already showed this, share this webpage. You can do this at the summary level across all conversations. You can also do this at the individual interview level. I didn't create one individual interview. So, yeah, I think the power of sharing is threaded pretty well throughout the product.
Rose: Yeah. Agreed. That was a follow on update we launched a little while back, which was the ability to share clips externally.
So you can share, like, two minute highlight from an interview, which can be really powerful way to get that.
James Harris: Yep. Very fast to do that. Example clip. And we'll create that. And then I can share this. Once the clip is I can done loading. I can share that in the same way.
Rose: Yeah. This has been really awesome. So I think we are at time actually with that. So great question to end on. Thank you everyone for your thoughtful questions today and for joining us. Be sure to check out our upcoming events. I shared a link to the builder event we have coming up in the chat. We have more as well that you can check out on our events page.
You will get a recording of today's session in your inbox tomorrow and see a quick survey pop up when this closes. We'd love your feedback. And, yeah, thanks, James. Thanks, everyone, and we'll see you next time.
James Harris: Thanks, Bye.