Test Marketing a Product Name

Don't ask your prospective customers if they "like" a product name or, worse, if they think the name is a "good" one. What they like doesn't matter. Since they aren't familiar with naming and branding principles, their opinion about what constitutes a good name, though interesting, is irrelevant.

Instead, ask:

1. Have you ever seen or heard the word?
2. When you read or hear this word what does it bring to mind, if anything?
3. Would the word be easy for you to learn to spell?
4. Is the word easy for you to pronounce?

Your prospective customers are qualified to answer these questions, and the answers are directly relevant to the quality of the name.

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

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

Citizendium

You're probably familiar with Wikipedia , but have you checked out Citizendium ?

Cauvin

Search This Blog