Pragmatic Outsourcing

Tips, tricks and traps of IT offshore outsourcing

Red Flags to Watch Out For

How do you know that a relationship with your vendor is going south? Of course if all your partner’s employees just do not show up for work you know that something is rotten in the state of Denmark. That would be somewhat unusual event and probably irreversible. The goal here is to identify early symptoms of a fatal disease of deteriorating partnership. In techno world we call them red flags.

The earlier you identify developing issues with the relationship the higher the chances that you can nip it in a bud and return to a mutually beneficial rewarding relationship. Small companies typically offer a high level of transparency and short communication channels. That makes identifying issues much easier task. In large companies the issues can develop without knowledge of many stakeholders, that’s why watching the relationship dynamics is especially important for those. Read more »

June 12, 2009 Posted by | Managing Offshore Engagements | | Leave a Comment

Offshore Technical Due Diligence

A couple years ago I went through a technical due diligence (TDD) of several relatively small offshore vendors. The vendors were providing product development services for one of my clients, the vendors also supported operations of the SaaS for all of the products. The client had fully outsourced s/w product development and support to those vendors and retained practically no technology resources internally with exception of MIS / SaaS IT support.

The goal of the TDD process was to asses whether the vendors are efficient and can continue performing fairly complex projects involving working with sensitive information. There are a couple important distinctions here:

  • The vendors were in large degree focused on the product development for my client and the rest of their business was relatively small.
  • The vendors have been performing services for a number of years with very light oversight from the client’s side.
  • The quality of work to date has been on a low side yet deemed sufficient for the money.

Read more »

May 22, 2009 Posted by | Making Offshore Decision, Managing Offshore Engagements | | Leave a Comment

Laws of Nature

I just added a new post to my new blog Common Sense ManagementLaws of Nature and the Need for Management. It touches upon one of my favorite metaphors – application of the Second Law of Thermodynamics to management and offshore outsourcing (see also Fundamental Laws of Outsourcing). The message common to these posts is quite simple – you must stay on a top of your projects, resources and engagements otherwise they would quickly deteriorate.

Having said that I have to admit I should pay more attention to what I preach and follow my own recommendations. Just a few days ago I was going through a small project that seemed to be falling behind. The issues became clear in a few minutes after I walked in the meeting discussing the project status.

The objectives for the project I stated about two months ago were lost and the void was filled in by something substantially more complex (And that illustrates another law – “nature abhors a vacuum”). My offshore team was happy to work on more challenging projects, estimates appeared too high, that required in-depth analysis, more people were getting involved, more issues discovered, that generated substantial amount of R&D that increased the complexity by an order of magnitude… Involved in the meeting there were six people from onsite and almost as many from offshore.

For me, at this point an unattached side observer, it was obvious that the efforts being extended to address the project exceeded the value of it by a great margin. It was not at all clear to people so passionately involved in resolving the problem.

About an hour later it was all over. The vicious circle was broken as the proverbial Gordian Knot. The projects objectives were not only restated but addressed. It required 15 minutes from an engineer who had not been even aware of the discussion. Yet the sunk cost of the project was unrecoverable, exceptionally high and not justifiable by any means. Is there anyone to blame for it except the manager (me) who abdicated the project to those who did not have enough technical depth to cut through the distractions of secondary objectives?

Add to FacebookAdd to DiggAdd to Del.icio.usAdd to StumbleuponAdd to RedditAdd to BlinklistAdd to Ma.gnoliaAdd to TechnoratiAdd to FurlAdd to Newsvine

May 19, 2009 Posted by | Managing Offshore Engagements | | 2 Comments

Five Steps to Keeping your Vendor

I started my earlier post Five Steps to Keeping your Business with comparison of an offshoring engagement to a bad marriage: courting, expensive wedding, honeymoon, initial struggles, mundane irritation, aggravated frustration, and bitter divorce. The post touched upon the most important steps vendors should take to keep their business. Now let me cover the buyer’s side. And first let’s discuss a couple reasons for keeping your vendors. Of course if a vendor fails your expectations by a large margin there are not too many reasons for keeping that vendor, if any. If the vendor is perfect the thought of changing them is rather unlikely. (Please do let me know what your vendor is in this case, so far I fail to find one!) The question is relevant to vendors that in general deliver on expectations and sometimes exceed them and yet are in many ways imperfect, sometimes even worse than that. To some degree these reasons for keeping the vendor summarize to “Don’t fix if it’s not broken” – Read more »

May 11, 2009 Posted by | Managing Offshore Engagements | | Leave a Comment

Data Entry Gig: Execution Control

In my earlier post Notes from a Data Entry Gig I covered a few areas related to a small data entry project. There were several areas that were left untouched, one of them – execution control, is worth covering by itself.

There are many things you can do to get execution under control on medium to large scope engagements. Project/program management, account reviews, etc. That’s not the methodology to be used on a small gig such as limited scope web research, data entry, SEO, etc.

Considering that discipline and control issues associated with freelancing have to do with a lot of its Cons I was rather skeptical farming out data entry to a few gals in several small cities in Philippines. One would say “it’s a small data entry, what can go wrong”, yet you and I know the possibilities to screw it up are endless. “And then I saw the tool, Now I am a believer.” [almost from Neil DiamondRead more »

May 6, 2009 Posted by | Managing Offshore Engagements | | 2 Comments

Five Steps to Keeping your Business

Offshore teams delivered a significant portion of the products and services for the companies I worked for. My experience in utilizing offshore whether it is measured in years, number of projects or dollars sent offshore is rather substantial. You would think that by now I should have settled on a couple partners who I use on the majority of my engagements the way most VPEs settle on DB platform, app server, language, etc. Actually that is not the case due to many reasons, the main being different needs call for different partners. There is however another reason worth serious discussion – many vendors lose their clients mainly by not doing good enough of a job of keeping them. Whether you look from the vendor’s or buyer’s side that’s a shame…

escher_ascendingIt’s a common knowledge that in the service industries the cost of a dollar earned from a new customer is substantially higher than from an existing relationship. Yet for some reason that rule is ignored with unexplainable consistency. In particular I see it common with some of my offshore vendors. All too often a relationship with an offshore vendor goes through typical stages of a bad marriage: courting, expensive wedding, honeymoon, initial struggles, mundane irritation, aggravated frustration, and bitter divorce.

It takes two to tango, and being unbiased marriage counselor I should offer my connubial advice to both sides – buyers and sellers. I will, with this post focused on the vendor’s side:

  • Communication is critical element of any engagement and in particular distributed. Even two people who know each other exceptionally well and live under one roof are known to have communication problems, it’s no surprise offshore engagement fall apart due to communication problems. Communication problems have a cumulative nature, meaning that small issues accumulate and result in large scale problems. There is much to be said (and I will do that) about improving communications in offshoring engagements, for now just one critical aspect: You should establish and follow communication process. You should treat communication process as you would treat a manufacturing process. In particular consider no missed steps or other changes to the process unless you expect substantial improvement in efficiency AND the changes are agreed upon by all stakeholders. Read more »

April 30, 2009 Posted by | Managing Offshore Engagements | | 4 Comments

Notes from a Data Entry Gig

Large pool of cheap resources sometimes is enough of a motivation to outsource tasks. Sometime even those that you might not have done in the first place ;) It also is very tempting to engage manual labor rather than create, debug and use tools. Those reasons along with some business drivers were behind a data entry project I started a few weeks ago. While small and fairly simple the project offered a few interesting lessons to learn and a couple of interesting points to share.

  1. There are many places where you can find freelancers. Most of those places offer offshore labor. Even local resources such as craigslist will generate more response from offshore than from locals, even if you specify “locals only”. In my case I was specifically looking for offshore resources and the rock bottom rates. I knew that every site has its own community of freelancers, what was somewhat surprising is how substantial the difference in response would be. Response to my ad from 5 sites I tried in the first 3 days was 0, 2, 3, 6, and 78. The last figure was the response from oDesk community. It’s no surprise that the best candidates also came from oDesk. As a matter of fact I ended up to picking all providers from oDesk (I was looking for 5 people).
  2. The rates diversity was quite surprising as well. My project which was a basic internet research and data entry attracted freelancers from all over the world with majority of applicants from India, Pakistan and Philippines. There were a couple bids from USA (I frankly doubt that the work was planned to be performed by USA resources though). The lowest bid was $0.78 an hour (Bangladesh), the highest was $26 an hour (India).
  3. The quality of responses varied greatly from thoughtful and professional to “Need a job!”, the last one incidentally was one of the highest bids as well.
  4. Fit between the job and skill set was decent with a few exceptions even though I had somewhat of a difficult time categorizing my project – fitting it into one of the categories / subcategories provided by the sites.
  5. Each of the sites has its own idiosyncrasies and proprietary conventions; that makes search for freelancers across several sites rather cumbersome. In this case I did not have to work across the sites – the difference in response clearly made oDesk a better place to seek for my resources. That is not always the case though. In particular many type of projects such as web design, graphical arts, etc. would find equally strong support on many sites.
  6. For this project pruning candidates was not complex – I cut off everyone with rate above $5 an hour and those who did not appeared to put any efforts into their bid. That still gave me about 25 candidates, at that point ratings and hours worked helped me quickly pick top ten.
  7. I did not put a lot of efforts in the “Interviewing”; a quick email exchange quickly showed whether the person appeared professional and responsive enough. A few of candidates requested Skype conversations, that was a bit more time consuming and I am not sure whether for this kind of project the time is justified.
  8. I picked 7 suppliers (my target was 5). Can you guess why? Of course the quality of suppliers, especially when you scrape the bottom of the rate barrel is a hit or miss. One of them “did not show up for work” after the bid was accepted, one turned out so dense that I had to stop working with her after two days into the project.
  9. I now have only three suppliers left. All three are from Philippines and all are doing a decent job. The rates are 1.11, 2.78 and 3.33 an hour. The communications are sufficient. Productivity as expected or even better. I think so far I can call this project a success.

