Knowledge is vital intellectual property and is one of the most significant assets of an organization. Notably, it needs to be highly prioritized and managed strategically to enhance continuous improvement by capturing and reusing knowledge. Technology enterprises are associated with innovation, productivity, a collaboration of multidisciplinary professionals, tight budgets, and challenging time-schedules. These factors combined are often what leads to challenges with knowledge management. Frequent disappointments with past knowledge management initiatives have motivated organizations to gain a new understanding of the complex mechanism of knowledge, which governs the effectiveness of an enterprise. This study elaborated on identifying knowledge flow barriers and handling knowledge by lessons learned (LL) practice in a case company and identify changes to ameliorate the flow. Albeit, the observations revealed that the difficulties related to finding LL documents were not the main issue, it was the contribution of the leaders. The case company demonstrated a discrepancy between what they said they do, and what they actually do. Besides these barriers, the research also detected divergence in the fundamental understanding of the theoretical aspects within knowledge management and LL, which indicates confusion and absence of awareness for the project managers and the leaders. Implementation of Systems Engineering (SE) methods, such as Communities of Practice (CoP) or triple loop lessons learned may fill both the gaps in the company but also in the literature when it comes to improving knowledge flow in large-sized delivery projects. on a continuing basis (Li and Oppenheim, 2002). Government Accountability Office (GAO) discovered that LL at NASA was not routinely identified, collected, reviewed, and accessed by projects managers, which impedes them from exploring space faster, better, and cheaper (Li and Oppenheim, 2002).We observed that the case company did not prioritize continuous lessons learned, documentation of it, and follow-up on the lessons learned. A consequence of this is that the engineers and other project participants are doomed to repeat the same mistakes because they cannot find any valuable documentation. Due to this low priority, they are limiting their full potential. The ability to create, capture, store, share, apply and reuse knowledge is a vital key in any project. If employees with specific skills, knowledge, and/or experience leave the company due to retirement, better job offers, personal reasons, death, and so forth, they will lose valuable expertise. If their asset is not properly stored and distributed within the company it can cause a loss and influence the development, economic aspects, delivery time, stakeholders, end-customers, and many other areas. Literature Review Knowledge and knowledge management in Systems Engineering: Knowledge is often referred to as the experience, concepts, values, beliefs, education, and ways of working that can be shared and communicated (Sainter et al., 2...