A Practical Training Path

The easiest way to fail at rationality training is to treat it as inspiration rather than practice. Inspiration is pleasant. Practice is what changes judgment. This is deeply unfair, but reality has not asked for our approval.

This page turns the Basic Guide into routines. Use it for individual practice, team training, education, coaching, hiring, leadership development, or personal decision improvement.

Stage 1: Awareness

    • Learn the core vocabulary well enough to use it correctly.
    • Practice separating facts, interpretations, and conclusions.
    • Start noticing your strongest recurring biases.
    • Notice where you perform confidence instead of earning it.

Stage 2: Structured Practice

    • Keep a decision journal for 30 days.
    • For each important decision, write your prediction, confidence level, alternatives, and what would change your mind.
    • Review results weekly instead of waiting for memory to rewrite history like a tiny propaganda office.

Stage 3: Basic Stress Testing

    • Ask one thoughtful person to critique your reasoning.
    • Look for the strongest opposing evidence.
    • Rewrite an opposing argument in its strongest fair form.
    • Identify one bias that may be influencing your conclusion.

Stage 4: Action Integration

    • Turn the skills into routines for meetings, planning, budgeting, conflict resolution, media evaluation, and personal decisions.
    • Use checklists when the stakes are high and time is short.
    • Judge progress by improved outcomes, not by how sophisticated you sound.

 

 

The 30-Day Decision Journal

A decision journal is a simple written record of what you decided, why you decided it, how confident you were, what you expected, and what actually happened. It is one of the fastest ways to expose the gap between imagined judgment and real judgment.

Memory is not a clean archive. It is a creative assistant with loyalty issues. A journal makes it harder for memory to quietly upgrade your past reasoning after outcomes arrive.

 

Decision Journal Template

Journal field What to write
Date When the decision was made
Decision or belief What you are deciding or evaluating
Goal What outcome you want
Known facts What you directly know or can verify
Interpretations What you think the facts mean
Alternatives Other reasonable options or explanations
Prediction What you expect to happen
Confidence level Your confidence from 0 to 100 percent
What would change my mind? Evidence, feedback, results, or expert critique that would lower confidence
Outcome review date When you will check what happened

 

 

30-Day Practice Sequence

Week Practice focus Daily action Weekly review question
Week 1 Foundation skills Define terms, separate facts from stories, track confidence Where did I treat interpretation as fact?
Week 2 Logic Break apart one argument, identify premises and conclusion, check for false dilemmas Which argument looked stronger after inspection, and which looked weaker?
Week 3 Evidence and testing Write one testable hypothesis, prediction, and disconfirming condition What evidence did I avoid because it was inconvenient?
Week 4 Data, probability, causality, and bias Ask for base rates, check causality, identify one bias, review predictions What did I learn about my judgment pattern?

 

 

 

Weekly Review

Once a week, review your decision journal. Do not conduct a trial where your ego is the judge, prosecutor, defense attorney, and motivational speaker. Use simple questions:

    • What did I predict?
    • What actually happened?
    • Was my confidence too high, too low, or about right?
    • What did I miss?
    • What did I learn?
    • Which bias appeared most often?
    • Which question would have improved my decision?
    • What will I do differently next time?

 

 

Everyday Applications

Personal Decisions

Use the Basic Guide when choosing between options, evaluating a relationship pattern, deciding whether to spend money, planning health behavior, or deciding whether your first interpretation of an event deserves the royal throne.

    • Define the actual decision.
    • Separate what happened from what you think it means.
    • Name the uncertainty.
    • Write what would change your mind.
    • Choose one action that tests your current view.

Work Problems

Use the Basic Guide when a team is arguing, a process is failing, a report seems too confident, or a meeting has begun circling the drain with professional vocabulary.

    • State the conclusion being proposed.
    • List the premises.
    • Ask what data supports the claim.
    • Ask what comparison or baseline is missing.
    • Screen for false dilemmas and hidden assumptions.

