Iterative Validation Techniques Ensure You Launch Value With Your GenAI Product 

By now, Generative AI is old news. CEOs, CMOs, business owners and managers are all wondering how they can incorporate AI into products and work routines to make lives easier, generate more revenue and create better decisions with less effort.  

The Importance of Failing Fast 

Within a product-minded organization, failing fast and validating our ideas with real users is key to lean product delivery. Demoing a low-fidelity prototype to users and stakeholders can provide just enough information on specific features and experiences so that we can get feedback early on for product market fit and technical feasibility (at a high-level). Often, it is key to early detection of potential problems or misalignments with leadership – which saves time and money in the long run by avoiding costly rework and ensuring the product meets business requirements.  

Generative AI Enters the Chat Room 

Let’s be honest. Training and deploying products utilizing an LLM can be time consuming (and expensive). It depends on factors such as the size and complexity of the model as well as the computational resources that are available. A team can utilize a pre-trained LLM for a head start however, if your product requires personalization based on a particular industry, use-case, or user base you may spend a significant amount of time – a few weeks or several months – fine-tuning your LLM to meet your outcomes. 

So how does rapid prototyping and Generative AI work together in this new world of ours? How do we design and build with just enough fine-tuning in support of valuable features and user-friendly UI? 

Fake It till You Make It … Into Generative AI 

Product designers come with a whole slew of tricks up their sleeves when validating concepts with users and stakeholders. My favorite of these is something called the Wizard-of-Oz technique.  

This technique involves manually controlling the “AI” behind the scenes. The product designer acts as the hidden operator, providing predefined responses based on user input, creating the illusion of an intelligent interaction. 

Once basic interfaces are designed for users to interact with, a set of potential responses are prepared for different user prompts aka “Golden Utterances” or actions. The Product Designer will provide the response in real-time – mimicking the behavior of an AI. They can do this through text chat, voice interaction or manipulating visual elements based on what the user does.  

Side note: Many tools offer features to support this technique. For example, Figma has the capability to make real-time changes to a prototype as the user interacts with specific hotspots. 

Fine-Tuning Your Wizard’s Responses 

In support of the Wizard-Of-Oz technique, a Product Designer or Content Strategist should put some thought into how the AI would respond and what it might say when. Utilizing the following techniques are quick exercises to think through and iterate on how to shape the LLM. The goal is to prioritize creating a natural and engaging user experience, even if the interaction is not truly driven by AI. Through each iteration, insights can be fed to the AI team to further tweak their LLM. 

Pre-Scripted Interactions 

Based on the specific user journey being validated, create a script or flowchart outlining the possible written, verbal or action oriented interactions between the user and the “AI.” This script defines the responses and outcomes based on user input, simulating a basic level of intelligence. The advantages to this activity is it allows for quick feedback for a linear interaction with limited complexity. However, the more complex the user journey – the more complex the script. I recommend utilizing an Agile mindset and focusing on the smallest and most meaningful chunk of experience that produces value. 

Random Response Generation 

A pre-scripted interaction can be further refined by generating a pool of pre-written responses and randomly selecting them based on user input or prompt. This creates a sense of variation and avoids repetitive interactions when testing the flow with your users – something you should be accounting for as a risk to the experience. Doing so may create insights on tone, level of detail needed and usability.  

Validating The Data Within Your Responses 

LLM responses and prototype experiences are closely tied to the relevance and value of data. Presenting statistics or facts sometimes may be considered “eye-candy” if not relevant to the user journey. The following activities may help you find opportunities to reduce training time by utilizing a smaller dataset or simpler model architecture.  This will create efficiencies, however, it’s important to keep your users in mind. A generalized LLM may not meet your specialized user goals in all cases. Work with your Product team to understand where corners can be cut and where extra data or architecture refinement is needed. 

User Interviews and Research 

One effective way to validate the value of data is to conduct user interviews. By talking to potential users of your product or service, you can get a better understanding of their needs and pain points. This information can then be used to evaluate whether the data you are collecting is relevant and useful to your users. These example questions can help you understand what would make the most impact to your users: 

  • What are your biggest challenges or pain points related to the problem your product or service is trying to solve or their particular user journey? 
  • What kind of data would be most helpful to you in overcoming these challenges or pain points? 
  • What tools do you currently use to help alleviate some of your current challenges? 
  • How would you use this data in your daily work or life? 

