MindMap Gallery 01 Feynman Technique (CTRS Model)
100 top mental models. Help you grow and take off. Feynman techniques help us improve our learning ability. Students in need can save them.
Edited at 2022-08-10 06:59:10This is a flowchart illustrating the process of archiving monthly failure analysis reports and tracking the implementation of improvement measures. The diagram is structured into five main steps, each with specific tasks and sub-tasks.Monthly Report Collection & Organization: This step involves collecting failure analysis reports from various departments, reviewing them for completeness, and categorizing them by product, failure mode, and severity. Root Cause Analysis & Statistics: Here, the focus is on categorizing causes, analyzing trends, identifying root causes, and compiling statistics on high-frequency failure modes and key components. Improvement Measure Formulation & Assignment: This step includes formulating improvement measures, assigning responsibilities, and setting timelines for implementation.Measure Implementation Tracking & Verification: It involves tracking the progress of implementation, verifying effectiveness, and confirming issue closure.Knowledge Base Update & Monthly Report Output: The final step covers archiving reports, updating the knowledge base, and compiling monthly summaries.This template can be easily reused and adapted using tools like EdrawMind to suit different organizational needs.
This is a timeline infographic detailing the annual product certification acquisition countdown process, structured into four sequential phases. The first phase, Certification Planning & Initiation, encompasses goal setting, timeline planning, resource preparation, defining specific certification objectives such as CCC/CE/FCC, formulating an annual plan with key milestones, and allocating necessary budget, personnel, and sample resources. Following this, the Application & Testing Phase involves material submission, coordination with certification agencies, core testing procedures, preparation of technical documents, application forms, and samples, selection of the appropriate certification agency, and execution of critical safety, EMC, and RF tests. The subsequent Rectification & Acquisition Phase focuses on addressing and rectifying any identified issues, re-verification processes, acquisition of the certificate, analysis of test issues, implementation of necessary fixes, and modification of samples for supplemental testing. Finally, the Countdown Monitoring phase emphasizes tracking progress, managing risks, monitoring remaining days and key milestones, managing time, technical, and cost risks, and maintaining effective internal and external communication throughout the process. This comprehensive template can be readily reused and adapted using tools like EdrawMind to meet diverse organizational requirements.
This is a flowchart detailing the weekly update and review plan for technical documents. The process is divided into six main stages, each with specific tasks and responsibilities. It begins with Weekly Planning, where the document scope is defined, update objectives are set, and schedules are arranged. Next, Document Updates involve maintaining various documents such as hardware design documents, test specifications, and BOM tables, alongside version control and archiving. Internal Review Preparation follows, focusing on compiling review materials, identifying participants, and setting agendas. The Review Meeting stage includes document examination, problem discussion, decision recording, and responsibility allocation. After the meeting, Review Feedback Processing takes place, involving issue tracking, document modification, quality checks, and closure verification. Finally, Output Deliverables are prepared, including official release versions, release notifications, review reports, and plans for the next week. This structured approach ensures systematic and efficient management of technical documents, and the template can be easily adapted using tools like EdrawMind.
This is a flowchart illustrating the process of archiving monthly failure analysis reports and tracking the implementation of improvement measures. The diagram is structured into five main steps, each with specific tasks and sub-tasks.Monthly Report Collection & Organization: This step involves collecting failure analysis reports from various departments, reviewing them for completeness, and categorizing them by product, failure mode, and severity. Root Cause Analysis & Statistics: Here, the focus is on categorizing causes, analyzing trends, identifying root causes, and compiling statistics on high-frequency failure modes and key components. Improvement Measure Formulation & Assignment: This step includes formulating improvement measures, assigning responsibilities, and setting timelines for implementation.Measure Implementation Tracking & Verification: It involves tracking the progress of implementation, verifying effectiveness, and confirming issue closure.Knowledge Base Update & Monthly Report Output: The final step covers archiving reports, updating the knowledge base, and compiling monthly summaries.This template can be easily reused and adapted using tools like EdrawMind to suit different organizational needs.
This is a timeline infographic detailing the annual product certification acquisition countdown process, structured into four sequential phases. The first phase, Certification Planning & Initiation, encompasses goal setting, timeline planning, resource preparation, defining specific certification objectives such as CCC/CE/FCC, formulating an annual plan with key milestones, and allocating necessary budget, personnel, and sample resources. Following this, the Application & Testing Phase involves material submission, coordination with certification agencies, core testing procedures, preparation of technical documents, application forms, and samples, selection of the appropriate certification agency, and execution of critical safety, EMC, and RF tests. The subsequent Rectification & Acquisition Phase focuses on addressing and rectifying any identified issues, re-verification processes, acquisition of the certificate, analysis of test issues, implementation of necessary fixes, and modification of samples for supplemental testing. Finally, the Countdown Monitoring phase emphasizes tracking progress, managing risks, monitoring remaining days and key milestones, managing time, technical, and cost risks, and maintaining effective internal and external communication throughout the process. This comprehensive template can be readily reused and adapted using tools like EdrawMind to meet diverse organizational requirements.
This is a flowchart detailing the weekly update and review plan for technical documents. The process is divided into six main stages, each with specific tasks and responsibilities. It begins with Weekly Planning, where the document scope is defined, update objectives are set, and schedules are arranged. Next, Document Updates involve maintaining various documents such as hardware design documents, test specifications, and BOM tables, alongside version control and archiving. Internal Review Preparation follows, focusing on compiling review materials, identifying participants, and setting agendas. The Review Meeting stage includes document examination, problem discussion, decision recording, and responsibility allocation. After the meeting, Review Feedback Processing takes place, involving issue tracking, document modification, quality checks, and closure verification. Finally, Output Deliverables are prepared, including official release versions, release notifications, review reports, and plans for the next week. This structured approach ensures systematic and efficient management of technical documents, and the template can be easily adapted using tools like EdrawMind.
Feynman Technique (CTRS Model) top mental model
What is the Feynman Technique?
1. four words
Concept concept
Teach teach others
Review Review
Simplify Simplify
2. The so-called Feynman technique is to use your own language to explain something clearly in the simplest words, preferably so that laymen can understand it. (The kind that an 8-year-old child can understand)
Why learn the Feynman Technique?
1. Input helps output, output forces input
2. Because teaching others is the best way to learn and apply what you teach
3. According to the learning pyramid theory, only listening and watching, learning without using can only remember 5~30%, but teaching others can remember 90% of the knowledge content.
4. Feynman model can help you accurately find knowledge blind spots and improve learning efficiency
5. Explaining knowledge with knowledge can improve the absorption rate of knowledge
6. Under the pressure of teaching, learning changes from passive to active.
7. There are a lot of blind dimensions when learning passively, and you don’t know that you don’t understand; only when you teach others, these blind dimensions will be exposed, which is to check for omissions and fill in the gaps.
How to use Feynman technique?
1. step
Step one: concept.
learn new concepts Express it in your own language. (Pretend to teach it (knowledge, concept) to an 8-year-old child, and try your best to make him understand what you are expressing)
Step Two: Review.
Review some of the stuck points in the process of explaining knowledge. A feedback and a record are needed
Step 3: Simplify.
Reorganize the language to make it organized and simplified. The explanation is more concise, clear and clear.
Step 4: Teach.
To see if there is anything wrong with your understanding, teach it to another person so that he can understand it too.
2. Way
output
speak out
comminicate
speech
lecture
Write it down
writing
simplify
Explanation of dimensionality reduction in popular vernacular
contact application
From now on, when I read books, I will no longer be busy reading, memorizing knowledge, and writing notes. But after reading it, tell it to yourself, or even tell it to others. Do more sharing output and help others solve problems. In the process of solving problems, you can check for omissions and fill in the gaps where you have not learned deeply or masterfully.
To test whether I really understand this concept, grab a friend next to me and explain this concept to him. If he understands it, it proves that I have learned it! Ha ha
I don’t pretend to be mean, I refuse to use lofty words, I use plain and down-to-earth language to express the concepts I have learned! For example, Brother Zhiyuan explained to me that electric current is like flowing water, and I still have a deep impression on him.
contact life
In the Internet age, it is very easy to spread content and get feedback, which can help us improve our content. Improve and resend, the quality will be better each time.
For example, it is very difficult for ordinary people to get a lot of feedback by writing articles. Even if the article is published in a newspaper or magazine, they still have to wait patiently for a reply or a phone call from the reader. But now, with just a click of the mouse, it is possible to receive comments or likes from readers in a few seconds. If the article is well written, feedback will come flooding in within a short period of time.
Every time I finish watching a video on Douyin or read an article and answer, I try my best to comment and leave messages below. This is actually a way of forcing input by output. I didn’t feel it at first, and I felt that I Nothing has changed, so I'm about to give up. But after persisting, one day I suddenly found that my language expression, organizational skills and writing skills had improved to a higher level. This is just like what Steve Jobs said. , if there are too many lines, a surface will be formed. We can use this surface to do various things, that is, quantitative changes lead to qualitative changes!