Skip to content
Published on

Find Your Own Method — Through Curiosity and Metacognition

🇰🇷KO🇺🇸EN🇯🇵JA
Split View필사 모드
Authors

Opening — The 5 a.m. That I Could Not Copy

For a while, I was a person who woke up at 5 a.m. More precisely, I was a person who was trying very hard to wake up at 5 a.m.

The trigger was simple. A developer I admired wrote on his blog that his life had changed thanks to a routine of "5 a.m. wake-up, two hours of deep work, then exercise." Judging by the traffic and comments, a great many people said it had worked for them too. I thought: this is proven. I just need to do exactly the same thing.

So I set my alarm for 5 a.m. The first week I survived on willpower. By the second week my head was foggy from noon onward. In the third week I dozed off in a meeting and a colleague asked if I was okay. By the fourth week, I would wake at 5 a.m., sit at my desk, stare blankly at the screen, and fall back asleep.

That routine was probably real for him. He was not lying. But it was a method shaped around his body, his sleep cycle, his job, his family situation. I am closer to a night owl, and my sharpest focus comes after 10 p.m. — a fact I was refusing to admit at the time. I had copied someone else's answer onto my own exam sheet.

This essay is a record, born from that failure, about how to find a method of your own. It gathers what I bumped into and learned while working at LINE, while learning English and Japanese and a bit of Chinese, and while playing table tennis. I tried to write it not as abstract self-help slogans but as procedures you can actually run.

Core Insight — Methods Cannot Be Copied, Only Principles Can Be Transplanted

First, let me clear up one misunderstanding. "Find your own method" absolutely does not mean "do not learn from others." If anything, it means the opposite.

The problem is that we try to import someone else's method wholesale. But a method is like a plant grown in the soil of that person's context. Uproot it and replant it in your own pot, and it usually withers. What can be moved is not the method itself but the principle that makes the method work.

The principle that made the 5 a.m. wake-up work for that developer was "secure a solitary block of uninterrupted focus." That principle is universal. But the specific implementation, "5 a.m.," belonged only to him. I had to carry the same principle into a different implementation: "two hours after 10 p.m."

In one sentence:

Extract the principle from someone else's method, then redesign the implementation to fit yourself.

This entire essay is really about how to practice that one sentence. And the two engines that make it possible are curiosity and metacognition.

Why Copying Is So Tempting

We keep copying even though we know it is risky, and there are reasons.

  1. Uncertainty is scary. If I design from scratch, I might be wrong. A proven method from someone else looks like "the answer," which is reassuring.
  2. Thinking costs energy. Analyzing my own situation and forming a hypothesis is far harder than searching and copying the top-ranked article.
  3. We want to lean on authority. If a famous, successful person did it, it feels like we can offload the responsibility onto them.

These three are human reactions. They are nothing to be ashamed of. But you have to be aware of them so you can ask yourself: "Am I copying right now simply because I do not want to think?"

The First Engine — Experimenting With Curiosity

Your own method does not appear by sitting at a desk and pondering. It appears only through experiments. And the fuel that keeps you experimenting without burning out is curiosity.

Curiosity Instead of Obligation

If you approach English with the obligation that "I must memorize 50 words every day," you will not last a month. But if you approach it with curiosity — "How many unfamiliar expressions show up in one episode of a show I love? If I catch them all, will the next episode be easier to follow?" — the story changes. It is the same vocabulary work, but now it has become a search for the answer to a question.

The heart of curiosity-driven experimentation is turning every attempt into the form of a question.

  • "Am I a morning person or an evening person?" → Do the same task in the morning and evening for two weeks and compare the output.
  • "Do I memorize better by writing by hand or by reading aloud?" → Split the same amount across both methods and test three days later.
  • "Do I focus better in silence or with a little ambient noise?" → Measure separately in a cafe and in a library.

It is fine if the answer turns out wrong. An experiment is, by definition, the act of confirming that a hypothesis can be wrong. A wrong answer is still "data about me."

Designing a Small Experiment

Grand experiments that overhaul your whole life fail. A good experiment is small, time-bound, and measurable.

