A personal “congratulations” to John Scherer

John Scherer will receive ODN’s Lifeline Achievement Award for 2015.

This blog and my Gloria satiric blog exist because John Scherer pressured me to write. Thank you John.

The most useful critique of my global OD work and my style has come from John. His comments have had context, depth and John’s  intent is to help and support. When he speaks, I listen.

John has boundless energy. He inspires, he innovates and he learns, all the time. John has a heart of gold, a heart bigger than he is. John is a giver.His clients are very lucky.

I am a better consultant for having John as a colleague. I am enriched for having him as a friend.

And he truly deserves the recognition he is getting.

Bravo, Johnny boy, from Gloria and me.

 

Share Button

Responsiveness to email and culture

Astrid from Munich, Neta from Tel Aviv and Harry from Newark are on the same team.
When Astrid (Germany) gets an urgent request via email from Neta or Harry she puts together a detailed and full answer and gets back to the sender within 3-5 days.
Harry (US) regards Astrid’s email replies to urgent requests as too long and detailed. He would have preferred a shorter answer, in “a bit less time”. Harry thinks that 48 hours is “enough grace for something urgent”.

Neta (Israel) expects a daily update by email from Astrid as to the status of her urgent request. She views Astrid’s approach as “totally non-responsive”. “By the time I get her answer, “I forgot the question”. When Neta gets an urgent request via email, she puts everything aside to provide the answer, often backing up her email answer with a text that the urgent request has been answered.

Harry “puts time aside” for urgent requests, but does nothing after 7pm and nothing on holidays “unless the world is coming to end”. Harry believes that were people to plan better, some of this urgency could disappear.
Neta does not like to plan at all and believes that planning is an empty ritual.
Astrid could spend all her time planning and wishes that Harry and Neta were more orderly.

Share Button

How to do OD consulting with a startup

This post will address how to go about doing OD with start ups and their founders.

At face level, there is a good match between the value proposition of OD and the needs of startups.

  • Startups have talent, flexibility, a high level of engagement and do not suffer from the chronic ailments of older organizations.
  • OD provides a development platform (mindset, concepts, skills) to support the new technologies/products which are being created. Sounds like a dream world to me.

However, founders are generally not receptive to OD. The very qualities of the founders that enabled them to become founders, prevent them from proper leverage of OD. The founder, who essence is breaking down the barriers of innovation, often views “organizational issues” in one of two ways:

1) Organizational issues are banal, ‘a matter of common sense”, (meaning the common sense of the founder.)

2) Organizational issues are a chance to reinvent human nature; “I will create an organization which will change the way people organize.”

The constraining forces inhibiting growth of a startup are often organizational and behavioural. Startups have ideas, technologies and great people; frequently they have a detailed road map of the development of the technological solution they are engineering. Yet founders of startups do not generally address the issue:” what type of organization do I need to develop to support these great ideas?”

Founders often react poorly to OD consultants. Not only are many founders arrogant, many OD practitioners lack the technical savvy to gain respect.  OD consultants tend to be much older than founders, which add more complexity since the OD consultant can be seen as the “parent”. (I am 71 and many of my clients are in their twenties).

Generally founders appoint the admin to be the first HR manager, along with facilities and car rental! That certainly closes the HR route to work with startups at an early stage.

Often, investors who want their founders to get grey haired organizational development support put OD consultants on the Board, or attach some strings to the money that they invest making OD “compulsory”. This approach certainly limits the trust that will develop between the founder and the OD consultant, although I remember two cases when that approach worked.

OD in startups generally begins when the founder steps aside to becomes CTO and brings on a professional CEO . The struggle between the founder and the new CEO is a great place to start an OD project. 98% of the work I do in startups began this way.

Once a project starts, I suggest the following emphases:

1-Ensure that the development of the organization parallels the development of the organization 6 months down the road

2-Develop a dialogue and an action plan around developing scalability. (Anyone who wants to know how this is done should leave contact details below).

3-Develop a plan whereby the organization does not need to either enslave itself to the initial group of employees, nor push them aside. There are many ways of doing so.

4-Develop a life cycle dialogue and action plan about people, skills, “mores” and structuring.

Follow me @AllonShevat

Share Button

Leaderless teams are a bullshit fad

I am old enough to remember plenty of management fads which claimed to be elixirs for all the ills of organizing.

