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 !
Friday, August 24, 2007
Process
Posted by
Rohit
at
12:06 PM
0
comments
Thursday, August 9, 2007
Problem of Plenty
Do ever have such a problem? A problem of plenty? I would be highly surprised if the answer is "NO".
As executives we are always faced with multiple choices. Our days are filled with multiple, concurrent activities and we have a constant stream of choices to make, decisions to make.
But what do you do with the Problem of Plenty?
It would be wrong to say that ignore the other options that come our way and just focus only on one priority or take. We can never be successful when we do this (BTW, as executives whenever we make a statement using "NEVER", we are generalizing which is a wrong thing to do). Anyway, the point is very simple - train our mind to evaluate all the options, tasks and arrive at a decision rapidly. Remember, our mind goes as fast as we want. At the same time, there are moments when we have to put some challenges at the back-burner and reevaluate the current issues at hand and work through them.
I always have thought that it is so wonderful to be a captain of an commercial airplane or a brain surgeon or a heart surgeon - You have hundreds of passengers that have entrusted their lives to you and as a captain you have to coordinate hundreds of activities as the plane lands or takes-off. Same for the surgeons, peoples lives depend on the activities that these folks perform and believe me - these folks have a "problem of plenty" going on in their own minds.
So, the next time around, you are faced with multiple choices to make at the same moment in time, are you going to get overwhelmed or are you going to go with the flow and take a decision and move-on? Think about it !
Posted by
Rohit
at
3:32 PM
0
comments
Monday, July 30, 2007
Excuses
Its been a long absence from the Blog world. Let us see which excuse should I pick - dog ate my blog-notes, busy at work, lazy to post a blog, did not care to post a blog or all of these. Not sure which to pick.
So here is the challenge - you and/or your team has a tight timeline for a work-product delivery. There are regular check-points and everything looks green as an emerald. However, 48 hours before the end of your timeline something blows-up and you know for sure you cannot recover and deliver in the 48 hour window. So, what is the excuse you choose?
I see it at various levels of organizations where workers across the rank and file are searching for excuses. It is very easy to see when a manager or an executive starts of as "We were on target however..." and there comes the excuse. Why do we have to search something else to blame and not ourselves for the poor planning and execution. Such mishaps bring out the real leaders because a real leader, irrespective of their rank in the organization, is resilient and has a clear strategy to accept the mistake and bounce back even if it means looking at a revised timeline.
Back to where I started from, where was I all this while? I was busy at work and too lazy to post a blog.
So, the next time around, you hit a road-block just before your project delivery date - are you going to look for excuses or going to stand-up and admit that you messed-up? Think about it !
Posted by
Rohit
at
2:28 PM
0
comments
Thursday, June 21, 2007
Vacation
I was recently reading an article somewhere on how more and more of the work-force carries their cellphone / laptop / blackberry etc. etc with them on their vacation. If that was not enough, a large population actually checks their email while on vacation. To complete the story, quite a few of them actually join conference calls while they are on vacation.
Having said all this, picture the other side. As executives we promote the concept of implementing self-sustaining generic processes which are not "individual dependent" and also implement systems to remove the "human dependency" which basically implies that we implement process where A SPECIFIC person does not need to be involved in completing a process, anyone or someone can fill-in a slot when THE SPECIFIC person in not available.
Something is not correct with this picture - because we contradict ourselves. We try to achieve self-sustaining, scaleable processes and at the same time we are so dependent on specific individuals that a mere mention of a vacation puts us into "who is your back-up mode"? It does not end there - for the folks who go on a vacation supposedly without a Blackberry or a laptop or a cellphone they are always worried - "how is the work going on"? Think of it like this - will the IRS stop functioning if you left planet earth today? What about GE? Will that function if you died today (if you are an employee at GE or IRS? Of course they will continue to exists. So then, why is vacation a big deal for us as managers / executives?
So the next time around, someone on you team is planning a vacation - are you going to ask for their contact information while on vacation or are you going to use this as an opportunity to implement a process that is not person specific? Think about it !
Posted by
Rohit
at
11:53 AM
0
comments
Thursday, May 31, 2007
Banana
Ever heard anyone use this metaphor in the business world? Not really. But I think that the shelf-life of a banana is the same to that of technology available today. And that is where business can use this parlance of a banana.
Think of it like this - As executives we spend long hours discussing new business processes and then use technology as a lever to implement and streamline these processes. By the time we implement these technology-enabled processes, well, the core-technology has evolved and we are back to the drawing boards either trying to retrofit the newer technology to existing process. Most of the time, across the world, the major push-back is due to the fact that there are process-changes in companies and quite a few of these changes are driven by the fact that there is new technology available to better perform the work.
Why do companies keep chasing the infinite - implement technology only to yank it out later because it has become out-dated and has a shelf-life of a banana? Here today, gone tomorrow - with that as an open secret, we as executives need to address current problems in efficiencies because if we do not do it, our competitor will. We need to adopt the latest greatest technology and then be prepared to accept and implement the changes that come with any technology.
So, the next time around, you are evaluating a new technology are you going to ask yourself and the technical provider - how new is this technology or how old is this technology? Think about it !
Posted by
Rohit
at
10:25 AM
0
comments
Monday, May 21, 2007
Innovative Company
This is something that the Business Week came out last week with a list of 25 top innovative companies. They list Apple as the number 1 innovative company of the world. As I was reading this article I began to think what really makes a company innovative? What do you define as "Innovation"? (See my previous rambling on innovation)
How in the world can you say that Apple is the most innovative company in the world? It is extremely wrong to say one company is the most innovative company of the world. It is similar to what kids say to each other - My Dad is the strongest dad in the whole world ! How can one compare two distinct companies, for example, one that makes computers, music players, and now cell phones (namely Apple) to another company that saves lives by manufacturing cancer fighting drugs (namely Genentech)? You cannot and should not give the title of the Most Innovative Company of the World to either because each catering to different segments.
One key feature that these yard-stick magazines fail to perform is look at the value add that each employee brings to the company which basically means that if I were to draw a huge value-chain analysis chart for every employee of the company I should be able to see distinct addition as a I perform the analysis. That is when I will really be able to say what is the most innovative way and therefore say if that company is the most innovative company within that product segment.
So the next time around, someone tells you that their company featured on the most innovative companies list - are you going to congratulate them or ask them "which segment are you the most innovative in?". Think about it !
Posted by
Rohit
at
1:15 PM
0
comments
Friday, May 18, 2007
Courage
Courage - Not something that someone usually talks about at work. I have worked with folks from various countries on initiatives however have never ever heard people talk about courage openly. This is something like "the birds and the bees" - it is always there but you never talk about it !
Why don't we talk about courage in the business environment so openly like we talk about ROI, Initiative, Mergers, Acquisition etc. etc. I think it comes down to the fact that people talk about the "Risk" of doing business, the "Risk" of executing a project however are afraid to say that they have the courage to go down a path that they choose based of some data. Why are executives afraid to use the word "courage"? Because, in my opinion, they are afraid of failure. Afraid of being seen by their team that they were not courageous enough to take the more risky path that would have ensured success.
Courage in the business parlance does not really end when something fails. Courage really kicks in when something fails. I see more and more executives having very little courage to stand-up and say that "I am responsible for this failure". It takes a lot of courage to accept failure. I agree someone in your team did not perform his / her role and therefore the team failed. However, more and more executives do not have the courage to say that they were the leaders of the team that failed. Finger-pointing kicks in rather than courage. Enron is a prime example.
So, the next time someone asks you why did you select the a particular option in your business, are you going to say it was the least risky or you are going to say because I am courageous I took the option that will ensure success? Think about it!
Posted by
Rohit
at
4:16 PM
0
comments