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

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 (coaching, AI, productization) 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

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

What does Organizational Sloganeering indicate?

Sloganeering is the repeated use of empty words geared at influencing behaviours and/or attitudes.

Politicians use slogans all the time. Those of you who live in democracies know that slogans are often empty promises. Those of us who live in other types of regimes know how to decipher slogans and guess what the regime really means.

Organizations use slogans almost as much as politicians.

Most of us are less skilled at understanding slogans in an organization that we are in understanding political slogans.

 I want to provide possible directions of what sloganeering can indicate.

1-There is a gap between actual and desired behaviours that management does not how to bridge, so they are using slogans. Let’s call this sloganeering due to ignorance.

2-There is only a message that management wants to purvey; there  is no willingness  to commit resources to make it happen, so slogans are being used to obfuscate.Let’s call this sloganeering as malicious lipservice.

3-Instead of solving problems pragmatically, there is a corporate religion which is being promulgated, in the hope that more religion will cure the organization. Let’s call this organizational religious  fanaticism.

4-Slogans are used as imperialistic tools to conquer someone else’s territory. The massive  use of “big data” and “internet of things” are illustrations of this. Let’s call this sloganeering as weaponry.

Case Studies

  • The slogan: Worship your customer.

This company was not willing to invest in the necessary IT to serve its customers, so they invested in sloganeering internally and externally.

  • Let teamwork make it happen

This company hired managers who built empires and after several failed attempts to create more synergy, slogans are being administered, which makes “more sense” that replacing managers.

  • Quality is everybody’s job

This company makes very aggressive commitments to the market which are unachievable. So initial product releases are crap. Yet the CEO truly believes that everyone should own quality. BTW, the measurement system supports speedy releases.

In all the supervision work I do with consultants, I place a major focus on how to diagnose and use the company’s slogans to understand and deal with organizational pathologies.

One final word of caution. Has a company hired you to train its employees about how to implement its slogans? Don’t do it since the chances of being relevant are very very very (3 verys) low. But you sure can get burned!

Share Button

The Management of Blame by Senior Managers

In the natural course of doing business, things go wrong.

For some of the things that go wrong, people assume responsibility; for other things that go wrong, blame is assigned. The management of blame is part and parcel of organizational life. Blame is part of the game at all levels of the organization.

At the very top of every organizational/business pyramid, there are people with huge egos, and the management of blame is a tool that protects the valuation of the ego and the reputation of the very senior players.

As a matter of fact, managing blame is a critical skill often ignored by the starry eyed consultants who tweet and write about leadership. Many claim that blaming is characteristic of poisonous leadership, or a dysfunctional culture. I disagree.

My experience of 35 years in 4 continents suggest to me that almost all senior leaders have (and use) a vast array of political skills, one of which is the allocation of blame to others when things go wrong. Without blaming skills, you do not reach the top. 

Organization development consultants need to pay more attention to the allocation of blame as a generic built in characteristic of leadership at the top, because senior management teams “manage” the allocation of blame all the time, looking for a place to “park the blame”, and have someone else pay the fine.

I want to point out 12 frequent types of blaming used by people in senior positions.

  1. Pushing  unrealistic commitments
  2. Demonizing a certain figure
  3. Blaming one’s predecessor
  4. Picking on one member of the team without dismissing him/her
  5. Blaming the entire senior team
  6. Blaming the regulators (over-under regulation)
  7. Constant shifting of blame, like a swan casting water off it back
  8. Lack of employee “engagement”
  9. Making ambiguous demands and then, ex post facto, expressing dissatisfaction about the results
  10. Maliciously and intentional under-resourcing
  11. Over simplification  of complex tasks
  12. Appointment of incompetent people to do complex job

I have never encountered any senior manager or senior team where some blaming dynamic is not in place. Furthermore, the blaming dynamic often reflects the pathology of the organization.

The starry eyed idealistic consultant, armed with leadership models fresh from academia, avoids discussing the blame factor, and focuses solely enhancing accountability, ownership and mutual dependencies. By ignoring the realpolitik of senior leadership , the consultant will become irrelevant.

A professional practitioner understands what part of the blaming dynamic is changeable and works to mitigate the dynamic, whilst accepting that the treatment of the blame pathology can only go so far.

One final comment. In Asia, senior management tends to vocally blame subordinates far less than in Europe and North America, due to the obligation of the leader to appear to be compassionate. Blaming does occur, but it is much more subtle.

Share Button

From contact to contract-that’s a key time to diagnose

All of us who have studied and taught organizational diagnosis know a plethora of diagnostic models. But diagnosis should begin before the work itself actually starts and this post is geared to pointing out what we should be looking at in the very initial stage between contact and contract.

Paying close attention to what we learn about the client in this period of time often provides the context and direction for the diagnosis and intervention.

Here are five things worth noting.

1-Misplaced/wrong expectations about the nature of OD

  • Clients may overly define the scope of work and expected measurable “deliverables”, forcing you commit to something you know nothing about.

2-The ideological/religious nature of the corporate creed

  • Clients who lecture you about the corporate culture and ask you ensure that your work will reinforce the Holy Grail.

3-Lack of respect

  • Clients who cancel initial meetings again and again, often at the last minute, yet demand total flexibility on your part.

