Innovating at no costs

This post is dedicated to those, who still think that innovation is a costly affair:

“I agree with you” -- is what I could say and that would sum it up. But most of my friends know that I don’t really agree to it.

As I have pointed out in my this post (http://itcit.blogspot.com/2008/07/cheating-innovation.html) , there are two types of innovators. Since we know that type 1 innovation is costlier than type 2 innovation, most businesses should actually go for first kind of innovation (‘Creation’) only when the second type (‘Application’) is not available. And yes it is quite possible that all your efforts and money spent on type 1 innovation goes in vain due to changes in market condition or due to someone else creating and launching a similar or better product before you do. However, type 1 innovation can give you massive returns (if type 2 innovation is also applied effectively on the product obtained from type 1 innovation) much more than what type 2 can give you.

In that sense, I would say Innovation (type 1) is like the stock market --- high risk, high return. If you are not looking for high returns, you can still get decent returns (in fact, better returns in turbulent times) from bonds/ deposits i.e. type 2 innovation.

Non-fluid employees of large corporations

Large corporations, be it IT or non-IT (I will talk more in terms of IT firms), have the tendency of making people stick or non-fluid i.e. the same group of employees (the entire hierarchy) carrying on from one project to another. Though restructuring and location-transfers help to certain extent, but the time period during which this stickiness develops is shortening. Yes, this helps the organization in a way (better bonding between team members since they have been working together for long), but it also creates a problem. With such clusters getting formed, you would either have to go for the complete cluster or nothing. Hence, the skill availability gets severely hit and, while the employee utilization levels remain low, there is always demand for people -- a fake demand due to artificially choked supplies.

Final word
I think though such stick clusters are good, however, these clusters should be broken at regular intervals in order to ensure better access to talent across the organization. One important break-point should be the allowed time-frame for the cluster to remain a cluster once it is on 'bench'.

Even big R&D firms choke innovation

Once a great business leader (who heads a multi-billion dollar company) was stuck with a business problem for which neither he nor his wise men could come up with a real good solution. He went on and poised the question (in a simplified form) to a group of young children at a school. Children exclaimed at the simplicity of the question. And soon Jack had the solution (rather multiple solutions) before him.
Moral of the story:
1) Think different. Don’t choke innovation. Float your problems (wherever possible) to larger group of brains – instead of limiting it to your (labelled) wise men

2) Collaborate and reach out: someone from outside your team/group might turn a seemingly difficult problem into a real easy one.

3) Appreciate the fact that different people see things differently and different thought processes could actually bring out totally different views

Hyped SaaS !! Can we have 'Kaas' too.

