A design system that doesn't respond to feedback becomes disconnected from reality.
Feedback-driven improvement means the system evolves based on:
how teams actually use it,
what problems they encounter,
and what they need to build better products.
Without feedback loops, the system team operates in isolation,
making assumptions that may not match real-world needs.
Collect feedback systematically
Feedback should be easy to give and easy to process.
Collect feedback systematically
Bug report
Current behaviorWhen the viewport is mobile, the component now going to full width.
Expected behaviorWhen the viewport is mobile, the component should go to full width.
Component affected mds-status-bar
Banner
Button
Modal
Table
Button component
Submit
Provide clear channels for feedback (forms, issues, surveys).
Rely solely on informal conversations or hallway chats.Make feedback collection part of regular workflows.Wait for feedback to come to you.
A list of tools and services related to this argument.potentially outdated
Track component usage and adoption patterns.Assume all components are equally valuable.Identify unused or underused components.Ignore metrics that suggest components aren't working.
A list of tools and services related to this argument.potentially outdated
Teams need to see that their input leads to change.
Feedback acknowledgment and implementation
Implemented2 days ago
Button component feedback form
Feedback: "Add a feedback form directly on the component page"
Response: Added inline feedback form with status bar. Users can now provide feedback
directly from the component documentation page.
In progress1 week ago
Table component mobile responsiveness
Feedback: "Table component doesn't work well on mobile devices"
Response: Investigating mobile layout improvements. Expected completion in 2 weeks.
Acknowledged3 days ago
Accordion component accessibility
Feedback: "Accordion needs better keyboard navigation"
Response: Thank you for the feedback. We're reviewing accessibility improvements for
the next release.
Acknowledge feedback promptly and transparently.Collect feedback without responding or acting on it.Communicate when and how feedback influenced decisions.
Make changes without explaining the connection to feedback.
A list of tools and services related to this argument.potentially outdated
Accordion custom iconAllow custom icons for accordion items
2 teamsLowP2
Prioritize changes that affect many teams or critical workflows.
Treat all feedback requests with equal urgency.Balance quick wins with strategic improvements.Only pursue large, complex changes.
A list of tools and services related to this argument.potentially outdated
Feedback should inform decisions, not just sit in a backlog.
Feedback-driven roadmap
Q1 2024Completed
Button component improvementsBased on feedback: 12 teams reported mobile touch target issues. Implemented larger touch
targets and improved mobile interaction patterns.
Q2 2024In progress
Table component enhancementsBased on feedback: 8 teams requested multi-column sorting. Currently implementing sorting
capabilities and mobile responsiveness improvements.
Q3 2024Planned
Accessibility improvementsBased on feedback: Multiple teams highlighted keyboard navigation issues. Planning comprehensive
accessibility audit and improvements across all components.
Regularly review feedback and usage data to inform roadmap.Collect feedback without integrating it into planning.Share how feedback shaped system improvements.Make decisions in isolation from user needs.
A list of tools and services related to this argument.potentially outdated
