Work
Communications work in a cabinet-level state agency: request queues, editorial production, house style, accessibility, and the documentation that lets any of it survive a change in staff. Below are the things I built, and below those, what I've come to think about building them.
Selected work
-
Rebuilding the request queue
A five-person communications office was taking requests from every division of a 400-person department by email. I built the queue that replaced it, then moved it again when the department consolidated platforms.
What happened: TODO — the number that proves it. Requests handled per month, turnaround time before and after, or the backlog that stopped existing.
-
The ECECD Briefing
A biweekly bilingual newsletter to roughly 50,000 subscribers, and the seventeen-page procedure that makes it possible for someone other than me to send it.
What happened: TODO — open rate, subscriber growth, or click performance on the sections you restructured.
-
The communications documentation set
Three documents — a style guide quick reference, a handbook, and a procedures manual — that establish how a cabinet-level department sounds and who decides.
What happened: TODO — adoption across divisions, or the recurring argument that stopped happening once the guide existed.
-
Continuity through a change in administration
A thirty-eight-page operational transition guide and five role-specific worksheets, built so a communications office can survive the January 2027 turnover without losing what it knows.
What happened: TODO — how it gets used, or what leadership did with it.
-
Establishing an accessibility practice
Contrast-compliance matrices for the full brand palette, screen reader verification across three platforms, and a phased rollout — turning a stated standard into an enforceable one.
What happened: TODO — palette combinations retired, staff trained, or issues caught before publication.