I recently came across a fantastic article about why it’s so important for decision makers on a project to be present during project meetings and design reviews. The author of that article relives some of his past difficulties in tracking down decision makers and offers the stern advice to cancel a project review if the decision maker can’t make that meeting.
While reading through the article (which was funny, so you should read it), I was reminded of my own project experiences in which a decision maker wasn’t brought in at the right time. Whether you’re in-house or working at an agency, you’ve probably experienced this problem and felt the impacts on the project.
I’d love to know: What things have you done to help mitigate the effects of decision makers not being in the right meetings at the right time?
Beautiful and free? What more could a designer ask for?
Along my journey to becoming a better UI/UX designer, I was introduced to the (what I would soon discover to be) crazy world of mobile app design. Getting to know the design guidelines for the different platforms resulted in a sad realization that software teams oftentimes put too much emphasis on the features list and not enough on the delight that those features could bring users.
I critiqued Zurb.com for a Bloc.io course assignment. Zurb is awesome, but here’s what I had to say about its homepage animated hero, a design trend I hope soon fades away.
This week marked the halfway point of my time in Bloc.io’s UX/UI Design program. At the beginning of this thing, for some crazy reason I had it in my head that I’d be able to give a week-by-week replay of my journey to becoming a better UI designer. I sorely underestimated not only the work that’s required of any full-time student but also the sheer volume of new things I’d cram into my brain. Here’s some of what I remember of my first 6 weeks transitioning from just a plain ol’ UXer to a more well-rounded software creator. Continue reading…
This week in my Bloc.io program, I was tasked with making the landing page I’d created for a fictitious SaaS product more responsive. For years I’d known about responsive design and media queries but never really dug into how it all actually worked. After taking my first stab at responsive design, I’ve realized four key things that I’ll remember on my next responsive project.
I’ve been working in the UX field for almost 8 years now. Over the past three or four years, I’ve gotten deep into the SaaS world. Less than a year after starting to work at a educational technology (edtech) startup, I’m leaving my job to go back to school….to learn how to become a “unicorn.” I’m hoping that my story will inspire others to take a leap of faith to follow their gut (at the very least, you’ll know why I left my job).
Ask users what they want.
Don’t ask them what they want or what they would do, watch them…listen to them…and then put the pieces of the puzzle together.
Respond to usability issues with, “Training will fix that.”
Why waste time training when we could do it right in the first place?
Prescribe implementation to a design problem.
Focus on the user need. Let UX and dev focus on finding the right solution to address the problem.