As I read Susan Weinshenk’s blog series 7 Tips To Get A Team To Implement Your Recommendation I wondered why we find ourselves struggling to convince a team that we know what’s best, that our ideas are right? Why do we continue to walk into design reviews praying that our carefully considered work won’t be dismantled? (Insert scene of Don Draper walking into a client pitch.) I hear this all the time “They brought me onboard, so they must understand the value of UX. Why won’t they listen to me?” Heck, I’ve said it myself. Truth is that it’s time for change. Designers must change.
Look at the evolution going on within the development community. Agile methodologies like Scrum have enabled programmers to redefine their relationship with stakeholders. They have created a new way of working that is more effective, creates more business value, increased client satisfaction and last but not least, happier developers. What can we as designers learn from our counterparts to increase our own effectiveness and job satisfaction?
Agile requires people working together on a project to act like a team. Everyone is responsible for the outcome regardless of rank or discipline. It’s an egalitarian structure. (Picture team-building exercises. Trust falls aplenty.) Teams are “self organized” in cross-functional style, which allows everyone to contribute according to their strengths as well as cover gaps instead of restricting themselves to an organizational silo. Collaboration is the name of the game. Agile team members talk to each other A LOT. There is plenty of white-boarding and figuring things out together.