Media and Public Claims

Use the Basic Guide when evaluating headlines, statistics, public claims, expert commentary, social media posts, and persuasive narratives.

    • Identify the claim.
    • Check the evidence.
    • Ask whether the sample is representative.
    • Look for base rates.
    • Separate correlation from causation.
    • Ask what the opposing evidence says.

 

 

Simple Hiring and Screening Checklist

This checklist can be used for hiring, promotion, team development, teaching, coaching, or role fit. Do not use it as a robot judge. Use it as a structured way to notice how a person thinks.

 

Skill Screening question
Clarity Can the person define key terms and explain reasoning clearly?
Evidence sense Can they separate observation from interpretation?
Logic Can they identify weak arguments, hidden assumptions, and false dilemmas?
Scientific reasoning Can they form a testable hypothesis and name evidence that would disconfirm it?
Data literacy Can they ask where data came from, what is missing, and whether definitions changed?
Probability sense Can they talk about uncertainty honestly without collapsing into vagueness?
Bias awareness Can they name the bias most likely to affect their judgment?
Updating Can they describe a time they changed their mind for good reasons?
Action quality Do they connect thinking to better decisions and outcomes?

Simple Interview Prompts

    • “Tell me about a time you changed your mind after seeing new evidence.”
    • “Describe a decision that went badly. What did you miss?”
    • “Take a current problem and walk me through your hypothesis, evidence, uncertainties, and alternatives.”
    • “What would you need to see to conclude that your current approach is not working?”
    • “How do you tell the difference between a correlation and a likely cause?”

 

Tiny Systems-Thinking Preview

In the earlier version of this rationality sequence, systems thinking appeared sooner. In this reorganized version, full systems thinking moves to the Intermediate Guide because beginners need to land the plane before being handed air-traffic-control software.

For now, keep only this preview: some problems cannot be solved by looking at one cause alone. They involve interacting parts, incentives, feedback, delays, habits, roles, rules, and unintended consequences. When your Basic Guide methods keep revealing repeated patterns, moving causes, and delayed effects, that is a signal to continue to the Intermediate Guide.

Basic version: Ask, “What else is interacting with this problem?” That is enough for now. No giant systems map required. Civilization may continue, somehow.

 

Final Basic Guide Practice

    1. Return to the real problem you chose on Page 1.
    2. Define the decision or belief at stake.
    3. Write the argument for your current view in premises and conclusion.
    4. Write the strongest fair opposing view.
    5. Write one testable hypothesis and one prediction.
    6. List base rates or background information that matters.
    7. Identify one causal trap and one bias that may affect you.
    8. Write one small next action and one review date.

 

AI Support Prompts for This Page

    • “Create a 30-day decision journal template for this recurring decision type: [decision type]. Include prediction, confidence, alternatives, and review fields.”
    • “Review this decision journal entry and identify what I missed, what evidence was weak, and what I should track next time: [entry].”
    • “Ask me weekly review questions based on these decisions and predictions: [paste entries].”
    • “Create a simple hiring interview prompt set to evaluate basic rational thinking skills for this role: [role].”
    • “Based on this problem, tell me whether basic rationality tools are enough or whether I may need intermediate tools such as systems thinking or structured analysis: [problem].”

 

Frequently Asked Questions

How long does it take to learn this?

You can understand the basics quickly. Building the habits takes longer. This is more like physical training than collecting quotes.

Do I have to journal every decision?

No. Journal meaningful decisions, repeated decisions, high-stakes choices, and decisions where your confidence may be misleading.

What if I hate writing things down?

Use short entries. A five-line journal beats a majestic unwritten system living only in your imagination.

Can these tools be misused?

Yes. Clever people can use logic, data, and rationality language to manipulate, dominate, or confuse others. The moral test matters: are these skills helping you get closer to truth and produce better outcomes, or just helping you win status games?

 

