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

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...

5 Ways Companies Make Product Decisions

In the last blog entry, we reviewed the  four problems that companies face, or are trying to overcome, as they make product decisions .  Now we'll look at the ways that most companies make their product decisions. Companies that develop, market, and sell products and solutions make strategic and ongoing tactical decisions.  They decide what features to include in their products, what messages they will use to communicate the value of their products, what marketing tactics they will use, what prospective customers they will target, and many day-to-day choices. Whether or not these decisions are deliberate or ad hoc, most companies use some combination of the following ways of making product decisions. (A downloadable "map" that summarizes the product decision landscape is included at the end of this article.) Customer Wants Product decisions based on feature requests, focus groups, and what prospects and customers say they want. Companies are selling products to ...

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 problems she faces or the ...