Reading time: 1 – 2 minutes

So here’s the deal: I’m going to SXSW this year and hopefully giving a talk with my friend @unruthless. She’s the genius developer/designer and I’m the awesome designer/developer and we will hopefully be giving a talk titled: “Connecting Concept to Code: Tips for Designer/Developers”. We will be exploring the why’s of design and connecting them with the how’s of code. We’ll cover all the fun stuff like web typography, colors on screen, webpage visual hierarchy, grid systems, and making the logo bigger (it’s Texas right?). Read more about our panel over at the SXSW Panel Picker site and consider giving us a vote if the topic peaks your interest!

Thanks!

Reading time: < 1 minute

In this quick tip I’ll show you how to add some subtle texture to make your designs a bit more realistic and earthy.

Reading time: 2 – 2 minutes

This past week I had a chance to speak at the Front-End Design Conference down in steamy St. Petersburg Florida. I had a great weekend that included meeting tons of awesome people, lots of tasty drinks, salsa dancing and plenty of air-conditioning.

My talk was titled “Design is in the Details” and it went pretty well even though I was nervous. I made sure to include lots of good design guidelines in my talk as well as jokes and lots of plaid references. You can take a look at my slides below. Not sure if anyone got a video or audio recording of the talk.

Also just wanted to say a quick thanks to everyone that helped put the conference together, the speakers and all the attendees! You guys are AWESOME!

Reading time: 1 – 2 minutes

I feel pretty comfortable talking about design in most situations. I love critiquing and offering design help, writing blog posts and sharing my design knowledge. One thing I’ve never done is speak in front of a group of people. Blah blah blah everyone has a fear of public speaking blah blah blah, myself included. But this time I’m doing something about it and kicking that fear to the curb.

I’ll be speaking at the Front-End Design conference on July 23rd in St. Petersburg Florida. If you are in the area take the day off and come on out! If not stay tuned – I’m sure there will be a video of me rambling about design and plaid after its all over. If all goes well I’ll (hopefully) have another talk lined up down the road with my super awesome developer friend @unruthless at this small little gathering in Texas. *crosses fingers*

So I just wanted to challenge you guys to grow a pair and do what scares you. This is the only thing that will push you to grow.

Reading time: 4 – 7 minutes

I’m sure we have all had experiences with P.I.T.A. clients before. These types of clients require lots of meetings, phone calls, emails, special attention and hand holding. If you aren’t prepared for the time commitment, these clients can blow through the alloted hours in a design budget faster than I can down a Red Bull. I’ve had some interesting experiences with these types of clients and have some tips and suggestions that will make the client designer relationship much smoother.

1. Explain your work process

Often times P.I.T.A. clients have never worked with designers. They are likely to be unfamiliar with the typical design workflow. Take the time to write out your work process and explain what happens when, so nothing comes out of the blue. This also helps preempt the millions of questions that are surely going to be flung at you at some point.

2. Set and Assign Project Milestones

Along with explaining your work process – its good to have project ‘milestones’. This way the client has some expectation of what will happen when, and who is responsible for it. These dates do not have to be set in stone. Having a plan for when things are going to happen is a good idea and reassures the client. Also assign responsibility for milestones so it is clear who is responsible for what.

Side-note: I use Basecamp for project management and setting project milestones are a great way to represent these deadlines visually.

Added bonus: Basecamp emails the person responsible for said milestones 48 hours before they are due. Just a handy little tool to nudge your client into getting that elusive web copy finished!

Common milestones (and responsibility) for my web design projects are:

• Client survey – client
• Initial call – designer
• Site-mapping & wireframing – designer
• Content creation – client/copywriter
• First Round Design – designer
• Initial Design Feedback – client
• Endless Rounds of Revisions – designer
• Coding – designer
• Testing – designer
• Soft Launch – designer
• Post Launch bug reporting/fixing – client & designer

3. Add Additional Hours to Your Budget

Time spent in meetings, talking on the phone and writing emails is time working on a project and should be billed for accordingly. I usually budget a certain amount of hours in a project to account for this. However, P.I.T.A. clients require more personal attention, more explanation and face to face meeting time.

Include these hours in your initial project estimate and be honest about what they are for. Explain to the client that these hours will only be billed for if the time is used. This lets the client know that your time is important and they are less likely to take advantage of it knowing that they are paying for it. Now this isn’t to say that you need to bill for every second talking to the client – I usually let small things slide, but I try to bill for planned meetings, conference calls etc.

4. Explain Technical Details in Writing

Often times clients are much less technical than designers and developers and thus have a hard time understanding the jargon we throw around. Its always a good idea to explain any technical details in writing. This can be an excellent reference for the client after your initial discussion. This should also prevent having to explain things over and over again because you can simply reference your written documentation.

5. Remember to Breathe

Dealing with P.I.T.A. clients can be REALLY frustrating at times. Its always good to step back from time to time and take a deep breath and take a break from the project. The same goes for the client. Sometimes postponing things for a day or two can help you perspective and clarity on a project.

6. Last Resort: Fire The Client

If things get REALLY bad there’s always the option of ending the project early and severing the client/designer business relationship.

This comes at a price. The client will probably want a part or all of their deposit back (depending on how much of the work has been done). It’s always good to be honest with clients when doing this. Let them know this isn’t working out, the project is requiring more hours than you have available or budgeted for, or the business relationship isn’t working. Nothing personal – wish them the best and recommend them to another designer or developer. Try to end things on a good note and avoid burning bridges.

