Centralization and Decentralization

Top management loves centralization. Rank and file prefer decentralization.

Why?

Imagine you are the CEO of a company with multiple teams. 

Teams need software to do their work. When the need arises for a software, someone from each of the team talks to the software company negotiates a price and procures the software. 

As a CEO, you observe this and see it as a duplication of effort – wastage of time, energy, and resources. You think you can improve efficiency by centralizing the software procurement process. Only one team will be doing the work – the software procurement team. Also, this team will be able to negotiate a better price due to multiple orders, remove redundancy, manage licenses better, and block unnecessary software spends.

Since software cost is a real expense, you can quantify the gain from this exercise.

black-ceiling-wall-161043

What about the downside?

Earlier, each team could independently procure the software they saw fit. Now, the individual teams have to go through the centralized procurement team and justify the need; this leads to back and forth and delays. The delay affects the cadence of work leading to employee dissatisfaction. Employee dissatisfaction leads to reduced quality of work, which in turn negatively affects the bottom line.

It is not easy to quantify the second-order effects of centralization, sometimes impossible.

The CEO, due to the broad nature of her work, sees the duplication everywhere. She also witnesses the expenses as a result of this; it is in her face. She wants to eliminate this and bring efficiency and cost-saving to the organization. Hence, she champions centralization. 

The rank and file are hands-on; they have to deal with the management policies to do their work. They experience the second-order effects of centralization day in and out. They instinctually develop anti-centralization spidey sense

Unline the rank and file; the CEO does not have the ringside view of the second-order side effects of centralization. The rank and file do not see the duplications the CEO sees because they do not have the same expansive look like that of the CEO.

Centralization efforts have a quantifiable impact. If not entirely measurable, you can do some mental gymnastics to get an idea.

The downsides of centralization are unquantifiable. The unquantifiable plays a crucial role in success, sometimes much more than the quantifiable.

Morgan Housel calls this the McNamara Fallacy.

McNamara Fallacy: A belief that rational decisions can be made with quantitative measures alone, when in fact the things you can’t measure are often the most consequential. Named after Defense Secretary McNamara, who tried to quantify every aspect of the Vietnam War.

Let us flip the earlier scenario. Imagine that the centralized procurement team does bring in efficiency and reduce cost, albeit at a minor loss of productivity. The software procurement expense as a whole is never on the mind of the rank and file; the rank and file do not look at it as closely as the CEO; it is not always on their face. Hence, the rank and file still view centralization as a bane, even when it brings in advantages.

The consensus is that a decentralized way of working trumps a centralized approach; this applies to the military too. Jocko Willink, a prolific US Navy Seal, champions decentralized command. 

There are valid cases for centralization, especially when the talent required to do something is in short supply, and there are legitimate gains to be had from economies of scale. But, when you centralize, think hard of the unquantifiable second-order effects of the decision.

Get articles on coding, software and product development, managing software teams, scaling organisations and enhancing productivity by subscribing to my blog

 

Working Hard To Be Lazy

The programming world heralds laziness as one of the virtues of a programmer.

Larry Wall, the creator of Perl, says – Most of you are familiar with the virtues of a programmer. There are three, of course: laziness, impatience, and hubris.

What no one tells you is that this laziness does not come for free; one has to work hard to imbibe this trait.

 

work-47200_640

 

In practical terms, what does being lazy translate to?

  1. Doing as little as possible, never more than needed.
  2. Instead of doing things yourself, delegating to well-established tools, libraries, and frameworks.

Let us work with some concrete examples.

You want to parse a CSV file.

You think: let me load the file, parse it line by line, and split each line on a comma. You roll up your sleeves and code this. You feel smug having solved the problem yourself without anyone’s help.

Trouble starts when the CSV you parse has a header. Now you add an if condition to detect the first line. Later, someone uploads a CSV separated by a tab instead of a comma. You add another if condition to accommodate this. Another person uploads a CSV which has quoted fields. You start doubting yourself and ask how many such “unknown unknows” are there when it comes to parsing a CSV?

