the first round client meeting.
Invite the designer to all Agile ceremonies.
This housekeeping can eliminate barriers. Another way to support this relationship is to bring a third voice into the equation: the user’s.
User research advocacy reduces designer-developer rework
Maybe an online portal has lots of apps under one UI and america phone number list a ton of custom work. Weeks and months of design and development hours go into it. No one wants to waste their time. That’s why it’s necessary to validate requirements with users.
Mattison recommends that designers and developers co-create high-fidelity mockups. He never wants to be in the position where someone points out that the team made some assumptions, which made that work less solid or valid.
It’s not surprising that one of Mattison’s favorite design collaborations included a team that tested an element every 10 weeks. It kept everyone on track to meet the spirit of what the user desired. Today, he’s committed to the design practice of user research. He frequently asks his teams how they can make sure what they’re building fits the needs of the user – before they get too deep in the process.