SaaS is fast getting popular just like anything that receives extensive hype. However, the good thing with such hyped concepts is that they bring to light the basics that have been kind-of forgotten (or not treated seriously enough). This (SaaS) is a case similar to design patterns (see http://itcit.blogspot.com/2008/06/invisible-design-patterns.html). The concept has always been there, it is just the hype that is new. There have been shared servers, shared telecon services, shared hosting services, and tremendous softwares have been developed in order to cater to niche needs of various business verticals and sub-verticals. All these are like SaaS in action (in a way). So, nothing new there.

Let me, however, take another slant on this one. Can we take some learning from the SaaS concept and start treating reuse and knowledge management (which are kind-of aimed to achieve similar purpose in their own earnest) more seriously. I am not saying that IT firms (especially large IT firms) are not taking KM and reuse seriously -- what I am saying is that there needs to be a more focused effort. Or to put it more simply -- let's create a hype around KM+resuse. Should I call it 'KaaS' -- knowledge as a service?

SaaS: http://en.wikipedia.org/wiki/Software_as_a_Service

Cheating = Innovation

Consider this:
Innovator 1: The person who conceives the idea e.g. the person who thought of and created the first internet networking website but made almost no money from it*
Innovator 2: The person who copied this idea and raked in millions through it.

We are labeling a copy-cat as innovator...Foolish - Isn’t it? But that is true, innovation has many dimensions (broadly 2 dimensions) – Innovator 1 was great on the ‘Creation’ aspect while Innovator 2 was great on the ‘Application’ aspect.

Can we say Innovator 1 > Innovator 2 or the other way round?
Well, it really depends on what objective these innovators had in mind and were they able to achieve those objectives. However, for most businesses, Innovator 2 would be better than Innovator 1 because the inherent objective of most businesses is to make money.

So, innovation (of type 2) might not actually be a big ticket item as most people think it to be.

* This is just an example and doesn’t refer to any person in the real world

No one wants to join IT industry

Today, I am in a thought-provoking mood. So, i will leave you with a thought.

How many IT pros in India went on to pursue IT as a career because they really had a liking towards it? Or was it more because IT was the easiest choice and there was nothing else to bank on for a living?

And if you yourself are Indian IT pro, do you actually want to continue with your career in IT? Or would you rather quit IT if given an option?

I will leave it here then. Just think. And also think, why i asked you to think on these lines-- and you will have the answers?

Why restructuring causes attrition

Restructuring exercise in any organization is interpreted by people (employees) in this way: If I am going to get a new boss and a new department, I will have to prove myself again to the new group of people. I would be better off joining a new firm at a much higher pay scale. This is a typical case of comfort zone disturbance.
Similarly, a person (an employee) might feel loss of respect in the organization or might get a feeling of jealousy due to the promotion of others or better pay-revisions of others. Again, this is a comfort zone disturbance.

And whenever there is a comfort zone disturbance, people seek greater value (self perceived value) for themselves at other places (firms) either through a perceptibly better role or salary. Note that here we are talking about self-perceptions -- but isn't that the most important factor in employee retention.

Outsourcing is no more the same

With the US economy receding, there is an increased focus within firms to on cutting all kinds of spending. And outsourcing is no more the same as it used to be few months back.

The shares of Indian IT companies have plummeted as a result of this economic slowdown (partly due to appreciating rupee too). However, while IT spending is going to be cut to some extent by some companies, there will be others who would be looking to outsource more in an effort to cut costs. So, this will kind of balance out or maybe tilted a bit towards outsourcing. But note that here we have not considered those firms who have not been outsourcing. These are the 'rich' companies who have been against outsourcing. But now they will discover that outsourcing can be their savior in difficult times. Hence, they will be forced to outsource work to countries like India.

What does this mean for Indian IT companies?
1) Risk is spread better because number of clients will increase thereby reducing the dependence on a few clients.
2) Overall demand for outsourcing will increase, thereby propelling the growth of these companies further

Attrition can’t be attributed to aspirations, salaries or job location

Whenever we talk of attrition, we talk about one of the following:
1) Job/ Role aspirations not getting met
2) Salaries being too low or revisions being improper
3) Preferences of people for particular job location (generally near to their permanent residence or family/ friends)
4) Uncooperative boss

However, these are just the triggers (the cause) to a disturbance (the affect) which leads to attrition. The disturbance we are talking about here is the 'Comfort zone disturbance'. And this is really the cause of attrition. So, what do we do to bring down attrition?

It's quite simple. Change the affect that these triggers cause. If you can somehow prevent comfort zone disturbances, you can control attrition. This means, you need to identify the elements that comprise the comfort zone of your employees; and then you need to balance out those elements whenever a comfort zone disturbance is created. It does involve quite a bit of thinking, but I believe that is the only way of controlling attrition.

Name to face and face to name

Outsourcing has been the key driver of IT industry in India and several such IT service providing countries. This has led to use of global delivery models wherein the business teams don't know the development teams. This means people are simply names (and seldom do we put faces to names). Similarly, sometimes the teams working for a particular client might not know each other well enough i.e. no names to places.

I think that overall comfort level of all the parties involved would somewhat increase if we were to put names to faces and faces to names. So, ensure:

1) Sharing of photos/ videos between onsite and offshore folks

2) Parties to be organized at account level so that people get to mingle (this finally helps in team bonding and knowledge sharing)

Now outsourcing can't cause unemployment in US

Yes. Now there is enough space for everyone in the IT industry. We often talk about outsourcing being the cause of unemployment in the US and other developed countries. This was probably true till last year or maybe even this year; however, this has changed very fast now. Here is what has caused this:

