UNIT â IV_PCI Complaints: Complaints and evaluation of complaints, Handling o...
Â
problem identification.pptx
1. Participatory study
⢠Participatory study is more sustainable
⢠It is more on issue focused
⢠Active Involvement
⢠Action oriented
⢠Democratic decisions and results will be
benefited to masses
2. Problem identification problem
analysis
⢠Define the Problem. What is the problem?
⢠Step 2: Clarify the Problem
⢠Step 3: Define the Goals
⢠Step 4: Identify Root Cause of the Problem
⢠Step 5: Develop Action Plan
⢠Step 6: Execute Action Plan
⢠Step 7: Evaluate the Results
⢠Step 8: Continuously Improve
3. Problem statement
⢠A problem statement is a concise and concrete
summary of the issue you seek to address.
⢠Contextualize the problem. What do we
already know?
⢠Describe the exact issue
⢠What do we still need to know?
⢠Show the relevance of the problem. Why do
we need to know more about this?
4. ⢠Set the objectives
⢠What will you do to find out more?
5. Cause/ Effect Analysis
You reap what you sow
⢠The things you do are like planted seeds, and
those seeds produce a crop which is the result
of your actions.
⢠The quote is an example of the cause and
effect relationship. Your action, sowing good
or bad seeds, produces a reaction, a healthy
or rotten harvest.
6. Cause/ Effect Analysis
⢠A cause is an action, and the effect is the
resulting reaction
⢠In the cause and effect relationship, one or
more things happen as a result of something
else.
⢠A cause is a catalyst, a motive, or an action
that brings about a reactionâor reactions. A
cause instigates an effect.
7. Cause/ Effect Analysis
⢠An effect is a condition, occurrence, or result
generated by one or more causes. Effects are
outcomes.
⢠A cause is why something happens. An effect
is what happened.
⢠You canât have an effect without a cause, nor
can you have a cause without an effect
8. Cause/ Effect Analysis
⢠Cause and effect analysis, also called a âcause
and effect diagram,â is an assessment tool
that combines brainstorming and mind
mapping techniques to explore the possible
causes of an issue. It was developed by Kaoru
Ishikawa, a quality management pioneer in
the 1960s and originally used as a quality
control tool.