Asking for and receiving feedback is one of the most important parts of any designer's role. Collecting, sorting, and prioritizing feedback in your design process is crucial—whether you're a solo freelancer working directly with clients or part of a large cross‑functional scrum team.
The goal is to gather and understand feedback as it relates to objectives, timelines, and budget. Without this, you can find yourself operating in a vacuum and presenting something that doesn’t align with stakeholder intent or technical feasibility.
What we’ll cover
- Getting feedback from your immediate team
- Collaborating with sister scrum teams
- Presenting updates to stakeholders
1. Getting feedback from your immediate team
When to ask
Ask for feedback early and often. Scrum teams include multiple roles—each with unique context. Frequent alignment prevents rework and keeps progress moving.
Tools for asynchronous feedback
Use short Loom videos to walk through design decisions and proposed options. This provides essential context that static mockups can miss and allows collaborators to review on their own time.
What to include in your videos
- Context and goals of the work
- Key design decisions and alternatives
- Pros and cons and any technical constraints
- User research insights that informed choices
- Specific feedback requests, timeline, and next steps
2. Collaborating with sister scrum teams
In larger organizations, multiple scrum teams often work on different features within the same product. Share updates and collect feedback across teams to keep UI patterns consistent and avoid redundant work.
- Schedule designer‑to‑designer reviews mid‑sprint
- Use FigJam or Miro to capture asynchronous feedback
- Hold post‑development engineer reviews for edge cases
3. Presenting updates to stakeholders
Executives have limited time. Keep updates concise and easy to consume. Silent QuickTime demos under a minute work well—they can be watched between meetings and embedded into decks.
The perfect accompanying message
- Changes since last review
- Specific feedback needed
- Response deadline
- Impact of delays
Final tips for better feedback loops
- Seek feedback early and often
- Understand perspectives from engineering, product, and stakeholders
- Match your method to your audience (Loom, QuickTime, FigJam)
- Establish regular cadences to prevent last‑minute surprises