1. Growth rate of IT industry in India
With the growth rate of Indian IT industry not relenting, and the rate of creation of talent not matching it, it is obvious that there is going to be dearth of talent in Indian IT industry. Moreover, the India has not yet become a consumer of IT services in a big way. So, the growth rate is expected to be robust (same if not better) over the years to come. So, this gap between talent demand and supply is going to widen further and there will be no other choice for Indian IT companies except for hiring from US and other countries. Recently, TCS opened a 1000 people center in Ohio, US.


2. Overall economic growth of India
India is fast moving from its status of a 'developing country' to a 'developed country'. So, there is demand for talent and skill (at all levels) in all industry segments in India. Since the demand is coming from all sectors, and the pay scales rising fast in non-IT segments too, there is further dearth of talent in India.

Do you think Indian IT industry will be able to contribute to unemployment in US anymore?

No one wants SEI CMMI, not my guys at least

A typical IT services company sells SEI CMM or SEI CMMI big time. And the selling is so huge that they have almost forgotten the value that SEI CMMI brings to an organization. See http://itcit.blogspot.com/2008/06/sei-cmmi-is-crap.html

The big problem at hand is -- people (on ground) don't want to follow the processes laid by the IT firms as per SEI CMMI. The quality department is almost always running behind the delivery guys to get them to follow the processes. I know that this is the trend across most big IT services companies. But why do people not follow SEI CMMI processes in the right earnest (they do follow/fake them under the pressure from SQAs)?

I did a study, quite long back, and the major observation that came out from it was:

1. People don't understand the objective behind these processes -- and no one takes the pain to make them understand the objectives -- instead the focus is on getting them to comply either through carrot or through stick

2. Even if people are told the objective behind the processes, the objectives are explained in way that focuses towards the benefits to the IT firm and not towards the individual -- I believe the benefit of processes is more for the individual. How? Check --http://itcit.blogspot.com/2008/06/no-it-firm-benefits-from-sei-cmmi.html

Hence, people are not motivated enough to follow these processes. And wherever there is a lack of motivation, the failure is imminent.

No IT firm benefits from SEI CMMI

Answer these questions:

1) Why does one create a grocery shopping list?

2) Why does one check and cross verify ones banking transactions?

3) Why does one buy insurance?

Here are the answers:

1) Because human memory has limitations and very few people have such a sharp memory so as to remember more than 5 items

2) Because we want to be sure that nothing is amiss

3) To cover our risks

So, we are doing all these things for our own benefit. Similar is the case with SEI CMMI processes:

1) Your checklists (coding/design/ delivery etc) help you ensure that you have not missed out on anything -- if you miss out on any of these, you might have to slog later to correct them or bear the consequences

2) Similarly, requirements traceability matrix helps you tally and cross check that none of the requirements have been missed out in design, coding or testing

3) Defect prevention strategies (as advocated by SEI CMMI 5) are like risk covers -- and if there are lesser defects later, your life will be cool.

So, it's not the IT firm you are working-for that will benefit from SEI CMM or SEI CMMI, it will be you (the person who uses/implements these processes on ground) who will benefit the most

SEI CMMI is crap

Most IT firms have grossly misunderstood SEI CMMI. Today, IT firms treat SEI CMMI purely as a marketing stunt. In fact, the situation has become so bad that most IT professionals now despise SEI CMMI and consider it as crap. For most people, the mere mention of SEI CMMI is repelling.

But is it really crap and is it really just a marketing stunt?

Most people reading this blog would be aware of 'Design patterns’ and how they came into being -- Read http://itcit.blogspot.com/2008/06/invisible-design-patterns.html. Design patterns are just a compilation of best practices and tried-and-tested solution to problems that are repeatable across IT projects.

On the same lines, SEI CMMI, as I understand it, is simply a collection of best practices and guidelines for software engineering and management. In fact, I sometimes refer to it as the magic key for dumb project managers; a key that ensures the success of their project if they follow the SEI CMMI principles in the right earnest. It has really made the job of project managers really easy. It helps cover most project risks and proactive mitigates them. Things like - Requirement traceability, configuration management, acceptance criteria, defect prevention meetings are surely a prescription of ensuring success. In fact, these are the things that any project managers should be ensuring in any case (whether CMMI or not) --- SEI CMMI just reminds the PMs that they should take care of these things.

