Video summary

Anatomy of a Problem | The Trial

Main summary

Key takeaways

Educational

Main Ideas / Concepts

  • Problem-solving requires a disciplined process, not just opinions or criticism.
  • You can’t solve a problem you can’t define.
  • A “problem” is relative to context—especially to:
    • your goals
    • the gap between current reality and desired outcomes
  • Correct problem definition depends on:
    • knowing the goal/purpose
    • identifying the obstacles that block the goal
    • verifying that the obstacle is real (evidence-based / “scientific thinking”)
  • Solutions must target causal factors, otherwise they won’t resolve the problem.
  • Problem identification must be done at the correct scale (e.g., national vs. campus). Narrow views can produce disconnected or misleading policies.
  • Popular premises/labels (e.g., “gender pay gap,” “patriarchy,” “neoliberalism”) are not enough by themselves—they must be tested against evidence and connected to goals.
  • When analyzing issues, avoid overthinking or jumping to conclusions; repeatedly ask “why” and check assumptions.

Methodology / Step-by-Step Problem-Solving Framework

A. Core Process for Solving Problems

  1. Understand the problem
    • Define what the problem is (not just that something “feels” wrong).
  2. Identify the right problem correctly
    • Pinpoint what exactly is the problem “here.”
  3. Read the consequence map/chain
    • Determine causal factors by verifying that A causes B (not just that A and B coexist).
    • Use a chain of consequences to connect causes to effects.
  4. Design the solution
    • Build an appropriate and effective solution aimed at the identified causes.
    • If the solution doesn’t match the real causes, the problem remains unsolved.

B. How to Define Whether Something Is a “Problem” (Goal–Gap Logic)

A situation becomes a problem when all of the following hold:

  • There is a defined goal/purpose (desired state).
  • There is a current reality / starting point.
  • There is an obstacle that hinders achieving the goal.

Therefore: “Is X a problem?” → “It depends”, because it depends on:

  • the goal
  • whose perspective/context it is
  • whether the obstacle truly blocks that goal

C. How to Validate That the Problem Is Real (Evidence-First)

Treat reality verification as scientific thinking / scientific method:

  • Collect evidence that the claimed obstacle exists.
  • Don’t assume—prove (or robustly test) that the obstacle/cause is present.

Example logic:

  • If a roof isn’t leaking, you can’t “solve” a non-existent leak problem.
  • If discrimination is alleged, you must show it’s not explained by other variables and that the difference is attributable to the claimed cause.

D. How to Avoid Incorrect Causal Attribution

  • Don’t stop at surface correlation (e.g., “women earn less → discrimination”).
  • Continue asking why until you can eliminate alternative explanations.
  • Watch for measurement problems and confounders such as:
    • job type
    • seniority
    • company differences
    • customer preferences
    • productivity
  • Recognize that “competence/merit” can be hard to define operationally and may itself require evidence.

Detailed Discussion Examples Used to Teach the Framework

  • Traffic/congestion as “a problem?”
    • The answer depends on context/goals: what inconveniences one group may not be a goal-blocking obstacle for another.
  • Government program funding mismatch (2026 plan needs 100, budget only 80)
    • Demonstrates problem = obstacle/gap between goal and reality.
    • Even if expectations differ, the key is the missing resources (a 20 gap) that prevents reaching the goal.
  • “Tax the rich”
    • Shows how unclear definitions create policy failures:
      • “Rich” may refer to wealth, not income
      • wealth taxation has different effects than income taxation
    • If policy definitions aren’t operationalized and system-designed, unintended consequences can occur (e.g., business closures, unemployment).
  • Scale problem (campus vs national)
    • Root causes may change when moving to national scale.
    • Campus issues can be symptoms rather than the nationwide system-level obstacle.
    • Policies can fail if built from too narrow a perspective.
  • Gender wage gap / gender wage discrimination debate
    • Emphasizes:
      • proving discrimination means showing differences are caused by gender, not other variables
      • “competence” isn’t self-evident—you need a defensible measurement
      • even controlled scenarios may hide variables (e.g., customer response, timing of sales effectiveness)
    • Educational point: labeling a phenomenon isn’t enough; you must test the cause.

Guidance for Student Presentations / Constructing “Problem” Analysis

When asked to present “problems in higher education,” do the following:

  • Define the purpose of higher education first
    • Choose a clear goal rather than many competing goals.
  • Choose which problem to focus on based on:
    • the goal
    • feasibility
  • Show the obstacle is real (use evidence).
  • Explain why solving that specific obstacle is the best priority.

Capital/Resources Composition (to Manage “Too Many Goals”)

  • A clear goal should be feasible given available resources (“capital”).
  • Capital is broadly interpreted as resources you can mobilize—not only personal money.
  • For large goals, you need team composition:
    • people bringing different types of capital (brains, network, money, connections)
  • Incorrect composition means goals can fail even if you have partial assets.

Practical “Don’t Overthink” Rule

Avoid overthinking every detail. Keep it simple:

  1. choose the goal
  2. identify obstacles
  3. verify obstacles exist
  4. select solutions targeted to those obstacles

Example framing: For cheating, ask why the rule system fails (e.g., if 90% cheat, the system design/implementation is likely undermining goal achievement).

Main Lessons / Takeaways

  • Goals come first; problem definition is goal-relative.
  • A problem is an obstacle blocking a goal, not just an unfairness feeling.
  • Causality must be tested (A truly causing B).
  • Reality and evidence must be validated before declaring an obstacle/problem.
  • Think at the right scale; otherwise solutions become disconnected.
  • Solutions must connect to the problem’s true causal structure.
  • Popular labels and assumptions should be tested, not accepted as facts.

Speakers / Sources Mentioned (from subtitles, as best as can be determined)

Primary Speaker / Host

  • Kania (also referred to by nicknames such as “Kania Cita”)

Other Recurring Participants / Questioners (students or speakers)

  • Jansen
  • FMI (name appears as “FMI from TB”)
  • Marlin / Merlin (University of Indonesia; also introduced as “Merlin”)
  • Wahyun Hidayat (Untirta History Education)
  • Marsya (Faculty of Law, Universitas Padjadjaran)
  • Dick Wyudi (Communication Science, Universitas Sumatera Utara)
  • Muhammad Hamid (State Islamic University Semarang / “Polisung State Islamic University Semarang” per subtitles)
  • Diki (Communication Science speaker; appears to be the same as Dick Wyudi in parts of the transcript)
  • Fahmi (mentioned during debate; appears to be another participant)
  • Wahy(ur) / Wahyu (participant giving a perspective on inequality/system)
  • Sor Hero / Ichirox Trewa
  • Eirox Trewa (name appears; likely same as Ichirox Trewa/Hero due to overlap)

Additional Sources / Entities Referenced (not listed as speakers)

  • Jerome, Richia (mentioned as comparison examples—people from Malaka)
  • Taylor Swift (example)
  • Jeff Bezos, Elon Musk, and “Taylor Swift” (examples for “tax the rich” and wealth/income)
  • KRL and an escalator example
  • Malaka scholarship / Malaka (context for participants and session)

Original video