Post-Workshop Behavior Reinforcement: How to Pick the Two Behaviors and Write Them So People Can Do Them
Post-workshop behavior reinforcement starts one step earlier than most plans admit: deciding which behaviors you are actually reinforcing. Pick two, not nine, and write each one as a trigger plus an action a person can perform on an ordinary Tuesday. Everything downstream, the daily cue, the manager scripts, the measurement, depends on that sentence being specific enough to do. Most programs skip it, carry a list of themes out of the room, and then wonder why nothing moved.
Here is the test. Ask three people who attended your last workshop what they are supposed to be doing differently.
If you get three different answers, or three themes, the reinforcement problem is not the cadence. It is upstream of it.
Quick answer
Choose two behaviors and write each as "when this happens, I will do this." Run a four part filter over any candidate: it has to be observable, available daily, inside the person's control, and costly to fake. Then rewrite the theme the workshop produced into that sentence. Two specific behaviors across 66 days changes two habits. Nine vague ones across 66 days changes nothing, because the daily cue, the manager's attention and the measurement all get divided nine ways.
Key takeaways
- Two behaviors. Occasionally one. Nine reinforce none.
- Four part filter: observable, available daily, in their control, costly to fake.
- Write the trigger, not just the action. "When X happens, I will do Y" is the form research backs at 2 to 3x on follow-through across 94 studies (Gollwitzer).
- A theme is not a behavior. "Accountability" cannot be practiced. Returning a decision with one question can.
- The rest of the workshop stays knowledge. Reference material, not a daily cue.
Why workshops produce themes instead of behaviors
Not a criticism of workshops. It is what a workshop is built to do.
A good two day session covers models, cases and discussion. It ends with energy and a shared vocabulary, which is a real output. But vocabulary is where it ends, and vocabulary is not practiceable. People leave saying "we need to be more accountable" because that is the altitude the room was operating at.
Then the follow-up plan inherits that altitude. The daily action becomes "reflect on accountability today," the manager is asked to "reinforce accountability," and the report at the end measures how many people opened the email. Research puts classroom to job transfer at 10 to 20%, and without structured follow-up 75% of managers show no measurable improvement (Brandon Hall Group). A large share of that gap is not a cadence failure. It is a specificity failure that happened before the cadence started.
The four part filter
Run every candidate behavior through these four tests. A behavior that fails any one of them will not survive 66 days.
| Test | The question | Why it matters |
|---|---|---|
| Observable | Could someone watching the person tell whether it happened? | If only the person knows, you cannot count it and the manager cannot recognize it |
| Available daily | Does the situation that triggers it come up most days? | A behavior that fires twice a quarter cannot form a habit inside the window |
| In their control | Can they do it without anyone's permission, budget or calendar? | Anything requiring approval stalls in week one and teaches people the program is theater |
| Costly to fake | Does doing it require real effort or a real choice? | A behavior that can be performed without thinking produces compliance, not change |
"Give more recognition" passes observable and daily, but it is cheap to fake. "Run better one to ones" fails availability for most managers, since they happen weekly at best. "Hand decisions back" passes all four, which is why it keeps showing up in programs that work.
Rewriting a theme into a behavior
This is the table to take into the last twenty minutes of your next workshop.
| What the room produced | What it has to become |
|---|---|
| Be more accountable | When I commit to a date in a meeting, I will say it out loud and write it in the notes before the meeting ends |
| Empower the team | When a report brings me a decision they could make themselves, I will hand it back with one question |
| Communicate better | When I send a request, I will state the deadline and what done looks like in the first two lines |
| Give more feedback | When I see something worth repeating, I will name the specific action within 24 hours, not at the next review |
| Listen more | When someone brings me a problem, I will ask one question before offering a solution |
| Be more strategic | When I plan my week, I will block one hour that is not reactive and name what it is for |
Notice what every row on the right shares. A trigger, an action, and a way to know afterward whether you did it. That is not a writing preference. It is the implementation intention structure, which across 94 studies produces a 2 to 3x effect on follow-through (Gollwitzer).
The Tuesday test is the shortcut when you are in the room and short on time: can a person do this on an ordinary Tuesday with no crisis on? The longer version of that test, and the rest of the last twenty minutes, is in The Day After the Offsite.
Why two and not nine
Nine behaviors feels responsible. The workshop covered nine things and leaving any out feels like waste.
But the constraint is not what the program can deliver. It is what a person can hold. Every behavior you add divides three scarce things:
| What gets divided | What happens at nine |
|---|---|
| The daily cue | Each behavior gets a prompt every nine days, which is not repetition |
| The manager's attention | The manager recognizes nothing specific, because nothing is specific |
| The measurement | Nine thin numbers instead of two you can defend to a sponsor |
Two behaviors over 66 days is two habits. Nine behaviors over 66 days is a newsletter.
The honest version of the conversation sounds like this: we taught ten things, we are changing two, and the other eight are reference. Saying that out loud protects the program, because it sets the standard the program will be judged against.
What happens to the rest
The eight you are not reinforcing are not wasted. They are knowledge, and knowledge has a different delivery mechanism than behavior.
| The content | Where it belongs |
|---|---|
| The two target behaviors | The daily cue, the manager script, the dashboard |
| Models and frameworks taught | A reference people can reach for when the situation comes up |
| Context and case discussion | The shared vocabulary, which the workshop already delivered |
| The nice to have behaviors | The next campaign, after these two are automatic |
That last row matters. Behaviors you decided not to reinforce are not rejected, they are queued. A second campaign after the first one closes is a far better outcome than nine behaviors fighting each other for sixty six days.
Turning two behaviors into sixty six days
Once the behaviors are specific, the daily unit almost writes itself. Each day takes one behavior and gives the person a single, small version of it to perform today, ending in a commitment.
A week on "hand decisions back" is not the same prompt seven times. It is seven angles on one behavior: notice when it happens, try the one question version, try it with someone more junior, notice what you did with the time you saved, hand back something harder, ask a report what they wished you had handed back, name the one you got wrong.
That is what makes repetition tolerable across 66 days, which is the median time to automaticity and up to 254 days for complex behaviors (Lally et al., UCL). The reason the window is that long is in The Science of 66 Days.
What it produces when the behaviors are specific
| Organization | What was reinforced | Result |
|---|---|---|
| JetBlue | Front line supervisor behaviors across six airports | Leadership nominations up 91% |
| Romano's Macaroni Grill | Manager behaviors in half the restaurants, compared against the rest | Manager turnover cut 60% year over year; 72% improved on every measured behavior |
| A global professional services firm | A behavior sprint after a multi-day workshop for 1,500 leaders | 91% enrolled voluntarily; 96% of commitments made were completed |
| PPG | Behaviors from cohort workshops, carried by a daily layer | Self reported gains of 89% on positive interactions, 85% on encouraging innovation |
The independent read on the mechanism is the Claremont Graduate University evaluation (Felkey et al. 2021): 136 employees, daily prompts each ending in a commitment, a 64% check in rate against a 41% industry average, p < .001. Check in and NPS were measured directly; wider organizational outcomes were extrapolated.
How ProHabits fits
ProHabits is the reinforcement layer for leadership development, and the behavior selection above is the input it runs on.
You bring the two behaviors. We turn each into a sequence of MicroActions, one a day, by email or text, no app and no login: a question, evidence with a named source, one action for today, and the I commit button. The manager gets five scripted moments across the window. The dashboard reports commit rate, completion of commitments and stories shared by segment, so you can see which of the two behaviors is moving and which needs another week.
If you are not sure your two behaviors pass the four part filter, that is the conversation worth having before anything gets built.
90% of training vanishes in a week. ProHabits makes it stick.
The full argument, with the day after framed as the product, lives here:
The Day After Leadership Training
Keep reading
- The Day After Leadership Training, the cornerstone
- The Day After the Offsite, on the last twenty minutes in the room
- How to Reinforce Leadership Training, on the five mechanisms
- Leadership Training Follow-Up Program, on build versus buy
- How to Measure Leadership Behavior Change, on counting what moved
- The Science of 66 Days, on the window
Two next steps
Send us the behavior list from your last workshop and we will tell you which rows pass the filter, or build a campaign around the two that do.