Saturday, June 19, 2010

Music !

Dreamy nightmare...
scary angels
Friendly demons,
Balmy suns,
Scalding nights,
real imaginations
imaginary reality.
Restless soul
Trapped in strife,
cant explain,
It isn't who I am !*
Dream a little,
Jailed soul
soaring free
Life isn't
reams of reasons
but, notes... ...,
bars of rhymes...
Cant explain,
That is what,
I'd yearn to be !
* Two lines, as tribute to Pink Floyd :-)

Saturday, March 13, 2010

The Flow

Today Neel was pensive. That’s a bit of understatement; he has been quite pensive and lost for a while. "For a while" is a bit of understatement – that being a few years. He was driving today in the peak Bay area traffic around 5PM; where opportunities abound in the Land of opportunities. I’m being cynical, as usual, he thought. The ‘as usual’ had become a norm in those afore-mentioned few years. As he slowed down at the intersection, he wondered if it symptomatic of the proverbial cross-roads he seemed to be at. If he had a say today, he’d be back at work, generally procrastinating or checking out what was happening around his home town, surfing the internet; or back at his large stylish house, seeing movies that he had enjoyed growing up; or those lovely mellifluous Rafi’s or P.B.Srinivas’ songs.

Neel a.k.a Neelakantan R Iyer, to the outside world, was living the American dream and had arrived in life. He had 4BR house in the Palo Alto, 3 cars; he himself was driving a Beamer. Or whatever, he thought! His lovely wife – when was the last time, they had a good conversation – Pam (a.k.a Parimala), who had a career of her own now; and two children – A girl who was a senior in the High School – was it 12th? Or as he would have said in his days – “My name is R.Neelagandan, 10th Standard B section” in his small town back in Tamil Nadu. Today, as much he tried to avoid, he had to pick his daughter from the special math class that she was going to a tutor on the south-side of the town - he had not wanted to face the very uncomfortable silence that fills the chasm between them and compensate with banalities. Pam had an important meeting that she didn’t want to miss and had asked Neel to do the chore, as an exception to their division of labor. So here he was, down the 85S in the start-stop traffic, driving from rote without really concentrating…

As he got into the steady moving traffic, his mind once again rewound to black and white… He had married Pam after both the families had matched them up; He had stars in his eyes and dreams in his head. The American dream. He was a hot-shot techie who was very good in what he did. It was a great time, a time that he always looked back in fondness – they were both genuinely happy in each other’s company and made plans. Work had been good, in fact, feel-good too. Then life happened, he thought wryly – they had Shreya, their daughter; Pam had put her own plans on hold. Pam was very keen to stay with the kids in their formative years. As Shreya grew up, she was a bundle of joy for Neel; she was there when he left for work and then made sure she was awake when he came back from work, however late it was. He adored her; his life seemed so complete and blessed when Sharan arrived. Pam spent another 5 years with him. As both the kids started school, Pam started on her career – she went to school, got a degree and joined one of the few start-ups. That was nearly 10 years ago. He was growing fast in his company; from an individual contributor, he climbed the ladder of Technical lead, architect and was behind some of the company’s key innovations. . He was busy, she was busy and the kids were busy. But slowly, something gnawed at him. He wasn’t sure what it was initially… Was it burn-out? Was it lack of time together as a family? Pam now is in a place in her career that he was when he was growing rapidly and feeling the glow. He never found the kids at home – they were either some class or the other; or were at sleep-overs. He often came to an empty home, pottered around the kitchen, and cooked something up for himself and the family. They hardly had dinner together. If they were all at home, they were all doing their own thing. His attempts to get all of them together were all thwarted by lack of cosmic alignment of everyone’s calendar! Or my feeble attempt, rather.

Neel got off the free-way and slowed down at the stop-light. It was red. Was it a symbolic message? Am I the Bruce Nolan? He waited behind several cars for the light. The light turned green, he eased into the traffic again. He was in the back-roads. Back-roads he thought aloud… or cross-roads… Neel’s career had hit a plateau. He wasn’t certain (and possibly didn’t care) if his sense of ennui was due to that; or his ennui created the career slow-down. He was also increasingly finding himself not able to connect to materialistic culture – yeah, it is easy to be not materialistic, when you drive a beamer! He had that inner urge, overwhelming of late, to reconnect with his roots – people, friends, language. He wanted to be able to connect to his parents, his friends, his childhood memories back home. The last time he was back in India, he had really enjoyed the time – connecting back with his father with their usual arguments and meeting his friends over a drink! He had instantly felt at home with those guys. He had started reading tamil literature; also tried and flamed out spectacularly in teaching in Shreya and Sharan Tamil. He was hoping this would be a project to reconnect with Shreya. Shreya had rejected the whole process outright, leading to a still-born project. She had just moved away from him during his hectic days and she had her own ideas now. He had heard Pam talk about some boy-trouble at school, a boy of apparent Indian lineage. Neel didn’t probe too much since he was sure if he knew all he would certainly not like what he hears.

The American dream had become a bit stale and rudderless. He had a sense of longing for something that he couldn’t really pin-point. He felt like a cast-away, without a sail shifting in the high seas with no frame of reference and no control. He and Pam talked a couple of times of returning. But it always fell through and they had, in the mean-time acquired the citizenship. He was an American; and his last tie to being an Indian officially was cut off, as he returned the Indian passports. Try as he may, he just could not relate himself to be seen an American. He tried the local Indian, South Indian, Tamil and micro-org meetings and gatherings – the ersatz culture left him more restless. Neel wondered all this restlessness stemmed from to the fact that he was culturally adrift and when the end comes, he would not know where he belonged. He yearned to be in the place where his heart knew it belonged. The only solace was he felt a reasonable sense of stillness, when he visited the temples in non-peak hours; he preferred to go alone there; he’d pray quickly and sit there for long. He wondered if it’s that hope in the faith (or was it faith in the hope?) that kept the sanity sometimes and do, eventually, what is pragmatically possible given where he was.

