Problems
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, on urgent things that do not matter, on problems framed by others for their benefit.
Our purpose is to solve problems. The higher skill is choosing problems worth solving. This hub holds two halves of that skill: knowing which problems matter, and knowing how to solve them once chosen.
Problems owns the good/bad judgment. It asks whether the gap is real, virtuous, costly, avoidable, and worth naming. A good problem increases agency when solved. A bad problem burns attention, rewards theatre, or traps you inside someone else's frame.
Problem solving is the bridge between good questions and good decisions. Questions reveal the real gap. The problem statement makes the gap solvable. Decisions commit the next move and create proof.
Decision Ladder
Use the ladder in order:
| Layer | Owns | Question |
|---|---|---|
| Problems | Good vs bad | Is this the right gap to solve? |
| Potential | Risk vs reward | What could this become, and what could it cost? |
| Priorities | When and why | Should this win scarce attention now? |
| Plans | How and who | What bridge gets built, and which agents of change carry it? |
Do not plan before the problem is clean. A plan for a bad problem only makes the wrong work faster.
Choose the Problem
Where the valuable problems live — across AI, business, crypto, economics, governance, science, and society.
- Problem Domains — the catalog of high-leverage problems worth your attention
Solve the Problem
Once chosen, move from fuzzy pain to a clear, solvable statement.
| Step | Question | Output |
|---|---|---|
| Classify | What type of problem is this? | Simple, complicated, complex, chaotic, or NP-hard |
| Define | What is the real gap? | Root cause, not symptom |
| Align | Do we agree it is the problem? | Shared frame and incentives |
| State | Can anyone act on it? | One clear problem statement |
| Value | Is it worth solving now? | Ranked bet with upside and proof |
Use the five priorities as a quick diagnostic:
- Why does this problem matter?
- What truths define it?
- What do we control right now?
- What do we see that others miss?
- How will we know progress is real?
Scout Pass
Before solving, scout the gap. The point is not to collect every problem. The point is to find the few gaps where focused attention can create disproportionate progress.
| Move | Question | Output |
|---|---|---|
| Scan | What signal says value is trapped here? | Evidence of pain or pull |
| Categorize | What kind of problem or obstacle is this? | Simple, complicated, complex, chaotic, or NP-hard |
| Clarify | What is the root gap, not just the symptom? | One problem statement |
| Prioritize | What upside makes this worth attention now? | Ranked bet |
| Commit | What decision tests the next move fastest? | Action with feedback date |
Problems have potential upside. Opportunities have obstacles. The same protocol handles both: name the gap, classify it honestly, decide whether it deserves attention, then learn from the result.
Classification
What type of problem are you solving? See Systems Thinking for frameworks.
| Type | Description | Approach |
|---|---|---|
| Simple | Cause and effect are well-defined | Use best practice |
| Complicated | Domain expertise is required | Analyze with experts |
| Complex | No obvious pattern exists | Experiment to prove what works |
| Chaotic | Cause and effect are unclear | Probe for black swan exposure |
| NP-Hard | Efficient solution is not guaranteed | Verify candidate solutions fast |
Constraints
Before solving, follow the stream to the extremes to make a map of reality.
- What are the actual constraints, not the assumed constraints?
- What is the root cause, not the symptom?
- Who benefits from the current state?
Consensus Gap
"I see a problem" must become "we agree on the problem."
This is where coordination dies.
| Failure | Sound |
|---|---|
| Different perception | "That is not a problem for me" |
| Different priorities | "This other thing is more urgent" |
| Different definitions | "When you say X, I hear Y" |
| Different incentives | "Solving this helps you, not me" |
To build consensus: share raw data, find root causes together, commit only when aligned.
Problem Statement
A problem well stated is half solved. Follow the streams to get a true map of reality.
- What needs to be solved?
- Where is the problem observed?
- Who is impacted?
- When does it occur?
- Why does it prevent progress?
- How is it observed?
- How often does it happen?
- What does it cost in money, time, quality, energy, trust, or attention?
- Why is it urgent now?
The goal is not prose. The goal is a statement clear enough that someone can start solving the right thing immediately.
Problem Valuation
Problems are raw material. Good questions are the catalyst that converts them into opportunities. Good decisions turn the chosen opportunity into action.
- Progress: What would progress look like?
- Performance: How can we quantify progress?
- Perspective: Who needs this? Who understands it?
- Platform: What infrastructure and know-how are required?
- Product: How can the solution sell itself?
Can you sell that the reward is worth the effort?
1. What annoyed you? (trigger)
↓
2. What was the actual problem? (root cause)
↓
3. How should it work? (vision)
↓
4. What would success look like? (artifacts)
↓
5. Will you bet on fixing it? (appetite)
Example
A great problem statement quantifies the gap:
Weak: "Our onboarding is confusing."
Strong: "40% of new users abandon signup before completing step 3, costing ~$12K/month in lost conversions. Users who complete onboarding have 8x higher 30-day retention."
| Question | Answer |
|---|---|
| What | 40% abandonment at step 3 |
| Where | Email verification step |
| Who | New users |
| How much | $12K/month, 8x retention difference |
| Why it matters | Revenue impact and retention signal |
The gap is clear: 40% abandonment needs to become 15%. The bet is obvious.
Why This Matters
The hardest problem is identifying which problem to focus on. Get that wrong and every downstream decision compounds the error. Get it right and the work almost solves itself.
The test is simple: if solving the problem would not create more agency, clearer choice, or better value flow, it is not a Dreamineering problem yet.
Context
- Questioning System — ask better questions so the real problem becomes visible
- Decision Making — choose the next move once the problem is clear
- Problem Domains — choose high-leverage problem spaces
- Systems Thinking — reason about complex problems and feedback loops
- Flow State — where problem solving becomes play
Questions
What is the most important problem you are not working on, and what is the cost of that choice?
- Which current problem is a symptom of a better question you have not asked?
- What decision would test your problem statement fastest?
- Who must agree this is the problem before solving it creates real value?