Sketch Meetup, and how to talk to clients.

So, I recently got the opportunity to talk to local designers, developers and other freelancers in my City. After I posted my portfolio on a local Facebook group. I was approached by one of the admins to be part of the speakers for the event. I haven’t tried speaking in front of an audience, but since I told myself that 2018 will be the year that I will try to do new things. I obliged.

 

One of my talking points is how to talk to clients, and how it has helped me when freelancing. Here are some tips that has helped me as a freelancer. Made my life easier, and improved, and fostered my relationships with my clients, and how it helped me improve my craft.

Talking with authority

You are the professional. You are the one getting paid. You should have the confidence that you can deliver the product that your client has paid for. Thinking that you are the best designer in the world (obviously you’re not, and no one is) will convince your client that you are worth it. Obviously you have to back this up with the product that you are delivering. That brings me to my second point:

Always work on your craft

I try my best to have my workload be full every week, but in times that I have some downtime. I improve my design skills. Read up on best practices, and follow what other designers are doing, and maybe steal their ideas. There are a handful of websites where you can see other designers work, and get inspiration from:

  1. http://dribbble.com/
  2. https://www.behance.net/
  3. https://www.awwwards.com/
  4. http://alistapart.com/

Good designers copy, Great designers steal.

I usually work on small, to medium freelance projects, and there is a caveat with working on small sized projects. You have no access to big data, and budget. You cannot do very in-depth UX studies because the deadline, or sometimes the budget just isn’t there. One way to fix this is looking at BIG websites and following them. When you think about it, they have psychologists, UX professionals, and access to analytics that help them come up with an interface that works best.

I recently worked on redesigning a dating website, and the goal was to improve search filtering for users. The deadline was fast approaching, and we didn’t have the budget to do deep UX research.  So I went to a rivaling website (okcupid), and followed how they did their search filters.

This method fixes a couple of things:

  1. You now have UX that a big company, with big pockets has done research for
  2. More time to work on other stuff that you, and your client needs to get done.
  3. Your life is now easier.

 

Obviously you still have to add your personal flair to the interface to make it “your own”, but now you have a working product.

Don’t be afraid to say NO.

There are times, where I have to work on something that I have no idea where to start. It might be a different industry, a different tech stack, or the aesthetic that your client wants is not your forte. Be honest to your self, and to your client that you have a somewhat limited experience in that field BUT, you will do more research on it, and will do your best to learn, and be ready for the project that you will be working on. This will convey to your client that you are willing to set aside time to study the product that you are working on.

You are not an employee

A lot of freelancers think that since the client is paying them. That they are now suddenly an employee. Personally, I think this is wrong. A contractor, and a client is a partnership. No one is above each other, since at the end of the day. your goal is the same. You have to set boundaries that you have your working hours, and that you cannot answer right away, etc. Or that feature that he wants you to work on pro-bono should be paid as well.

Prevent scope creep, and requirements should be written in stone

Before I work on a project, I always make it a point to have a list of items that needs to be done, a certain deadline that they want to reach, and the number of revisions that I have to do. This will save you a lot of time (money), and headache in the long run. You have to set expectations at every start of the project. This will make your client happy, and you at the same time.

Ask for a downpayment

This is one of the best tips that you can use as a designer. BEFORE I start working on a project, I always ask for a 50% initial down payment, and the remaining 50% on completion of the project. This serves multiple things.

  1. You are already for before you start working $$$$
  2. Clients will respect you more, and value your time more since they already paid for it. They are more invested to the process. Its a commitment for them. You are not just an email address that they are talking to. Cancelling the project would result in a loss of that money
  3. If the project is big enough, and you need more people to work on it. It can cover subcontracted help.
  4. Deposits minimize the chance of non-payment. Basically that. For example, you have already wasted 40 hours a week for 3 weeks on a project, and at the end of the day, the client doesn’t want to pay. You’re shit out of luck since you are in your city, and he is halfway around the world.

Conversational English

Just like the software that we are using. Be it Sketch, Photoshop, Adobe XD, or whatever. That’s all useless if you cannot talk to your client. Being able to converse in their language is a big part of them trusting you, and conveying to them the confidence, the idea, and the process that you are about to do.

And here are some pictures of the talk:

Responses

Show form

Leave a Reply

Your email address will not be published. Required fields are marked *

  • Oh_Lightbulb says:

    It’s not bad. Decent, if basic info. But I’d say it’s fairly good advice. I’m an editor, so I looked at it with a critical eye. Couple of things: I think that the pics are too big. I don’t want to have to scroll too much to get into the meat of it. Maybe thumbnails so I can choose what to look at? Also weird white spacing at the top. Then, inconsistent spacing between the titles and the paragraph, then again at the next paragraph. Use parallel structure for your subheads. And really, ALWAYS think parallel structure, I just noticed a few subs were off. Also inconsistant punctuation in the subs and no capitalization. There is a period on one of the subs. And you should really use headline-style capitalization. Here’s a helpful site: https://headlinecapitalization.com/ Many uses of passive voice and adverbs. Adverbs signal weak writing, avoid, avoid, avoid. I found one double space in the copy. There are a few sentences here and there that have no subject or are incomplete. It might sound OK in casual conversation, but in writing, it is jarring and looks bad. Some of the structure and word choices made me think English is not your first language, If that’s the case, well done! Your writing in English is amazing. If not, work on your writing. If that makes sense.

    I’d like to see a tighter intro with no extraneous stuff or fluff. Tell me what you’re going to tell me and get to it or you’ve lost me. https://writingcenter.unc.edu/tips-and-tools/introductions/

    Also, there is no conclusion. You sort of just stop writing.
    This is a weakness of mine too. I’ve been trying hard to write better conclusions and CTAs. https://adespresso.com/blog/call-to-action-examples/ (Notice in that article the really good intro and subheads?)

    I think that’s it. I hope I don’t sound harsh, I don’t mean it like that at all. Just editing. 🙂 Keep up the good work! (Call to action! BOOM!)

  • Houstonpersker says:

    I would consider an image slider or thumbnail solution for the bottom portion that is all pictures.

    I know you asked for feedback on your post, but… I like how clean your website is it has a very minimalist feel. I am of the opinion that your menu might be over-designed. Those two empty boxes below “About” and “UI UX Projects” make it feel unfinished.

    I do like the action the menu has when it expands across the screen from the left. Solid website.

  • cocoakit says:

    Thanks for the reply. It’s very informative, I especially appreciate all the links.