Unknown unknowns are risks that come from situations that are so unexpected that they would not be considered.

CSV parsing might have a lot of “unknown unknowns” for you – a person who is not well versed with the intricacies of CSV format. But there are experts out there who know the CSV format and have written libraries to handle all the edge cases and surprises that it might throw. You hedge your “unknown unknown” risk by delegating the CSV parsing to one of these libraries.

In short, be lazy, do as little as possible, and delegate to well-established libraries.

“Fools say that they learn by experience. I prefer to profit by others experience.” 

― Otto von Bismarck

Let us consider another scenario.

You want to store a counter in a database. One approach is: when you want to increment the count, you get the current count from the database, add one to it and store the new count back in the database.

Do you see the problem with this approach?

What if many threads are doing this in parallel? You will end up with a wrong count. A better approach is to delegate the task of incrementing the count to the database by leveraging SQL’s arithmetic operators. This approach makes the counter increment atomic. Many threads trying to increment the count is no longer a concern.

By doing less yourself and delegating the task of incrementing the counter to the database, you have saved yourself from bugs.

Why is this hard work?

This sort of thinking does not come easy; you have to work hard to identify where what and to whom you can delegate the work.

Dunning-Kruger effect might have a role to play in this. We believe we are the experts and best suited to do things.

In the field of psychology, the Dunning–Kruger effect is a cognitive bias in which people assess their cognitive ability as greater than it is. It is related to the cognitive bias of illusory superiority and comes from the inability of people to recognize their lack of ability.

While coding, most of the time, you are solving a problem that someone else has already solved, probably in a different context. Be aware of your biases and always question: Is this something I have to code myself, or can I offload this to an already written, well established and well-tested library or framework?

“Learn from the mistakes of others. You can’t live long enough to make them all yourself.”

― Eleanor Roosevelt

Get articles on coding, software and product development, managing software teams, scaling organisations and enhancing productivity by subscribing to my blog

Image by Clker-Free-Vector-Images from Pixabay

The Million Dollar Question

What is the point of life?

All of us have pondered over this question. Luminaries have devoted their lives in the pursuit of an answer to this question. Philosophers have written voluminous texts trying to answer this question.

I am no Yogi, but that does not disqualify me from trying to answer this profound question. Beware, my answer might leave you with a feeling of meh.

During a holiday, a group of us friends played a weird game of football. We were randomly dribbling the ball, passing, and tackling each other – no teams, rules, goals, and referees. This pointless pursuit of the ball was fun.

What is the difference between kids and adults?

emily-morter-8xAA0f9yQnE-unsplash

Kids involve themselves in pointless pursuits. They are always engaged in one activity or the other. These consume them. We, the self-critical adults, try to see a point in everything. Few things consume us.

Give a cardboard box to a kid. She can keep herself occupied with the box for hours—an adult dreads at the thought of this.

When a child is young, she loves to draw irrespective of whether she is good at drawing or not. As she grows older, she pursues drawing only if she finds herself good at it. Enter adulthood, she becomes self-critical and continues her hobby only if she sees a point in it.

As an adult, try to remember the last time you were engaged in and consumed by a pointless activity.

A child actively indulges in role-play, creating stories in her head and acting it out. An adult passively watches role play in tv-series and movies. A child plays a variety of games. An adult passively enjoys sports watching others play.

As we age, we move from an active to a passive life. We try to seek a point in everything.

A child has no time to search for meaning. She is busy indulging herself in everything. The activity is the end; it is not a means to an end. I believe the same goes for life.

The point of life is not to search for meaning but to indulge in it. It is a pointless existence, and there is a joy to be had in understanding this. It is liberating.

Get articles on coding, software and product development, managing software teams, scaling organisations and enhancing productivity by subscribing to my blog

Photo by Emily Morter on Unsplash