Nation's four strands principle as a framework for balancing ESP vocabulary programs¶
Design · All designs
Evidence · no claims cited
Description¶
The article applies Nation's (2007) framework of four strands—"meaning-focused input, meaning-focused output, language-focused learning and fluency development"—as guidelines for combining subject matter and English learning in an ESP course. The framework holds that "learning from input alone is not enough" and that programs need "a balance of well proven learning activities across the four strands". The author uses it to evaluate both advantages and disadvantages of the vocabulary activities in students' evaluations.
Design Implications¶
Context¶
Requirements¶
- The vocabulary program should balance activities across all four strands, with 95-98% of running words within learners' previous knowledge for meaning-focused input
Constraints¶
- The article notes more students favored a bilingual class over all-English teaching (38.30% commented positively on all-English class)
Target Learners¶
- accounting majors in an ESP course
Learning Goals¶
- technical vocabulary acquisition and retention
- professional communication skills in accounting
Claims¶
Related Designs¶
Examples¶
-
Key Sources¶
- Liju Xu. (2018). Learning and Retaining Technical Vocabulary with Enhancement Activities in an ESP Course. English Language Teaching, 11(10). https://doi.org/10.5539/elt.v11n10p145
Page metadata
| Field | Value |
|---|---|
type |
design |
id |
four-strands-principle-esp-vocabulary |
title |
Nation's four strands principle as a framework for balancing ESP vocabulary programs |
description |
The article applies Nation's (2007) framework of four strands—"meaning-focused input, meaning-focused output, language-focused learning and fluency development"—as guidelines for combining subject matter and English l... |
status |
review |
generated |
by process:settle-candidates on 2026-11-03 |
trust |
unverified — no one has confirmed this page's content |
sources |
1 — liju-xu-2018 |
Frontmatter is the page's machine-readable record — see the Schema & Guide.