Definition:
Fundamental: A non-accusatory term describing something implemented only at its bare functional level, but not yet properly completed or robust.
Explanation:
The term “fundamental” refers to systems, processes, or features implemented minimally to meet an immediate project deadline or delivery requirement but not subsequently refined or completed to a sustainable standard.
Although functional, these fundamentals often lack essential attributes such as comprehensive documentation, support infrastructure, or operational resilience.
Common examples include:
- Software: implemented without proper support teams or documentation.
- Network features: implemented but still requiring significant manual intervention and maintenance.
- Business processes: heavily reliant on a single individual’s specialised knowledge, creating vulnerability due to lack of redundancy.
Using the term “fundamental” avoids assigning blame while clearly highlighting the importance of addressing the unfinished aspects. It implicitly communicates to management that such tasks are critical for long-term operational efficiency.
Completing fundamentals not only reduces business and technical debt but also significantly lowers operational risks and ongoing resource overhead.
Although refining existing fundamentals might appear less exciting compared to pursuing new initiatives, the long-term benefits, such as freeing resources and reducing risk, substantially enhance organisational capacity for future projects.
Disclaimer: As always these posts are not aimed at anyone client or employer and are just my personal observations over a lifetime of dealing with both management and frontline associates.