The cycle meeting ends at four on a Friday. The medical director has walked through the new subgroup data, marketing has shown the refreshed visual aid, and the regional managers have run two role plays each. People leave the hotel ballroom (or close the video call) feeling that it went well. By Monday morning, some of what they heard is already harder to recall, and nobody knows which parts.
That is not a criticism of the people in the room. It is how memory works. The question for anyone who owns an internal event for the field in pharma (a cycle meeting, a launch meeting, a kickoff) is not whether forgetting will happen, but whether the event has been designed around it. Most are not. We think an event should be treated as the middle of the learning window, not its start or its end, and here we set out what that looks like before, during and after the day itself. This is an event-design guide for employee training. Events for HCPs are a different thing, and we keep them separate below.
Hybrid events solved access, not attention
A few years ago the debate was about format. Face to face or remote? Full congress presence or a virtual booth? Most organisations have settled into a pragmatic mix. National cycle meetings are back in person, regional updates happen online, and the large international kickoff has become a hybrid of plenary streams and local breakouts.
The format question turned out to be the easy one. Getting people into a session, physical or virtual, is now largely a logistics problem that event teams handle well. What has not improved much is what happens inside people's heads during and after the session.
Anyone who has sat through a two hour virtual plenary knows the pattern. Cameras go off after the first twenty minutes. Chat goes quiet. A few people are clearly answering email. In a ballroom the signals are subtler, but they are there: the phones under the table during the third data slide, the coffee break that runs long because the corridor conversation is more useful than the agenda.
None of this shows up in the metrics most events report. Registrations, attendance and a satisfaction score tell you that people came and that they did not hate it. They tell you nothing about whether a rep can now explain the secondary endpoint to a sceptical specialist in week three of the cycle.
Unrehearsed material fades fast, and spacing helps
We have written about the forgetting curve at more length elsewhere, so here is only the part an event planner needs. In 2015, Jaap Murre and Joeri Dros published a replication of Ebbinghaus' original forgetting experiment in PLOS One. It was a relearning experiment with a single participant memorising nonsense syllables. Measured as savings (how much less effort it takes to relearn a list), savings after 31 days were down to about 4%.
The study illustrates forgetting in its specific experimental task. It does not tell us how much of a cycle meeting a rep will remember next week. Clinical content has meaning, context and prior knowledge attached, and it will not follow a curve measured on nonsense syllables. We don't know the rate for your audience, and neither does anyone else until they measure it. What we do know is that leaving the content untouched for two weeks is a bad bet.
Unrehearsed material fades fast. Most event plans put the first follow-up email in week two, and never find out what faded.
This is where most event designs go wrong. The follow-up, if there is one, is a slide deck in the shared drive and a recap email some days later. That does very little. What works better, in our experience and in the learning research, is retrieval: asking people to pull the information out of their own heads, repeatedly, at spaced intervals, with feedback when they get it wrong. It is less comfortable than rereading.
Design the event as a window: before, during, after
When we help a team plan a cycle meeting, a launch meeting or a medical education event for the field, we think in three phases. The live day is the middle one, and often not the most important.
Before: find out what people already believe
Two to three weeks before the event, send short pre-reading and a set of questions on it. Not a test with a pass mark, just a handful of one-minute challenges on the topics the event will cover: the disease area, the mechanism, the key trial, the competitor's positioning.
This does three useful things. It primes the audience, so the plenary lands on prepared ground rather than cold. It gives the event team a picture of where the real gaps are before the agenda is locked. And it sets a baseline, so you can later say something honest about what changed.
A scenario we see often: the brand team assumes the field is shaky on the new efficacy data and plans forty minutes on it. The pre-event questions show the efficacy story is fine, but a large part of the team confuses two elements of the mechanism, and a smaller group is unclear on a label restriction. The agenda changes. The medical session spends less time on the efficacy slides and more on the mechanism, with a short, pointed segment on what the label does and does not allow.
That is a better meeting, and it cost almost nothing to find out.
During: make people answer, not just listen
On the day, the aim is to turn the audience from spectators into participants at regular intervals. After each block, a short round of questions on what was just presented. Five questions in sixty seconds is enough. People answer on their phones, the room sees the distribution of answers, and the speaker can address the most common wrong answer on the spot.
This changes the atmosphere of a session more than you would expect. When people know a question is coming at the end of the block, they listen differently. The medical director who has been talking to a room of half-attentive faces suddenly has a room that wants to know the answer.
As the meeting closes, run a short battle: teams or regions competing in a synchronised window on the full content of the event. It sounds like a gimmick until you watch it. The energy in a room during a well run twenty minute battle is quite different from the energy during a closing summary slide, and the competition is doing real work. Every answer is a retrieval attempt.
HCP education is a separate case, and we would not mix it with any of this. Scientific events for healthcare professionals are run by Medical under their own codes and review processes, with different objectives, and they are not a venue for promotional enablement or for competing on scores. If you want interactive questions there, keep them anonymous, without prizes and without any link to employee performance data, and let Medical and compliance decide what is appropriate. Everything else in this piece is about training your own people.
After: the four to six weeks that decide the outcome
This is the phase almost everyone underinvests in. A few days of follow-up questions is too short. Forgetting keeps running for weeks, and the cycle the event prepares for usually lasts longer than that.
What we recommend instead:
- In the first 48 hours, a round of questions on the most important content, so it comes back before it has had long to fade.
- Over the next four to six weeks, short, regular challenges (two or three a week) that bring back each key topic at increasing intervals.
- For each person, a focus on their own mistakes: the questions they got wrong come back to them, with a short fix, until they get them right on a later attempt.
- A second battle somewhere around week four, ideally tied to a real moment such as the first regional meeting after launch.
The individual focus matters more than people expect. A rep who already knows the dosing schedule does not need it drilled again, only checked later on. A rep who confused two subgroups needs to see that specific point again, soon, and then later. Sending everyone the same recap wastes the time of the people who already know and underserves the people who do not.
What you can measure when you design it this way
An event built around questions produces data as a side effect. Not satisfaction data, but knowledge data, broken down by topic, by team and by person.
The most useful measure is what we call a knowledge gap: one person, wrong on one question, at their first attempt. That gap counts as closed only when that same person later answers the same question correctly. It is a stricter measure than an average score, because it tracks individuals rather than averages, and it separates people who learned from people who simply never had the gap.
With that measure in hand, a post-event report can say things like:
- which topics the audience arrived weak on, and whether the event moved them;
- which teams or countries are ready for the cycle, and which need another push;
- which specific misconceptions survived repetition and need a manager or MSL conversation instead of more questions.
That last category is the most valuable. In our programs, some gaps receive a verified correction and others remain open. These are usually genuine misconceptions, often about mechanism or about how to position the product against a competitor, and people keep choosing the same wrong answer with confidence. More questions alone are unlikely to fix them. A coaching conversation, a ride-along or a short session with medical is the next thing to try, followed by a retest.
A fair objection: "our people are already overloaded"
This is the pushback we hear most, and it is a reasonable one. Reps have CRM notes to write, targets to hit, compliance training to complete. Adding six weeks of follow-up to every event sounds like more noise.
Three answers. First, the time involved is small: a one-minute challenge two or three times a week is less than the time most people spend on the event recap email they never open. Second, the questions are about the content they need in their next call, not a separate curriculum. A rep who can answer the objection question on Tuesday is better prepared for the specialist on Wednesday. Third, and this is the part that surprises people, a well designed competitive format is something people choose to do. Participation in these programs is typically high when the questions are relevant and the competition is between real colleagues.
The real cost is the opposite one. A national cycle meeting represents a large investment: travel, venue, speaker fees, and above all, a day or two of the entire field force not seeing customers. If much of what was presented has faded before the first call, a good part of that investment is lost, whatever the satisfaction scores say.
Why this matters more now
The pressure on field teams has not eased. IQVIA's Launch Excellence IX report (June 2025) estimates that about $200 billion of revenue is at risk from loss of exclusivity by 2030, and that companies will need an unprecedented number of launches, each performing consistently well, to fill the gap. McKinsey's analysis of 210 launches between 2003 and 2009, published in 2014, found that about two thirds of new drugs miss pre-launch consensus expectations in their first year, and that early underperformance tends to persist.
In that environment, every cycle meeting, launch meeting and kickoff carries more weight. The field has fewer chances to get the story right, and fewer minutes with each HCP to tell it. An event that informs people for a day is not enough. The event has to leave them able to use the content weeks later, in a real conversation, without notes.
Start with one event, not a program
You do not need to redesign your whole event calendar. Pick the next cycle meeting or brand meeting and add the three phases around it: a baseline two weeks before, questions during, and six weeks of short reinforcement after. Measure gaps at first attempt and gaps closed. Then compare what you learned with what the satisfaction survey told you.
At Atrivity, this is most of what we do: one-minute challenges between real colleagues, battles in a synchronised window, and Gap Fixing that sends each person the fix for their own mistakes, with readiness reported by team, country and topic. But the principle works whatever tool you use. The question to bring to your next event planning meeting is simple: what will our people still know six weeks after this event, and how will we know?