- Why do you NOT finish a craft project?
- Or DON'T get your car fixed?
- Or DON'T finish a writing project?
- Why does a prospect or customer need your product?
- What problem is he trying to solve?
- Why does the prospect or customer want to solve his or her problem?
- What does a prospect or customer want to feel when he or she purchases your product?
- What is happening in his or her life to make this problem a priority?
- Are you accomplished for today? For now?
- How much do you break down a task and decisions to consider it complete?
- Someone browses and determines what he would like to buy
- He may create a wishlist (decision point)
- Then he decides to buy – puts it into the cart
- Debates the cart and promos and the like (decision point)
- Then he completes info to purchase (decision point)
- Select the button to spend the money (decision point)
- Confirmation (done)
This is also true for functionality. Look at Turbo Tax. Turbo Tax is successful because it breaks down figuring out your taxes into simple steps. You can leave at any time and come back. You can skip around and finish sections that you have the information to complete and leave other sections blank until later. There are percent complete indicators for each section so you always know how much you really have left to do. And it tracks how much of a refund you will get – so you know that progress as well and where you could find additional deductions.
How this maps to the Customer Relationship Lifecycle
- Find out why someone wants your product – learn more about them, their motivations, and their problems. Conduct surveys, start a social listening program, interview customers – find ways to gather their input and voices. Learn not just the logistics for why they are purchasing. Learn about the emotional benefits they want to get from solving their problems.
- Invest in proper personas. I can't stress this enough. Get that baseline ready to create your journey.
- Create a journey map for the various pre-purchase processes and indicate all of the customer decisions required. This would be the minimum decisions for a process. Get customer input for additional decisions needed.
- Provide quizzes, checklists and other materials to help someone determine what their problems, challenges, and potential solutions really are. Just because a prospect is researching your product doesn't mean that the prospect really should buy your product.
- Learn the personal benefit for the customer to solve their problem as well as the personal benefit for everyone who would use the product.
- Provide checklists and related materials to help the prospect decide if your solution is right for him
- Provide materials that outline your capabilities and solution versus your customer
- Provide cost calculators to help determine monetary value
- Provide calculators to determine the time and cost it will take to use the product
- Ensure that you are meeting the emotional needs of the customer once he purchases the product – it was worth his investment and commitment to your company and product. This is more involved and requires customer research. But if this is done properly, it is worth it from the perspective of happy customers, repeat customers and referrals.
- Make sure that the features related to the user's motivation to fix the problem are easiest to complete
- Understand what it driving the need to solve a problem and offer the right assistance when it makes sense. This includes help, supporting content, reference materials, videos, and related items.
- If possible, keep functionality simple, clear and quick. It shouldn't take long to complete a task (meaning it should be familiar to use)
- Reduce the amount of training needed to start using and understanding a product
- Include status bars and indicators for percentage complete or what it takes to reach a goal provide input/insight into what’s happening. The user needs to know what is being asked of him and what to expect
- Product pricing – make sure it is in line with the severity and priority of the problem. A complex problem will take a while to buy – and solve – even if the price is low. Or at least, it should. Simpler problems can be solved more easily and directly. But there should be a relationship between the price, time to purchase, and the product cost
- Make sure, based on user motivation for why they want to use the product, that support is easily available. And it is available in formats that they prefer to use.
- Similar to product, keep steps simple and clear or include a status bar for solving problems or resolving logistical/operations issues
- Include checklists to help fix problems
- Communicate in the best way digitally – video, audio, or text. Communicate to the user the way he wants to receive communication
- To determine eligibility for special offers, make it clear what will earn you the rebate or other offer
- Understand the emotional motivation for someone to buy and use your product – and respond to your customers with empathy if they are failing to use it in some way