In addition to user interviews, there are other methods you can use to validate the value of your data. These include: 

  • Conducting surveys or polls to gather feedback from a larger group of people 
  • Analyzing existing data to identify trends and patterns 

Card Sorting 

Card sorting is a useful technique when building an LLM prototype to gather feedback on the organization and labeling of the product or generated responses. In respect to their user journey, asking users to sort cards representing different features or generated responses into categories, you can gain insights into how users perceive and understand the product’s structure. By understanding how users perceive and organize information, you can make informed design decisions that enhance the usability, efficiency, and overall effectiveness of your product. Below are some specific ways card sorting can benefit LLM prototyping: 

Identifying Natural Categories 

Card sorting can help you identify the most natural and intuitive way to organize the different features, data points and interactions of your LLM prototype. This can help you guide user’s based on their way of thinking. 

Uncovering Hidden Relationships 

Card sorting can also help you uncover hidden relationships between different features and interactions.  

Label Clarity 

Card sorting can also be used to get feedback on the labeling of your responses. By observing how users categorize data points, you can identify labels that are ambiguous, misleading, or insufficiently descriptive so that the labels are clear and reduce confusion. 

Label Consistency 

Card sorting can help ensure consistency in labeling by identifying instances where different users assign different labels to the same data points. This feedback can be used to develop a standardized labeling system that minimizes variability and helps to reduce the overall burden of training the LLM. 

Iterate On Your Techniques 

AI and new technology will continue to disrupt how we build products far into the future. We will need to sharpen our product mindset tools and continue to evolve into the future. When building new features and products, Agile delivery and Lean Discovery techniques help teams avoid waste and validate that the product they are building is the right one.  

Our Unique When Compared To The Competition

“In order to be irreplaceable one must always be different.”

– Coco Chanel

Inspired by one of the assets described in the “Product Managers Survival Guide“, I put together a very basic Competitive Analysis Google Sheet. The sheet isn’t extremely detailed or in-depth. At this stage, we just want to get a feel for what is out in the market, how they compare to our product and if they appeal to our target users.

I chose these products because they each have a different solution for the problems encountered while travel planning.

Diaro / Evernote / GeoSpike / Polar Steps – Help me log the details / memories during my experience
Google Maps / Trip Advisor – Find the bar, restaurant, experience
Minube / Trip Advisor – Help me plan before and share my recommendations after

Where is the opportunity then? What is our “unique”?

I hypothesize that one app can custom build and recommend itineraries prior to a trip, nudge you to note memories along the way and share data-based travel details with other explorers. Based on our assumptions, our personas should embrace this vision.

Right now, a traveler is using at least two services when planning our their trip, looking for recommendations or sharing their updates. I wonder how many times a user forgets which application they saved their notes to from that trip they took over five months ago. How often do international travelers bop around town for an evening and regret not taking photos of the establishment name at the top of the menu?

The need is out there. The success of our product would depend on users actively inputting their travel data into our app, rather than across multiple platforms, and delighting them enough to encourage use while traveling.

“OK blah, vision… blah, blah, blah… what does your app actually do?”.

User stories, backlogs and client benefit analysis…. here we come!


Why Can’t We All Just Get Along?

It’s nice to have valid competition;

It pushes you to do better.

Gianni Versace

On a scale of 1 – 10, how proud do you think Adam Smith would be of that statement? (Yeah… that Wealth of Nations guy…)

How often do you find yourself thinking about your competition with such grace? Sometimes? Never? More prone to waking up in the middle of the night to a cold sweat wondering how long it would take for your hair to turn to dreads if you grabbed your bug-out-bag, changed your name to Delilah and left for Southern Ohio in the next 14 minutes? Yeah same.

Competition should scare you. To remain stagnant is to die… especially in technology. If you take some time to study your competitors – to respect them – I believe they would become an invaluable source of information for your MVP.

Unfortunately, scanning for competition is not a task that completed once and then forgotten about. Existing and potential competition must be continually monitored, reconsidered and evaluated alongside your product.

Finding your competition is not that hard. For your consideration:

  • Google it. Yeah… all those keywords you’ve been using to describe your product to other people? See what already exists in the Google Machine.
    • Super fun tip… why not setup a Google Alert and let the Googles come to you!
  • Ask your [potential] users. If they have a need for your product, they are likely fulfilling it with some kind of other service already.
    • If they are open to it – ask them what they find valuable and challenging about it.
  • Read! Blogs, magazines, comments, books, tweets, whatever. Be a sponge!
  • Listen! Networking events, TED talks, Podcasts, seminars, etc.
    • It’s like Reading but with your ears!