If you are facing a data entry, web scraping, email response, etc. project here are a couple tips I suggest for you to consider:

  1. Using freelancing sites saves time of sourcing candidates, simplifies management, and helps with payment aspects.
  2. Today the rate target could be $3 an hour plus / minus a buck.
  3. Have a very simple, concise and unambiguous project description. A step by step operating procedure should be developed. (remember the 3rd fundamental rule of outsourcing?)
  4. Do not invest too much effort in selection of the candidates; it’s easier and faster to start another project and get a bunch of new candidates than try to pick just the right ones. Using the project above as example – the candidates I thought were the best are no longer on my team, one of them was the no-show.
  5. Use the site communication methodology rather than your own email. That reduces the clutter in your own inbox and helps with categorization of email and follow up.

I guess that’s as much as this project deserves. I am kicking off  a SEO/SEM project shortly. It will be a bit different will see how it pans out and whether there is much to learn from it.

Add to FacebookAdd to DiggAdd to Del.icio.usAdd to StumbleuponAdd to RedditAdd to BlinklistAdd to Ma.gnoliaAdd to TechnoratiAdd to FurlAdd to Newsvine

April 23, 2009 Posted by | Managing Offshore Engagements | , | 1 Comment

Basics of Non-verbal Communications

I started talking about body language and non-verbal communications (commonly referred as NVL) a while ago kicking off the discussion with a picture of consummate liar. NVL is a general topic that applies across industries and domains, the reason I bring it up here is that NVL is exceptionally important during face to face interactions with your partners. The cross cultural aspect of offshore relationships introduces whole another layer of complexity to NVL, often complicating already perplexing aspects of communications. To understand it you need to have a solid grasp on basics of NVL. Crawl before you run so to say. Of course understanding basics of NVL will help you in many other aspects of communications both professional and personal.

Of course this post is only a few brash strokes on a canvas – if you find NVL topic of interest you may want to look into a few books which I found helpful. Anyway…

Body language or non-verbal language refers to conveying messages without words. We are accustomed to use common gestures which are the “words” of NVL for example nodding your head in agreement or shaking it in disagreement, facial expressions – smile, frown, disgust, etc. Many or NVL “words” are much more subtle though. They do communicate message to outside world sometimes much louder than plain words would.

In a personal spoken message according to Albert Mehrabian (Psychology Today, 1968) the total message is communicated via:

  • 7% is conveyed by the words
  • 38% by the vocal tones, and
  • 55% by facial and body expression

How about that? More than half of the message comes across via body language! Talk about the Cons of outsourcing! When you work with someone and do not see him or her the chances are you will miss half of what they are saying or it will take twice as long.

More so the body language is less controlled by our conscious mind and often radiates the true message. Just look around and you will see plenty examples of it. I started writing this post while on my way to the office in BART, as on purpose to help me with an example a couple walked in the car and sit across. The couple was having one of those discussions: her eyes were red and full of tears; they sit on the bench at least a foot apart, her fist were clinched and body pasture uptight / uneasy. He was much more relaxed and appeared in control, he was the one doing all the talking in very persuasive somewhat mechanical manner, the topic was apparently very emotional and she was hanging on his every word, looking deep into his eyes. I could not hear a word yet it was somewhat clear that he did something that had hurt her and now was explaining / asking for forgiveness. By the Fruitvale station there was no more distance between them, his arm was on her shoulders, at the West Oakland they kissed lightly, by the Embarcadero station the kiss was real, the fight was over, and the guy was forgiven. She relaxed as if the seat suddenly became 100 times cozier and looked so much happier, so did he… What she did not see during the conversation, as she was maintaining that rare unbreakable eye contact, was his body language and all classical signs of deception. For me as a side observer sings were obvious as if I was watching an NVL training tape – here is the hand to mouth move, now he’s rubbing his neck, and here goes that proverbial blinking… As I was walking out of the car I saw her happy smile. Isn’t love grant?

There are a few very important elements to reading NVL:

  • North American gestures do not necessarily represent gestures correctly in other ethnic cultures. As a matter of fact you need to make sure to read up on foreign NVL before getting involved in face to face communication with your offshore partners, innocent or positive gestures could be offensive in other cultures, e.g. infamous American feet on the table the gesture that is extremely impolite in many cultures and exceptionally offensive in the Middle East.
  • Many people can easily control what their NVL broadcasts to the outside world in an initial stage of conversation or its “static” stages. For example anyone can start a conversation with a smile, specific body position, etc. As the conversation moves along and becomes more engaging / more emotional the mind loses its control over NVL. If you are trying to read NVL pay specific attention to changes in NVL. Changes in NVL are significantly more important than “stance” or specific elements of NVL displayed for a period of time.
  • You are probably not the only one who is NVL aware. More so some people put substantial effort in mastering in NVL outbound communications and use it as powerful deception or influence techniques. For example a powerful technique taught in many sales classes is mirroring – mimicking conversation partner’s body language. Mirroring is known to increase chances of positive outcome of the conversation – closing the deal; it comes from one of core principals of influence theory; that’s a whole another topic for discussion.

Well, that probably covers the main elements of the foundation.

Add to FacebookAdd to DiggAdd to Del.icio.usAdd to StumbleuponAdd to RedditAdd to BlinklistAdd to Ma.gnoliaAdd to TechnoratiAdd to FurlAdd to Newsvine

April 17, 2009 Posted by | Contract Negotiations, Managing Offshore Engagements | , | Leave a Comment

More Thoughts on ESL

A while ago when still a student I stumbled upon a great supplemental income opportunity: a friend of mine, an editor in a science journal, was looking for part time interpreters. The task was quite simple: writing summaries of technical articles. To me my French even though practically non-existent seemed strong enough to do that maybe, just maybe, with some support of a dictionary. I stopped at my friend’s office and he handed off to me a half a dozen articles on various medical topics. I was quite flabbergasted and asked – why medical? I am a technical guy. Math, engineering, maybe software, but why medical? My friend just smiled – if I give you articles in your specialty I will only get back what you know of the subject, chances are, that everything new and or controversial will be missed, and that’s assuming that you know French well… After a few nights of checking every word in a dictionary and still not being able to put the puzzles together I decided to switch to different means of making money.

I have seen the same phenomena with many technology professionals for whom English is somewhat of a struggle. They often step back and rely on their technical skills in understanding their client needs, interpreting the information inflow, often to the detriment of the project. That in particular common for advanced ESLers. When working face to face with native speakers and not communication related misunderstandings are easier to address, non-verbal language and timely feedback are of great help in this case. When you introduce the offshore factor, the time and cultural differences on the top of language handicap communications mistakes accumulate and widen the gap in understanding. Technology professionals have a tendency to bridge the gap with things they are familiar with and make decisions on behalf of the client.

Dealing with this issue requires efforts on both sides and unfortunately there is no panacea. Trying to get every assumption documented and signed off is a recipe for a productivity disaster, leaving things up for interpretation by developers is asking for even more troubles. Many of the tools I find helpful and efficient in this case come from agile development practice, in particular short release cycles and frequent demos.

Of course learning English remains to be one of the most important tasks on the provider side. But with over 600,000 words it’s easier said than done. Classes and books will only get you a fraction of the way there. What can one do to continuously advance in that utmost important skill while keeping they day job? We take our chances and use different methodologies. For me motivational tapes from Brian Tracy, Zig Ziglar, and Anthony Robbins were the main tool not only in building the vocabulary but changing my Russian gloom and doom attitude. Some people listen to NPR some watch a lot of movies. Having mentioned that lat me share with you a story I hear from Kirill (offshore development manager for a large s/w company on weekdays and my blog reader in his spare time). He told me about a Russian developer manager who took watching movies to heart; he also combined business and pleasure and watched primarily action movies. Being very gifted in terms of language he built broad vocabulary of words and idiomatic expressions, a lot of idiomatic expressions unfortunately mostly borrowed from Dirty Harry wannabes. That did not do him particular well :( If you are working on your language skills here is Kirill’s advice –

One of my guys in St. Petersburg has outstanding English and I asked him how he had mastered it. He said that he listened regularly to free podcasts at www.eslpod.com. I checked the site out and downloaded tons (close to 5G) of historical podcasts. Topics are pretty basic, but the language they use and pronunciation is very good. I wish I had something like this when I just came over here :)

