Video summary

Why you should be using systems thinking to solve problems

Main summary

Key takeaways

Educational

Main ideas and lessons

Why systems thinking

  • Systems thinking helps you see connections, handle ambiguity, and recognize that others may see only problems while you see patterns and relationships.
  • It improves your thinking so you ask better questions and become less manipulable.
  • It builds critical thinking alongside systems thinking, rather than focusing only on memorization or rigid “pattern matching.”

Purpose of the talk (objectives)

  • Introduce systems thinking and critical thinking.
  • Explain how to do it (not just definitions).
  • Provide tools you can use immediately.
  • Use examples to examine problems from multiple system-related angles.

What a “system” is

  • A system is a set of objects with relationships between them.
  • Thinking systemically means treating a situation as composed of interacting parts within boundaries.

Questions that guide understanding

  • The talk emphasizes the Kipling questions: who, what, where, when, why, how (attributed to Rudyard Kipling’s Just So stories).
  • This supports understanding by turning vague problem statements into structured inquiry.
  • Also referenced: “five whys” as a way to get at root cause.

Definition of “problem” (important distinction)

The word “problem” is used sloppily; it can mean multiple things. The talk distinguishes:

  • Problem as uncertainty/question: “a matter of doubt”
  • Problem as a proposed question for discussion/solution
  • Problem as an undesirable situation: the outcome you don’t want
  • Problem as the cause: what produces the undesirable situation
  • Problem as the task: “what we need to do about it”

Problem-solving as an iterative process

  • Treat solutions as something you test. If the undesired situation persists, you iterate.
  • The core cycle:
    1. Start with an undesirable situation
    2. Define the problem space / understand what’s going on
    3. Conceive solution options
    4. Choose ideal solution criteria (constraints/requirements)
    5. Trade off among options
    6. Select and implement the preferred option
    7. Verify whether the undesirable situation is resolved
    8. If not resolved, go back and iterate

Systems-thinking approach to solutions

  • In non-systems thinking, answers are often treated as either/or (e.g., “yes/no”).
  • In systems thinking, solutions form a continuum:
    • Unacceptable
    • Acceptable
    • Optimal
  • Confidence/ignorance are also treated as valid:
    • “Don’t know,” “depends,” or probability-based answers are acceptable outcomes when information is insufficient.

“System thinking and beyond” (perspectives)

  • The talk uses blind-men/elephant and Sherlock-style metaphors:
    • You can’t see everything from one position.
    • You must shift perspectives and combine views.
  • Multiple perspectives are presented as a structured way to analyze issues:
    • External / systems-thinking perspectives: big picture, context, assumptions, “black box” view of what the system does and how it interacts
    • Internal / analysis perspectives:
      • Functional: what the system does
      • Structural: how it is organized
    • Progressive perspectives: generic comparisons and alternatives to find out-of-the-box solutions; plus temporal/history-style views
    • Quantitative and scientific perspectives: numbers/data and forming a hypothesis-like scientific output

Out-of-the-box solutions

  • Out-of-the-box ideas usually come from switching to the right perspective box—especially generic/progressive ways of comparing similar systems in different contexts.

Active brainstorming and avoiding argument confusion

  • Active brainstorming is framed as asking questions, not just answering.
  • In group work, you can:
    • Write questions and answers separately from your perspective matrix
    • Later categorize answers rather than debating placement immediately

Methodology and instruction-style content

A) Systems thinking questions (Kipling questions)

  • Use who / what / where / when / why / how to structure understanding of a situation.
  • Apply them systemically and systematically to clarify:
    • the nature of the system,
    • root causes of undesirable outcomes,
    • and how potential solutions might work.

B) Correct “problem” framing

When someone says “that’s a problem,” translate it into clearer components:

  • Identify the undesirable situation (what outcome is unwanted).
  • Identify the cause (what produces the undesirable situation).
  • Identify the problem/task (what needs to be done to address the undesirable situation).
  • Avoid circular or sloppy phrasing like “the problem is to figure out the problem.”

C) The problem-solving process (decision-making cycle)

  • Input: an undesirable situation
  • Steps:
    1. Define the problem space / understand what’s happening
    2. Conceive solution options
    3. Identify solution criteria (constraints such as affordability, time, feasibility)
    4. Trade off options based on the criteria
    5. Select a preferred option
    6. Formulate strategies and plans for implementation
    7. Implement
    8. Verify the outcome
    9. If not resolved, iterate back to earlier steps (possibly reconsider solution space)

