Problems

What is the most valuable problem you should focus your attention on right now? How do you know?

A problem is the gap between where you are and where you want to be. The size of the gap is the size of the opportunity. But most effort gets wasted on symptoms pretending to be causes, urgent things that don't matter, and problems framed by others for their benefit.

Our purpose is to solve problems. The higher skill is choosing problems worth solving. A good problem moves the system from pain toward potential. A bad problem burns attention on preventable rework, avoidable issues, or friction that should not exist if the work was done correctly.

Good Problems

A good problem is a Reality-backed gap with a clear cost, a defined future state, and a smallest action that produces feedback. It is pain with a path to learning.

A bad problem is a poor focus for attention. It may be real pain, but the framing is wrong: a symptom treated as a cause, inherited urgency, an incentive trap, or rework created by missing standards, skipped checks, unclear ownership, or weak handoffs.

Use five tests:

• Reality: good problems have evidence; bad problems run on assumption, vibe, or loud complaint.
• Dream: good problems serve purpose and meaning; bad problems only quiet noise.
• Action: good problems have a small test; bad problems expand before the gap is clear.
• Feedback: good problems improve the next question; bad problems end at activity.
• System: good problems remove a cause; bad problems rework a symptom.

A problem without a Reality reading is only a claim. A solution without feedback is only activity.

Rework Test

Ask this before committing attention:

Would this problem disappear if the work had been done correctly?

If yes, the visible issue is evidence of a system failure. Solve the standard, check, ownership, or handoff that created the rework. Do not only patch the incident.

Problem Ledger

Well-defined good problems are worth gold. They are not disposable notes. They are strategic assets.

A problem database turns friction into memory. Each record should preserve the Reality gap, root cause, classification, value proposition, priority, energetic weight, prediction, status, and resolution. The point is not administration. The point is compounding judgment: the next person or agent should see which problems were real, which were solved, which were not worth fixing, and which revealed better questions.

Bad problems still belong in the ledger when they teach the system. Mark them as rework, misframing, duplicate, or wont-fix. That prevents the same attention leak from returning under a new name.

The Inner Loop

Problems don't exist in isolation. They sit inside a cycle that converts friction into progress:

QUESTION → PROBLEM → DECISION → ACTION → FEEDBACK
    ↑                                        |
    └────────────────────────────────────────┘

Step	What Happens	Where It Lives
Question	Curiosity finds friction	An insightful question is timeless and priceless
Problem	Friction gets named and measured	A problem well-stated is half solved
Decision	Options weighed, commitment made	Process over outcomes
Action	Smallest move that tests the thesis	Protocols encode what works
Feedback	Outcomes compared to expectations	Performance closes the loop

The quality of the question determines which problems you see. The clarity of the problem statement determines whether it gets solved. The discipline of the decision determines whether the solution compounds.

The Inner-Inner Loop

The full FLOW loop moves intention into evolution:

INTENTIONS => CAPTURE IDEAS -> PRIORITIZE -> COMMIT-ACTION -> MEASURE OUTCOME -> QUESTION-LEARN => EVOLVE

Questions, problems, and decisions run inside every station. They are the inner-inner loop:

QUESTION -> PROBLEM -> DECISION -> ACTION -> FEEDBACK

Each pass asks:

• Capture Ideas: what signal is real? Decide what deserves to enter the system.
• Prioritize: which gap matters most? Decide what problem gets attention.
• Commit-Action: what bet will test the bridge? Decide what action receives commitment.
• Measure Outcome: what changed in Reality? Decide whether the action closed the gap.
• Question-Learn: what did feedback reveal? Decide what better question evolves the loop.

The loop connects three layers:

• Reality is perception and perspective: what is actually happening, what evidence proves it, and what cost is visible.
• Dream is purpose and meaning: why this gap is worth closing, and what better future it points toward.
• Action is commitment and attention: the chosen move that tests whether the bridge is real.

Good problems make each station sharper. Bad problems break the loop because feedback does not compound.

Dig Deeper

• AI Problems — alignment, attention, and automation risk
• Business Problems — value creation, incentives, and execution gaps
• Financialization — extraction replacing production
• Governance Problems — coordination failure at scale
• Science Problems — discovery systems under broken incentives
• Societal Problems — platforms shaping attention and flourishing

The Metacrisis

Technology that empowers can also destroy. We shape our tools, then our tools shape us. Five forces converging:

Force	What's Breaking	Domain
Tech risk	AI, biotech, cyber weapons getting cheaper and more powerful	AI
Extraction	Capital extracts instead of funding production	Financialization
Coordination failure	Everyone optimising locally, losing globally	Governance
Broken incentives	Publish or perish, ship or die, engage or starve	Science, Business
Platform failure	Systems that extract attention rather than support flourishing	Society

Systems Failure

Dreams pull engineering along. Engineering pushes expansion of dreams. When they decouple, systems break.

Imbalance	What Happens	Example
Too much dream	Can't execute, endless promises	Web3 vaporware, never ships
Too much engineering	Efficient at wrong things	Optimising extraction, not value
No anchor	Drifting, no shared purpose	Institutions losing legitimacy

Coordination requires agreement on facts. When facts become contested, coordination becomes impossible. Truth is the meta-layer — when it fails, everything built on it fails.

Context

• Questions — The capability that converts problems into progress
• Problem Solving — Protocol for stating problems clearly
• Decisions — Turn solutions into commitments
• Flow State — Where problem-solving becomes play
• Control System — Engineering what mantras try to do
• Pattern Recognition — See the pain others miss
• Listening — Hear what someone needs, not what they say
• Empathy — Understand the suffering before naming the problem

Questions

Which problem-identification method — user interviews, friction mapping, or market gap analysis — produces the most actionable signal for a venture at the zero-to-one stage?

• At what problem severity level does a solution become a must-have rather than a nice-to-have — and how do you verify you've crossed that threshold?
• How does the Tight Five framing (problems as the entry point to purpose) change which problems you choose to work on versus traditional market sizing?
• Which problem category — coordination, trust, or information asymmetry — is most consistently underestimated by technology founders?
• Which problems in your ledger are worth gold because they are well-defined, Reality-backed, and reusable?