*P.I.T.A. stands for pain in the ass. Don’t get me wrong – designers need clients and clients need designers. I respect all my clients, but sometimes you just have to have a funny term for annoying clients

How do you deal with P.I.T.A. clients?

Share your tips, suggestions, and/or horror stories in the comments or follow me on twitter and discuss!

Reading time: 1 – 2 minutes

I recently participated in Meredith Marsh’s Business card exchange and received a CRAPTON (yes thats a scientific value) of cards. I’ve picked out the cards that caught my attention and talk about the design traits that make them stand out from the crowd.

How Does Your Business Card Measure Up?

What did you do to make your business card stand out and have some impact? Post a link to your design and let me know what you did and why you did it.

Reading time: 2 – 3 minutes

Design from different perspectives is a series of short video interviews detailing the different kinds of jobs and environments that are available to designers and the pros and cons of each situation. In this video I chat with interview Chad Engle about his experiences working as a designer at an advertising agency. Stay tuned and grab the RSS feed for more interviews with other freelancers, creative directors, in house designers & more!

More About Chad

Twitter: Chadengle
Website: thechadengle.com

I am a designer & creative consultant. I work on projects large and small. I am also the editor for Fuel Your Creativity.

I created a little thing called Design Community Twitter Hours which, would not be possible without several people. I spend most of my time designing and creating. I try to find interesting and creative things on the web as well as apps that are well designed and fun to use.

What do YOU think?

Do you work at an advertising agency? Wish you could? Want to be interviewed? Feel free to chime! I’d love to hear your take on some of the same questions I asked Chad!

Check out the other videos in this series

Design From Different Perspectives Part 1: Kevin M. Scarbrough – Freelance Designer

Design From Different Perspectives Part 2 – Stephen Olmstead – In House Designer

Reading time: 2 – 2 minutes

Design from different perspectives is a series of short video interviews detailing the different kinds of jobs and environments that are available to designers and the pros and cons of each situation. In this video I chat with interview Steven Olmstead about his experiences working as an in house designer and freelancing on the side. Stay tuned and grab the RSS feed for more interviews with other freelancers, creative directors, in house designers & more!

A Bit More About Stephen…

Twitter: @sonatacreative
Website: Sonatacreative.com

Check out the other videos in this series

Design From Different Perspectives Part 1: Kevin M. Scarbrough – Freelance Designer

Design From Different Perspectives Part 2 – Stephen Olmstead – In House Designer

Design From Different Perspectives Part 3 – Chad Engle – Agency Designer

Reading time: 2 – 3 minutes

Design from different perspectives is a series of short video interviews detailing the different kinds of jobs and environments that are available to designers and the pros and cons of each situation. In this video interview Kevin from Robot Monster Ghost shares his experiences on the the good, the bad an the ugly of freelancing and running a small studio. Stay tuned and grab the RSS feed for more interviews with other freelancers, creative directors, in house designers & more!

A bit more about Kevin…

Twitter: @RMGco
Website:RobotMonsterGhost.com

Kevin’s Scarbrough in 2 paragraphs or less:

I’ve designed for a steady diet of unusual clients (a fashion designer in Italy, a Bolivian wine bar, a New Zealand boat manufacturer, a Russian hosting company, etc.). I’ve learned project management the hard/best way.

I’ve hiked to the bottom of the grand canyon, I briefly owned a snarky t-shirt company based on mad science, I helped set up a rave to raise money for Unicef, as a kid I used to try to improve ads on the radio and TV, and on vacation I make up wild stories about who I am.

What do YOU think?

Do you freelance full time or run a small design studio? Wish you could? Want to be interviewed? Feel free to chime! I’d love to hear your take on some of the same questions I asked Kevin!

Check out the other videos in this series

Design From Different Perspectives Part 1: Kevin M. Scarbrough – Freelance Designer

Design From Different Perspectives Part 2 – Stephen Olmstead – In House Designer

Design From Different Perspectives Part 3 – Chad Engle – Agency Designer

Reading time: 3 – 4 minutes

Nick Snyder recently sent me an email with a question he’s been dealing with at his full time job. “Is it ok to show and code unused designs in your portfolio” I thought answering the question here in order to shed some light on this frustrating topic and hopefully help others out as well.

Niki,

Thanks for your time and keep up the sweet tweets
—Nick Snyder

Hey Nick –

Thanks for emailing me and asking. I’ve definitely been in your situation before and understand the frustration of dealing with designs that veer away from your original intended design (thats a huge topic to address in itself!). The first thing I would do is ask your employer about showing work in your portfolio. You have every right to show the work you’ve done, but its always nice to give them a heads up and credit where the work was created. I would even bring up showing the first round designs. If they are ok with it you are in the clear and everyone is happy. If they aren’t ok with it you could just show them during an in person interview – or on a special portfolio page that isnt public.

I would also say that showing the first design and then showing the coded result isnt a bad thing. I’ve seen situations where a designer shows their intended design but then notes that the live site has been altered by the client or they host their coded version of the site. Again I would ask/inform your employer of what you want to do just to be in the clear. Most design agencies or even those that work with designers understand that things change and clients don’t always give the best design direction.

I hope that answered your question Nick – thanks again for asking!

Do you show unused designs in your portfolio?

What would you do in Nicks situation? Have you been in this situation yourself? Leave a comment and let me know what you think!

Also – if you have a design question you want answered feel free to shoot me an email and ask away!

Photo Credit Pak Gwei