Feynman Technique for Multiple Projects: How to Simplify, Retain, and Execute Without Overlap

The Feynman Technique is a 4-step method to deconstruct, simplify, and retain complex concepts by explaining them in plain terms. When managing multiple projects—e.g., a marketing campaign, a software sprint, and a personal event—it prevents mental overlap by forcing you to translate jargon into actionable clarity. Here’s how it works for multi-project contexts:

• 1. Choose a concept and explain it like you’re teaching a 10-year-old. Example: For a blockchain in a finance project, write: 'It’s a shared notebook where everyone can add entries, but no one can delete or alter past records.' Avoid domain-specific terms like 'decentralized ledger.'
• 2. Identify gaps by underlining where you resort to jargon or blank out. Example: If you’re explaining agile methodology to a non-tech team, you might realize you don’t know how to describe sprints without using software terms. That’s your gap.
• 3. Simplify with analogies from other projects. Example: Compare asynchronous communication (remote work) to 'leaving sticky notes for your roommate'—a metaphor that works for both tech and non-tech teams.
• 4. Review and organize: Rewrite the explanation from simplest to most complex, then tailor it to each project’s context. Example: A generic definition of prioritization ('choosing what to do first based on impact') becomes specific for a marketing project ('impact = conversions') vs. a development project ('impact = blocking dependencies').

Step-by-Step: Feynman Technique for Prioritization Across 3 Projects (Real Example)

You’re juggling three projects with overlapping deadlines:

• Project 1 (Marketing): Launch an email campaign (deadline: 2 weeks).
• Project 2 (Development): Learn a new framework (deadline: 1 month).
• Project 3 (Personal): Organize a family event (deadline: 3 weeks).

The shared concept is prioritization. Here’s how to apply the Feynman Technique:

Step 1: Simple Explanation

Write: 'Prioritization is deciding which tasks to do first, which to delay, and which to drop, based on what moves the needle most and what can’t wait.'

Step 2: Identify Gaps

Reread your explanation. You’ll notice you haven’t defined 'moves the needle' for each project. For the email campaign, it’s open rates; for the framework, it’s ability to deliver the internal project on time; for the event, it’s guest satisfaction. This is your gap.

Step 3: Simplify with Analogies

Use a universal metaphor: 'Prioritization is like packing a backpack. You can’t take everything, so you choose lightweight items with high value (e.g., a first-aid kit) and leave out heavy, non-urgent items (e.g., a book).' Apply it to each project:

• First-aid kit (high value, little time): Sending emails on high-open-rate days (Project 1), learning basic framework commands (Project 2), confirming key guests (Project 3).
• Book (low value, much time): Designing the perfect email template (Project 1), mastering advanced framework features (Project 2), choosing event decorations (Project 3).

Step 4: Review and Organize

Rewrite your prioritization definition with concrete examples for each project. Store it in a 'Feynman glossary' (a shared doc or app) and review it when deadlines overlap. Example output:

• Generic: 'Prioritization = choosing tasks based on impact and urgency.'
• Marketing: 'Prioritize tasks that increase open rates (e.g., subject lines) over those that don’t (e.g., template design).'
• Development: 'Prioritize commands that unblock dependencies (e.g., API calls) over nice-to-have features.'
• Personal: 'Prioritize tasks that ensure guest comfort (e.g., seating) over aesthetics (e.g., centerpieces).'

How to Apply the Feynman Technique to Learning New Skills for Multiple Projects

When learning a skill for one project (e.g., React for development) while managing others, the Feynman Technique accelerates retention by forcing you to connect it to existing knowledge. Example:

Step 1: Explain the Skill Simply

Write: 'React is a tool to build user interfaces by combining small, reusable pieces (components).' Avoid terms like 'virtual DOM' or 'state management.'

Step 2: Identify Gaps

You realize you don’t know how to explain 'components' without referencing code. That’s your gap.

Step 3: Simplify with Analogies from Other Projects

Use a metaphor from your marketing project: 'React components are like email templates. Each template (component) has a specific job (e.g., header, footer), and you mix and match them to create a full email (interface).'

Step 4: Review and Organize

Rewrite your explanation with actionable steps for your development project: 'To build a dashboard in React, create a component for each section (e.g., charts, tables) and assemble them like Lego blocks.' Store this in your glossary and review it before coding sessions. For deeper steps, see Master New Skills Fast with the Feynman Technique for Rapid Learning.

Feynman Technique for Mental Blocks: How to Unstick Yourself

When overwhelmed by a project’s complexity, pause and ask: 'Which concept here don’t I fully understand?' Apply the Feynman Technique to that concept. Example:

• Block: You’re stuck on a financial report because you don’t understand profit margins.
• Step 1: Write: 'Profit margin is the percentage of revenue left after subtracting costs.'
• Step 2: Identify gaps: You don’t know how to calculate it. That’s your gap.
• Step 3: Simplify: 'It’s like your take-home pay after taxes. If you earn $100 and pay $30 in taxes, your profit margin is 70%.'
• Step 4: Review: Rewrite with an example: 'For a product that sells for $50 with $30 in costs, the profit margin is ($50 - $30) / $50 = 40%.'

