Effective problem-solving algorithm (EPSA)
It is a basic method of Troublehacking for
research and development of external systems
research and development of external systems
TERMS
Effective problem-solving algorithm (EPSA) – it is a basic method of Troublehacking that allows to invent nonstandard solutions and put them into practice through deep analysis of non-technical systems. It is based on system analysis, risks theory and tools of Theory of Inventive Problem Solving (TRIZ).
Goal's core – a method for the detailing of the end results. It answers the question "what should be being done" by the systems at the moment of goal fulfillment.
Core's obstacles – a fully elaborated property of the system that should be eliminated or modified for the implementation of the goals' cores.
Perfect end result (PER) – one of the basic terms of TRIZ. Problem solving with minimum (or ideally none) resources (time, money, skills, energy, connections, etc.)
Goal's core – a method for the detailing of the end results. It answers the question "what should be being done" by the systems at the moment of goal fulfillment.
Core's obstacles – a fully elaborated property of the system that should be eliminated or modified for the implementation of the goals' cores.
Perfect end result (PER) – one of the basic terms of TRIZ. Problem solving with minimum (or ideally none) resources (time, money, skills, energy, connections, etc.)
DESCRIPTION OF THE EFFECTIVE PROBLEM-SOLVING ALGORITHM
1) Entries
Information about a problem or description of a goal. Useful facts, conditions and limits.
2) Goal's core
Finding what should be being done at the moment when the end result is being achieved.
3) A list of stages
Creating a list of the most obvious stages before the end result.
4) Subgoals' cores
What should be being done for the full implementation of each stage? Concise and clear subgoals.
5) Systems
Writing down all systems used on all stages. Generally, they are the same.
6) Perfect end result (PER)
Taking each stage and writing for each system's PER in which "the system itself implements the subgoals' cores".
7) List of obstacles
Defining obstacles for each stage that prevent the implementation of the subgoals' cores.
8) Obstacles' cores
Defining a property of the system that creates the obstacles. It will be a subject for elimination or modification.
9) Primary brain-stormIndependently or in a team of professionals trying to come with up with ways to implement all subgoals' cores for each PER and solutions for each obstacle. Using our imagination and personal experience.
10) Sorting out resources
Sorting out our check list of resources, trying to visualize and speaking them out loud. Going through each PER and applying resources forming realistic options for the implementation of the subgoals' cores.
11) Optimization of ideas
Writing down all invented ideas, sorting them out and checking their credibility independently or with professional help. Isolating most simple and effective ideas that can be implemented with minimum expenses in the nearest time while waiting for the end result.
12) Massive testing of ideas
With minimum expenses (money, time, etc.) within a short time put into practice the most simple and effective ideas in order to calculate which of them are the most effective in achieving the end results.
13) Scaling of the best ideas
Investing resources into ideas that have been proven to be effective during the testing.
Information about a problem or description of a goal. Useful facts, conditions and limits.
2) Goal's core
Finding what should be being done at the moment when the end result is being achieved.
3) A list of stages
Creating a list of the most obvious stages before the end result.
4) Subgoals' cores
What should be being done for the full implementation of each stage? Concise and clear subgoals.
5) Systems
Writing down all systems used on all stages. Generally, they are the same.
6) Perfect end result (PER)
Taking each stage and writing for each system's PER in which "the system itself implements the subgoals' cores".
7) List of obstacles
Defining obstacles for each stage that prevent the implementation of the subgoals' cores.
8) Obstacles' cores
Defining a property of the system that creates the obstacles. It will be a subject for elimination or modification.
9) Primary brain-stormIndependently or in a team of professionals trying to come with up with ways to implement all subgoals' cores for each PER and solutions for each obstacle. Using our imagination and personal experience.
10) Sorting out resources
Sorting out our check list of resources, trying to visualize and speaking them out loud. Going through each PER and applying resources forming realistic options for the implementation of the subgoals' cores.
11) Optimization of ideas
Writing down all invented ideas, sorting them out and checking their credibility independently or with professional help. Isolating most simple and effective ideas that can be implemented with minimum expenses in the nearest time while waiting for the end result.
12) Massive testing of ideas
With minimum expenses (money, time, etc.) within a short time put into practice the most simple and effective ideas in order to calculate which of them are the most effective in achieving the end results.
13) Scaling of the best ideas
Investing resources into ideas that have been proven to be effective during the testing.
MULTIPURPOSE RESOURCES CHECKLIST
1. Is it applicable in a particular medium?
Internet, software, distribution in a medium, country, city, street, building, spot, crowded place..
2. Is it applicable at particular events?
Community, event, membership club, competition…
3. Is it applicable at particular time?
Time of the year, time of day, holidays, special public events, events in life…
4. What people will benefit from its implementation?
Persons, communities, organizations…
5. Is it feasible under particular status?
Head of the system, creator of the system, head, manager, couch, star, famous person…
6. Is it implementable for money?
Hire a professional, provoke participants' interest with rewards…
7. Is it doable when you know something or have a particular skill?
To know how to do something, being able to influence people, medium, the elements of the system's core…
Internet, software, distribution in a medium, country, city, street, building, spot, crowded place..
2. Is it applicable at particular events?
Community, event, membership club, competition…
3. Is it applicable at particular time?
Time of the year, time of day, holidays, special public events, events in life…
4. What people will benefit from its implementation?
Persons, communities, organizations…
5. Is it feasible under particular status?
Head of the system, creator of the system, head, manager, couch, star, famous person…
6. Is it implementable for money?
Hire a professional, provoke participants' interest with rewards…
7. Is it doable when you know something or have a particular skill?
To know how to do something, being able to influence people, medium, the elements of the system's core…
HISTORY
Effective problem-solving algorithm (EPSA) contains methods of the Theory of Inventive Problem Solving (TRIZ) created by a soviet inventor and engineer Genrich Altshuller (~1946). In contrast to TRIZ, Effective problem-solving algorithm (EPSA) was created to combat life problems, not technical tasks. The author of the effective problem-solving algorithm (EPSA) is Ilya Vladimirovich Volochkov. The first models of EPSA and Troublehacking were created and put into practice in 2012. It was published for the first time in 2018 [A Realist's Diary: Money, Relationships and The Meaning of Life]