# Systems Thinking Don’t look at component parts. Even job roles are broken into component parts. We tend not to look at systems. Look at cause and effect of component parts (causal relationships) and how they have utility. Causes are not seen within the existing system Look at properties that aren’t created by component parts, but are created by the system. Emergence is caused by component parts working together to create new qualities beyond the core properties. >[!EXAMPLE]+ Wetness is a new quality that emergence’s from the combination of hydrogen and oxygen. Neither hydrogen nor oxygen have wetness as a property When systems are created that create emergence you get superpowers. ## Three key areas 1) Feedback loops - iterating cycles - Previous iteration provides resources for next iteration - Effects are caused by these feedback loops 2) Bottlenecks - What is the one point for the constraint 3) Balancing Properties. We should design for emergence in our lives. - Different parts of our lives need to speak to each other. Pillars, Pipelines and Vaults (PPV) Pipelines are action aspect. This is OmniFocus - values goals - Goal outcomes - Projects - Action items. Vaults is knowledge management - how you capture various information - Then moves into knowledge vault. This is DT. Focus, Alignment and resurfacing in context are essential to knowledge management.