There you are with your hit-list inventory of competitors. What next?

First, I suggest comparing features of your product with theirs. What do they do that you don’t? What do you do that they don’t? Is the product a mature service or new to the market? It’s important to compare objectively. Just because it works for their users doesn’t mean it will work for yours. On that note…

Who are their users? Based on your research, would your users be overlapping with theirs at all, a little bit or entirely? What phase in the adoption life cycle are most of their users?

Company demographics can give you some insight on what they’re capable of delivering. Things to consider: company size, types of skillsets on their team, their financial position, location (access to talent), board of advisors (connections), etc.

What is their market share? Are they are giant or just a little guy?

Feeling pretty bad about yourself yet? Don’t. There are silver linings. As you continue to research, you may find an app or business that does something similar to you but not exactly. They might have a much larger market share and cater to a wider audience. Embrace the niche! Perhaps this is an opportunity to build a partner relationship or position yourself to be bought out (if that’s your end goal). The important thing is to gather information first and then strategize on how best to use that intel.

Let’s try this out with Share My Spots…

The Results Are In…

As I browsed through the responses from the Share My Spots survey, a few thoughts went through my head.

Ohhhh danngggg it… I didn’t realize this particular group of people all were in the same age group!

Need more dude data.

Probably should seek some people outside these demographics to validate that people with high school educations or vocational training do find travel recommendation sharing and researching important. If that hypothesis is not correct then we may have better defined our target market.

Some of the labels didn’t generate on the chart.
Below “Yelp” is “Google Maps or similar location based app”
Below “Google Documents” is “Word”
Below “Calendar Application” is “Pen / Paper / Physical Notebook”
Below “Google Keep” is “Notes in IPhone, location feature in pictures”


Yelp… that’s surprising. Is Yelp even that popular abroad? Who uses it – Americans? Probably should get some international people on this survey.

Pen and paper huh? I wonder if these users would find print functionality important. Or even a way to jot handwritten notes down. Scanning photos or notes, etc.

Checklists – good idea.

IPhone location feature for pictures – brilliant! Could this be our unfair advantage or a unique value proposition?

Ok… so no to genuine curiosity – that makes sense.

I wonder if there is a way we can group or recommend itineraries based on location and walking distance. Maybe I can slide in super casual car rental or hotel recommendation while users create itineraries based on the data.

Trust… did not think about how important this is. I wonder how we can establish that? Reviews… voting… travel experts? This could also be a barrier to engaged users if trust isn’t established with early adopters.

Seems like organization is a huge pain point.

What if there’s a way for you to visually see if someone has used your recommendation? Like a “check-in to this recommendation” feature. Or upvoting / downvoting… going back to trust here.

Love this idea of being able to attach location data to photos. Maybe actively encouraging users to use this while vacationing. New user type?

It may make sense to have “taste profiles” so a user can filter by “adventurous” “relaxing” or “honeymoon”. Also another great way to target recommendations or advertisements.

I don’t know why I feel surprised that most people said “yes”. I thought it would be a harder sell. Also great idea about ad-free.

So What Did I Learn?

A lot actually… in my opinion. Talking to actual users or potential users is a great way to define what’s important to them and what they find valuable. Obviously we want to sell them on the app and get them to download it initially but we also want active and engaged users. This survey gave me a few new ideas to keep them coming back.

A personal belief – what sets highly valued products apart from their competitors is that they don’t chase.

Of course, competitive analysis is important. You must be aware of what your rivals are doing so that you can challenge your product and adapt to meet new user demands or expectations. But NEVER should you just blindly follow a competitor’s list of features, carelessly assume they make sense for your users and implement them without a question. That makes you a copy-cat. That makes you (and this is a technical term) super lame.

Next Steps

After doing a little bit of research on some of the questions I called out above, I’ll be feeling pretty good about making some user benefit statements. However, since we brought up competitors… let’s do a little snooping.

Don’t Be A PEST(LE)

While we let our surveys marinate, I thought it might be nice to take a step back and see what kind of outside factors may give us issues should we choose to pursue Share My Spots. A PESTLE Analysis quantifies those factors from several angles and is a really great tool for brain-storming sessions.