So, why is it so difficult for IT firms to ensure SEI CMMI compliance in their firms? Well, i will include this in my next post.

Don't ask your IT guys to use innovations

One of my favorite books 'Jonathan Livingston Seagull' by R. Bach, talks about boundaries being in the minds of people. These boundaries create the impression of unachievable or impossible. And Bach is able to convey the message very clearly and in the most succinct way. The question is "Who creates these boundaries?” We collectively do it as a society. First we create these boundaries and later, once these boundaries have become rigid, we talk about removing them and innovating. We tell people that 'today business can thrive only on innovation' etc. We create new models for executing our jobs. We provide them some tools for doing their jobs more efficiently.

Still doesn't work. Does it?So, what do we do then? Well, instead of giving fodder to the horse, tell it the path to find fodder.

Enable your guys (again, I am referring to employees of an IT services firm) to be innovators and not just users of innovations. That is what you need -- A big team of innovators.

And how do we prepare this team?

This can only be achieved if you orient the thought process of your guys in the right way. Just lead them to the point from where they have multiple options to proceed ahead -- instead of leading them straight to the solution. Then tell them how the final solution was reached. Ask them what could be the other possibilities and in what scenarios would such possibilities form a better choice. So, instead of telling them how the internally-developed (by some geek at your firm) productivity enhancement framework/tool works to generate code (or whatever) for a particular tier, tell them how it could have been done differently to achieve a different end. This is actually what we call as stimulus for 'Lateral thinking'. And this is what today's IT services firms need.

IT services firms dont need innovations ...

With the margins of IT firms getting hit due to slowdown in the biggest IT market, there is sudden focus on innovation, cost-cutting, productivity and high-end services. Great!! At least the IT services companies are now thinking about innovation. But what they are thinking of is not as useful as they are thinking it would be.

By creating products and selling IPs (intellectual property), you can get limited amount of boost on margins. By promoting use of tools, there can only be a limited increase in productivity levels.
This is fine in the short term -- as a tactical measure. However, sustained growth can't be achieved through these measures. What you need to do is - "Bring innovation in the thought process of your organization". Enable your people to think of ways to do things differently -- create tools of their own. You will need to prod them and give some directions and let them complete the circuit of innovation. Yes, this is a slow process --- However, this is the only way we can sustain growth and also lead to proper utilization of the brains of several thousands of IT people.

When i say direction, i mean telling (showing) them how some easy tools were created and throwing questions at them on what could be the different possibilities arising from it. This is what i call " Weaving a framework for innovative thinking". So, don't tell them 'Use tools', enable them to create their own tools.

Skill-based application frameworks

With the skilled programmers becoming a rare commodity and uncontrolled growth of IT industry, there is a need to think differently. We now need to move from requirements based frameworks to skill-based frameworks. By skill-based frameworks I mean, designing the applications/frameworks in such a way that people with low skill levels are also able to develop the required applications. Yes, we have already been supporting programming languages like Java, various modern-day application servers, IDEs etc for the same reason. However, as the need for skilled people increases and we find there are lesser numbers available, we will have to keep moving to more encapsulation i.e. skill based frameworks.

So, in effect, what we are looking at is an additional parameter (skill level of people) for deciding the architecture and framework of an application, besides the usual thing (customer requirements). This is something that we might see in future.

However, the best way of achieving this would be to create 2 frameworks:
1) A customer-requirements-based framework
2) A developer-skill-based framework

So, the development happens using the developer-skill-based framework and you create a tool to directly convert the skill-based framework to the requirement based framework.

This is what I think is the future and the most realistic solution to the skill-shortage problem.
I will further elaborate on this in my future posts.

Any opinions on this are most welcome.

Invisible design patterns

And you thought that the design patterns were a recent thing?

Of course not. If I reflect back on my yester years, I find that these design patterns are actually the solutions to the problems that I myself developed. And few years later I was being told to read and learn about design patterns. Once I read through, I realized that what I thought of as a new thing or a fantastic concept was actually something that I knew about since ages. Some clever guy had named them as design patterns and asked the world to use them. Anyways, that person has done a lot good by bringing this to the notice of everyone. I wonder, why I did not think of putting some fancy names to my design solutions and call them design patterns.

