Use Cases for Sales Enablement

The sales folks in your organization need to connect with customers by addressing their specific situations and problems. Arming sales with use cases and scenarios can help.

The idea is to document use cases and scenarios for all situations that a qualified lead might face. When a sales person is on the phone with a prospective customer, she then can not only tout benefits of the product, but she make those benefits tangible and clear by applying them to the prospect's situation.

Fleshed-out use cases and scenarios contain the following information that is critical to a sales person interacting with a prospect:

Description of the functional goal of the user. The name of the use case/scenario should convey what the user wants to accomplish. An explanation of the context and the reasons is also helpful.
User interactions with the product. The step-by-step description of how the user will interact with the product to achieve her functional goal.
Preconditions and postconditions. Conditions that exist before and after the user has interacted with the product as described in the use case/scenario. Preconditions and postconditions indirectly capture the nonfunctional behavior (usability, performance, etc.) of the product.

But keep in mind that most of what your sales people should be doing is first asking questions to understand the customers' situation, problems, the implications of those problems, and the need/payoff associated with the problems. Only then can they identify the use cases and scenarios that are truly compelling to the prospect.

Laura Patterson has more on use cases for sales enablement here.

Comments

Why Spreadsheets Suck for Prioritizing

The Goal As a company executive, you want confidence that your product team (which includes all the people, from all departments, responsible for product success) has a sound basis for deciding which items are on the product roadmap. You also want confidence the team is prioritizing the items in a smart way. What Should We Prioritize? The items the team prioritizes could be features, user stories, epics, market problems, themes, or experiments. Melissa Perri makes an excellent case for a " problem roadmap ", and, in general, I recommend focusing on the latter types of items. However, the topic of what types of items you should prioritize - and in what situations - is interesting and important but beyond the scope of this blog entry. A Sad but Familiar Story If there is significant controversy about priorities, then almost inevitably, a product manager or other member of the team decides to put together The Spreadsheet. I've done it. Some of the mos

Is Customer Development Pseudoscience?

The “Science” of Lean Startup Lean startup practitioners embrace the scientific method, seeking the "truth" about what business model and strategy will lead to product success. We do so by: Formulating hypotheses Crafting and running experiments to test them Learning from the experiments Iteratively feeding our learnings back into revised hypotheses Sounds pretty scientific, at least in spirit, doesn't it? Yet this process actually neglects a key ingredient in the scientists' mode of operation. To identify what’s missing, let’s examine “customer development”. Customer Development Steve Blank is one of the pioneers of the lean startup movement. He introduced into the lean startup lexicon the term “customer development”. Customer development consists of sessions and interactions with customers to test hypotheses. For example, a product manager might interview a prospect, asking if she agrees with the product manager’s hypotheses about the problem

Interaction Design: the Neglected Skill

Your product development organization has a big, gaping hole in it. (Be prepared to feel defensive as you continue reading.) One of the most important roles in product development is the role of interaction designer. An interaction designer designs how the users will interact with the product and conceptualize the tasks they perform. He decides whether, for example, the user interface will be command driven, object oriented (clicking on objects then specifying what to do with them), or wizard based. The interaction designer decides the individual steps in the use cases. Every company has one or more people that play the interaction designer role. Usually, those people have little or no expertise in interaction design. Sadly, they typically don't even realize how unqualified they are. Let's see who typically plays the role at companies. Engineer . An engineer is an expert on building what is designed. Yes, an engineer may know how to design the internal structure of the hardware

Cauvin

Search This Blog