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.

Comments

Popular posts from this blog

Swimming against the tide 🏊‍♂️

Need a favor! I will not have asked unless it was urgent and required. So please I do expect your full support in return 🙏 Why?  What's Happening?  We have taken up a fight against all the big whales. It’s been a couple of years and the fight is getting intense. The market is tough because of Covid-19, the Ukraine war & the inflation in the USA. And of course, the whales are not liking it any better that we are trying to bring down their prices. So basically, I and my team at BillTrim are swimming against the tide 🏊‍♂️ and need a tonne of support to make it to the shore safely. We have recently pivoted our business model from trimming your bills and charging 25% to something quite more appealing & committed called " BillPay ". Now, we not only negotiate your bills but also keep tabs monthly to make sure they stay lean and paid on time. This is another step towards our goal of having BillTrim be free for all users. We have finally decided to get into fight mode a

Asking the RIGHT question

It's surprising how human communication is so flawed and no one is paying attention to fix it at the fundamental level.  Just like the languages in Technology are evolving, well so should our human language. But sadly the language we use daily, to get by, isn't evolving to simplify our needs. We do introduce new slang and some words to our vocabulary every year but that doesn't help much.  Because of this oftentimes it's not that the answers don't exist, it's just that we aren't asking the right question. And this is true when it comes to asking questions to a computer or a family or friends or colleagues etc. Even media houses seem to be intentionally ignoring this and becoming more of an entertainment+ gossip propagator instead of helping society find answers and evolve. Let me give you an example. Let's say we want to know an answer to: How do I lose weight? Well, the default behavior is we stop here and immediately start looking for answers. But inst

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