AI Systems for Content at Scale: Claude Projects
I've been a one-woman production team at various points in my career, and I've nurtured direct reports as they've taken on larger and larger projects. AI is one more way I turn my solo-production studio into a scalable system. To date, I've built several Claude projects, markdown-encoded to take my raw inputs and map them to our internal audiences, producing more custom and consistent communications briefs that drive enablement and adoption — and cut the time it takes on my end.
Mapping A11y+G11n to Buyer Personas
Our Marcom org runs on a shared set of buyer personas and buying-group roles full of C-suite archetypes widely used in our highest level campaigns. I don't own that system, but I am doing my best to ensure accessibility and globalization show up there, too. I've been engaged in outreach and in mapping our A11y and G11n content and product capabilities onto those existing personas and roles — where each creates value, which buyer cares and why — to make the case that inclusion belongs in the standard process, not bolted on at the end. Integrating into this system and its processes and campaigns is still in motion.
Single Source of Truth: SharePoint
Duplicated content is where accuracy goes to die. As coverage, assets, and updates piled up across teams, I built one maintained home for all of it in SharePoint so people pull from a single source instead of each keeping their own slightly-wrong copy. The systems win isn't the page itself; it's what it prevents: version drift, dead links, and three people answering the same question three different ways. Build it once, maintain it in one place, and the team stays aligned as the work scales.
Denver University: Master's Capstone
Exploring the causes and feedback loops that contribute to resident engagement in local governments. A deep analysis of foundational factors of the digital divide and mitigation strategies to build trust in government agencies.
Agency Model: Proof of Concept
After developing collateral and campaigns for my first two years, it was clear that the existing system of production (namely, me) was unsustainable. I started thinking of my assigned divisions, peer talent, and deliverables as all the elements to an agency, and set about transforming our approach at the leadership level while also developing administrative staff in new capacities.
I trained reliable reception and admin staff in composing and distributing our email newsletters, calendaring for events, updating the website, and using DIY graphics solutions. Supervisors got experience in developing personas and brainstorming messaging and KPIs for campaigns.
This model of creation and distribution built more capacity for me to be a strategist, and our tactical producers gained valuable job experience and training to add to their list of marketable skills. This also proved a beta concept for the larger Citywide centralization effort to come.
Agency Model transition: City of Longmont
My capstone thesis laid the foundation for systemic change at the City. As the organization shifted to accommodate a growing need for communications, I had a unique opportunity to present my thoughts on how we could better reorganize our heavily siloed team into a more efficient system of production and response in community events. This model is currently on its way to reality, and our change management plan and capacity building is in stage 3 of 6 growth stages designed by me and our Communications Director.
This model represents survey data, focus group feedback, and team workshop ideas in addition to internal resource auditing and needs assessments.
Deploying the System: Sharepoint Architecture
Again, with copious amounts of design thinking, research, problem solving, and feedback, I used my software development certificate skills to provide the documentation and use case data for our Sharepoint-based work request intake system.
Based on the restrictive nature of architecting a work intake solution within the confines of Sharepoint, I had to rethink my models for how websites are built, align expectations with reality, and make adjustments based on user behavior, psychology, skills and ease with the program, and balance that with maintenance and scalability over time.
My solutions have been developed in concert with the City's chief Sharepoint Architect and input from various divisions, departments, administrative staff, leadership, and teammates.