Work Samples
Plans that people use
A selection of deliverables across change management, internal comms, and ERP implementations.
AI Tools & Process Efficiency
Copilot for Communications
How I use AI to build faster, more consistent communications infrastructure — not just to draft content, but to create systems that scale.
Pre-Launch Communications Tracking System
For the WAM Release 2 deployment communications effort, used Copilot to consolidate scattered information from communication plans, draft communications, review comments, process notes, Teams discussions, and broadcast procedures into a single, structured workflow. The goal wasn't just to save time — it was to build a repeatable system that would carry forward into future deployments and hypercare.
What I built with Copilot
- Comprehensive communications process — draft creation through final distribution
- Communications tracker with due dates, reviewers, statuses, links, and notes
- Standardized Broadcast Sending Checklist
- SME feedback logs and revision documentation
- Approval routing guidance tied to the deployment schedule
- SharePoint PDF publishing and link-testing procedures
- Reusable templates for review requests, feedback logs, and communication tracking
Business benefits
- Reduced risk of missed approvals, incorrect distribution lists, or broken SharePoint links
- Standardized communication development and distribution across the program
- Centralized requirements, decisions, and history into a single reference source
- Improved onboarding and handoff capability through documented, repeatable processes
- Reusable operating model for future WAM deployment and hypercare communications
Time savings by activity
| Activity | Saved |
|---|---|
| Building comms process documentation | ~3 hrs |
| Creating communication tracker | ~1 hr |
| Reviewing deployment schedule | ~50 min |
| Consolidating Teams notes | ~50 min |
| Documenting approval workflows | ~50 min |
| Broadcast sending checklist | ~45 min |
| SME feedback logs (per communication) | ~25 min each |
M&A Standard Operating Procedures
Communication SOPs developed for merger and acquisition scenarios.
Core & Main Acquisition Release
External news release announcing the close of Core & Main’s acquisition of Canada Waterworks, written for a publicly traded company under legal and investor review. Issued Sept. 30, 2025.
ERP Rollout Communication Plan (ADKAR)
A composite communication plan built on the Prosci ADKAR model, drawn from experience leading change communications across multiple ERP and enterprise system rollouts. Covers persona-based messaging, a change champion network, go-live hypercare, and post-launch reinforcement.
LEAP Dictionary: Mincron-to-D365
A quick-reference translation tool built for the Core & Main LEAP rollout, mapping familiar Mincron terms to their new D365 equivalents so branch teams could adopt new system language faster.
Core & Main
ERP Communications Suite
A set of materials produced for the Core & Main ERP pilot — from executive-facing letters and pilot announcements to employee reference tools and recognition program assets. Company name and identifying details have been modified or removed.
ERP Pilot Announcement
Internal announcement used to launch the Core & Main ERP pilot program, introducing the initiative to branch teams and explaining what to expect.
Letter to Leaders
A leader-directed communication piece setting expectations before the ERP pilot launched — giving managers the context they needed to answer questions on the floor before employees started asking them.
ERP Employee Brochure Series
Four-part brochure series built for different phases of the ERP rollout — each one aimed at a specific audience moment: awareness, understanding, readiness, and reinforcement. Designed to be handed out at branch visits and posted in break rooms.
Leader Guide
A visual leader reference guide produced for the ERP pilot — gave managers a single-page resource covering key messages, FAQs, and where to direct employees who had questions.
ERP Terminology Reference Card
A quick-reference glossary built so branch employees could quickly map familiar terms to new system language — reducing confusion and support tickets during the go-live period.
Internal Communications
Additional Work Samples
Town Hall & Strategic Rollout Communication Toolkit
Every message a leader delivers on the factory floor either lands or it doesn’t, so the goal was one script that worked the same in a five-person huddle and an 1,800-person auditorium. Planned logistics, scripts, and content for town halls (500+ attendees), strategic rollouts (1,800+ attendees), and virtual quarterly meetings (1,200+ attendees), reaching 80% attendance through data-driven engagement strategies. This sample shows the talking points structure, the anticipated questions leaders were prepped on, and the delivery notes used to keep the message the same in every room.
Brand Voice & Tone Guide
A style guide only matters if people open it, so this one trades long explanations for short rules and one real before-and-after rewrite. Composite example built from internal communications style work across more than one organization, not tied to a single employer. Includes voice principles, do’s and don’ts, and a rewritten memo showing the same information in half the words.
Communications & Change Impact Snapshot
Numbers don’t replace the work, but they prove it happened, so this snapshot pulls the reach and adoption results from programs described elsewhere in this portfolio onto one page. Includes adoption, engagement, and attendance metrics across ERP rollouts, an IoT platform launch, event production, and federal communications work. Every figure ties back to a specific program, not a projection.
34 Days: Leading Communications Through Crisis
Thirty-four days of labor uncertainty affected 5,000+ employees at John Deere’s Waterloo Works, and someone had to keep the message consistent while conditions changed daily. This interactive timeline walks through all three contract votes alongside the communications actions taken at each stage, from continuity planning a year before the strike to the return-to-work messaging that followed ratification.