Well, as the say it’s better late than never – I’m signing up …

Add to FacebookAdd to DiggAdd to Del.icio.usAdd to StumbleuponAdd to RedditAdd to BlinklistAdd to Ma.gnoliaAdd to TechnoratiAdd to FurlAdd to Newsvine

April 14, 2009 Posted by | Managing Offshore Engagements | , | Leave a Comment

10 Offshore Deal Showstoppers

I love English and it is slowly becoming my true second language. While English is still very much a work in progress for me I think I am doing better every day. Nowadays I can even challenge some native speakers with language questions that would get them quite puzzled. For example, is a “showstopper” a good thing? Almost anyone working in IT industry will tell you – No, that’s a very bad thing. Well, it is not exactly correct – take a look in a dictionary… Anyway, I am planning on covering a few showstoppers (in IT sense of the word) that I consider a deal breakers when it comes to hiring an offshore outsourcing vendor.

1. Acting like an idiot –fighting with me, bragging, being condescending, doubting my intelligence, etc. I have seen all too often vendors torpedo themselves by acting rather shallow. Here are just a couple of real life examples:

  • “Nick, we hear it all the time… What a dumb question!”
  • “Why use Skype? We’ll set you up with the software we developed in house – it is 100 times better.”
  • “Nick, you just don’t understand…”
  • “We have the best people in the entire city of Moscow and as a matter of fact in Russia altogether.”
  • “Nick, this is so simple, anyone would understand it. Let me take you through it step by step…”

2. Lying, in particular when the lies are obvious. I typically tell to my prospect offshore vendors upfront that’s I am not a neophyte in outsourcing, yet some of them almost immediately after introduction launch into telling me how their clients saved over 300% in IT costs, about virtually zero turnover ratio, building 100+ member teams in 2 weeks, etc. These claims go beyond lying and fall in category “treating me like an idiot”. There are many areas where I see offshoring vendors commonly bend the truth a bit too far, and that why I always interview prospect employees – all kind of things came to the surface.

3. Playing games. I am not a strong negotiator and do not sell or buy for living. That doesn’t mean that I fall for every trick in the book. More so, if I recognize that a vendor is playing games with me chances are I won’t continue the discussion even without asking them to play a flute first. That is particular common and less offensive when it comes to negotiations, yet still annoying and the chances are will throw a bucket of cold water on my desire to work with the vendor.

4. Bashing competitors. Very common practice that is likely to give a vendor a single benefit – never talking with me again. Here are just a few examples from my recent past:

  • a. From a talk with a Hungarian outsourcing firm: “Nick, are you really comfortable working with Russians? You know that all Russian outsourcing companies are owned by mob, don’t you?” Obviously these guys did not know that I spent first 30 years of my life in Russia…
  • A discussion with a founder of an offshore company in Odessa, Ukraine: “Nick, are you serious about considering China? That’s just silly. I’ve worked with Chinese for years and can tell you they all dumb and lazy…” In response I told the guy that my wife was Chinese; while it is not true, that was so worth it – watching the tap dance that followed.
  • From a discussion with VP of Sales for an outsourcing firm in China talking about another outsourcing firm in China: “I know them very well, and I have to tell you working with them will give you nothing but headaches – huge turnover, very low quality of resources, practically nobody with fluent English…”

5. Showing signs of dysfunctional company. Breakdown in communications, mixed messages, process breakdowns, “right hand doesn’t know what the left hand does”, not responding to my inquiries – these are just some of the common signs of a dysfunctional company. Those signs surfacing during presales / sales process or contract negotiation stage are sure deal killer in my book.

6. Displaying signs of bodyshop. Bodyshops or/and software sweatshops are not the organizations I would partner with for many reasons: low quality of deliverables, incompetent staff, high rate of conflicts – just to name a few. The trick is to recognize it early. Fortunately, signs of bodyshop are often right on the surface. The most common is condescending attitude of sales team towards resources to be involved in delivery. Another one, a bit less obvious, is a very quick turn around on sales materials with no visible impact on sales team (bunch of worker bees in back office slogged through the night to get the drones ready for presentation).

7. Unreasonable pricing. Typically excessive pricing comes decorated with statements such as “we are not the cheapest but we are the best” or “these are just list prices and we can negotiate from here”. That approach turns a large portion of contract negotiations in a slapstick comedy which I do not enjoy. Unreasonably low pricing has a turn offs of a different nature, ranging from “these guys are desperate” to “what’s the catch”.

8. Going over my head or behind my back. Not sure whether that one needs an explanation. Doing something like that is known to be a “corporate culture crime” in any industry / environment. And yet I see it surprisingly often. The funny part is that the email sent to my boss is likely to end up in my inbox with “FYI” or even “Nick, why are thy contacting me?”

9. Applying overly aggressive sales techniques. Having been in the industry for a while I have seen a lot of them ranging from twisting arms and applying pressure or guilt to outright pathetic begging. Once a CEO of midsized Indian outsourcing company literally cried in my office begging my to give his company just one chance, he showed me the pictures of his kids and wept talking about so many of his employees to go hungry – you might think it was a scene from Bollywood tearjerker.

10. Picking a wrong tone for the discussions. That’s a tricky one as everyone has their personal preferences and pet peeves. I think you can’t go wrong by just being consummate professional in all aspects of your communication. For example, I believe that you are better off being cold rather than getting too casual too quick – “Nick, buddy, take a foot of the breaks! When are you goona sign the doc I sent you?” But maybe that’s just me…

Many of the items are not necessary related to integral components or cultural fabric of specific vendor organization. Many of these items are mainly related to sales person who represent the company and you might ask why I would stop working with a vendor just because their sales person is not the sharpest cheese on a platter? Well, there are at least few reasons –

  • Most of the time what you see during sales process is enhanced version of what will appear during the delivery stage.
  • A company that hires and uses sales staff that could be defined by one of terms is probably not worth working with.
  • There are plenty of alternatives to spending time with people who annoy you.

Add to FacebookAdd to DiggAdd to Del.icio.usAdd to StumbleuponAdd to RedditAdd to BlinklistAdd to Ma.gnoliaAdd to TechnoratiAdd to FurlAdd to Newsvine

April 8, 2009 Posted by | Contract Negotiations | | Leave a Comment

Basics of Win-win Negotiating

If you heard anything about negotiations you probably heard about win-win negotiations (WWN) as well. As a matter of fact you might have heard the term even if you never dealt with negotiations at all. It’s a very popular buzzword in business, politics, etc. But doesn’t it sound like an oxymoron? Negotiations term in our minds typically translates to two sides with conflicting objectives trying to find a compromise, what can win-win term to do with it?

Well, the first and the most important step in reaching win-win outcomes, is getting away from the cliché above. You need to put yourself in a different state of mind, and that is not that at all complex. If you approach negotiations as “two parties with conflicting objectives trying to find a compromise” that what your negotiation process would be. Negotiations in this case is very much like a sport game or a bitter divorce – there is a fixed amount of assets that could be divided between two parties. In reality most of the businesses negotiations deal with substantially more assets that meets the eye and the assets do not need to be “divided” but distributed / redistributed in some manner, more so in many negotiations new value is created increasing the negotiations asset pool dramatically. Understanding of it allows you to focus on maximizing overall value as well as the value gained by each party, and that leads you to win-win negotiations.

Going forward in this post let’s consider negotiating an initial offshore contract as the main example. Getting to a final contract signature could be a very complex and lengthy process with legal, ops and execs involved, with emotions flying high, many things going wrong, and some seriously bruised egos; that feels in matrimonial terms as a dressed rehearsal for a bitter divorce. Negotiation initial contract could be also a well organized process akin to planning session for long and complex journey.

The first scenario besides being hard on you is also almost a certain recipe for engagement failure. Let’s discuss some of the main techniques and tools that help change typical carpet trading style bargaining into professional win-win process negotiations that are easy on our nerves and establish solid foundation for the engagement success:

