Microsoft, in four phases.

The Vendor

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, she was asked to stay as the backfill for the Content Operations Manager who was leaving. She agreed.

Content Operations Lead

Stepped into the backfill role and stayed in it for two years. Ran an accessibility compliance audit across the Relationship Marketing asset library and rescripted the noncompliant HTML herself, work no one had asked her to do that brought the team into compliance with Microsoft's accessibility standards. Then led the operations side of the Alta/Snowbird program when Microsoft split its commercial brand into Office 365 and Microsoft 365: over 100 Relationship Marketing campaigns 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. She ran this one as a single coordinated operation.

Senior Business Program Manager, Relationship Marketing Operations

"Hard project, give it to Tiffany. Never been done before, give it to Tiffany."

Converted from vendor to full-time employee in April 2021 after a Microsoft Super Hiring Day she walked out of believing she 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 across the three areas. Beyond the campaign work, she carried multiple cross-business initiatives in parallel.

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.

European Union Data Boundary (EUDB)

Drove the EUDB rescripting effort across every Relationship Marketing email and every 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.

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. She found them, fixed them, and rebuilt the targeting logic the campaigns ran on.

The pattern

By the end of this period she had become the operations lead the team handed the work no one else could solve. Her unfair advantage was fluency across the full pipeline: she understood what data was 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 she had mastered every aspect of Relationship Marketing Operations, she went looking for a people management role.

Group Manager → Director, MarTech Enablement and Operations

Moved to people management in January 2024, new to the events space and asked to ramp into Microsoft's most demanding events quarter (April through June) in her first months on the job. Over two years she navigated successive organizational realignments, each adding scope rather than replacing it. By her final Connect period her 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 operate autonomously beyond her tenure.

The RTM migration

Took ownership of the largest platform migration in the function's recent history when no other operational DRI existed: 1,228 live events, 3,819 content blocks, and 619,030 customer registrations migrated from Dynamics 365 Outbound Marketing to Real-Time Marketing across four successive waves. 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 she ran 45 daily stand-ups and authored roughly 80 twice-daily executive updates that became the single source of truth her 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 to 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 the customer data layer 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. Resolved 18 of 19 tracked issues across the global Tour data flow within three weeks, with no in-flight events disrupted. Restored seller lead visibility for NRF Rethink Retail by tracing three event records incorrectly classified as digital instead of in-person, unblocking field post-event re-engagement and earning direct field acknowledgment.

System health, reframed by data

Independently initiated a defensible bug-versus-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 the engineering org being held responsible. The methodology was peer-validated and redirected accountability where the data pointed rather than where assumption defaulted. Embedded the practice into the weekly System Health rhythm, where it now operates continuously rather than as a one-time exercise.

Operating model and people

During her manager's extended medical leave in 2024, 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 creates 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 at the February 2026 Lightning Shares. Throughout the period: delegated to develop, shielded the team under pressure, modeled accountability through evidence rather than narrative, and built the team to outlast her tenure.