Bad experiment: "Starting this year I will change my life with a miracle morning."
  - Too big / no deadline / not measurable / no exit

Good experiment: "For two weeks I will shadow English from 10-11 p.m.,
                  and rate my focus 1-10 each time I finish.
                  If the two-week average is under 6, I change the time slot."
  - Small / two-week deadline / scored measurement / clear decision rule

I call this a "two-week sprint" and apply it to almost all my learning. Two weeks is too short for a habit to set in, but it was long enough to get a feel for whether something suits me.

70-20-10 as a Reassuring Excuse

There is a 70-20-10 learning model often cited in corporate training. It is a rule of thumb that people learn roughly 70 percent from real experience and challenging tasks, 20 percent from interaction and feedback with others, and 10 percent from formal education such as books and lectures. It is closer to an intuition about ratios than a precise scientific law, but it gave me a useful excuse.

The message is clear. Do not cling only to books and lectures (the 10 percent); shift your center of gravity toward hands-on experiments (the 70 percent). Reading about someone else's method in a book is the 10 percent. Your own method is built in the remaining 90 percent.

The Second Engine — Objectifying With Metacognition

If curiosity turns the wheel of experiments, metacognition is the ability to read those experiments. Metacognition is "thinking about thinking" — the ability to step back and observe what you know and do not know, and how you are learning.

Do Not Mistake Familiarity for Skill

The scariest trap in learning psychology is the "fluency illusion." Read a textbook several times and the content becomes familiar to your eyes. We mistake that familiarity for "I know this now." But familiarity and retrieval ability are completely different things.

The famous study by Roediger and Karpicke shows this well. A group that, after reading, closed the book and tried to recall the material on their own (retrieval practice) far outperformed a group that merely reread the same material, when it came to long-term memory. This is the "testing effect."

Metacognition's first job is to break this illusion. Distinguish "what became familiar through reading" from "what I can write down again on a blank page." After studying a concept, I always write out an explanation on an empty page with nothing in front of me. Wherever I get stuck is what I truly do not know.

A Learning Log — Externalizing Metacognition

Metacognition done only in your head fades quickly. I externalize it in writing. Not a grand diary, but a three-line learning log per day.

[2026-06-12]
- What I did: Shadowed one Japanese news clip (NHK Easy)
- Where I got stuck: Still distinguishing the particles 'wa/ga' only by feel
- What to change next: Tomorrow, try dictation on the same sentence first

Stack just two weeks of these three lines, and patterns emerge on rereading. "Ah, in listening I always collapse on particles." "My sessions logged at night satisfy me far more than afternoon ones." These surface as data. They are the raw material for designing your own method.

The Premise of a Growth Mindset

Carol Dweck's concept of a growth mindset is the foundation here. If you accept "I am just not a morning person" as a fixed fact, there is no reason to experiment. But if you ask, "The data so far favors the evening, but would changing the environment change that?" the experiment comes alive again.

That said, do not mistake a growth mindset for a magic spell that "anything is possible if you try." Dweck herself cautioned against this in later interviews. A growth mindset is the attitude of "taking on challenges while changing strategies," not "just try harder." The point is adjusting strategy, not the sheer amount of effort.

Language Learning, the Best Laboratory

There is no better field for practicing how to find your own method than language learning. Feedback is relatively fast, and there are so many variables that the things to experiment with are endless. Let me unpack what I learned across English, Japanese, and Chinese.

English — Until I Found Comprehensible Input

For a long time I approached English with "vocabulary lists plus grammar books." My TOEIC score went up, but my mouth froze in meetings. When I had to communicate in English with colleagues in Japan and Taiwan at LINE, I realized the words I had memorized almost never came up in real situations.

The turning point came when I encountered Stephen Krashen's concept of "comprehensible input." The hypothesis is that the key to acquisition is encountering a large amount of content slightly above your current level (i+1) while still understanding it. It is not a theory that is fully agreed upon in academia, but for me it was a decisive hint to change direction.

