Le MONSTRUEUX système de révision des admis en médecine

Main ideas / concepts

• The “working method” obsession is a trap. Many students fail because they keep searching for a miracle method (often via social media) rather than building a stable, personalized system and improving it steadily.
• Top performers don’t mainly think in terms of “methods” or “work time” first. They focus on a deeper “vision”: implementing a revision system that produces results, then iterating it based on feedback.
• Working hours and motivation are not the differentiators. The argument is that:
  • Students who pass and fail can both work very long hours (e.g., 8 vs. 14 hours doesn’t reliably explain outcomes).
  • Everyone is motivated; goodwill/calling/genetics/social circle may influence outcomes statistically, but the main practical difference is still framed as system vs. non-system.
• Same tools can lead to different results because the system design (and weak components) differ.
  • Even with common tools (flashcards, reminders, blank sheet, Pomodoro, etc.), success varies.
• A revision “system” is not a “method.”
  • A method is a single technique.
  • A system is an interconnected set of components (“cogs and gears”) that work together across time and subjects.
• System efficiency is limited by its weakest component.
  • Even if most parts are strong, one weak factor (sleep, understanding, flashcard quality, etc.) drags everything down.
• Continuous improvement in versions (V1, V2, V3…) beats switching methods.
  • Treat the system as living and evolving, not fixed.
  • Regular data analysis is required to know what’s slowing the system down.
• Mental stability comes from reframing failure as “system problems,” not “you are bad.”
  • This reduces self-blame, helps students adjust without panic, and maintains hope.
• Key foundation pillars first.
  • Before optimizing techniques, the system must be built on sleep, exercise, and decompression.

Method / instruction list (6-step protocol)

1. Establish non-negotiable pillars (3 S’s):

   • Sleep
   • Exercise
   • Decompression/unwinding (time to rest between classes and bedtime) These foundations determine the baseline for how fast the whole system can run—because the system runs at the weakest component’s speed.

2. Choose 2–3 fixed techniques to start (don’t over-stack tools):

   • Examples mentioned: exercises + corrections, review notes using reminders, flashcards from mistakes, diagrams/simplified explanations.
   • Use multiple-choice questions regularly and review notes daily (several times a day).

3. Improve what you already use before adding more:

   • First, make your current techniques work “perfectly.”
   • Only after that, add additional methods for specific situations.

4. Take stock and personalize (track “why” you do actions):

   • Maintain a clear understanding of what you do and its role in your strategy.
   • Avoid copying influencer advice blindly (e.g., buying pre-made flashcard packs without understanding your strategy).

5. Set monitoring + tracking + checkpoints (data analysis must be regular):

   • Action monitoring file per course:
     • which courses
     • number of reviews/views
     • dates
     • notes (so you can later see trends/graphs)
   • Time tracking log:
     • measure actual productive study time (not just “I work 6am–10pm,” but real study vs. distractions like scrolling)
     • stop the timer for breaks/non-study activities
   • Checkpoints:
     • at least weekly (Sunday evening around 7 PM) to review grades/system and adjust
     • more frequent (even daily) during urgent periods or when struggling

6. Accept being bad at the beginning and follow the protocol until exam day:

   • Early performance will often be worse (September-self ≠ end-of-year-self).
   • The goal is not immediate excellence; it’s building a system that becomes excellent over time.
   • The system should reach higher “versions” by the exam.

Practical mechanism emphasized (“vision” of top students)

• Start with a stable system and fixed schedule intensity.
• Get results.
• If results aren’t good: keep the system stable, analyze, and fix the weakest component rather than changing methods or endlessly increasing hours.
• Only after the system is improved should the student increase workload/intensity (e.g., approaching mock exams/finals).

Core idea: don’t treat failure as a reason to “swap methods.” Treat it as a signal to debug the system.

Examples / case stories used to support the message

• Case 1 (older learner/refresher path):

  • Started very low rankings (e.g., 94/182, then 70/200, etc.).
  • Improved through versions (V3 onward), eventually reaching 11th/194 in imaging, and later 3rd place with ~17/20.
  • Key claim: he wasn’t panicking because he knew his system was evolving and had a history of improvement.

• Case 2 (student arriving in November):

  • Initially switched methods, became stressed and “sinking.”
  • After adopting the protocol and receiving daily feedback and daily improvements, she recovered and was accepted into medical school despite a disastrous first semester.

Key “lessons” summarized

• Stop hunting for a one-size-fits-all “miracle method.”
• Build a personal revision system with foundation pillars first.
• Use data analysis frequently to identify the weak component.
• Improve the system progressively via versions, not by swapping methods every two weeks.
• Reframe performance as system efficiency, not personal worth.
• Track actions and time, and run structured weekly/daily checkpoints.
• Accept early imperfection and commit to the protocol until exam day.

Speakers / sources featured

• Speaker: Nasser (implied by repeated address “Nasser” and the narrator’s name)
• Sources mentioned (not featured as direct speakers): coaching communities / “influencers,” YouTube/TikTok/Instagram (as places where students search for methods)