D) Systems-thinking “response continuum” for decisions

For decision-making, consider more than yes/no:

  • “Yes,” “No,” “It depends,” and “I don’t know” are legitimate states.
  • If “depends”: collect more information to reduce uncertainty.
  • If “don’t know”: either obtain more information or treat uncertainty as part of the decision.

E) Perspective-based analysis template (matrix approach)

  • Use a matrix combining:
    • perspectives (big picture/external, internal functional/structural, progressive, quantitative/scientific),
    • with Kipling questions.
  • For each perspective, ask relevant questions such as:
    • Who is involved?
    • What are they doing?
    • Where/when does it occur?
    • Why are they doing it (assumptions/motives)?
    • How does the system operate or interact?
    • What happens under alternative conditions?
  • Write down questions and partial answers; don’t force everything into one matrix cell.
  • Use the output to gain understanding; later, fill reasoning into separate tools/boards/charts.

F) Critical thinking: template for argument analysis (Peg / “holistic thinking” tool mention)

  • The talk distinguishes:
    • disputes (where you refute an opponent),
    • arguments (where you support a position).
  • To evaluate an argument, identify:
    • Point/Claim (what is being claimed?)
    • Opinion/Conclusion
    • Reasons
    • Evidence
    • Unstated premises
    • Connections between reasons and conclusions
  • Check whether the reasoning is:
    • Valid
    • True
    • Acceptable
    • Relevant
    • Sufficient
  • Improve arguments by:
    • adding missing reasons/evidence,
    • removing loaded language,
    • and anticipating objections.
  • If refuting:
    • look for counterexamples and counter-evidence,
    • and either refute, modify, or suspend judgment pending more information.

Examples used to illustrate concepts

  • Mask-wearing decision (COVID-19 shopping)
    • Demonstrates using yes/no vs uncertainty and criteria-based decisions.
  • “Problem with my watch”
    • Demonstrates distinguishing undesirable outcome, cause (dead battery), and follow-up task (replace battery), including alternative outcomes (self vs shop).
  • Kiosk queues at a university
    • Shows how an out-of-the-box solution came from an analogous system (traffic “yellow boxes” to prevent congestion).
  • Camera analysis
    • Demonstrates how different perspectives apply differently:
      • big picture (use cases),
      • operation (capturing/storage/retrieval),
      • structure (lens/charger/body),
      • generic/continuum (types of capture methods),
      • temporal evolution (media over time),
      • quantitative (resolution/pixels),
      • scientific/hypothesis depending on the issue.
  • Car and house examples
    • Used to reinforce perspective-specific relevance.

Takeaways (explicit summary list from the speaker)

  • Acceptable solutions matter (not only correct/optimal ones).
  • Decision states can include:
    • “don’t care,” “don’t know,” and “it depends.”
  • Use holistic thinking via:
    • perspectives,
    • Kipling questions,
    • active brainstorming,
    • a template for critical analysis of arguments.
  • Use STL / STALL-style pause:
    • Stay calm, Think, Ask questions, Listen
    • Emphasis that listening yields more information than talking.

Speakers / sources featured

  • Joe Casser — main speaker; presenter of the talk
  • Rabbi Moshe Heim Lozado — source of the quoted idea about competitive advantage from understanding how things are systematically categorized/related
  • Rudyard Kipling — credited with introducing the “Kipling questions” framework in Just So / “the elephant’s child” references
  • Barry Richmond — referenced as foundational work influencing systems thinking teaching approach
  • Miller’s Rule — referenced: “number nine is limited” as a cognitive constraint
  • Schrödinger — referenced via Schrodinger’s cat paradox to discuss decision uncertainty
  • Dez McHale — referenced via a book thank god i’m an atheist for examples of logic/rhetoric/humor ambiguity
  • Peg (peg.title) — referenced as the author/creator of the critical analysis argument template tool name: “from peg title”
  • Dogpile.com — meta search engine mentioned as a source for checking information
  • Amazon.com — mentions “look inside” feature and book access
  • University libraries / library research — referenced as a practice for discovery and cross-checking
  • CRC Press — mentioned indirectly via a discount coupon for ordering the book

Original video