Blog

Turn a conference into a useful handoff for your team

A conference can fill a notebook and still leave a team no wiser. Notes often stay with the person who attended, while colleagues receive a hurried summary days later, stripped of context and hard to act on. A better approach is to treat attendance as a handoff: collect a small number of useful ideas, record what they mean for your organisation, then pass them on in a form someone else can use.

That handoff starts before the event. Look at the programme and choose sessions based on decisions your team may need to make, rather than trying to attend everything. If a speaker or contributor interests you, check their public profile in advance; for example, the samir jaber page can be part of that background reading. The aim is to arrive with a question, not a stack of biographical details.

Choose a question before choosing a session

Give each session a job. You might want to understand how another organisation handles a recurring problem, find evidence for a proposal, or hear how a new method works in practice. A clear question makes it easier to decide which talks deserve your time and what to listen for once you are there.

Keep the list short. Two or three questions are usually enough to guide a day without turning every conversation into an interview. Write them somewhere easy to reach, and leave room to follow an unexpected topic if it proves relevant.

Take notes for someone who was not there

Raw notes make sense to the person who wrote them, but they often fail as a handoff. Record the speaker’s main point in plain language, then add the example or evidence that supports it. Mark your own interpretation separately. This distinction helps colleagues tell a reported claim from your assessment of it.

It also helps to capture the conditions around an idea. A method that worked for a large institution may not transfer directly to a small team. Note the resources, constraints or assumptions the speaker mentioned. Those details are often what determine whether an idea can be tested at home.

Use a consistent note format

A simple template reduces the work of turning several sessions into one coherent account. Use the same headings for each session, and leave a blank field when you do not have an answer rather than filling the gap with guesswork.

  • Question: What were you hoping to learn?
  • Main point: What did the speaker argue or demonstrate?
  • Evidence: Which example, result or source supported the point?
  • Conditions: What resources or circumstances shaped the approach?
  • Team relevance: Where might this connect with current work?
  • Next step: What small action could test the idea?

These notes do not need to read like polished minutes. Short, specific phrases are easier to review than long passages copied from slides. If a claim needs checking, mark it clearly and verify it before including it in a recommendation.

Make the handoff small enough to happen

Within a day or two, turn the notes into a brief update. Start with the question the team cares about, explain the most relevant finding, and state what you think should happen next. One page is often enough. Include links to relevant materials only when they help colleagues check a detail or explore the subject further.

Separate information from action. A useful update might say that a speaker described a particular process, that it appears relevant to a current project, and that the team could test one part of it over a fortnight. This gives colleagues a concrete proposal without presenting a conference anecdote as settled evidence.

Close the loop after sharing

A handoff is complete when someone uses it, questions it or decides to leave it aside. Ask colleagues which points were useful and what remains unclear. Their response can shape a follow-up conversation, a small trial or a decision not to pursue the idea.

Then record the outcome where the team can find it. A short note on what was tested, what happened and what changed gives future attendees a starting point. Over time, conferences become part of the organisation’s working knowledge rather than isolated days away from the office.