SWBATS
A framework for writing learning objectives using the stem 'Students Will Be Able To' followed by a measurable action verb.
Also known as: Students Will Be Able To, SWBAT, Learning objective format
Category: Frameworks
Tags: education, teaching, curriculum, instructional-design, frameworks
Explanation
SWBATS (Students Will Be Able To) is a widely used format for writing clear, measurable learning objectives. Each objective starts with the phrase "Students will be able to..." followed by an observable action verb and the specific skill or knowledge to be demonstrated.
## The format
**Students Will Be Able To** + **action verb** + **specific content/skill** + **context/conditions** (optional)
Examples:
- Students will be able to **identify** the three branches of government
- Students will be able to **analyze** a dataset using regression techniques
- Students will be able to **design** a REST API following best practices
- Students will be able to **evaluate** the trade-offs between different architectural patterns
## Why SWBATS works
- **Forces measurability**: the action verb requirement prevents vague objectives like "understand" or "know"
- **Student-centered**: focuses on what the learner achieves, not what the instructor covers
- **Assessment-aligned**: each SWBAT naturally suggests how to assess it (if they can "analyze," give them something to analyze)
- **Bloom's-compatible**: action verbs map directly to Bloom's Taxonomy levels, helping ensure cognitive variety
## Using SWBATS for course creation
1. **Start with the end**: what should graduates of your course be able to do that they couldn't before?
2. **Write SWBATS at multiple levels**: module-level objectives feed into course-level objectives
3. **Use varied cognitive levels**: don't write all objectives at the "remember" level—include application, analysis, and creation
4. **Limit per module**: 3-5 SWBATS per module keeps focus sharp
5. **Test each one**: for every SWBAT, ask "how would I verify this?" If you can't, rewrite it
## SWBATS hierarchy for courses
- **Course-level SWBATS**: broad capabilities ("design and deploy a full-stack web application")
- **Module-level SWBATS**: intermediate skills ("implement user authentication using JWT tokens")
- **Lesson-level SWBATS**: specific, granular abilities ("write middleware that validates JWT tokens")
## Common pitfalls
- Using "understand" or "learn" instead of measurable verbs
- Writing objectives that are really topics ("Students will be able to: databases" is not a SWBAT)
- Making objectives too broad ("Students will be able to program") or too narrow ("Students will be able to write a for loop in Python 3.11")
- Forgetting to align assessment with the stated SWBATS
Related Concepts
← Back to all concepts