2025: A Year in Review

2025 has been a year of change, personally and professionally.

At the beginning of the year, I worked directly in the technical writing space, leading documentation initiatives. In April, I transferred to a role in PMO transformation. Through it all, I realized I was still solving the same problem: making information accessible and empowering people to learn and understand on their own.

January 2025 - March 2025

At the beginning of the year, I continued in my role as a Documentation Program Manager. While the title suggests roadmaps, stakeholder alignment, and task tracking, my leadership focus was on creating and launching a developer portal. On the surface, this looked like a traditional documentation initiative; but in practice, it became a knowledge system designed to empower developers to use our SDKs with confidence.

Leading a small team, I made executive decisions while also working hands-on: setting up backend systems, designing the site, defining the information architecture, and contributing directly to the content. Everything we built centered on improving the developer experience: helping users find what they needed quickly, understand how the SDKs worked in real-world scenarios, and move forward without waiting on support. The portal wasn’t just a collection of articles; it was a self-service environment that enabled developers to solve problems independently.

April 2025 - December 2025

In April, I transitioned into a new role focused on transformation as a Knowledge Manager within the PMO. I was no longer working directly with customer-facing content; instead, I became responsible for creating a PMO playbook and improving PMO operations. While this work was initiated in response to a recent audit, its purpose extended far beyond compliance; it was about empowering team members to confidently perform their roles.

In this role, I partner with leaders to define new governance, document it clearly, and train teams on updated processes. The work ensures that team members understand expectations, communicate more effectively, and operate with shared standards and purpose. Much like the developer portal before it, the playbook is evolving into a self-service knowledge hub—one that gives internal teams clarity, reduces ambiguity, and enables them to work independently and effectively.

Knowledge as the common theme

When I reflect on 2025, the common theme that stands out is knowledge. On the surface, my two roles appear very different: creating a developer portal fits squarely within technical writing, while internal governance and transformation are often viewed as operational or procedural work. But at their core, both are forms of knowledge management.

Knowledge management is the practice of creating, retaining, and sharing information so it can be discovered, understood, and used when it matters most. Whether the audience is external developers or internal teams, the goal is the same: ensure that critical information is discoverable, leveraged, and retained.

As you reflect on your own work this year, consider how you act as a steward of knowledge:

• Do you share information that helps others succeed?
• Do you capture knowledge so it can be reused later?
• Do you teach or mentor others, formally or informally?
• Do you find better ways to do things? Do you help others adopt them?

We’re all stewards of knowledge in one way or another. In 2025, I was reminded that while roles may change, the work of enabling people through clear, accessible information remains the same.