Are New Year Resolutions only for individuals? Can organizations have resolutions? Of course, they can but the stickiness and success on achieving or maintaining the resolution lies on not just one individual but on a team. The success for any resolution is in making change happen and making it stick a.k.a change management in terms of jargons.

Change is a people’s process and people resist adopting new practices and behaviors. Change management is an organizational process aimed at empowering employees to accept and embrace changes in their current business environment. Some of the factors that need to be considered while designing a change management program to ensure success are:

  • Analyze the impact the change will have on people – This will help the leadership team to direct their energy towards addressing the impact and on affected people
  • Building a case for change – People take things personally and are affected emotionally. So building an emotional case towards why the change is required and how their change will increase the success factor by several folds, will help in creating a connection with them.
  • Role models – The entire leadership team needs to be committed and act as role models towards embracing change.
  • Change management ambassadors – In addition to the leadership team, appoint several team members across the entire organization as ambassadors of change. Peer-to-peer interactions are more effective than pushing behavioral change from the top.
  • Continuous improvement – Change management is not successful as soon as everyone adopts the new practice, but only when after a certain period of time and without any external push, the new practices are maintained and people have adapted themselves to the change. For the long term, best practices should be introduced to capture the full benefit of change.

Change is imperative. Embracing change is key to speed of implementation and success. So go ahead list your resolutions, implement them and embrace change.

(References: http://www.strategy-business.com/article/00057?pg=all)

Happy New Year

Peek into the various events at CI held in 2010


Happy Thanksgiving

The World Cup came to an end the previous week after a month of fine football. I may not have watched as many games as I wanted to, but I certainly did learn a few things. By now most of us are familiar with Zakumi, Waka Waka, Jabulani and Vuvuzelas. I always think of a soccer game being similar to two companies fighting to get an order from a client. The best company / team wins.

  1. Speak your customer’s language – In US, soccer is known as football. Even though I grew up calling the game as football, in US I preferred to speak the local language and call it soccer.
  2. Experience plays a major role. After playing several games, players got used to the first round ball. The teams and their players went though an initial learning phase.
  3. Star performers help but Team Work prevails. Team work is a hallmark of winning teams. One of the greatest upsets of the World Cup was the French’s teams defeat. The French team failed mainly due to the infighting. Spain won mainly because of team work when compared to teams with star performers such as Rooney, Ronaldo etc.
  4. Early setbacks help. It is better to know the problems during the early stages itself. This would help in taking corrective action and setting the pace for rest of the games which in a way is agile.
  5. Prepare for the alternate. Many players missed their penalty kicks in this World Cup. It left me wondering if efforts were taken towards alternates.
  6. Make good use when opportunity knocks. Ghana lost the opportunity of entering into the semi final during the last minute in the game.
  7. Leadership is important. A leader identifies, builds the team and drives home the mission.
  8. Competition is never small. All battles should be taken seriously as overconfidence can let the entire team down.

This is just a summary of the lessons learned from the world cup. Every match irrespective of whether it is soccer or cricket or tennis or baseball etc. is a lesson by itself. Happy Analyzing 🙂

~ Ramya

CI @ Sage Insights 2010

CI @ Sage Insights 2010

Season’s Greetings

Our business would not be possible without your continued support.

All of us at CI join in saying

‘Thank You’ & wishing you a

‘Happy and particularly Prosperous New Year’

This year instead of sending a gift or even a card to our contacts we have decided – in the interests of the environment and of those more needy than ourselves – to donate an equivalent amount to charity. We will donate to charity a specified amount in proportion to the number of people who clicked the link.

Towards providing homes for the old aged forsaken, destitute and orphaned children homeless

CI Family

Why am I writing about SKY Meditation in this Product Engineering Blog? When I first started writing this post, I was focusing only on SKY Meditation. But as I started reading more about it, I was able to relate it with Agile methodology.

Ramani Ramachandra, MD, CI Global Technologies is a member of ‘The Rotary Club of Jersey City’. He spoke last week at the Rotary on the values of SKY (Simplified Kundalini Yoga) Meditation.

Ramani said that SKY Meditation is a form of meditation
that involves the interaction of one’s mind, body and soul.
The stress and hectic pace of modern-day life, he suggested,
causes one to forget the place of one’s soul in life. Nevertheless,
Ramani said, Yoga is now more popular in the United
States than in India – its place of origin.
He said that our priorities in life change as we accomplish
the milestones we set for ourselves. For example, he said,
after accumulating the money deemed necessary to lead a
comfortable life, one then seeks to achieve a milestone in
achieving personal health and after that, personal happi ness
and after that – peace of mind.


As I said before I was able to relate this to using Agile Methodology for Product Development. For example: Agile methodology involves the interaction of the product development team, customer service team and the customer. As the requirements keep changing we are still able to fix it with the next sprint and develop a product which results in a happy customer.

If you are able to relate your product development methodologies to something similar to what I have written then I would love to hear about them. Drop in a comment and lets get the discussion rolling.

~ Ramya