Pages

Saturday, July 28, 2012

Customer Driven Organization - Key of Success !!

"Thanks to our customers, we turned a potentially disastrous mistake into a great opportunity." ~ Michael Dell (founder of Dell Inc.)




Customer-driven Innovation

Customer-Driven innovation is not a one-time event or a slogan, it's a philosophy and a mindset.
You should live this principle daily. Observe people, live your customers' life, watch how they use your product to learn what works and what doesn't work. Encourage experimentation and risk taking. Involve everyone.

 Yin-Yang of Customer Value Creation
Require every person, regardless of their position to spend time on customer contact and services activities. Help your employees to understand the customer's needs by involving them in listening to customer feedback after a product launch. Ask all your employee to get on board with customer-driven innovation. Ingrain it in your operations so deeply that is becomes a part of DNA of your company

Case in Point Dell Inc.




Michael Dell founded Dell Inc. in 1984 with $1,000 and an unprecedented idea – to build relationships directly with customers. Dell Inc. is the fastest growing company in the industry. It was added to the Fortune 500 list in 1992 and achieved more than $44 billion in sales in 2004. The three golden Dell rules are:


Disdain inventory


Always listen to the customer


Never sell indirect.


Dell Computers were the first personal computer company to organize and build itself around the idea of direct customer feedback. "Our attitude was diametrically opposed to the engineering-driven thinking of "Let's invent something and then go push it onto customers who might be willing to buy it." Instead I founded the company with the intention of creating products and services based on a keen sense of the customer's input and the customer's needs. I spend about 40% of my time with customers," says Michael Dell


Selling Is Problem Solving
 
Google is the Internet’s number one search engine today. What is the reason for their remarkable success? It’s beta testing and market learning. They launched a less than perfect service into the market place to get market feedback. Feedback is the answer to dominating a market. It also makes great business sense. Google's competitors  were trying to perfect a product by themselves separate from their target market as Google was continuously and rapidly upgrading their original beta version by listening to the customer. They strived to achieve harmony with the reality
 

Customer driven Innovation - 7 basic practices

Customer-Driven Innovation is not a one-time event. It's a philosophy, a mindset, and a habit. You should live this principle daily if you wish to keep creating an innovative customer value, developing attractive product designs, and ultimately win the value innovation competitive game.


1. Observe people to understand hidden and unarticulated customer needs.


2. Live your customer's life, "walk a mile in the shoes of your customer".


3. Involve everyone, require every person, regardless of their position, to spend time on customer contact and services activities. Ask all your employee to get on board with customer-driven innovation and value innovation. Encourage experimentation and risk taking.


4. Involve customers in testing the prototype of your new product.




5. Help your employees to understand the customer's needs by involving them in listening to customer feedback after a new product launch.




6. Watch how the customers use your product to learn what works and what doesn't work.




7. Ingrain customer-driven innovation in your corporate culture and operations so deeply that is becomes a part of DNA of your company.

Saturday, March 24, 2012

The Purpose of an FMEA




FMEAs help us focus on and understand the impact of potential process or product risks.


A systematic methodology is used to rate the risks relative to each other.


An RPN, or Risk Priority Number, is calculated for each failure mode and its resulting effect(s).


The RPN is a function of three factors: The Severity of the effect, the frequency of Occurrence of the cause of the failure, and the ability to Detect the failure or effect.


The RPN = The Severity ranking X the Occurrence ranking X the Detection ranking.


The RPN can range from a low of 1 to a high of 1,000.


Develop an Action Plan to reduce risks with unacceptably high RPNs.


Use FMEAs as the basis for Control Plans. Control Plans are a summary of proactive defect prevention and reactive detection techniques.


Assembling an FMEA Team


FMEAs should always be conducted by teams.


The best size for an FMEA team is 4 to 6 people, carefully selected, based on the contribution they can make to the specific FMEA.


An FMEA team should represent a cross-section of the company in terms of functional responsibility and level in the organization. Team members typically come from:

Manufacturing


Engineering


Materials/Purchasing


R & D


Maintenance


Quality


Tech Service


Customers


Suppliers


FMEA team members do not necessarily need to have extensive knowledge of the design or process being targeted. In fact, sometimes it helps to get an outsider's fresh perspective.


The FMEA team needs a leader to help set up and facilitate meetings, to ensure the team has the necessary resources, and to make sure the team is progressing toward completion of the FMEA.


Monday, March 12, 2012

What You Need to Know About Failure Mode and Effects Analysis (FMEA)


Every product or process has modes of failure. The effects represent the impact of the failures. An FMEA is a tool to:
1. Identify the relative risks designed into a product or process.


2. Initiate action to reduce those risks with the highest potential impact.


3. Track the results of the action plan in terms of risk reduction.


FMEAs help us focus on and understand the impact of potential process or product risks. A systematic methodology is used to rate the risks relative to each other. An RPN or Risk Priority Number is calculated for each failure mode and its resulting effect(s). The RPN is a function of three factors: The Severity of the effect, the frequency of Occurrence of the cause of the failure, and the ability to detect (or prevent) the failure or effect.


RPN = Severity rating X Occurrence rating X Detection rating


The RPN can range from a low of 1 to a high of 1,000


Once the RPNs are determined, you need to develop an Action Plan to reduce the risks of failure modes of unacceptably high RPNs. Next, use the FMEA as the basis for developing a Control Plan. Control Plans are a summary of defect