I started an experiment to find "content I understand about 80 percent of." Not news that was too hard, nor children's content that was too easy, but the developer YouTube channels I loved sat exactly in that spot. The unknown 20 percent filled in naturally, and above all, I kept going. Because it was fun.

Japanese — Building the Korean-Speaker Advantage Into the Design

Japanese called for the opposite strategy from English. For a Korean speaker, Japanese grammar is easy to enter because the word order is almost the same. Instead, you tend to collapse on pronunciation, kanji readings, and subtle nuance.

So I boldly cut my grammar study time and poured time into listening and repeating aloud. "Spend less time on the parts similar to Korean, and concentrate time on the parts that differ" was a design reflecting my starting point as a native Korean speaker. This is exactly why an English learner cannot simply copy me. Their starting point is different.

Chinese — Set the Metric Early

I am still a beginner in Chinese. Precisely for that reason, I decided early on "what to measure." At the beginner stage, I learned within a week that the bottleneck for everything was not word count or grammar progress but the ability to hear and distinguish tones. So the metric for my first two-week Chinese sprint was "accuracy when four tones are played in random order."

The very fact that the metric differs by language is itself the message. English was "hours of comprehensible input," Japanese was "dictation accuracy," Chinese was "tone recognition rate." Even when the same person pursues the same goal (acquiring a foreign language), a different target means a different method and a different measurement.

Comparing the Three Language Strategies

ItemEnglishJapaneseChinese
Difficulty for Korean speakerUpper-mid (different order)Low (similar order)Mid (tone barrier)
Early bottleneckListening, real expressionsPronunciation, kanjiDistinguishing tones
What I cutVocabulary memorizationGrammar studyConversation ambition
What I increasedComprehensible inputShadowing, dictationTone listening drills
Two-week metricContent comprehension rateDictation accuracyTone recognition rate

What matters in this table is not the contents of the cells but the fact that every cell is filled in differently. There was no single all-purpose study method.

Designing the Environment and Rhythm That Fit You

A method does not work in a vacuum. It works on the stage of environment and rhythm. Even for the same person, change the stage and the outcome changes.

Finding Your Focus Time

In "Deep Work," Cal Newport argues that uninterrupted, deep concentration is the core asset of knowledge work. But when that time should be differs from person to person. Newport's message is not "do it in the morning" but "secure an uninterrupted block."

I reread two weeks of my learning log and marked the time slots of sessions rated 8 or higher in satisfaction. They were overwhelmingly after 9 p.m. It was the moment data beat my intuition.

Matching Your Energy Curve

Energy is not constant through the day. It is reasonable to place hard tasks (learning new concepts, writing) at high-energy times and light tasks (review, vocabulary retrieval) at low-energy times. I kept failing when I tried to learn new concepts in the sleepy slot right after lunch; once I switched that slot to light review only, my satisfaction rose sharply.

Spaced Repetition and Rhythm

Memory leaks faster the more you cram it in at once. Spaced repetition is a method of gradually lengthening review intervals so you recall right before forgetting. This is close to a universal principle that works for almost everyone. But the specific intervals and tools must be tuned by the individual. Some use an app (like Anki), some use paper cards, some use a learning log. The principle is the same; the implementation differs.

What Table Tennis Taught Me

I play table tennis. At first I copied a strong player's form exactly. But with my height, my arm length, my wrist flexibility, that form only felt awkward. Something my coach said stayed with me: "Textbook form is a starting point, not a destination. Once you have the fundamentals, you have to carve it down to fit your own body."

That is exactly the theme of this essay. Learn the fundamentals (the principle) faithfully, but carve the final form (the implementation) to fit your own body. Sport, study, work — in the end it was the same story.

Deeper Language Experiments — A Record of Failed Attempts

List only success stories and it sounds like a lie. In reality, more than half of the language experiments I ran were failures. Those failures taught me more.

English — The Failed Full-Episode Dictation

When I first learned the concept of comprehensible input, I got excited and ran an experiment to dictate an entire episode of a show I loved. It took two hours per episode, and by the first week I was utterly drained. My learning log recorded satisfaction of 3 and 4 every day. The two-week result was clear: this was too heavy and unsustainable for me.

