Why design feedback is broken

Your team just wrapped a homepage redesign. The Figma file looks great. Then the feedback starts rolling in — a Slack message here, an email there, a screenshot in WhatsApp with a vague "can you move this up a bit?"

This is the reality for most design teams. And it's costing way more than a few minutes of confusion.

The problem with scattered feedback

Design teams lose hours every week chasing down feedback across tools. Comments live in email threads, Slack DMs, PDF annotations, and — worst of all — verbal conversations that nobody writes down.

When feedback is spread across five different platforms, someone has to play detective. Designers end up scrolling through Slack threads, digging up old emails, and cross-referencing meeting notes just to figure out what needs to change. That's not design work — that's admin work.

The result? Missed revisions, duplicated work, and frustrated clients who feel ignored.

The real cost

Every unclear comment creates a revision cycle. Designer interprets it one way, stakeholder meant something else. Now you're on version seven of a hero section that should've shipped days ago.

Multiply that across every project. Every client. Every week. Teams lose 5-10 hours a week just organizing and clarifying feedback. An entire workday — gone to a broken process, not a lack of skill.

What good feedback looks like

Good feedback is contextual. It lives right where the design lives — pinned to a specific element, on a specific version, with a clear status.

Instead of "the spacing looks off on the card component," imagine a pin placed directly on the card with the note: "Reduce padding from 24px to 16px to match the design system." That's actionable. That's specific. That gets resolved in one pass.

Good feedback also has ownership. Every comment is assigned to someone. No ambiguity. And it has a status — open, in progress, resolved — so the whole team sees where things stand at a glance.

How teams are fixing it

Centralize all feedback in one place — no exceptions. Set clear review windows so feedback doesn't trickle in for weeks. Use tools that tie comments directly to the design, not to a separate doc or chat thread. For practical advice, check out our 5 tips for faster design reviews.

The result: fewer loops, faster sign-off, and a process that doesn't make everyone miserable. Want to know what this actually costs your team? Read about the hidden cost of scattered design feedback.

A better way

That's why we built layernote. Pin it, comment, assign, resolve. Live website, Figma file, static mockup — doesn't matter.

One place. Nothing lost. Ship faster.