Apologizing the wrong way: case study (revised)

Very innovate Israel based companies deploy projects and products in a very aggressive time frame, often months before competing development centres manage to do so.

The speed of development and deployment  is enabled by “speed as strategy”,  a developed work ethic (there is no work life balance in Israel in the high tech sector),  flexibility, high tolerance for risk,  and less importance attached to the formalism of planning and documentation

Wouldn’t you know it, but often these newly released products and releases are often buggy and need to be cleansed and purified on the customer site once deployed.

So, while the customer gets the competitive value he asked for quickly, the customer is furious what is perceived as the “sloppiness” and “poor finish”, the very attributes which enabled the Israeli vendor to deploy so quickly.

With well known thick skin stemming from the entrepreneurial  spirit, augmented by Israeli chutzpah (gall/cheek), the Israeli developers can take the heat well and fix the bugs quickly. However, a problem can arise when the Israeli supplier is asked to apologize, especially in SEA and Japan.

There is an expectation in many parts of SEA and Japan that an apology will express humility and remorse. The client wants to see that the vendor is truly sorry and ashamed.

The Israel vendor will apologize in a matter of fact statement and then, the Israeli will get to the perceived important part: explain the root causes and what will be done. Example: “I am sorry about bug 240. However, it is not revenue impacting. The bug stems the difference between the R&D development environment and the environment in tyour  site, and engineer Itai (m) will do 9000 hours of testing and stay here for a month; it should be fine; don’t worry.”

This explanation is seen as remorse-free ; it often aggravates the client even more than the bug itself.

The Israeli wants to apologize for the deficiency  itself and explain the cause, and the client wants to see the pain of remorse and regret!

I have spent hundreds of hours explaining this to Israeli vendors. It is an uphill run, because the essence of the innovative personality is generally numb about such matters.

One client of mine was forced by his distributor to hire someone (me) to “improve apology skills”.

Share Button

Engineering Sandbagging and Culture

Sandbagging is a method of managing the expectations of peers and managers by giving estimates well below the “doable”. When better results are achieved, the individual shines.

One reason that explains some of the sandbagging in the engineering world is universal: management makes hallucinatory aggressive commitments to demanding customers;  engineers respond with gloom to protect themselves from working 6 months with no weekends as well as a means of procuring engineering resources from overly zealous management.

There are additional cultural factors impacting how and why people sandbag. I shall illustrate 4 examples and provide the recommended choice of managerial action for each case.

1) An Israeli engineer will sandbag because everything is a negotiation, all the time. The planning process itself is seen as a negotiation in which middle ground is reached. The recommended choice of managerial action is to negotiate, long and hard, and then sign the Israeli off on his commitment.

2) An Indian engineer will sandbag via negotiation, but  differently than his Israeli counterpart. The Indian will initially agree to what he has been tasked with, yet as the project progresses, he will surface obstacles and barriers to meeting the deadline. Like the Israeli, the Indian negotiates but in instalments. The recommended choice of managerial action is to work closely with the engineer, not allowing too much time to pass before he “updates you” the commitment he made is passé.

3) A Thai engineer will sandbag is a unique fashion. If he knows you very well, you will get an accurate answer. However, if you are remote and not close to the Thai, he will tell you something that he thinks you want to hear. Then, via gossip or via telling other people, he will sandbag to save his own face in the case of delays. It may come to you from a 3rd party in the form of :“Boss, Khun Sumchai told me that his commitments are very optimistic”. The recommended choice of managerial action is to try to build up a personal and trusting relationship with the Thai to get real (not klenjai –outwardly pleasing) answers.

3) An American engineer will sandbag expediently (in order not to damage his career)  by questioning the planning assumptions again and again, or wearing out the manager by overdoing on ritualistic planning. This will be followed by an apparent, half baked commitment basked in nice language like “we’ll do our best”. The recommended choice of managerial action is to ask “what is realistic”, without delving into planning overdose.

Share Button

Commitments to customers and culture-a case study

1 Goal of this post:

The goal of the case is to illustrate how people from different cultures approach the issue of dealing with making an aggressive commitment to demanding customers.

2 The customer:

The customer is a utility provider in Asia. The customer is requesting a feature which will allow households to monitor the air pollution in their home using a cell phone application, and send the data to a central data bank, enabling corrective action by the authorities.

The president of the utility has demanded that “go-live” day is in 6 months, to coincide with the Provincial Premier’s visit to the capital city of a certain province.

If everything goes well and deployment happens in 6 months, the  CEO of this utility will look very good, and more important, the Premier will  look even better.

3-The potential vendors:

Fred is the CEO of Freddy and Sons, a US based firm, which develops software for Green Environments.