What I learned here is that "even a good principle fails when implemented at the wrong intensity." Dictation itself is an effective technique. But when I lowered the intensity — dictating only the 30-second stretch where I got stuck rather than the whole episode — satisfaction rose to the sevens and it finally became sustainable. I kept the principle and adjusted only the intensity of the implementation.

Japanese — The Failed Brute-Force Kanji Memorization

I also ran an experiment of brute-force memorizing 30 Japanese kanji a day. Within three days everything I had memorized earlier leaked out, because I ignored the spaced-repetition principle and crammed it all at once. So I cut to 10 a day and switched to a method of mixing in and retrieving words from three days earlier, and retention rose sharply. A small amount many times beat a large amount once.

Chinese — The Failure of Understanding Tones Only in My Head

I thought I could just memorize Chinese tones from a chart. First tone is high and flat, second tone rises, and so on. I memorized the chart perfectly, yet when I heard actual speech I still could not distinguish them. Once again I confirmed that knowledge and retrieval ability are different. In the end I abandoned chart memorization and switched to a self-test of listening to random tones for five minutes a day and identifying them. Another case where retrieval practice beat understanding.

The common thread across these three failures is clear. The principles (comprehensible input, spaced repetition, retrieval practice) were right, but the first implementation did not fit me. Failure was not evidence that the principle was wrong; it was a signal to adjust the implementation.

The Measure-and-Adjust Loop

Everything so far ultimately reduces to one repeating loop. I call it the five-step loop of "observe → hypothesize → experiment → measure → adjust."

1. Observe   : What is not working right now? (e.g., I cannot follow meeting English)
2. Hypothesize : Why? (e.g., not enough exposure to real expressions)
3. Experiment : What will I change for two weeks? (e.g., 20 min of English podcast daily)
4. Measure   : How will I gauge the effect? (e.g., weekly self-score of meeting comprehension)
5. Adjust    : Given the result, what do I change? (keep if score rises, change if it stalls)

The life of this loop is step 4, measurement. Without measurement, all you have is "a feeling that I worked hard," and you cannot know the real effect.

How to Choose a Metric

A good metric satisfies these three things.

  1. It measures outcome, not action. Not "I studied every day" but "my comprehension rate went up."
  2. It is measured neither too often nor too rarely. Measure hourly and the noise is huge; measure quarterly and it is too late. Two weeks was my standard.
  3. It can be scored. It must convert to a number such as 1-10, an accuracy rate, or time, so a trend becomes visible.

A Practice Checklist

For those just starting, here is a one-cycle checklist you can follow as is.

  1. Pick just one area that frustrates you most right now. (Several at once fails.)
  2. Turn that frustration into a one-sentence question. ("Why can't I follow meeting English?")
  3. Form just one hypothesis. (More than one mixes variables.)
  4. Design a small two-week experiment. Decide one action to do daily.
  5. Set the metric in advance. Decide before the experiment starts to stay objective.
  6. Write a three-line learning log each day. What you did, where you got stuck, what to change.
  7. After two weeks, reread the log and look at the score trend.
  8. Decide whether to keep, adjust, or discard. Then return to step 1.

Run these eight steps just two or three times, and even when you read someone else's article you will automatically ask, "What principle should I take from this person's method, and how should I change the implementation?"

You Do Not Need Fancy Tools

Many people ask which app they need to install for all this. Honestly, the tool barely matters. For a while I tried flashy tracking apps, but the tools that survived longest were a three-line learning log in my phone's notepad and one simple table for recording scores. The simpler the tool, the less friction, so you actually keep using it. The point is not the sophistication of the tool but the consistency of recording and the habit of rereading. A single paper notebook and a pen are enough to run every procedure in this essay.

Balance — The Opposite Trap of Blind Stubbornness

Reading this far, there is a risk of taking it as "right, ignore everyone and go my own way." That is the trap in the exact opposite direction. Let me point out the traps you can fall into while overemphasizing your own method.

Trap 1 — Ignoring Proven Fundamentals

