Document the why, not just the what
Surface-level fixes create repeat tickets. Root-cause documentation creates experts. I always write for the second one.
About
Equal parts translator, troubleshooter, and teacher. Here’s the short version of a long story.
yes, I label everything 🏷️
I’ve spent more than 20 years face-to-face with customers, long enough to know that behind every “simple question” is a person who just wants to feel taken care of. That belief has shaped everything since.
The last several years took me deep into the SaaS world at Pax8, one of the world’s largest cloud marketplaces. As a Partner Support Escalation Engineer I became the go-to specialist for Microsoft GCC High licensing and provisioning: government cloud tenants, AOS-G, provisioning workflows, and the billing edge cases that make grown engineers sigh.
Along the way I discovered my favorite thing isn’t closing tickets. It’s making sure the same ticket never comes back. So I wrote the docs, built the trainings, mapped the processes, and mentored the teams. Now I do exactly that for clients as an independent consultant.
Anna
01 The road so far
Twenty-plus years of service work across industries. The common thread: people remember how you made them feel while you fixed the thing.
Provisioning support for one of the world’s largest cloud marketplaces. Among the highest ticket volumes on the team, with quality scores to match.
The go-to for government cloud licensing, complex escalations, and cross-team coordination. Wrote the playbooks, trained the trainers, found the $20M gap.
Bringing all of the above to MSPs and SaaS teams that need a calm expert, better documentation, and processes that hold up under pressure.
02 Character references
Pulled straight from a peer-submitted leadership review. Their words, not mine.
Spots challenges early, gathers the evidence, and brings leadership solutions instead of just problems.
Seeks out different perspectives and makes sure every voice is heard before deciding.
Teaches the why behind the what, so quality survives without her in the room.
Structured workflows, tidy documentation, zero scavenger hunts for that one login.
Follows through on commitments and communicates with clarity and integrity.
2025 Confluence Recap
Atlassian’s year-end recap put it nicely: “You’ve created plenty of pages from scratch and shared more information with your organization than most people. Way to go!”
my docs even outlived my role changes ✍️
03 The toolbox
Microsoft ecosystem
Work & knowledge systems
Data & communication
04 How I work
Surface-level fixes create repeat tickets. Root-cause documentation creates experts. I always write for the second one.
Success isn’t a closed-ticket count. It’s the person on the other end feeling heard, helped, and a little smarter than before.
High-pressure escalations need a steady hand. A methodical, logical approach puts everyone at ease, including the client.