You finish a DevOps workshop. The slides were tidy, the demo ran, and the questions at the end were polite and few. Two weeks later, nothing has changed in how people work. If this sounds familiar, you are not alone, and the cause is rarely the content. This post is a small diagnosis in four parts: the symptom, the likely cause, a test you can run and a fix. The thread running through all of them is that training for “the team” lands with nobody, while training aimed at one particular quiet person at the back of the room often reaches everyone.
The symptom: a good session that does not stick
People nodded. Feedback forms said “useful”. Yet the next sprint looked the same, deployment steps were still done by hand, and the one person who actually asked a question privately admitted she was lost by the second half. Every trainer has met this pattern. It is easy to blame attention spans or motivation, but those explanations feel suspiciously convenient.
A better question is: who was I speaking to? If the honest answer is “everyone”, that is the diagnosis in a nutshell.
The likely cause: a made-up average learner
When a session is built for a whole room, the designer pictures an average attendee: moderately experienced, moderately curious, moderately busy. That person does not exist. Real rooms hold a developer who has never touched a production server, an operations engineer who distrusts automation, and a manager who wants to know why any of this matters. Pitch the talk at the middle and you miss all three.
The second cost is subtler. Speaking to everyone makes you cautious. You skip the concrete example because it might not apply to somebody, and you replace it with a general statement that applies to nobody. Listeners sense the vagueness, even if they cannot name it.
The test: find the person you were not speaking to
Here is a quick exercise you can do after any session. Write down the name of one attendee who said very little. Now ask three questions about her:
- What did she most likely hope to leave with?
- What was she afraid of being asked?
- How much attention could she realistically give after a day of her normal work?
If you cannot answer, you have found your gap. Interestingly, the process of answering usually reveals what the session lacked: an example drawn from her actual job, a pause for the nervous question, or a shorter close because she was already tired.
The fix: rebuild one segment for one person
You do not need to redesign the entire course. Choose one segment, the one that confused the most people, and rebuild it for her. Use her vocabulary. If she works with tickets and release notes, explain version control through those. If she writes scripts for a database team, begin with a script she might recognise.
Then shorten it. Most teachers are surprised by how much of a segment exists to protect the teacher: extra caveats, extra definitions, extra history. Cut what she would not miss. What remains tends to be clearer and, strangely, warmer in tone, because it sounds like a person talking to a person.
A worked example: the pipeline segment
Suppose your session included twenty minutes on continuous delivery pipelines. The original version defined the term, drew a diagram with several stages and listed benefits. Attendees saw a lot of boxes.
The rebuilt version addresses one imagined listener, a tester named in your head as Meera, who spends her Fridays running the same checks by hand. You open with her Friday: “Every release, you open the same spreadsheet, run the same steps, tick the same boxes.” Then you show where an automated pipeline could take over the repeated checks, and where it could not, so she keeps the judgement calls. The diagram arrives last, as a summary of a story she already follows.
Same topic, same twenty minutes, very different effect. Notice that you did not remove the content. You gave it an owner.
What to do in the room itself
Preparation helps, but the live moment matters too. Walk to the part of the room where the quiet person sits. Ask a question that has no wrong answer, such as “what does this step look like in your current job?” Then wait longer than feels comfortable. Silence after a good question is not failure; it is thinking time, and a nervous learner often needs it more than anyone.
If you teach online, the same idea applies with small changes. Offer a chat channel for private questions, tell people that a confused look is welcome information, and end each section with one sentence that begins “if you are new to this, the thing to hold on to is”. That sentence is addressed to exactly one person, and she will notice.
Common objections
“But I have forty people in the room.” Yes, and each of them is one person at a time. Speaking vividly to one often lets the others see themselves in the example. A concrete case is easier to adapt than an abstract rule.
“Won’t the others feel left out?” Rotate the imagined listener from segment to segment: the sceptic, the newcomer, the manager, the on-call engineer. Over a session, everyone gets a turn at being the one you are talking to.
“Does this take more preparation?” Slightly at first, then less. A clear picture of a listener makes decisions faster, since you can ask “would Meera care?” and move on.
Connecting it to the wider picture
Behind most stuck training lies a broader theme: change is carried by people, and people take it in one conversation at a time. The write-up on steering people through a change in working culture makes the same point at organisation scale. And if your attendees struggle with the vocabulary itself, pairing the session with a gentle reference such as a beginner-friendly glossary of the terms people meet first saves the trainer from stopping every few minutes to define jargon.
How long until you see a difference?
Do not expect a transformation overnight. The first sign is usually small: a question that arrives by message the next morning, or a colleague who tries one new habit and mentions it at stand-up. Treat those as evidence that the segment reached somebody. Write them down. After three or four sessions built this way, you will have a private collection of real reactions that tells you far more than a satisfaction score ever did, and it will guide the next rebuild.
Keeping what you learn
After each session, jot a few lines for yourself about who you were talking to and what happened. Over time you will notice patterns in which imagined listeners work best. Some trainers share these reflections publicly, as short stories for one imagined fellow trainer. One option is iBlogUp, where each author gets a personal subdomain for their stories and followers can subscribe by feed, though a private notebook serves the purpose equally well. What matters is the habit of reflecting on a specific person, not the venue.
A short checklist for your next session
- Name the one person each segment is for.
- Open the segment with a moment from her working day.
- Remove anything she would not miss.
- Leave a pause for the question she might be too shy to ask.
- Afterwards, ask her directly what stuck.
The cure for a session that did not stick is rarely more slides. It is a clearer picture of a human being in the room, and the willingness to speak to her plainly. Do that, and the rest of the room often follows without being told.