When AACSB reviewers ask a program for evidence of student learning, they're looking for the same three things most accreditors want: a clear definition of what students were supposed to learn, measurement that's tied to actual student performance rather than course-completion proxies, and evidence that the program uses those measurements to improve.
Most programs can produce the first. Many can produce a rubric-scored assignment or a standardized test that addresses the second. Very few can produce all three at the class level, across multiple competency domains, without pulling a graduate assistant off something else for three weeks.
The Class Outcomes Report is built to close that gap.
What the Report Measures
Every time a student plays through a scenario in The MBA Game, the game tags their performance against two things: the frameworks that were tested, and the AACSB-aligned competency domain those frameworks live in. A Northstar supply chain case isn't just "a simulation" — it's a specific set of plays that exercise Operations and Supply Chain Management, with every decision carrying a scored mastery tier. A governance case pulls from Corporate Governance & Ethical Leadership. A capital allocation scenario sits in Corporate Finance & Capital Markets.
When you open the Class Outcomes Report, the first thing you see is the class-level view.
The top band shows headline metrics — students, average plays per student, average XP, certifications earned, learning outcomes authored. Below that, the Mastery Distribution chart breaks the class into four evidence-ready tiers: Exemplary (≥85%), Proficient (75–84%), Developing (60–74%), and Emerging (<60%). These tiers map cleanly onto the kind of four-level rubric most assessment committees already use, which makes the output drop-in compatible with existing program assessment plans.
Game Coverage and Engine Coverage tell you what the class actually practiced — which games they played and which interaction types (quiz, diagnostic, calculation, allocation, negotiation, and so on) they engaged with. If your assessment plan specifies that every student should encounter quantitative decision-making, the Engine Coverage view tells you whether that actually happened.
Evidence at the Competency Level
The second view is where most assessment committees spend their time.
Each bar represents a competency domain — Financial Accounting & Analysis, Strategic Management, Corporate Finance, Analytics & Evidence-Based Management, Marketing, Organizational Behavior, Technology Strategy, Economics, Operations, Project Management — and reports the class-wide average across every outcome authored for that domain. The bars are colored by tier, so a reviewer can read the bar chart exactly like a rubric: green is proficient-and-above, gold is developing, red is emerging.
The Top Achievement and Focus Areas panels at the bottom do something the flat bars can't: they name the individual learning outcomes where the class is strongest and weakest, with the actual outcome text. That's the data a program director needs to walk into a curriculum committee meeting with a concrete recommendation — not "we should teach more operations" but "the class is averaging 10% on 'sequence project tasks and milestones' and 'manage project stakeholders across the lifecycle' — let's add a project management module in week six."
Assessment data that can't tell you what to do next isn't really assessment data. The Focus Areas panel exists so that the report closes the loop AACSB wants to see closed — from measurement to decision to curriculum response.
Why This Matters for Program Review
Programs have historically struggled with three pieces of AACSB's assurance-of-learning expectations. The first is direct measurement — most programs rely on course grades, which blend effort, attendance, and performance into a single number. The second is coverage at the program level — even when individual courses measure well, it's hard to prove that the program as a whole is addressing a competency. The third is closing the loop — showing that the program responds to what it measures.
The Class Outcomes Report addresses all three. Direct measurement: every scored play is a student actually making a decision, not a student reporting that they learned something. Program-level coverage: because the game cuts across 12 game types and ten AACSB-aligned domains, one cohort playing through a term generates evidence that would take a program months to assemble from course-level artifacts. Closing the loop: the Focus Areas panel translates measurement into action.
For the Instructor Too
Assessment evidence is a program-level concern, but the same data is useful at the course level. Instructors can see which students are in the Developing tier and pull them in for office hours. They can see which games or engines the class is avoiding — some cohorts chase XP through the games they're best at — and nudge the cohort toward the areas it's underweighting. Before the final exam, a quick glance at the Focus Areas panel tells the instructor exactly what to review in the final class session.
The report isn't the only output in the instructor dashboard — there's also per-student performance, engagement trends, and exportable gradebook data. But the Class Outcomes Report is the one most programs end up showing to their dean, their curriculum committee, and their accreditors.