A bad trivia question is a specific kind of injustice. You know the answer — you're certain of it — and then the host reveals something slightly different, or the question had a second valid interpretation, or the answer depends on which edition of which encyclopedia you happened to read. The room erupts in argument. The game stumbles. Someone goes to refill their drink and doesn't come back. A single badly written question can derail an entire trivia night, and the worst part is that it didn't have to. Writing good trivia questions is a craft, and like most crafts, it's mostly about learning what not to do.
The Foundational Rule: One Unambiguous Answer
Every great trivia question has exactly one correct answer that every reasonable, knowledgeable person would agree on. This sounds obvious. It is apparently extremely difficult to achieve in practice. Consider the question: "Who invented the telephone?" The intended answer is Alexander Graham Bell. But Elisha Gray filed a patent application for a telephone device on the same day as Bell in 1876, and Antonio Meucci had been working on a voice communication device since the 1850s and received a US congressional resolution of recognition in 2002. Any of those three names is a defensible answer. The question is broken.
A good question narrows its scope so precisely that only one answer fits. "Who was granted the first US patent for a telephone, in 1876?" now has exactly one correct answer. The additional specificity doesn't make it harder — it makes it fair.
The discipline of adding scope is the most important skill a question writer can develop. "What is the largest country in the world?" (Russia, by area; but China by population, and this distinction matters). "What is the longest river in the world?" (The Nile by traditional measurement; the Amazon by some more recent measurements). Specificity saves lives. Ask for the largest country by land area. Ask for the river with the highest water discharge. The question becomes unambiguous, and your players can actually feel good about getting it right.
Question Length and the Difficulty Dial
There is a counterintuitive relationship between question length and question quality. Very short questions — "Who painted the Mona Lisa?" — tend to be either too easy (everyone knows Leonardo da Vinci) or too hard in a cheap way ("Which 16th-century Flemish artist painted a work that some historians have argued is the original Mona Lisa?"). The sweet spot is a question long enough to contain the information needed to answer it, but not so long that answering it becomes a memory exercise rather than a knowledge exercise.
Example of pyramid structure done right: "This element, discovered in 1898 by Marie and Pierre Curie, is named for the homeland Marie had been forced to leave — the country then under Russian, Prussian, and Austro-Hungarian partition. What is the element?" The question rewards chemistry knowledge at the start, history knowledge in the middle, and gives geography context at the end. Someone who knows the periodic table gets it immediately. Someone who knows Polish history gets it from the second clue. Everyone else pieces it together and feels satisfied. (The answer is Polonium, named for Poland.)
What to Avoid: The Most Common Mistakes
The "Which Year" Question. "In which year did X happen?" is almost always a luck question masquerading as a knowledge question. Unless your players are genuine history specialists, exact years are guesses. Knowing that World War I began in 1914 is knowledge. Knowing the exact year that the Eiffel Tower was completed (1889) is a coin flip for most players. If you must use a year, use it as a verifiable clue within a larger question, not as the answer itself.
The Double Negative. "Which of the following is NOT a mammal that does NOT lay eggs?" If your question requires a flowchart to parse, it's a bad question. Clarity is a prerequisite for fairness.
The Too-Recent Question. "What song topped the Billboard Hot 100 three weeks ago?" is not a trivia question. It's a current events test, and it ages to dust within days. Give your questions at least a year before using them. Cultural facts that survive a year tend to be durable enough to be genuinely testable.
The Too-Obscure Question. There is a difference between a question that rewards deep knowledge and a question that no one could answer without having read a specific footnote. "What is the middle name of the third-tallest person ever recorded?" is not hard trivia. It is unfair trivia. The goal is a question where the knowledgeable person should be able to answer it and should feel rewarded for their knowledge. If the answer is so obscure that even experts in the field would guess, it belongs in a different format.
The Partial Answer Problem: A Host's Nightmare
In live trivia, partial answers are the greatest test of a host's judgment and the greatest source of player frustration. "Name a Shakespeare tragedy" is an acceptably open question. "Name the Shakespeare tragedy set in Denmark" has one answer (Hamlet), and "set in Verona" has two (Romeo and Juliet; The Two Gentlemen of Verona). The host who hasn't anticipated this is about to have a very bad five minutes. Before finalizing any question, ask yourself: is there more than one answer that a knowledgeable person could reasonably give? If yes, either revise the question to exclude the alternatives or prepare to accept all defensible answers.
Great questions share a quality that's hard to quantify but instantly recognizable: when you hear the answer, you feel something. Either the satisfaction of having known it, the sting of having almost known it, or the genuine delight of learning something new. That's the target. Not hard for its own sake. Not easy for the sake of crowd-pleasing. Satisfying — the specific satisfaction of a question that was worth asking.