Skip to main content

Explication

Explication is the process of analyzing the usage of a word or phrase and formulating a logically consistent definition that clarifies its meaning. Product managers explicate the terminology of customers to settle on the most effective way of wording product requirements and communicating with customers.

Conventional wisdom dictates a product manager should communicate in the "language of the customer". Unfortunately, there is no such single language. Different customers use words in different ways and use different words to describe the same thing. A product manager must therefore navigate this terminological landscape and determine the best words to employ in requirements and customer communications. The product manager should explicate the various alternative terms and, after deciding on an operational meaning for each alternative, select the ones that she judges customers will most readily understand.

For example, imagine your company provides Internet data centers to customers. It focuses on customers looking for high availability in their web sites. A frequently-used word among customers is "server". Yet different customers mean different things when they use the word:
  • Customer A means "the program(s) that process incoming requests and reply with content".
  • Customer B means "the computer(s) that process incoming requests and reply with content".
  • Customer C means "the conceptual aggregate of load-balanced computers and programs processing incoming requests and replying with content."
In your product requirements, how should you define "server"? In the brochures you hand out at trade shows, how should you define "server"?

Explicating the term yields the answer. However, you can only explicate a term in relationship to other terms. In my next entry, I will describe a powerful explication tool that some product managers use to model these relationships.

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

Stop Validating and Start Falsifying

The product management and startup worlds are buzzing about the importance of "validation". In this entry, I'll explain how this idea originated and why it's leading organizations astray. Why Validate? In lean startup circles, you constantly hear about "validated learning" and "validating" product ideas: The assumption is that you have a great product idea and seek validation from customers before expending vast resources to build and bring it to market. Indeed, it makes sense to transcend conventional approaches to making product decisions . Intuition, sales anecdotes, feature requests from customers, backward industry thinking, and spreadsheets don't form the basis for sound product decisions. Incorporating lean startup concepts , and a more scientific approach to learning markets, is undoubtedly a sounder approach. Moreover, in larger organizations, sometimes further in the product life-cycle, everyone seems to have an opinio

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