Gal is the CEO of Gal and Sons, a Tel Aviv based firm, which develops software for Green Environments.

4-How does Fred handle the situation?

Fred has devoted over 400 hours analysing the contingencies.Fred has learned that even in the best case scenario, the software will be 3 months late.

Fred will now put together a very detailed plan, and then meet with the customer and try to change the timetable, or reduce the scope of what can be delivered, all this will be done in a spirit of transparency.

Fred does not want to surprise the customer and he certainly does not want an unhappy customer.

This utility is in a very large country, and the last thing Fred wants to do is tarnish his firms’ reputation.

4-How does Gal handle the situation?

Gal met with the customer and said: “we can do it”. “We can start tomorrow”, said Gal to the elated customer, who was waiting for a dithering Fred.

Gal’s “plan” is to push his people hard and see what can be done.

Gal believes the client knows he is “over-buying” (asking for something that cannot be done) and Gal believes that the client knows that Gal is “over selling”, ie, making impossible commitments.

Gal plans to build a very close relationship with the client, and if and when Gal cannot deliver what he promised, “something” will be improvised that will ensure everyone looks good. Gal has in mind three or four pyrotechnical displays which will titillate the Premier on his visit. Gal believes that the time to plan is when the crisis is upon him, NOT now as work gets underway.

5-What are Fred’s assumptions?

Customers need to be satisfied; plans enable control; transparency pays off; long term more important that short term.

6-What are Gal’s assumptions?

Customers need to be managed; plans may cripple survival, transparency can be counterproductive or idiotic; short term survival more important than the “long term”.

Share Button

Waiting till the consulting market gets better is useless-ask yourself 4 questions to ensure relevancy

Samuel Beckett’s play “en attendant Godot” (Waiting for Godot) is about people waiting for someone who never shows up. The play illustrates that while meaning may exist in the world, we human beings are not too good in discovering it. It is not strange that Beckett’s genre is the Theatre of the Absurd.

OD consultants are waiting for the market to improve. The goal of this short post is to show absurd this is, and propose an alternative.

In one of my previous posts this week, I focused on the growing irrelevance of OD as currently practised. This irrelevance has caused a drop in demand for Organisational Development. Add to this, the universities keep churning out OD consultants at an alarming rate. Perhaps (in Israel where I live) we may soon have more OD consultant than lawyers, or even more OD consultants than Middle East “experts”.

With the lessening of demand and the growth of supply, there is not only a problem on the horizon, it’s here.

The OD consultants who are waiting for the clouds to pass over and waiting for the economy to improve need to wake up and smell the coffee. Godot never comes. The cheese has moved. OD is moving forward, not going back.

What is to be done instead of Waiting for Godot?

OD consultants get work if they are relevant.

Here are 4 questions  you need to ask yourself (and have superb answers) to be remain relevant , which will ensure a backlog of work.

Invest

1) What relevant value do I need to provide to enable effective functioning in a global organizational configuration? What are the situations of global organizing which clients can come to me to solve?

Divest

2) From which beliefs do I need to divest, i.e. present beliefs  which limit my relevance and make me sound absurd?

Focus

3) Since OD services do not have universal appeal, upon whom should I be focusing on to provide the value I create?

Reputation and Position

4) How do I build my position as a content expert (not only facilitator) in the domain in which I work?

Share Button

Overuse of the word “trust”

The term trust is overused; trust means too many things to different people. In the global workplace. The term trust is thus rendered useless, for all intents and purposes.

For example, here is a dynamic between Germans and others with whom they work:  Follow the process and I will trust you; when I trust you, I will follow the process.

Or another example seen between Chinese and Americans: Mr. Wu and Mr. Smith sign a 40 million dollar deal. Then Mr Wu asks Mr Smith to hire his son for a year so that the son  can get a visa to the US. Smith does not trust Wu because he is corrupt. Wu does not trust Smith because “I just did him a favour, and he won’t even help me with my son”.

There are of course many more examples of words which lose their meaning in the global workplace; in a previous post I elaborated on the term  respect.

I have spoken over the years I have been consulting with thousands of people who do trust one another, and I have developed ten statements which operationalize what trust is. Here in the public domain, I will share 3 of the ten.

1) We represent one anothers’ views when the other party is absent.

2) We implement what we decide upon.

3) We assume positive intent.

Share Button

Culture and Lesson Learned Methodology

Within most global organizations, the same version of a “Lessons Learned” (LL) methodology is blindly used with all populations, despite the cultural and behavioural factors which inhibits the  effectiveness of the  lessons learned methodology.

Three  examples will suffice.

1) Let’s take the example of Holland, Germany, Israel and France where criticism can be well valued.

