In 2025, writing great technical documentation is not just about what you write. It’s about how fast you can produce it, how you manage it, and where you publish it. That’s why I use the full Microsoft 365 stack—Word, SharePoint, Lists, and Copilot—to write, manage, and publish documentation faster and
🚀 Lessons I Learned Writing BRDs for a Project That Didn’t Go as Planned 🧠The Project That Taught Me the Most Not every project ends in success. Some fall short. But as a business analyst, those are the ones that teach you the most. I was brought into a
In digital transformation work, we often focus on what’s not working. But sometimes, the real problem is what’s not there at all. That’s where a Gap Analysis Document becomes one of the most valuable tools in a business analyst’s kit. I used it recently on a government compliance transformation project—where
In every digital transformation project, there’s usually one low-effort fix that saves hours of wasted time. This is one of those fixes. And it came from process mapping. 🧠The Context I was working as a business analyst on a digital onboarding rollout for a national education provider. They were
AI is changing the way we work. And as a technical writer, I’m not resisting it. I’m embracing it. Not because I think it will take over the job—but because it helps me do my job better. Faster content creation.Smarter editing.More time for real collaboration. That’s what AI gives me.
Imagine this: Your most experienced employee—the one who knows all the ins and outs of your operations—leaves. No notice. No handover. Just gone. Maybe they won the lotto. 💸Maybe they found a better opportunity.Or maybe life just happened. What would happen to your business? ⚡ Operations stall.⏳ Projects slow down.💰
Some business processes look simple—until you try to document them. Then you realise no one does it the same way, the steps are hidden, and the handoffs are undocumented. I hit this exact wall working on a digital transformation project for a national services provider. They were replacing three legacy
When you’re improving a process or implementing a new system, you can’t stop at understanding how things work today. You also need to define how they should work tomorrow. That’s where to-be process mapping comes in. As a business analyst, it’s one of the most important tools I use to
One of the biggest mistakes new business analysts make is taking what they’re told at face value. The SME says “that’s how the process works” — and they write it down. The stakeholder says “we just need a system that does this” — and they add it to the list.
