Usage life cycle
We have all mastered different skills and tools that we care about or use frequently. Many times we forget what the initial struggles were once we reach a certain comfort level. A similar change happens when we develop products. We learn and internalize different mechanisms and logic and what was once hard becomes intuitive, and we my end up building things with overwhelming learning curves. So it’s a healthy habit to regularly take a step back and look through the eyes users at different levels of experience with your product.
The following 6 sections outline different phases of a typical usage life cycle, from somebody who has never heard of your product all the way to them becoming a power user. It is helpful to think through each phase and consider what the current user needs are, what their understanding of bitcoin and your product likely is, and how you can help them successfully navigate.
Every user starts here and most remain in this phase. At this point, they have never heard or seen your company or product before.
A user hears about the service for the first time. This could be via a word of mouth recommendation, advertising, a news article, social media, or any other channel. Whichever it may be, this exposure is usually extremely short and limited, so it’s important that the purpose and benefits of your product are clear. Users already start to form a mental model from the first contact with your product. If it appears trustworthy and well-considered from the start, they will expect their future interactions to be the same. The same applies if your product looks intimidating or buggy.
A user becomes interested in your product. Maybe they have heard about it several times or their first interaction was convincing enough that they decide to try the product. At this point, they generally understand the benefits and likely have a need for the product that they are looking to address. They evaluate your product, and you as the creator, from multiple perspectives to make an informed decision whether to move forward. “Is this a convenient way to get done what I want to do? Can I trust this product and its creators? What can I lose? Can I get out if something geos wrong?” These are some of the questions they may have and if most can be answered positively, users take the next steps.
First use #
The user tries the service for the first time. They made an intentional decision to move forward and expect to be satisfied. They are still not very familiar with exactly how your product works, and their expectations may not match what your product actually offers. Thefore it is very important to pay close attention to the design of the first-time use, also known as onboarding experience. Users should be able to quickly and successfully achieve the task they have in mind, while getting introduced to the basic concepts and best practices for using your product. This experience sets expectations for future interactions. If the first use is frustrating, users are less likely to come back as they weight off whether the trouble is worth the benefit.
Regular use #
Through repeat use, the user becomes more familiar with the service and starts using more features, in a more sophisticated manner. Their mental model of your product becomes more complete and closer to yours. Repeat use also implies that users have begun to make your product part of their lives. While first-time users are typically non-commital, repeat users have stronger expectations, while also being willing to put in more work to get the most our of your product.
Passionate use #
These are expert users with high expectations. They will express strong wishes, provide feedback and also spread the word to potential new users. Very few users actually make it to this phase, and you should have a special relationship with them. They can be your strongest promoters and also help push the product further by engaging with you and your team.
A leaky bucket #
Some users disappear at every step in the life cycle. If you understand where and why they drop off, you have a better chance at fixing those issues and hopefully getting more and more passionate, satisfied users.
There are various user research techniques that can help identify these types of issues.
The usage life cycle is based on product familiarity. Another helpful way of thinking about user experiences is to consider common user flows.