Skip to main content

Three Bosses


Often priceless insights come from things you resist in doing in the first instinct. This blog briefly describes one such lesson learned over the past quarter.

Been an avid observer, initially, my gut reacted with aversion. I was more than convinced that having more than one boss is just a bad structure in any organization be it a fast-paced startup like the one I head or be it any other medium or large scale organization especially in IT.

I was empathizing as always and putting myself in the employee shoes and concluding it as a bad idea. Having two bosses was annoying but imagine having three, ouch!! simply nightmarish, it must be.



Note: Boss = Supervisor = Manager = Team Leader

Though by not shouting out my gut feelings, I let the situation rolled in for a while. To my surprise what I experienced, did shock me. I observed that most employees outgrew their growth from their previous experience in a very short amount of time.

The employees were exposed to three distinct styles of management. At first, sure, it must be frustrating but trusting each of their bosses intentions and foresight, they learned things at thrice the speed they normally would in any normal setup. Three bosses with three approaches, three ways of planning, three ways to encounter questions and discover solutions. This was an interesting setting that we stumbled upon unintentionally and which ended up teaching me something that normally will be unthinkable.

On the flip side, the three bosses scenario directly points to lack of processes & lack of communication between and within all tiers. I am deeply appreciating the importance of "clear" communication day by day. As per my belief, among all the soft skills, communicating clearly is one of the hardest to master.

Now please don't interpret me wrong. I am not promoting to have more than one boss in all cases. Rather am simply indicating that if the styles of managing and leading are different, then the outcome of having more than one boss,  may surprise you positively. Thus I will request you to evaluate using the scale of "employee growth" and give this assortment a chance.

Besides, to be fair, over time we did sorted things out and "EMPOWER" all the right persons so that generally an employee is supposed to report to just one boss and not more. Though, once in a while, it's ok to stir the pot, considering the benefits it reaps on both sides.

To end, learn to clearly communicate and learn to grow & empower your juniors & colleagues. The after effect is stunningly beautiful.

Labels

Labels:

Comments

Post a Comment

Popular posts from this blog

SiLence: A Mysterious Language

When I am alone and quite or else in a group at a place where words have ceased to exist it’s precisely in those moments I feel an existence of a person name "NoBoDy" or at least that’s what I named him or may be her, I am not sure of its gender. "NoBoDy" speaks in a language weirder then its existence. I named it “SiLence”. "NoBoDy" even yells sometimes, just like us. And "NoBoDy" yells in so hard that I always try to switch to our action mode , the one which we are so much used to, and so are completely unconscious about, most of the time. I mean things like listening to music, thinking, planning, gazing at something, playing games, reading etc in simple words. I figured out that this makes it stop yelling. And so I try my best to kind of keep beating it every now and then, by using our action mode technique. "NoBoDy" belongs to "No Country” following “No Religion” and it’s the purest form of religion I have come to...
1 comment
Read more

ASSumption of SCALE

During a recent Skype meeting with one of our lead developer, I heard him say "what if we have 100 times ... " Now don't get me wrong, I have been there and done exactly the same, various time myself. But not having been involved directly, gifted me an opportunity to look at the software development process a bit objectively, over the past year. And I have come to this, unshaken realization, which is to "stop daydreaming on SCALE" and consequently make costly assumptions that will leave its ripple effects throughout the project. Unnecessary "Tech Debt" in other words. Imagine a 10-year kid planning on opening a lemonade factory after selling just 10 lemonade, of which 5 are bought by own family and friends. This is not only naive but also super dangerous thought that developers think of more than they should, especially, young ones. I will like to remind and request all startup developers to remember a principle namely "Do Things that Do...
1 comment
Read more

How a human mind works - A machine perspective

To understand the root cause of any situation, drilling with "5 whys" is my default approach. When I am curious and doing this exercise in my mind, I am not sure about counting the number of whys, to be frank. The "5 whys" is pretty much a natural flow of questioning that I've been doing without much effort for years.  Recently I was having a conversation and we were discussing how to change an outcome. This question was a trigger for me to think about the process of decision-making without our minds and how it leads to an outcome. Let me try to put my thoughts in a structured way. Imagine a machine that takes inputs and gives an output. And it has various stages in between. Our mind is this machine. The stages are Inputs, Enhancing the Inputs, Judgement, Decision, Action, Outcome and Experience. Let's understand each of these seven stages. Stage 1: Inputs     This stage represents the raw inputs that the mind is receiving. It can come from many sources the ...
Post a Comment
Read more