How a Digital Communication lesson gets built, from draft to final video call

Every lesson in Digital Communication Skills begins with something a learner has actually tried to do and found awkward. Someone wanted to reply to a grandchild's message without the keyboard jumping about. Someone else was invited to a video call and sat looking at the link for ten minutes. I keep a running list of these moments, and the lesson topics come from that list rather than from a menu of software features.

Once I have chosen a situation, I write down the single outcome the learner should reach by the end. Not three outcomes, one. A lesson might end with a short email sent to a friend, or with a camera and microphone switched on and working before a call. If I cannot state the outcome in one plain sentence, the lesson is too big and I split it before writing anything else.

• One situation per lesson
• One outcome stated in a single sentence
• Split anything that needs two

The first draft is deliberately plain. I write each step the way I would say it across a table: open the message, tap the box that says reply, type your first line. I avoid shortcuts and jargon until the learner has met the word in context, and when a term like attachment or mute is unavoidable, it gets a short explanation the first time it appears.

I also write in the order things happen on the screen, not in the order that is tidiest for me. That means mistakes are included. If a common slip is sending a reply to everyone instead of one person, the draft shows what that looks like and how to notice it before pressing send, so the learner is not surprised later.

A draft is only a guess until someone follows it. I ask friends and former students, adults of different ages and comfort levels, to work through a lesson without my help while I watch quietly. I do not explain or rescue. Where they pause, squint, or ask what a word means, I mark the spot, because that is where the lesson is unclear rather than where the learner is slow.

These sessions regularly change the lesson. A step I thought was obvious turns out to hide two actions. A button I described by its icon is easier to find by its label. I would rather discover this in a living room than after the lesson is published, and I repeat the test after every significant rewrite until people get through it without stopping.

• Observe without helping
• Mark every pause
• Retest after rewrites

Video calls are the part learners worry about most, so the practice is designed to feel low pressure. We use a rehearsal exercise where you open a practice screen, check how you look and sound, and learn where the controls sit, all before anyone else is on the line. The aim is to remove the surprise of seeing yourself on screen for the first time.

I also build in the awkward realities: a frozen picture, a muffled voice, a call that starts before you are ready. Learners are shown what each looks like and the calm first thing to try. Knowing that a glitch is common and fixable does more for confidence than any amount of reassurance, and it keeps the first real call from feeling like a test you could fail.

After testing comes the part people rarely see: cutting. I remove any step that does not serve the one outcome, shorten sentences, and replace general advice with a specific example. A lesson that asks the learner to hold too much in mind at once gets split. Short pieces are easier to repeat, and repetition is how these skills settle in.

I then read the finished lesson aloud and time it at a gentle pace, leaving room for the learner to pause and try each step on their own device. If I find myself hurrying through a paragraph, that paragraph is too dense. The final check is simple: could a patient friend follow this over a cup of tea without needing me in the room.

No lesson is ever truly finished. Software changes its layout, learners bring new questions, and phrases that read clearly one season can feel stiff the next. I revisit each lesson when something shifts and adjust the wording, not the purpose. The aim stays the same: a learner finishes feeling that writing an email or joining a call is something they can do on an ordinary day.

I would also rather say plainly what a lesson does not cover. It will not turn anyone into a polished writer overnight, and it does not replace practice with the people you actually want to talk to. What it offers is a calm starting point, a clear sequence, and permission to go slowly.