Keystone Symposia · Study Group

The Work Behind the Conference.

Role
Product direction, workflow design, development
Organization
Keystone Symposia
Stack
Next.js, TypeScript, PostgreSQL
Stage
In development · 2026

The operational perspective

Built from the inside.

My work at Keystone Symposia began in Marketing and Communications: filming scientists, designing meeting materials, publishing content, and helping complex research reach its audience. Over time, the work took me deeper into the technology and operations behind that communication.

Years spent building websites, supporting live programs, and working across conference operations accumulated into an understanding of the organization’s handoffs, exceptions, and institutional memory. I brought that perspective into Study Group: a platform for the work that happens before a conference reaches its audience.

Study Group cycle overview showing preparation, reviewer rosters, scientific review, and deliberation
The staff workspaceA planning cycle connects concepts, people, review rounds, and the next stage of work. Fictional demonstration data.

From idea to program

3 connected stages
01

Shape the ideas

Community proposals, recurring topics, and staff knowledge become concepts with enough context for a useful scientific review.

  1. Public proposal intake
  2. Staff preparation and screening
  3. Scientific categories
  4. Previous meeting context
02

Gather judgment

Experts review the science, share discussion, and submit private feedback. Staff follows coverage and prepares the evidence for advisory deliberation.

  1. Reviewer workspace
  2. Shared discussion and guidance
  3. Saved and submitted feedback
  4. Consolidated review results
03

Develop the program

Staff decisions carry scientific direction into organizer briefs, detailed programs, advisory meetings, and required revisions.

  1. Commissioning and organizer teams
  2. Versioned program proposals
  3. Meeting agendas and workbooks
  4. Revisions and scientific approval

Scientific continuity

  1. Concept
  2. Study Group input
  3. Advisory recommendation
  4. Commissioning
  5. Program development
  6. Review and revision

The product decisions

The handoffs carry the meaning.

A conference begins with an idea and develops through many people’s judgment. Forms, surveys, email, spreadsheets, and meeting books each hold part of the story. Staff maintains continuity by knowing where to look and remembering how the pieces relate.

I translated those relationships into explicit workflows. A reviewer’s response, an advisory recommendation, and a staff decision carry different authority. The platform preserves each contribution and makes the next commitment visible.

Fictional Cellular Communication review with scientific context, staff guidance, and shared discussion
The reviewer experienceScientific context, staff guidance, discussion, and private feedback stay together. Fictional example.
Fictional scientific program editor with commissioned brief, saved revision, and program overview
Program developmentA commissioned brief develops into a detailed, versioned scientific program. Fictional example.

What the system preserves

4 design decisions
Scientific context
The rationale, feedback, and guidance travel with the idea into later stages.
Responsibility
Review input, advisory recommendations, appointments, and staff decisions have separate authority.
Version history
Submitted programs, closed results, and published meeting materials preserve the versions people used.
Access
Private drafts, structured feedback, discussion, and staff notes have explicit audiences.

Institutional memory

Make experience available.

Experienced colleagues bring years of context to planning: previous programs, organizers, speakers, attendance, and related scientific themes. The historical-program archive gives that knowledge a searchable place and lets selected editions accompany new review material.

Agendas and workbooks draw from the same scientific records. Submitted versions, closed results, and published meeting materials preserve what people actually used, so the reasoning remains available as the work moves forward.

Fictional SAB planning workbook with agenda navigation and scientific breakout programs
The meeting workbookThe agenda, assigned scientific breakouts, and selected program versions form one meeting reference. Fictional example.

My contribution

From organizational knowledge to a working product.

  1. Translated accumulated operational knowledge into the product model, scientific planning lifecycle, and connected staff experience.
  2. Designed and developed concept intake, expert review, program development, and meeting preparation workflows.
  3. Defined version history, explicit responsibilities, and access rules that preserve the meaning of scientific decisions.
  4. Built illustrated documentation and fictional demonstration scenarios for evaluation and staff walkthroughs.