"Your own method" does not mean you may skip the fundamentals. In table tennis, fundamentals like grip and stance are a proven foundation shared by nearly all masters. Ignoring this with "I'll grip differently" is not your own method; it is just a bad habit. You must distinguish what is a universal principle from what is the domain of individual difference.

Trap 2 — Using Experiments as an Excuse Never to Go Deep

If you only ever switch to a new method, you reach depth in nothing. The core of "deliberate practice," as Anders Ericsson describes in "Peak," is focusing on weaknesses and repeating them long enough. Experiments exist to find a method, not as an excuse to dodge depth. Once the method is set, what follows is the territory of tedious repetition.

Trap 3 — Protecting Your Ego by Ignoring the Data

The most dangerous stubbornness is averting your eyes from clearly poor measurements because of the ego that "my method is right." My 5 a.m. experiment was like that. The data (afternoon fog, dozing in meetings) was already signaling by week three, but I held on one more week saying "my willpower is just weak." The real courage of metacognition is admitting, with data, that your hypothesis was wrong.

Trap 4 — Stopping Learning From Others

Paradoxically, the fastest path to finding your own method is observing others a great deal — not to copy, but to extract principles. A good learner watches others' methods more, dismantles them more critically, picks out only the principles, and reassembles them into something of their own. This is why 20 percent of 70-20-10 is interaction with others.

Trap 5 — Getting Addicted to Experimenting Itself

This is the trap I realized last. For a while I found testing new study methods so fun in itself that I spent more time changing tools and methods than actually mastering anything. I switched note apps five times and jumped between vocabulary apps three times. Each time I felt "this tool is the real one," yet the number of words I actually memorized did not grow.

I call this the "meta-work trap." Refining your method feels enjoyable and productive, but it can become an elaborate excuse to dodge the tedious work of producing real output. So I made a rule: "Change a tool or method only once per cycle (two weeks). Within that, do nothing but real work with the chosen method." I separated experimenting from executing by time.

How a Good Learner Watches Others

The best habit for avoiding these traps is, paradoxically, to watch others more and better. At LINE I often watched the screen of a colleague who wrote great code over his shoulder. But I watched not "which shortcut does he use" but "in what order does he break the problem down." The former is implementation (something to copy), the latter is principle (something to transplant). The same observation becomes either copying or raw material for design, depending on what you choose to look at.

Copying vs. Your Own Method — At a Glance

AspectBlind copyingBlind stubbornnessHealthy own method
Learn from othersCopy wholesaleBarely learnExtract principle only
MeasureNoIgnore itCore tool
When wrongBlame othersRefuse to admitRevise hypothesis
FundamentalsMimic without contextIgnoreLearn faithfully
ResultWithersStalls or declinesGradual improvement

The healthy path lies in the middle of the two extremes. Learn fully from others without copying wholesale, push your own way while staying humble before the data.

What LINE Taught Me — Metacognition Through Code Review

The first time I felt the power of metacognition in my body was not from a book but from code review during my days at LINE. As a junior, I focused only on writing "code that works." But when I gathered the review comments from senior colleagues, I noticed the same remarks repeating: "Split this function so it does one thing only," "This variable name does not reveal its intent," and so on.

At first I fixed each comment only where it landed. Then it hit me: this is exactly like an error notebook for English dictation. So I began sorting the review comments I received and stacking them in a note. After about a month, my weaknesses stood out clearly as data. More than half of the problems in my code came down to a single pattern: "this function carries too many responsibilities."

That is the essence of metacognition. Anyone can fix an individual mistake as it appears. But gathering mistakes, finding the pattern, and attacking the root of that pattern is work of a different order. I changed from a person who receives review comments into a person who analyzes the distribution of his own review comments, and after that the frequency of the same remarks dropped noticeably.

What is interesting is that this code-review error notebook is really an application of retrieval practice and spaced repetition. Pulling a comment back out days later and self-checking — "Did I avoid this trap in this code?" — was a self-test. A principle from learning psychology had been transplanted into the entirely different implementation of workplace code review.

Copying vs. Designing — What Is the Difference

