How My Experience Formed My Unique Approach:
Due to the size and placement of brain tumors, patients often lost the ability to perform core, routine, behaviors (like writing or speaking). However, patients who were bi-lingual or had some form of “back-up” retained the less dominant. Observing this phenomenon illustrated the importance of contingency plans in the same principle, ie speaking multiple languages, from various perspectives in order to protect the integrity of the principle rather than a deep attachment to the means of actualizing it.
What can be assigned in a routine/automated manner should be set up at the initiation of the project in order to free up mental space for expansion. Core structures should be set up with extreme scrutiny at insemination as it creates the container that for the resources of the project to be used with intention in measurable ways / not waisted on emergency reinforcement of a weak framework.
The integrity of your data model is directly dependent on the quality of the data used to train it (GIGA - Garbage In / Garbage Out). You must stand behind what you create in full awareness of its proper use-cases and its limitations. Translated to a business perspective, it means that even if the company and the project is fueled by strong ideals, a rotten team will fail to retain the integrity required to make and maintain measurable impact in that area.
Just because the pipeline has fueled C-Suite business decisions for the past 20 years with “reliable values that look good” doesn’t mean those numbers aren’t shit. Why continue to invest in old systems that have already proven to be ineffective? Drop the rot, transmute the rest, and re-invest what remains with scrutiny. Otherwise, a personal attachment to “rightness” will be he fungi that infects your structure and bring it down from within.