# Unmasking Unexpected Lessons There’s always something unpredictable about classes that keeps us on our toes. Maybe it’s the professor’s left-field humor, or a surprise quiz when you’re least prepared. But for me, it wasn’t just the humor or quizzes that made this class memorable—it was a face mask, a clinic visit, and a whole lot of reflection on knowledge management (KM). So, here’s the rundown of how a simple day in class turned into an unexpected lesson in KM and why I might never look at a face mask the same way again. ### **A Bit of Humor to Start the Day** The day started a little late—nothing out of the ordinary. Our professor stepped out of the classroom for reasons unknown, giving us a few minutes to mentally prepare (or, in my case, to hope I remembered enough from the last sessions to avoid embarrassment). When he returned, the class kicked off with a prayer led by one of our classmates. Now, if there’s one thing I’ve learned about our professor, it’s that you can always count on him for a bit of humor. Right after the prayer, he asked our class mayor a seemingly straightforward question in Bisaya (non-verbatim): “Naay bay virigin diri?” (Translation: “Are there any virgins here?”) But, in a comical twist, the mayor misheard him and thought he was asking if someone was celebrating their birthday. That made me chuckle from the back of the room. And as fate would have it, someone *was* having a birthday, a classmate seated just two seats away from me. Funny how things work out. But the comedy didn’t end there. Our professor quickly clarified his question, sparking laughter throughout my group. Moments like these are always a good reminder that a little humor can ease the tension and make learning less of a chore—an important lesson when discussing something as dense as KM. ### **The Mask That Launched a Journey to the Clinic** Then my mask got me in trouble. Our professor asked if a classmate seated on the right was sick since he was wearing a mask. He said that lack of sleep was making him unwell. Clearly worried, our facilitator advised that he go to the clinic. Then the focus turned to me—also masked up. When he asked whether I was sick, I answered simply "yes," not mentioning that my illness was non-communicative. Neither the flu nor a cold was raging inside me. Rather, my mask was a defense against my years of struggling with chronic sinus allergies. I even had a history of nasal polyps, which sound to be rather pleasant. But eager to stay in class, I decided to take off my mask instead of explaining. Our professor, however, wasn’t having it. Not as punishment but rather out of concern for the class's health, he urged me to visit the clinic. He said, "We're in a confined space," reminding me that a communicative disease would sweep like wildfire. And you know what? He had it right. That did not stop me, though, from feeling a little bitter of the circumstances. I mean, there were plenty of masked students last meeting, and no one was sent to the clinic. So why now? ### **From Classroom to Clinic: The Unexpected Field Trip** So off I went, mask in face, accompanied by a friend who had also been exiled to the clinic. I had a whirl of ideas in my head as we walked. I first worried about missing an important section of the lecture. I still found KM to be a somewhat new concept, and my fear of missing behind cause a bit of distress at me. I laughed at the circumstances, though. Imagine being sent from class for a face mask! When we arrived at the clinic, a staff questioned, "What's the problem?" "Our professor sent us here because we're wearing masks," my friend said. The clinic staff blinked in surprise. Apparently, it wasn’t the norm to send students to the clinic for this reason, and they found it amusing that we were following orders so strictly. They even reassured us that, given the lingering presence of COVID-19, wearing masks wasn’t just acceptable—it was encouraged. ### **An Unexpected Nostalgia Trip** While waiting for our check-ups, we had to retrieve our health records. Now, this may not sound like a big deal, but pulling out that dusty file was a trip down memory lane. I hadn’t thought about those documents since my first year in university. Suddenly, I was flooded with memories of that time—my naïve excitement about college life, the overwhelming number of requirements, and how, in what felt like the blink of an eye, I am now a 3rd year student. It was one of those moments where you realize how far you’ve come, and just how much knowledge you’ve accumulated along the way ### **The Clinic Check-Up** Our check-ups were routine—blood pressure, temperature, a quick listen to our breathing. My blood pressure was slightly high, which didn’t surprise me since I’d only had an hour of sleep and a concerning amount of caffeine. But the final diagnosis? Allergies. No flu, no cold, just the same sinus issues I’d been dealing with for years. I was prescribed Cetirizine, a familiar antihistamine, and that was that. My mask-wearing wasn’t about protecting others—it was about protecting myself from the allergens that love to attack my sinuses. But still, the experience made me reflect on knowledge management. ### **Knowledge Management in Action: Clinic Edition** Think about it—what just happened was a perfect example of KM in action. In KM, we talk a lot about tacit knowledge (what we know from experience) and explicit knowledge (what can be documented or communicated). The clinic visit was a lesson in how tacit knowledge (my understanding of my sinus issues) intersects with explicit knowledge (the clinic staff’s formal records of my health). Before this visit, no one in class knew why I wore my mask knowing that it wasn't mandatory anymore. It wasn’t written down anywhere. But my tacit knowledge of my own health conditions wasn’t enough to protect the class from misunderstanding. It took explicit documentation—my health records, my doctor’s check-up, the prescription—to translate that personal knowledge into something that could be shared and understood by others. This, my friends, is the essence of KM: transforming tacit knowledge into explicit knowledge that can benefit not just an individual, but a community. And in this case, it wasn’t just about learning something new—it was about creating a shared understanding. ### **Learning from Others: BTM 3B’s Lesson** Since I missed most of the class, I hung out with some acquaintances from BTM 3B. Lucky for me, they had already gone through a similar lecture with our professor, and they filled me in on the key points I missed. We talked about two types of knowledge: tacit and explicit. Tacit knowledge is that personal, intuitive kind of knowledge, the stuff you can’t quite put into words—like knowing how to ride a bike or recognizing a familiar face. Explicit knowledge, on the other hand, is the kind you can write down, organize, and communicate to others—think textbooks, documents, and databases. According to them, our professor also touched on the importance of applying technology in management. He shared a formula: $$ \textnormal{IT} = \textnormal{Hardware} + \textnormal{Software} $$ which connects to KM by showing how tech solutions (both hardware and software) can help manage, store, and share knowledge more effectively. Even though I wasn’t in class, this conversation reminded me that learning doesn’t just happen in a formal lecture. It happens in everyday interactions, in casual conversations, and in unexpected places—like the clinic or during a chat with schoolmates from another section. KM, at its core, is about sharing knowledge and learning from others, wherever that may happen. ### **Connecting the Dots: My KM Takeaways** By the time my classmates returned from class, it was almost lunchtime. They teased me for missing the session, but I wasn’t too worried. Between my trip to the clinic and my conversation with BTM 3B, I realized I hadn’t missed as much as I thought. In fact, the whole experience was a lesson in KM itself. What I learned that day was that KM isn’t just about managing data or creating systems. It’s about the flow of knowledge—how it’s created, shared, and used. From the professor’s concern over my mask to the clinic’s response to my allergies, each step involved a transfer of knowledge. My tacit knowledge became explicit when I explained my allergies, and the clinic’s records became part of my personal knowledge base. And, of course, I gained new insights from my schoolmates, blending their tacit experiences with the explicit knowledge from the lecture. This is the beauty of KM. It’s not confined to a single system or process. It’s in the classroom, in conversations, in the clinic, and even in the most unexpected moments. ### **Final Thoughts: An Experience to Remember** I know I've already mentioned this in my previous blog post, but this quote from Albert Einstein truly resonated deeply with my experience: > “The only source of knowledge is experience.” And after this day, I couldn’t agree more. It wasn’t the lecture I’d expected, but it was a lesson I’ll never forget—one that connected health, humor, and knowledge management in a way I never saw coming. Sometimes, it’s the detours in life that teach you the most, and this one certainly did. --- # 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/september-2024/unmasking-unexpected-lessons.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.