I’m trying to create a few pages about things, that are more like notes in
different stages of completion.
Theory of Constraints
Goal Trees are at the start of what you want to
achieve.
Current Reality Trees help you find the
current problems with your system.
Solving Conflicts is at the base of solving your
problems. Finding conflicts in your system is one of your main priorities.
Thinking Clearly shows the four obstacles
that keep you from seeing and solving your problems.
The list
A nice way to use the goal tree is to use a color scheme to show which goals are already fulfilled and which are not. A schema that can be used is red, orange, green.
color when Red The condition is not fulfilled Orange The condition is partially fulfilled Green The condition is completely and satisfactorily fulfilled The nice thing about the tree and the color scheme is that when you have colored the leaf nodes, you can then combine the colors upwards.
A Goal Tree consists of nodes and arrows. The nodes are your goals, critical success factors and necessary conditions. The arrows are the logical connections. These arrows connect goals with the sub goals.
An arrow can be read as “In order to have X, we must have Y”. In a small diagram, this looks like: X ← Y.
You start with the Goal. The Critical Success Factors are necessary to reach your goal.
To improve a Goal tree, you need to examine the items in the tree. Using a technique similar to five why’s you can improve the goal tree.
Ask the question: why do you need it?
Example: garden shed Let’s look at the goal of “Garden shed”. Why do I need a garden shed? Because I need to store my garden tools. Why do I need to store my tools? I want to have a clean garden.
In Jira, an issue is a task and a note at the same time. The issue is a place to focus the information to the point where you can complete some piece of work.
These are four obstacles to clear thinking.
Reality is complex Reality is complex and you need complex solutions to solve problems.
Eli Goldratt defined the Principle of Inherit Simplicity. This means that reality is inheritly simple. Because of this simplicity, conflicts can be resolved using the following steps.
Clarify the conflict Surface the assumptions Challenge the wrong assumptions There is a relation with shadow work. In shadow work you should also keep conflicts in your mind and try to merge them.
The Theory of Constraints talks a lot about conflicts. Conflicts are what keeps us from becoming better. On part to becoming better at TOC is to know when you are in a conflict. There are certain words that can help you to notice a conflict.
TOC often talks about the large conflicts. These are the conflicts that most people have a problem with. When you dissolve these conflicts you help the most people.
This current website is built with Hugo. I wanted to try to build my own theme
with Tailwind. With Hugo it is not very easy to use Tailwind. The biggest
problem I found was that Hugo does not reload CSS with livereload.
The Current Reality Tree is a sufficiency tree shows (part of) the current situation of a system. It is used to model how causes and effects lead to certain undesirable effects (UDE). The arrows in the tree show which cause leads to which effect.
When there multiple arrows from a cause to an effect, then each cause creates the effect by itself. Removing one of the causes will perhaps lessen the effect, but not remove it completely.
These are some of my thoughts about Markdown in Logseq. In this note I try to find the assumptions behind the conflict.
This is thinking I did on my and is not associated with how Logseq will work now or in the future, this also does not represent goals of the Logseq team. This is what I think the goals could be.
The conflict Goal tree This is the goal tree, for some of the features we “need”.