How Many Slides Per Training Hour? Density Rules for Generated Decks
Asking how many slides per training hour you need sounds like a formatting question and is really a cognitive load question. Generated decks in particular tend to run long, because generation reflects the structure of the source document rather than the rhythm of a delivered session, and a 40-page policy produces 60 slides that nobody can sit through. Knowing the target density before you generate, and what to cut afterwards, is what turns raw output from an AI slide generator into something deliverable. Key Takeaways 🖥️ Sign In to Access Your Dashboard The Baseline Numbers There is no universal figure, but the ranges are consistent enough to plan against. Format Slides per hour Time per slide Instructor-led, discussion-heavy 12 to 15 4 to 5 minutes Instructor-led, standard 15 to 20 3 to 4 minutes Instructor-led, technical walkthrough 20 to 25 2 to 3 minutes Self-paced with narration 25 to 30 2 minutes Self-paced, reference-heavy 30 to 40 1 to 2 minutes The instructor-led numbers surprise people who have sat through 60-slide corporate sessions. Those sessions overran, or the instructor skipped slides, which is the same problem expressed differently. Self-paced runs denser because learners control pace and can re-watch. Density is not a virtue there either, but the ceiling is higher. Why Generated Decks Run Long Generation follows the structure of what you feed it. A policy document has sections, subsections, and definitions, and each of these looks like a slide boundary to a generator. Delivered sessions do not work that way. A session has beats: an opening, three or four substantive moves, a practice element, and a close. Ten source sections might map to four session beats, and the generator has no way to know that. Three patterns produce the overshoot: Definitional slides: Source documents define terms formally. Sessions introduce terms in passing while doing something with them. Definition slides are the single largest category of cuttable content. Section headers as slides: Useful in a document, dead air in a session. Exhaustive enumeration: A policy listing twelve categories becomes twelve bullet points or three slides. A session needs the two categories that matter and a reference handout for the rest. Cutting Down to Deliverable Length Work in this order. Cut every standalone definition slide: Fold the definition into the slide where the term is first used. Merge section headers into the following slide: The heading becomes the title. Collapse enumerations: Show the two or three items that matter, and move the full list to a handout. Learners will not retain twelve items from a slide regardless. Convert content slides to prompts: Where the instructor will talk through a point, the slide needs an anchor, not the full argument. This alone typically removes 20% of a generated deck. Move reference material out: Tables, thresholds, and specifications belong in a document learners can search, not in a deck they watch once. The same logic applies to audio, as covered in what changes when learners listen instead of read. 📄 Generate a Free PDF Sample Course in Your Cloned Voice One Idea Per Slide The rule is simple and almost universally violated. When a slide carries two ideas, the second gets less attention or none, because the audience is still processing the first when the instructor moves on. This is a straightforward consequence of working memory limits, described in cognitive load theory. Practical tests. If your slide title contains “and”, it probably carries two ideas. If a slide has more than five bullets, it carries several and If you cannot state the slide’s single point in one sentence, it has not got one. Splitting a dense slide into two raises the slide count and lowers the cognitive load, which is a good trade even though it moves the density number in the wrong direction. The count is a planning heuristic, not a target to optimise. Vary Density Within a Session Constant pacing produces attention decay regardless of the count. A workable rhythm alternates. Several quick slides establishing context, then one substantial slide the group stays on for eight minutes, then a practice element with no slide at all, then quick slides again. The slides that anchor discussion are the ones worth designing carefully. Most of the rest are signposts. Treating every slide as equally important is why decks feel flat, and it is also why they take three times longer to build than they need to. Plan the beats first and generate against them, rather than generating from the document and hoping the rhythm emerges. Where the Effort Moves To be clear about scope: no generator knows your session rhythm, because that depends on your audience, your instructor, and how much discussion you want. The cutting decisions are yours. What generation changes is where the effort goes. Producing a first-pass deck from source material takes minutes rather than a day, so the instructor’s time moves from building slides to deciding which ones survive. That is the higher-value use of it, and the version that reaches learners is better for it. For a provider building decks across 20 courses Metric Before After Time to first-draft deck 6 hours 20 minutes Instructor time on slide editing 6 hours 90 minutes Average deck length, 2-hour session 58 slides 34 slides Sessions overrunning Frequent Rare Cutting a Generated Deck Down Frequently Asked Questions If your last generated deck felt bloated, the cause was the source document’s structure rather than the generator. Plan the session beats first. 👉 Book a Live Platform Demo with an EdTech Expert
Bilingual Training Decks: Arabic RTL Layout Problems and How to Solve Them
Building an Arabic training presentation exposes problems that never appear in English decks, and most of them are not translation problems. Flipping text direction changes reading order, which changes where the eye lands, which breaks layouts that were designed around a left-to-right scan. Add English technical terms inside Arabic sentences and numbers that stay left-to-right regardless, and you get decks that are technically correct and visibly wrong. Whether slides come from an AI Course Builder or PowerPoint, the fixes are the same. What Actually Breaks 🖥️ Sign In to Access Your Dashboard Reading Order Changes Where Emphasis Lands In a left-to-right deck the eye starts top-left. Designers put the most important element there without thinking about it. In an Arabic deck the eye starts top-right. A layout with the headline top-left and supporting detail on the right now leads with the detail. The slide is not mistranslated; it is misdirected, and the effect compounds across a fifty-slide deck. The fix is mirroring the layout rather than only the text. Titles move right, bullet indentation reverses, image and text columns swap, and navigation elements follow. Most presentation software handles paragraph direction automatically and does not handle any of this, which is why decks that pass a text check still look wrong. Bidirectional Text Is the Hard Part Arabic runs right to left. Numbers run left to right. Latin-script terms run left to right. Real training content mixes all three constantly. A sentence containing an Arabic explanation, an English product name, and a figure has three direction changes in one line. This is bidirectional text, and rendering it correctly is genuinely difficult. What breaks in practice: Two mitigations. Keep Latin-script terms to a minimum in Arabic content, substituting Arabic equivalents where they exist and the audience accepts them. And check every slide containing a mixed-direction line visually, because automated checks will not catch these. Charts and Diagrams Must Be Mirrored Text direction is the visible half of the problem. Visual flow is the half people miss. Process diagrams: A left-to-right flow reads backwards in an Arabic deck. Mirror the sequence and reverse the arrows. Bar charts with time on the x-axis: Time should progress right to left, matching reading direction. Left unchanged, the chart implies the trend runs the wrong way. Numbered lists: Numbers sit to the right of the text. Icons implying direction: Arrows, progress indicators, and “next” affordances all need reversing. Element English deck Arabic deck Title position Left Right Bullet indentation Left Right Process flow Left to right Right to left Time axis Left to right Right to left List numbering Left of text Right of text Directional icons Point right Point left Numerals Left to right Left to right, unchanged Note the last row. Numerals do not mirror. Attempting to reverse them is a common and confusing error. Typography Differences That Matter Arabic script has different metrics from Latin script, and applying English typographic settings produces cramped, hard-to-read slides. Line height: Arabic needs more, because letters extend above and below the baseline more than Latin characters. Increase leading by roughly 20% over your English setting. Font size: Arabic at the same point size reads smaller. Increase by one to two points for equivalent legibility. Text length: Translated Arabic typically runs 20 to 25% shorter than English. Text boxes sized to English content will look empty, so layouts need adjusting rather than reusing. Font choice: Not every font has usable Arabic coverage. Test with your actual content, since fonts that render headings acceptably often fail on diacritics or extended characters. 📄 Generate a Free PDF Sample Course in Your Cloned Voice Bilingual Decks: Parallel, Not Combined Providers often ask for one deck carrying both languages. It rarely works. Two languages on one slide halves the space available to each, produces competing reading directions on a single surface, and doubles the cognitive load for learners who only need one. The result serves neither audience well. Parallel versions work better. One source, two outputs, generated together so they cannot drift. Learners get a deck in their language, and the deck is designed for that language rather than compromised between two. The exception is a glossary or terminology slide, where side-by-side presentation is the point. Keep those bilingual and make everything else parallel. The same variant logic applies here as in reusable course architecture. Keeping Both Language Versions Aligned To be clear about scope: generated slides follow templates, so RTL correctness depends on the template being built for it. A template designed for English and switched to Arabic will carry the layout problems described above. What generation changes is that both language versions come from one source. When content updates, both regenerate rather than one being edited and the other quietly falling behind, which is the usual fate of manually maintained bilingual decks. For a provider delivering bilingual programmes across 15 courses Metric Before After Arabic decks available 4 of 15 15 of 15 Time to produce an Arabic deck 1 week Same day Versions drifting after content update Routine None Slides requiring manual RTL correction Every one Mixed-direction only Fixing an RTL Deck in Seven Steps Frequently Asked Questions If your Arabic decks were made by switching text direction on an English template, the layout problems are still there. Rebuild the template rather than fixing slides individually. 👉 Book a Live Platform Demo with an EdTech Expert