THE MICROSOFT CHAPTER
Microsoft, in four phases
It began as a 3-month process audit and became eight years and four distinct phases. Each adding scope and responsibility; never replacing it.
NOVEMBER 2018 — FEBRUARY 2019
The Vendor
Three-month engagement, Relationship Marketing Operations
Joined Microsoft as a vendor with a single brief: figure out how Relationship Marketing Operations actually worked. In three months, built the L0-through-L3 process architecture from first principles, identified the optimization gaps the team had been operating around, and designed the KPIs the function would use to measure itself for the next two years. Hired to draw a map of the territory. The map became how the team operated. Three months in, I was asked to stay as maternity leave coverage for the Content Operations Manager. I agreed.
Backill became ownership.
FEBRUARY 2019 — APRIL 2021
Content Operations Lead
Relationship Marketing Operations
Stepped into cover the Content Operations Manager while she was out on maternity leave and stayed for two years. Ran an accessibility compliance audit across the Relationship Marketing asset library and drove rescripting noncompliant HTML for all campaigns, bringing the team and campaigns into compliance with Microsoft’s enhanced accessibility standards. Then led the operations side of the Alta/Snowbird rebrand, when Microsoft split its consumer and commercial brand into Office 365 and Microsoft 365: over 100 Relationship Marketing campaigns were updated across asset branding, customer-friendly data mapping, scripting and the reporting layer that pulled the new data through. Brand transitions of this scale usually fragment across teams. I ran this as a single coordinate operation for all Relationship Marketing campaigns.
By 2021, Microsoft had seen enough.
APRIL 2021 — JANUARY 2024
Senior Business Program Manager, Relationship Marketing Operations
Power Platform | Fabric | SI Partner Success
Converted from a vendor to full-time employee in April 2021 after a Microsoft Super Hiring Day. I walked out believing I had bombed the interview. The offer call came the next morning. The hiring manager who made that call has remained a trusted working partner in the years since.
The job: lead three program pods (Power Platform, Fabric, and SI Partner Success, the only non-standard pod the team supported), translating marketing strategy into technical campaign design at 13 to 15 campaign launches per month per pod. Beyond the work, I carried multiple cross-business initiatives in parallel.
European Union Data Boundary (EUDB)
Drove the EUDB operations across every Relationship Marketing email and in-product campaign, aligning the storage of tenant-level data with regulatory requirements for the European Union and protecting Microsoft’s compliance posture across an entire customer engagement surface.
~794 campaign scripts
New Commerce
Drove the New Commerce migration when Microsoft restructured tenant agreements from multi-invoice purchases to single-invoice consolidation, rescripting every Relationship Marketing campaign whose targeting or personalization logic relied on purchase or tenure data. The change quietly broke campaigns across the function. I found them, fixed them, and rewrote the targeting logic the campaigns ran on.
Email Deliverability v-team
Sat on the cross-functional v-team chartered with improving inbox placement at Microsoft scale, working through deliverability triage and conversion solutioning across the Relationship Marketing engine.
A new operating model
Designed, piloted, and rolled out a new operating model that gave every business area that adopted it faster go-to-market velocity, higher campaign throughput, and a steady pipeline of capability and feature requirements for future work. The model became the template by which new pods onboarded.
The pattern
By the end of this period, I had become the operations lead managing cross-functional complex and novel work. My unfair advantage was fluency across the full pipeline: I understood what data was readily available, how it could be used in targeting and personalization, how the delivery engines worked, and how all of those pieces came together to produce metrics worth reviewing. When I had command of every aspect of Relationship Marketing Operations, I went looking for a people management role. It was time to build others.
New team, new function, same approach.
JANUARY 2024 — MAY 2026
Group Manager →Director, MarTech Enablement and Operations
MarTech, Operations and AI Center of Excellence
Moved to people management in January 2024, new to the events marketing space and asked to ramp into Microsoft’s most demanding events quarter (April through June) in my first months on the job. Over two years, I navigated successive organizational realignments, each adding scope rather than replacing it. By my final period, my remit had expanded from marketing capabilities and execution operations to also include event capabilities and full-scale event platform operations: three pillars that would typically span three distinct Director-level teams. Built and led a hybrid team of twenty-one direct reports across full-time employees and vendor partners, designed to operated autonomously beyond my tenure.
The Real-Time Marketing Migration
Took ownership of the largest customer-facing platform migration in my org’s history: 1,228 active events, 3,819 content blocks, and 619,030 live registrations migrated from Dynamics 365 Outbound Marketing to Real-Time Marketing across four successive waves and five weeks of 24/7 coverage. Designed the governance framework from first principles across Engineering, Operations, and Data and Analytics, and ran a wave-based rollout validated against each cohort before proceeding. The program operated at red status for four consecutive weeks; across that window I ran 45 daily stand-ups and authored roughly 80 twice-daily executive updates that became the single source of truth my leadership chain relied on for decision-making. Personally drove root-cause analysis on a production-only API defect that blanked registration pages for events with executive speakers, identifying why the issue had not surfaced in UAT or PPE and coordinating the fix through resolution. All four waves complete and successful, with continuity of customer experience preserved throughout.
Data integrity stewardship
Served as the single operational owner for seller-impacting data incidents that fell between organizational boundaries. During the AI Tour, personally diagnosed that null values passing through customer data later were overwriting Marketo language preferences, causing Hong Kong customers who had selected English to receive communications in Traditional Chinese. Led the cross-functional war room when approximately 2,000 attendees at the Chicago AI Tour stop were incorrectly flagged as no-shows, surfacing an unknown data flow issue resulting from improper platform integration. Restored 86K erroneous opt-out signals caused by the same platform integration.
System health, reframed by data
Initiated a defensible bug v. non-bug ticket classification framework when undifferentiated platform-health volumes were driving inaccurate accountability narratives. Structured month-level analysis of 92 representative tickets reclassified 63 (69%) as non-bugs: change requests, configuration errors, training gaps, or items with root cause outside of the marketing technology org being held responsible. The methodology was peer-validated and redirected accountability where the data informed rather than where assumption defaulted. Embedded the practice into a weekly System Health rhythm, where it now operated continuously rather than as a one-time exercise.
Operating model and people
During my leader’s extended medical leave in 2024, I identified that team funding had been allocated in ways that left vendor engagements vulnerable if specific stakeholder motions were deprecated. Designed a budgeting structure that protects team scope against single-program loss and created a safely-budgetable pattern for future fiscal years. Co-authored the Innovation Capacity Playbook for Microsoft’s MarTech Extended Leadership Team and presented it to the full manager community in February 2026 Lightning Shares. Thoughtout the period: delegated to develop, shieled the team under pressure, modeled accountability through evidence rather than narrative, and build a team with a designed structure to outlast my tenure.