How do you identify and challenge your assumptions in systems thinking?

In system design, we will have 2 maps: the current system map and the desired future system map. From the current system to the future system, there are lots of assumptions that need to be made and validated. Some common assumptions include the highest leverage points for interventions, the expected relation change between stakeholders, the feedback loop evolution, the system pattern stability(linear or non-linear), and the expected outcomes of each stakeholder.

To challenge assumptions, you must understand the opinions and facts used in decision-making. Any statement that is not supported by facts is considered an opinion. Any opinions that are used in the decision-making process are assumptions. Sometimes, it is hard to explicitly list all the factors and considerations when making decisions. If the process involves group decision-making, the voting power and the stakeholder interaction will disproportionately affect the result. However, we should never forget that the goal is not to test all the assumptions we made in system thinking; the goal is to manage the risk of assumptions to bring us to the desired future.

Transparency is essential when communicating with different stakeholders. When the problem is dynamically complex, people should carefully visualize the system map with 2-D diagrams. Often, the problem is a 4-D diagram, and every time we conduct dimension reductions, specific information will be hidden or distorted. The process will lead to a certain degree of bias. Bias originates from incomplete information, which usually leads to problematic unintended results. Focusing on the controllable factors and preparing for the worst-case scenario will help reduce some risks.

As a recent graduate with an MSc in Systems Thinking in Practice, I am concerned that this is an AI generated conversation via LinkedIn. Any assumptions I have are based on interacting with a human. When this is in question, who knows where it will lead . . . ?

You challenge your assumptions of any Sytem by assuming you have assumptions. As contrite as that sounds it is genuinely the place we need to start. Admit to ourselves we will always have our own bias, or own world view, lense or story. I find the key to discovering those assumptions once you admitted to yourself they will be there is to ask your stakeholders, ask for their help to understand better, openly invite them to point out your own assumptions, to (in their eyes) correct you. Ask what did you get wrong, or at least not quite right. It took me many years of experience to become humble enough to ask for my misheld beliefs to be challenged and exposed. From there, as a team we could all learn more and uncover better understanding.

This process is native to the world of User-Experience design. In the concept phase, we have a hypothesis and/or requirement, we do research to triangulate certain elements in order to begin designing. Design a possibility. Then validate towards another iteration of the design. Systems Thinking in UX Design is the triangulation of truth and it is inherent to the quality of our production. But many do not know how much Systems Thinking influences UX.

Identifying and challenging assumptions in systems thinking involves: 1. Reflection: Regularly question your own beliefs and viewpoints. 2. Diverse Perspectives: Seek input from others with different backgrounds and expertise. 3. Ask Why: Use the "Five Whys" technique to dig deeper into underlying assumptions. 4. Document Assumptions: Clearly list assumptions and revisit them periodically. 5. Scenario Testing: Explore different scenarios to test the validity of your assumptions. These steps help ensure a more comprehensive and unbiased understanding of the system. #DhandheKaFunda