Certamus · Guide
Your first case competition
What actually happens, what the deadline really means, and the three things that separate a team that places from one that submits.
What you are actually being asked
A case brief looks like a business problem. It is really a test of whether you can decide something under conditions where nobody can be certain.
That distinction matters on day one. Teams entering their first competition tend to treat the brief as a research task: gather everything, understand the industry, then form a view. You run out of time at step two, every time.
Work the other way. Form a rough view in the first hour, then spend the rest of the time trying to break it. You will be wrong early, which is cheap, instead of uncertain late, which is fatal.
The deadline is not when you think
If submission is Sunday night, your deck is finished Saturday. The gap is not slack, it is the only chance you get to rehearse, and an unrehearsed talk wastes analysis you already did.
Almost every team gets this wrong, including us. The honest version is that work expands until the deadline eats the rehearsal, and the only fix is treating the practice run as the real deadline and defending it.
Three things that separate placing from submitting
Answer the question they asked. Not the adjacent question you had better material for. Read the prompt again at the end and check, line by line, that you addressed it.
Show your arithmetic. If the brief gives no financials, build them in the open, put the assumptions on a slide, and say that the finding is the ranking rather than the exact number. A panel forgives an assumption they can see. They do not forgive one they have to go looking for.
Cut to three. Whatever the analysis produced, the recommendation is at most three things. A deck with nine recommendations reads as a team that could not decide, and deciding is the thing being marked.
What nobody tells you
Most of the competition happens before you present. Judges have read the same brief twenty times, and by the third team they know which assumption is load bearing. They are not waiting to be impressed, they are waiting to see whether you found it.
So find it, and say it first. There is more on that in say the weak part first.
What the first week actually feels like
Mostly it feels like not knowing whether you are behind. There is no marking scheme visible, no feedback until the room, and a brief that could be answered twenty ways.
The teams that cope have one habit in common: they decide the answer early and spend the week trying to break it, rather than gathering material and hoping a conclusion appears. Gathering has no natural end. Breaking a claim does.
You are not being marked on effort
This is the hardest thing to accept in the first one. Nobody in the room knows you read forty pages of industry reports, and nothing in the marking rewards it unless it changed the recommendation.
Judges mark what they can see in eight minutes: whether there is an answer, whether the number under it is built rather than asserted, whether you know where it is weak, and whether it holds in Q&A. Everything else is preparation for those four things or it is not worth the hours.
Read the brief three times, on three days
Once to understand it, once to find what it is not saying, and once after you have a draft answer, when you will notice requirements you have quietly dropped.
The third reading is the one that catches the loss described in what actually loses: an excellent answer to a question the brief did not pose.
Losing the first one is the normal outcome
Most teams do not reach a final early, and the ones that improve fastest are the ones who write down why immediately afterwards, while the room is still fresh: the question nobody could answer, the slide the panel skipped, the moment the timing went.
That list is worth more than the result. Ours is on every case page, in the section on what we would do differently, which exists because the honest version of that note is the only part of a loss that compounds.