Put yourself in WWN state of mind:

  • First thing you need to do is to realize that there is a variable amount of resources to be divided / redistributed and both sides can “win”. Take for example an MSA, I’ve seen some that were just one page long and some over 20 pages long. They serve the same purpose and in large degree touch on the same topics. The breadth and more so depth of them is quite different with longer versions offering many more elements to discuss / negotiate.
  • Starting from early steps of the negotiations your dominant concern should become to maximize joint outcomes. Think about the process of WWN as a process of creating value. In particular search for options of providing additional value for your negotiating partner. For example if you are on a buyer side that might include references, leads, sharing development expertise, helping with building the process maturity, etc.
  • You need to get to a realization that there are many tangible and intangible benefits both parties can offer each other in addition to hard-core contract ingredients. Take for example references or leads a customer the parties can exchange.
  • Understand that the opponent’s interests are not necessarily the way you perceive them, so take the most positive view. Put yourself in your negotiating partner shoes and take the most optimistic outlook at what they may be trying to accomplish. For example, if you are on a buyer side think in terms “if I were the vendor what value I could provide to the buyer? What can I do to exceed their expectations”
  • Focus on interests, not positions, including your own. That is very important point, it is all too often we forget the goals we are trying to accomplish and get our horns locked in fighting on positions, pursuing fleeting often irrelevant objectives. Many times I’ve seen people forgetting the topic of negotiation and only striving to look good, win, prove the point, etc. Well I’ve done it myself…

You can start establishing the foundations of the WWN right after and only after you put yourself in WWN state of mind. One of the most important steps in establishing the foundations is making sure that WWN is indeed a possibility:

  • Always initially ask for more than you expect. That serves to multiple purposes, one of the most important being establishing negotiation space, which in turn helps your opponent to avoid “losing face”.
  • Look for points to negotiate and by all means avoid single-threaded negotiations. When you get to a single-threaded negotiation, or negotiating upon a single point (most common would be “the rate”) the chances of “building additional value” disappear as negotiation turns to dividing a limited amount of resources between two parties. Keep as many points open as possible till you are ready to get to the closure.
  • Get you opponent to act in WWN manner as well. Make sure that your negotiating partner understands that your position is “win-win or no deal”. Get your opponent to take same position as well. That could be not trivial and require substantial effort if your opponent doesn’t have experience in WWN or doesn’t believe in WWN.

The process of WWN is not overly complex; it’s just different from what many people consider “the right thing to do” when it comes to negotiations. In “typical” negotiations one person’s interests oppose the other’s. The dominant concern in this type of bargaining is usually maximizing one’s own interests. Dominant strategies in this mode include manipulation, forcing, and withholding information. In WWN dominant concern is to maximize joint outcomes and dominant strategies include cooperation, sharing information, and mutual problem solving.

After the parties established WWN mindset and environment the process moves towards building a partnership dealing with elements that parties have opposite interest in becomes non-confrontational collaboration rather than face to face combat so common for haggling. When you encounter a topic of that divides / pulls parties apart consider the following techniques:

  • Seek out (brain storm) mutual gain opportunities through out your negotiation process. Every turn in the negotiation offers additional opportunity for discovery and broadening the negotiation landscape. Generate a variety of possibilities before deciding what to do / how to proceed.
  • Seek objective or legitimate standard to base an outcome on, to evaluate the solution. For example Net 30 is the most common (standard) payment term in SMB environment for outsourcing contracts. Working with large organization such as government or pharma you likely have to consider Net 60, when dealing with contractors you may want to consider Net 15 or due upon receipt.
  • Build on commonalities rather than address the differences, consider “we are in this together” as the main metaphor. Sometimes to bring you and your opponent (negotiating partner) on the same side it helps to find a “mutual enemy”. For example when building a initial outsourcing contract instead of fighting around common problems such as “what if you will not deliver on time and my resources are spinning wheels waiting for you…” consider “loss of productivity” as a “mutual enemy”. That set of mind promotes by far more productive discussion and typically results in better contractual framework.

OK, the title of this post is “Basics of Win-win Negotiating”, “basics” not “insights” or “advanced techniques” and I think I am way deep in the weeds now. So, I guess I should stop now… And thank you so much if you still reading. I am afraid I lost most of my readers by now, including myself…

Add to FacebookAdd to DiggAdd to Del.icio.usAdd to StumbleuponAdd to RedditAdd to BlinklistAdd to Ma.gnoliaAdd to TechnoratiAdd to FurlAdd to Newsvine

April 2, 2009 Posted by | Contract Negotiations | | Leave a Comment

10 Annoying Things Freelancers Do to Destroy their Business

I have been working with freelancers through out my career and recently, thanks to services like oDesk, I find myself doing it more often. So you might think that I am happy with what I get, at least in general. Well, one of the reasons I continue to stay engaged is my high tolerance for pain – I am prepared to go through piles of hay to find that needle. And I have to tell you, looking for freelancers is very much like digging for gold – you literally have to go through tons of dirt to find it.

Interestingly enough many freelancers who have skills, knowledge and maybe even talent often torpedo themselves, aggressively sabotage their chances of getting customers right in the begging of the process. They make simple yet lethal mistakes that turn off clients before they got the chance to learn about freelancer’s ingenuity. Of course many mistakes could be made during execution of the project as well as its closure. I am not talking about technical or skill set issues though, my focus is on soft behavioral aspects of your communications with the client. Below are some of those mistakes:

  • Not reading my project description before replying to it. Your three page long template proposal will get in a recycle bin faster than you would think. At least adjust your opening statement, show me that you read the post…
  • Not using proper grammar and spelling. English is my second language and still a work in progress; I still struggle with grammar myself, yet many proposals I see push that envelope way too far. Grammatically poor introduction screams in my face “Communicating with this freelancer will be a real pain!” Spelling mistakes are even worse – how can I entrust my project to someone who doesn’t even make an effort to turn on a spellchecker?
  • Talking with me like I am a teenager. Your slang (especially when combined with ESL marvels) comes across as complete lack of intelligence and class. By the way, spellchecker is not likely to recognize your “gonna”, “wanna”, “gimme”, take a hint. Let me clarify this point – after you established rapport you may find that your client is using colloquial language and slang, following the suite in this case could be OK, still not when you put your words in writing.
  • Being excessively polite. Your culture and language might require twenty minutes of praise and compliments before you get to business but I am an American, cut to the chase guy. More so, being overly polite and using somewhat unusual forms will telegraph a wrong image, your mentioning my “ultimate wisdom” only makes me think of a snake oil salesman.
  • Not being punctual / prepared for your interview. I think of proposal / interview stage as a “honeymoon” in a relationship with a freelancer, it all goes downhill from there. Late for your Skype call? Having troubles finding your headset? Can’t introduce yourself? Chances are that’s the last time you’ll hear from me.
  • Bidding too high or too low. Even though I can understand motivation of people bidding high or low, I typically ignore the bids that stand out in that respect. It’s probably clear why high bid is a losing proposition: unless you got the market cornered the price does matter. Less obvious is a low bid. The main issue here is trust and the fact that we as buyers have been conditioned to expect a “catch” or “bait and switch” with a low bid. Maybe $2 an hour is a perfect wage for combination of what you sell and your standards of living, yet if everyone else bids $15 or higher you should stay in ballpark otherwise the chances are your bid will be ignored.
  • Not following though. Few things annoy me more than a freelancer responding to my post and then dropping off without note / returning my questions. Maybe you realized that I am not the right customer / the project is not in your sweet spot / whatever. It’s perfectly OK to bail out from bidding process, just don’t forget let you customer know. A simple “regrets” note can do a lot for you on a next opportunity that could be exactly what you are looking for.
  • Telling me that you know what I need better than I do. That for some reason is particular common for developers from Eastern Europe and particular from my motherland Russia. If you indeed know (which is highly unlikely) suggest, illustrate, propose – don’t push, don’t fight with me, I get enough fighting when I tell my clients that I know better.
  • Playing games with scope / rates / budget. For many of us on a buyer side many of these games are transparent, most us who’s been in the industry for over 5 years seen at all – “bait and switch”, “low ball”, “door in a face” – you name it. As a matter of fact we make purchases and are being sold on daily basis. We get occasionally burned, sometimes badly. In stock market, real estate, cars, utilities… And when we come to work last thing we want to see is someone trying same techniques…
  • Leaving debris behind. That is my personal pet peeve. Just a few days ago I was looking through code deliverables from a freelancer who just finished a small RoR project for me. Looking through the code I found plenty of loose ends such as hard coded ID addresses, uncommented debugging code, etc. That was the first project this particular freelancer got from me and it is the last one.

I can go on and on, ad infinitum ad nauseam, but I’ve reached my self imposed limit of 10 bullets. I might revisit it later though.

BTW, an initial version of this post posted as a guest blog at oDesk blog got some harsh critique for grammar and other language mistakes I made from Nancci Maloney, probably on of the oDesk freelancers:

Sir, I understand some of your frustrations, but -

If you are going to criticize someone, you need to be sure your own house is in order. You state your second pet peeve is not using correct grammer and spelling.

Look at your 1st bullet – it’s a recycle ‘bin’ – been is a verb. If you had ‘read’ through your post you would know ‘red’ is a color.

2nd bullet – your English is ‘a’ work in progress – sort of changes the meaning of the sentence. If you still ’straggle’ with concepts then you need to look up struggle in the dictionary.

Why would I entrust my paycheck to someone who can’t use spellcheck?

There are other lesser grammatical errors in your post but I think you get the idea. My mama always said people in glass houses shouldn’t throw stones. It’s pretty sound advice.

Not sure if you noticed there are two spelling errors in Nancci’s comment.

