Most of the laid-off designers were either senior or lead designers, had been with the company for 2 years or more, and were high performers. One-fifth of them think that getting laid off was retaliation against them and 72% don’t believe that “overhiring” was the real reason for the layoffs.
Why did you quit your last job? This was the main question in my recent study I did with designers. I received 156 responses to my survey, most of them were from Product/UX designers, second and third in number of responses were graphic designers, and web designers.
I'm so excited, the book is finally all I wanted it to be from the start. I also launched an updated website with it, so I'd love to hear your thoughts about it and about the book if you decide to buy it. Cheers!
Yup, that's a great point. This article is based on a chapter from my book but this is chapter 6 out of 13 already. In earlier chapters, I discuss how we need to know the content, the goals of the text and what are the user's goals (read, skim, search etc.). Of course, we can't be 100% sure on their goals but we can take an educated guess based on the content we're designing with. Decisions like these should be based on that (+ personal preference of course).
That's ok. I actually wanted to include such note about the units in the first place but forgot (in the book I use REMs and pixels only as fallback but changed to pixels in the article for simplicity). Your comment reminded me to add this note in. And I know how frustrating it can be when working on typographic details on the web. Are you having any specific problems?
You're right about the pixels. I used them because the examples set in pixels are the easiest to understand. I added a note that outside of these examples, the units used should be EM or REM. Thanks for the feedback!
Hey, Matej here, I'm part of the UX team at GitLab. I understand that it can look like we don't spend much time polishing the user interfaces and experiences that much but I can assure that we do. We don't have a split in % on how much time we should spend polishing existing things but maybe it's something we should consider doing.
Our application covers the whole DevOps lifecycle which means it takes a lot of effort to upkeep existing and constantly ship new features, but we always strive to do our best.
Thanks for the feedback, I think it will trigger internal discussions on how much time we should spend polishing existing features and experiences.