# Blisters, Blogs, and Breakthroughs: A KM Journey

The last Knowledge Management (KM) class of the semester was on September 18, 2024. But I wasn't there. Instead of sitting in the classroom, engaged in a conversation I had grown increasingly fond of, I found myself confined to my bed, battling something I hadn’t expected—Varicella, or more commonly known as chickenpox. It’s one of those illnesses we associate with childhood, something most of us think we left behind. Yet, here I was, at this pivotal moment of the semester, laid up and fighting off both the fever and frustration.

### The Diagnosis and The Struggle

It all started innocently enough. Just a day before that final class, I found myself feeling off—more tired than usual and a little feverish. I didn’t think much of it at first; we all have those off days, especially as students juggling multiple responsibilities. But later that night, it was clear something wasn’t right. Small blisters started popping up on my skin. When I went to the doctor, the diagnosis was immediate: chickenpox.

It felt like a cruel twist of fate. My body had become the battleground for an infection that completely drained me, both physically and mentally. Tasks I had taken for granted—like sitting up or walking across the room—suddenly became overwhelming. The dizziness, the fever, and the constant itching were a package deal I hadn’t signed up for.

Funny enough, just a week before, my professor had actually sent me to the clinic. He thought I might be coming down with something infectious because I had been wearing a mask, and he was concerned for the rest of the class. Back then, I wasn’t sick—just cautious and have some history on nasal polyps (you can read my blog about it [here](/ice-311-blogs/september-2024/unmasking-unexpected-lessons.md)). But now, his assumption had become my reality. My doctor's orders confined me to isolation for two weeks. It was frustrating, to say the least, but there was little I could do other than rest and ride it out.

### The Inability to Connect

The worst part wasn’t even the fever or the blisters—it was the isolation. In those first few days, the exhaustion was so intense I couldn’t even reach out to my classmates. The simple act of texting to ask about what I had missed felt like running a marathon. My usual lifeline to the outside world—my phone—became a source of frustration. Normally, it’s the first thing I reach for when I need answers, but now, even looking at the screen made my head spin.

I wasn’t just physically weak; I was mentally disconnected. My body had forced me to take a break, but my mind was restless. I kept wondering what I had missed in that last KM session, particularly since it was the final face-to-face class of the semester. It was more than just a class for me—it felt like the culmination of everything we had worked toward throughout the course. And yet, there I was, unable to do anything but rest and wait until my body allowed me the clarity to focus again.

### Curiosity Sets In

Several days later, when the fever finally started to break, I could feel my curiosity pushing through the lingering exhaustion. Though I still felt physically drained, my mind was racing. I wanted to know what had transpired in that final KM class. It was the kind of curiosity that doesn’t let you rest until it’s satisfied, and I knew I wouldn’t feel settled until I caught up.

So, I did what any curious student would do: I turned to my classmates’ blogs. Fortunately, some had already written about the class, sharing their reflections and insights on the session. I read through their posts eagerly, piecing together what I had missed. It felt like I was connecting the dots, reconstructing the experience from the fragments they had left behind.

#### “The Last Face-to-Face Knowledge Management Class”

One blog that caught my attention was titled "The Last Face-to-Face Knowledge Management Class," and reading through it, I could almost picture the session unfolding in my mind. It wasn’t just another lecture, but a culmination of everything we had learned throughout the semester.

The class had started with a light-hearted twist: a latecomer was asked to perform a talent as a playful penalty. The classmate danced, impressing everyone, including the professor. It was refreshing to see how a light moment could set the tone for an otherwise serious discussion about Knowledge Management.

The core of the lesson revolved around creating a roadmap—not just a metaphorical guide, but a structured plan for capturing, sharing, and utilizing knowledge. I could almost hear my professor’s voice as my classmate described the professor’s insistence on clarifying what a roadmap truly was. It wasn’t just about setting objectives but about outlining a clear, actionable plan to achieve those goals.

While my classmates got a head start in learning and discussing about the roadmap, this wasn’t a one-off task. It was a crucial Learning Evidence that we will submit later this semester, and I’m part of a group that will be working on it. Reading the blogs about the roadmap activity got me even more excited. I can’t wait to apply what I’ve learned when it’s our turn to build this roadmap for a real organization. It’s a chance to bring theory to life, and I’m eager to dive in!

#### Insights from the BTM Section Blog

Curiosity wasn’t satisfied with just one blog, though. I also stumbled upon another reflection from a schoolmate in the BTM section. This blog was titled *"Final Formal Session: Knowledge Management Tools and Techniques,"* and it provided a slightly different perspective on the class. While my first read focused more on the overall experience, this one delved into the practical side of things—the tools and strategies discussed.

