A full schedule can still produce an empty symposium.

Each speaker presents good work. The audience asks a few questions. The next session begins. At the end, participants have heard several talks and share no clearer account of what the field should do next.

Chairing and co-chairing symposium programs across ICPC World Finals cycles changed how I think about convening technical communities. I now design the program around a question that several talks can answer differently.

Choose a question with a decision behind it

“Competitive programming education” is a topic. It can hold almost any submission.

A useful program question creates a boundary. How should a university move students from a first contest to independent practice? Which parts of contest infrastructure should be shared across regions? What evidence would show that a curriculum transfers beyond familiar problem types?

The question should matter to someone who can act. A coach may revise a training sequence. A contest director may adopt a tool. A researcher may test a claim that practitioners currently settle by intuition.

I write the expected decision or next investigation before inviting speakers.

Select disagreement the audience can inspect

Variety of affiliation does not guarantee variety of thought.

Two speakers may use different vocabulary while making the same recommendation. Another pair may appear to disagree because they serve different student populations. The program should make the controlling difference visible.

I look for contributions that vary along a useful dimension: scale, student preparation, contest level, institutional support, geography, or evidence. The speaker should be able to state the conditions under which the method worked.

This lets the audience compare claims without turning the session into a contest between personalities.

Prepare the connection before the event

Speakers naturally optimize their own talks. The chair has to optimize the session.

Before the event, I share the program question and ask each speaker for the claim, evidence, and boundary they intend to present. I identify overlap while there is still time to change it. I also send one question that connects each talk to another contribution.

This preparation should improve the talks without making them uniform. The goal is a common surface for comparison.

When speakers first encounter one another’s arguments on stage, the session spends its limited discussion time discovering the agenda.

Give the audience work

An audience can listen carefully and leave every decision to the panel.

I want participants to test the claims against their own setting. A short prompt can ask which assumption fails at their institution, which artifact they could reuse, or which measurement they would need before adopting the method.

For a small room, participants can compare answers directly. For a larger program, the chair can collect questions by category and use them to choose the discussion path.

The audience should know why a question was selected. “We have time for one more” is scheduling. “Several coaches reported that this method assumes weekly staff support” is synthesis.

Preserve decisions and unresolved questions

Recordings preserve presentations. They rarely preserve what the community learned across them.

The program record should capture:

  • the question the session addressed;
  • the distinct claims presented;
  • the conditions attached to each claim;
  • resources participants can use;
  • disagreements that remained;
  • an owner or venue for the next step.

I avoid manufacturing consensus. A clear unresolved question is a useful result when the session has exposed the evidence needed to settle it.

The record also helps the next symposium avoid restarting from the same broad topic.

Build the next chair into the cycle

A recurring symposium should not depend on one person’s invitation history and private context.

The operating record needs selection criteria, speaker status, communication templates, program decisions, deadlines, and post-event findings. A future chair should be able to see why the schedule took its final form.

I also want other organizers to own complete parts of the cycle while the current chair is available. Someone can lead one track, run speaker preparation, or produce the session record. Shared visibility is not the same as shared responsibility.

Review the symposium by what moved

Attendance and speaker quality matter. They do not settle whether the convening worked.

After the event, I ask:

  1. Which program question became easier to answer?
  2. Which conditions explained disagreement between speakers?
  3. What did participants identify as usable in their own setting?
  4. Which unresolved question now has a sharper test?
  5. Which artifact or collaboration continued after the session?
  6. Can the next chair reconstruct the decisions behind the program?

A symposium earns another cycle when it leaves the community with better questions, inspectable choices, and people prepared to carry the work forward.