Magga Dóra

Magga Dóra


User experience designer with background in psychology and computer science. Loves anything and everything that has to do with user behavior. Also loves travelling, photography and teaching. Please refer to her CV for details. One of the founders of Arctic Girl Geek Dinner - Tæknitátur.

Watch me at TEDx Reykjavik in 2009

Read more posts by Magga Dóra.

Portfolio and more information
My LinkedIn profile

Roles

The other day I stumbled upon a tweet that caught my attention. @drewm said:

Poll: As a designer, would you want your developers to tell you if they think your designs are outdated? Or keep quiet and let you fail?

Reference

It got me thinking about my projects and how much better results I get when I’m working with a web developer that I trust, that gives me feedback and is committed like I am to creating a great user experience with the product we are creating. I have been fortunate enough to work with a couple of developers like that.

So I replied to Drew:

@drewm The dialog between the designer and the developer makes the end result much better so I want to discuss

Reference

and i decided to see what other people are thinking and ran into this reply:

@drewm as a developer: would you like your designer to tell you they think your code is inefficient and bad structured? 🙂

Reference

A few other repliers shared the same sentiment. And I could see that Drew like me thought about roles cause his next tweet was this:

It’s a balancing act between wanting the project to be the best it can be, and overstepping the mark with someone else’s role in the team.

Reference

Of course in any team roles are important but sometimes team members lose focus on the end result and start focusing on roles. And that is detrimental to any project.

When all team members transcend their roles and prioritize the outcome of the project over their job description you get a better outcome. When team members are ambitious on behalf of the product they are creating over their careers you get a superior product.

So I’m a little worried about the responses that Drew got. They indicate an unwillingness to discuss, to cooperate, to work together for the best result. The indicate a willingness to fail, to assign blame. Makes me wonder what sort of welcome feedback from testers receives in these teams. A little later Drew posted the result of the poll:

Poll results: most designers would want to know, but wouldn’t want to be told. So, osmosis it is, then.

Reference

I of course didn’t see all the responses that Drew got so I don’t know how he came to this conclusion but regardless I think it is such an important thing to keep the dialog open that who we believe wants discussion and who doesn’t is beside the point. The dialog should be open. We can open it in all our teams. Let me start by saying:

Please, when you start implementing my design, tell me how it can be better so that we can create the best user experience for our users.

🙂
MD


No Comments

Your thoughts:

* Pretty please