How to Analyse Language Choices
Analysing language choices
Language analysis means explaining how a writer uses words to create meaning and effect — not just spotting techniques, but showing why they matter. It's central to GCSE English Language reading questions.
What to look for
- Word choices (diction): why this exact word? Consider its connotations (the feelings/ideas it suggests).
- Figurative language: similes, metaphors, personification.
- Imagery: words that appeal to the senses (sight, sound, touch…).
- Sound devices: alliteration, onomatopoeia, sibilance.
- Sentence forms: short punchy sentences vs long flowing ones.
- Tone: the writer's attitude (angry, calm, sarcastic).
Zooming in on single words
The best analysis often focuses on one powerful word. Ask:
- What does it literally mean?
- What does it connote (suggest)?
- Why might the writer have chosen it over a similar word?
Example: "The soldiers staggered home." Staggered (not "walked") connotes exhaustion and injury, suggesting the human cost of war.
The method: What / How / Why
1. What does the writer do? (name the technique/word)
2. How does it work? (quote and explain the method)
3. Why is it effective? (the effect on the reader)
Worked example
The writer describes the storm as a "raging beast". This metaphor compares the storm to a wild, uncontrollable animal, suggesting it is dangerous and alive. The word "raging" adds a sense of fury, making the reader feel the storm's threatening power. ✓
Common mistakes
- Feature-spotting — naming a technique without explaining its effect.
- Being vague ("it makes it interesting") instead of specific.
- Ignoring connotations of individual words.
Exam tips
- Always link a technique to its effect on the reader.
- Zoom in on a single powerful word and explore its connotations.
- Embed short quotations rather than copying whole lines.
Quick recap
- Analyse how and why language creates effect — go beyond naming techniques.
- Explore word choices and connotations, imagery, sound and sentence forms.
- Use What / How / Why and always connect the method to the reader's response.