Sustaining generic process

The dream of every executive - design and implement a cookie-cutter, sustaining generic process. Teams across the world try and achieve some form of efficiency in their processes and try to leverage this process the next time around in the hope of standardizing.

Can this dream of one process for a specific product development / deployment be achieved? The answer everyone wants to hear is "YES". The answer that is realistic is "MAYBE".

And here is why - when teams are formed to create a standardised process they look at their existing value-chain. They put in the thought of how will a standard process function across this value-chain, look at the various parameters and stakeholders and X-weeks later produce a generic process. This process will continue to function in its self if that was the only process in the world! The fact of the matter is it is not. And therefore the troubles begin because your customer wants you to provide the data in a different format or there is a new law that requires that when you manufacture in China and Ship-To UK you need to have 7.5% VAT etc. etc. This is when you break your Sustaining Generic Process.

So how do you achieve a more sustaining generic process? You step out of your realm and look at the overall process first in your department, then your overall organization and then in the industry segment that you operate in. Visualize and evaluate various options that can impact your processes based on the industry maturity and experience and then design a process. Take the Banking Industry as an example - the processes are standardized, cookie-cutter to a very very large extent irrespective of the bank you are dealing with.

So, the next time around you sit with your team to design a sustaining generic process, look at the complete picture, think out of the box and put something that will catapult your organization to the top in your industry segment. Think about it!

Can't and How

A usual work day across the world, deadlines, issues, concerns etc. etc. We are always battling these with teams, users, customers and so on. What I have seen is whenever there is a paradigm shift that is proposed for issues or for an action plan that calls for extremely tight timelines the usual answer is "It Can't be done".

Whenever I lead a team, I coach them to think a little differently and instead of saying "It Can't Be Done" they should say "How Can It Be Done".

The problem is saying "It Can't Be Done" is more than a statement - it limits one's ability to think beyond. People always forget - the human mind is capable of great things however we end up locking the capabilities by saying "It Can't be done".

As a leader, it is our responsibility to coach the team to think beyond their capability. How do you go about it? There is no cookie-cutter, one-size-fits-all methodology however what I have see that works is just pushing the team to think of a a more holistic picture of the problem and how the decision would impact the overall solution. This more-or-less gets the creative juices going because the team is at least made aware that by saying "It Can't Be Done" the impact to the overall solution is more greater than the problem at hand. The team begins to think on how to minimize the impact to the overall project and that is what it takes them to turn round the corner from "It Can't Be Done" to "How Can It Be Done".

So, the next time around, you are hit by an issue, before you accept "It Can't Be Done", ask yourself, how do I explain the bigger picture to the team because the solution is out there. Think about it.