The latest CES show in Vegas promises more integration between devices in your hand, home, stores, cars, hotels etc. etc. which makes me think - Wasn't the basic promise from the IT land to have "ease of information" and NOT "overflow of information"
I see this happening not only at CES but all over the world. We want more information in order to have a better control. As executives, we push the need to have more information readily available in order to not have a reactive action but a proactive action. Guess what, and I am sure you all have felt it - whatever business processes (and associated IT systems) you designed and implemented for a proactive mode was outdated by the time it was installed.
So how do you design something for the future? If there was a simple answer then we would never have a "reactive" mode for anything. I read in some book a while ago - our ancient ancestors planned their meals by putting their ear on the ground and trying to hear the animals coming their way. This enabled them to be prepared to hunt the the animals down. It was true then, it is true today. Don't sit in your ivory towers. Meet the people on the ground and in the fields. They know your business. Your customers and yes your competitors. The folks in the trenches will help you plan for the future and yes you might live through the information overload.
So the next time around there is a new speech by Mr.. Gates talking about integration between your cell phone and the cars of the future, are you going to go look at that or you are going to look in the rear-view mirror since the future happened yesterday? Think about it !
Monday, January 7, 2008
Where is the future?
Posted by
Rohit
at
1:51 PM
0
comments
Tuesday, December 11, 2007
B2B
Its been a long long time since I had a chance to sit down and write on my perspectives. This time around I will write about B2B.
Hasn't there been written enough about B2B? Business-To-Business, yes sure. There is tons and tons of material written on the birth of this concept etc. etc. You can read about all that till you are blue in your face.
What about the other B2B? Do you ever take time to review the other B2B? Refresh your mind? Back-To-Basics. This is the other B2B that I think needs attention.
In every thing that we do at work, we are constantly learning new things, new technologies, new processes, new methods and so on. How many times as executives do we take the time and go back to basics? How many times do we send our teams to go back and learn the basics? Never ever.
Simple elements like treating people with respect. Managing resources to achieve long term efficiencies. Thinking global, acting local.
We tend to get caught in the mundane pieces of executing to plan that we lose focus of the basic fundamentals that have made us what we are. As executives, we tend to push to get our objectives met, goals exceeded and so on. How many times do we sit down, talk to the people without asking for a commitment, without asking for a timeline? Just respecting the individual for what they are and not the hard-work that they have put in.
As we get ready to close this year and begin to put our goals and objectives for the next year, I am going to have one of my goals as respect the individual. Are you? Think about it !
Posted by
Rohit
at
3:00 PM
0
comments
Wednesday, October 17, 2007
Fast or Far
The other day I was listening to Al Gore's Nobel Peace Prize acceptance speech and he started of with a quote from Africa - "If you want to go fast, go alone. If you want to go far, take a few people with you".
How very true. Don't we see that happening every day at work? Someone sitting up there in an ivory tower makes a statement and expects everyone down in the trenches to follow him / her with immediate effect because this new policy / process / system needs to be implemented quickly. Resources are mobilized and we get into the execution phase and find that we are inundated by issues. Why does it happen? Did we not plan correctly? I think what really happens is the real buy-in (taking a few people with us) did not happen.
We have seen this happen time and again, technology or a business process does not cause the bottle-neck. It is the people who cause the bottle-neck and in the same token it is the people who are responsible for the success of an endeavor. How can the same entity be responsible for the success and the failure?
So, the next time you are embarking on a new goal for your organization - are you going to go all alone and run fast towards your far-reaching goal or you are going to spend the time, get all the major stakeholders with you and all of you go towards the far-reaching goal together? Think about it!
Posted by
Rohit
at
12:57 PM
1 comments
Tuesday, October 9, 2007
A Spanner in the Wheel
I have been preparing for a marathon run for a long long time. Over a year actually. Every thing that could go wrong went wrong. Busted knee. Job change. Timings going wrong etc. etc. Anyway, my half-marathon is on 10/14/07 and I have been ramping-up perfectly well till last night. I have had a bad bad bout of allergies which has got me worried if I can recover in time for the race.
Okay. All of this is good. How does this fit into my blog of business talks?
You plan for a big huge transformation project with teams working over a year across continents. You have checked and cross-checked everything before you begin your home-stretch and then "it" shows its ugly-head. Something out of the blue. Like my allergies. Something totally unplanned for which might derail you. What do you do? How do you recover with less than 96 hours before prime-time?
Is there a clear answer? A magic bullet that will make all your troubles disappear? Never ever. If someone promises you a magic bullet, well then you are in fantasy land.
This is what I think really needs to happen to manage situations that hit you out of the blue just before D-Day: Evaluate, Review, Evaluate, Execute. I see that happening all the time, executives get nervous and start having status meetings multiple times a day to review the situation. I agree you need to do this if you are fighting a war but in the business world, as Jack Welch puts it, go by your gut. Evaluate your various options including aborting the project. There is no harm in reviewing this as an option. Once you have reviewed the impacts of each option, evaluate one more time the final chosen option(s) and execute. I cannot stress any more on why you need to execute perfectly. There is no room for error.
During all these activities never ever lose control. Be calm and be in control.
Anyway, the next time around, you suddenly find a spanner in the wheel, are you going to panic or going to attack the problem or going to live with the problem? Think about it.
Posted by
Rohit
at
8:34 AM
0
comments
Wednesday, September 26, 2007
Comebacks
This morning while driving to work I heard an interesting piece on the radio. A tree that is over 2600 old and was believed to have been "dead" for over 30 years was sprouting new leaves since the past week. This tree was burnt in a wild-fire, was struck by lightning and was believed to be dead since then.
This got me thinking - as executives do we ever face such scenarios' - companies thought to be bankrupt come back stronger, executives serve a jail sentence and come back stronger. We read about this and leave it there. Have you ever sat and wondered what does it take to stage a come-back? Did Martha Stewart think differently to come-back after her prison term? How did IBM turn-around from the early 1990's? What did Apple Computers do to come where they are today compated to 15 years ago?
We need to think like winners in our mind. The recipe for success is very simple. Think long, think hard and execute flawlessly.
Any shortcuts to this makes it difficult or virtually impossible for you to stage a comeback and put you into various false starts. Once the cycle of false starts begins it takes a super-human effort to break that cycle. I see this everyday even for smaller issue-resolutions. Teams do not think long and hard and try to provide a solution to the customer, which fails, so another band-aid solution is provided which again fails and so on. Eventually, the customer is tired of us and we then begin our plot for the "comeback" or regaining our credibility.
The next time around, your team fails in something and you begin the turn-around, are you just going to put out the fire or are you going to analyze why you failed in the first place? Think about it !
Posted by
Rohit
at
10:13 PM
0
comments
Monday, August 27, 2007
Life-Work Balance
There are tons of published material on Work-Life balance. Tons of printed material and 100's of GB of electronic material. However, I think there is a fundamental issue in the way it is expressed as Work-Life balance because it means that "Work" comes first and then comes your personal "Life".
Have we as executives ever wondered that by improving the "Life-Work" balance we can improve the moral of the team. I was meeting a few friends over the weekend and a couple of them were quite demoralized. As I was talking to them, I gathered that they had challenging work, were leading teams and delivering results however they were always on conference calls while at home and during the weekends. They were hardly spending time with their family and friends. Their "Life" was out-of-balance since their "Work" was made the top priority.
I thought that once if their executives saw this group of demoralized managers who were delivering results today but would not be able to do this for long they would do something about their "Life-Work" balance. As executives, it is our primary responsibility to ensure that the team's support structure ensures success.
So, the next time around, you are faced with a team that is demoralized due to a project / product failure, I am sure you will perform a "Lessons Learned" session with them however will you also look at the "Life-Work" balance support that you had provided which resulted in the result that you got? Think about it !
Posted by
Rohit
at
9:39 AM
0
comments
Friday, August 24, 2007
Process
I was thinking the other day about the need for articulating processes and procedures in a company. Why do we need to do that? Is the company not functioning without the documentation? What is the value-add (or ROI) for investing the time and resources on documenting processes? As an executive have you ever explained this need?
Every organization has their own silos of knowledge. In a typical start-up more of the action is performed at the spur of the moment and as the organization-grow in terms of human-resources than revenues is when you feel the need to have documented processes and procedures.
Now for a very large organization, you again need these sets of processes and procedures documented because there is a human-turnover. If you had a static workforce which never ever left the company, gave them instructions once and let them do their jobs everyday for the rest of their lives then we would not ever need such processes and procedures.
The question however is what is the ROI for a company that has never invested in documenting processes and procedures? How do you calculate the ROI in this case? Remember, there is always an ROI for an investment. The ROI can be tangible or intangible and may be spread over many many years or in some cases over a lifetime (for example the Green Company revolution - more in a later blog). With that being said, break the ROI if it is spread over many years into some form of short-term strategic initiatives and some long-term strategic initiatives and use these as the measure to communicate to the larger audience the need to develop documented processes and procedures.
There is no magic bullet - you need to invest time and document your policies / processes and procedures in order to build a long-term healthy company and update them periodically to be current. Period.
So, the next time around, you find some holes in the processes of your company, instead of letting it go, how are you going to use that to use it to help your company grow? Think about it !
Posted by
Rohit
at
12:06 PM
0
comments