This page connects Ritchhart's eight types of thinking to Fink's six dimensions of significant learning, with concrete tools for computing and engineering course design in the age of AI.
Bloom's Taxonomy tells you how cognitively demanding a task is. But it says nothing about whether students will care about it, connect it to anything real, or know how to keep learning after the course ends. Fink's Significant Learning framework fills that gap, mapping the full terrain of what meaningful learning changes in a person: how they think, what they integrate, who they become, and how they continue growing. For computing faculty, this matters because the half-life of a specific tech stack is short. The capacity to keep learning is what sustains a career.
Fink's Application and Integration dimensions map directly to what employers mean when they say graduates cannot transfer knowledge. Designing for them closes that gap.
Learning How to Learn is the most underassessed dimension in computing curricula and the most important for long-term career success.
AI performs best at Foundational Knowledge. Human Dimension, Caring, and Learning How to Learn are where student thinking is irreplaceable and where course redesign has the most impact.
New to these frameworks? Hover over a Fink dimension to see which types of thinking activate it. Notice how most thinking types touch multiple dimensions at once.
Redesigning a course? Click the dimensions you want your next major assignment to target, then note 1-2 thinking types you will intentionally build in.
Hover or click any card to highlight connections. Use the legend or pathway buttons to filter.
A BST implementation assignment typically hits Foundational Knowledge and Application. Adding one question, "Describe a real system you use that likely relies on a tree structure and compare your implementation to what you would expect in production," activates Integration and begins to build Caring.
Week 1: Think-Puzzle-Explore before implementation. What do students already think they know? What puzzles them? (Learning How to Learn)
Midpoint: Connect-Extend-Challenge. How does this connect to data they have worked with before? How does it extend their mental model? (Integration)
Submission: I Used to Think / Now I Think. Where did their understanding shift? (Learning How to Learn + Caring)
A standard beam-loading lab targets Foundational Knowledge and Application. Adding a reflection on a real structural failure chosen by the student activates Integration. Asking who was centered in the original design assumptions activates Human Dimension.
Pre-lab: Students identify one real structure they interact with and predict how it handles load. (Integration)
Lab report: Compare results to the real structure. What assumptions did the original designers make? (Application + Integration)
Reflection: Whose safety was centered in those assumptions, and whose was not? (Human Dimension + Caring)
Design critiques often stay at Application. Structuring critique around a specific user from research activates Human Dimension. Ending with "what would you not compromise on for this user?" activates Caring in a way that produces professional values, not just preferences.
Before critique: Each student identifies the one user need their design is most accountable to. (Human Dimension)
During critique: Feedback is structured around that user. Does this design serve that person? Where does it fall short? (Application + Integration)
After critique: What is the one thing you would not compromise on, and why? Written response. (Caring + Learning How to Learn)
Use this workflow alongside the interactive chart. It takes 20-30 minutes for a single assignment and applies to any technical course.
Which Fink dimensions do your course outcomes imply? Which are currently underrepresented in your major assessments?
Use the chart to find thinking types that activate your priority dimensions and map to your discipline's reasoning practices.
Add a thinking routine checkpoint before, during, or after the assignment. Target less than 15 additional minutes of student time.
Specificity is the signal. Generic fluency suggests offloading. Idiosyncratic, experience-grounded responses suggest genuine thinking.
Three tools designed for immediate use in computing and engineering course design.
A structured thinking routine template with discipline-specific prompts for CS, engineering, and HCI courses, plus a faculty guide.
Download template (Google Doc)A rubric for assessing depth of thinking process, not just the final product. Adaptable for code reviews, design reports, and lab write-ups.
Download rubric (Google Doc)A visual showing the path from assignment design to thinking routine to observable evidence to assessment insight.
View diagram