Hello Arthur,

To quickly answer some of your questions — I used to work 60–80 hour weeks in the first few years. That led me to being incredibly fast at what I do (both thinking / problem solving and actually moving rectangles around) so now I work between 30 and 40 hours and accomplish the same as I did doing 60–80.

But also I don’t mean ONE person should do everything — that would lead to some biases and preconceptions. It’s best to have a 2–3 people in the team. My point was that they should all have more-than-good knowledge of all fields. Someone can be better at research, some other person at UI’s.

But having people who DON’T understand design and only talk and “ideate” cripples processes.

The wireframe and checkout example is one that comes from a real life situation — a guy that’s good at talking but horrible at actual problem solving did a wireframe just like that, scribbled poorly on a piece of paper. To place the checkout on the top right you seriously don’t need a wireframe as it’s pretty common practice.

My point is that people should acquire more skills from around what they do at a minimum of “quite good” level. Not “good enough”. Because if everyone speaks the same language the team can simply do better work.

So that’s awesome that as a researcher you taught yourself Sketch and Figma. This is exactly what this article was trying to accomplish :)