Design reviews are well-known to designers but may not be familiar to other practitioners involved in optimizing user experience. A large UX team within the federal government found the design review process was creating conflict within the unit. They turned to DFFRNT to provide training and develop policies that would smooth the review process and build a more effective team.
Innovation, Science and Economic Development Canada (ISED) has a broad mandate. This federal government department focuses on investment, science, small and medium-sized businesses, sustainable technologies, global trade, and tourism. Within ISED is the Design Centre of Expertise (DCoE), which functions as the user experience team for the department’s website, software, interfaces, and tools.
In the design field, you can sometimes get myopic about your own design. That’s why it is standard practice to have design reviews and invite feedback and critique. With user experience design teams becoming more multi-disciplinary, there may be professionals from other fields of expertise who are unaccustomed to this process.
At ISED, some members of the DCoE team were unfamiliar with the concept of a design review. The organization wanted to make the feedback process more effective. It turned to the experienced designers at DFFRNT to develop a customized process for design review.
At DFFRNT, we have extensive knowledge of strategic design and offer training and advisory services to help large organizations in both the public and private sectors build internal user experience expertise.
Design, product development and software development are very ritualistic in nature. We wanted the ISED UX team to develop their own design review process, to make their own rules.
We developed and presented two training sessions for the DCoE team, and then codified the results in a framework document and a poster summarizing the salient points of giving and receiving feedback.
Let’s jump on a call and see if there is a DFFRNT way to approach it.
Click here to book a no-obligation discovery call.