![\"Five](\"https:\/\/www.mlcpresentations.com\/wp-content\/uploads\/2026\/08\/BLOG-5S-Lean-Presentation-Design_Cover-5S-Workflow.webp\")
<\/span>Key Takeaways<\/span><\/h2>\n\n\n\n\u2022 Seiri selects:<\/strong> it removes material that does not support the audience’s decision, without rearranging or redesigning what remains.<\/p>\n\n\n\n\u2022 Seiton orders:<\/strong> it gives every selected element a precise position and creates a reading path, without deleting content.<\/p>\n\n\n\n\u2022 Seiso inspects:<\/strong> it exposes and corrects visual defects while keeping the message, data and sequence unchanged.<\/p>\n\n\n\n\u2022 Seiketsu standardizes:<\/strong> it turns a successful solution into a reusable template system, such as a family of linked section dividers.<\/p>\n\n\n\n\u2022 Shitsuke sustains:<\/strong> it makes compliance with an existing standard a recurring habit through ownership, reviews and short retrospectives.<\/p>\n\n\n\n<\/span>The 5S are not five generic design tips<\/span><\/h2>\n\n\n\nThe original 5S method<\/a> organizes a workplace, makes problems visible and prevents good practices from disappearing over time. A presentation is also a workplace\u2014only the person working in it is your audience. While you speak, people must find the message, connect it to the evidence and understand what to do next.<\/p>\n\n\n\nThis is why the 5S do not replace the broader Lean Presentation Design methodology<\/a>, nor do they compete with general presentation design principles<\/a>. They provide a specific operating sequence for transforming a deck and preserving the result.<\/p>\n\n\n\n<\/span>Five questions keep the principles separate<\/span><\/h3>\n\n\n\n- Seiri:<\/strong> What deserves to remain in the main flow?<\/li>
- Seiton:<\/strong> Where should each selected element go?<\/li>
- Seiso:<\/strong> Which errors must I identify and correct in what remains?<\/li>
- Seiketsu:<\/strong> Which rules should I encode so that the solution can be reused?<\/li>
- Shitsuke:<\/strong> How will I verify that the existing standard is respected over time?<\/li><\/ul>\n\n\n\n
That distinction matters. If one example could illustrate two or three principles equally well, it is probably too vague. In the examples below, each transformation changes one lever only.<\/p>\n\n\n\n
<\/span>1. Seiri \u2014 Sort: remove what does not serve the decision<\/span><\/h2>\n\n\n\nSeiri is selection. Every slide, chart and sentence must earn the right to stay by helping the audience understand the message or make the required decision. Material that fails the test does not always need to be deleted forever. It may belong in the speaker notes, a pre-read or an appendix.<\/p>\n\n\n\n
Imagine an HR team asking an executive committee to approve a three-month onboarding pilot. The working deck contains a central chart that compares the pilot options, but it is surrounded by old screenshots, secondary benchmarks, repeated quotations and exploratory charts. In the Seiri transformation, the central chart does not move and is not redesigned. The team removes only the fragments that do not contribute to the approval decision.<\/p>\n\n\n\n![\"Seiri](\"https:\/\/www.mlcpresentations.com\/wp-content\/uploads\/2026\/08\/BLOG-5S-Lean-Presentation-Design_01-Seiri.webp\")
Seiri in practice:<\/strong> the core slide stays the same; only nonessential content disappears.<\/figcaption><\/figure>\n\n\n\n<\/span>How to apply Seiri<\/span><\/h3>\n\n\n\n- Write the decision or desired change in one sentence.<\/li>
- Inventory every slide, chart, paragraph and appendix without editing them.<\/li>
- Mark each item as essential, support on request or unnecessary.<\/li>
- Keep only the evidence required to reach the decision in the main flow.<\/li><\/ol>\n\n\n\n
The Seiri boundary:<\/strong> only the quantity of content changes. The core chart, takeaway and layout remain untouched. If you start moving objects or fixing the palette, you have already moved into another S.<\/p>\n\n\n\nThis principle is consistent with the MIT Communication Lab’s advice to determine the message of each slide and remove elements that distract from the takeaway. The practical difference here is procedural: Seiri is the explicit gate that decides what stays in the workflow.<\/p>\n\n\n\n
<\/span>2. Seiton \u2014 Set in order: give every selected element a place<\/span><\/h2>\n\n\n\nAfter Seiri has reduced the material, Seiton arranges what remains. It works at two levels: the sequence of the deck and the hierarchy inside each slide. Your audience should not have to reconstruct the argument or search for a label far away from the data it explains.<\/p>\n\n\n\n
In this example, six presentation slides are already approved: context, problem, evidence, solution, implementation and decision. Before Seiton, all six are present but connected by crossing lines and unclear jumps. After Seiton, the same six slides form one unambiguous path. Nothing is removed, and no slide is visually redesigned.<\/p>\n\n\n\n![\"Seiton](\"https:\/\/www.mlcpresentations.com\/wp-content\/uploads\/2026\/08\/BLOG-5S-Lean-Presentation-Design_02-Seiton-Create-a-Clear-Path-v2.webp\")
Seiton in practice:<\/strong> six elements before, the same six after; only position, sequence and reading path change.<\/figcaption><\/figure>\n\n\n\n<\/span>How to apply Seiton<\/span><\/h3>\n\n\n\n- Order the deck as a logic chain: context, problem, evidence, solution and decision.<\/li>
- Turn topic labels into sentence titles that state the message.<\/li>
- Place the takeaway first, the proof second and supporting detail last.<\/li>
- Group related objects and label data directly whenever possible.<\/li><\/ol>\n\n\n\n
The Seiton boundary:<\/strong> the inventory is fixed. You are not deciding whether an element deserves to stay; that decision belongs to Seiri. You are deciding where an already selected element must live so that the audience can follow it.<\/p>\n\n\n\nResearch on the assertion-evidence approach<\/a> is relevant here: a sentence headline and visual evidence make the message easier to follow than a generic topic heading followed by a list. Seiton converts that idea into a repeatable ordering discipline.<\/p>\n\n\n\n<\/span>3. Seiso \u2014 Shine: find and fix defects<\/span><\/h2>\n\n\n\nSeiri has already decided what must remain. Seiso does not remove any more content: it inspects what remains and corrects errors that compromise accuracy, legibility or consistency. In a factory, cleaning reveals leaks, cracks and anomalies; in a presentation, the equivalent is making defects visible\u2014an incorrect value or label, an object out of alignment, insufficient contrast or an overlap.<\/p>\n\n\n\n
The Seiso example uses the same analytical chart with the same two data series before and after. The inspection identifies three specific defects: an incorrect starting point, one misaligned marker and an incomplete legend. The corrected version fixes only those errors; message, data inventory and sequence remain unchanged.<\/p>\n\n\n\n![\"Seiso](\"https:\/\/www.mlcpresentations.com\/wp-content\/uploads\/2026\/08\/BLOG-5S-Lean-Presentation-Design_03-Seiso-Find-and-Fix-Defects-v2.webp\")
Seiso in practice:<\/strong> the same chart, with the same elements, moves from inspection to the correction of three defects.<\/figcaption><\/figure>\n\n\n\n<\/span>How to apply Seiso<\/span><\/h3>\n\n\n\n- Compare numbers, labels, units and sources with the original data.<\/li>
- Inspect alignment, spacing, overlaps and consistency between the legend and the chart.<\/li>
- Verify contrast and legibility at the real viewing distance, including in grayscale.<\/li>
- Correct one defect at a time without changing the message, the data or the quantity of content.<\/li><\/ol>\n\n\n\n
The Seiso boundary:<\/strong> Seiri decides what stays; Seiso checks whether what stays is correct. Here, no element is removed and the story is not reordered. Content and message remain unchanged while only defects in accuracy, alignment and legibility are corrected.<\/p>\n\n\n\nThe empirical study Declutter and Focus<\/em><\/a> is a useful reminder that decluttering and directing attention are not cosmetic preferences. They can affect how efficiently readers interpret a visualization.<\/p>\n\n\n\n<\/span>4. Seiketsu \u2014 Standardize: turn one good solution into a system<\/span><\/h2>\n\n\n\nSeiketsu captures what works and turns it into a reusable system. In presentations, the system may include slide masters, layouts, placeholders, grids, typography, chart rules, units, sources and accessibility requirements. The aim is to make the correct choice easy to repeat and the incorrect choice harder to introduce.<\/p>\n\n\n\n
The example is a family of five section dividers. Every slide contains the same five geometric objects\u2014a circle, square, triangle, diamond and pentagon\u2014in the same positions, with identical margins, typography and palette. The template changes one controlled variable: on each divider, a different object lights up in yellow to show the active section. You are not arranging five existing messages. You are defining the matrix that will generate future slides.<\/p>\n\n\n\n![\"Seiketsu](\"https:\/\/www.mlcpresentations.com\/wp-content\/uploads\/2026\/08\/BLOG-5S-Lean-Presentation-Design_04-Seiketsu.webp\")
Seiketsu in practice:<\/strong> one template produces a coherent family of dividers by changing only the active object.<\/figcaption><\/figure>\n\n\n\n<\/span>How to apply Seiketsu<\/span><\/h3>\n\n\n\n- Define four or five recurring slide intents: opening, message with evidence, comparison, process and decision.<\/li>
- Set a type hierarchy, grid, spacing rules and one controlled accent color.<\/li>
- Standardize charts, dates, units, sources and naming conventions.<\/li>
- Build the rules into layouts, placeholders and guides instead of leaving them in a forgotten PDF.<\/li><\/ol>\n\n\n\n
The Seiketsu boundary:<\/strong> this is not Seiton at scale. Seiton finds the best place for selected content in one deck. Seiketsu encodes the rule that governs a class of future slides. The distinction is the difference between arranging five slides and designing the mold that will produce fifty consistent slides.<\/p>\n\n\n\nPowerPoint supports this logic through its Slide Master and associated layouts<\/a>. For the organizational dimension, see MLC’s approach to the corporate PowerPoint template as an efficiency engine<\/a>.<\/p>\n\n\n\n<\/span>5. Shitsuke \u2014 Sustain: make the standard a habit<\/span><\/h2>\n\n\n\nShitsuke is the discipline that keeps the system working when deadlines, copied slides and local exceptions start to pull it apart. It does not design the standard\u2014that is Seiketsu\u2014and it does not continually redesign it. It makes sure that an approved standard is used, checked and learned from.<\/p>\n\n\n\n
In the example, the template already exists on both sides. The team produces six recurring monthly decks. Without a routine, small exceptions accumulate: an outdated cover, a missing source, a chart copied from the wrong master. With Shitsuke, every delivery passes the same lightweight preflight, has a named owner and ends with a ten-minute reflection. The change is not the template; it is the cadence of verification.<\/p>\n\n\n\n![\"Shitsuke](\"https:\/\/www.mlcpresentations.com\/wp-content\/uploads\/2026\/08\/BLOG-5S-Lean-Presentation-Design_05-Shitsuke.webp\")
Shitsuke in practice:<\/strong> the standard already exists; recurring review prevents drift across successive deliveries.<\/figcaption><\/figure>\n\n\n\n<\/span>How to apply Shitsuke<\/span><\/h3>\n\n\n\n- Assign an owner to the presentation system, not only to this month’s file.<\/li>
- Run a short preflight before each delivery and a deeper review on recurring decks.<\/li>
- Maintain one trusted master and clearly label local or experimental slides.<\/li>
- After presenting, spend ten minutes on hansei<\/em>: what worked, what failed and what should change next time.<\/li><\/ol>\n\n\n\n
The Shitsuke boundary:<\/strong> the template is already designed. If you are still choosing the grid or inventing the divider system, you are doing Seiketsu. Shitsuke begins when the question becomes: \u201cDid we use the agreed system again, and did we check it?\u201d<\/p>\n\n\n\n
\u2022 Seiton orders:<\/strong> it gives every selected element a precise position and creates a reading path, without deleting content.<\/p>\n\n\n\n \u2022 Seiso inspects:<\/strong> it exposes and corrects visual defects while keeping the message, data and sequence unchanged.<\/p>\n\n\n\n \u2022 Seiketsu standardizes:<\/strong> it turns a successful solution into a reusable template system, such as a family of linked section dividers.<\/p>\n\n\n\n \u2022 Shitsuke sustains:<\/strong> it makes compliance with an existing standard a recurring habit through ownership, reviews and short retrospectives.<\/p>\n\n\n\n The original 5S method<\/a> organizes a workplace, makes problems visible and prevents good practices from disappearing over time. A presentation is also a workplace\u2014only the person working in it is your audience. While you speak, people must find the message, connect it to the evidence and understand what to do next.<\/p>\n\n\n\n This is why the 5S do not replace the broader Lean Presentation Design methodology<\/a>, nor do they compete with general presentation design principles<\/a>. They provide a specific operating sequence for transforming a deck and preserving the result.<\/p>\n\n\n\n That distinction matters. If one example could illustrate two or three principles equally well, it is probably too vague. In the examples below, each transformation changes one lever only.<\/p>\n\n\n\n Seiri is selection. Every slide, chart and sentence must earn the right to stay by helping the audience understand the message or make the required decision. Material that fails the test does not always need to be deleted forever. It may belong in the speaker notes, a pre-read or an appendix.<\/p>\n\n\n\n Imagine an HR team asking an executive committee to approve a three-month onboarding pilot. The working deck contains a central chart that compares the pilot options, but it is surrounded by old screenshots, secondary benchmarks, repeated quotations and exploratory charts. In the Seiri transformation, the central chart does not move and is not redesigned. The team removes only the fragments that do not contribute to the approval decision.<\/p>\n\n\n\n The Seiri boundary:<\/strong> only the quantity of content changes. The core chart, takeaway and layout remain untouched. If you start moving objects or fixing the palette, you have already moved into another S.<\/p>\n\n\n\n This principle is consistent with the MIT Communication Lab’s advice to determine the message of each slide and remove elements that distract from the takeaway. The practical difference here is procedural: Seiri is the explicit gate that decides what stays in the workflow.<\/p>\n\n\n\n After Seiri has reduced the material, Seiton arranges what remains. It works at two levels: the sequence of the deck and the hierarchy inside each slide. Your audience should not have to reconstruct the argument or search for a label far away from the data it explains.<\/p>\n\n\n\n In this example, six presentation slides are already approved: context, problem, evidence, solution, implementation and decision. Before Seiton, all six are present but connected by crossing lines and unclear jumps. After Seiton, the same six slides form one unambiguous path. Nothing is removed, and no slide is visually redesigned.<\/p>\n\n\n\n The Seiton boundary:<\/strong> the inventory is fixed. You are not deciding whether an element deserves to stay; that decision belongs to Seiri. You are deciding where an already selected element must live so that the audience can follow it.<\/p>\n\n\n\n Research on the assertion-evidence approach<\/a> is relevant here: a sentence headline and visual evidence make the message easier to follow than a generic topic heading followed by a list. Seiton converts that idea into a repeatable ordering discipline.<\/p>\n\n\n\n Seiri has already decided what must remain. Seiso does not remove any more content: it inspects what remains and corrects errors that compromise accuracy, legibility or consistency. In a factory, cleaning reveals leaks, cracks and anomalies; in a presentation, the equivalent is making defects visible\u2014an incorrect value or label, an object out of alignment, insufficient contrast or an overlap.<\/p>\n\n\n\n The Seiso example uses the same analytical chart with the same two data series before and after. The inspection identifies three specific defects: an incorrect starting point, one misaligned marker and an incomplete legend. The corrected version fixes only those errors; message, data inventory and sequence remain unchanged.<\/p>\n\n\n\n The Seiso boundary:<\/strong> Seiri decides what stays; Seiso checks whether what stays is correct. Here, no element is removed and the story is not reordered. Content and message remain unchanged while only defects in accuracy, alignment and legibility are corrected.<\/p>\n\n\n\n The empirical study Declutter and Focus<\/em><\/a> is a useful reminder that decluttering and directing attention are not cosmetic preferences. They can affect how efficiently readers interpret a visualization.<\/p>\n\n\n\n Seiketsu captures what works and turns it into a reusable system. In presentations, the system may include slide masters, layouts, placeholders, grids, typography, chart rules, units, sources and accessibility requirements. The aim is to make the correct choice easy to repeat and the incorrect choice harder to introduce.<\/p>\n\n\n\n The example is a family of five section dividers. Every slide contains the same five geometric objects\u2014a circle, square, triangle, diamond and pentagon\u2014in the same positions, with identical margins, typography and palette. The template changes one controlled variable: on each divider, a different object lights up in yellow to show the active section. You are not arranging five existing messages. You are defining the matrix that will generate future slides.<\/p>\n\n\n\n The Seiketsu boundary:<\/strong> this is not Seiton at scale. Seiton finds the best place for selected content in one deck. Seiketsu encodes the rule that governs a class of future slides. The distinction is the difference between arranging five slides and designing the mold that will produce fifty consistent slides.<\/p>\n\n\n\n PowerPoint supports this logic through its Slide Master and associated layouts<\/a>. For the organizational dimension, see MLC’s approach to the corporate PowerPoint template as an efficiency engine<\/a>.<\/p>\n\n\n\n Shitsuke is the discipline that keeps the system working when deadlines, copied slides and local exceptions start to pull it apart. It does not design the standard\u2014that is Seiketsu\u2014and it does not continually redesign it. It makes sure that an approved standard is used, checked and learned from.<\/p>\n\n\n\n In the example, the template already exists on both sides. The team produces six recurring monthly decks. Without a routine, small exceptions accumulate: an outdated cover, a missing source, a chart copied from the wrong master. With Shitsuke, every delivery passes the same lightweight preflight, has a named owner and ends with a ten-minute reflection. The change is not the template; it is the cadence of verification.<\/p>\n\n\n\n The Shitsuke boundary:<\/strong> the template is already designed. If you are still choosing the grid or inventing the divider system, you are doing Seiketsu. Shitsuke begins when the question becomes: \u201cDid we use the agreed system again, and did we check it?\u201d<\/p>\n\n\n\n<\/span>The 5S are not five generic design tips<\/span><\/h2>\n\n\n\n
<\/span>Five questions keep the principles separate<\/span><\/h3>\n\n\n\n
<\/span>1. Seiri \u2014 Sort: remove what does not serve the decision<\/span><\/h2>\n\n\n\n
<\/span>How to apply Seiri<\/span><\/h3>\n\n\n\n
<\/span>2. Seiton \u2014 Set in order: give every selected element a place<\/span><\/h2>\n\n\n\n
<\/span>How to apply Seiton<\/span><\/h3>\n\n\n\n
<\/span>3. Seiso \u2014 Shine: find and fix defects<\/span><\/h2>\n\n\n\n
<\/span>How to apply Seiso<\/span><\/h3>\n\n\n\n
<\/span>4. Seiketsu \u2014 Standardize: turn one good solution into a system<\/span><\/h2>\n\n\n\n
<\/span>How to apply Seiketsu<\/span><\/h3>\n\n\n\n
<\/span>5. Shitsuke \u2014 Sustain: make the standard a habit<\/span><\/h2>\n\n\n\n
<\/span>How to apply Shitsuke<\/span><\/h3>\n\n\n\n