Taxonomy Verbs Math

Using Bloom's Taxonomy Verbs With Math Objectives

Most people treat taxonomy verb lists like they're magical incantations that make lesson plans look professional. They don't. The real work is picking the right verb for what the student actually needs to do, and meaning it.

I've spent years watching teachers take a generic verb list and paste it into math objectives without thinking about what the verb actually requires. You'll see things like "students will analyze the function" written next to a worksheet where kids are just plugging numbers into a calculator. That's not analysis. That's following steps. The mismatch between verb and actual task is the most common problem I see, and it's usually invisible until you actually audit the assessment. Here's how it works in practice. You start with the cognitive level you actually want, then pick a verb that matches, then design the task and assessment to fit that verb. Not the other way around. The Bloom's Taxonomy hierarchy still holds up for math: remember, understand, apply, analyze, evaluate, create. Each level demands a different kind of student output, and each requires a different kind of assessment. When I was building curriculum standards for a district a few years back, we had a requirement to align every objective to a specific cognitive level. The problem hit hard when we got to geometry proofs. A lot of the draft objectives said "prove" but the actual tasks were fill-in-the-blank two-column proofs with the statements already partially completed. That's applying, not analyzing or creating. I rewrote about forty objectives that week because the assessments didn't match the verbs. It took three days of back-and-forth with the math coaches who insisted their original wording was fine. It wasn't.

The verbs matter because they dictate the cognitive demand. If you write "calculate the area of the following shapes," every student does the same operation. That's application. If you write "determine which methods are most efficient for calculating area across different polygon types," students have to compare strategies and justify choices. That's analysis and evaluation. The topic is identical. The thinking required is completely different. One counter-intuitive thing nobody warns you about: higher-level verbs don't automatically mean deeper learning. "Evaluate the validity of the proof" sounds like analysis, but if the proof is straightforward and the rubric only checks whether students agree or disagree, it collapses into a basic recall task. Students just repeat what the teacher already told them is true. The verb creates the appearance of rigor without the substance. I learned this the hard way when a state reviewer flagged our benchmarks as misaligned. We had "evaluate" scattered throughout the second semester units, but the assessments never required students to actually critique reasoning they hadn't been given guidance on beforehand. Another thing that catches people out: verbs like "classify" and "compare" sit in a gray zone between understand and analyze depending on complexity. Classifying triangles by angles is understand-level work if the categories are given and the criteria are clear. Classifying data sets by distribution type using self-selected criteria is analyze-level. The verb doesn't change. The cognitive demand does. You have to look at the full objective, not just the verb, to know what level you're actually targeting.

For the verb list itself, I keep a working document organized by level rather than alphabetically. It's faster to scan when you're drafting objectives under time pressure. Remember level: define, identify, list, recall, name. Understand level: explain, describe, interpret, summarize, classify. Apply level: solve, compute, demonstrate, use, execute. Analyze level: differentiate, organize, attribute, compare, deconstruct. Evaluate level: critique, justify, assess, defend, judge. Create level: design, construct, formulate, produce, develop. When you're writing objectives, try this sequence. State the content standard first. Then decide what the student needs to do with that content to show mastery. Then pick the verb that matches. Finally, design an assessment that can only be completed correctly using that verb. If any step breaks, the objective is misaligned. I also test every objective by asking what a student could do wrong and still get full credit. If a student memorized a procedure from the board can complete the task, the verb is probably too low. The task should require something the procedure alone can't deliver.

Common mistakes: using "understand" as a verb (it's not assessable), writing objectives with two verbs connected by "and" (which level do you assess?), assuming the verb determines the assessment format (a multiple choice quiz can measure analysis if the questions are designed right), and using the same verb across a whole unit without varying cognitive demand (students need practice at each level, not repetition of one). There's a free verb generator at bloomstaxonomy.com/verbs that most people link to, but honestly the pdfs from Anderson and Krathwohl's revision of Bloom's Taxonomy are better. The original 1956 version and the 2001 revision both have math-specific verb recommendations that the generic lists skip. The revision specifically addresses how verbs shift meaning in disciplinary contexts, which is the exact problem you run into with math objectives. One more practical note: when you're aligning to state standards, the standards themselves often imply a verb even when they don't state one. "Solve equations" in a standard is apply-level. "Justify each step" in a standard is evaluate-level. I've seen teachers miss the verb that was already in the standard and downlevel their objective by replacing it with something easier to assess. Check the standard language before you write your own verb. It's usually more precise than what you'd come up with on your own.

The whole system has limitations. It doesn't handle procedural fluency well. Memorizing multiplication facts or recalling derivative rules isn't really captured by any level above remember. You need a separate track for that. It also doesn't account for the time required to reach higher levels. An objective with "design" in it might need three weeks of scaffolding before students can actually do it. Writing the verb in September doesn't make it achievable by October. And finally, it's easy to overthink. Sometimes "solve" is exactly the right verb and you shouldn't pad it into something that sounds fancier but means less.