Skip to content

Prepare for Your Next Program

Overview

The most useful thing about reviewing one program is that it makes the next one better. This article is the bridge: take what you learned from the program that just ended and turn it into concrete adjustments before you launch the next one.

When to use: between programs — after you have analyzed outcomes, before you start setting up the next program.

For analyzing what happened, see Analyze Program Outcomes. For the mechanics of duplicating a program, see Copy a Program.

How to Use It

Start with what you learned

Before opening Eventene, write down the answers to a few questions:

  • What worked well that you should keep doing?
  • What did not work that you should change?
  • What surprised you — for better or worse?
  • What would you do differently if you were starting today?

You probably already touched on these in Analyze Program Outcomes. Treat that note as your starting point.

Reuse the structure, not the data

Most of your previous program is reusable. Copy it and adjust:

  1. Copy the program — see Copy a Program
  2. Update dates and times — shift everything to the new schedule
  3. Refresh activities — drop, add, or restructure based on what you saw
  4. Update questions — keep what worked, rephrase what did not
  5. Reuse tags and email templates — keep your team on consistent terminology

Copying preserves the structure, questions, and tags but does not bring participants or responses with it. Each new program starts clean on the data side.

Adjustments that come from real lessons

A few common patterns and what to do about them:

  • High no-show rate on an activity — reduce capacity, send earlier or more frequent reminders, or reconsider the time slot
  • Low response rate to a question — rephrase it, make it optional, or remove it
  • An activity filled instantly with a long waitlist — add a second session or raise capacity
  • A required Product caused friction — reconsider whether it should still be required, or whether the price needs to change
  • Walk-ins were common — embrace them (offer on-site registration) or reduce them (better pre-event reminders)
  • Communications were sent reactively — pre-schedule the routine ones for the next program

Reuse what saves time

Some pieces of your setup compound across programs the more you reuse them:

  • Tag scheme — the same VIP / Speaker / Workshop tags work across programs
  • Email message types — standard invitation, reminder, and confirmation messages can be reused with small tweaks
  • Group structures — your main groups and subgroup rules often carry over

The goal is not to start every new program from scratch, but to start it from a base that has already learned a few lessons.

Tips & Best Practices

  • Do this work soon after the program ends, while details are fresh
  • Capture lessons in a short note attached to the program — a paragraph is plenty
  • Avoid changing too much at once between programs — change a few things deliberately so you can tell what helped
  • Share lessons with the team; the people who ran the event often see things the data does not show