A frontend designer (who may also go by UI developer, client-side developer, UI engineer, design engineer, frontend architect, designer/developer, prototyper, unicorn, or Bo Jackson) lives in a sort of purgatory between worlds
This is my life. I am often shoe-horned into the role of pure developer, when in reality I’m a designer that develops for the front end. Organizations that I’ve worked with in the past tend to separate the two, and this puts me in the precarious position of having to choose between them. Or those who don’t understand my skill set tend to take me with them when they need a technically minded individual to interpret and discuss a topic.
While some of this organizational separation may be justified, creating a division between designers and frontend developers is an absolutely terrible idea.
He mentions how he thinks that front end designers are particularly well-suited to bridge the divide between design and development and I couldn’t agree more. It’s a key skill set in any organization that creates and designs user interfaces.
Brad Frost is also referencing the article Development is Design.
I went to Chicago Camps UX Camp last weekend and thoroughly enjoyed the experience. From the opening keynote right on through to the final session discussing content modeling, the day was packed with information that I can bring back to my freelance work and primary job. It was a full 14 hours of driving and learning that was rather tiring, enlightening, and everything in between.
One particular talk stood out in my mind as one that I need to research, learn, and discuss with my larger team to see if implementing the methods in any sense would work for us.
Sprint, the book in all its glory.
The talk was, Facilitating Google Design Sprints, given by Zeke Binion:
Making products that customers love is hard. So giving yourself 1 week to do it sounds crazy.
But many companies spend months or years building products only to learn that their customers don’t want it. Google’s Design Sprint solves this problem by focusing a cross-disciplinary team on a clearly defined problem, empowering them to generate many creative ideas, and ensuring they are building the right product by putting a prototype in front of customers in just 5 days.
The 45 minute session was focused primarily on facilitation rather than process, but I am intrigued.
In his talk he discussed Google design sprints, as outlined in Sprint: How to Solve Big Problems and Test New Ideas in Just Five Days, and it is a process I am heavily interested in learning.
I have just received my copy of the book, so stay tuned for further process discussions.
To be clear, I am using an Amazon affiliate link to direct traffic through to Amazon. Shameless, I know. Just trying to earn a little bit of cash.