"Copy someone's method" and "extract the principle from someone's method and design my own" look similar on the surface. Both reference others. But the process and the result are completely different. Here is the difference I came to see by moving back and forth between the two.

AspectCopy as-isExtract principle, then design
Opening questionWhat should I doWhy did this work
What you takeA concrete action (5 a.m.)The working principle (uninterrupted focus)
Analysis of my contextSkippedStart point, rhythm, constraints analyzed first
MeasurementBarely anyA metric set from the start
When it does not fitBlame willpower, self-blameChange the implementation and re-test
Asset accumulatedNone (search anew each time)Data about myself
One year laterStill hunting for another methodA methodology of my own has formed

The most important rows in this table are the last two. Copying does not accumulate. If it does not fit this time, you simply return to the search box. Designing, by contrast, stacks "data about myself" each cycle, and that data makes the next experiment faster and more accurate. It is an asset that compounds.

Case Study — A Two-Week Table Tennis Backhand Log

Abstract talk does not land, so let me publish an actual experiment I ran, the log just as it was. The topic was neither English nor Japanese but a table tennis backhand. For a long time I struggled with my backhand drive catching the net.

First I set the observation and hypothesis. "The backhand catches the net (observation) → maybe the racket angle is too closed (hypothesis)." Then I set the metric: "sets of 10 balls, five sets, the rate that cleared the net." Measuring the baseline before starting, I got 22 of 50 balls, 44 percent.

[Two-week table tennis backhand log — metric: success rate out of 50]

Day 1  Baseline: 22/50 (44%) — not conscious of racket angle
Day 2  Hypothesis A: open the angle slightly  → 27/50 (54%)
Day 4  Conscious only of angle, now overshooting. New variable: swing length
Day 6  Hypothesis B: angle + shorter swing  → 31/50 (62%)
Day 8  Bad-condition day. 24/50 (48%). Logged as noise, held judgment
Day 10 Applied pushing with the forearm instead of the wrist → 36/50 (72%)
Day 12 Tried to reproduce the same feel → 35/50 (70%). Reproducible, not luck
Day 14 Final: 38/50 (76%) — +32 points vs. baseline

Conclusion: the key variable was not 'angle' but 'pushing with the forearm.'
     The first hypothesis (angle) was only partly right. Without measurement,
     I would have stalled forever, conscious only of the angle.

What I want to highlight in this log is the "held judgment" on Day 8. Had I scrapped the hypothesis on seeing the low score of a bad-condition day, saying "I knew it would not work," I would never have met the breakthrough on Day 10. A single measurement contains noise. You must look at the trend. And it matters that the first hypothesis (angle) was only partly right. Experiments often bring back an answer different from your first thought.

Metacognition Check — A Four-Step Self-Question Frame

Telling someone to "step back and observe" is vague. So when I get stuck in some learning or work, I made it a habit to throw the following four questions in order.

  1. What am I mistakenly assuming I know? Check whether you are mistaking familiarity for skill. Writing an explanation on a blank page reveals it instantly.
  2. What is the real cause of the block right now? Find the root, not the surface symptom. The root of "I cannot follow meeting English" may be not vocabulary but a lack of exposure to real expressions.
  3. Am I copying right now because I do not want to think? The question that demands the most honesty. Pause once before opening the search box.
  4. Is the data colliding with my ego? Check whether you are averting your eyes even though the measurement contradicts your hypothesis.

These four questions correspond exactly to the core traps covered in this essay. Number one is the fluency illusion, number two a wrong hypothesis, number three blind copying, number four blind stubbornness. Running this checklist once whenever you are stuck lets you quickly diagnose which trap you have fallen into.

Frequently Asked Questions (FAQ)

Q. I have no time to experiment. Can you just hand me one proven method? I completely understand. But "proven" was proven in that person's context. The less time you have, the more a small experiment is the answer. Filtering out a bad fit quickly with a two-week experiment saves more time than clinging to it for six months.

Q. How do I tell what is a universal principle and what is the domain of individual difference? Generally, "things nearly all experts share" are close to principles (e.g., spaced repetition, retrieval practice, fundamentals). Meanwhile, "things on which people give opposite testimony" are the domain of individual difference (e.g., time of day, music or not, handwriting or not). The latter is exactly what is worth experimenting with.