Quick Background on The PESTLE

PESTLE is an acronym and stands for:

Political. Economic. Social. Technological. Legal. Environmental.

Each factor, as Daniel Feiman of Build It Backwards says, could be measured against the following components:

  • Potential impact (low, medium, high)
  • Time Frame (immediate, short-term, long-term)
  • Type (positive, negative)
  • Direction of Impact (increasing, decreasing)
  • Relative Importance (low, medium, high)

This second step is important because although a factor may be changing it may not be important to your business / app – or it might be important, but not for five or six years from now.

Some say a PESTLE should be done at least once a year – especially in technology. Outside factors are constantly changing.

PESTLE Thoughts On Share My Spots

Political

Data Privacy

As data privacy continues to grow in importance, the use of APIs created by companies like Google that share and store user information will likely have more hoops to jump through when utilizing their services (See GDPR).

  • Time frame: short-term
  • Type: neutral
  • Direction: increasing
  • Potential impact: medium
  • Relative Importance: medium

New Internets & Standards

Countries like China and Russia ideally would like to control what type of information gets shared within its grid. Therefore, if we were to want to sell our product to users in those countries, we would need to abide by their standards.

  • Time-frame: short-term
  • Type: negative (potentially)
  • Direction: increasing
  • Potential Impact: high (Duh… our app is for world-travelers)
  • Relative importance: high

Economic

Recessions

Am I the only one composedly absorbing podcasts about this US recession that may or may not come in 2020?

  • Time-frame: short-term
  • Type: negative
  • Direction: uuuhhhmmm… depends who you talk to
  • Potential Impact: high
  • Relative importance: low (for the moment)

Low-Budget Airlines and Restricted Seating Options

The introduction of low-budget airlines like Spirit, Frontier and WOW Airlines have been popular among consumers. To compete, other airlines, like United for example, now offer “no frills” options that don’t include any extras like carry-ons or the ability to choose your seat. Lower-cost travel opens the market up to more consumers and encourages higher volume of travel.

  • Time-frame: immediate
  • Type: positive
  • Direction: increasing
  • Potential Impact: high
  • Relative importance: high

Social

Emotions Regarding Travel

Specialized tourism and solo travel have been steadily on the rise. Low budget travel, travel-rewards credit cards, home-rentals, translation apps, travel review websites and many other services have made the world highly accessible. Although services and technologies rapidly evolve and disrupt by the season, the tourism industry is strong and not going anywhere.

  • Time-frame: immediate
  • Type: positive
  • Direction: increasing
  • Potential Impact: high
  • Relative importance: hight

Technological

APIs

Let’s say we do piggy-back on the Google framework (no decisions yet). We are then at the mercy of Google. They change – we change. However, using an existing API (and a one as sophisticated as Google’s) you won’t be rebuilding the wheel and instead layering on existing, stable technology.

Fun fact: Google’s API recently made a change to their billing structure. What once was a free service, is now a pay-as-you-go service. Any details like this would need to be considered when creating a cost-structure.

  • Time-frame: immediate
  • Type: neutral
  • Direction: neutral
  • Potential Impact: high
  • Relative importance: hight

PWA vs Apps

Progressive web apps are a newer technology promising responsive web applications that interact like native apps. One positive – not having to manage multiple application versions for different operating systems like Android and Apple. One negative – at the moment, the technology is only supported in Chrome. Are native mobile applications a thing of the past? Are PWAs a shiny waste of resources? Only time will tell.

  • Time-frame: short-term
  • Type: neutral
  • Direction: increasing
  • Potential Impact: high
  • Relative importance: medium

Legal

API Guidelines / Legalities

If Share My Spots uses an existing API (like Google’s), then we likely will need to adhere to their guidelines. Not doing so will cause fun legal headaches and setbacks. Any API decision will need a thorough understanding of what we can or cannot build and what would be considered copyright infringement.

  • Time-frame: immediate
  • Type: neutral
  • Direction: neutral
  • Potential Impact: high
  • Relative importance: high

Environmental

Climate Change

As the world’s climate continues to shift, these changes may permanently affect travel destinations making them less “tourist-friendly”. However, there’s also the chance that some areas may see a favorable change in climate which may increase travel to that particular destination. Increase in the amount and severity of storms may impact areas where travelers live – thus decreasing their likelihood to have funds for travel. This factor is highly volatile and unpredictable.

  • Time-frame: long-term
  • Type: generally negative
  • Direction: increasing
  • Potential Impact: high
  • Relative importance: low for the moment


