ARTICLE SUMMARY: Design, like art, is a matter of personal perception. What one person sees as beautiful or effective another may view differently. There in lies the problem.
Design projects succeed when everyone involved agrees on what the final product should be. This means collaboration is essential, but it also needs structure. Setting clear guidelines ensures that team members are on the same page, communicate effectively, and work toward a shared goal.
From personal experience, Ted Goas’ “How I review design work“ provides a roadmap to help design teams establish a common definition of good design through a structured approach. Part of this roadmap includes
- Having a Narrative
- Your Own Ideas
- Masking Complexity
Having a shared goal helps designers, developers, and stakeholders work toward the same vision, reducing confusion and miscommunication. When everyone understands the goal, the design remains cohesive across different screens, components, and experiences.
When team members agree on the purpose and priorities of a design, they can provide more constructive feedback and work together more effectively. A clear goal ensures that the design meets user needs rather than being driven by personal preferences or conflicting ideas.
Ted Goas concludes his article by reminding us, “When we embrace different definitions of “good,” lean on clear frameworks, and create a supportive space for critique, we can deliver design work that hits both creative and business goals.”
This article is well worth reading, especially helpful for anyone involved with design teams. Let us know what you think in the comments.