So let me apologize in case some of those niximorons are still in this post and suggest that you should “do what I say not what I do” :)

Add to FacebookAdd to DiggAdd to Del.icio.usAdd to StumbleuponAdd to RedditAdd to BlinklistAdd to Ma.gnoliaAdd to TechnoratiAdd to FurlAdd to Newsvine

March 26, 2009 Posted by | Managing Offshore Engagements | | Leave a Comment

Twitter – a New Tool in my Offshoring Toolbox

Eric Pan asked an interesting question on Linkedin – “Other than IM, email and phone call, I am thinking if twitter can improve communication with offshore teams in software development. Do you have any success story to share?”

The immediate reaction of the community was quite negative, e.g. “…the security is horrible and the 140 character limit (as noted in other answers) precludes its effective use… ” or “ … It will be a big distraction. I am not sure how you envision project communication…” I am afraid people behind these answers totally missed the point. I found the question rather thought provoking and after giving a few minutes of attention came to conclusion that twitter could be a rather helpful tool in some type of outsourcing / offshoring projects.

Twitter is quite a new phenomena and in its buzzpower its is successfully wrestling with Facebook and Google, it remains to be seen how rich he’s going to make its founders and whether it will stay for a while or fade away like many fads of the net era.

So far I had a few attempts to become a regular twitter and found neither pleasure nor purpose in it. Some say it could be helpful for my blog promotion, some suggest that it’s mandatory for building your personal brand. Not sure, I will probably give it another try… but that is not the topic here.

On the other hand communication is a backbone of offshoring engagements. One can not overestimate importance of communications for running teams of all kinds, 100 fold so for distributed ones. So if there is a tool that helps in communication processes it at least is worth careful consideration. There are plenty of tools we already have at our disposal – face to face meetings, phone conf calls and one on one discussions, email individual and group, intranet, wiki and sharepoint, chats, do we need another one? Well, is there a gap that needs to be covered? Probably there is none. Is there some way to improve current coverage, I bet!

Going back to twitter origins – it is all about status reporting. What are you doing? In technolingo that translates to What are you working on? Or What is your current status? That makes total sense. Skype chat is for discussions and instant updates. Twitter provides a vehicle of distributing status updates to a group of people in rather non-invasive form without clutter and overhead of email. The follower model is a solid alternative to to:/cc:/bcc: where the sender has to determine distribution list, putting the distribution in the hands of the receiver makes a lot of sense in a group setting.

Are there limitations to twitter – oh boy, where do I start? – but that’s not the point, if instead of nixing the idea for the tool limitations you take a proactive positive look you suddenly find many features that could be indeed very helpful.

I see a good fit to use of twitter in several areas of my offshore SDLC, for example milestone notifications on regression test runs, build reports, etc. There are also multiple possibilities in other areas, take for example production support / uptime notifications…

Not too long ago tools like YIM or Skype were considered bad practices and were banned from corp. IT world, for exactly the same reasons my distinguish LinkedIn colleagues are bashing Twitter today. Will see how this one pans out… let’s reconnect in a year or so?

Add to FacebookAdd to DiggAdd to Del.icio.usAdd to StumbleuponAdd to RedditAdd to BlinklistAdd to Ma.gnoliaAdd to TechnoratiAdd to FurlAdd to Newsvine

March 24, 2009 Posted by | Managing Offshore Engagements | | 5 Comments

Search for SWAT

There is famous French expression cherche la femme (find the woman) implying that behind a cause of almost any event there is a woman (well, in its most common meaning the phrase has negative and sexist connotation). Cherche La SWAT or “Search for SWAT” is an approach I have been using and recommend others to use when selecting an IT service partner, offshore vendors included.  I honestly believe that behind almost any success in our industry there is a SWAT team…

A couple days ago I had a pleasure of meeting with two guys who’s been running their local technology shop for quite some time now. Both were top notch developers who’ve been in the industry probably at least as long as I, maybe longer. A bowl of outstanding Pho in a greasy spoon Vietnamese restaurant, college campus attire, and potential partnership created special ambiance that is particular conducive for nerd bonding.

After quick introduction and buzz word exchange we realized that we were only a degree apart and for awhile were working for startups that we fiercely competing with each other. We laughed through tears talking about how a company with 2 developers and 12 marketers and no product can put out of business a superb product with 12 talented engineers and 1 marketer behind it and then after sharing similar stories about dot com bust and being screwed by VC and CEOs we finally dove into discussion of technical capabilities of the firm my hosts were representing.

It is amazing how quickly these two guys who are as remote to sales and marketing as naïveté to Capitol Hill were able to give me a sense of comfort in their services and products. I guess many sales guys can take a few tips from these nerds. Well, faking competence takes a lot of competence and thus no need for faking ;)

Probably the main reason for such instant connection was a common mind set and similar language even though spoken with very different accents. What was the most important is that these guys had very similar pitch to what I have been using when promoting my services for very long time. These two guys were representing a SWAT team – Specialists With Advanced Tools.

There are many SWAT team out there, yet they are a tiny minority in the vast pool of IT resources. There are a few things that are common between SWAT teams, in particular they

  • are typically comprised of top notch professionals with substantial experience or/and IQ off the charts;
  • are typically specialized shops with individual contributors not making claims outside of their domain;
  • often are small in size and tightly knit teams, many of their members have history of working together possibly in some other firm(s).

SWAT team pitch is typically around results, quality, and productivity. In development arenas they tend to offer veni, vidi, vici model – pragmatic approach to delivering the product and no concern for recurring tasks, when it comes to providing ongoing services they are typically very pragmatic and process oriented. They do not tend to dazzle you with marketing materials and prefer to quickly cut to the chase. If they want to show off anything than it’s typically their weapons – advanced tools – for example a development framework they developed and refined over the years.

Besides obvious benefits of SWAT teams (efficiency, reliability, focus, etc.) there are a few exceptionally important aspects that set SWAT teams apart from a majority of service providers including most prominent companies. To some degree you can call those aspects “advanced tools” as well:

  • Established network of technology leaders and individual contributors of all ranks.
  • Time and scale proven technologies, solutions, libraries, patterns, and reusable components.
  • Best of breed technology tools as well as process, policies, and methodologies.
  • Established relationships with software and hardware vendors.
  • Established partnerships with consulting organizations and offshore providers.

I hope by now I made it obvious that SWAT teams are the teams to find and work with. The trick is the “find” part since there are not that many of them and plus there are plenty of imposters. To a large degree that is very much like for employees – “looking for people is very much like digging for gold, you literally need to go through tons of dirt, but you are looking for gold, not for dirt.”

Add to FacebookAdd to DiggAdd to Del.icio.usAdd to StumbleuponAdd to RedditAdd to BlinklistAdd to Ma.gnoliaAdd to TechnoratiAdd to FurlAdd to Newsvine

March 23, 2009 Posted by | Offshore Vendor Selection | | Leave a Comment

Offshore, Nearshore, Right Shore, Best Shore… oh My

As we can see generating x-shore names is a popular among all kind of companies even established players such as capgemini and eds jumped on band-naming wagon.

It won’t take long till someone trademarks smartshore or ezshore or put a copyright on the word shore – too bad all nautical charts would have to be reprnted… Other companies find using shore words too mundane and invent their own words and phrases such as Chindus Strategy (China-India-US) or BRIC-sourcing. And Me2 – with my term of Disposable Outsourcing.

Hey, why not? That’s somewhat akin to starting companies in the dot-com era – the more confusing it was the high the chances VCs would be all over it … Well, let me tell you, there is no best shore when it comes to IT, there is no best of all shores, and there is no silver bullet. By all means why would anyone outsource if they could deliver on their obligations without headache of dealing with geographically distributed culturally remote third parties?

During those good old days when a Ph.D. from a 3rd world country was only $8K a year cost advantage was so profound that that it was practically impossible to resist the temptation of outsourcing. Today if Ph.D. is asking for $40K the chances are s/he bought the diploma on some black market. With average saving of mare 20-30% it’s not about cost advantage anymore, we go offshore for variety of reasons, goals and objectives. Defining those should be your first step before you even consider vendor search and daunting task of picking perfect destination. “If a man knows not what harbor he seeks, any wind is the right wind.” [Seneca] It should be set of your own objectives, reasons and goals specific to you organization, not taken verbatim form some book or my blog (even though I think you can find a lot of helpful ideas in Top Reasons for Outsourcing or My Reasons to Outsource).

When the reason are clear in your mind it’s time to start picking the “shore” and like with grocery shopping you may want to start with the nearest supermarket and only if what you need is not there you would consider taking a longer drive. Thinking of that metaphor it could be actually not that far off. I live in one of those cul-de-sac communities, the nearest supermarket to my place is expensive and offers limited selection, I do not often shop there, but it’s great when you just want to hop in a car and bring a gallon of milk and a loaf of bread. My main shopping place is about 15 min further driving, but it still doesn’t cover all what I need, for example Whole Foods is about 30- min drive from my place and I still go there once in a while, and add to it occasional trips to farmers market, wineries of Napa, or my friend’s organic farm…