May I Take A Moment Of Your Time?

I believe users should be involved in the entirety of the product process – conception, hypotheses, flow, wire-framing, ui and implementation. I believe product management should talk directly to users. I believe the best way of talking to users is to have in-person one-on-one conversations. Unfortunately, this post is not about in-person interviews.

I’m talking about surveys today. Surveys are are great way to get a mass amount of data from your potential user-base. As opposed to behavioral data captured in interviews, they capture what users think. Benefits include:

  • Confirming assumptions about your user-base
  • Acquiring user pains and valuable opinions you may not have been privy to
  • Validating whether this type of user is even interested in the product you’re offering
  • Gathering insight which leads to improved questions for better surveys and interviews – wooooooo! (It is a vicious cycle though)

I hypothesized that the Subject Matter Expert Planner would be my Early Adopter and would help launch Share My Spots. To quickly gain some data on these users, I reached out to a few friends who fit the profile. Each person I shared the survey with was on a varying degree of how much they fit into that persona. Some, I thought, may have even fit into Recommendation Focused Traveler. The Travel Influencer, I felt, needed their own targeted survey focusing not only on the app but also how it would affect their profession.

There are several great survey services available – some free and some not so free. For this exercise, I chose Google Forms. In addition to being effective, the setup was fairly easy.

This initial survey is my gut check. My goals were:

  • Keep it light. Don’t burden these lovely individuals that take time out of their day to answer my questions.
    • Communicate why you are asking them for this information and what it would be used for.
  • Sprinkle in some demographics.
  • Focus on pain points and be open to the fact that I may not be aware of all the pains they experience
  • Innocently throw in a question that speaks to monetization. (How can I can make money off of this application without being a d*ck about it.)

Some final thoughts when creating your survey questions:

  • Don’t ask leading questions.
  • Don’t make assumptions.
  • Do some research when formulating demographic questions.
  • Don’t overthink it. You won’t get all the information you need from one stupid survey. It’s better to send out a bad survey, get feedback and revise than fretting over the “perfect” survey for weeks.

Who is this for anyway?

For this product to be viable, I will need to understand who this product is for. At this point, I have a few assumptions.

Customer Segments

Subject Matter Expert Planner

Leslie is a 25 – 45 year old female with a successful career that offers her the flexibility to travel. When planning, she scours the internet reading Trip Advisor reviews, skims travel blogs, follows local Instagram restaurants and reads books to find the best things to do and places to visit. She has a trusted group of like-minded travel friends whom she trusts for recommendations, should she be traveling to a location they’ve already visited. They, in turn, ask her for recommendations when planning their own trips. Leslie prides herself on being organized and planning an itinerary that is in line with her goals and interests.

Jobs To Be Done:

  • Find restaurants, bars, excursions and sites of value
  • Organize these spots in a way that are easily accessible and clear on where they are located
  • Plan an itinerary using location-based information
  • Share visited locations with friends

Travel Influencers

via GIPHY

Markus (23 – 40 year old male; better known as ‘_where_is_markus_’ on Instagram) spends his time traveling the world, while growing photo envy and FOMO in his followers. Each image is artfully crafted to amaze you and subliminally sell you something. After all, this is how he makes his living. Although he scrutinizes what he endorses, Markus is fully aware that the recommendations he makes drives business to those establishments. As a result, he wants to share his lists in ways that inform and are helpful to audiences and don’t scream “this is an advertisement”.

Jobs To Be Done

  • Manage and share location-based travel recommendations
  • Monetize on new forms of revenue

Recommendation Focused Traveler

via GIPHY

Erik is a successful 25 – 45 year old male. He loves to travel but doesn’t like the tedious work of planning his trips. On the other hand, he refuses to sign up for group tours because they are usually expensive and don’t give him the freedom to go off-itinerary if the opportunity should arise.

Jobs To Be Done

  • Quickly acquire a list of recommendations based on location, interest and expense
  • Ability to access this information for relevant options while abroad

My Early Adopters

I believe my early adopters will grow out of the Subject Matter Expert planner segment. They would get the most value out of a limited MVP. Influencers would benefit from functionality around sharing and categorizing while Recommendation Focused Travelers need engaged audience data. Although important, these features would be prioritized to roll out in future cycles of the application and a bit of time will be needed to grow a user base to supply the recommendation data.

