New York, NYUSA
June 25, 2012
As UX juggles the big ideas and tactical sprint objectives, juggling the right priorities can be a challenge. I'm most interested in the methods others have used to prioritize objective per breakpoint. I'm also interested in the underlying technology, too. I spent a large amount of my career in front end web development, and I pride myself on understanding the mediums I design for. What are the technical challenges our front end developers will go through, and how can I, as the UX designer, help mitigate that?
We are just employing RWD in our organization, so we will not have a lot to share. I think the best insight I can give would be around rallying your troops. We convinced a very large group of stakeholders that this is a good idea. Most people responded to the ad revenue we'd gain in a mobile solution, but others found the idea of being cutting edge very appealing. Given that I am at a company that does content creation for both print and digital, it's essential the company portray a new cutting edge persona online.
While I'm new to RWD, The Boston Globe example is the one everyone points to. We are not trying to be anywhere near that ambitious at first– we're going to roll out far fewer break points at first. But being responsive, layering in new breakpoints later will be easier than with traditional static layouts.
I would like to meet others who are tackling this problem in the publishing industry. I'd like to share concerns, thoughts, and ideas. I'd especially love to learn from those who have completed projects. What did they find were the project management and UX issues that caused the most grief?
I'm a UI / UX expert in the New York City market, working for a large content publisher after a very long stint in desktop, mobile, and embedded software. I have a BFA in Graphic Design, starting my career in visual design and front-end development.