I probably remember “TQM” (Total Quality Management) best of all, because of its vast popularity despite it being total nonsense.  Indeed, within just a few years, “time to market” had relegated “quality” to the back seat.  And if you think quality is still a driving force, take a flight or call a mobile service provider!

I smell a new TQM skunk! In social media as well as academic journals, there is a lot of vibe about the lessening prominence of leadership as well as the need to focus on enhancing self-management for both the sophisticated nerd and the average Joe.

I have worked with many organizations which put a high premium on leaderless and self-management. Without an exception, they all “outgrew” this or died from decision paralysis and astounding mediocrity.

This short post will provide my perspective on this new religion-de-jour!

1) Leaderlessness and self-management have a manipulative basis.

  •    Empowered by information technology yet bogged down by ERPs and mistrust, it may be sexy to espouse the value of self – management, but it is cunning to an extreme. It certainly does create someone to blame when the system does not work too well.
  •    Power is concentrated in the hands of the ruling class, the tycoons, the powers that be or whatever. A call to “leaderlessness” and self-management sounds to me a general telling his front line troops to “develop the strategy and battle plan”, and then shooting them in the back for being cowards.

2. Self Management in the ERP hell.

In many organizations, ERP has replaced common sense and initiative, and serving the process is so dominant that there is almost no room for either good leadership or self-management. So let’s put the blame where it lies, and not promote the false messiah of self management.

3. Psychology

People need leaders to admire and hate. I see this as a self-obvious truth. Am I too old? Out of touch? Or is someone peddling a new fad?

4-Complexity

As the world of work became so complex and high speed, integration between disciplines and perspectives becomes absolutely critical. This integration does not happen by itself, because of ego, power games and bandwidth issues. Leaders drive integration by choosing the right people and leading/managing them properly.

So yes, I do see leaderlessness, holacracy and over dosing on  self management as a new fad and in many cases, pure crap, misleading, manipulative and/or irrelevant.

But it sure is going to be lucrative.

And an afterthought- Organizations and people need leaders; employees, equipped with an end to end perspective of what’s going on. That does NOT negate the fact that  yeam members must learn to  work with their peers to resolves issues without undue escalation.

Share Button

Let’s get real about “agility”

There are several major reasons that organizations are not flexible enough to adapt to changing circumstance. In this post I will examine three, and suggest what needs to be done to achieve more flexibility.  (There are of course other reasons, like bad politics. which I will not deal with in this post).

1) Too much chaos

Sam, Lisl and Ethan’s company started in a garage. Sam wrote the key algorithms , Lisl raised money and Ethan looked for a strategic partner. All 3 wrote code. All decisions were made together by consensus.

Their company now has 50  people with 4 major  subcontractors. All decisions go up to Sam Lisl and Ethan who still manage the company like 3 nerds in a garage. Decision making is a nightmare, locked in the free-spirited “we-all-decide-everything” mode. (Last week they had a one day meeting about with which travel agency to work).

In essence, their company has become the very essence of rigidity, with decisions lagging by 4 months.

2) Too much bureaucracy

I will not use a case study to illustrate this type of rigidity in a large  company . We all know it all too well. These organizations have an ERP which has replaced common sense. The work flow  is a nightmare. Every minor issue generates tens to hundreds of emails, as anxious staff make sure that they serve the process and transfer blame backwards or forwards. It is very hard to do very simple things, and impossible to do anything creative. Everything takes much much longer than it should, and the organization (often assisted by internal OD) is obsessed with process improvement.

3) Organizations which have adopted agile methodologies.

Prompted by “best practices”, blind emulation of technology and pure stupidity, there are a plethora of “agile methodologies” available to organizations who want to apply agile coding practices to the art of organization. (In some ways this reminds me of western politicians who want to promote liberal democracy in the Middle East).

An agile methodology is an oxymoron, like thought leadership. In the quest to loosen up from too much or too little order in order to gain more flexibility, organizations embrace yet another cause of rigidity,  a “methodology”.

Summary

Organizations are rigid because they have too much or too little “order”.

An agile methodology is self defeating.

Organizations whose rigidity stems from chaos need order.

Organizations with too much order need less IT driven processes, digital detox and massive injections of common sense. Yes, common sense.  Ni plus ni moins.

Agile organizational methodologies should be replaced with smart hires, lot of room for common sense, and small teams (as geographically consolidated as possible) that meet face to face with their smartphones off.

 

 

 

 

 

Share Button

The dangers of “organizational utopianism”

A major component of organizing is balancing mutual dependencies between people and functions.

