Design Mockups: What to Expect and How to Give Feedback

The moment has arrived: your design team has sent over mockups of your new website. Suddenly you're staring at full-color, beautifully rendered pages and feeling the weight of needing to provide meaningful feedback. This guide will help you understand what you're looking at, what to focus on, and how to communicate your thoughts in ways that lead to a better final product.

What Design Mockups Actually Are

Design mockups are high-fidelity visual representations of what your website will look like. Unlike wireframes, which focus on structure and layout, mockups incorporate all the visual elements: colors, typography, images, icons, and branding. They show how the approved wireframe structure will be brought to life with your visual identity.

For more insights on this topic, see our guide on Website Launch Checklist: 25 Things to Verify.

Think of the progression this way: if wireframes are the architectural blueprints, mockups are the detailed renderings that show exactly what the finished building will look like—including the paint colors, fixtures, and landscaping.

Mockups are typically created as static images, though you might receive them in an interactive prototyping tool that lets you click through different states and pages. Either way, remember that mockups are still design files, not functioning code. The development phase comes next.

What to Focus On During Review

With so much visual information to process, it helps to have a structured approach to reviewing mockups:

Brand Alignment

Does the design feel like your brand? Check that colors, fonts, and overall tone match your brand guidelines and the impression you want to make. If something feels "off," try to articulate why. Is it too corporate? Too casual? Too busy? Too sparse?

Visual Hierarchy

Your eye should naturally move to the most important elements first. Does the design guide attention appropriately? Are headlines prominent enough? Do calls-to-action stand out? Is it clear what visitors should do on each page?

Consistency

Look across multiple pages. Do similar elements look and behave consistently? Are headings treated the same way throughout? Do buttons maintain consistent styling? Inconsistency creates confusion and erodes trust.

Content Fit

If real content has been placed in the mockups, does it fit well? Are there awkward line breaks or text that seems crammed into too-small spaces? If placeholder content is used, consider whether your actual content will work in those containers.

Emotional Response

Step back from the details and consider your overall emotional response. Does the design make you feel proud? Excited? Professional? Trustworthy? Your gut reaction matters, even if you can't immediately articulate why.

How to Give Constructive Feedback

The way you communicate feedback significantly impacts how effectively it can be addressed. Here are principles for feedback that helps:

Be Specific

Instead of "I don't like the colors," try "The blue feels too corporate for our brand—we're going for a warmer, more approachable feel." Instead of "Something's wrong with this page," try "The testimonials section feels lost at the bottom—I'd expect it to have more visual prominence."

Explain the Problem, Not Just the Solution

When you prescribe a specific solution ("Make the logo bigger"), you might accidentally create new problems. When you explain the underlying concern ("I'm worried visitors won't recognize our brand quickly enough"), designers can find the best solution—which might be logo size, but might be something better.

Distinguish Preferences from Requirements

Some feedback is subjective preference; some addresses genuine problems. It's helpful to distinguish between "I personally prefer blue to green" and "Our brand guidelines require this specific shade of green." Both types of feedback are valid, but they should be weighted differently.

Consolidate Stakeholder Input

If multiple people on your team are reviewing mockups, gather all feedback and present it as a unified response. Contradictory feedback ("Make it bolder" from one person and "Make it more subtle" from another) puts designers in an impossible position. Resolve internal disagreements before presenting feedback.

Prioritize Your Feedback

Not all feedback is equally important. Help your design team understand what's critical versus what's nice-to-have. If you have twenty pieces of feedback, identify which five matter most.

Common Feedback Mistakes to Avoid

Even well-intentioned feedback can go wrong. Here are pitfalls to watch for:

Design by Committee

When too many people provide unfiltered feedback, the result is often a muddled compromise that satisfies no one. Designate a single person to consolidate and present feedback.

Scope Creep

The design phase isn't the time to add features or pages that weren't in the wireframes. Structural changes at this stage require going back to wireframing, which impacts timeline and budget.

Comparing to Competitors

"Can we make it look more like [competitor's website]?" is rarely helpful feedback. If there's something specific you admire about a competitor's site, articulate what that is and why it appeals to you.

Forgetting the Users

It's easy to focus on what you like personally while forgetting what your users need. A design that appeals to you but confuses your customers isn't a successful design.

What Happens After You Approve

Once mockups are approved, the design becomes the specification that developers will build from. This is why thorough review matters—changes after development begins are significantly more costly in both time and money.

That said, minor refinements often happen during development as designs meet real content and browser constraints. Approved mockups are a target to build toward, not an unchangeable contract.

Tips for a Smooth Review Process

• Take your time: Don't rush feedback. Live with the designs for a day or two before responding.
• View at actual size: Mockups viewed on a small laptop screen versus a large monitor can give different impressions. Try to view them at realistic sizes.
• Check mobile designs: If mobile mockups are provided, review them with equal care. Mobile visitors likely make up a significant portion of your traffic.
• Trust the process: If something looks different from what you imagined, consider that the designer may have good reasons. Ask questions before demanding changes.
• Celebrate what works: Don't only point out problems. Noting what you love helps designers understand your preferences and builds a positive working relationship.

Related Reading

• The Website Discovery Phase: What Happens and Why It Matters
• Website Wireframes Explained: Why Every Project Needs Them
• Website Content Gathering: Your Role in the Process