CASES IN POINT
ORG & CULTURE DESIGN 01 | MARKETING OPERATIONS
Defining a new role in the marketing technology function
role design · competency modeling · career architecture · team scalability
Work in the marketing technology function was split across three roles: (1) a business program manager who owned the business layer and served as connective tissue to business stakeholders, (2) a marketing technologist who owned the build, and (3) a capability lead who owned feature and capability development and change management.
The seams between them created diffuse accountability, institutional knowledge, vendor dependency, and lossy handoffs.
Staffing three specialists against every program was neither affordable nor scalable.
SITUATION
I consolidated the three roles into a single unified role with end-to-end ownership of a program or domain.
I built a competency model that defined the skills the role required, established multiple levels mapped to the company's leveling framework, and preserved genuine specialization where delivery coordination still called for it.
I made the scope legible through lifecycle ownership maps and role-clarity artifacts.
APPROACH
End-to-end ownership replaced diffuse accountability.
The team grew more resilient, because managers could flex across programs rather than being locked to a single specialty.
Role clarity improved onboarding and calibration, and gave the team a defined career path for the first time.
IMPACT
ORG & CULTURE DESIGN 02 | MARKETING OPERATIONS
The Clean Slate Initiative: Removing Silos for Agility
organizational change · silo removal · cross-training · capacity flexibility
The team was organized into three heavily siloed verticals.
Prestige dynamics had calcified between them, no cross-vertical coverage was possible, and work surged unevenly with no way to move capacity to where it was needed.
Individual contributors had grown so siloed that they leaned on vendors rather than owning the work themselves.
SITUATION
I gave the team six months to cross-train voluntarily. When that effort did not take hold, I implemented a clean slate: every assignment was wiped and every person reassigned to a new vertical.
Success now depended on cross-training, so cross-training happened.
I deliberately mixed the teams to dissolve the prestige dynamics, and people who were invested in status rather than the work self-selected out.
APPROACH
The silos dissolved.
The team became genuinely agile on capacity, able to surge wherever the work was heaviest.
Technical capability moved in-house and off vendors.
The team's composition strengthened through the natural departure of status-motivated individuals.
IMPACT
ORG & CULTURE DESIGN 03 | MARKETING OPERATIONS
The Three Pillar Model: Structuring ownership for scale
operating model design · ownership & accountability · intake governance · org scaling
A reorg drastically increased my scope, adding planning & enablement and platform operations to my existing scope of program management and execution operations.
Quickly, I realized a new operating model was necessary to scale across the team for the ever-changing demands of the business.
Organizing by work type had never mapped cleanly to functional need.
Execution staff absorbed platform work because no one owned that layer, planning fell through the cracks, and unplanned intake landed on the execution team with no front door.
SITUATION
I designed a three-pillar functional operating model: a planning and enablement function to serve as the front door and connective layer, an experience operations function to own hands-on delivery, and a platform operations function to own platform health, configuration, and governance.
I sequenced the ownership transitions to operational reality rather than forcing a single cutover, holding certain handoffs until dependent migrations were complete.
APPROACH
Every layer gained an explicit owner.
The model scaled with the business because it was organized by function rather than work type.
Intake was governed through a defined front door.
Several team members stepped up into pillar leadership.
IMPACT
ORG & CULTURE DESIGN 04 | MARKETING OPERATIONS
The Org Chart Merged. The Culture Didn’t.
post-merger integration · facilitation · culture building · behavioral standards · expectation clarity
A reorganization merged two teams with a history of friction into a single group, adding platform operations and planning to an existing management team.
The org chart combined them; the culture did not.
There were two rival camps, no shared standards, no shared definition of success, and no common role identity.
SITUATION
I designed and facilitated an alignment session built around a neutral shared theme that neither team owned, using a light touch of humor to let hard messages land.
It opened with a compact I made to the team, setting expectations of myself before setting them of anyone else.
From there it moved through a set of non-negotiable operating principles covering psychological safety, ownership, delivery standards, and communication, then introduced the unified role and its competency model, and closed with concrete individual actions tied to each person's development plan.
APPROACH
Two rival cultures left with one shared set of expectations, established in a single session.
Culture was made explicit and enforceable through behavioral standards rather than left to chance.
Status dynamics were defused through a neutral frame and a shared role identity.
The session set the cultural foundation the later structural reorganization was built on.
IMPACT
TECH MGMT 01 | MARKETING OPERATIONS
The critically delayed platform migration no one thought possible
platform migration · crisis recovery · executive escalation & management · cross-functional leadership
A business-critical event management platform had been built on a CRM marketing module that was set for deprecation, with a hard removal date.
Three-quarters of the platform was custom-wired to infrastructure that could be removed without warning.
The migration had been known to be necessary for roughly two years, but was repeatedly deprioritized against competing demands and stalled even after it was funded.
When I inherited the scope, the platform was already months past its deprecation deadline.
To my knowledge, it was the first migration of its kind the organization had ever attempted, with immediate customer-facing exposure if it broke.
SITUATION
I moved first into triage: assessing the true state of the platform, convening stakeholders who had been scattered across the effort, and escalating for executive visibility.
I converted a stalled initiative into an owned, actively driven program with a clear owner and a defined execution framework, and drove the cross-functional alignment the migration required.
When a cloud update later retired the underlying module and the platform went down, the groundwork was already laid, so the outage landed on a migration that was already in motion.
I led the emergency rebuild under direct executive scrutiny.
APPROACH
A potential catastrophe became a controlled recovery.
More than a thousand events were migrated off the dead module.
A risk that had been stalled for two years was finally executed.
The organization completed the first platform migration of its kind in its history and established a repeatable playbook for the next one.
IMPACT
TECH MGMT 02 | MARKETING OPERATIONS
The cost of skipping governance & best practices in tech integration
crisis management · data governance · operations management · cross-functional alignment · risk management · data quality
A net new event platform was integrated with the marketing & sales tech stack without following established procedure.
There was no business requirements document, no cross-functional planning, and critical stakeholders — specifically the marketing technology and operations team — were never consulted.
The integration also introduced a novel data architecture that had never been tested internally.
When three events executed before the problem was discovered, the data flow was fundamentally broken: post-event customer communications went to wrong recipients, sellers received leads they should never have received, and the marketing and sales organizations had no way to know which data was reliable.
The root cause was an absence of governance — engineering teams proceeded without validation, testing, or expert input.
SITUATION
I immediately stood up a war room and brought together the appropriate cross-functional teams.
When data and event engineering teams did not show up to take ownership, my team became the operational bridge.
I designed an interim operating model, collaborating with sellers and signal teams, to contain the damage while the underlying integration was corrected.
The model worked as follows: after each event, my team pulled all available data sources and compared them to identify anomalies.
They then raised alerts to data and event engineering with specific findings and remediation requirements, creating visibility and accountability.
Simultaneously, they coordinated with the integrated marketing team to time post-event customer communications for when cleaned data was available.
We also validated lead distribution with the sales team, manually verifying that sellers received only the leads they should have.
My team maintained this operational burden across the entire correction cycle while data and event engineering worked through their backlog to fix the root cause.
APPROACH
The interim operating model prevented further downstream damage to customer experience and sales credibility.
While data and event engineering took six months to fully remediate the integration error, my team's manual processes ensured that post-event marketing cadences executed accurately and sales received validated leads.
The cost of that operational lift — six months of manual data reconciliation, anomaly identification, and cross-team coordination — became a visible measure of the cost of bypassing governance.
Beyond the immediate crisis, this situation created a structural case for why intake, testing, and cross-functional alignment matter: the alternative is six months of firefighting by the people who should have been consulted at the start.
IMPACT
TECH MGMT 03 | MARKETING OPERATIONS
Governing the URL Tag: Building Durable Channel Attribution
data governance · attribution modeling · marketing operations · measurement systems
After our fall flagship conference closed, stakeholders asked a question we could not answer: where did registrations actually come from, and where should the next dollar go?
We had registration totals and we had channel-level activity, but no way to connect the two.
The gap was not analytical. It was operational.
URLs were being created ad hoc across every channel with no shared tagging standard, no ownership, and no monitoring.
Any attribution model built on that data would have inherited its inconsistency.
SITUATION
I owned operationalizing channel attribution, and built the model alongside my execution operations lead.
The foundation was URL and tag governance. My team took single-point ownership of creation, governance, maintenance, and monitoring for every trackable link across every integrated channel: social and influencer placements, email, web, partner, and paid.
The technical work was the harder half. Several platforms in our stack auto-appended their own parameters to outbound URLs, which corrupted the tags we were setting deliberately. Our social publishing platform and our marketing automation platform both did this in different ways.
I worked through each to identify the behavior, then designed around it so our governed tags survived the handoff intact rather than getting overwritten or duplicated.
Privacy constraints shaped the model as much as the tooling did. We could not deanonymize significant portions of the journey and I was not willing to publish attribution that implied otherwise.
So we scoped the model to what we could defend: first touch and last touch, with a weighting approach that treated first touch without registration and last touch with registration as distinct signals. That gave stakeholders a defensible stack rank of channel contribution without overclaiming what the data could support.
Once the model held, my lead and I trained every marketer, builder, and operator on the tagging standard and the governance process.
We then built the reporting layer with our analytics team so the output reached stakeholders in a consistent form.
APPROACH
Stakeholders could see channel performance for the first time and could rank where registration volume was actually coming from. That informed budget allocation directly.
The model outlasted the event it was built for. It became the standard for channel attribution across our event portfolio, flagship and scale alike, because the discipline lives at the point of URL creation rather than in downstream reconciliation.
Enforcing consistency at the source is what made it durable.
Anything built to clean up messy data after the fact would have degraded the first time a new channel or platform entered the mix.
IMPACT
OPERATIONS 01 | MARKETING OPERATIONS
Implementing the EU Data Boundary commitment in post-sales campaigns
data residency · program management · cross-org coordination · compliance delivery
As acting lead business program manager, I coordinated a cross-organization effort to bring post-sales marketing campaigns into compliance with the company's regional data residency and privacy commitments.
The scope did not stay still: what began as a narrow regional concern expanded to cover the entire campaign estate regardless of target market, against a fixed and critical deadline.
The work also had to be coordinated with several large parallel efforts, including a platform migration and the standup of a new trust boundary-compliant sending instance, while upstream data changes kept moving underneath the plan.
SITUATION
I built and drove a single implementation plan for rolling out the required segmentation changes across a campaign estate spanning more than a dozen product lines, and shared it broadly so every team executed from one source of truth.
I built a bi-directional mapping of data streams to campaigns so we could rapidly assess impact whenever upstream changes hit, an asset that paid dividends repeatedly.
I led enablement across the individual campaign teams to find where routine work and compliance work intersected, so the effort closed the gap without creating new technical debt.
I ran a weekly operating rhythm, kept leadership current on status and risk, escalated judiciously, and owned incident management for every blocker.
APPROACH
The implementation was completed on time, against a fixed deadline and a scope that expanded to the full campaign estate of 240+ email and in-product marketing campaigns.
It landed with minimal data issues despite touching a dozen-plus product lines and many data streams, and earned direct recognition from the upstream data partners the effort depended on.
By deliberately finding the intersections between routine and compliance work, it closed the gap without leaving new debt behind, and the data-stream mapping became a reusable asset well past the original deadline.
IMPACT
OPERATIONS 02 | MARKETING OPERATIONS
Recovering erroneous opt-outs when data goes rogue
data integrity · consent management · root-cause analysis · cross-system reconciliation
The enterprise tracks, for every customer, whether they have opted in to receive communications on a given topic, through a central consent and preference system.
A newly introduced event platform was integrated into the marketing technology stack without following established data-integration practices, and as a result began transmitting incorrect opt-out signals into the consent system.
Tens of thousands of contacts were marked as opted out of communications they had never actually declined.
This arrived while the organization was already struggling to reach its eligible audience, so the erroneous suppression both compounded a contactability problem and created a consent-integrity exposure.
SITUATION
I owned the recovery end to end.
The task was to determine, for each affected contact, whether they had genuinely opted out before the faulty signal and should stay suppressed, or had been wrongly suppressed and needed to be restored.
I did this by reconciling four separate datasets spanning more than a hundred thousand customer records, tracing each contact's true consent state prior to the erroneous signal.
The work was painstaking because the stakes ran both ways: restore someone who genuinely opted out and you contact a person who did not consent; leave someone suppressed who did consent and you block communications they wanted.
I spent two weeks in that reconciliation with privacy at my side the entire way.
APPROACH
Every erroneously suppressed contact was identified and restored to their correct opt-in state, a one hundred percent recovery.
Consent integrity was re-established.
Tens of thousands of contacts returned to the eligible audience, easing the strain on outbound reach.
The scale of the failure made the cost of skipping integration discipline concrete, and informed how new platforms were brought into the stack afterward.
IMPACT
OPERATIONS 03 | MARKETING OPERATIONS
From Bottleneck to Factory: Redesigning Intake to Enable Campaign Velocity
marketing operations · systems thinking · process & operating model design · campaign management · cross-functional alignment
The relationship marketing post-sales operating model accepted all campaign requests without first validating whether the underlying data or platform capabilities existed to support them.
This created cascading problems: inability to resource requests appropriately, no forecasting clarity, and no systematic way to surface capability gaps to the data engineering and platform engineering teams.
The result was a bottleneck disguised as a process — requests piled up, priorities became murky, and the organization couldn't distinguish between "this campaign is hard to execute" and "this campaign is impossible with our current stack."
New capabilities and features had no intake mechanism, so even when engineering teams built something valuable, marketing didn't know about it or didn't know how to use it.
SITUATION
I designed a two-path intake and prioritization model anchored on a capability assessment process.
All incoming campaign requests — regardless of time horizon (monthly, quarterly, or fiscal half) — went to a single intake gate.
I personally reviewed each request to determine viability based on existing data and platform capabilities. For requests I could assess independently, I routed them directly: viable requests flowed to campaign prioritization and execution; non-viable requests went to a capability path.
For requests requiring cross-functional assessment, I hosted a capability assessment call that brought together data engineering, platform engineering, marketers, builders, and analysts.
In that meeting, I collectively determined whether the ask was viable given current capabilities and what the business was trying to achieve.
Non-viable requests were then routed to data and platform engineering backlogs during semester planning cycles, creating a continuous feedback loop where new capabilities and features rolled back into the marketing campaign pipeline as they shipped. Viable requests moved immediately to execution.
APPROACH
The two-path model enabled me to rebuild the entire operating model across all product lines, not just my own.
Campaigns executed increased dramatically: my personal output alone grew from thirty to thirty-five campaigns per year to over seventy-four — more than doubling your throughput.
The marketing team doubled overall campaign volume while maintaining quality and execution fidelity.
The model created a virtuous cycle: as new capabilities shipped from engineering, they fed back into the marketing pipeline, continuously expanding what was possible.
Once the operating model was in full swing, the marketers ran out of campaign ideas — the bottleneck shifted from execution back to ideation, suggesting the true ceiling for campaign velocity was constrained only by business creativity, not operational capability.
IMPACT
MARKETING STRATEGY 01 | MARKETING OPERATIONS
The Multi-CTA Model: Turning a database constraint into a global standard
marketing strategy · campaign optimization · email marketing · demand generation · deliverability · multi-region execution
The email marketing database for pre-sales and events faced a critical contactability challenge. High email volume to the same audience was degrading deliverability and reducing the ability to reach prospects at scale across the Americas, APAC, and EMEA regions.
Simultaneously, the team needed to maintain registration goals for regional events — a tension that made reducing send volume feel risky from a business perspective.
The core problem was structural: single call-to-action emails meant more total sends per leads, compounding deliverability issues while stakeholders remained skeptical that bundling content could preserve conversation outcomes.
SITUATION
Rather than accept the contactability v. conversion tradeoff, my team piloted a multi call-to-action email model.
The approach grouped thematically related content into single emails, reducing overall send frequency while preserving variety and relevance. We also experimented with call-to-action positioning in the emails to test whether primacy had any impact on registration behavior.
The pilot was designed to not only measure deliverability and contactability improvements, but also engagement metrics, specifically open rates, click-through rates, and overall campaign performance, to directly test the stakeholder concern that registration goals would suffer.
The pilot ran for approximately six months across all three regions, Americas, APA, and EMEA, creating a distributed test bed that would validate the model’s robustness across geographies.
APPROACH
The multi call to action approach increased open rates from 28% to ~40%, a significant lift, while achieving and exceeding registration goals across all three regions.
The success was consistent enough that the model was templatsized and later became a field marketing requirement for event marketing campaigns.
This shifted the constraint from a database hygiene limitation into a scalable, repeatable process that allowed the team to reach more leads more effectively without increasing send volume.
IMPACT
MARKETING STRATEGY 02 | MARKETING OPERATIONS
When nurture campaigns don’t nurture
lifecycle marketing · customer journey analysis · data-informed strategy · stakeholder influence
When an attendee registers for an event, they are tagged with a marketing motion aligned to that event, and each motion is meant to trigger a specific nurture email series: a first email within a day of the tag, then one a week on a set cadence.
On paper the experience was clean. In practice it had decoupled from its design.
The marketing motion nurture series had never been built for an event audience, no bridge connected event registration to the series that followed, and the creative was dated.
There was reason to suspect the experience was broken operationally, not just aesthetically, and the finding would also inform a broader case to move off the legacy marketing automation platform.
SITUATION
I traced the full journey from registration tag through eligibility to delivery and cadence, and found a systems failure at scale: only a low single-digit percentage of event attendees were receiving the nurture experience as designed, while the overwhelming majority received nothing as intended.
The root cause was not the nurture logic but the platform itself, which had been extended through custom integrations to the point where it no longer performed reliably.
I compiled the analysis for event and marketing leadership with a direct message: what you believe is happening to your attendees is not what is happening.
Then I offered three paths, in order of uplift: (1) a bridge email to give attendees context for the series they were about to receive; (2) event-specific nurture series tailored to the event and motion rather than the generic pre-sales default; and (3) a modular approach that would let a small set of composable templates flex across events, which the current over-engineered platform could not support and which strengthened the case to migrate.
APPROACH
The data on the failure rate made the case for change undeniable, and leadership approved piloting the event-specific strategy.
The entire post-event nurture architecture is now being reconsidered on those recommendations.
Early pilot results show a significant engagement lift, with open rates in the mid-to-upper forty percent range.
And by demonstrating both the operational failure and the strategic ceiling the legacy platform imposed, the analysis became a key pillar in the broader platform migration argument.
IMPACT
MARKETING STRATEGY 03 | MARKETING OPERATIONS
License Assignment Isn’t Permission to Email: Rebuilding End-User Strategy for Tenanted Products
marketing strategy · enterprise governance · campaign design · customer escalation · risk management · stakeholder management
The product pod I supported launched two new end-user marketing campaigns for a pair of adjacent low-code products.
The trigger was license assignment: when an organization assigned a license to an end user, that user automatically entered an onboarding campaign built to drive product adoption based on user behavior.
Tenant admins could disable end-user marketing in their admin center, and this customer had left it enabled.
A strategic enterprise account had just purchased over 280,000 licenses across both products as part of a planned replacement of an incumbent competitor tool. They had an internal change management plan and a communications sequence they intended to run on their own timeline. Our campaign fired first.
Their employees learned about the platform change from us before their own leadership had announced it. The escalation came in within days.
SITUATION
I suppressed the account from the first product's end-user campaign immediately.
The second product's campaign was built on identical logic with the same trigger and the same audience, and it was not caught in the initial suppression.
When the customer assigned the second set of licenses, their end users were emailed again.
The account then put the full 280,000 license purchase on the table: another email to their employees and they would pull it.
I owned the remediation from that point. I closed the gap on the second campaign, audited every other campaign built on license-assignment triggers for the same exposure, and established suppression that operated at the tenant level rather than campaign by campaign.
I then led the cross-functional working team on the underlying strategy question, which was larger than one account: should we be emailing end users at all about a rollout the tenant organization is orchestrating itself?
The existing model treated license assignment as marketing permission. That assumption had never been examined.
APPROACH
The account relationship held and the license purchase stayed in place. More durably, the strategy work changed the model.
We moved away from license assignment as an automatic campaign trigger and built conditional logic that recognized tenant-driven deployments and deferred to the customer's own change management timeline.
That became the standard for subsequent end-user campaigns tied to license events, and it protected enterprise accounts from having their internal communications preempted by our automation.
Suppression architecture also shifted from campaign-scoped to tenant-scoped, which closed the structural gap that allowed the second incident.
IMPACT