How to build an annual event improvement roadmap
The review meeting produced thirty good ideas, and by March nobody remembers which ones were meant to happen.
The short answer
An improvement roadmap is a short list, usually three to five items, chosen from the year's lessons by impact and effort, each with an owner, a date and a way to check it worked. It sits beside the event calendar so the work fits the weeks you really have.
Take inputs from event recurring failure analysis, the event annual supplier review and the budget view in event portfolio budget forecast. Then choose, rather than keep everything.
Collect candidates in one place
- Repeated problems from the failure log, ranked by how often and how much they cost.
- Supplier changes arising from the annual review.
- Attendee, speaker and member feedback that came up more than once.
- Cost or effort that kept growing, such as manual registration reconciliation.
- Ideas from committee members, kept separate from problems so they are not confused.
Choose by impact and effort
Score each candidate on impact and effort as low, medium or high. Start with high impact and low or medium effort, then add at most one larger piece of work if capacity allows.
| Impact | Low effort | High effort |
|---|---|---|
| High impact | Do this year. Schedule first. | Do one if capacity exists. Break into stages. |
| Low impact | Do when spare time appears. | Drop or park, and write down why. |
Steps to a roadmap the committee will follow
- List candidates and score them in one meeting, with the owner of each present.
- Select three to five items and write the reason for each rejected idea.
- For every item, write the outcome in plain words, the owner, the start and finish dates, and the evidence that will show it worked.
- Place each item on the calendar in weeks with spare capacity, checking against your calendar capacity planner or equivalent sheet.
- Review progress quarterly and move or drop items openly if capacity changes.
Why roadmaps stall
- Too many items. Anything beyond five tends to slip.
- Improvements scheduled in the same weeks as the busiest events.
- No evidence defined, so nobody can say whether an item is finished.
- An owner who changes at the committee rotation with no handover of the item.
Worked example · Fictional example
Four items chosen out of nineteen
Fictional organisation and figures, for illustration only.
Persatuan Fiktif Juruukur Bahan listed nineteen ideas after its annual conference. The committee scored them and chose four, one of which required a supplier change.
The roadmap places the registration-plan decision date in January, the supplier comparison in April and the post-event survey redesign after the conference. It records that a mobile app idea was parked because of effort and cost, with the reason noted for next year.
| Item | Impact | Effort | Owner | Dates | Evidence it worked |
|---|---|---|---|---|---|
| Registration plan decided 8 weeks out | High | Low | Programme owner | Jan to Feb | Plan signed off by date |
| Compare two AV suppliers | High | Medium | Treasurer | Apr to May | Written comparison to committee |
| Handover pack template | Medium | Low | Secretary | Mar | Template used for next committee |
| Redesign post-event survey | Medium | Low | Secretariat | After conference | Response rate compared to last year |
Use this yourself
Annual improvement roadmap
Limit the table to five rows. Keep the parked and rejected list underneath with reasons.
| Improvement (outcome in plain words) | Source (failure log, supplier review, feedback) | Impact | Effort | Owner | Start | Finish | Evidence it worked | Quarterly review notes |
|---|---|---|---|---|---|---|---|---|
Handle it in-house, or bring in help?
Your team can usually handle this when
- Your events are few and one person can hold the roadmap.
- The committee reviews progress at meetings it already holds.
- Items are small and mostly within the secretariat's control.
Outside planning help earns its fee when
- Improvements keep losing out to the next event's workload.
- Items need coordination across committees, suppliers or several events.
- A new committee needs a roadmap carried forward without losing the thread.
Need someone to keep the roadmap moving?
A recurring programme manager can run the selection meeting, place each item in weeks with capacity, chase owners and report progress to your committee each quarter. What to improve, what to spend and which suppliers to change stay with your committee. The roadmap then carries across committee changes with its record intact.
Questions organisers ask
How many improvements should be on the roadmap?
Three to five for most small teams. A short list that is finished teaches the committee that the roadmap works.
Where do big ideas go?
Park them with a reason and a review date. Large items can be broken into stages, with only the first stage on this year's roadmap.
Who should own the roadmap?
One person, usually the secretariat head or portfolio coordinator, with each item owned by whoever can actually do it.
What if capacity falls during the year?
Move or drop items openly at the quarterly review and record why. Quietly letting them slip leaves nobody knowing what was decided.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.