Monash ICPC All articles
Team Preparation

Fifteen Minutes, Three Questions: A Post-Contest Reset for Monash Squads

Monash ICPC
Fifteen Minutes, Three Questions: A Post-Contest Reset for Monash Squads

Photo by Photo by Jeswin Thomas on Unsplash on Unsplash

Bad contests are not wasted contests. They are wasted when the only debrief is a group chat that says 'rough one' and then everyone logs off. For Monash ICPC squads, the useful move is smaller and more disciplined: a fifteen-minute post-mortem that ends with one drill per person. It is short enough to run after a Wednesday practice contest, a Saturday online round, or a local university contest, and structured enough that it does not turn into an hour of re-litigating a single wrong answer.

Why fifteen minutes?

Memory fades quickly. The details that matter — which problem you opened first, when the panic set in, why you resubmitted without testing — are freshest immediately after the contest. A long debrief feels thorough, but it usually rewards the loudest voice and the most dramatic bug. Fifteen minutes forces the team to separate facts from feelings and to leave with a training plan rather than a verdict.

Pick one person to run the clock and one person to take notes. The note-taker is not the coach and not the judge. Their job is to capture the timeline and the action items, not to assign blame.

Minutes 0–3: rebuild the timeline

Start with facts only. Go problem by problem and reconstruct the order of events: first read, first solve, first submission, first stuck point, first panic. Ask three questions:

Write the answers down. This is not the place for 'I thought you were doing it' arguments. If the team cannot agree on a fact, mark it as unclear and move on. The timeline is a map, not a trial.

Minutes 3–8: sort failures into three buckets

Most lost problems fall into one of three buckets. The distinction matters because each bucket needs a different drill.

Implementation failure. The algorithm was right, but the code was not. Classic examples: an off-by-one in a prefix sum, a forgotten long long, a graph traversal that marks visited too late. These are cheap to fix with repetition and testing habits.

Strategy failure. The team chose the wrong problem, split badly, or kept one person on a task for too long because abandoning it felt like waste. These are not fixed by writing more code. They are fixed by practising problem selection and time checks.

Knowledge gap. Nobody knew the technique. This is the easiest bucket to identify and the easiest to over-react to. One unknown technique does not mean the team needs a six-week lecture series. It means someone should learn the pattern and teach it back in twenty minutes.

For each lost problem, assign one primary bucket. Do not let every problem become a knowledge gap. Most contest losses are implementation or strategy losses wearing a knowledge-gap costume.

Minutes 8–12: one drill per member

The output of the post-mortem is not a list of everything the team should study. It is one targeted drill per member for the next week. One. The drill should be small enough to finish and specific enough to measure.

Examples:

Write the drill on a card or in the team notes. Include the owner, the deadline, and the evidence that it was done. 'Practise graphs' is not a drill. 'Implement 0-1 BFS from scratch twice and write down the deque invariant' is a drill.

Minutes 12–15: write the next-week card

Close with a single card that the team can read before the next practice. Keep it to five lines:

This card is the difference between a debrief and a training plan. It also stops the same conversation from happening next week. If the team cannot fill it in fifteen minutes, the team does not have a plan; it has a mood.

Keep the ritual boring

The best post-mortems are a bit dull. No speeches, no blame, no heroic promises to 'grind graphs all week'. Just a timeline, three buckets, one drill each, and a card. Run it after the next local contest or online round and see whether the following week's practice feels different. If it does, the team has found a repeatable habit. If it does not, the post-mortem itself becomes the next thing to debug.

All Articles

Related Articles

Five Graph Habits That Cost Australian Teams Points

Five Graph Habits That Cost Australian Teams Points

Role Cards, Not Rigid Boxes: A 2026 Experiment for Monash ICPC Teams

Role Cards, Not Rigid Boxes: A 2026 Experiment for Monash ICPC Teams