Systems thinking lets you step back from the detail to look at the whole holistically.
I’d explain it by likening it to looking at an end to end process before diving into a specific part. Without knowledge of the whole you might focus on something while missing context or risks etc.
One way I apply it in my current role is reviewing architecture documents to find areas of risk, ways and things to test as well as opportunities for automation and potential ways to use mocks and stubs to increase testability. In my current context it also allowed me to have early conversations about data and design.
I’d explain it by likening it to looking at an end to end process before diving into a specific part. Without knowledge of the whole you might focus on something while missing context or risks etc.
One way I apply it in my current role is reviewing architecture documents to find areas of risk, ways and things to test as well as opportunities for automation and potential ways to use mocks and stubs to increase testability. In my current context it also allowed me to have early conversations about data and design.