Posted on

10 important things for creating highly effective posters

Poster-Visualizing your thoughts

Posters are great way of visualization the power of learning.

People remember things more, if they visualize things. The posters located at strategic location helps in conveying message of the top management to the whole team. Posters are the messages to all. Things that are important for best poster building are;

  1. The poster should convey the message.
  2. The Poster should be in language of people.
  3. Posters should use pictures, graphs etc.
  4. Posters should be interactive, They should talk with people.
  5. Posters should be attractive.
  6. Posters should be specific.
  7. Poster material should be long lasting.
  8. Posters should be smart and has capability to link with people.
  9. Poster size, font size should be visible.
  10. Posters should be innovative.

10 important things for creating highly effective posters

Few examples of best posters used for visual management in 5S, root cause analysis, lean management etc. are shown as below:

Poster-Identifying MUDA
7 Wastes poster-Lean management
The Red Tag System-Sorting process in 5S
5S Planet Poster
5S poster- Lean Management
5S Pyramid Poster
5S poster- Lean Management
5S Structure
5S poster- Lean Management
Poster-Root Cause Analysis
Root Cause Analysis- 5 Whys

Poster 5S Methodology

The posters requires creativity & innovation. Many software are also available for making posters. very basic software & tolls that can be used for making poster are as below:

  1. Paint
  2. Microsoft publisher
  3. Power point
  4. Microsoft word

Start Following us on Facebook page, Pinterest and Linkedin.

Many online tools are also available, but these are the very basic tools, which will full fill majority of the requirement.Go ahead & create your own posters. Think freely & innovate something new and benefit the society.

Key words: Lean management,lean management tools, visual management, 7 waste,5S cycle, 5S lean, 5 s lean management, zara lean management, why lean management, using lean management, under 5s, 5s walks

Posted on

Case Study – Frequent maintenance in Stack Analyser (Banish MUDA)

Case Study – Frequent maintenance in Stack Analyser (Banish MUDA)

This is a beautiful case study resembling positive approach of the team towards finding solution.

A stack analyser was having very high frequency of maintenance. Being mounted in stack of incineration plant, the probe was exposed to dust & acidic gases, which were the main cause of probe failure.  Main Issues with the Analyser is:

  • High Frequency of Cell and heater failure.
  • Frequent chocking of cell assembly.
  • High time required for cleaning and cell replacement.
  • High cost of maintenance

The team took up the challenge to come out of the issue. The study done was a good example of usage of various reliability tools like RCA, Fishbone diagram, Brainstorming, etc. ,there is another angle to it, ie. Lean Management. The main objective of the study was to reduce the quantity of jobs performed on the analyser.

The team has recently gone through “7 Wastes-Mr. TIMWOOD “. They decided to identify the wastes in the activities on the analyser. All the activities were identified & written.

Each activity was studied and type wastes were identified.

Case Study- Frequent maintenance in Stack Analyser (Banish MUDA)

Analysis of the identified waste is as under:

  1. Transportation of probe to the repair location: Can the probe be repaired at the installed location?
  2. Motion of the workmen for steaming, hammering & temporarily electrical connections: Why Steaming, Hammering is required? Why temporarily connections are required?
  3. Defect during leak checking: What is the procedure for ensuring correct assembly?
  4. Inventory: How to reduce inventory required supporting the frequent maintenance?
  5. Waiting: Why can’t the warm up done at location?
  6. Over Processing: Why calibration & response check is required two times?

The next step was to find answer to these questions. The maximum time was consumed by removal of Cell & seal assembly. RCA tool, Why Why analysis was used to drill down to accumulation of the acidic dust at the cell as the root cause. A ceramic diffuser was prepared with OEM, to put in place of mesh, which is more capable of filtering dust. This small change after value engineering has resulted in substantial improvement in terms of time, cost, inventory, maintenance frequency, reliability & availability of the instrument.

Continuous Improvement

Cost of Modification: Rs. 25000

  • Total time of job was reduced from 8.8 hours to 4.3 hours.
  • No. of jobs reduced from 10/year to 4/year.
  • Material cost reduced from Rs. 1.8 Lakh to Zero.

Continuous Improvement

Experience of industries has been concentrated in different quality, Reliability & Lean tools. Correct knowledge & implementation of these tools is necessary for best results.

Check other case studies on Vanilla Ice Cream and Flight 5390 failure.
Start Following us on Facebook page, Pinterest and Linkedin.

Case Study- Frequent maintenance in Stack Analyser (Lean Tools)

Posted on

Fault Tree Analysis (FTA)