During the process of LL, overly positive statements may even be  seen as “ducking out”;  dwelling for too long about what went well is as boy scout-ism from which little can be learnt. The result of lessons learned in these cultures  is a list of things that went wrong, why and what needs to be done differently by whom the next time.

2) In many parts of Asia, public negative statements about things that have happened are avoided to enable save facing.

During the process of LL, communication will be oblique, indirect and low keyed and one will need to understand what was not said. Apology, humility and a promise to try harder next time are the publicly shared lessons learned that can be generated within these cultures.

3) In the US and Western Europe, the overdosing on politically correct can obfuscate lessons learned because the lessons, once learned, need to be cleansed linguistically.

Clearly all 3 cultures are ill suited to apply the same  lessons learned methodology.  Yet LL methodologies originate in western corporate headquarters and as such are based on one flavour suits all.

An interesting and value creating role for an OD consultant is to interpret the cultural script of a lessons learned exercise . Herein is a vast secret code which is fascinating to decipher. 

———-

Dear subscribers,

In order to clean up the spam, all blog subscriptions were deleted and a new subscription system installed. Please re register and sorry for the trouble.

Allon

Share Button

Critical issues facing Organizational Development-revised

“The outlook wasn’t brilliant for the Mudville Nine that day;

The score stood four to two, with but one inning more to play,

And then when Cooney died at first, and Barrows did the same,

A sickly silence fell upon the patrons of the game.’

From Casey at the Bat –Ernest Thayer         Hebrew translation

Let’s look at the context in which OD is practiced nowadays and what this all means.

1) There is a severe economic crisis which has been going on for a long time. While some phoney “economic indicators” may look better than they did in 2008, the truth is that organizations are war zones in which people struggle not to join the ranks of the unemployed. Few people expect to have job satisfaction; “ satisfaction” is having a job. Since market conditions favour the employer and not the employee, people are no longer all that important. People have become spare parts.

The cornerstone of OD was to align the individual with the organization and focus on creating an environment which is good for the individual and for the organization. Thus, the relevance of OD’s value proposition appears bizarre at the present moment.

2) Professions should have professional standards. These professional standards serve as a balance and complement the commercial criteria by which professions are evaluated. So, a chartered accountant who has a thriving business but violates accounting practices will find himself in deep water.

OD is a poorly defined profession with no borders. There are no agreed upon professional standards. Thus, commercial standards are totally dominating how OD is practiced. OD has become a commodity, sold by an OD vendor, and the OD practitioner must satisfy the client. If the client does not know what he needs, this is irrelevant because you “follow the money” and deliver what has been ordered.

A cornerstone of OD was to “speak truth to power”. If one needs to “titillate” and please the “customer”, the ability of OD to delivery on one of its major principles is castrated.

3) OD was founded by White Western and European males, and the Western values of OD are  in line with those of the founders: participation, openness, authenticity, delegation, team work.

Organizations are now configured globally. In most of the world, there is more autocracy, more secretiveness, more discretion than is seen in the west; many of the values of OD are seen as parochial and irrelevant to the way people should operate, especially when they are threatened as people are in today’s economy.

4) As OD “stood its ground” and waited for the economy to “recover”, other professions cannibalized OD.

Change Management promises those in power that changes can be “managed” with a set of templates. HR’s disguising itself as a “business partner”, has cast aside/betrays the lobbying for the human resource and often serves as management’s 5th column to “deal” and contain the human resource. Unions and organized labour may/will fill in the vacuum. Certainly in the country where I live, re-unionization is rampant.

5) OD had a massive focus on communication. In organizations, people rarely talk too much any more; they text and email and use portals. A major domain in which OD brought huge value is shrinking.

6) Now that Corona has created unprecedented crisis and unrelenting change  in all organizations and systems, there is a new challenge to our relevance.

  • Jobs are very scarce. Very scare. Like 4 leaf clovers. And that means that it becomes an employers’ world: sans work-life balance; sans perks; sans engagement; sans paid vacation; sans lunch coupons.
  • Choppy choppy is back in season. 3 jobs will become one. Three departments will become two. Six engineers will become four. And until that happens, organizations will be war zones between people vying to be retained.
  • The roles and functions focused on gender equality and diversity will be totally marginalized and wither away. It’s a world of many people drowning and very few life jackets.
  • Dreams, vision and big ideas will be relegated to the back burner.

We need to be faster, more short term focused, less non-directive and far more creative, shaking off values which hold us back from being relevant in this economic catastrophe. This is a tall order for a profession so enamored by its past, and trapped in the values of another world which is dead and gone

Oh, somewhere in this favoured land the sun is shining bright;

The band is playing somewhere, and somewhere hearts are light,

And somewhere men are laughing, and somewhere children shout;

But there is no joy in Mudville — mighty Casey has struck out

