MBA students: stop taking notes in case discussions

Case method teaching is specifically designed to resist preparation. An MBA student who has spent Sunday evening reading the Ryanair case, annotating the financials, and building a MECE framework for the operational model will spend Monday morning watching their preparation become obsolete in the first ten minutes of class discussion.

The professor calls on someone who reframes the entire case around labour relations. A response from the row behind reframes it again around airport negotiating leverage. A third comment from a student who worked in aviation before the programme introduces operational detail that wasn't in the case. The professor's response to that comment is the insight that will appear on the exam.

None of this is on the slides. None of it was in the pre-read. It emerged from the dialogue of the case discussion itself — and the student who was writing notes when the aviation insight landed missed what the professor said next.

What makes case method different

Case method teaching — the dominant pedagogy at leading business schools including LBS, HBS, INSEAD, Said, Warwick, and Chicago Booth — asks students to prepare an analysis and then abandon it in real time as the class discussion evolves. The insight is emergent. It cannot be pre-read because it doesn't exist until the room creates it.

This produces a note-taking problem that is structurally distinct from lecture capture:

The content is unpredictable. You cannot write outline notes based on expected content, because the discussion goes where it goes. The student who tries to write a sequential record of the discussion is always processing the sentence that just ended while the next one begins.

Your contribution is the cost of good notes. If you're writing when the professor asks "what would you have done differently as CEO?", you miss the question. If you're writing your answer, you miss what the student next to you says — which might be the point the professor builds the rest of the session around.

Class participation is graded. At many business schools, 30–50% of the module grade comes from class participation. A student who is writing instead of contributing is sacrificing marks for notes that are incomplete anyway.

The guest executive is unrepeatable. When a former COO joins the session to speak about how the case actually played out — what they did differently from the teaching note, what they'd do differently again in retrospect — that content exists nowhere else. You cannot find it in the case book or the academic literature. You either captured it or you didn't.

What the AI workflow changes

Record the case discussion with Kuulo on an iPhone placed on your desk or in your bag. Attend the session fully: contribute, respond, track the argument as it evolves.

After class, generate the AI summary. Kuulo's speaker diarization has separated your professor's voice from student contributions. The summary covers: the case's central strategic problem, the frameworks the class applied, the key arguments made and who made them, the professor's synthesis, and — if a guest speaker attended — their additions to the case narrative.

This is available in under two minutes. By the time you're in the corridor outside the classroom, you have a structured record of the session.

For case discussion specifically: Kuulo's Business Case Discussion template structures output around the case's strategic question, the options the class evaluated, the decision criteria debated, the conclusion the class reached, and the professor's teaching points. This is a different structure from lecture notes, and the difference matters — a case discussion note that reads like a lecture summary misses the evaluative architecture that makes case method pedagogically distinct.

Group project documentation

MBA programmes are structured around team-based project work: consulting projects, business plan competitions, live-client engagements, syndicate group preparation. These generate significant team meeting content where attribution matters.

"We agreed to go with the second pricing scenario" is a less useful project record than "Alex proposed the second pricing scenario because of the sensitivity analysis showing higher margin at the mid-market price point; the team agreed after Maya flagged that it reduced the risk of low-price positioning against the incumbent."

Kuulo's diarized group project meeting produces the second version of that record. When the project sponsor asks why you chose the pricing strategy you chose, the attributed notes contain the reasoning, the objections that were raised, and who proposed what. This is the kind of documentation that makes group projects run better — not because it enforces accountability, but because it ensures the group's reasoning is available to everyone when decisions need to be revisited.

Guest speaker sessions

MBA programmes invest significantly in bringing practising executives, investors, and entrepreneurs into the classroom. These sessions generate content that is specifically non-reproducible: the personal narrative of a decision made under pressure, the specific mistake the founder made in Series A negotiations, the exact framing a CFO uses when presenting bad news to a board.

Writing notes during a guest speaker session means you're always a sentence behind. The speaker is not reading from slides — they're talking, at their natural pace, following their own associative narrative. The moment you start writing the sentence they just completed, you miss the transition into the next story.

Kuulo captures the full session. The AI summary identifies: key biographical/career insights, the strategic decisions discussed and their outcomes, the explicit advice offered, and the questions-and-answers that generated the most substantive responses. The guest speaker's exact phrasing — "the moment I knew we'd mispriced the Series B was when our lead investor asked a question nobody on our team could answer" — is preserved rather than paraphrased into a lesson-about-pricing bullet point.

Networking notes

An MBA programme's value is disproportionately in the network. The people in the cohort, the alumni speakers, the recruiter relationships, the professor connections — these matter for decades.

After a networking event or an alumni speaker dinner, a 60-second voice memo into Kuulo — "Sarah Chen, class of 2019, now at Permira — said to reach out about the TMT portfolio track; mentioned she's looking for associates who have operator experience" — generates a structured contact note with the person's background, the context of the conversation, and the specific follow-up agreed. Filed and searchable across the programme.

This is not the kind of thing people build as a habit, because building it manually is tedious. A voice memo that generates a structured note takes 60 seconds. The alternative is a name scrawled on a business card that becomes illegible by the time you get back to your accommodation.

The syndicate culture

Business schools run on study groups — syndicates of 4–6 students who prepare cases together, share notes, and develop a collective analytical framework across the programme. The note-sharing culture is established and expected: if you produce a clear, structured case summary, it circulates.

A Kuulo case discussion note shared in the syndicate WhatsApp group after a session is a different quality of contribution than a personal note photographed and posted. It's structured, attributed, and complete — the professor's teaching points are there, the guest executive's additions are there, the key argument the best contributor made is there.

The student who produces this for the first session sets a standard. The syndicate either matches it or benefits from it. Either way, the quality of shared preparation across the cohort improves.

What to do with the recording after graduation

The recordings, summaries, and case notes generated across a two-year MBA are a persistent intellectual asset. The strategy frameworks discussed in the Competitive Dynamics module. The negotiation principles from the simulation. The finance intuitions built across the corporate finance case series. All of it searchable on your device.

Three years into a career, when you're advising a portfolio company on a pricing decision and the framework feels half-remembered, the case discussion notes from your MBA module are on your phone. Not on a platform that closed its API, not in a subscription that lapsed, not on a cloud server with a 3-month retention policy. On the device that's already in your pocket.

The MBA note library is worth building. Kuulo builds it automatically, in the background, while you're doing the actual work of the programme.