TTV is the time before customers experience the value promised after 'purchasing' the product (e.g., a free trial or a freemium).
Let's take @canva as an example. You can use it immediately. You get sucked in and don't even notice that you've just become their customer! :)
You can easily minimize #TTV by using the Bowling Alley Framework. It's like using "bumpers" to guide users to the outcome your product promises.
There are two types of bumpers:
1. Product Bumpers
Their goal is to help adopt the product within the application.
a. Welcome Messages — displayed after logging in. It's an opportunity to greet users, make them feel invited, and restate the value proposition. They can also set expectations.
b. Product Tours — Eliminate distractions and allow users to focus only on the most critical options. It commonly starts with the question about what users would like to accomplish with the product. Let your users choose their adventure.
c. Progress Bars — Help users understand what's their progress. It's a good practice to start with a substantial percentage of the bar filled in so that users can feel that they are already underway instead of starting from scratch.
e. Onboarding Tooltips — Helpful messages are displayed when interacting with application elements (e.g., mouse hover). It shouldn't be too intrusive; e.g., forcing users to click every detail on a page may not be a good idea.
f. Empty states — After the first login, many applications are tedious. There is no data specific to you; without it, it's virtually impossible to understand what value you will get once you start using the product.
There are two ways:
a) Present users required steps and prompt them to take action.
b) Prevent it from happening. Dynamics 365 Sales populates every trial with sample data. I presented it at the beginning of this article.
Conversational bumpers work to educate the users, set their expectations, bring them back to the application, and eventually upgrade their accounts. I selected the two most popular forms:
a. User Onboarding Emails — can include welcome messages, usage tips, sales touch (to upgrade accounts), case studies, communicating the benefits, information about trial expiration, or post-trial surveys. You can easily automate most of them.
b. Explainer Videos — The name is self-explanatory. Videos can generate even 1200% more engagement than text and images. I highly recommend it, especially for complex products.
Sometimes there might be some UI guy who takes care of selecting stock photos or modifying the CSS styles. But in reality, the usability of the product is not taken seriously by anyone.
So the usability sucks.
2. The Designer is engaged too late.
The Designer is asked for help when low-fidelity prototypes are ready, or worse, once the application is built. Their only job is to "make it prettier."
No matter how much they try, it's like lipsticking a pig.
• The number one book for all Product Managers.
• Most of your ideas are not going to work.
• Principles of product discovery, which results in a validated product backlog.
• You need to be very specific when identifying the most important business problems.
• Your role as a leader is to help everyone on the team achieve the competence necessary to solve those problems.
The biggest collection of PM learning resources: books, podcasts, videos, internships, free courses, conferences, frameworks, and much more (October 2022): 🧵
With over 200,000 subscribers, it's simply the number one product newsletter on this planet. You will also find a link to the world's best product podcast on the newsletter page: lennysnewsletter.com
A broad range of topics you may know from Inspired, Empowered, or Loved. Product Management, Product Discovery, Leadership, Product Marketing, and much more: svpg.com
It happens when the product manager forgets about the "Why" and becomes a waiter. 🧵
To please everyone, PM collects and waterfalls all the requirements to the team. But no matter how much they implement, it gets only worse. Features shipped in a hurry do not solve anyone's problems and do not drive the expected business results.
The feature factory.
Fortunately, you can prevent or escape that trap. Try this: