Good feedback is like giving clear directions to someone who wants to help you. The better your directions, the closer you’ll get to what you want. Bad feedback wastes time and money.

1. Be Specific, Not Vague

Instead of saying: “I don’t like it” Say this: “The blue color feels too bright. Can we try a darker shade?”

Instead of saying: “Something’s wrong with the contact page” Say this: “When I click the contact button, nothing happens”

2. Focus on One Thing at a Time

Don’t send a long list of 20 changes. Pick the three most important things first. Your developer needs time to work on each item properly.

3. Explain Why It Matters

Help your developer understand your business needs.

Example: “The phone number should be bigger because most of my customers are older and need to see it clearly.”

Use Simple Words

You don’t need to sound technical. Use everyday language:

• “Move this higher up”
• “Make this stand out more”
• “This is hard to read”
• “This feels too busy”

Point to Exact Spots

When something is wrong, show exactly where:

• Take a screenshot
• Draw a circle around the problem area
• Say which page you’re looking at
• Mention if you’re using a phone or computer

Give Examples

Show your developer what you like:

• “I love how Amazon’s search works”
• “This restaurant’s menu page is perfect”
• “Look at how clean this feels”

Good Feedback Sounds Like

• “The bakery’s opening hours are wrong. We close at 6 PM, not 8 PM.”
• “The photos are beautiful, but can we make them load faster?”
• “I love the design! Can we add our new phone number to the top?”

Bad Feedback Sounds Like

• “Fix everything”
• “Make it look more professional”
• “My friend says it’s ugly”

Regular Check-ins Work Best

Your developer should show you progress every week. This prevents big surprises at the end.

Don’t Wait Until the End

If you see something you don’t like early on, speak up. It’s much easier to fix things as you go.

Use This Simple Format

What: Describe what you see
Where: Say exactly where the problem is
Why: Explain why it matters to your business

Example:

• What: The “Book Appointment” button is too small
• Where: On the main page, below the salon photos
• Why: Customers need to book appointments easily – this is how I make money

Don’t Compare to Competitors

Instead of saying “Make it like John’s bakery website,” explain what you like about John’s site.

Don’t Ask for Personal Opinions

Your teenager might not be your target customer. Focus on what your actual customers need.

Don’t Change Everything at Once

Pick your battles. Your website can grow and improve over time.

Your Developer Wants to Help

They want you to love your website. They’re not trying to make your life difficult.

Ask Questions

If you don’t understand why they suggest something, ask them to explain it in simple terms.

Be Patient

Good work takes time. Rushing leads to mistakes.

Try Everything

• Click all the buttons
• Fill out the contact form
• Try it on your phone
• Ask a friend to look at it

This helps you give complete, useful feedback instead of finding new problems later.

1. Be specific with your feedback: say exactly what’s wrong and where it is
2. Explain why changes matter: help your developer understand your business needs
3. Use simple, everyday language: you don’t need to sound technical
4. Give feedback regularly: don’t wait until the end to speak up
5. Focus on one thing at a time: don’t overwhelm with long lists of changes
6. Test everything before giving feedback: make sure you’ve tried all features
7. Be patient and ask questions: good work takes time and communication
8. Remember your developer wants to help: work together as a team