Skip to main content

Creative Calls to Action

I've mentioned before that your web site should have a call to action. I also gave some simple examples of actions. Today, while running around Town Lake here in downtown Austin, I brainstormed some new possibilities:

  • Quiz. Quiz your visitors about the product or service you provide and grade them on their performance. For example, if you sell a service, grade your visitors on how well they could perform the service themselves (without your help).
  • Audit. Assess your visitors' situations based on a short form they fill out. Give them a free assessment that shows how much they need your product or service to improve their situation.
  • ROI calculator. Based on a form they fill out, show your visitors the probable impact of your product or service on their ROI.
  • Derivative product. Let your visitors use a product developed using the product or service that you offer.
Some attributes to consider when deciding on a call to action for your web site:
  1. Modest commitment. The action should require a modest level of commitment from visitors but not be or appear burdensome.
  2. Remarkable. Ideally, the action creates word of mouth (WOM). Visitors send e-mails to their colleagues and friends with links to your site. Bloggers write about your site and link to it.
  3. Message reinforcement. The action should reinforce the key messages you want to convey in marketing your product.
  4. Gateway. The action should be a gateway to a further level of commitment that leads to buying your product.
Other ideas?

Comments

Popular posts from this blog

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

Use Case as a Black Box

Consider the following use case: Purchase Items Actor: Purchaser Precondition: Purchaser types at least thirty words per minute and has a web navigation efficiency rating of at least 40. Postcondition: For the average Purchaser acting at full efficiency, the number of seconds elapsed is no more than 30 + 20 * n, where n is the number of items purchased. The name of the use case represents a functional requirement. What does the product do, or enable the user to do? Purchase items. What are we to make of the preconditions and postconditions? What relationship do they have to the requirements for the product? Answer: the preconditions and postconditions are the nonfunctional requirements attached to the functional requirement . Another way of expressing the nonfunctional requirement would be as an attribute and associated constraint: Usability: For a Purchaser who types at least thirty words per minute and has a web navigation efficiency rating of at least 40, it shall take no

Henry Ford's "Faster Horse" Quote

You may have heard the ( apocryphal ) Henry Ford quote: If I'd asked customers what they wanted, they would have said "a faster horse". Over at the On Product Management blog , Saeed gives his take on this infamous quote. He "hates" it, and gives some compelling reasons. Saeed is spot on in his explanations. Personally, I think the quote is great, but it's a matter of interpretation. The valid point of the quote is not that it's a bad idea to facilitate a conversation with your market to better understand it. The valid points are: You must ask the right questions to get valuable answers. You must interpret the answers thoughtfully - often outside their direct meaning - to glean reliable information. Asking questions is not always the best way to "listen" to your market. (E.g., sometimes pure observational studies are more reliable.) Nonetheless, I find the quote is helpful to combat "armchair product management" in the