As designers, we don’t design in a vacuum. A good designer will need to learn to take the feedback from their peers, clients, and bosses to solve a particular design problem.
The goal of this document is to establish consistent guidelines for giving and receiving feedback on design, as well as reviewing and approving design as a group.
By first working independently on a problem, then converging to share insights, teams can leverage the benefits of both work styles, leading to rapid data analysis, diverse ideas, and high-quality designs.
To build superior products at scale, combine a classic business toolset with an open and transparent mindset.
Using Abstract to version control sketch files, collaborate on designs, and maintain a source of truth for final designs to be implemented.
With new product decisions happening constantly, how do you keep people updated with what is being worked on? How do you find the balance between over-documenting and keeping everyone well informed?
This article explores a workshopping technique which helps teams find simple, elegant solutions to the projects they’re working on.
How Abstract improved file organization and collaboration in our design team.
Detailed wireframes, high-fidelity comps, and motion prototypes all got enshrined as critical deliverables. Those design artifacts are unimportant. Only one deliverable matters: the product itself.
We all know how important collaboration is, but how many of us actually collaborate effectively with our teams?
Have you ever left a design critique feeling defeated and less excited about your work? Or frustrated because you didn’t get the type of feedback you were looking for?
Collaboration sounds great—until someone schedules another aimless “brainstorming” meeting. Bringing diverse people together can unleash their collective powers, but it takes more than a white board and Post-its.
Creating and refining UX deliverables is typically not a solitary act, and we frequently see UX professionals working with other team members to create documentation and design artifacts.
Design critiques are a critical part of the iterative design process, but all too often they are poorly thought out, poorly structured and poorly run. Here are 20 simple ways to make your design critiques more effective.
Our experts discuss the best ways to collaborate with stakeholders—whether internal or external—and customers—and why collaboration is so important.
What does the critique do for the design and the rest of the project? Do critiques really help and are they necessary? If so, how do we use this feedback to improve our creative output?