The article/interview hits quite the target. The lack of user contact, in the design process of designer, via user research, testing and others co-design methods, that would implies the user in the process and get the designer close to the real end-users.

Moreover, I blame the companies that thought every problem can be solved by designers in the software waterfall process and let the developers shut it. It can never work.

it reminds me of Tracktl http://www.tracktl.com/en/product.html

there you go : https://web.archive.org/web/20170313222854/http://ffffound.com/

:D

Like everybody : work your stuff, try different techniques it will help you define yours. Few months ago, someone proposed to draw 20 heads a day, every day for at least a month. and keep every single one so you can have a critic of your mistake and know what to change and explore. Also : draw reality. It will teach your way out around mastering perspective (and drawing organic stuff like humans, trees, etc.) have a look at this guy : https://www.youtube.com/watch?v=R6mjYW6XMuM it might keep you motivated to go out and try other techniques Oh and if you can, draw models, preferably nudes. you will be great in drawing people in no time

But honestly, the best advice I can give you is : get a teacher. You will learn faster, she will be a good critic and will challenge you in drawing various stuff. It sounds obvious, but really it is the best !

fuck yeah Design, sometimes I love you

this is sooooooo cool

Low-poly design for 2017 ? YEAH RIGHT

love it, and love the work for drxlr.com

I do hate SCRUM, each and every time it didn't work for the exact reasons listed in this article. I'm glad someone wrote this article, it adds weight to the proposition I will make to my boss

Well, in my agency, we do a lot of user testing (I mean, there is rarely a project without user research and testing).

My recommendations for one-to-one interviews would be : 6 is the extra minimum, 8 is nice and 12 is actually the maximum. above 12, you will rarely find anything interesting or unheard before. most of the time I try to do around 6 to 8 people of the target audience.

of course, it depends of the maturity of the project and what you want to test. Is it the overall flow ? is it tiny graphical details ? or is it information architecture ?

I like the idea of Luca to make rounds of 5-6 testers, it should return interesting things. (Also, if you want to do A/B testing, as many users as possible would be a must !)