post

B2B product management

Artificial Intelligence (AI) & Machine Learning (ML)

Building Product Teams

Business Strategy

Data Driven Product Management

Digital Transformation

Diversity and Inclusion

Minimum Viable Product

OKRs

Prioritisation

Product Design

Product Research

Product Development Process

Product Ethics

Product Discovery

Product Leadership

Product Management Career

Product Strategy

Stakeholder Management

🌎 <a href="https://www.mindtheproduct.com/world-product-day/" style="color:#FFFFFF;text-decoration:underline;">Happy World Product Day!</a> Be sure to celebrate product, yourself, and your peers today! 🎉

Are you really understanding your users or going through the motions?

Why can’t we get accessibility right? Claire Bauden (SVP Global Product Design, Global Payments Inc.)

Ditch the PRD template and embrace the PRD checklist

How to price your subscription product: insights and examples

Can product operations and innovation be friends?

Footer About

Footer Contribute

Footer Get Involved

Footer Links

Mind the Product

Sunday Rewind: The good, bad, and ugly of OKRs by Jenny Herald

Product Management

Sarah Oliver

In this MTP Engage Manchester talk, <a href="https://twitter.com/lisavigar">Lisa </a><a href="https://twitter.com/lisavigar">Vigar</a> takes us through the journey &#8211; from launch proposition in September 2018, to winning a prestigious Webby award &#8211; of the <a href="https://www.amazon.co.uk/BBC-MEDIA-APPLICATIONS-TECHNOLOGIES-LIMITED/dp/B07BY9LKLG">BBC Voice for Kids Alexa app</a>. She outlines some of the lessons learned around the challenges of developing voice products and working with children, and highlights the importance of detailed user research to engage and retain a regular audience (especially when your audience includes the complexity of parents and children!)
<h2>Misunderstood MVP</h2>
There is a saying that if you’re not embarrassed by the first version of your product, then you’ve launched too late. We all understand that the intent behind that saying is that you shouldn’t invest too heavily in an initial launch &#8211; an MVP &#8211; which might reveal you’re on the wrong track.
However, the first lesson the team on this product learned was that if you are truly embarrassed by the first version of your product, then there’s a good chance you’ve misunderstood what’s valuable to the audience, and don’t have a clear understanding of what they want.
To quickly test the appetite for a kid’s voice app, the team created one game but didn’t launch it due to lesson number two: if you’re embarrassed by the first version of your product, you’ve possibly misunderstand what’s valuable to both your audience and your business. The team recognised that to find the sweet spot, you need to understand what’s valuable to both.
It turned out that the business stakeholders weren’t comfortable signing off on such a stripped-down product experience, so lesson number two led to &#8216;MVP Take 2&#8217;. The first skills which were launched on the app were actually three games, followed a month later by three stories.
<h2>User Testing</h2>
The team did multiple rounds of user testing &#8211; exploring how the app was being received, and trying to learn what level of complexity kids can handle. It’s worth remembering that the business goal was to have their users (children) regularly returning to the app, and discovering the huge breadth of content available in the Cbeebies library. They quickly learned a few valuable lessons about presenting children with options for what they’d like to do:
<ul>
<li>Children are generally capable of cognitively handling (making a meaningful choice between) just two options.</li>
<li>Children tend to enthusiastically shout out answers before hearing the full question, so the team needed to invert the questions. Instead of asking “Who do you want to play with? Andy or Justin?” they would need to give the options first; “Andy and Justin are here – who do you want to play with?”.</li>
</ul>
The initial testing was insightful, but the initial wave of usage data was highly unexpected; the app was being used, but people weren’t coming back and listening regularly. Over 70% were only using the skill once a week, and quantitative data wasn’t telling them enough, so they started to dig into other sources of data:
<ul>
<li>Skills store reviews &#8211; to see what feedback people were leaving</li>
<li>In-home diary studies &#8211; they asked users to complete these in their home environment</li>
</ul>
From these data sources, they realised there were three key problems:
<ol>
<li>Users didn’t know how much content there was</li>
<li>Users only picked from the two options presented (they didn’t know how to go “off-menu”)</li>
<li>Users are unable to find the content they want</li>
</ol>
<h2>How the team iterated the MVP</h2>
Considering that one of the team’s goals was to help more users to access the wealth of CBeebies content, this initial wave of usage data was troubling. Thankfully, they had the insights and the capability to dig in, iterate, and learn more.
<h3>Challenge Statements and Discovery</h3>
The team worked in challenge statements framed by “how might we…” questions so, based on the user insight above, they asked themselves:
<blockquote>How might we increase the breadth of content discovered and consumed by our audience?</blockquote>
This is all about Discovery, but discovery is very hard in the voice space with no imagery or physical interfaces! The next step was a workshop, bringing the multidisciplinary team together to look at research data, listening to the skill, and brainstorming &#8211; they came up with lots of post-its and ideas.
<h3>Prioritisation</h3>
Pulling together everything they generated, the team went on to do a traditional impact/effort analysis to prioritise the top three ideas:
How might we…
<ol>
<li>Tell users how much content we have</li>
<li>Allow users to “scroll” through our content</li>
<li>Support any content title (brand or character)</li>
</ol>
Taking what they learned into consideration, and thinking about the problems they were trying to solve, they also developed the following design principles:
<ol>
<li>It must make sense that only two options are presented</li>
<li>If there is a question, end the sentence with it</li>
<li>Be as precise as possible</li>
</ol>
While having those requirements was a great step forward, trying to solve for all of them simultaneously felt impossible. That was, until the team realised they could solve the problem by completely removing the “question” component of the voice interface:
<ul>
<li>They could tell the children how much content there was to play with, introduce the scrolling functionality (choose one or ask for more),</li>
<li>support any title without tying the content to a single character,</li>
<li>and lastly, be suggestive by asking “how about this option”, instead of “choose A or B”.</li>
</ul>
The navigation became instructional without a question, and this was all done in 18 words. The team tested the functionality with a group of children using a lo-fi prototype and it worked incredibly well. The children said “more” a lot, and both frequency and retention increased, although interestingly more from the stories and songs than the games.
If you’re curious about where this commitment to research and iteration led, as of February 2020 (the time of this talk), the BBC Kids Skills App has won awards, has five games and 31 stories, and the team continued to release new content every month including song playlists.
<div class="g g-21"><div class="g-single a-170"><a class="gofollow" data-track="MTcwLDIxLDEsNjA=" href="https://www.pendo.io/pendomonium/"><img decoding="async" src="https://www.mindtheproduct.com/wp-content/uploads/2024/06/MTP-Footer_ad.png" /></a></div></div>

core/freeform

Reduce risk, fail faster: Experimenting across the product development lifecycle

Iterating Your Voice Product, by Lisa Vigar

Sarah Oliver