Course catalogs are written to describe content. Almost nothing about how a course will actually feel to take is in the description—that lives in the syllabus, in the grade breakdown, and in what students who took it last year will tell you if you ask a specific enough question.
For anyone who does their best work on teams, or who has learned the hard way what a badly-structured group course costs, the format details matter at least as much as the subject.
Read the grade breakdown first
Before the description, before the reading list: find the percentage of the grade attached to group deliverables.
A course that's 60% team project is a fundamentally different commitment from one that's 20%, regardless of topic. It means your grade depends substantially on people you may not choose, your calendar has to accommodate four other calendars, and the course's peak workload lands wherever the deliverable does—not spread across the term.
Neither is better. But you should know which one you're signing up for, and you should not accidentally take three of the first kind in one term.
Check whether teams are assigned or self-selected
This single detail changes the character of a course more than most people expect.
Assigned teams are the realistic simulation and the better learning experience. You get people whose working styles you didn't pick, which is the actual condition of professional life. They're also higher variance—you might get an excellent team or spend ten weeks managing someone who has checked out.
Self-selected teams are lower variance and faster to get productive, because you skip the norming phase. They're also how people end up working with the same four classmates for two years, which is comfortable and narrows what you learn.
A defensible pattern: deliberately take one or two team-heavy courses with assigned teams for the range, and use self-selected teams where the workload is heaviest and you need predictability.
Map deliverable dates across your whole schedule
This is the highest-value hour of course selection and the one almost nobody spends.
Pull the syllabi for every course you're considering and plot the major deliverables on one calendar. What you're hunting for is clustering—three team projects due within the same ten days is a term-defining problem, and it's completely invisible when you evaluate courses one at a time.
It's also fixable at registration and nearly unfixable afterwards. Swapping one elective for a similar course with a different deliverable rhythm costs you nothing in October and is impossible in November.
If you're recruiting, overlay the interview calendar too. Superdays and final rounds cluster, and they cluster in the same weeks as midterm deliverables. There's a longer piece on managing that specific collision, but the cheapest fix is choosing a schedule that doesn't create it.
Questions worth asking students who took it
Course reviews skew toward the professor and the difficulty. The useful questions are more specific:
- How were teams formed, and did it work?
- Was there a peer evaluation component, and did it affect grades meaningfully?
- Did the team deliverable have a clear rubric, or did you have to guess what "good" meant?
- Roughly how many hours a week did the group work take, at its peak rather than on average?
- Did the professor intervene when a team had a problem?
That last one matters more than it sounds. A course with heavy group work and an instructor who won't engage with team dysfunction is a course where a bad draw has no remedy.
The trap of optimizing for content alone
The most common selection mistake is picking entirely on subject and discovering the format doesn't fit how you work. A brilliant course you experience through a dysfunctional team teaches you less than an adequate course with a functional one—you spend your attention on coordination overhead rather than the material.
The inverse trap is real too. Choosing exclusively for comfort—all individual assessment, no group deliverables—costs you something specific at recruiting time. Group projects are where behavioural interview stories come from: the conflict you navigated, the moment you influenced without authority, the failure you learned from. A term of solo work is a term that generates very little of that material.
Format matters at the school level too
Everything above assumes you're already enrolled. If you're still choosing between programs, the same logic applies one level up: the format of a program shapes your experience more than its ranking does.
An evening part-time cohort, a weekend executive format, and a full-time program are different products even at the same school—different classmates, different team constraints, different amounts of time you can plausibly give a group deliverable. MBA Lab's directory lists the formats each school reports by state and by category, including online, executive, and part-time options, so you can at least see which schools offer the shape you need before you compare anything else. Confirm the current lineup with the school directly—formats change more often than catalogs do.
A simple filter
When two electives look close, pick the one where you can answer these four questions:
- What percentage of my grade depends on other people?
- Do I choose those people?
- When exactly are the deliverables, and what else is due that week?
- What happens if my team has a problem?
If you can't answer them from the syllabus, ask. A course that's evasive about its team structure is telling you something about how much thought went into designing it.