The Organic OS - Critical Updates for a New OS

When I use new operating systems, I often wonder why they weren't finished to begin with. I mean, updates and service packs seem never ending; why couldn't they just foresee all of the problems instead of just rushing things to market?

As much as I feel that the end user should be offered a better experience with new operating systems, I must also accept that not everything could have been predicted accurately with their  introduction (Windows Vista excluded!). So, when a new business begins planning and implementing systems, they soon find out what is working and what is failing miserably because the planning has been transformed into the human side of things.


That being said, part of the planning should include alternate avenues when problems arise, because not everything that looks good on paper actually works when human emotions get involved. 

On several occasions, I had been informed that the 'new system' that was being planned was going to be solid when implemented because the people who were in the front lines could 'take it or leave it' with an attitude of 'my way or the highway'. They even went as far as saying that the workers would have to work around the plan no matter what and not the reverse. One problem with that kind of attitude is that the planner in charge of the operation didn't want to hear the human side of things because everything was so neatly illustrated on paper and there was no way the plan could fail, but if the people doing the legwork aren't consulted, there is the risk of losing great people.

Getting to know the team members is essential in order for the plan to be more realistic. The team members will, no doubt, offer keen insights that will help iron out the potential wrinkles of a new plan. It would seem very egocentric of a planner not to do thorough team research and big egos have been known to cause system failure.


Bosses, Consultants & Planners:

1) Check with your team members about possible hiccups of a new system. The front line workers see all of the deficiencies that will cause any new system to be less effective than it should be.

2) Update attitudes by communicating every detail of a new system to make each team member feel as though they are a part of a brilliant plan rather than just a pawn.


3) Update your own attitude after you've investigated thoroughly. This will happen once you've heard from the front line workers.


4) Update the plan to reflect newly discovered problems and ask the workers for possible solutions rather than try to figure it out all by yourself.


5) Most importantly - update your methods before you start a any new plan.