# Case Study 2 - 10/11/2024 ### Introduction In the modern university setting, institutions are not only centers of learning but also massive, complex organizations that rely heavily on automated systems to ensure that their business processes run smoothly. This particular case highlights the challenges one such university faced when its aging automation systems began to falter, threatening the continuity of its operations. The situation was made worse by the resignation of their top programmer, who left due to dissatisfaction with his salary, leaving the university vulnerable to system failures and operational inefficiencies. Unsurprisingly, the system issues led to significant delays, unresolved business process issues, and growing frustration among its clientele. The university formed serveral committees to address the problem, but these efforts proved futile. After several attempts, the university had no choice but to rehire the same programmer they had lost. He returned as a contractor and resolved the issue in ten days, successfully upgrading the university’s automation systems. However, his final invoice totaled a staggering P300,000.00, raising concerns about the fairness of the charge—especially considering that the work only cost P50,000.00, leaving P250,000.00 for his services alone. Was this fee justified? Or was it an exorbitant cost for what seemed like a relatively straightforward task? In this article, I’ll unpack these questions by exploring it in the context of Knowledge Management (KM), cost of downtime, value-based pricing, and market rates. I'll also discuss how automation, specifically information systems (IS), influenced university operations, and why the programmer's expertise may have been more valuable than initially thought. ### Data, Information, and Knowledge (DIK) in the Case

Example of raw data in the case

