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.


Sha said…
You could give Folyo a try:

It'll get you better designers than that, I can promise!
PJ Brunet said…
The last image you posted could be fixed, the big problem is see is the teal/gray (doesn't fit) I'd say change the hue on that or just drop the saturation and take it to gray if you're feeling lazy. When in doubt, drop the saturation on colors that stand out too much. It's probably the #1 sign of a newbie designer: too intense colors. If you're squirting color right out of the tube onto the canvas without mixing, please pass me some sunglasses ;-)

Mastering color really takes work and it's definitely time consuming--very few artists have the time/patience for it. This is why I often work in charcoal and ink washes--working in color takes 50x longer but I don't see 50x the profit. Choosing colors for the web is easier, but the economics is the same. Easiest way to go, like you're saying, just match everything and go monochromatic. Statistically most people like blue--that's always a safe bet ;-)

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!

Code versus Configuration

At Ethos we are building a distributed mortgage origination system and in mortgage there is a lot of different user types with processes that vary depending on geography.  One of our ongoing discussions is about how much of the logic resides in code vs. being in a workflow system or configuration.  After researching this topic for a bit, I have arrived at a conclusion that the logic should live outside of code very infrequently, which might come as a surprise to a lot of enterprise software engineers. Costs of configuration files and workflow engines First thing that I assume is true is that having any logic outside of the code has costs associated with it.  Debugging highly configurable system involves not only getting the appropriate branch from source control, you also need to make sure that the right configuration values or the database.  In most cases this is harder for programmers to deal with.  In many FinTech companies where the production data is not made readily acce

Intuitive Programming - Comments

Comments are a topic of vibrant discussion.  Ever since programmers could leave some text in the program that was ignored by the machine the debate started: “what’s a good comment, what’s a bad comment, why comment?” There are endless instructions to programmers that say many of the following things: 1) Describe your function! 2) Don’t write in the comment what you wrote in the code. 3) Tell people why you are doing what you are doing. What I think has been missing from this discourse is the audience for comments and through those audiences there is intent.  The code is being read, skimmed or analyzed by people and tools.  So what are the audiences and reading modes? 1) Maintaining and enhancing the code 2) Skimming through the entire module or file to figure out what the overall structure is 3) Reviewing the test files to check out the test coverage and edge cases 4) Seeing the docstrings of functions while being in a separate file altogether 5) Reviewi