From Casey at the Bat –Ernest Thayer     Hebrew translation

 

 

 

Share Button

How can a US based manager deal with 3 difficult aspects of Israeli business culture

 

 

It ain’t easy managing creative people.There are hundreds if not thousands of US based managers who are managing Israelis, especially in R&D and Engineering.

The US based managers enjoy the hard working nature of the Israelis, the boundless  creativity and the pragmatic, no nonsense approach of “doing whatever it takes” to get the job done. On the other hand, the way that Israelis do business can be very annoying to US based managers.

I have a list of about 45 annoying things that Israelis do to American manager and how to deal with them. In this post I will deal with three of the more annoying behaviours.

1) Israelis argue all the time. Absolutely  everything (especially management direction) is up for debate. While this debate enables a lot of the creativity, it is often hard for a US based manager to manage the endless filibusters in order to “move on”.

The best way to deal with this is to let the arguing go on until “enough is enough” and then end it very forcefully by standing up, raising your voice, and tell them to stop arguing. You can do so in English, and if necessary in Hebrew. If there are two Hebrew words a US manager should learn, they are “tafsiku lhitvakech”-stop arguing. (תפסיקו להתווכח)

2) Israelis challenge authority all the time. If a US manager believes that once he has given direction “my word be done”, he will be in for a rude awakening. Israelis (like Aussies) are very suspect of authority and never acquiesce without a good fight. The upside is that you won’t encounter passive resistance, but you sure will encounter active resistance.

The best way to deal with the challenge to authority  is to absorb some punishment, fight back, and when enough is enough simple say….”the discussion is over-do what you are told”. The Israelis will respect this far more than a weak and politically correct hint, such as “get over it, guys”.

3) After a decision has been made, Israelis often return to the decision and try to re open it with new facts and opinions. More than anything else, this drives US managers crazy. The upside of this behaviour is that last minute changes often enable a more flexible response; the downside is that this flexibility is not scalable.

The best way to deal with this is to allow re opening of decisions in engineering and technical matters, and not allow this reopening of decisions in other less critical areas. When you do not allow an Israeli to revisit a decision, you may lose his trust, but take the risk, because otherwise you can spin wheels in endless debates.

Share Button

When communicating with a non confrontive culture, how to ensure that real agreement exists? (revised)

 

Many cultures shun confrontation of any kind in the work place, the most extreme examples being Thailand and the Philippines, as well as many other places in Asia, the Middle East and South America.

In these cultures, verbal agreement is given to show respect, give face, preserve harmony and avoid embarrassment.

So how does a Westerner go  about verifying if the verbal agreement being expressed is more than just “being polite”?

1) A very close and trusting relationship will inevitably over time enable you to get more “meaty” input.

2) Use a third party. If you have spoken to X and are not sure what she thinks, ask Y if X agrees with you or not.

3) Ask the same thing in many ways. Assume for example, that you have spoken to X to inform her that product documentation will be available only in English, and X must “manage the customer for at least a  year” until local documentation is available.  X has given an apparent yes.  To make sure, ask X, “Will the client think our company is arrogant?” “What are the risks?” “How will this impact your credibility”? “Please tell me risks I am not seeing”? “Would you prefer I change my decision?”

4) Listen to what is not being said. For example “that could work” is different than “that will work”!

5) Is body language affirming what the words are saying? If X is looking down or away from from you whilst agreeing, you have your answer.

6) Do not use cell phones or emails to verify understanding of complex issues. Be there in person.

A helpful glossary: 

  • This could work may mean-this won’t work.
  • I need to think about it, but it’s a good idea- may mean-rubbish.
  • I will do, may mean- I will do albeit I don’t agree.
  • Not bad, may mean- piss poor.
  • Yes, may mean-No.
  • Please explain, may mean- No.
  • Ok, may mean, -it’s your dime.

Share Button

Credibility can be more important than vision

Managers (especially those educated in the West) often feel the need to provide vision, hope and clarity of direction even in the most turbulent and uncertain waters. The managerial assumption is that people need hope and something to cling to. This managerial assumption has a cultural bias.One part of the cultural bias is that ambiguity needs to be mitigated because it is intolerable. Another part of the cultural bias is that stories should have happy ends, sort of “ all is well that ends well“ as a desired state.

Not all cultures have a need for management to provide this perceived sense of phony hope, especially if the provision of this hope compromises credibility of their manager. For many cultures, it is “ok` to promise blood, sweat, tears, criticism, temporary floundering and worse, as long as the boss is seen as credible,  technically competent, street smart and on top of things. The cultural bias herein is the overriding need for credibility, the willingness to let go of the perceived myth that we control our destiny and the tolerance for ambiguity in a hostile environment.

And thanks to GC for making me think.

Share Button