The client came to us with a tactical ask: what should we send members, and when should we send it? The work ended somewhere much bigger — a framework for deciding where personalization should happen, what business outcome it should move, and what technology had to exist to make it real.
01 · The reframeThe real problem was not email
The original brief was framed around email marketing strategy: messaging moments, cadence, content opportunities, and member lifecycle triggers. That was a reasonable place to start, but it quickly became clear that email was only one visible surface of a much larger experience.
Different stakeholder groups were using the word personalization to mean different things. CRM was thinking about triggered communications. Loyalty was thinking about member engagement. Digital teams were thinking about app surfaces. Operations was thinking about service delivery. Technology teams were thinking about platform capability. Everyone was talking about personalization, but they were not talking about the same thing.
The problem was not a lack of personalization ideas. It was the lack of a shared decision framework for deciding which ideas mattered most.
02 · Customer lensCreating the future-state customer experience
The client already had a rich set of ethnographic research describing customer behaviors, needs, and motivations. My role was not to generate more customer data — it was to transform existing understanding into a strategic model that could guide experience, personalization, and technology decisions.
To make the opportunity tangible, I developed a future-state customer journey around a realistic customer scenario: a busy working parent trying to coordinate a meal for her family at the end of a long day. Her goal was not simply to place an order. She wanted everyone in her family to get something they enjoyed with as little effort, uncertainty, and interruption as possible.
Rather than starting with channels such as email, SMS, or the mobile app, I started with a customer moment. Sally was not trying to open an email. She was trying to get dinner for her family with as little effort and uncertainty as possible.
The question shifted from “what message should we send?” to “how can personalization help Sally succeed at each stage of her experience?”
Relevance before promotion
Current-state gaps showed that personalized offers and family-relevant meals were not consistently surfaced when the need emerged.
Reduce memory work
Frequently purchased items and family preferences needed to be easier to recall, add, and adjust without placing separate follow-up orders.
Right channel, right moment
Service updates could not depend on one channel alone; timing and channel choice had to match urgency and context.
Context carries trust
When something went wrong, service recovery needed customer history and order context so resolution felt continuous, not disconnected.
03 · Research foundationHow the strategy was grounded
The client already had rich ethnographic research about members. My role was not to collect more customer data; it was to synthesize the existing evidence, stakeholder needs, and business goals into a strategy framework that could guide investment decisions.
CRM, Loyalty, Digital Product, Operations, Care, and MarTech needed one shared planning model.
Existing member research was synthesized into a future-state journey and opportunity framework.
A shared vocabulary distinguished audience, lifecycle, real-time, and predictive personalization.
The model later became part of the agency’s broader research-and-strategy offering.
04 · The frameworkConnecting experience to investment
I created a future-state customer strategy framework that organized the work around four connected layers. The point was not to produce a prettier journey map. The point was to create a planning model that could force every recommendation to connect back to a customer moment, a business outcome, and a delivery capability.
05 · The shared vocabularyA maturity model for personalization
The first thing the organization needed was a common language. I introduced a four-level personalization model that helped stakeholders distinguish between low-complexity segmentation and higher-maturity capabilities that required real-time data, platform orchestration, or predictive modeling.
This language mattered because it made investment conversations more precise. A stakeholder could no longer say, “we need personalization” and leave the execution undefined. They had to name the customer moment, the personalization level, the business outcome, and the enabling capability.
06 · Why it workedThe artifact changed the conversation
The framework allowed each stakeholder group to read the same artifact from their own perspective without breaking alignment. CRM could look at lifecycle triggers. Technology could look at enablement dependencies. Business leaders could look at where AOV, retention, or satisfaction were most likely to move. Experience teams could stay anchored to the customer journey.
07 · ImpactWhat changed for the client and the agency
08 · ReflectionThe value was not the map — it was the model
The most important thing this engagement taught me is that organizations rarely lack ideas. They lack a way to compare ideas across customer value, business impact, and execution readiness.
The artifact worked because it did more than describe a journey. It created a shared decision system. It helped stakeholders move from “what campaign should we send?” to “which customer moments deserve investment, and what capabilities do we need to deliver them?”
What started as an email strategy request became a repeatable strategy framework — one that influenced client investment direction and expanded the agency’s ability to sell higher-value research and strategy work.