I can’t tell what shore is going to be the best for you, chances are it is different from what is best for some of the vendors knocking on your door, but one thing I am sure of – chose it wisely. We are free to a point of choice, after that the choice controls the chooser.

Add to FacebookAdd to DiggAdd to Del.icio.usAdd to StumbleuponAdd to RedditAdd to BlinklistAdd to Ma.gnoliaAdd to TechnoratiAdd to FurlAdd to Newsvine

February 26, 2009 Posted by | Making Offshore Decision | | Leave a Comment

Main Forces of Negotiation

A little while ago I started a thread covering general negotiation tips, tricks, and techniques. Just for the sake of consistency let me repeat the caveat I mentioned before: negotiation is a complex skill if not art. If negotiations are not particular your cup of tea you may consider involving professionals, in particular those who have experience negotiating offshore contracts. At least you owe it to yourself to go through some serious reading on the topic prior to diving into the deal making. Many of these books cover the main forces of negotiation (Time, Information and Power) in great details so I will take a very superficial approach in covering them. In addition I touch upon two more forces which are at least as important yet are not typically covered – Skills & Experience.

The topic of negotiations is complex and comprehensive; each of the bullets below probably deserves at least a few page long post by itself. So by any means do not expect that reading this post will make you a professional negotiator. I do hope that it would be a good check list to keep handy for your next opportunity to negotiate.

Let start with Time:

The main rule of Time is very simple: The party under the greatest time pressure is the one at disadvantage / the one to lose the ground. Here are a few main tips on dealing with Time in consideration of the rule:

  • Do your best not to put yourself under the time pressure; for example committing to your management that you will have offshore contract done by end of month would not be a good idea.
  • Learn to recognize time pressures your opponent is under.
  • Never reveal that you are under time pressure; that shows your weakness and gives your opponents more armor.
  • Try to put your opponent under time pressure.
  • Recognized when your opponent uses time pressure against you (it’s often artificial / manipulation that could be easily deflected).
  • As the time flies away and the finish line approaches the time pressure grows and the party under the highest pressure start losing the ground. Typically 80% of concessions are made during last 20% of the negotiation time span, so do not leave too much to the end.
  • Be aware of special timing, e.g. end of year / quarter bargaining, but do not be swayed by it, it could be nothing but artificial – just another “time pressure building” technique.

The next major force of negotiations is Information:

You can consider Information as the currency in the world of negotiations. The side that has more information pertaining to the topic of negotiations has the upper hand. Offshore negotiations offer a great illustration of that rule. Consider an example of negotiations around a blended rate. The vendor knows the rates to be paid to the team members, anticipated turnover rate, cost of overhead and all the other components that define exact/true cost of the team. The vendor also has other factors that affect the minimum number the vendor is prepared to agree upon. If the customer has access to the same information they can as easily define minimum rate and take hard stance on negotiation driving to get the bottom line price.

Another illustration is access to specific information such as pressures that would make your opponent to be more flexible. For example if you learn that the sales person who is working with you had not met his quote and could lose his job if this deal is not closed. Knowing that allows you to time negotiations close to say quarter end and let the time pressure itself drive the rates down.

Same goes in the opposite direction – for example a vendor just learned that a couple of competitors bailed out from the negotiations with you. The vendor could easily use this knowledge to get more concessions out of you.

Manipulation of information is a strategy game that requires in-depth understanding of goals and objectives of the process. Here are some of the guidelines for getting better at this game:

  • Gather as much as you can information prior to entering the negotiation and continue collecting it through out the negotiation process.
  • Be very careful in disclosing and distributing information, some supposedly innocuous facts can turned out to be critical ingredients in the information repository. Consider following a good old “Need to Know” principle.
  • Consider disclosing information as trading of goods. For example if I disclose some information to you I would expect a similar act or a concession of different nature in return.
  • At the same time you should understand that information sharing is a mandatory component of negotiations in particular when searching for a win-win solution.
  • Never assume that you know all the facts or that your information is correct.

The 3rd major force of negotiations is typically called Power. At a very high level, Power is ability to influence people, make them do things that otherwise they would not do. Power by itself is just ability, application of power that what makes the difference in the behavior of people.

There are several main ingredients of Power as it pertains to the negotiations:

  • Situation power, e.g. buyer vs. seller in offshore contract negotiations.
  • Reward power, ability to provide rewards.
  • Coercive power, ability to punish, intimidate.
  • Title / position power; note high importance of it in offshore negotiations.
  • Expertise power.
  • Power of flexibility, often undermined yet exceptionally potent ingredient.
  • Character power, charisma, consistency, integrity, command of respect.

Interestingly enough the most important is not the Power itself but its perception. You can say that Power in some sense is similar to beauty: power lies in the eye of the beholder. Another way to put it is if you are perceived in the position of Power you are.

Consider “title” power – if your opponent perceives you as a high ranking official they would interpret your statements in that way even if in reality you are not. For another example of perception of power consider asking your boss for a raise (I assume that you are top notch contributor). Things that could be going through your mind would assign your boss the coercive power – “what if as a result I get fired!?” while the boss might not have this power (firing you could be disastrous for the organization) and the only thoughts in your boss mind would be “how cheap can I get out of it” assigning you the coercive power (ability to punish by quitting).

Negotiations is a game of skill, and as a matter of fact many skills, so I prefer to include the Skill in the list of the main forces of negotiations. The list that covers skills required for running successful negotiations would be very long and complex, so I take a high road suggesting only the main areas. And even though it is greatly simplified the list might seem intimidating, yet you should consider it in its comparison to the task. Offshore negotiations are not necessary as complex or stressful as Union or hostage negotiations, so you do not have to have all the skills at top level. More so the skills may be distributed among the team members and that would make achieving the success much more realistic task.

Foundational skills or ability to –

  • Learn and improve.
  • Control your own emotional state.
  • Maintain your own integrity.

Specific skills pertaining to negotiation process –

  • Setting goals, objectives, outcomes.
  • Defining and staying within boundaries, limits, constraints, conditions.
  • Using negotiating techniques – recognizing, using and countering negotiating gambits.
  • Finding and driving for a Win-Win outcome whenever is possible.
  • Obtaining and maintaining required authority

Analytical abilities are particular important for defining game plan and assessment of opponent’s position / game plan –

  • Negotiation limits / negotiation space.
  • Best Alternative to Negotiated Agreement (BATNA).
  • Final Exit Point (FEP) and a Reservation Point (RP).
  • Offers, propositions, tactics, techniques.

Behavioral skills and abilities –

  • Focus
  • Observation skills
  • Planning and organizational skills
  • Rapport building skills
  • Flexibility
  • Creativity
  • Tenacity

Command of communication techniques –

  • Presentation skills
  • Active listening
  • Art of silence
  • Read opponent’s non-verbal language
  • Communicate non-verbally
  • Information recovery

And the last in the list of the main forces of negotiation is Experience. The only way most of us can become good negotiators is by consistent learning and using multiple aspects of the art in real life. As in many areas of our activities it comes down to mileage, the more you sail the better you get at controlling your boat…

Add to FacebookAdd to DiggAdd to Del.icio.usAdd to StumbleuponAdd to RedditAdd to BlinklistAdd to Ma.gnoliaAdd to TechnoratiAdd to FurlAdd to Newsvine

February 24, 2009 Posted by | Contract Negotiations | | 2 Comments

10 Things you Don’t Want Offshore Vendor to Know

I am an avid proponent of open communications and believe the more partners know about each other the better are the chances for the partnership to be successful. There are still a lot of things that you should keep to yourself for the same general reason – to increase the chances of the partnership being successful.

1. Game plan. Negotiations are an ongoing part of business relationship – not just the talks around the contract. Keep you card close to the chest and never disclose the game plan, even far after the game is over.

2. Decision making process. Whether you signing the initial contract, extending the scope of the engagement or making changes in the way the relationship is run you should not disclose the details of decision making process. In particular if you are the one making the decision you should not proudly announce it. There are many reasons for keeping it low, let me mention just a couple:

  • Disclosing decision making process will limit you ability to use “high authority” negotiation gambit that is a powerful technique for getting more in negotiations.
  • The last thing true decision makers need is all might of vendor sales force targeting them through every sales channel.

3. Budget. I always give my vendors an indication of the budget but never exact figures. One of the main reasons to keep it private is the nature of budgets – they change, funds get reallocated, etc. And of course something to be said about negotiation upper hand with less information at your partner disposal.

4. Roadmap. Product and relationship roadmaps should be shared with your vendor only at a very high level. Details should not be communicated for many reasons – business counterintelligence and agile nature of the roadmaps (similar to budget note above) being the most important.

