Reviewing a conference from recorded talks: how to draw shared conclusions
Write an analytical conference review from recordings: choose a question, compare talks, preserve disagreements and distinguish your conclusions from the speakers’ words.
A list of talks doesn’t explain the topic
“First one speaker spoke, then another” tells readers what was on the programme, but rarely explains what the talks added to our understanding. An analytical review starts with a reader’s question: which approaches came up, where did they agree and what remained in dispute?
Set the scope at the start. If you watched one track, name it rather than attributing its conclusions to the whole conference. Record the event date and the version of the recordings. Slides, supporting material and later clarifications may change how you interpret what was said on stage.
Compare the talks before writing
State the question your review answers
Choose a topic the talks you watched really have in common. Keep it narrow enough for a useful comparison. For example, instead of “everything about teamwork,” look at ways of passing decisions between project members and where each method falls short.
Make a record for each talk
Record the main claim, example, supporting evidence and conditions for each talk. Keep the speaker’s name, talk title and timestamp. Separate claimed results from the data the speaker showed. A success story does not necessarily tell you how anyone measured the result.
Look for similarities and differences
Compare answers to the same question. Check whether the context, team size and type of task are comparable. An apparent contradiction may come from different conditions. The same words may hide different definitions that you need to explain to readers.
Draw a conclusion and state its limits
Group the sections by theme if that makes more sense than following the programme order. Support each general claim with specific talks. Mark your interpretation separately, along with open questions and the evidence missing for a stronger conclusion.
Two talks on recording project decisions
This is a fictional training example. The names, circumstances and outcomes are included solely to explain the method.
In one talk, the speaker showed a short decision log used by a small team. The other discussed how several departments with different responsibilities sign off on decisions.
Both approaches record decisions, but they operate under different conditions. A more complex process in the second talk doesn’t make the simpler format obsolete.
A review can explain the shared principle: the next person must be able to find the decision and interpret it correctly. Then show how scale and decision-making authority change what goes in the record and how it is approved. This is the reviewer’s analysis, not a direct quotation from the conference.
| Criterion | Talk A | Talk B |
|---|---|---|
| Context | One team | Several departments |
| Focus | Find the decision quickly | Understand who can sign off |
| Open question | How do they update old records? | How do they avoid delays? |
Comparison matrix for a conference review
Fill in the same fields for each selected talk. That makes it easier to see where the comparison relies on incomplete information.
Event / date / track covered: Reader’s question: Talk and speaker: Main claim: Context of use: Example and supporting evidence: Limits stated by the speaker: Timestamps and materials: Where it agrees with other talks: Differences and possible explanations: Our analytical conclusion: What is still unknown:
Check the accuracy of your generalisations
- The review states what it covers.
- It is clear who made each important claim.
- The conditions behind the approaches have been compared.
- The author’s conclusion is presented separately from any agreement between speakers.
A closer look
Do I need to summarise every talk?
No, if the review has a clear theme. Explain how you chose the talks and use those that help answer the question.
What if one talk wasn’t recorded?
State the limitation and use only material readers can verify. Don’t reconstruct exact quotations from a vague memory.