Since starting as a technical services writer, I’ve realized how much of writing happens before I actually draft anything.

Reviewing requirements, checking source documents, and asking someone to clarify a detail are all part of the job. I’m learning to pause when something is unclear instead of trying to write around it.

It’s a small shift in how I approach my work, but an important one: understand it first, then explain it.

A self-initiated brand storytelling project. I wanted to show how a founder story can make an abstract branding lesson feel real, so I wrote a narrative-led business article following "Andrew," a fictional real-estate owner whose marketing spend isn't converting.

The piece moves from the business problem to the underlying communication gap, includes a before/after messaging example, and closes with a broader lesson on positioning, trust, and customer perception.

https://wax-corleggy-398.notion.site/3e50f1f57c7880c0a7ede04ee00ebda4