This situation provides us with several raw data points like: * P 300,000.00 * P 50,000.00 * 10 days * several * P 250,000.00 At this stage, these facts are merely raw data, devoid of meaning or context (Salia, 2024). Within the knowledge management framework, the processing and organization of data transforms it into valuable information. For instance, we now understand that the university formed **several** committees in response to the automation system's failure, but these committees proved unsuccessful. As a result, they had to rehire the former programmer, who resolved the issue. The invoice he submitted, valued at **P300,000.00**, included an actual cost of **P50,000.00**, indicating that he charged **P250,000.00** for his expertise. This transformation of data into information gives the raw facts meaning and structure (Salia, 2024). Ultimately, the case scenario itself constitutes information. Further interpretation of this information gives us knowledge—a deeper understanding that is actionable and context-driven. In this case, the P 250,000.00 charged reflects the programmer’s tacit knowledge—his personal, experiential understanding of the university’s systems, which was critical to solving the problem quickly. The committees were ineffective precisely because they lacked this specialized knowledge. This demonstrates the importance of tacit knowledge in maintaining operational continuity and justifies the cost by highlighting the value of avoiding financial damage from prolonged downtime (Anderson, 2023). ### The Value of Tacit Knowledge and Expertise in Justifying the Fee The P 250,000.00 charged by the programmer can be further understood in terms of tacit knowledge and the economics of expertise. Tacit knowledge, by its nature, is difficult to document but essential for solving complex problems (Anderson, 2023). The programmer’s deep understanding of the university’s automation systems allowed him to resolve an issue in 10 days, whereas committees formed to solve the problem had failed. This ability to diagnose and fix the issue quickly, leveraging years of experience, justified the premium fee charged for his services. To further understand this, it's useful to consider the distinction between explicit, implicit, and tacit knowledge, as outlined by Anderson (2023). * **Explicit knowledge** is easily articulated and shared, such as manuals or documented procedures. For example, technical manuals of the university’s systems would fall under this category. * **Implicit knowledge** refers to the application of explicit knowledge, such as how to perform tasks effectively. The programmer likely relied on implicit knowledge when applying his understanding of the systems to efficiently solve the automation issues. * **Tacit knowledge**, which is most relevant here, is the hardest to document and codify. It represents the personal, experiential knowledge that enabled the programmer to solve the problem in 10 days, something the committees could not achieve without his expertise. This tacit knowledge was essential and irreplaceable, highlighting why the university had to pay a premium for his services. Becker’s (1962) human capital theory supports this justification, as it posits that individuals invest in their knowledge and skills with the expectation of receiving a return. The scarcity of the programmer’s expertise within the university elevated the value of his services. Thus, the P 250,000.00 charged represents compensation for the unique, irreplaceable knowledge that only the programmer could provide. ### The Hidden Cost of Downtimes and Business Disruptions When considering the cost of the computer programmer’s invoice of P250,000, it is essential to weigh it against the potentially crippling consequences of IT downtime. According to Jack (2024), downtime has both tangible and intangible costs, ranging from lost revenue and productivity to reputational damage. For an organization, an unplanned outage lasting just one day can easily surpass P250,000, especially if it involves critical system failures or data loss. This makes the programmer’s invoice not just a fee for service but a preventive measure that can save the company from even more significant financial and operational losses in the future. The invoice reflects the programmer's expertise as a direct investment in business continuity. By addressing and resolving the root causes of downtime—which, as mentioned, is the failing component—the programmer ensures that future interruptions are minimized or entirely avoided. As seen in real-world examples, even small businesses can suffer six-figure losses from brief outages (Jask, 2024). When factoring in the cost of mitigation, the invoice is justified as a strategic defense against downtime’s disruptive impact rather than a mere operational expense. ### Business Process Automation (BPA) and Security Risk Management: Ensuring Future Efficiency and Security The programmer’s intervention not only restored the university’s automation system but also upgraded its Business Process Automation (BPA), positioning the institution for enhanced future efficiency and security. BPA, as literature suggests, automates repetitive tasks, improves accuracy, and streamlines operations, reducing manual errors and operational delays (Brañas, 2024). This upgrade will likely optimize critical functions such as student enrollment, financial transactions, and service management, ensuring smoother workflows and better data management. More importantly, the BPA upgrade addresses significant security risks associated with legacy IT systems. According to Schrader (2024), outdated systems pose considerable cybersecurity threats, being more vulnerable to breaches and compliance failures due to their lack of modern security features and vendor support. By upgrading the system, the programmer has future-proofed the university against such risks, ensuring it meets current security and compliance standards, thus avoiding potential penalties or audit issues. This long-term benefit justifies the premium fee charged by the programmer. His expertise not only resolved the immediate operational issues but also safeguarded the university from future disruptions and security breaches. The literature underscores the importance of automation in boosting productivity and minimizing security risks, making this upgrade essential for the institution’s continued success (Perez, 2023; Schrader, 2024). Without this intervention, the university would have faced more serious problems down the road, including more potential downtime, reputational damage, and financial loss, reinforcing the value of the investment in both immediate system restoration and future risk mitigation. ### Knowledge Management: The Core Issue At the heart of the university’s crisis is a breakdown in Knowledge Management. As Davenport and Prusak (1998) describe, KM involves capturing, distributing, and effectively using knowledge. When the programmer left, the university lost access to critical tacit knowledge. Had the university established a Knowledge Management System, it could have mitigated the problem by ensuring that both explicit and tacit knowledge were documented and stored (Anderson, 2024). Explicit knowledge is easier to capture—things like technical manuals and operational procedures—but tacit knowledge, the kind that’s gained through personal experience and deep familiarity, requires more effort to document. However, it’s also far more valuable in complex problem-solving, which is why its absence left the university so vulnerable. Without a proper KMS in place, they ended up paying a premium to access knowledge they once had internally, a direct consequence of poor KM practices. The **Knowledge Life Cycle**, as discussed by **Skyrme (2011)**, offers valuable insight into how organizations can better manage and retain knowledge. It involves both the sharing of existing knowledge and fostering innovation. In this case, had the university focused on capturing both explicit and tacit knowledge, the problem might have been resolved internally without requiring an external expert. This highlights the importance of **KM** in building organizational resilience and reducing dependence on single individuals for critical expertise. Additionally, proper Knowledge Management strategies, such as conducting surveys to identify dissatisfied employees, could have led the university to a smarter decision—possibly identifying and addressing the programmer’s dissatisfaction early. Transforming data from employee feedback into actionable information would have allowed the institution to retain him, potentially preventing the costly rehire process. ### Information Systems and Automation: The Role of Hardware, Software, and Peopleware in Knowledge Management The university’s automation system can be understood as an information system (IS), and from what I have learned in our KM course, information systems are composed of three important elements: hardware, software, and peopleware—the human expertise required to operate and maintain the system. While the hardware (servers, machines) and software (applications, algorithms) can be managed, the absence of knowledgeable people who can manage, configure, and maintain those—in this case, the programmer—left and, as a result, made the system vulnerable to failure. This highlights the essential role that people play in the overall effectiveness of an IS, especially when dealing with custom-built or complex legacy systems. Through a knowledge management lens, the university's failure to capture the programmer’s tacit knowledge before his departure contributed to its reliance on his re-engagement. A well-structured Knowledge Management System (KMS) could have stored this critical knowledge, ensuring it remained accessible to the organization even in his absence. This situation underscores the need for KM strategies that don’t just store explicit knowledge (e.g., manuals, guides) but also find ways to capture the more elusive tacit knowledge that is often vital in resolving complex, real-world problems (Anderson, 2024). ### Value-Based Pricing and Market Rates The concept of value-based pricing offers another lens to justify the P 250,000.00 fee. Value-based pricing sets fees based on the value delivered to the customer rather than simply the time or materials used (Calabrese & De Francesco, 2014). In this case, the university paid for the outcome—the swift resolution of a critical problem that had threatened to disrupt operations and damage its reputation. The value of restoring the university’s systems and preventing further downtime was far greater than the direct costs of resolving the issue. Market rates for highly specialized IT contractors further justify this fee. According to Shiklo and Lipnitski (n.d.), software maintenance costs can range from $5,000 to $50,000+ per month, depending on the software type, number of users, and required activities. Calculating these amounts over an average 30-day month, the daily rate for the lower estimate ($5,000 per month) would be $166, or approximately PHP 9,496.69. Over a 10-day contract, this results in PHP 94,966.90. For the higher estimate ($50,000 per month), the daily rate comes to $1,667, equating to around PHP 95,367.40 per day, totaling PHP 953,674.00 for 10 days. When compared to these industry-standard rates, the invoice of P 250,000.00 is more than justified. It aligns with the lower end of the market scale while considering the critical importance and urgency of the work delivered, further reflecting the true value of the service provided. ### Lessons Learned and Recommendations Several key lessons emerge from this case study, particularly within the **Knowledge Management** context: * **Implementing Knowledge Management Systems (KMS) for Knowledge Retention:** The university’s inability to retain critical knowledge after the programmer’s departure highlights the necessity of a Knowledge Management System (KMS). A robust KMS would have allowed the university to capture both explicit and tacit knowledge, ensuring that essential information about the automation systems was preserved. Davenport and Prusak (1998) emphasize that organizations should not only document processes and systems but also focus on capturing tacit knowledge through structured documentation, thus avoiding over-reliance on individual expertise. Had a KMS been in place, the university could have mitigated the risks associated with losing its primary expert and prevented the need for high-cost external consultation. * **Mentorship Programs to Facilitate Tacit Knowledge Transfer:** One of the key issues in this case was the university’s failure to transfer tacit knowledge before the programmer left. Mentorship programs are critical in facilitating this transfer by pairing senior employees with junior staff to ensure that valuable knowledge is passed on before employees leave. Winstanely (2024) underscores the importance of mentorship in creating continuity within organizations by systematically transferring tacit knowledge. Had the university established such a program, the programmer’s experiential knowledge of the automation system could have been transferred to junior staff, ensuring the institution maintained the capacity to manage its systems internally. * **Investing in Human Capital as a Long-Term Asset:** The university’s decision not to retain the programmer because of salary disputes overlooked the value of human capital as a long-term investment. Kenton (2024) notes that organizations should treat employee expertise as a strategic asset rather than a cost to be minimized. By investing in key personnel, organizations can avoid high costs associated with knowledge loss and the need for expensive external consultants. In this case, retaining the programmer, or at least facilitating a smooth transition, would have avoided the P 250,000.00 emergency repair fee. Organizations that view their human capital as a long-term asset reap benefits in stability, continuity, and cost savings. * **Implementing Regular Employee Satisfaction Surveys:** As part of a comprehensive Knowledge Management strategy, the university should implement regular employee satisfaction surveys. These surveys can provide valuable data that, when processed into information and knowledge, can help identify potential issues before they escalate into crises. In this case, such surveys might have alerted the university to the programmer's dissatisfaction, allowing for proactive measures to address his concerns and potentially prevent his departure. ### Conclusion In the end, the P 250,000.00 fee charged by the programmer can be justified when we consider the long-term value of the expertise involved, the hidden costs of prolonged downtime, value-based pricing, market rates, and the importance of Knowledge Management. The university’s failure to capture and retain critical knowledge before the programmer’s departure resulted in a costly re-engagement. However, the cost of hiring him back was far outweighed by the potential financial and reputational losses that would have occurred if the system had remained broken. Furthermore, this case study emphasizes the need of not only controlling knowledge but also of using it to guide wise, proactive actions. If the university had followed appropriate knowledge management techniques—that is, frequent employee satisfaction polls and feedback systems—it might have found and resolved the programmer's discontent before it resulted in his leaving. By being proactive, the university might have avoided the crisis it was in and the later expensive rehiring of the programmer as an outside consultant. Lastly, this case serves as a powerful reminder of the importance of managing knowledge effectively. Whether through a formal Knowledge Management System or informal mentorship programs, organizations must prioritize capturing the expertise of their employees to avoid crises. In doing so, they not only ensure operational continuity but also foster a culture of knowledge sharing that can prevent expensive, last-minute solutions like the one faced by this university. ### References Becker, G. S. (1962). Investment in Human Capital: A Theoretical Analysis. *Journal of Political Economy*, *70*(5, Part 2), 9–49. Brañas, A. (2024, April 26). *What is Business Process Automation (BPA) – A Complete Guide*. Qflow. Calabrese, A., & De Francesco, F. (2014). A pricing approach for service companies: service blueprint as a tool of demand-based pricing. *Business Process Management Journal*, *20*(6), 906–921. Davenport, T. H., & Prusak, L. (1998). Working knowledge: how organizations manage what they know. *Choice Reviews Online*, *35*(09), 35–5167. Jack, S. (2024, September 9). *What is the cost of IT downtime for small businesses in 2024?* E-N Computers. Kenton, W. (2024, July 3). *Human Capital Definition: Types, Examples, and Relationship to the Economy*. Investopedia. Perez, J. (2023, April 12). *How Automation Drives Business Growth and Efficiency - SPONSOR CONTENT FROM SALESFORCE*. Harvard Business Review. Schrader, D. (2024, January 10). Mitigating the security risks of legacy IT systems. *Security Info Watch*. Shiklo, B., & Lipnitski, A. (n.d.). *Software Maintenance Costs: How to Estimate and Optimize*. Skyrme, D. J. (2011). *KM Concept: Knowledge Cycles*. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://usep.gitbook.io/ice-311-blogs/case-studies/case-study-2-10-11-2024.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.