"technical" ux design
DESCRIPTION
Slides from a presentation given to the User Experience Design Immersive class at General Assembly. The conversation focused on the following topics: 1) should designers know how to code? 2) should coding be part of the job? 3) what should a designer know? HTML/CSS? Ruby/Python? CMS? E-commerce platforms? 4) how does a designer go about picking up these technical skills?TRANSCRIPT
make it better
Designing, Technically
prepared for ga uxdi
On being a “technical” designer
make it better
Should designers know how to code?
designing, technically
prepared for ga uxdi
tweet @skotcarruth
make it better
Should designers code?
designing, technically
prepared for ga uxdi
tweet @skotcarruth
make it better
The Upsides
prepared for ga uxdi
designing, technically tweet @skotcarruth
make it better
The Job Market
• “Highly proficent in building prototypes in HTML+CSS+JavaScript.”
• “First, the individual will need a broad skill set that includes UI/UX, visual design, and, ideally, frontend implementation in HTML/CSS.”
• “Comfortable coding in HTML/CSS for responsive web and email design”
• “UI/UX Designer and Front-end Engineer”
designing, technically
prepared for ga uxdi
tweet @skotcarruth
make it better
Gauging Feasibility
• How long will this interface take to implement?
• Can we even add this feature to our existing system?
designing, technically
prepared for ga uxdi
tweet @skotcarruth
make it better
Prototyping
• HTML prototypes can represent interaction better in tests
• Responsive prototyping
• Templating can make it faster and less tedious
designing, technically
prepared for ga uxdi
tweet @skotcarruth
make it better
Chipping In
• Don’t send a design that’s impossible to code
• Get in there and close some tickets!
• Smaller teams == broader individual skill sets
• Inside jokes
designing, technically
prepared for ga uxdi
tweet @skotcarruth
make it better
Creating Efficiencies
• Why pay two if one can do the job
• More consistent vision
• Less documentation
• Less “telephone”
designing, technically
prepared for ga uxdi
tweet @skotcarruth
make it better
Understanding systems
• Interaction design usually implies interaction between:
• the user
• the system
• Real companies and processes are complex
• Underlying software very likely has inherent limitations
designing, technically
prepared for ga uxdi
tweet @skotcarruth
make it better
The Downsides
prepared for ga uxdi
designing, technically tweet @skotcarruth
make it better
Unrealistic Expectations
• “UI/UX Designer and Front-end Engineer”
• You can’t be an expert at everything
designing, technically
prepared for ga uxdi
tweet @skotcarruth
make it better
Some people can play the piano and the banjo, but when they play them both at once it
sounds really crappy.
prepared for ga uxdi
designing, technically tweet @skotcarruth
Roger Belveal
http://www.quora.com/Why-dont-more-designers-code
make it better
UX is increasingly complex as it is
• More and more platforms to design for
• Users are less and less tolerant of poor UX
designing, technically
prepared for ga uxdi
tweet @skotcarruth
thanks to Sagi Shrieber https://medium.com/@sagishrieber/why-designers-should-not-code-anymore-5fc3f7d5510d
make it better
It can change your thinking
• Conway’s Law
• “Implementation Model”
• Optimizing for the code vs. optimizing for the user
designing, technically
prepared for ga uxdi
tweet @skotcarruth
thanks to Wayne Greenberg and Josh Seiden http://www.waynegreenwood.com/unicorn-shmunicorn-be-a-pegasus/
make it better
A threat to the profession
• The Great Unicorn Quest
• Devaluing “pure” design
designing, technically
prepared for ga uxdi
tweet @skotcarruth
make it better
When you know the constraints of your technologies, you can save
clients money and make your developers happy.
prepared for ga uxdi
designing, technically tweet @skotcarruth
make it better
Technical Documentation
designing, technically
prepared for ga uxdi
tweet @skotcarruth
make it better
The more technical you are, the less documentation you need.
prepared for ga uxdi
designing, technically tweet @skotcarruth
make it better
If you are very technical, you can provide insight to developers
in your documentation.
prepared for ga uxdi
designing, technically tweet @skotcarruth
make it better
What is helpful to know?
designing, technically
prepared for ga uxdi
tweet @skotcarruth
make it better
Basic Markup
prepared for ga uxdi
designing, technically tweet @skotcarruth
make it better
On-the-job Learning
prepared for ga uxdi
designing, technically tweet @skotcarruth
make it better
Popular CMS’s
prepared for ga uxdi
designing, technically tweet @skotcarruth
make it better
Popular E-commerce Platforms
prepared for ga uxdi
designing, technically tweet @skotcarruth
make it better
Mobile SDKs
prepared for ga uxdi
designing, technically tweet @skotcarruth
make it better
Database Design
prepared for ga uxdi
designing, technically tweet @skotcarruth
make it better
How do I learn?
designing, technically
prepared for ga uxdi
tweet @skotcarruth
make it better
Where to learn
• Pair with programmers (or ask for feedback)
• RTFM
• Treehouse, Lynda, Code School, Codeacademy
• GA
• Just play with stuff
designing, technically
prepared for ga uxdi
tweet @skotcarruth
make it betterinternal only
Questions?