01 — Start with the goal, not the design

Before commenting on colors, fonts, spacing, animation, or layout, go back to the business goal.

Ask:

• What are we trying to communicate?
• Who needs to understand this?
• What should people feel?
• What action should they take?
• What problem is this design solving?

For example, instead of:

“I don't like this homepage.”

Try:

“The homepage looks polished, but I don't think a first-time visitor understands what we do within a few seconds.”

That's much more useful. The first statement gives the designer a preference. The second gives them a problem to solve.

---

02 — Explain what feels wrong

You don't need to know the exact design problem. You just need to describe what you're experiencing.

Maybe:

“It feels too playful for our audience.”

Or:

“The design looks good, but it doesn't feel as trustworthy as I want the brand to feel.”

Or:

“There is too much happening at once, and the main message gets lost.”

These observations help a designer investigate the underlying issue.

Sometimes the problem isn't the color.

It could be:

• Typography
• Visual hierarchy
• Composition
• Imagery
• Spacing
• Tone
• Content structure
• Brand positioning

Describe the feeling. Let the designer diagnose the design.

---

03 — Separate preference from purpose

This is one of the biggest differences between useful and unhelpful feedback.

There's a difference between: “I personally don't like blue.”

and

“Blue makes the brand feel too corporate for the younger audience we're targeting.”

The first is personal preference. The second connects the preference to strategy.

Personal preferences aren't irrelevant. But when you're building something for a business, the question shouldn't always be:

“Do I like this?”

A better question is:

“Does this help us achieve what we're trying to achieve?”

That's where creative decisions become more objective.

---

04 — Don't solve the designer's problem for them

Founders often have a strong instinct to suggest the solution.

For example:

“Make the logo smaller, move this section up, change the font to something like Helvetica, and maybe use a darker background.”

Sometimes that's exactly what is needed. But often, you're describing a symptom rather than the actual problem.

Instead, try:

“The logo feels like it's competing with the main message.”

Now the designer has room to explore the right solution.

Maybe the logo needs to be smaller. Maybe the headline needs more emphasis. Maybe the entire hierarchy needs adjustment.

Good feedback identifies the problem. Great designers help find the solution.

---

05 — Use references carefully

References are incredibly useful. But sending five different websites and saying:

“Make ours like this.”

can create more confusion than clarity.

Instead, explain what you like about the reference.

For example:

“I like how this website uses large typography and generous spacing. It feels confident without being loud.”

That's much better than:

“I want it to look like this.”

You can even break references down into:

I like: The typography, spacing, and simplicity.

I don't like: The color palette and overly editorial imagery.

Our goal: Keep the clarity but make it feel more technical and modern.

Now the designer has direction without being forced to copy another brand.

---

06 — Give feedback based on priority

Not every issue deserves the same attention. If you have 15 comments, don't treat all 15 as equally important.

Try grouping them:

Must fix

Issues that affect the business goal, usability, positioning, or brand direction.

Should improve

Important refinements that would make the work stronger.

Nice to have

Small details that can be addressed if time allows. This makes the process much easier for everyone. It also prevents a common problem:

Spending 30 minutes discussing a 2% detail while missing a 50% strategic issue.

---

07 — Give feedback in one place

Feedback scattered across:

• Slack
• Email
• WhatsApp
• Figma comments
• Voice messages
• Random screenshots

quickly becomes difficult to manage.

A centralized feedback system keeps the project moving.

For each comment, ideally include:

What: What are you referring to? Issue: What's not working? Why: Why does it matter? Priority: How important is it?

For example:

Hero section — High priority The headline feels too generic. We want visitors to immediately understand that we help growing SaaS companies build stronger digital products.

That's actionable.

---

08 — Don't give feedback before understanding the work

Sometimes a design looks strange because you haven't understood the thinking behind it yet.

Before saying:

“Why did you do this?”

try:

“Can you walk me through the thinking behind this direction?”

That question can change the entire conversation.

You may discover that:

• The color was chosen for accessibility.
• The layout is designed around conversion hierarchy.
• The typography supports the brand positioning.
• The animation exists to guide attention.
• A design choice was made specifically for mobile users.

Understanding the reasoning doesn't mean you have to agree. But it gives you better information before making a decision.

---

09 — Give feedback while the direction is still flexible

Feedback becomes more expensive when it arrives too late.

A project might move through: Strategy → Concept → Design → Development → Launch

If the strategic direction is wrong, discovering it during development creates unnecessary work.

That's why early feedback should focus on:

• Direction
• Audience
• Positioning
• Concept
• Tone
• Structure

Later feedback can focus more on:

• Typography
• Spacing
• Motion
• Details
• Polish

The earlier you solve the right problem, the less you have to redesign later.

---

10 — Avoid feedback by committee

More opinions don't always mean better creative work.

When five people give five different opinions, the designer often ends up trying to satisfy everyone. That's how focused creative direction becomes diluted.

A better approach is to establish: One decision-maker.

Others can contribute context and expertise, but someone should ultimately own the decision. This doesn't reduce collaboration.

It creates clarity and accountability.

---

11 — Give designers room to challenge you

A good creative partner shouldn't simply execute every request.

Sometimes they'll say:

“We can do that, but here's why we don't recommend it.”

That's valuable.

You hired them for their expertise, not just their ability to move pixels.

If the designer understands your goals, audience, and constraints, allow them to challenge assumptions when they have a reason.

You don't have to accept every recommendation. But you should be able to discuss it.

Healthy creative collaboration isn't agreement all the time. It's productive disagreement with a shared goal.

---

A simple feedback framework founders can use

Next time you're reviewing a design, try this:

1. What is working?

Start with what feels right.

2. What isn't working?

Identify the specific concern.

3. Why?

Connect the concern to the audience, business, or brand goal.

4. How important is it?

Mark it as high, medium, or low priority.

5. What outcome do you want?

Describe the result you're looking for, not necessarily the exact design solution.

For example:

What works: The overall direction feels premium. What doesn't: The homepage feels slightly too corporate. Why: Our audience is mostly younger founders and creative teams. Priority: High. Desired outcome: Keep the premium feel but make the brand feel more approachable and energetic.

That's feedback a designer can actually work with.

---

The best feedback isn't “make it better.”

It's “here's what we're trying to achieve.”

Founders don't need to learn typography, grids, color theory, interaction design, or motion principles to give good creative feedback.

They need to communicate:

The goal. The problem. The reason. The priority. The desired outcome.

From there, the creative team can do what they're good at:

turning problems into solutions.

And when both sides understand their role, the work gets better, revisions become more focused, and projects move faster.

Good creative work isn't created by designers alone.

It's built through better collaboration.

---

A quick checklist before sending feedback

Before you hit Send, ask yourself:

• Does this comment explain the problem?
• Have I explained why it matters?
• Am I giving direction or just expressing preference?
• Does this connect to our audience or business goal?
• Is this actually important right now?
• Am I solving the problem too early instead of letting the designer explore?
• Can the designer take this feedback and act on it immediately?

If the answer is yes, you're probably giving useful feedback.

Better feedback doesn't mean more feedback. It means clearer feedback.