12 Favorite Problems Workshop

Guide the user through identifying, refining, and using their 12 Favorite Problems -- the open-ended questions that serve as a personal capture filter for their Second Brain.

Inspired by Richard Feynman, who kept a dozen important problems constantly in mind. Whenever he encountered a new technique or insight, he tested it against all twelve.

Why This Matters

Most Second Brain failures stem from one of two problems:

• Over-capturing: Saving everything, using nothing (no filter)
• Under-capturing: Not saving enough because nothing feels "worth it"

The 12 Favorite Problems solve both: they provide a personal relevance filter that ensures captures are meaningful without requiring judgment on each individual item.

The Workshop — Creating the List

Step 1: Brain Dump (5 minutes)

Prompt the user:

"Write down every question, curiosity, challenge, or aspiration you can think of. Don't filter -- aim for 20-30 raw questions across all areas of your life: - Career and professional growth - Health and well-being - Relationships and community - Creative projects and hobbies - Financial goals - Learning and personal development - Contribution and impact

>

Start with whatever comes to mind. I'll help you refine them."

Wait for the user's list before proceeding. If they produce fewer than 15 items, prompt with category-specific starters:

"What about [under-represented category]? Is there a question or challenge there that's been on your mind?"

Step 2: Refine Into Open-Ended Questions (5 minutes)

Help the user rewrite each item as a genuine question:

Transformation rules:

• Start with "How can I...?" or "What...?" or "How might I...?"
• Must be open-ended (no yes/no answers)
• Must be broad enough to last months or years
• Must be specific enough to recognize a relevant answer

Before/After examples:

Work through the user's list item by item, suggesting refinements but respecting their wording preferences.

Step 3: Select the 12 (5 minutes)

From the refined list, help the user select 12 using these criteria:

1. Energy test: Would you be excited to stumble across an answer?
2. Longevity test: Will this still matter in 6 months?
3. Diversity test: Do the 12 span different life areas? (Not all work, not all personal)
4. Recognition test: Could you spot a relevant answer if you encountered one randomly?

Present the selected 12 in a numbered list. Ask:

"Read through these. Do they feel like YOUR questions? If any feel forced or borrowed, swap them for something more personal."

Step 4: Test the Filter

Validate the list works as a capture filter:

"Think of the last 3 things you saved, bookmarked, or found interesting. Does each one relate to at least one of your 12 problems?"

• If yes: the filter matches actual behavior. The list is calibrated.
• If no: either captures are unfocused OR the problems don't reflect real interests.

Adjust accordingly.

Step 5: Save the List

Save the 12 Favorite Problems as a persistent reference:

# My 12 Favorite Problems
**Created:** [date]
**Last reviewed:** [date]

1. [Problem 1]
2. [Problem 2]
...
12. [Problem 12]

## Capture Rule
When encountering new information, test it against these problems.
If it provides an answer, a new angle, or a spark for ANY of them — capture it.

Where to save:

• In the user's PARA system: Areas/Personal Development/ or pinned at the top level
• If using Obsidian: as a pinned note
• If using Notion: as a favorited page
• The key: it must be instantly accessible during capture moments

Using the List — Ongoing Integration

During Capture

When the user encounters new information:

"Does this relate to any of your 12 problems? If yes, capture it and tag it with the problem number. If not, ask: is it inspiring, useful, personal, or surprising? (The 4 capture criteria.) If neither, skip it."

During Weekly Reviews

Reference the 12 problems during weekly reviews:

"Looking at what you captured this week — which of your 12 problems got the most attention? Which got none? Are the neglected ones still important, or have your priorities shifted?"

This turns the weekly review from a maintenance chore into a strategic check-in.

During Monthly Reviews

Review and update the list:

• Replace problems that no longer resonate (2-3 changes per quarter is normal)
• Add new problems that have emerged from recent projects or life changes
• Check if any problems have been answered -- celebrate and replace them

During Project Kickoffs

When starting a new project, cross-reference:

"Which of your 12 Favorite Problems does this project address? This helps you stay motivated and recognize relevant captures as they appear."

Maintenance Schedule

Key Principles

• These are YOUR problems. Resist impressive-sounding questions borrowed from

thought leaders. The best 12 problems are deeply personal.

• Open-ended, not goal-shaped. "How can I become a better communicator?" works.

"Give a TED talk" doesn't -- that's a project, not a problem.

• Broad enough to last, specific enough to filter. "How can I be happy?" is too

broad. "How can I design my mornings to start each day with energy?" is focused.

• It's normal for them to change. A list from 6 months ago should look different.

Life evolves; so do your questions.

Reference Files

For the complete 12 Favorite Problems methodology and capture criteria:

• `../para-organize/references/code_framework.md` -- Full workshop steps, capture criteria, and AI-enhanced capture workflows