The fulfillment of mutual dependencies is the very essence of successful organizing, yet the dependencies which enable organizing always create anxieties. I am fully aware that people skim articles, but the stuff in italics is really important! 😉

There is no way whatsoever to eliminate the inherent anxieties of organizing; they can only be mitigated. Any attempt to “cure these anxieties” is organizational Utopianism.

Political utopianism, be it communism or nationalism, has bred disaster. Bread lines, racial hatred and massive use of force are the direct results of ideologies which purport to have all the answers. (I will avoid discussing the “salvation” promised by religious Utopians.)

In the realm of OD and change management, there is plenty of Utopianism, which expresses itself in stylish one size fits all models, universal truths and so called shared values. Utopian solutions come along with high priests who implement these total solutions.

Organizational utopianism is no less dangerous than political utopianism. Utopian organizational solutions breed cynicism, disengagement, sloganeering (which castrates communication) and exploitation. Total solutions for organizing end in disaster.

Organizing is very complex at the emotional level. There are no quick fixes, none whatsoever. An awareness of the inherent anxiety bred by organizing itself is probably the most important tool in the arsenal of organizational practitioner.

Share Button

Working with highly manipulative managers

Often senior managers are highly skilled in the act of manipulation.  As a matter of fact, it  is one of the very reasons that senior people reach the top.

Highly manipulative leaders/manager often commission consultants when manipulation is no longer effective. Most frequently this happens upon being promoted, or when there is a need for rapid change.

Influence and manipulation may look similar but there are major differences-

  • lack of intentional functional transparency
  • lack of consistency, e.g, measuring X and demanding Y. (Talk quality and measure speed)
  • built in need for escalation to get things done (very very common)

I do not want to quibble about what manipulation is because, like pornography, we know it when see it.

In this post I will give 6 guidelines about how to work with highly manipulative managers who commission consulting work.

  1. Be open about your own agenda. (I want to make money. I want to build my reputation, I hate failure) Exposing agendas models migrating away from manipulation.
  2. Do not be judgmental about manipulation. The client must understand that while manipulation may no longer work, it is not useful to  knock what he/she thinks brought him up through the ranks.
  3. Use the here and how to “expose” each and every manipulation that your client uses with you.
  4. I have found use of paradoxical interventions most useful with this population
  5. Provide useful  alternatives to manipulation, acknowledging that the alternatives to manipulation have unwanted side effects. (Kipnis and Pois are still relevant).
  6. Be fully transparent. Transparency is the ultimate mitigation mechanism of manipulation.

Case-

Helmut commissioned me to work with him on implementing an organizational change which is moving too slowly. Helmut has been  CEO for 6 months, and previously he was head of the European Sales Division.

Helmut has succeeded in every role he has had until now. His results have been  impeccable. This is no longer the case.

Helmut plays his various team members against once another. He gives the same task to  5 different people.He is purposely vague so that everyone is always guessing what he means.

In our initial meetings, Helmut was vague about what he wanted. Two other OD consultants were also involved, all with vague overlapping mandates. Helmut blamed me that I was not practical. In a long and heated 2 hour discussion, I called him on his manipulation and resigned. He re-hired me two days later, and he even  oked that I publish this post. Things are moving.  But I watch my back. 

Share Button

Have you sold your soul as an OD consultant?

Preface:

Before you start reading: Although this is a short post, several links are provided. These links provide illustrative and satirical support for the point I am making.The links are well worth reading.

The crisis OD is facing has caused many practitioners to sell their soul. Now “selling one’s soul” is a tough thing to admit, and we all probably look at other consultants and claim that they, not I, have sold out.

So I prepared a short quiz that will indicate the degree of having sold out.

There 6 signs may indicate the severity of the sell out. I am not going to define what this means, because, like pornography, we all know it when we see it.

The Quiz:

If you agree with 3 of these statements, we know what profession you are in, so please quote the price.

Share Button

Chronic Diseases of Organizations

 Opening Comments

Very much similar to people, organizations tend to have chronic diseases.

These diseases are a function of

  • life cycle of the organization,
  • CEO’s who have lead and founded the organization,
  • domain in which the organization operates,
  • degree of regulation,
  • random factors that we do not understand.

The goal of this post is to illustrate some of the more frequent chronic diseases and suggest ways that OD can be harnessed to address (not cure) these ills.

Many of the chronic conditions listed below may appear in all organizations, yet only a  constant recurrence of the same ailment make it chronic.