5. Details of competition. The competition can offer a lot during contract negotiations: from cannon fodder to reasonable alternative. Your offshore partner should know that competition exists (at least that would keep them on their toes) but not the details, even the names of competing entities is not something to disclose. Among many reasons let me point out just a couple:

  • You probably have an NDA in place, that’s already a strong reason to keep your lips sealed.
  • The runner-up competitor today can be a vendor of choice tomorrow.
  • You do not know what kind of back-end links your vendors have in place.

6. IP / Know-how. If you must share anything of that nature make sure that the information distribution is governed / controlled tightly. The vendors with the best intention have little power over disgruntle employees – the prime venue of information leak. Employ distribution of the information on a Need-to-Know basis.

7. Confidential information. Same as above applies to many aspects of your business, internal and external (e.g. customer data). Consider rules associated with on handling ePHI (electronic protected healthcare information) or financial information and penalties associated with its mishandling. This is a very comprehensive topic; I will cover it in a stand-alone post.

8. Dirty Laundry. Sharing it with your vendor can hurt you in many ways; in particular consider the scenario of the relationship gone sour for any reasons; won’t you prefer your ex-partner to know as little about you as possible?

9. Personal details. Do not get close and personal with the vendor / vendor employees. There are many ways it can end up costing you more than you bargained for. There is no harm in sharing you “public” personal details (married, three kids lived in Bay Area all your life, etc.) but sharing little known data may put you in a difficult situation.

10. Ulterior motives. Ulterior means hidden – so keep it that way, if you pick your vendor based on something rather than items stated in your RFP, keep it to yourself. It’s amazing what kind of confessions I heard in that department (e.g. “I picked the company in China because my wife is Chinese and it makes it easier for us to stay in touch with her family”). This won’t help you professional image / reputation and can actually hurt your career…

Add to FacebookAdd to DiggAdd to Del.icio.usAdd to StumbleuponAdd to RedditAdd to BlinklistAdd to Ma.gnoliaAdd to TechnoratiAdd to FurlAdd to Newsvine

February 17, 2009 Posted by | Making Offshore Decision | | Leave a Comment

Offshore Impact: Personnel Issues

So you are moving forward with offshore initiative, maybe a new or expanding an existing one. What is going through the minds of your team members? What kind of questions are coming up? What is not letting them sleep at night? That’s not difficult to imagine:

  • Is my job at risk?
  • Is my salary at risk?
  • Is my career at risk?
  • Is my quality of life at risk?
  • Is my project / department / team at risk?

Let’s start with a reality check: chances are there will be three groups of people easily categorized by the answers to these questions – Yes, No and Mixed / In between. There will be people who can lose their jobs or forced to take lower paying jobs. Transferring jobs offshore may reduce scope of career opportunities or completely eliminate some. Some people might be asked to work odd hours, and so on. Maybe some of the team members won’t be affected at all. And for some there will be a mixed impact. That impact on employees inevitably affects the employer, and as I pointed in my earlier post The Darkest Side of Outsourcing that impact could be very serious. That’s why minimizing negative impact of personnel issues is likely to become your primary objective as an outsourcing champion or the manager in charge.

One of the ways to do it is to tune into your team’s WII.FM station. What’s In It For Me? What is the silver lining of the offshore initiative for your team members? That of course depends on specifics of your organization and the scope of offshoring; here are just a few general ideas for your consideration:

  • Offshoring might offer an opportunity to offload grunt work freeing up employees to work on more interesting / engaging projects.
  • In similar manner offloading grunt work may allow organization and its employees to focus on core strengths and areas of competence.
  • Sometimes offshoring opens an opportunity for the employees to learn new technologies / products.
  • Management / leadership opportunities can open up.
  • Specifically offshore management opportunities could be attractive option for career development. With offshore here to stay experience with offshoring can benefit many employees even those not involved in management / leading roles.

Let me repeat something I mentioned in The Darkest Side of Outsourcing: Associating introduction of offshore with layoffs – replacing local workforce with offshore resources is a double hit on remaining workforce with inevitable impact on employee morale and overall workforce quality:

  • Employee motivation will disrupted with result in increase in political behaviors, anger, fear – which is likely to negatively impact quality of customer service, performance decline, and decline in quality of work atmosphere.
  • “Survivors” experience more stress due to longer work hours with re-designed jobs, and increased uncertainty regarding future downsizings.
  • Senior and the most marketable employees may leave with result in decline of overall quality and qualification of workforce and loss of institutional memory.

A silver lining here is an opportunity those events could represent for some of the employees: an opportunity to show one’s ability to excel under pressure, a chance to step up to challenge and learn new product, skill, fulfill the void left by departing employee.

In my experience I’ve seen that on numerous occasions – a problem creating a launching pad for capable but for some reason unnoticed or underappreciated employees.

The question is whether as the leader of organization you can carry on positive message and motivate the troops to take advantage of the opportunity rather than dwell on native events and unforgivable loses. Another question is whether you can deal with inevitable negativity and ripple effect of the changes. Here are a few things to consider for dealing with the personnel impact:

  • Consistent non-stop communication. Check out 7 Cs of communications and follow those as much as you can afford considering the situation.
  • Consistent aggressive motivation. “Motivation is like food for the brain. You cannot get enough in one sitting. It needs continual and regular top up’s.” [Peter Davies]
  • Be prepared to pay above market. Hopefully offshore cost savings can offset some of the cost impact.
  • Invest heavily in the staff redundancy. That is a complex issue that requires longer discussion, let me just mention just one aspect of it: staff redundancy will give you the confidence to operate in the challenging environment that offshoring is likely to create in your organization.
  • Process and methodology changes / adjustments / improvements to create environment tuned to the new organizational layout.

Add to FacebookAdd to DiggAdd to Del.icio.usAdd to StumbleuponAdd to RedditAdd to BlinklistAdd to Ma.gnoliaAdd to TechnoratiAdd to FurlAdd to Newsvine

February 14, 2009 Posted by | Managing Offshore Engagements | , | Leave a Comment

The Darkest Side of Outsourcing

While writing a post on a topic of personnel impact of the offshore outsourcing I had to go through a rather unpleasant exercise – I had to terminate one of my employees. Termination is never fun, it is particular painful on a backdrop of economy downturn. Through my career I had to let go a great number of people, mainly due to the industry’s downturns / massive layoffs. Layoffs are painful yet the sheer size of the event makes it easier on everyone. Things tend to go much more close and personal when you have to let go someone on a performance basis.

Reaction of the person being let go on a performance basis is very difficult to predict and control. I have seen budges fly in my face, verbal explosions and threats, I have been in situations when I had to call security and once got very close to calling an ambulance. This time it did not go particular well either. The employee got agitated, angry and quite upset with the unfairness of the event. After the termination the direct manager of the employee and I started receiving harassing calls from a blocked number on our personal phones…

Sending jobs offshore is likely to create a few enemies. For example when I introduced offshore concept in Spear Technologies one of my key employees came back with a common in this case blackmail techniques: “I’ll quit”; he did not, just remained never ending pain in the neck. Two other people quit citing offshore decision as one of main reasons. If sending jobs offshore means layoffs things can get quite ugly. Especially if the laid off employees are picked on a performance basis, what is quite typical and the right way to go, especially in smaller companies.

Performance based termination rarely goes well, and sometimes goes exceptionally bad. It was not long ago when a laid off employee took lives of executives of his company in a Santa Clara startup. As my CEO put it “There is too often a thin veil that covers members of society and when the wind blows, the veil can come off. After 10 years in the emergency department I can tell you that apparently senseless violence is hardly rare. The details of this occasion are making headlines but frankly not the violence. Very sad to me is not just the violence but the lack of priority or even care for this guy’s own family. He destroyed more lives than he ended.”

I’ve written about potential pitfalls of outsourcing and will write more. You should move carefully and make educated steps when outsourcing, if your offshoring decision is causing / associated with local job losses be exceptionally careful. You could be making the decision based on spreadsheets and what if analysis, for better good, the company survival and bottom line needs; for you that might mean “nothing personal” yet for those who are about to face job search in today’s market it will be very personal. To minimize potential backlash consider a few general tips:

  • Deliver clear and consistent communications with messages covering reasons, expected goals and objectives, as well as processes behind. The communications should in general precede the events and continue on long past them.
  • Do not cut the jobs across the board. Rather, make the tough decisions to selectively cut jobs. Do not disguise performance based termination as layoffs.
  • Focus on those who stay, yet remember that “survivors” will judge you / organization by the way layoff was conducted and downsized employees were treated

Associating introduction of offshore with layoffs – replacing local workforce with offshore resources is double hit on remaining workforce with inevitable impact on employee morale and overall workforce quality:

  • Employee motivation will disrupted with result in increase in political behaviors, anger, fear – which is likely to negatively impact quality of customer service, performance decline, and decline in quality of work atmosphere.
  • “Survivors” experience more stress due to longer work hours with re-designed jobs, and increased uncertainty regarding future downsizings.
  • Senior and the most marketable employees may leave with result in decline of overall quality and qualification of workforce and loss of institutional memory.