How to Organize Feynman Explanations Across Projects Without Losing the Big Picture

Use a 'Feynman glossary' to store simplified concepts for each project. Structure it like this:

• Project Name (e.g., 'Email Campaign')
• Concept (e.g., 'A/B Testing')
• Simple Definition: 'Comparing two versions of an email to see which performs better.'
• Analogy: 'Like taste-testing two cookie recipes to pick the best one.'
• Connection to Other Projects: 'Similar to split-testing ads in the social media project.'
• Actionable Example: 'Test subject lines A and B for the next campaign.'

For a system to separate contexts without losing the big picture, see Bullet Journal for Multiple Jobs: Exact System to Separate Contexts Without Losing the Big Picture.

Common Mistakes and How to Avoid Them

• Mistake 1: Confusing simplification with dumbing down. The Feynman Technique isn’t about staying at the basics—it’s about understanding the essentials to go deeper. Example: Don’t explain machine learning as 'magic that predicts things.' Instead, write: 'It’s like teaching a child to recognize dogs by showing them lots of pictures until they learn to tell them apart.'
• Mistake 2: Using the same analogy for all projects. A metaphor that works for one project might confuse another. Example: Comparing algorithms to recipes works for beginners but not for a technical team. Create project-specific analogies.
• Mistake 3: Leaving concepts on paper. The Feynman Technique is useless if you don’t apply it. Example: After simplifying time management as *'deciding which tasks are like water (urgent) and which are like wine (important but not urgent),' label your tasks accordingly in your task app.
• Mistake 4: Treating projects as silos. The Feynman Technique shines when you find patterns across projects. Example: If your development project uses sprints and your marketing project uses feedback cycles, realize both are ways to iterate quickly and apply lessons from one to the other.

How to Integrate the Feynman Technique with Your Task Management System

The Feynman Technique helps you understand concepts, but you need a system to execute them. Here’s how to combine it with a task app like Foco:

• 1. Create a 'work' for each project in Foco (e.g., 'Marketing Campaign,' 'Development Sprint,' 'Family Event') and assign each a distinct color. Use the attached notes field for each task to store your Feynman explanations. Example: For the task 'Learn basic React commands,' add a note with your analogy: 'React is like Lego: each component snaps together to build something bigger.'
• 2. Use Foco’s voice capture to dictate Feynman explanations on the go. Example: While walking, record: 'A sprint in development is like a relay race: each team member runs their part and passes the baton (the code) to the next.' Foco will transcribe the audio and save it as a note in the task 'Plan sprint 3.'
• 3. Group tasks by concept in Foco’s 'List' view. Example: Filter tasks tagged with 'prioritization' to see all related tasks across projects, each with its Feynman explanation attached. For more on prioritizing critical tasks, see Critical Power List: How to Identify, Prioritize, and Execute Critical Tasks.
• 4. Use Foco’s 'Kanban' view to visualize how concepts progress across projects. Example: Create columns for 'To Learn,' 'Simplified,' and 'Applied' to track your Feynman Technique progress for each concept.

If you receive tasks from multiple tools (e.g., Notion, GitHub, Jira), Foco’s Plus plan can unify them into one place without migrating data. See How to Unify Tasks from Multiple Apps in One Place Without Migrating Data.

FAQ: Feynman Technique for Multiple Projects

FAQ

Can I use the Feynman Technique for non-technical projects, like event planning?

Yes. The technique works for any domain by forcing you to translate jargon into plain terms. Example: For event planning, simplify 'RSVP management' as 'keeping track of who’s coming, like a guest list for a party.'

How long does it take to see results with the Feynman Technique?

You’ll notice immediate clarity after the first 4-step cycle, but retention improves with repetition. Spend 10 minutes daily simplifying one concept from your projects. Example: After explaining prioritization for your marketing and development projects, you’ll recall the differences faster when deadlines overlap.

What if I can’t find an analogy that works for all my projects?

You don’t need a universal analogy—create project-specific ones. Example: For a database in development, use 'a spreadsheet with rules.' For a customer database in marketing, use 'a Rolodex with notes on each person.'

How do I store Feynman explanations so I don’t lose them?

Use a shared doc (e.g., Notion, Google Docs) or a task app with note-taking features (e.g., Foco). Structure each entry with: Concept | Simple Definition | Analogy | Connection to Other Projects | Actionable Example. Review the glossary weekly.

Can the Feynman Technique help with procrastination?

Yes, by breaking mental blocks. When you procrastinate, ask: 'Which concept in this task don’t I understand?' Apply the Feynman Technique to that concept. Example: If you’re avoiding a financial report because you don’t understand cash flow, simplify it: 'Cash flow is like your bank account balance over time: money in (salary) minus money out (bills).'