2-Chronic Diseases, Symptoms and Possible Causes

  • Constant Reorganization

Symptoms-the organization is always preparing for a reorganization, implementing a reorganization, or after an unsuccessful reorg

Possible Causes– Incompetence, buying time, creating a cloud of uncertainly to enable blaming.

Example-K has a product that is no longer competitive, although they still have one legacy product which will make them money for decades. New technology initiatives are killed on arrival. The organizations has had 7 reorganizations in three years.

  • Processes Nazism

Symptoms– constant clarification of process, roles,  responsibilities, charter and the constant pursuit of clarity as the ultimate elixir.

Possible Causes-a desire to define away complexity; inability to implement teamwork

Example-P has technical presales in Holland, Sales in each geography and Product Management in Texas. All 3 functions mistrust one another. They have been defining roles and responsibilities for 12 years.

  • Measurement-ism

Symptoms-measure everything, if possible on line

Possible Causes-mistrust, IT-gone-mad, efficiency as strategy

Example-C has been loosing 200,000 end users yearly for five years due to a change in regulation. Performance indicators of the service team have been updated 33 times in the 4 years “to find out why people are opting out” of the service.

  • Sloganeering

Symptoms-constant window dressing and perfuming the pig to make things look better than they are, hiding and denial

Possible Causes: monopoly, government intervention, too much regulation, high level of media scrutiny

Example-a police force, loyal only to an elected official has been getting bad press for 8 years, due to racism, brutality and corruption, all which serve the mayor’s interest. Massive money is poured into internal communication and “image management”,

  • Silo-ism (the ultimate chronic disease, like back pain)

Symptoms-lack of transparency, maximization of sub systems

Possible Causes: latent or overt fear of coup, need to allocate blame, paranoia at the top, divide and conquer as a religion. measurement system, poor staffing

Example-A functional organization lacks end to end ownership of client issues. A very dominant CEO (and his father) have maintained control by “divide and conquer”. The CEO complains of siloism, although he constantly ensures that his managers squabble about ownership issues. He fires one executive every 5-6 years.

3-Guidelines for the OD practitioner

In order to address an organizations chronic illness, there are certain precautions that OD practitioners much factor into their interventions. After all, there is no need to “amputate a lung” due to chronic asthma.

Here are few guidelines that may help you treat chronic illnesses properly:

  • Understand the history of the organization
  • Understand the latent function and ongoing secondary benefit of all dysfunction, and that will be decisive in understanding if the illness is chronic or not. For example, the benefit of process Nazism is to avoid dealing with trust issues.
  • Set proper expectations, ie- mitigating the dysfunction, instead of curing it
  • Less intense care spread over time, instead of an extensive effort to drive change
  • Pain management, ie, adjustment to the pain
Share Button

Let’s look at OD like developers, not application engineers

One of the lessons I have learnt in my decades of OD work with high tech companies is that the “next generation” of products and services does not usually emerge from the same people/teams working on the present breadwinner.

A power structure develops around breadwinning products  whose role it is to preserve the centrality of the mind sets and skill sets which gain value from the breadwinners’  predominance. Hence, new ideas which challenge the current paradigm are often resisted.

The same phenomenon effects OD. The current version of OD is “stuck”, yet protected by the dominant practitioners, gurus and universities who benefit from the present versions of OD.

OD will not renew itself by gawking at the past or fiddling around with new packaging of old ideas, nor via peddling “applications” based on the same “core code” of the old OD, a professional dominated from day one by western values and western assumptions about human behaviour.

There are several core issues that can hasten the “realignment of OD with future reality”.

   1-The acutely diverse nature of the global organization which simply cannot adapt itself to western values. (openness, authenticity, personal development, empowerment)

   2-The massive dysfunction stemming from a severe overdose of IT driven business processes. (At present, OD cross dresses as change managers, ramming these processes into place).

   3-The alienation of the soul in the work place. (The engagement products which OD provides to deal with this are a pathetic bad joke)

Next generation OD will not be conceived in universities. My experience is that learning OD in academia is almost useless, at best. Nor will OD be reinvented by most current practitioners, who serve as “application engineers”, administering OD products, often mindlessly. naively, cynically or out of self preservation.

I believe that OD can benefit from emulating other professions which focus on anticipating future needs, not serve as an order taker for elixirs which address current aches and pains. In other words, renewing OD is an exercise in system architecture, not engineering.

These are very initial thoughts, and I will modify this post as my thoughts become clearer.

Share Button