After the final pitch: learning log for case teams.

The final pitch ends. Photos are taken. Someone wants to delete the messy slides. The Case Competition treats that moment as the start of a learning log, not as a trophy ceremony. A learning log is a short, dated record of what the team actually decided under time pressure: the governing question, the evidence that moved the recommendation, the Q&A that exposed a gap, and the one skill to train next. It does not invent winners, rankings, or testimonials.

Write while the room is still honest.

Memory after a pitch is a poor instrument. Within a few hours, teams rewrite history: the issue tree was “always clear,” the market size was “solid,” the recommendation was “obvious.” A learning log freezes the uncomfortable version. One page is enough. Four people can contribute four short paragraphs. The coach’s job is to refuse celebration language that erases the miss.

Use the same archive cases you already practise—transport, consumer, airline, people cases—as comparison objects, not as claims that your team won anything. The method is transferable. The result of one weekend is not a résumé headline.

Capture the governing question you actually used.

Write the question that sat at the top of the issue tree during the live analysis, not the prettier question you wish you had used. If the question changed mid-night, note when and why. A question specific enough to fail is still the standard. “How can the company grow?” is not a question. A decision with constraints, competitors, and a time window can be analysed.

Then note whether the MECE test held under pressure. Were two branches synonyms? Was a critical constraint—regulation, union response, cash—missing until a judge asked? The learning log should name the missing branch in one sentence so the next training week can target it.

Record which evidence actually moved the recommendation.

Teams collect folders of screenshots. Judges care about claims. In the log, list the two or three sentences that changed the recommendation. Examples of claim shape: “Peak-hour crowding is the binding constraint, not average daily ridership.” “Price is not the lever; mix and fixed cost are.” If a branch produced only a heading called “Market analysis,” write that failure plainly.

• Which quantitative check survived a sanity test?
• Which customer or rider insight was evidence rather than a slogan?
• Which competitive or institutional response was guessed rather than sourced?
• Which slide title stated an action, and which only named a topic?

Log the Q&A without mythology.

Q&A is where structure meets courage. Write the hardest question you received and the answer you gave, not the answer you planned later. Note whether the team had a single owner for Q&A or whether four people talked over one another. Note whether a risk slide existed or whether risks appeared only when a judge forced them.

Do not invent praise. Do not invent scores. If you do not know how you placed, the log still works. Learning is not a substitute for a ranking, and a ranking is not a substitute for a method.

Translate gaps into next training.

A learning log earns its keep when it becomes a practice plan. Pick one primary gap. If the issue tree collapsed, schedule a week of tree-building on archive cases with ruthless pruning. If market sizing was opaque, train transparent segmentation and assumptions. If recommendation slides had topic titles, train action titles and a governing slide. If roles were confused, practise lead, research, modelling, slides, and Q&A without turning the team into a rigid hierarchy.

An eight-week training path can absorb one gap per fortnight. A 24-hour competition rhythm can absorb one micro-drill: ten minutes to rewrite titles, fifteen minutes to prune the tree, five minutes to assign owners. The log tells you which drill to choose. Without the log, teams repeat the same overnight panic.

What coaches and schools should ask for.

Coaches can ask for the learning log before the next case pack is opened. Schools that host contests can ask teams for a one-page after-action note as part of learning design, separate from awards. The note should stay student-authored. Ghostwritten polish after the pitch is the same integrity problem as ghostwritten slides before it.

Judging language—insight, structure, quantification, practicality, communication, Q&A—can label the sections of the log. The point is not to recreate a score sheet. The point is to keep the team’s next practice honest.

A worked after-pitch scene.

Imagine four students leaving a room. They still disagree about whether volume or price was the binding issue. Instead of arguing in the lift, they open a shared page. They write the governing question they used. They write the claim that survived. They write the judge question that exposed the cash constraint they never branched. They write one next drill: rebuild a profitability tree with a cash branch before the next pack. That page is more useful than a group photo caption.

Practise the habit on previous cases in the archive. Build a tree, run a short pitch among teammates, then write the learning log even when no external judge is present. The method is the same; the honesty should not depend on a microphone.

What this page refuses.

This page refuses invented customers, prices, awards, and testimonials. It refuses treating a single successful pitch as proof of mastery. It refuses deleting the messy analysis because a slide deck looks cleaner. Continue with issue trees, recommendation slides, and the eight-week training path.