Basic Glossary

    • Abduction: Reasoning to the best current explanation while staying open to revision.
    • Anecdote: A single story or example. Useful, but weak evidence on its own.
    • Assumption: Something taken for granted without full proof.
    • Base rate: The background frequency of an event or condition.
    • Bias: A predictable pattern of judgment error.
    • Calibration: How well confidence matches actual accuracy over time.
    • Causation: A relationship in which one thing helps produce another.
    • Claim: A statement that can be examined, supported, challenged, or tested.
    • Conclusion: The main point an argument tries to establish.
    • Control group: A comparison group that does not receive the tested condition.
    • Correlation: A pattern in which two things vary together.
    • Counterexample: A case that shows a general claim is false or too broad.
    • Data: Recorded observations or measurements.
    • Deduction: Reasoning from general premises to a conclusion that must follow if the premises are true.
    • Evidence: Information that supports or weakens a claim.
    • Expected value: A way of estimating average likely value when chance is involved.
    • Experiment: A structured test designed to see what happens under defined conditions.
    • False dilemma: A mistaken framing that presents only two options when more exist.
    • Falsification: Trying to show that a claim is wrong through evidence or tests that could defeat it.
    • Hypothesis: A proposed explanation that can be tested.
    • Induction: Reasoning from observations toward a broader probable conclusion.
    • Logic: The study of valid reasoning and argument structure.
    • Measurement: A way of turning reality into something countable or comparable.
    • Mechanism: The process that connects a cause to an effect.
    • Observation: What is directly seen, recorded, or measured.
    • Peer review: Evaluation by qualified people who inspect reasoning, method, or evidence.
    • Premise: A supporting statement in an argument.
    • Probability: A judgment about how likely something is.
    • Rationality: The disciplined effort to align beliefs with reality and actions with goals.
    • Replication: Repeating a test to see whether the result holds up.
    • Scope condition: The condition under which a claim applies or stops applying.
    • Updating: Changing your belief or confidence when evidence changes.

 

Selected References and Source Links

 

 

What's Next

By this point, you have moved from learning rational thinking tools to actually practicing them. That is the real shift. A decision journal, prediction tracking, weekly review, and “what did I miss?” questions turn clear thinking into a repeatable habit instead of another noble idea quietly gathering dust in the attic of good intentions. Page 5 helps you become more accurate over time by comparing what you expected with what actually happened, which is rude of reality, but extremely useful.

But some problems are too tangled for basic methods alone. Some situations involve many moving parts, feedback loops, delays, hidden incentives, shifting contexts, conflicting values, emotional entanglement, and consequences that show up later, wearing a fake mustache. That is where Page 6 comes in. It helps you recognize when a problem has outgrown basic clear thinking and needs the next level: systems thinking, structured analysis, deeper self-awareness, and more careful handling of complexity.

The point is not to abandon the Basic Manual. These tools remain the essential foundation. Page 6 simply shows you when the foundation needs additional floors, support beams, and maybe a structural engineer who has slept recently. It prepares you to see the difference between simple problems you can solve with basic logic and evidence, complicated problems that need organized analysis, and complex problems that require systems thinking and adaptive learning. Keep going, because this bridge will help you know when to use basic methods confidently and when to step into the Intermediate Guide before reality starts throwing furniture.

Next: Continue to Page 6: Bridge to Intermediate, When Basic Methods Are Not Enough.

 

 


Copyright Notice

Except where otherwise noted, original content on this page and every page on the Universe Institute website is licensed under Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International. Logos, trademarks, and third-party materials are excluded. For the specific terms and exceptions of this Creative Commons license, see Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International.

Published works, white papers, and source materials belonging to other individuals or organizations are covered by their own individual copyrights and terms.

This document was produced through a collaboration of the Universe Institute and Job One For Humanity. Lawrence Wollersheim was the lead DMAP analyst on this project.