How to Teach PowerPoint and Give Slide Critique That Improves Decks

Being good at PowerPoint and being good at helping someone else get good at it are different skills. The fastest fix is usually to take the mouse and redo the slide. It feels helpful, and the learner leaves with a better slide and no better judgment.

This page gives you a repeatable way to diagnose, demonstrate, critique and coach. The running example is a learner named Priya, a new team lead who sent you her 10-slide onboarding deck with the note "Can you make this look better?"

Diagnose before you fix

"Make it look better" is almost never a design request. Before you touch a slide, sort the problem into one of six types. Each one needs a different kind of help:

Priya's deck has topic titles ("Benefits," "Tools," "First Week"), nine bullets per slide and a consistent template. That's a story and content problem, not a design one. Redesigning the colors would waste her time and yours.

Demonstrate one skill at a time

When the issue is the tool, teach the skill, not the slide. Use a five-step pattern and keep it to one skill:

1. Show a finished example. A slide where the skill is obviously working.
2. Explain the principle in one sentence. "Aligned objects read as related; ragged ones read as careless."
3. Demonstrate slowly, saying every click out loud.
4. Let the learner repeat on their own file while you watch.
5. Add a variation that makes them think, not just copy.

Here's what "align and distribute" looks like in five minutes:

When you demonstrate on a shared screen, zoom the editing view (Ctrl+mouse wheel) and pause on each menu so the learner can see the ribbon names you're reading out.

Use critique language that changes slides

Vague feedback ("it's busy," "make it pop," "I don't love the blue") makes the learner guess what you want, so they guess your taste instead of learning a principle. Use a four-part pattern:

1. Start with the slide's job. "This slide should get new hires to book their security training."
2. Name the issue. "The training deadline is bullet 7 of 9, in the same size as everything else."
3. Explain the effect on the audience. "People will skim the first three bullets and miss the one thing they must do."
4. Suggest one improvement. "Try making the deadline the title and moving the rest to the handout."

Coach the revision without taking over

The learner should make every change. Your job is to make the decision easy to think through:

1. Ask what the slide needs to do. Let them say it.
2. Offer two options, not one answer. "You could make the deadline the title, or keep the list and highlight the deadline in the accent color."
3. Let the learner choose and build it.
4. Compare before and after side by side.
5. Ask them to reflect. "What changed, and why does it work better?"

Use PowerPoint's review tools so the learner keeps the pen:

• Comments. Select an object and go to Review › Comments › New Comment (Ctrl+Alt+M). Anchor each comment to the object it's about, and @mention the learner so they get notified. They resolve the thread when they've acted on it.
• Version history. In a file stored on OneDrive or SharePoint, File › Info › Version History lets you both open the before version later. That's your before/after evidence for free.
• Compare. If the learner sends a revised copy as a separate file, open the original and use Review › Compare › Compare to see every change in the Revisions pane.

Close the loop with reflection

After the revision, ask one of these and write down the answer in the revision log:

• Which slide improved the most?
• What did you remove, and why?
• What would you do differently in the next deck?

If the learner can explain the change in their own words, the judgment transferred. If they say "because you said so," it didn't, and the next session should revisit the principle.

Run a 20-minute tutoring session

A tight structure keeps a session on one or two improvements instead of a tour of everything wrong:

The last step is the multiplier. Priya fixes one slide with you and then applies "every title states the takeaway" to the other nine on her own. Ask her to send the result before your next session.

Build a learning community around practice

One session improves one deck. A community keeps people practicing between sessions. Pick two or three of these and run them on a regular rhythm:

• Peer review rounds. Pairs swap one slide each week and use the four-part critique pattern.
• Before/after gallery. Learners post a before/after pair with a one-line rationale. Strong examples become teaching material.
• Weekly challenge. "Fix this broken slide" with a constraint ("no new colors," "three words max in the title").
• Office hours. A recurring open slot for workflow and tool questions.
• Template library. Shared, versioned layouts so learners stop rebuilding the basics.
• Learner portfolio. Each person keeps their before/after pairs, reflections and revision logs in one place.

A simple peer review form keeps critique specific:

Common mistakes when teaching and critiquing

• Taking the mouse. You get a better slide; they don't get better. Hands off unless you're demonstrating a click path, and give the mouse back immediately.
• Fixing the symptom. Redesigning a slide that has a story problem produces a prettier confusing slide.
• Taste comments. "I'd use green" is a preference. Tie every comment to an effect on the audience.
• Too many comments at once. Prioritize. Three per slide, one marked as most important.
• Teaching three tools in one demo. One skill, one principle, one variation.
• No reflection. Without "what changed and why," you can't tell if judgment transferred.
• Praising only polish. Call out good decisions too: "Cutting the agenda slide was the right call, the opening now gets to the point in ten seconds."

Practice