This post was not intended to be “all gloom and doom”. Not many people make offshore decision just for the fun of it. Outsourcing is only one of the tools IT leadership has at its disposal today and as any tool it has its dark side. Knowing that side should help you apply the tool properly and minimize collateral damage.

And the last tip for now – if you are planning to replace some of your local underperforming workers with offshore resources get unlisted – make sure that your personal contact info is not in company directory, white pages, linkedin, resume, etc. – not a trivial task nowadays…

Add to FacebookAdd to DiggAdd to Del.icio.usAdd to StumbleuponAdd to RedditAdd to BlinklistAdd to Ma.gnoliaAdd to TechnoratiAdd to FurlAdd to Newsvine

February 10, 2009 Posted by | Managing Offshore Engagements | , , | 1 Comment

Using Agile with Offshore

One topic that often comes up with relationship to outsourcing software development projects is the use of agile methodologies. Having run a number of projects using agile methodologies with offshore (nearshore) partners I found that some of the classic principles do not work as well, for example XP’s “pair programming” and “moving people around” need to be taken with a grain of salt / adjusted with consideration of the lack of collocation.

Of course when it comes to agile development you need to start with agile evangelists’ take on the subject. Martin Fowler in what is now a classic article Using an Agile Software Process with Offshore Development covers 14 major lessons learned:

1. Use Continuous Integration to Avoid Integration Headaches
2. Have Each Site Send Ambassadors to the Other Sites
3. Use Contact Visits to build trust
4. Don’t Underestimate the Culture Change
5. Use wikis to contain common information
6. Use Test Scripts to Help Understand the Requirements
7. Use Regular Builds to Get Feedback on Functionality
8. Use Regular Short Status Meetings
9. Use Short Iterations
10. Use an Iteration Planning Meeting that’s Tailored for Remote Sites
11. When Moving a Code Base, Bug Fixing Makes a Good Start
12. Separate teams by functionality not activity
13. Expect to need more documents.
14. Get multiple communication modes working early

That list presents a great set of guidelines, and none of them are in the conflict with foundational principals of agile development. Some of them are unfortunately in a conflict with realities you might be facing on your project.

Let me start with items # 2 & 3. That is an absolutely correct way to improve communications – make the offshore as onshore as possible by swapping people, putting semi-permanent representatives on both sides of the ocean, etc. The problem with it is that many companies, especially smaller ones can not afford this approach. Bringing and offshore person on-site roughly brings his/her rate to what you would pay a local resource and for any considerable length of assignment is likely to cost even more than local resource. Sending your local resource offshore increases the cost substantially. Personal life of ambassadors is likely to be affected not necessarily in a positive way. To minimize the impact you might consider younger ambassadors however a lack of experience may defeat the purpose. Once again, I can not agree more with both techniques yet the chances are you would have to compromise on those and thus creating inevitable negative impact on the project.

# 4. To some degree this section plays down an obstacle that could be an agile showstopper. Martin Fowler presents a few interesting examples of cultural challenges that his team successfully overcame. You might have not as much success with it, especially when working with a third party provider rather than captive resources. Try “anti-authority attitude” with any top tier vendors in India, see how far you get – and do please let me know. Also, there is much to be said about forcing foreign culture onto people who will have to stay in the society that doesn’t support it.

There are of course many others cultural challenges that deserve a serious discussion; let me just touch on one: some people call it “having Agile in DNA”; some call it “agile aptitude”. That would be a topic for a very long discussion; for now I will cut it very short: some teams are just not made for agile; and that is a cross-cultural phenomena. The culture puts its additional imprint on the issue with deeply embedded cultural traits such as conflict avoidance, hierarchical structure, meaning of respect, etc. you often find offshore. Unless you have the luxury of building your own team you would need to asses the team’s ability to go agile and your ability to guide it thorough. In some cases you will find that being practically impossible. If ignored or not handled properly subtle sabotage will find its way to the surface through malicious compliance and will bring your project to a memorable fiasco.

# 9: Short iterations have a great positive impact on the project and alas high overhead as well which exacerbated by offshore communication challenges, time difference, logistics, etc. could be unbearable. In my experience two week iterations presented a reasonable minimum.

#12 & 13 get us into a line of fire of the holly war between agile and waterfall :) And in my opinion that is as productive discussion as the “mind over matter” (by the way the later one has been solved: “if you don’t mind it doesn’t matter”). This is not an argument anyone could ever win, there is a place for agile there is a place for waterfall, and everything in between. Pick the best tool for the job, adjust your methodology to accommodate for organizational requirements, environment and team at hand… of course “If the only tool you have is a hammer, you tend to treat everything as if it were a nail” [A. Maslow]

I think it’s enough of picking on the celebrity, time for a couple observations of my own:

Minimize the time gap. You can find many blogs and articles that talk about the time difference as an advantage, what a joke! 11.5 hrs time difference with India can easily result in 48 (business!) hours delay in resolution of urgent issues. If agile is your chosen path consider minimizing that gap; your best bet could be a nearshore offering, or farshore partners who understand the value of team overlap. Some of my favorite vendors take this issue on with a vengeance starting work hours for their employees at noon local time; interestingly enough that gives them some add on benefits such as less challenging commute.

Pick only engineers with fluent English. That one seems like a no-brainer yet you will find a lot of push against it if you deal with pretty much any geography outside India. The meaning of “all our engineers read and write technical documentation in English” translates from Vendorian (the language vendors speak) as “some of our engineers went through English boot camp when in college). While that could be a manageable obstacle for teams operating as a black box or in a well managed waterfall that will be a showstopper for a mixed team agile project.

Select developers with approximately the same skill level with exception of very few on a high and a low end; the ranking for those exceptions must be clearly understood and communicated across the team. That one cuts deep in the heart of some agile practices and beliefs so I have to put a couple thoughts here:

In software development all engineers are equal and some are more equal… The difference in productivity and quality of code for strong developer and average one could be tenfold, expecting them to work together is like expecting turbocharged Porsche and limping horse powered carriage travel together in an autobahn. If you build your team with the best and the brightest chances are they could be equal even if their experience is at different level: a bright engineer will have no problems stepping aside in a face of reason or experience. When freedom of expression is given to an average or a mediocre contributor on team that also has high quality developers the result is predictable – it’s either beat him into pulp or produce code at average or mediocre level.

There are many other negative trends that naturally develop in teams with wild mix of skill levels – cherry picking, slavery, slacking off – just to name a few. By no means I am advocating for arbitrary hierarchy though… In my experience the best agile teams are formed by like-mind professionals of approximately same level of skills gathered around a top notch technical leader.

Adding offshore spin on the requirement to keep developers at approximately the same skill level adds a huge challenge to the team building process, especially in hierarchical societies or/and organizations.

Build a team. Easier said than done, and that’s why it is my favorite craft. Building teams with offshore components elevates the complexity of the task to a completely new level. When it comes to agile development building a team from a group of people working on the same project makes all the difference; the difference so profound that it feels like magic. The good news is that you do not need to graduate from Hogwarts to be successful at building balanced teams that perform well on agile projects. OK, this topic requires much more than just a couple paragraphs or a few posts, maybe a very active stand-alone blog can give the topic the justice it deserves… For now let me just mention my formula for success :)

nsf

Establish solid project management. A dedicated PM is an absolutely critical role on an agile project of a decent size. This role becomes twice as important when the team is not collocated and another tenfold if the team spans countries. Strong s/w PMs are a very scarce commodity though. It takes solid technical knowledge, superb PM skills and personality match, considering limited pay rate and unlimited challenges – it’s no surprise they are so difficult to find. By the way, when it comes to agile projects I would take certified PMP and get him/her to learn SCRUM (or whatever the methodology is) over SCRUM master in 4 out of 5 cases. Not sure whether I am jaded or just biased. Having interviewed hundreds PM through my career that so far has been my experience.

Continuously improve the process. There are many techniques that will help you to do so, iteration retrospectives is one of the easiest ones. My teams use round table discussion approach with everyone presenting keeps and tries that are captured and tracked by the PM. Tracking is essential as even great ideas tend to get lost unless there is a driving force behind it.

And the last one for now: do not compromise on tools. Agile teams have all too common gravitation towards open source. That’s commendable yet needs to be taken with caution. More so, when it comes to development tools open source doesn’t always mean the best or even “good enough”. Some tools supported by gainfully employed professionals offer impressive value and are substantially more reliable than those supported by the community. For example my team after numerous attempts to work around some limitations of CruiseControl settled on Bamboo with notable impact on productivity. Same goes for many other tools (CI, Testing, Code Review, Wiki, etc.), so do not compromise on them, pick the best you can afford.

Well, with all those caveats and warnings you might think that agile and offshore do not mix. I would not say so, while running agile projects with distributed teams is not a trivial exercise it could be productive, efficient and a lot of fun. Given the right opportunity I would do it a heartbeat.

February 5, 2009 Posted by | Managing Offshore Engagements | , | 9 Comments

Follow

Get every new post delivered to your Inbox.

Join 25 other followers