One thing that really stood out was the mention of brainstorming as a powerful Knowledge Management tool. The blogger described how the class had broken down the brainstorming process into two phases: divergent thinking, where all ideas are welcomed without judgment, and convergent thinking, where the group narrows down the most practical and useful ideas. It struck me as a simple yet effective way to structure group discussions. By allowing for creative freedom in the initial phase, the group could explore all possibilities before refining the ideas into something actionable.

Another key takeaway from this blog was the idea that blogs themselves can serve as valuable Knowledge Management tools. It was an insight that hadn’t fully occurred to me before, but after reading about it, it made perfect sense. Blogs are a platform for sharing knowledge in a way that’s both informal and organized. They allow for the exchange of ideas, encourage interaction through comments, and provide a space for continuous learning. It was a reminder that Knowledge Management doesn’t have to be confined to rigid, traditional methods. In fact, the tools we use every day—like blogs—can be just as effective.

### Reflecting on What I Missed

By the time I finished reading both blogs, I had a clearer picture of what I had missed. Of course, there was a part of me that wished I could have been there in person, contributing to the discussions. But at the same time, I realized that even though I wasn’t physically present, I hadn’t been left out. My coursemates’ blogs had given me access to the knowledge I missed, and that in itself was a powerful demonstration of the concepts we had been learning all semester.

Knowledge isn’t something that exists in isolation. It’s shared, transferred, and accessed in a variety of ways. My coursemates had shared their reflections with me, allowing me to catch up on what I had missed, and in doing so, they had reinforced one of the core principles of Knowledge Management.

This brings me back to something I’ve grown increasingly grateful for: Sir’s encouragement for us to create blogs throughout the course. What initially seemed like a simple exercise turned out to be one of the most effective ways for us to transfer knowledge. Despite only having four face-to-face sessions with him, I’ve learned so much—not just from his lectures, but from the way he’s encouraged us to explore and share our ideas. His approach to teaching Knowledge Management has been eye-opening. He’s shown us that learning doesn’t always happen in formal settings—it can happen through unexpected, creative tools like blogs.

### The Power of Isolation

Ironically, my forced isolation during the illness gave me a deeper understanding of the importance of connection. Knowledge Management relies on our ability to connect with others, to share and access knowledge even when we’re physically apart. During those days when I was confined to my bed, I felt disconnected from my classmates, but their blogs brought me back into the fold. It was a reminder that knowledge doesn’t have to be lost just because we’re not in the same room. Through digital tools—blogs, social networks, online forums—we have the ability to stay engaged and continue learning, even when life throws obstacles in our way.

This experience also gave me a new appreciation for how isolation can affect our ability to share knowledge. When we’re cut off from others, it’s easy to feel like we’re missing out, like we’re not part of the conversation. But in a well-managed Knowledge Management system, no one should feel left out. There should always be a way to access the information and insights we need, even when we can’t be there in person.

### Lessons Learned

As I recovered from my illness, I found myself reflecting on how the experience of having chickenpox paralleled some of the challenges we face in Knowledge Management. Just as I had been isolated from my classmates, knowledge within an organization can often become isolated or lost if it isn’t properly managed. It takes conscious effort—whether through a roadmap, a blog, or a brainstorming session—to make sure that knowledge is captured, shared, and used effectively.

The roadmap project that we are tasked to create is a perfect example of this. It should be designed to break down barriers to knowledge sharing, ensuring that everyone in the organization is on the same page and that valuable knowledge doesn’t get lost in the shuffle. I’m excited to contribute to my group’s roadmap in the coming weeks, applying everything I’ve learned throughout the course to create a Knowledge Management strategy that can make a real difference.

### Moving Forward

Looking back on these past few weeks, I’m grateful for the lessons I’ve learned—even the ones that came from being sick. This experience has taught me that learning and growth don’t always happen in a linear way. Sometimes, life throws us curveballs—like chickenpox—that force us to slow down and reflect. But even in those moments, there are opportunities to learn and to stay connected with the knowledge that matters most.

As I move forward in my Knowledge Management journey, I feel more equipped to handle not only the academic challenges ahead but also the unexpected obstacles that life may throw my way. Whether it’s through a roadmap, a blog, or a brainstorming session, I’ve learned that Knowledge Management is about more than just organizing information—it’s about resilience, adaptability, and the determination to keep learning, no matter the circumstances.

In the words of Maya Angelou, *“We may encounter many defeats, but we must not be defeated.”* This quote resonates deeply with me now. Despite the setbacks of illness, I haven’t been defeated. Instead, I’ve learned a valuable lesson in resilience, both in life and in Knowledge Management.


---

# 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/blisters-blogs-and-breakthroughs-a-km-journey.md?ask=<question>
```

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.