My early adopters would exhibit the following characteristics:

  • organized
  • research minded
  • desire to share knowledge
  • experienced with location based tools (such as Google Maps)

Next Steps

The summary above holds only my assumptions. My next step is to actually talk to these users to see if they would be interested in a product like Share My Spots and what type of features and data would be valuable to them.

PS – I’ll be using LeanStack’s free Lean Canvas builder to outline Share My Spot’s business plan. Linked is my progress so far.

Share My Spots – Product Vision

Hi. My name is Nicole and I’m a type-A travel planner.

Each trip makes me 1% better at planning weekend getaways, hiking treks and multi-city expeditions.

While planning I would capture results from research and recommendations in notes, shared documents and saved lists in Google Maps.

The documentation was helpful for a few reasons:

  • I found that fellow travelers would often ask me for recommendations from places I’ve travelled and I, in turn, would ask them the same.
  • I liked to capture places ahead of my trip so that I could easily reference them when I wanted a cocktail bar or a restaurant. Vacations are about relaxing – not Googling!
  • Plotting dots on a map ahead of time helped me plan my itinerary. If I knew I wanted to do a walking tour on a Thursday, I could plan to also visit a museum before it closes and stop for a quick cocktail afterwards before heading back to the hotel to change for dinner. Obviously it saves time by condensing a series of visits into one neighborhood as opposed to several neighborhoods in a day.

via GIPHY

And then came the idea…

What if I didn’t have to use multiple tools to do this? What if an application could make discovering, sharing, tracking and saving locations simpler?

The Vision

Share My Spots enables world travelers to share and discover location-based experience recommendations with like-minded individuals.

This case study will follow the journey of this product’s viability.

Timeboxing Is Your Friend

Throughout my experience in delivery I’ve dabbled in different techniques; tweaked some, lost some and added some back. My process has been ever evolving.

One thing, however, that I can’t get rid of is the idea of timeboxing a release. I believe that this leads to better decisions, better discussion and better solutions.

For example.

A product needs a new feature… let’s say… a way to share existing recipes with their friends. As long as the feature remains within budget, you can offer a multitude of ways to meet this requirement.

Premium Option 1:
Build a way to share to all major social media platforms, count the number of shares and offer the sharing functionality in a multitude of areas in the site.

Minimal Option 2:
Keep it simple by just offering a link that the user could copy-paste wherever they like.

I believe a key driver in making these types of decisions is…

via GIPHY

Yup… time.

Initially, it may seem like a simple suggestion (and worth of an eye-roll), but I’m proposing we change our mindset on time. We embrace it rather than fear the ticking clock.

What if we started setting release dates earlier in the planning process?

Early conversations with architects should focus on the problem space. Customers and leadership often offer specific solutions. However, from my experience, conversations focused on the problem we’re trying to solve keeps the solution space open and free of restrictions.

This information can be great for negotiating how time should be allocated throughout a project. If we have a pre-determined time budget of 50 hours we could have the following two options to choose from:

Solution Package 1:
Premium Feature 1 (25 hours)
Premium Feature 2 (25 hours)

Solution Package 2:
Minimal Feature 1 (5 hours)
Premium Feature 2 (25 hours)
Basic Feature 3 (20 hours)

Assembling packages like an a la carte menu, lets you assemble the best solution for your users that produce value for the customers in the time available.

I also think it empowers your team to be creative and feel a sense of ownership in the process.

What do you think? What is your driving factor when making decisions on release schedules and scope?

Benefits Analysis Google Sheet

I put together a Google Sheet to transition high-level problem-space discussions into a value proposition and prioritized feature backlog. The goal of this sheet is to put measurable metrics to each client problem/benefit so that decisions can be made based on metrics rather than emotions and gut feelings.

via GIPHY

Each benefit gets broken down by:

  • Classification: Must Have, Performance Benefit and Delighter
  • ROI: Based on some assumptions in effort and perceived value
  • Customer satisfaction, importance scores: To see how much this would impact the customer and how big of an impact you can hav
  • Opportunity Scores and high-level comparison to competition 

Once this is filled out in detail I think it’s a nice asset to have when building your roadmap.

View and download the sheet here!

I must also credit The Lean Product Playbook for a lot of inspiration lately. This book is super dreamy.