FTA is fault tree analysis, used for identifying causes required for a particular fault/event to take place.

This technique uses basic symbols of electronic & logic field. The Fundamental symbol used are AND & OR gate.

Truth table for AND & OR gates:

Input Output
0 0 0 0
0 1 0 1
1 0 0 1
1 1 1 1

Symbols of AND & OR gates:

and or gates

The failure mode being studied is called head event.

The basic concept of this technique is to put all effecting events in a logical form.  Take a case of motor stoppage. The motor can be stopped due to following reasons:

  1. Power loss
  2. Overload
  3. Coil Damage
  4. Process interlock operated

Further power loss can occur if the incomer power supply fails & the emergency generator also fails at the same time. Over load can occur due to chocking in pipe line, or, the isolation valve is closed. Coil can damage due to over current or moisture ingress. Process interlock can be operated due to instrument malfunction or real high vibration.

The Logic tree can be built as follows:FTA

All the identified events can be given probability of failure depending upon MTBF calculated from past events. In case both events are required for resultant event to occur ie. AND gate, the probabilities are multiplied. In case, any one input can have the resultant impact ie. OR gate probabilities are added.

The FTA Analysis is done for finding out all probable faults possible. This enables us to attack on right cause for identify & eliminating the fault.

check some of these interesting posts of time management and of super organiser as well.
Start Following us on Facebook page, Pinterest and Linkedin.

Posted on

Failure mode & effect Analysis (FMEA)

An Engineering technique for system reliability improvement.
FMEA refers to a structural tool to identify potential failures at component level, the causes of these failures, and effect these failures will have on the operation of the system.


1. Determine product & gather associated data.
2. List all the possible failure modes. This is a very important step, and should be given enough time and resources. For each failure ask how, where, when and why.
3. Calculate RPN (Risk priority No.)
4. Put all in descending order of RPN nos.
5. Development of action plan which the team deem most significant.
6. Failure with high Severity no. should be given importance even if RPN no. is low.
7. Document & report the results

Risk Priority No.:

RPN= Probability of Occurrence X Severity X Detection

Probability of Occurrence: this refers to probability of occurrence of failure
Severity: An estimate regarding the impact of this failure would have
Detection: An estimate of probability that the failure would be detected, if occurred.


This is a Before-the-fact action, not an After-the-fact action.

Applications of FMEA:

1. Design of reliability. This is termed as DFMEA (design FMEA)
2. Quality engineering. This is to improve process and is termed as PFMEA (process FMEA).
3. To prepare maintenance strategy of installed equipment.
4. Proactive identification and elimination of potential of failures.

Check some related post of FTA AND Waste in Lean Management also.
Start Following us on Facebook page, Pinterest and Linkedin.

Posted on

Flight 5390 Wind Screen Failure

British air ways flight 5390

Wind Screen blown out & the chief pilot got sucked outside the cockpit-Root Cause Analysis

Root Cause Analysis

Airway is the safest ways of transport in today’s world. This has been achieved by continual improvement by way of analyzing failures & putting strict compliance to findings. This is dedication of airlines & related agencies to work for safety of the passengers.
The incident on British airways flight 5390 is an example of how meticulously the investigation had been done.
Root Cause Analysis is not to find who did it, but why it was done.
Near crash of British air ways flight 5390 from Birmingham to Spain. Wind Shield blown out & the chief pilot got sucked outside the cockpit at an altitude of 17300 feet.
British airways flight 5390 took off from Birmingham airport to Spain on 10-June,1990. Couple of minutes after take-off, the wind screen got blown away. The vacuum generated, sucked the pilot outside the cockpit. His legs remain stuck inside cockpit. The crew had to hold on his legs, otherwise, his body, if released can flew into the engine, thereby taking down the plane. The Co-pilot took control of the situation & landed the plane safely on Southampton airport safely after 22 minutes in air. All persons on board was saved. The chief pilot immediately sent to hospitals, he had few fractures & mental trauma. Luckily, he could recover & managed to fly after 5 months.
The investigating officer collected all the evidence from the plane first hand. He found that the wind screen was fitted from outside the cockpit. Few of the bolts were missing. He took samples of installed bolts. As per maintenance history, the wind screen was replaced a night before.