Neel smiled wryly, as he turned the corner - have I?; it seemed his life here matched the quote from Jack Higgin’s novel Eagle has landed – “Son, you don’t play the game anymore, the game plays you”. He knew that he was just a Bot in the flow. It was like an assembly line that he has gotten onto and some connected sets of strings had taken over his life; and he just have to go with those pulls and pushes in the flow, that he had no real control over.

He parked in front of the building where Shreya’s class was on. As he waited, he saw her coming out with a boy talking animatedly – they had stopped, Shreya with her back to him and continued the conversation – it was obviously not pleasant. Then Shreya turned abruptly and walked towards the parking lot; she was crying – and she was surprised to see him instead of her mother. She quickly and furtively wiped the tears off and got into the car.

He looked at her, unsure if he could ask what was wrong; instead he smiled and asked her how she was. Shreya, responded with a simple ok and turned her face away. He guessed she didn’t want him to see her tears. He started the car and eased into the traffic; as he exited into the free-way, he stole a glance at Shreya; He reached out and smoothed her hair; she smiled weakly and looked out – she was still crying. He had a sudden urge to hold her as he’d done when she was a small girl and talk to her and if he could help. But he just couldn’t…

…Instead he entered the high-way, did the dance with the traffic, maneuvered himself to the car-pool lane on I-85; it was now automatic, the strings were activated – the flow would take him to his 4BR, 3B, 3Car Garage house. And to the next day. And beyond.

Sunday, February 28, 2010

Book Review - Checklist Manifesto

I had recently bought the Kindle, the e-Reader from Amazon - the first book on it was Atul Gawande's "Checklist Manifesto" - this book was recommended by two people I know, one from work and by another friend of mine from college, who I had reconnected with recently. What interested me in the book was the reviews that talked about resolving complex problems. I've personal interest in the theory of complexity and have my own perspective of it.

After reading the book, I believe there is a slight distinction - there are problems which are "complex" in nature in trying to find solutions and then there are problems that have known solutions but the complexity is in execution. The book is about the latter part of it.

Interesting part of it is Gawande' talks about Brenda Zimmerman and Sholom Glouberman (Univ of Toronto's) work on Complexity... Its another matter that it is very similar to Cynefin framework (that had interested me significantly and made me write my perspective on solving problem in complex space). Gawande, in his book, introduces the concept as following: systems can be understood as being simple, complicated, complex. Simple problems, such as following a recipe or protocol, may encompass some basic issues of technique and terminology, but once these are mastered, following the "recipe" carries with it a very high assurance of success. Complicated problems, like sending a rocket to the moon, are different. Their complicated nature is often related not only to the scale of a problem, but also to issues of coordination or specialised expertise. However, rockets are similar to each other and because of this following one success there can be a relatively high degree of certainty of outcome repetition. In contrast complex systems are based on relationships, and their properties of self-organisation, interconnectedness and evolution The metaphor used for complex systems is like raising a child. Formulae have limited application. Raising one child provides experience but no assurance of success with the next. Expertise can contribute but is neither necessary nor sufficient to assure success. A number of interventions can be expected to fail as a matter of course. Uncertainty of the outcome remains. You cannot separate the parts from the whole.

After classifying the problem-types as above, Gawande goes ahead and calls the challenges he describes in his book, as complex. Its erroneous since the most problems he describes are complicated - i.e., they are in the knowable space (as per Cynefin framework) and it just needs diligence in execution. The "complexity" in execution is a function of two things - the number of tasks that needs to be done without any errors, in the right sequence and short time duration within which those tasks needs to be executed...

If you let go the above issue, I'd still think his book is worth a read - he tells a good story. He has quite effectively woven a good front in building up the theme and then presented the solution. He could have been bit more concise, but I guess he was driven by a page-count-need ! Gawande's view is that in a complicated problem, due to its magnitude, the difficulty lies in getting the order, interfaces and hand-offs right amongst equals who bring in different competencies to the execution of the solution; A very visible and concise cook-book, not the one that tells what to do (which the experts usually know), but the one that is a gentle reminder/nudge. He calls this a checklist. I, personally agree to his solution. When you are up against time and pushed to do a number of actions (in a sequence that is essential), I'd rather have a guide (or a checklist) that helps me to do those. Personally, I'd rather take any guidance that would help me get the syntax right, that would help me spend my competency on the semantics of doing my work well.

Another key point of note that he talks about in the book, but I believe he has not highlighted it enough is the adoption of checklist. He describes how tough it was to introduce a checklist in the medical profession, when compared to the profession of flying. The essence being is that checklist are seen as a affront by the expert (surgeons) who believe the checklist are an insult to their authority, knowledge of systems and competence. It would have been of greater use, if he had also addressed some of the work, that led up to a successful adoption of checklist. Was it change management ? Was it working through the chain of command ? Was it through data ? Was it something else ? The message of checklist came through clearly in the first few chapters; instead of repeating it across with several more examples, it would have been a better, rather complete, if he had discussed the adoption too...

In any case, even though it falls short in some areas, a good book to read. Read it if you've the time, $$s and you'd want to know more than what is written above ! :-)