For context, Bloom's is a way to organize different objectives in learning. (We'll use it as the outline for this thread.)
The six layers are:
- Remember
- Understand
- Apply
- Analyze
- Evaluate
- Create
You'll notice that each layer requires more skill
The foundation of Bloom's is Remembering. Memorization gets a bad rap because rote learning is often over emphasized, but being able to recall facts is an unavoidable foundation of understanding.
(See: @ncasenmare's ncase.me/remember/ for a good overview)
But there are other ways to practice recall, too.
📄 Through quizzes and tests. But the problem is that testing is traditionally used a means of *evaluating* rather than a means of *learning*.
The downside of short answer is that it has a higher grading burden.
But the upside is that we remember what we think about.
Verbalizing what we've learned pushes us up into the next layer of Bloom's Taxonomy: Understanding
💡 While in Remembering we're able to recite facts, repeat lists, or name ideas. In Understanding we're able to paraphrase what we've learned, summarize key points, and (hopefully) explain it to someone else.
is quick way to verbalize what you've learned (and also aid with recall). The idea is, at the end of class write down:
1. the most important concept from that day and
2. one question or confusion that remains
A variant on asking questions is making Predictions.
Prediction improves retention because it also drives you to seek connections.
When you make a guess about what's coming next you're more interested in the answer.
And if you're wrong? Wrong guesses expose fluency illusions.
@AnnieDuke suggests that asking "Wanna Bet?" will clarify your own thinking
When you bet on what you think you know, you immediately take an "outside" view of your opinion (metacognition) and account for uncertainty, presuppositions, and alternatives
😺 Pre-reading Questions
Scan the headlines and diagrams to get a big picture outline of the text/lecture and then write down questions you expect the text/lecture will answer.
In "Small Teaching" James Lang calls this "Pause-predict-ponder":
During a lecture:
1. pause and
2. ask the students to predict what comes next and then ask *why* they made that Prediction.
After you've shown the answer
3. ponder. if the Prediction was wrong, what was different?
The idea is, before a lecture, take a couple minutes to fill a napkin (or sheet of paper) with everything you think you already know about a subject.
The motivation here is similar: you're activating the connections and models you already have in your brain to prepare your mind to make new ones.
What's the name of the framework we're using to look at the different layers of Mastery?
But there is a way to break this pattern:
Question: would you study harder to:
- make an A on a test or
- teach the material to the class?
are one of the biggest barriers to learning. We read the text and feel like we know the material when we actually don't
As it often happens, Step 1 is admitting you have a problem. Or in this case, recognizing areas you don't deeply Understand
In some ways, teaching to learn is a hack: we're using our social fear of appearing foolish before our peers to motivate us to identify gaps in our own knowledge and close them
APPLYING
🏌️ Practice Doing
Whatever skill we are seeking from our students, they should have time to practice it in class.
The only true way to learn is to Do.
We should give student the opportunity try their hand *before* they feel ready
As teachers, we should deconstruct skill practice into its smaller component cognitive tasks - and then teach these smaller skills.
An expert programmer doesn't think twice about these things, but they're a huge barrier for the novice.
ANALYZING
Experts organize knowledge in their minds in a way that novices can't (yet). If you make your knowledge organization explicit then you can share it
One of the easiest ways to do this is:
Concept maps help visualize organization of key ideas.
As both a teacher and a student it can help to be explicit about your knowledge organization by drawing out a concept map.
1. Realize concept maps are a Graph not a Tree
Most mindmapping software forces you to organize in hierarchical outline of parents and children.
But in reality, our knowledge is organized like a Graph where you can draw connections between any node.
First draft concept maps often end up as names of topics. But there are always multiple ways to organize your knowledge and teachers should try to communicate those.
Don’t let your tool restrict your though process. Just use pencil and paper if you need to.
Explicitly identify discipline-specific conventions. Programming has tons of these and experts often forget to communicate them
If you are a teacher, your goal is to create an environment where the students themselves form their own mental connections.
- Small Teaching by James Lang
- Teach Students How to Learn by Saundra McGuire
- How Learning Works by Ambrose et al.
If you're interested in learning, these books are great
What was the most important thing you learned from this thread?
What's one question you still have?