Session 3: Running an Online Classroom
Teaching online is not teaching in a room with a camera. This session covers running a real online classroom: video meetings, screen sharing, presentations, digital whiteboards, recording — and handling the technical failures that decide whether a lesson happens at all.
Learning objectives
By the end of this session you will be able to do each of these without prompting.
- Set up a video meeting platform properly for teaching rather than chatting
- Share your screen usefully, including what not to show
- Build presentations that support teaching rather than replace it
- Use a digital whiteboard to explain rather than decorate
- Record lessons correctly and decide what to publish
- Handle technical failure without losing the class
The taught content
Choosing and setting up the platform
The platform matters less than people think, but the settings matter a great deal. Zoom, Google Meet and Microsoft Teams all handle teaching; the differences are in free-tier limits, participant numbers and recording. For a Nigerian context the practical considerations are data consumption — video-heavy meetings are expensive for students on mobile data — low-bandwidth behaviour, and whether students can join from a phone without installing anything.
Then the settings that make it a classroom rather than a call. Mute on entry, because late arrivals with unmuted microphones destroy lessons. Waiting room or locked meeting, because an open link gets joined by strangers and occasionally disrupted deliberately. Chat enabled, because it is how quiet students ask questions they will not ask aloud, and it is often where the real confusion surfaces. Screen share restricted to host by default, opened deliberately when a student needs to show their work.
Send the link with the time in a specific zone and the topic named, and send a reminder. This sounds trivial and it determines attendance: a message that says 'class at 6' produces half the attendance of one that says 'Excel formulas, Tuesday 6pm WAT, same link as last week'. Ambiguity is the enemy of attendance, and attendance is the precondition for everything else.
Screen sharing
Screen sharing is the core teaching tool online, and most people use it badly. Share one window rather than your whole screen where the platform allows it — it keeps the class focused on the relevant thing, it prevents notifications appearing publicly, and it stops you accidentally revealing an inbox, a bank balance or a private message.
Then prepare the screen before the class. Close irrelevant tabs, turn off notifications entirely rather than relying on do-not-disturb, increase the text size so it is readable on a phone, and have the files you need already open. Most sharing problems are not technical — they are the forty seconds spent hunting for a file while twenty people watch, and the private information glimpsed while looking for it.
Share audio deliberately if the lesson needs it, and check what students actually see. Ask someone to confirm the text is readable, because what is clear on your laptop is often tiny on a phone, and most of your students are on phones. If you are demonstrating software, slow down: screen sharing has latency, and a click that seems instant to you arrives a second later for them.
Presentations that teach
A teaching presentation is not a document. The failure mode is a slide full of sentences that the teacher reads aloud, which is worse than no slide at all — the class reads faster than you speak, so they are either reading ahead and not listening, or listening and missing the slide. Never put on a slide what you intend to say.
The rule that fixes it: one idea per slide, expressed visually or in a few words, with the explanation spoken. A diagram, a screenshot with one thing circled, a short phrase, a large number. The slide carries the anchor and your voice carries the meaning. If a slide works without you speaking, it is a document rather than a teaching aid, and it should be sent as a handout instead.
Then the practical details. Large text — readable on a phone, which means far larger than feels necessary. High contrast, because low contrast disappears on a cheap screen in bright light. Build slides progressively rather than showing everything at once, so attention goes where you are talking. And number your slides, because 'go back to the one about the formula' is impossible otherwise and it will be asked.
Digital whiteboards
A whiteboard is for thinking out loud in front of the class, which is something a prepared slide cannot do. Its value is that it appears gradually, in response to what the class needs, and it can be changed when someone is confused. A diagram built live while you explain it teaches far better than the same diagram shown complete, because the class follows the reasoning rather than receiving the conclusion.
Keep it simple. Boxes, arrows, labels and a highlighter are enough for almost any explanation. Elaborate drawings waste time and add nothing, and the class is watching you struggle with the pen tool rather than thinking about the concept. Write large, because handwriting on a shared screen is much harder to read than typed text, and write less than you would in person, because small handwriting on a phone screen is illegible.
The whiteboard also solves a specific online problem: it gives you somewhere to put a student's question. When someone asks something, writing it on the board makes it shared rather than private, which means the other four people who had the same question get it answered too. That single habit is one of the largest differences between a good online class and a lecture with a chat box.
Recording, and when things fail
Recording lets absent students catch up and lets present ones revisit difficult parts, which is a genuine advantage of teaching online. But three things must be handled. Tell people you are recording, because consent matters and in some contexts it is a legal requirement under Nigeria's data protection framework. Check the recording actually saved — a lesson discovered missing a week later is unrecoverable. And consider what the recording contains, because anything on your screen during it is now permanent: notifications, names, marks, private messages.
Then the failures, which are certain rather than possible. Your connection drops. Have a backup: mobile data ready as a hotspot, and a message pre-written to send by WhatsApp telling the class what to do. The platform fails. Know a second one well enough to move the class in two minutes. A student cannot hear you. Ask the class to confirm audio at the start rather than discovering it twenty minutes in, which is when it is usually found.
The principle is that the lesson must survive the technology. Have the materials downloadable rather than only on your screen, have an asynchronous fallback — a screen recording and a written summary sent to the group — and do not spend the class apologising. A calm 'we have lost the connection, I will send the recording and we will pick up on Tuesday' is professional; ten minutes of 'can you hear me now?' is not, and the class remembers which one you did.
Instructor demonstration
The instructor sets up a real classroom session: platform settings for teaching, a screen prepared and shared as a single window, a slide rebuilt from a paragraph into a visual anchor, a diagram built live on a whiteboard, a recording started and verified, then a simulated connection failure handled with a pre-written fallback.
- 01
Compare the platforms
Set out free-tier limits, data consumption and phone-only joining. Explain that for most Nigerian classes, data cost and mobile access decide the choice.
- 02
Set the classroom settings
Enable mute on entry, a waiting room or locked meeting, chat, and host-only screen share. Explain that an open link gets joined by strangers.
- 03
Write the invitation properly
Name the topic, state the time with the zone, include the link and send a reminder. Explain that ambiguity is the main cause of poor attendance.
- 04
Prepare the screen
Close tabs, disable notifications entirely, increase text size, open the files in advance. Explain that most sharing problems are hunting for files, not technical faults.
- 05
Share one window, not the screen
Demonstrate the difference and explain that whole-screen sharing exposes notifications, inboxes and private information.
- 06
Verify what students see
Ask a participant to confirm the text is readable on a phone. Explain that most students are on phones and what is clear on a laptop is tiny there.
- 07
Rebuild a slide
Take a paragraph-filled slide and reduce it to one idea with a visual anchor. Explain that if a slide works without you speaking it is a handout.
- 08
Set the slide basics
Enlarge text, raise contrast, build progressively and number the slides. Explain that 'go back to the one about the formula' is impossible without numbers.
- 09
Build a diagram live
Draw boxes, arrows and labels while explaining. Explain that a diagram built live teaches the reasoning while a complete one delivers only the conclusion.
- 10
Put a question on the board
Take a student's question and write it up. Explain that this makes it shared, so the others who had the same question get it answered too.
- 11
Start and verify the recording
Begin recording, announce it to the class, and confirm afterwards that the file saved. Explain that a missing recording discovered a week later is unrecoverable.
- 12
Simulate a failure
Drop the connection and run the fallback: hotspot, pre-written WhatsApp message, downloadable materials. Explain that the lesson must survive the technology.
- 13
Check audio at the start
Ask the class to confirm they can hear before teaching anything. Explain that audio problems are usually discovered twenty minutes in, when the time is already lost.
Guided practice
Run a real online classroom session
You set up and run a short live session: platform configured for teaching, screen prepared and shared as a single window, one slide rebuilt from a paragraph into a visual anchor, a diagram built live on a whiteboard, a recording started, announced and verified — plus a written fallback plan for connection failure that you actually test.
- 01Choose a platform based on data cost and whether students can join from a phone.
- 02Enable mute on entry, a waiting room or locked meeting, chat, and host-only sharing.
- 03Write the invitation with the topic named, the time with its zone, and the link.
- 04Send a reminder before the session.
- 05Close irrelevant tabs and disable notifications entirely before starting.
- 06Increase the text size so it is readable on a phone and open all files in advance.
- 07Share one window rather than your whole screen.
- 08Ask a participant to confirm the text is readable on their device.
- 09Rebuild one paragraph-filled slide into a single idea with a visual anchor.
- 10Enlarge the text, raise the contrast, and number every slide.
- 11Build a diagram live on a whiteboard using boxes, arrows and labels only.
- 12Write a student's question on the board so the whole class sees it answered.
- 13Announce that you are recording, then start the recording.
- 14Confirm audio with the class before teaching any content.
- 15Verify after the session that the recording saved and is playable.
- 16Write a fallback plan: hotspot ready, pre-written message, downloadable materials, second platform.
- 17Test the fallback by actually disconnecting once.
The standard we hold you to
A live session run on a platform chosen for data cost and phone access, configured with mute on entry, a locked meeting or waiting room, chat and host-only sharing, invited with topic, zoned time and link plus a reminder, with tabs closed, notifications disabled, text enlarged and files pre-opened, one window shared and its legibility confirmed by a participant, one slide rebuilt into a single visual anchor with all slides numbered, a diagram built live from boxes, arrows and labels, a student question written on the board, the recording announced and started and later verified as saved and playable, audio confirmed before content, and a fallback plan written and actually tested by disconnecting.
Common mistakes and how to fix them
You left the meeting open with default settings
Fix: Enable mute on entry and a waiting room or locked meeting. An open link gets joined by strangers and occasionally disrupted deliberately, which ends the lesson for everyone.
You share your whole screen
Fix: Share one window. Whole-screen sharing exposes notifications, inboxes, balances and private messages to the whole class, and that cannot be undone.
You hunt for files while the class watches
Fix: Open everything in advance and disable notifications entirely. Most screen-sharing problems are not technical faults but forty seconds of searching while twenty people wait.
You never check what students actually see
Fix: Ask a participant to confirm the text is readable on their phone. Most students are on phones, and what is clear on your laptop is tiny on a small screen in bright light.
Your slides are paragraphs you read aloud
Fix: One idea per slide, expressed visually, with the explanation spoken. If a slide works without you speaking it is a handout and should be sent as one.
You show complete diagrams instead of building them
Fix: Draw live on a whiteboard. A diagram that appears as you explain teaches the reasoning; the same diagram shown complete delivers only the conclusion.
You recorded without telling anyone, or never checked it saved
Fix: Announce the recording and verify the file afterwards. Consent matters and may be legally required, and a missing recording discovered a week later is unrecoverable.
You have no plan for a connection failure
Fix: Prepare a hotspot, a pre-written message, downloadable materials and a second platform. The lesson must survive the technology, and ten minutes of 'can you hear me now?' is not a plan.
Expert notes
The habits that separate someone who can do this from someone who does it well.
- Choose your platform on data cost and phone access rather than features. Most Nigerian students are on mobile data and a phone, and a technically superior platform that costs them too much to join will have an empty classroom.
- Share one window, never your whole screen. It keeps attention on the relevant thing and it prevents the notifications, messages and balances that cannot be unseen once shared.
- Never put on a slide what you intend to say. One visual anchor per slide with the meaning carried by your voice, because a class that reads ahead of you is a class that is not listening to you.
- Test your fallback before you need it. Connection failures are certain rather than possible, and a plan you have actually rehearsed keeps the class calm while an unrehearsed one turns a two-minute problem into a lost lesson.
Key terms
- Mute on entry
- Arrivals joining muted. Prevents late-arrival noise from destroying the lesson.
- Waiting room
- A holding area before admission. Stops strangers joining an open link.
- Window sharing
- Sharing one application rather than the whole screen. Focuses attention and protects private information.
- Visual anchor
- The one image or phrase on a slide that the spoken explanation attaches to. Not a paragraph.
- Digital whiteboard
- A surface for thinking out loud. Its value is that it appears gradually and can change when someone is confused.
- Latency
- Delay between your action and the student seeing it. Why demonstrations must be slower online than in person.
- Asynchronous fallback
- A recording plus written summary for when the live session fails. What makes the lesson survive the technology.
- Recording consent
- Telling the class you are recording. An ethical obligation and in some contexts a legal one.
Homework before the next session
Configure your platform for teaching
Mute on entry, waiting room or locked meeting, chat enabled, host-only screen sharing. Then write the invitation properly: topic named, time with its zone, link included.
Rebuild three slides
Take three paragraph-filled slides and reduce each to one idea with a visual anchor. Enlarge the text, raise the contrast, and number them.
Run a fifteen-minute test session
Share one window, confirm legibility with a real participant on a phone, build one diagram live on a whiteboard, and record it. Verify afterwards that the file saved.
Write and test your fallback plan
Hotspot ready, pre-written message to the group, materials downloadable, second platform known. Then actually disconnect once and run it.
Assessment rubric
How this session is marked. The certificate for Online Teaching is awarded on the deliverable, not on attendance.
| Criterion | Passing | Excellent |
|---|---|---|
| Platform setup | Can start a meeting. | Chosen for data cost and phone access, with mute on entry, a locked meeting or waiting room, chat, host-only sharing, and a properly written invitation with a reminder. |
| Screen sharing | Shares the screen. | One window rather than the whole screen, tabs closed, notifications disabled, text enlarged, files pre-opened, and legibility confirmed by a participant on a phone. |
| Presentations | Has slides. | One visual anchor per slide with nothing written that will be spoken, large high-contrast text, progressive build, and every slide numbered. |
| Whiteboard use | Can draw on it. | Diagrams built live from boxes, arrows and labels to show reasoning, written large, with student questions written up so the whole class benefits. |
| Recording and resilience | Records sometimes. | Recording announced and verified as saved, audio confirmed before content, and a fallback plan written and actually tested by disconnecting. |
Session questions
Which platform should I use?+
Whichever your students can join cheaply from a phone. Zoom, Google Meet and Teams all teach fine; the deciding factors in Nigeria are data consumption, free-tier limits and whether joining needs an app installed. A superior platform with an empty classroom is not superior.
Should I record my lessons?+
Yes — absent students catch up and present ones revisit difficult parts. But announce that you are recording, verify afterwards that the file actually saved, and think about what your screen contained, because notifications and private information become permanent in a recording.
My students cannot see my screen clearly. What is wrong?+
Probably text size rather than connection. Most students are on phones, and what is readable on a laptop is tiny on a small screen in bright light. Increase the text size, raise the contrast, and ask a participant to confirm what they actually see.
How do I stop people joining and disrupting my class?+
Use a waiting room or lock the meeting once the class has arrived, and never post the link publicly. Also restrict screen sharing to the host by default, since an unexpected sharer is the most common form of disruption in an open meeting.
What do I do when my connection drops mid-lesson?+
Execute the plan you prepared: switch to a mobile hotspot, send the pre-written message to the group telling them what to do, and fall back to a recording plus written summary. Do not spend the class apologising — a calm fallback is professional and the class remembers which one you did.
This session is part of
Online Teaching
3 weeks · 6 sessions · ₦30,000 · you leave with a complete lesson plus a delivered class