SOLO Taxonomy for Learning Outcome Design in Higher Education

Let's be honest about how most learning outcomes get written. Someone opens a verb list, picks something that sounds appropriately rigorous, "analyze," "evaluate," "synthesize," and attaches it to a topic. The outcome is grammatically fine. It's measurable in the narrow sense that you can check whether the activity happened. What it doesn't tell you is whether "analyze the causes of the French Revolution" means listing three causes side by side, or explaining how those causes interacted to produce an outcome no single cause would have produced alone. Those are wildly different depths of understanding, and the verb alone can't distinguish them.

This is the problem SOLO Taxonomy was built for. Rather than categorizing outcomes by cognitive process, the way Bloom's Taxonomy does, SOLO categorizes them by how structurally complex the expected understanding actually is. It asks whether a student is meant to hold isolated facts, connect several facts within one context, or generalize a connection to a context they haven't seen before. Five levels capture that progression.

Notice what the table doesn't do. It doesn't ask "what should students know." It asks "how far does their understanding need to reach." That's the distinction the old version of learning outcome guidance tends to skip, and it's the one that actually changes how an outcome gets written.

Here's a habit worth watching for. Multi-structural outcomes are dangerously easy to write and dangerously easy to mistake for something more rigorous. "Describe the key stakeholders in a curriculum redesign" sounds substantial. It's still Multi-structural if a student can score full marks by listing stakeholders without explaining how their interests interact. Curriculum leaders auditing outcomes for depth should treat Multi-structural as the level where an article, and an outcome, most often overstates itself.
 

Now imagine this. A programme chair writes an outcome at the Relational level: "Students will explain how curriculum design decisions affect student retention outcomes." It's a well constructed outcome. It names a real connection, not just a topic. Then the accompanying assessment asks students to define retention, define curriculum design, and list three factors that influence each. That assessment is Multi-structural. It can't detect a Relational answer even if one exists, because it never asks a student to connect the two ideas.

This is where a lot of outcome design effort quietly goes to waste. The outcome specifies a depth. The assessment specifies a different, usually lower, depth. Whoever grades the work ends up scoring what the assessment actually measures, not what the outcome intended. On paper, the outcome was met. In practice, no one can say whether the deeper understanding it described was ever demonstrated.

Few institutions realize they don't have to choose between SOLO and Bloom's Taxonomy, because the two frameworks aren't answering the same question. Bloom's describes the cognitive process a student performs: remembering, applying, evaluating, creating. SOLO describes the structural complexity of what that process produces: isolated, connected within context, or generalized beyond it. A student can "analyze" (a Bloom's process) at a Multi-structural level, producing a list of disconnected observations, or at a Relational level, producing an integrated explanation. Bloom's tells you the verb. SOLO tells you whether the answer actually holds together.

Used together, they cover two different failure points. Bloom's helps catch an outcome that asks for too little cognitive work. SOLO helps catch an outcome, and an assessment, that never specifies how connected the resulting understanding needs to be. Neither one replaces the other, and treating them as rivals in curriculum discussions usually just means neither gets applied carefully.

Writing an outcome at the right SOLO level is a design decision. Making sure that decision survives contact with curriculum mapping, assessment design, and attainment reporting is an operational one, and it's usually where the depth gets lost. Creatrix Campus connects outcome design to curriculum management and to assessment and attainment tracking within one governed system, so a rubric, an assessment item, and the outcome it's meant to verify stay linked rather than living in separate documents that drift apart over time.

That connection doesn't write better outcomes, and it doesn't decide what SOLO level a course should target; that judgment stays with faculty and curriculum leaders. What it does is make the intended depth of an outcome traceable through to the evidence that's supposed to confirm it, so a programme review can show not just that outcomes were met, but that the assessments actually had the reach to check the depth those outcomes described.