Best practices for using Loom to give feedback on design projects

Giving feedback on design projects can turn into a mess of screenshots, endless Slack threads, or meetings nobody wants. If you’re tired of that, using Loom to record quick video feedback is a smarter, faster way to get your point across—if you do it right. This guide is for designers, product managers, and anyone who wants to give better design feedback without making things more confusing.

Let’s get into some real-world best practices that actually help.


1. Get the Basics Right Before Hitting Record

A common mistake: you dive in, start recording, and end up rambling, missing the important stuff. Here’s how to avoid that:

  • Know What You’re Reviewing
    Open the design file, prototype, or whatever you’re commenting on before you start. Have any comparison designs ready.

  • Jot Down Key Points
    Don’t script the whole thing, but make a quick bullet list of what you want to cover. This keeps you focused and saves everyone time.

  • Check Your Tech

  • Make sure your mic works and your screen is uncluttered.
  • Close tabs with sensitive info. Nobody needs to see your inbox or Slack DMs.
  • If your internet is slow, record locally and upload after—don’t risk a choppy video.

Pro tip: Keep your face on camera, if you’re comfortable. It’s more personal, and people are less likely to misread your tone.


2. Keep It Short (But Not Vague)

Nobody wants to sit through a 15-minute video for two minutes of feedback. Don’t over-explain—hit the key points, and move on.

  • Aim for 3-5 Minutes Max
    Anything longer, and people start zoning out. If you need more time, break it up by topic (“Let’s talk about the homepage first, then the mobile nav in another video”).

  • Be Direct, Not Blunt
    Skip the filler (“Hey guys, hope you’re having a great day!”). Just say what you notice and what you think.

  • Use Visual Cues
    Move your mouse, highlight, or click as you talk. Don’t just describe—show. Loom’s drawing tools can help, but don’t overdo the circles and arrows.

What to skip:
Don’t narrate every action (“Now I’m clicking here, now I’m scrolling down…”). Only point out what matters.


3. Make Your Feedback Actionable

General comments like “This feels off” or “Can we make it pop?” aren’t helpful. Get specific so the designer knows exactly what to do next.

  • Point to the Problem, Suggest a Fix
  • “The button color blends into the background—could we try something higher contrast?”
  • “Spacing between these cards feels tight. Maybe add 8px?”

  • Prioritize Your Feedback
    If you have a laundry list, call out what’s critical and what’s just nice-to-have. Designers appreciate knowing what to tackle first.

  • Ask Questions, Don’t Just Dictate
    If you’re unsure about a choice, ask why it was made. “Was there a reason for using this font here?” is better than “Change this font.”

Pro tip: If your feedback is subjective (“I just don’t like this color”), own it. Don’t pretend your opinion is a universal truth.


4. Organize and Label Your Loom Videos

If you’re sending out lots of video feedback, chaos is just a few links away. Make things findable.

  • Clear Titles
    Name your video with the project, date, and topic:
  • “Homepage Feedback – May 2024”
  • “Mobile Nav Review – Round 2”

  • Add a Short Description
    Loom lets you add a quick note. Use it to list what’s covered (“Covers hero section, CTAs, and footer icons”).

  • Timestamp Key Points
    If it’s a longer video, use Loom’s timestamp feature or just note “2:10 – Button color feedback” in the description.

  • Share Wisely
    Post your Loom in the relevant channel or thread. Don’t just DM it—people lose track.

What to ignore:
Don’t worry about editing out every “um” or mistake. Perfect videos aren’t the goal—clear feedback is.


5. Invite (and Respond to) Follow-up Questions

Loom makes it easy for people to comment or react. Use that—feedback shouldn’t be a dead end.

  • Encourage Replies
    End your video with, “Let me know if anything’s unclear or if you want to chat through options.”

  • Respond to Comments
    If someone asks a question under your video, reply there instead of starting a new thread. Keep the conversation in one place.

  • Don’t Be Precious
    If someone disagrees or has a better idea, be open about it. The whole point is to get to a better design, not to win an argument.


6. Know When Loom Isn’t the Right Tool

Loom is great for quick, visual feedback, but it’s not a silver bullet. Sometimes, a different approach works better.

  • Skip Loom If:
  • The feedback is super detailed and needs lots of reference links—use a doc.
  • You need a real-time back-and-forth—jump on a call or use Figma comments.
  • It’s sensitive or could be misunderstood—written notes might be safer.

  • Combine With Other Tools
    Loom is best as a supplement, not a replacement. Pair it with written summaries or design tool comments so nothing gets lost.


Common Mistakes (and How to Avoid Them)

Let’s keep it honest. Here’s what trips people up:

  • Rambling or Going Off-Topic
    Stick to your bullet points. If you catch yourself drifting, pause and refocus.

  • Being Too Vague (“Make It Pop!”)
    Say what you mean. If you want a bigger font, say “Try 20px instead of 14px.”

  • Overloading One Video
    Don’t cram every note about the whole project into a single recording. Split by section or screen.

  • Missing the Point
    Don’t get lost in nitpicks. Focus on what actually improves the design or solves the problem.


Wrapping Up: Keep It Simple, Iterate Often

The real trick with Loom feedback? Don’t overthink it or aim for perfection. Stick to clear, focused videos that actually help the project move forward. If something isn’t working—too long, too confusing, too many videos—adjust. The goal is better design, not more feedback. Keep it simple, keep it actionable, and don’t be afraid to hit “Record” again if you missed something. That’s how you actually get things done.