Skip to main content

Using Offshore Designers

I am working with a new design firm and this time to save some cash I decided to go offshore.  The guys I am working with right now are in India and I seriously think they don't get it.

In 2001 I had an offshore project management firm and we had partners in India, Belarus and Ukraine.  Honestly all of them sucked.  The best offshore designers we worked with were in Argentina.

I can already hear a bunch of voices complaining about generalizations, however I am not the only person to notice this.  Today I decided to go a step further and figure out: "why is it that the guys in Ukraine or India do not wow me with their designs?"

Let's dissect this latest project and figure out what has been going wrong.  I believe it's indicative of design issues in general.

  1. the designer didn't have an overall strategy for the design.  For example: are we going to go with vector graphics, photos, straight edges or rounded edges?  A lot of those types of decisions need to be done on an architectural level and the rest of the design flows from that.  What you get in the end of consistency in the application.  Can you imagine if Facebook all of a sudden had a big round beveled button somewhere?
  2. the designer doesn’t have the confidence or the genius to suggest something innovative.  A good design is innovative enough, but familiar enough that users are not confused.

Let’s take my last project for example.  I am trying to put a new skin on the projet I created during the DreamForce Hackathon –  I gave the designers the overview of the solution and I gave them some designs I liked.  What I got back were three starting designs.

The designs were a variation on the same theme.  One of them actually mixed photographic and drawn images in a way that didn’t work.  Another one had a bunch of colors. All of them had all caps text everywhere.

I decided to give the designers more direction and wrote out the text, while pointing out all the obvious issues like – please don’t put anything in all caps and keep the colors consistent.  What came back were three variations with all caps and a color scheme of an Indian rug.

The next iteration I got one design with a bright yellow color, which is nowhere to be found in Twitter or Chatter.  So I basically decided to lay out the front page in OmniGraffle and see if I can get these guys back to something normal.

Another iteration, better but not there – repeated elements on top and bottom, again new colors appearing out of the blue and still ALL CAPS everywhere...

So what now?  Is it a language barrier?  Is it an attention deficit?  Is it that people don’t understand the value of consistency and small things?  Who knows, but I bet its not the last time I am struggling with these guys.

Popular posts from this blog

SDET / QA Engineer Interview Checklist

After interviewing and hiring hundreds of engineers over the past 12+  years I have come up with a few checklists.  I wanted to share one of those with you so you could conduct comprehensive interviews of QA Engineers for your team.

I use this checklist when I review incoming resumes and during the interview.  It keeps me from missing areas that ensure a good team and technology fit.  I hope you make good use of them.  If you think there are good questions or topics that I have missed - get in touch with me!

SDE/T or QA Engineer interview checklist from Mike Borozdin
If you like this checklist you might want to check out these posts:
Emotional Intelligence in Software Teams  and Good-bye manual tester, hello crowdsourcing!

There are Only Two Ways to Treat Your Team

There are only two ways to treat your team: take care of them or let them go.  Early in my management career there have been times when someone has been underperforming on the team.  Before I knew better I let my emotions get the best of me: I’d give them the cold shoulder, avoid including them in conversations and look like I was upset with them. Thankfully with some good mentorship I came up with a simple rule: we are helping each other or you are off the team.

One of the biggest mistakes that folks make a lot of times is letting people linger on for too long.  Hiring good engineers is hard and getting new folks up to speed is hard.  You feel like you are going to miss your product delivery plan if you let someone go.

Letting folks linger when you are unhappy with each other creates a toxic environment.  This toxic environment is generally contagious and brings the entire organization down.  Of course you can’t have a constant state of euphoria on your team, but if a productive and…

Highly Effective Software Teams

A few weeks ago our Board of Directors asked me to present my assessment of the state of software.
 I was hired to organize and grow the software team and the directors wanted to know what kind of a team we needed to build.  I was hoping that I can just reference an article somewhere that would give me the answer, unfortunately I didn’t find anything suitable. During my research I did find some great material that will be helpful if your job is to put together a highly effective software team.
A highly effective software team has the following key characteristics: dependable, committed to shared goals, passionate about technology, respectful and compassionate.  These are not limited to technology industry, it can easily apply to finance, medicine, or sports as well.  Below is the summary and references that I found. Dependable If you are creating a software product, you need to deliver your software to your users.  Your users need to know that you are able to solve their problems on …