Don't take your job too seriously

As I ramp up on my other product, I am faced with two very different teams. One is huge, spread out, with a large budget, and complex operations that need to be set up from scratch; the other, small, agile, and with relatively simpler operations. One has such complexities that most sub-teams prefer a clear-cut direction and do not want to bothered with the issues across teams. The other has people who are very engaged in every aspect of the product and proactively involved in areas beyond their core work. The only thing common among them is that they are both startups of some sorts.

Both, are ideas that are coming to market in their own styles. And both require dealing with in slightly different ways. However, some things stay the same (and work like charm). Like most engineers (by training), I tend to deal with complexity with process. But while process can make things easier, they do not help deal with personalities. While dealing with atleast 6 different personality types in a single day, things can get messy. And in dealing with this, I have hit upon the perfect mantra. If I had thought of this when I was younger, my previous jobs would have been much easier.

While your job is important, it is not that important. Maybe just maybe, we want too much control in our jobs. We want to be able to control all the things that our position implies we do, we want picture perfect roadmaps, and teams which work like clockwork. And since people (or rather all of us) do not work like that, the trick might be to just let go a little bit. Trust that things will sort of work out the way we think. Plan but not over-plan. So I let go of certain things, and share responsibilities a bit more. Trust people to make up on those roadmaps which are sliding. Let someone keep a bit more control, while you cede a bit on your end. The end result: A bit more relaxed team and a calmer me. There are lot of people around me who are biting their nails and worrying about things. I believe that if we really want to lead, we need to stay calm and composed. Even amidst chaos. In fact, I propose that to be effective in today's chaotic product development environments, the prime capability one needs is composure.

Maybe the trick is to remember that we are all in this together and there is no clear-cut definition of what we do or what we need to do. I realized that by maintaining a balance between process and controlled chaos, definition and ambiguity, control and lack there of, I was calmer and much more effective at my job (successful? I do not know yet).

Maybe, Ladies and Gentlemen, the idea is not to take our jobs too seriously.

PS: On a crazy travel schedule for the past 4 weeks. Have visited Bombay, Delhi, Bangalore, New York, Boston among other places. Right now, all I want to do is to head home and sleep.