Technical Communication

Overview

Platform engineering only works if the people using the platform can actually use it. At Adobe, that means a large community of content authors and production teams who build and maintain pages across adobe.com — people who aren’t engineers but depend on what engineers ship. A standing part of my role has been making sure that gap stays closed.

What I do

Documentation — written guides and references for the authoring and Global Web Production community, covering new blocks, authoring workflows, and platform capabilities as they ship. Written for people who need to act on the information, not for people who already understand it.

Live demos — bi-weekly sessions that walk content authors through new platform features in real time, on real pages. The format keeps the feedback loop short: if something is confusing in a demo, it gets fixed before it becomes a support request.

Direct engagement — when colleagues across design, production, and content teams have questions about what’s possible on the platform, those questions come here rather than going into a queue. That directness is faster for them and keeps engineering aware of where the gaps are.

What I learned

The ability to translate complex engineering clearly — not just document it, but make it genuinely usable — is what makes the cross-team work possible. Without it, every handoff is a negotiation and every new feature needs an interpreter.