Q. Keeping a learning log feels like too much hassle. Three lines a day is enough. What you did, where you got stuck, what to change. Try to write it long like a diary and you will not last. The point is not length but consistency and rereading later.

Q. It is hard to score a metric honestly. Aren't self-scores subjective? They are subjective, true. But if the same person scores consistently by the same standard, the absolute value may be inaccurate while the trend is fairly accurate. What we need is not the absolute score but the direction: rising or stalling.

Q. I copied someone's method and it fits me really well. Is that copying? No. If you tried it and measured and it fit, that has already gone through an experiment. The problem with copying is taking it wholesale "without verification," not denying the very possibility that someone else's method might fit you.

Q. If I change my method every two weeks, won't I never build depth? Good question. The key is to distinguish an "exploration phase" from a "convergence phase." The first few cycles are exploration to find a method that fits you; here it is fine to change every two weeks. But once the method is set and the score starts rising steadily, you enter the convergence phase, where you dig deep into the same method with deliberate practice. Explore forever and you never reach the depth Ericsson describes. The experiment is only the entrance, not the destination.

Q. I am learning several things at once (work, English, exercise). How do I manage experiments? I recommend keeping only one active experiment at a time. Even with several areas, put the experimental variable only on the one that frustrates you most right now and keep the rest at their current state. Run several experiments at once and the variables mix, so you cannot tell what produced the effect. This is the same as the controlled-variable principle in science: change one variable at a time.

Q. My metric improved, but how do I know it was my method and not just the passage of time? It is hard to separate perfectly. But two things help. First, always measure a baseline before the experiment. Second, check whether the score drops when you briefly remove the variable. In the table tennis experiment, if deliberately not "pushing with the forearm" sent the score back down, that is strong evidence it was the real cause.

Closing — Read Yourself Rather Than Seek the Answer

After the 5 a.m. experiment failed, I blamed myself for a while. "Why can't I do what everyone else does?" Now I think the question itself was wrong. It was not what everyone does; it fit that one person, and I simply had a different answer.

Finding your own method is not a grand epiphany. It is a tedious, faithful repetition of throwing small experiments with curiosity, reading the results honestly with metacognition, and adjusting little by little according to measurement. What we truly learn in that process is not English or Japanese or table tennis form but the user manual for the system that is myself.

And that manual keeps updating across a lifetime. The rhythm that fit me in my twenties may not fit me in my thirties, and that is not a failure but the start of a new experiment. Do not try to find the answer; become someone who reads themselves. The answer changes every year, but the ability to read yourself compounds for life.

Looking back, the real gift of the 5 a.m. experiment was the failure itself. Without it I would not have gotten the data that "I am a night owl," nor would I have designed my night hours into my most powerful weapon. Every failed experiment gives you one square of information: "this is not me." Stack those squares and they become an increasingly clear self-portrait. So do not blame yourself too much when an experiment fails. Failure does not chip away at you; it draws your outline.

And the most important companion through all of this is kindness toward yourself. Seeing the data honestly and driving yourself harshly are different things. A good experimenter analyzes their failure data coldly while accepting the failure warmly as a human being. Only on that balance can you sustain experimenting for a lifetime.

I hope you start by picking the single most frustrating area today and turning it into a question. That is where your own method begins to grow.

The Whole Thing in One Sentence

If I compress this long essay into a single sentence, it is this. Learn principles from others, gather data from yourself, and reassemble the two anew every time. Curiosity makes that assembly enjoyable, and metacognition keeps it honest. Do not try to memorize the answer; cultivate the ability to read yourself. That ability outlasts any single method.

If you take only one thing from reading this, let it be "one two-week experiment." An insight you only read stays at 10 percent; only an experiment you actually run becomes the remaining 90 percent.

When that one experiment ends, good result or bad, you will be a person who knows yourself a little better than before. That is all of it, and that is the heart of it.

References

Discuss on Twitter • View on GitHub