4-Do they want to change, or do they want to “use and throw away”

  • Clients who milk you for long and detailed proposals, again and again , with a very aggressive time schedule and then make you hurry up and wait for an answer.

5-Accessibility to key information; stakeholder analysis

  • Clients who block access to senior management before HR puts a stamp of approval on your forehead.

I do a lot of supervision with consultants who seek guidance when projects go astray. One of my first areas of inquires is “tell me about the very beginning”. Alas, often it’s all there from day one. And acting right from day one saves a lot of heartache.

Recently, I was asked to do merger and integration work. In our initial meeting, the CEO asked me what “model” I use, and if I could finish it all “in 6 weeks”. That was all I needed to start work.

So remember, work starts with the first call, and if you act appropriately at this stage, the chance of success increases.

Share Button

On Managing Lower Back Pain and Organizational Response to Crisis

 Five weeks ago, I was getting dressed to go to a weekly lecture at a History Club which I attend; as I tightened my belt, I strained my lower back. I was totally unable to move for 4 days, and now, five weeks later, I am on my feet and doing most things again, with the pain lessening slowly as time goes by.

This has been a  hard period because despite the fact that I am fit, getting back “up to speed” is so hard, although I have been exercising for decades. The learning process of managing this back pain is no less painful than the back ache itself!

The goal of this short post is to reflect about the process of my learning about managing back pain and organizational response to crisis. This post is meant as a metaphor.

Very quickly I learnt that lower back pain is a mass of symptoms with many (but no clear) cause. There is no real model of what treatment works and what does not. Sometimes walking helps, sometimes walking  hurts; sometimes rest helps, sometimes rest makes things worse. Sometimes it pays off to be mindful of the pain and sometimes it pays off to be distracted.

And symptoms do need to be treated, especially since the problem is nothing but a mass of symptoms. The term “just a symptom” makes no sense in treating back pain. A symptom is not a “just”. The problem has no root cause, but the symptoms are very real.

Treating back pain involves a certain degree of acceptance, a mindset of humility, many eclectic concepts and tools, some rigour and a flexible plan, which changes but does not overly waver. And patience is critical. . (I must admit that I am a very, very impatient person).

Now I look at the way that organizations respond to their pain: diagnosing root cause, changes of structure, engagement plans, new IT based processes, axing people and process clarity. Even when organizations respond with “agility”, they do so rigidly with agile theories and routines.

In organizations, those in charge KNOW what needs to be done. They project clear goals and vision. When things do not work, people/things are blamed because there is a need to prove the “fix it” plan is right.

The essence of my reflection is that while organizations are not individuals and this post is “just a metaphor”, I think that eclecticism, humility,  balancing the  polarity between plan & improvisation have a hell of a lot to bring to the table. And maybe positive changes in organizations come from a lot of little things being adjusted.

Share Button

Why internal OD departments are often unable to drive relevant changes? (The chicken shit brigade)

Just last week, I was called to a meeting with a CEO who wanted to discuss the ramifications of “being forced to unionize”. The internal OD department in this very same organization was deploying 360 degree feedback at the level of junior supervisors, which was as relevant as chiropractic treatment for a corpse.

This CEO’s HR department employs 4 OD consultants, all of whom are irrelevant in dealing with the strategic organizational issues at hand. Instead of being relevant, they are dealing with chicken shit.  Why is this so characteristic of internal OD departments? In this post, I will try to make sense of this matter.

Large, bureaucratic government organizations, public utilities and veteran conglomerates develop internal OD department as they age ungracefully simplifying “organizing” into a set of processes and products which can be “administered” by what the Russian and Israelis armies both call a “politruk,” that is a political commissar, serving warm corporate lemonade, or providing soft skills to middle management.

These OD departments generally report into HR, which saves costs. Because of the growing anxiety of HR management about HR’s positioning, not rocking the boat becomes a dominant element of HR strategy. And nowhere is this conservative stance more apparent than in an internal OD department. Instead of positioning internal OD to be be strategic drivers of change, the emphasis is placed on delivering and administering regime goodies cooked up by the company kitchen. This breeds phenomenal cynicism and lack of trust.

Internal OD departments generally implement such routine tasks as the administration of surveys, and packaged training for middle management, commission outdoor training or perhaps force feed “engagement”, whatever the hell that means. As Levis Madore points out in comments section below, “castrated internal OD functions quickly become eunuchs who pose no danger to the executive levels as they proceed to (administer) cutbacks in the HR department which gradually (are)  transformed into process boxes with mere transactional tasks (to perform).”

The internal OD departments control access of junior external OD  consultants to the company. Very often when there is a budget to hire externals, they hire OD technicians who are controllable, inexpensive and slavishly  loyal. 

As a result, more experienced OD consultants are often commissioned directly by very senior managers, who ask these senior externals to “work in coordination” with the internals, or more often ignore them. Both scenarios are often ugly.

When does an organization need an external OD consultant? In my mind, the answer is counter-intuitive. A skilled internal OD consultant (not an OD product hack or what the Chinese call a barefoot doctor 赤脚医) is needed in the initial formative stage. That’s where organizations can get the bang for the buck, especially in organizational design.

However, very often start-ups in their formative stage commission external OD workdue to high cost, and end up “bringing the OD work inside”, after due castration by the HR manager, who may have been a senior admin or office clerk at the very beginning.

pt

The inspiring  politruk

Share Button