qué se aprende en OMA

201412241244.jpg

de la un poco triste y un pelín patética lista de Ivan Sergejev´s de las 20 cosas que aprendió en OMA te rescato cuatro

2) Architecture is 98% “production”.

10) There will always be people you will not be able to get along with. Don’t fight it. Treat them with respect at all times. Don’t be emotional. Professionalism and self-possession are key in business – just look at Sho or Rem during client meetings. Diplomacy is the art of dealing with a*holes. It is essential.

13) However, never say you are not sure if you can perform a certain task, even if you aren’t. Say “YES”.

17) Therefore, learn to work with imperfect but readily available givens. If you continue hunting for the perfect image to start photoshopping, you will keep looking and will never start working at all. So just start using what you have and produce an awesome piece of work anyway.

18) While en-route, remember: keeping your iteration cycle short is the key to producing great work. It’s ok to start with a sh*tty mock-up – just make sure it communicates your idea and you do it asap. Once you’ve shown it to your client/ colleagues/ boss and solicited feedback, you fix it. And again. And again. And again. You’ll be surprised how awesome it will turn out in the end.

mira la lista completa aquí

What I’ve learned at OMA

[From What I’ve learned at OMA | Ivan Sergejev’s Blog]

hattip: tnks JM Echarte!

aquí comentada por el propio JM https://nblo.gs/12euqe