Podcast: Play in new window | Download
In this episode I talk about two things you should avoid as a Web Designer. Both things deals with how you go about completing and working on a web design project. Fixing and correcting these things will improve your web design process and allow you to have better results when designing a website.
Referneces:
Hey Mike, great podcast. I got myself in a bad spot coding a site that did not have a finished design and it was horrible.
@Zach – I’ve been guilty of this in the past and I always end up in a bad spot coding the site while designing at the same time. Not a good process.
@Ron – Yes, coding and designing is frustrating because it limits you. But focusing on design first, you can put more into it. And same when coding. You should only be concentrating on that aspect on its own.
That’s exactly what I have been doing, I found when I am coding and designing I get frustrated. I am currently creating a magazine for my company. This is so true Research, Design , code , test , execute. That’s my template on every project.
Hey Mike! Thanks for sharing this wonderful video. I myself, have been guilty of not doing enough research or writing down what I needed to create, which made me end up scratching my head when I need to get into the drill…
It was quite frustrating, but after I started to write down the things I needed to create, and gathered inspiration etc. the process went much smoother.
So once again I, thank you for reminding us the importance of the 2 points you mentioned.
Looking forward for your next podcast post.
Great podcast Mike. I’ve done this before, tried rushing the design process or not entirely finishing the design, it’s such a waste of time!
@Brian – Thanks, glad you enjoyed the topic. You said it, when you’re designs and details are fully worked out, you’ll end up scratching your head during development which will lead to delays and creative blocks.
@Richard – Thanks for the insight. Good to know I’m on point with this topic. I’ve been guilty of this a long time. I have to stop myself from falling back into rushing through things.
Great post Mike. I find myself coding while designing sometimes and it is very time consuming. Thanks for the great tips and inspiration.
I have to disagree with #1. Very few sites are exactly like their final mockups because of the limitations of HTML and CSS. Instead of designing pages, you should be designing conponents that are from a style guide to make everything consistent. I’ve started designing in the browser and it has been a great experience. But before doing anything, you should always start with alot of research and sketches. Brad Frost’s blog post “Atomic Design” (http://bradfrostweb.com/blog/post/atomic-web-design/) elaborates more on designing UI components.
Thanks for for the great podcast Mike!
Hey Mike, What about articles that talk about designing in the browser? Just wondering what was your take on this: http://uxmag.com/articles/building-a-better-user-experience-by-designing-in-the-browser
@Jay – Bad, bad, bad! :) … I only like designing in the browser after the fact. After the site is done, I’ll sometimes tweak my css directly within the browser using the browser inspection tool. But other than that, I’m always designing in static form first, then coding second. That’s the best process that have worked for me over the years.
Are you not doing the podcasts anymore? Even if you just upload the videos that you make as a podcast that would be dope!
Hey Mike,
Appreciate the videos and blog post. All your information is very sound and on point. But, I was wondering what your thoughts were on using grid systems (like 960gs) and CSS frameworks as a sort of “shortcut” to designing a website.
Keep up the good work.
I so agree! I like designing after wireframing and before coding. It makes the process so much easier and I second guess myself a lot less, therefore I finish faster.