Outcome-sharing events — how they differ from ordinary events

An outcome-sharing event has many talks, many presenters, and many files. Getting each deck on the right screen at the right moment matters far more than stage production. And the work doesn't end with the event — the satisfaction results, photos, and improvement proposals still have to become a report the next program plan can use.

Three things that make it different

• The materials are the star — intake, version control, running order, and on-site switching are the core of operations
• The audience is the stakeholders — most attendees are presenters or evaluators, raising the bar for registration and protocol
• Reporting is mandatory — photo records, satisfaction surveys, and the final report are the event's real deliverable

Presentation management is half the job

Decks keep changing until the day before. Two deadlines are realistic: a first intake to check format and length, and a final version locked the day before the event. On site, files are staged in running order so one operator switches everything from a single screen. At the Yonsei RISE outcome-sharing event, this carried two symposium blocks and a discussion session in one flow.

Don't end the program at the last slide

Stop at the presentations and it's just a report meeting. Add Q&A, open discussion, and networking after the talks, and the day's results feed the next decision. When one team runs both the program and its report session — as with Ajou's IPE report session — participant context carries over and discussion design gets easier.

The report is part of the event

Shoot photos in distinct sets — presentations, discussion, networking. Run the satisfaction survey immediately after the event, when response rates peak. The final report pairs the scores with proposals for the next edition. The RISE event scored an average of 4.95 from 29 respondents, and its report included proposals like a stronger presentation archive and more discussion time.