Skip to main content

Prescriptive versus Descriptive Rules

When debating terminology, I have several times run across the issue of prescriptive versus descriptive rules. A prescriptive rule states how people should use a word; a descriptive rule states how people do use a word.

For example, many people pronounce "nuclear" as "new-cue-ler". Webster's has even accepted this oddity as one among several pronunciations. But does Webster's inclusion of the pronunciation mean that it is "correct" to pronounce the word that way? I don't think so. The inclusion of the pronunciation is descriptive; they included the pronunciation because it describes how a significant portion of the English-speaking population pronounces the word. They are not endorsing the pronunciation.

Interestingly, the same sorts of issues arise in the rules of games. I have debated rules of poker, for example, with people who insist the rule they follow is "correct" because everyone seems to play that way. But when I look up the rules in an authoritative source, such as Hoyle's Rules of Games, I sometimes find that the "official" rules differ from the common way in which people play.

I favor acting according to prescriptive rules rather than descriptive rules. Discrepancies between prescriptive and descriptive rules typically arise from ignorance - a larger and larger number of people who aren't familiar with a traditional rule begin to behave differently until few people even know what the original rule was. I want my rules to be based on full knowledge of both common usage and history, which sometimes means dismissing common usage as based on ignorance.

Comments

Prescriptive rules must be justified. They are normative. X should be done this way because Y. Descriptive rules do not require justification because they are empirically verifiable. A descriptive statement is either true or false. A truly prescriptive statement cannot be true or false.
Roger L. Cauvin said…
The fact that a descriptive rule is one that people actually use doesn't make it "true" or "false". We might define the "truth" of a rule as depending on its popularity. In that case, descriptive rules would be empirically verifiable (subject to the possibility of surveying use of them). However, no rules are true or false in isolation.
I'm not sure is prescription NEEDS to be justified. It certainly is not always justified in English!

Why not justify the action of prescribing rules by the need for a group of people from varying backgrounds (each with descriptive rules of their own) to efficiently converse with one another.

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