Skip to content

Latest commit

 

History

History
41 lines (23 loc) · 1.2 KB

File metadata and controls

41 lines (23 loc) · 1.2 KB

Name: Matthew McGilvery

Date: June 18, 2026 Topic: Problem Diagnosis Module

Problem Diagnosis

The Problem module helps users define friction before trying to solve it.

In Life Systems, a problem is not treated as a vague feeling, complaint, or inconvenience. It is defined as a structured relationship between four variables:

Problem = f(Trigger, Context, Conflict, Impact)

If one or more variables are missing, the issue may still matter, but it is not ready for full resolution yet.

The Four Variables

1. Trigger

The catalyst that starts the friction.

2. Context

The baseline environment, rules, constraints, and current conditions.

3. Conflict

The point where opposing forces collide.

4. Impact

The cost of doing nothing.

Purpose

This module helps users avoid solving the wrong problem. By defining the issue clearly, the user can move into complexity mapping, decision analysis, execution, and audit with a more accurate starting point.

Files

  • problem_framework.md: Full explanation of the problem equation.
  • internal_problem.md: Application of the model when the user is part of the bottleneck.
  • problem_framework.py: Optional Python reference model.