Root Cause Analysis
He interviewed the technician. He found removed bolts in dustbin. His observations were:
1. The technician was very experienced & has over confidence.
2. He matched the removed bolts, but did not refer the catalogue for correct size.
3. The size of bolts used was one unit smaller then recommended.
4. He was not having proper approach while fixing the windscreen & has to lean in awkward position.
5. He was having time pressure to fix the windscreen as the flight was scheduled for flight tomorrow morning.
6. There was no other engineer/supervisor to verify his job.
Root Cause Analysis:
As the plane achieves an altitude, there is difference in pressure inside & outside the cockpit. The windscreen was fitted from outside the cockpit and thus had to work against this pressure. During investigation, it was found that the bolts used was a size smaller that the correct size. As differential pressure increased, the bolts could not hold on & started giving away. The wind screen got blown out.
Further, investigation found that the removed bolts were also of wrong size. The technician tried to found a match with removed bolts without referring catalogue.
The Reasons can be categorized as follows:
1. Physical factors:
a. The Wind screen was fitted from outside as per design. Thus has to work against vacuum. The design was not adequate.
2. Human Factor:
a. The Technician did not refer catalogue and believed his knowledge.
b. The Technician continued to work in awkward position & had not firm grip on screw driver.
3. System Factor:
a. The job done was not verified by second person, being of critical nature.
There is always a system factor behind every incident or a near miss.
Probability of occurrence of this incident would have been minimized, if the wind screen had been fitted from inside. Also, If the airlines have redundant system check in place for critical jobs done on aircraft, this error would have been caught beforehand.

Be part of our Discussion forum
Start Following us on Facebook page, Pinterest and Linkedin.

Posted on

Vanila ice cream stopped my car

Root Cause AnalysisSound crazy!!! Isn’t it.
Go through an amazing piece of case study of root cause analysis, how a Pontiac car owner surfaced an interesting issue which is hard to believe.

A complaint was received by the Pontiac Division of General Motors:
‘This is the second time I have written to you, and I don’t blame you for not answering me, because I sounded crazy, but it is a fact that we have a tradition in our family of Ice-Cream for dessert after dinner each night, but the kind of ice cream varies so, every night, after we’ve eaten, the whole family votes on which kind of ice cream we should have and I drive down to the store to get it. It’s also a fact that I recently purchased a new Pontiac and since then my trips to the store have created a problem….
You see, every time I buy a vanilla ice-cream, when I start back from the store my car won’t start. If I get any other kind of ice cream, the car starts just fine. I want you to know I’m serious about this question, no matter how silly it sounds “What is there about a Pontiac that makes it not start when I get vanilla ice cream, and easy to start whenever I get any other kind?” The Pontiac President was understandably sceptical about the letter, but sent an Engineer to check it out anyway.
The latter was surprised to be greeted by a successful, obviously well-educated man in a fine neighbourhood. He had arranged to meet the man just after dinner time, so the two hopped into the car and drove to the ice cream store. It was vanilla ice cream that night and, sure enough, after they came back to the car, it wouldn’t start.
The Engineer returned for three more nights. The first night, they got chocolate. The car started. The second night, he got strawberry. The car started. The third night he ordered vanilla. The car failed to start.

Now the engineer, being a logical man, refused to believe that this man’s car was allergic to vanilla ice cream. He arranged, therefore, to continue his visits for as long as it took to solve the problem. And toward this end he began to take notes: He jotted down all sorts of data: time of day, type of gas uses, time to drive back and forth etc.
In a short time, he had a clue: the man took less time to buy vanilla than any other flavor. Why? The answer was in the layout of the store. Vanilla, being the most popular flavor, was in a separate case at the front of the store for quick pick up. All the other flavors were kept in the back of the store at a different counter where it took considerably longer to check out the flavor.
Now, the question for the Engineer was why the car wouldn’t start when it took less time. Eureka – Time was now the problem – not the vanilla ice cream!!!! The engineer quickly came up with the answer: “vapor lock”.
It was happening every night; but the extra time taken to get the other flavors allowed the engine to cool down sufficiently to start. When the man got vanilla, the engine was still too hot for the vapor lock to dissipate.
The problems may sound crazy sometime. There is always a systematic approach for geting to the root cause. The engineer first off all, did believe that there is some technical reason behind the Pontiac getting stopped every time vanilla is bought. He collected every data. He tried to find pattern & found one. He then related the pattern with probable technical issue & reached root cause.
We in daily life, are facing such issues & had become use to it. Improvement start, if we do not accept these issues & work dedicatedly and systematically for digging out the root cause. After years of experience, numerous RCA (Root Cause Analysis) & reliability tools have been developed and are available openly.
We aim to provide expert solution for helping out our business partners for long term solution.
Contact Us, Click here
Start Following us on Facebook page, Pinterest and Linkedin.