Since my agile design process presentation last summer, I’ve been constantly refining and iterating my design process. It’s evolved to include more Photoshop design—sometimes my brain just works better in the tool I’ve used for the past 18 years. But I still want to avoid having to build 50 Photoshop comps before a line of code gets written.
I still make a lot of wireframes—especially for sketching out how content needs to behave at different mobile breakpoints. Sometimes I use Balsamiq, sometimes I use a template I created for the Divi theme, and sometimes I sketch on the back of a printout. It doesn’t really matter, as long as I have a quick way to let the developer know what’s going on in my head.
My web design style guide has evolved the most
I’m pretty particular about design (OK, I’m extremely OCD), and I’ve written my own code for most of my career. Now that I partner with talented developers, I need a way to communicate all of those picky little details without constant emails and hovering and micromanaging. I’d like to continue working with them, so none of those are an option, lol! That’s why I create pretty extensive web design style guides that spell out all the teeny little details that I care about in black and white.