So, these were the visibly invisible, design patterns for me. However, if I look at them today, especially in J2EE context, I think they are fast becoming obsolete. Just looking to see who will be the next one to earn fame from naming some new design patterns.

3 secrets behind frequent restructuring of an IT firm

We recently heard about organizational restructuring in top IT companies of India -- wipro and Infosys. And this is not the first time that such an exercise has happened in these companies. If you look back into time, you will find that this happens quite frequently. So, business vertical based organizations get converted to geography based and then again to vertical based and the cycle goes on and on. So, let's see the reason cited by these orgs:

When moving from vertical based to geography based --> "This will enable us to focus on those particular geographies, hedge our risks, develop an employee base that understands the culture in particular geographies etc...."


When moving from geography based to vertical based --> "This will help us provide the whole range of services in a particular vertical and seamlessly across the globe etc...."

However, i see different benefits from it:

1. Satisfying aspirations of people
Well, this is a double-edged sword. On one hand you could be creating new designations or re-designating people in order to cater to their aspirations but at the same time some other people might feel that their aspirations are not going to be met and hence decide to leave the organization (some might also leave just out of jealousy). So, extreme care needs to be taken on this part.

2. Increased networking within groups
Since the people that formed one single group are now spread across different groups --- there is an automatic creation of communication channel between the new groups and their people. Hence, the level of networking and knowledge sharing gets a boost. Nothing else can lead to this level of networking (and that too at all hierarchical levels)

3. Fresh enthusiasm - like when you join a new company
Again a double-edged sword. People will need to prove themselves again (since their bosses have changed) and hence restructuring infuses fresh blood into the organization. However, some people might also think "Since this is going to be like working in a new company, why don't i actually go ahead and join a new company where i will also get a good jump in pay". These guys were previously sticking to the company because they gave more importance to their own comfort level in the organization then the pay they were getting.

Is the next big restructuring approaching your firm? Maybe yes, if it's been a long time (3+ years) since the last restructuring.

Shortage of people in over-populated India?

I would say 'IT' in India is a job spinner. I remember my days 14 years back when i was really slogging to get admission into one of the major engineering institutions (the IITs) . That was real hard work -- 16 hours put in every day continuously. The carrot was -- if i get into an IIT i will get a job for sure and if i don't i might have to really struggle. IIT entrance exam was a tough one where we had around 0.2 million students competing for around 2000 odd seats.

That was then.

Now, with the IT industry roping in engineering graduates from across India (and the world), the jobs are aplenty. Almost, all engineering colleges across India have campus selections in the IT industry. So, it easy guys. No more 'burning the midnight lamp'. Just chill. And note that the campus selections are rising by the day and students are booked when they have just completed 50% of their course i.e. 2 years of their study. Which also means 2 years in advance. In my days, even in the IITs, campus placements were not always 100%. But now all engineering colleges have excellent campus placements. Leave engineering grads, all grads are having a great time -- thanks to ITeS (IT enabled services) i.e. call centers and BPOs.

So, IT is a real job spinner. And, in fact, it looks quite strange that we are soon going to reach a stage wherein we will say that there is dearth of people (IT-able people) in the 2nd most populated country of the world (or has it become the most populated now)?

Let me introduce this blog and me

Friends,
I am MGoel, an IT pro who is fast approaching 10 years of age in Information technology industry. An engineering grad from India's premier institution (IIT) , I have worked across the globe on various IT assignments of various size and nature. I will not take this intro further since i see the risk of being interpreted as a self-seller.
So this idea of starting my blog came to my yesterday. And this is my first blog --- and even the first experience in the blogging world. So, i will discuss almost everything about IT on this blog.

Anything else that i need to write about on this intro???

So, welcome to my blog.

As i signoff, i am just thinking what my first post would be --- and i have decided that i will not think about the topics but will write about whatever comes to my head. And if you, my friends, want to discuss about something -- i will write about that.

That's how you will see IT thru the eyes of a globetrotting IT pro.

Thanks
MG