About 80% of the accounts I follow on Twitter are UX related, and this is giving me another big reason to do regular Roundup posts. There’s so much to wade through and there’s no way I can keep a list of the (ostensibly!) important stuff in my brain. I’ve also had a couple setbacks in my pursuit of the most effective plan to keep up with the field:
- Our Breyta Talks (monthly seminars led by a member of the UX team focusing on something cool/innovative/important in the field) have floundered at work since “work work” has seriously picked up
- I never heard back from anyone at UX Mentors. This one is especially disappointing because I’m a true believer in the benefits of mentorship, and more specifically hands-on experience with an expert!
I’m feeling good about the Roundup, though, so here are a couple things I’ve come across:
I’m always on the lookout for lightweight yet readable fonts (attractive, modern design + user experience = success), and recently found Lato. I changed my body text to Lato, but the difference may be so minuscule that it’s imperceptible (except to me). I’m ok with that.
A tech recruiter recently asked me if a “Researcher” is the lowest level in a hierarchy of positions at a UX design + dev firm. “So, researcher > designer > developer > director, is this correct?” Not only is this very INcorrect, it’s also pretty offensive. I graciously set the record straight and tried my best to convey that each position (and phase in the project lifecyle) is equally important. However, the truth is that many projects and firms do not have the budget or resources to prioritize each equally, and the discrete job titles and phases become blurred. Sometimes the director or even the designer has to do the bulk of the discovery/research work, and sometimes the developer has to do design work. Someone who excels at both design and development is called a unicorn, and thus not a real thing. However, these situations still occur on a regular basis. In my former life as a developer, I was in charge of interacting with clients to understand what they need, developing what they need, and providing tech support when they came across problems. If we’d had the budget to do research, several design iterations, and maybe even some support documentation, our user satisfaction would’ve been through the roof! I am candidly admitting to you that that was not the case. Anyway, here’s a great article that describes some tips for addressing all the phases (but mostly research) when time, resources, or human beings with diverse skill sets are scarce.