We have a massive problem in the modern professional world, especially in fields like Product Management and Conversion Rate Optimization (CRO). We confuse “familiarity” with “understanding.”
We read a whitepaper, attend a webinar, or skim a book like How to Talk to Anyone, and because the words make sense as we read them, we assume we’ve learned the material. But then, a stakeholder asks a difficult “Why?” during a sprint planning session, or we try to explain a new strategy to a junior developer, and we stumble. We fall back on jargon. We use “corporate-speak” to hide the fact that we don’t actually know how the gears turn under the hood.
This is what Nobel Prize-winning physicist Richard Feynman called “the difference between knowing the name of something and knowing something.”
To solve this, he developed what we now call the Feynman Technique. It is the ultimate mental model for anyone who wants to learn faster, retain more, and communicate with authority.
The Core Philosophy: The Great Explainer
Richard Feynman was often called “The Great Explainer.” He didn’t earn this title because he was the smartest person in the room (though he often was), but because he refused to accept a definition he couldn’t break down into plain English.
He believed that complexity is a sign of confusion. If you can’t explain a concept to a ten-year-old, you haven’t mastered it; you’ve just memorized a sound. For a Product Owner, this is vital. If you can’t explain your product’s value proposition without using the word “synergy” or “robust,” your strategy is likely built on sand.
The 4-Step Framework for Mastery
The Feynman Technique is a simple, iterative process. You can apply it to a new coding language, a psychological principle like Social Proof, or a complex financial model.
Step 1: Choose Your Concept and Write It Down
Start with a blank sheet of paper. At the top, write the name of the concept you want to learn. This sounds trivial, but it creates a “Mental Anchor.” By writing it down, you are committing to a single focus.
Pro-Tip for PMs: Don’t pick “Product Management.” That’s too big. Pick “The RICE Framework” or “Secondary Effects of Feature Bloat.” Be specific.
Step 2: The “Kid Test” (Teach It to a Child)
Imagine a ten-year-old is sitting across from you. Explain the concept to them. You must write out your explanation or say it out loud.
The Rule: You are strictly forbidden from using jargon or “fancy” words.
-
Instead of “Conversion Rate Optimization,” say “Making it easier for people to buy what they want.”
-
Instead of “Scalability,” say “The ability for a tool to work just as well for a million people as it does for ten.”
When we use jargon, we fool ourselves. When we are forced to use simple language, we are forced to understand the logic behind the concept. If you find yourself reaching for a “Product Owner” buzzword, stop. That is your first sign of weakness.
Step 3: Identify the Knowledge Gaps
This is where the real learning happens. In Step 2, you will inevitably hit a wall. You will realize you can’t explain a certain part of the process without getting “stuck” or reverting to technical terms.
These are your Knowledge Gaps. They are the holes in your understanding.
Instead of being frustrated, be grateful. You have just identified exactly what you don’t know. Go back to your source material—your books, your mentors, or your data—and study only those specific gaps. Once you have a simple explanation for the “hole,” go back to Step 2 and continue the explanation.
Step 4: Simplify and Use Analogies
Now that you have the pieces, you need to assemble them into a cohesive story. Review your explanation and look for any remaining complexity.
The best way to solidify understanding is through Analogies. An analogy connects something new to something the listener already knows.
-
If you’re explaining Technical Debt, compare it to a messy kitchen: “If you don’t clean as you cook, eventually the kitchen becomes so messy you can’t cook at all.”
-
If you’re explaining A/B Testing, compare it to a fork in the road: “We send half the people left and half the people right to see which way gets them home faster.”
If your explanation sounds like a story, you’ve mastered it.
Why This is a “Cheat Code” for Career Growth
As a Senior Content Writer or a Product Owner, your value isn’t based on how much information you possess; it’s based on how much clarity you can provide.
1. It Builds “True” Confidence
There is a massive difference between “Performing Knowledge” (acting like you know) and “Possessing Knowledge.” When you use the Feynman Technique, you develop a deep-seated confidence. You aren’t afraid of being asked a “stupid” question because you’ve already asked yourself those questions during Step 2.
2. It Optimizes Communication (The CRO of Speech)
In CRO, we talk about removing friction from the user’s journey. Jargon is friction for the listener’s brain. By using the Feynman Technique, you remove the “cognitive load” from your stakeholders, developers, and clients. You become the person who “makes things make sense.”
3. Faster Iteration
Because you are only studying the “Gaps” (Step 3), you aren’t wasting time re-reading things you already understand. You are surgical with your time. You learn exactly what you need, you verify it, and you move on.
Practice: The “Learnoverblogging” Way
I am currently building my YouTube channel, Learnoverblogging: The PM Hub, based on this exact principle. I’m not spending hours on fancy transitions or high-end color grading. Why? Because the “blogging” (the aesthetic, the polish) is secondary. The “Learning” (the breakdown, the clarity) is the product.
By “Learning Out Loud,” I am putting myself through Step 2 of the Feynman Technique every single day.
Your Action Item:
Pick one concept you’ve been “faking” your way through. It might be a new AI tool, a financial metric, or a team management strategy.
-
Sit down for 10 minutes.
-
Try to explain it to an imaginary 8-year-old.
-
Find your “Gap.”
-
Patch the hole.
Mastery isn’t about being the smartest person in the room; it’s about being the clearest.
