What are the four zones in a feedback grid?

The four zones are what I liked, what could improve, new ideas to try, and questions and concerns. Sorting feedback into these buckets forces clarity and gives you a prioritized to-do list.

When should you use a feedback grid?

Use it right after a review, demo, or usability test while reactions are still fresh. A concept test or design review before it generates the raw feedback you sort into the grid.

Feedback Grid Template (With an Example)

A feedback grid template captures reactions to your work in four simple zones, so feedback turns into next steps instead of a vague pile of comments. It’s quick to run after a review, a demo, or a usability session.

Why it works: unstructured feedback (“it’s nice,” “not sure about this part”) is hard to act on. Sorting it into four buckets forces clarity and gives you a prioritized to-do list.

The four zones

What I liked — what’s working; keep it.
What could improve — what’s weak or confusing.
New ideas to try — additions worth exploring.
Questions and concerns — open issues and risks.

How to use it

Collect in the moment. Run it right after a review or test, while reactions are fresh.
One note per point. Keep items atomic so they’re easy to sort and prioritize.
Separate signal from noise. “Questions and concerns” often hides the most important issues.
Turn it into action. “Could improve” and “new ideas” feed your next iteration — or a How Might We.

An illustrative example

Feedback after testing the SesTech concept:

Liked: Solving problems by voice, anytime; the personality felt friendly.
Could improve: Routing sends users to the generic homepage, not the right page; registration and syncing feel tedious.
New ideas to try: More voice tones; a more playful personalization flow.
Questions and concerns: Why ask for an account number if the bank app already exists? Is there a privacy concern with account access?

In four boxes you’ve got a clear, prioritized iteration plan — and a record of how you handled feedback, which is exactly the kind of maturity a case study should show.

What to use before and after

Before: a concept test or a design review generates the raw feedback.
After: reframe the strongest improvements with a How Might We and iterate.

For how handling feedback becomes part of a portfolio story, see the UX case study guide.

Turning messy feedback into clear next steps is part of the thinking a strong case study shows. Folioverse helps you turn that into a case study recruiters trust. Try it free.