We have so many named concepts in our leadership book that readers need a glossary. Should we explain all the terminology up front?
Do not make readers complete a terminology course before they reach the book's argument. Introduce a named concept when it helps them understand a problem or make a decision, and keep only the labels that provide lasting value.
Start with a terminology audit. List each term, its first appearance, the concepts needed to understand it, and where readers must use it again. This exposes dependency problems: a chapter may rely on a distinction the manuscript does not explain until much later.
For each label, ask:
- Does it name something meaningfully different from familiar language?
- Will readers need to recall and apply it later?
- Can we explain its purpose through a concrete situation before naming it?
- Does it duplicate another concept under a different name?
Arrange explanations in the order readers need them. Where possible, present the problem, explain the distinction, introduce the label, and then demonstrate its use. A glossary can support retrieval, but it cannot repair a chapter whose argument depends on unexplained vocabulary.
Ask AI to flag terms used before their definitions and passages that introduce several unfamiliar concepts together. Redirect it if it starts replacing necessary technical distinctions with vague everyday language.
After revising the structure, have a subject-matter reader check that simplification has not distorted the concepts. Have a less familiar reader explain the chapter's argument without consulting the glossary. Their explanation will show whether the terminology supports understanding or has become an obstacle to it.
Category: Developmental editing