Lifecycle messaging for a delivery platform

How I turned one-off campaigns into a messaging system that [result in one line, e.g. cut production time by about a third].

Role
CRM designer, lead on visual and message design
Team
[CRM, Ops, Product, Data]
Timeline
[Month 2025 – Month 2026]
Tools
Figma, [CRM platform], [analytics tool]
Replace with hero image: the system at a glance

Context

[Two or three sentences. Who the audience is, what messages they receive, and why those messages matter to the business. Keep platform specifics light.]

Problem

[What wasn’t working, in user terms first, business terms second. One sharp sentence beats a paragraph.]

[The insight that reframed the problem, written as one sentence.]

My role

[What you did versus what the team did. Be precise: “I led the template system and ran the tests; Data defined the segments.”]

Research and data

[Which signals you used: campaign metrics, Ops feedback, support tickets, interviews. What you learned from them.]

Replace with: journey map or segment overview
[Caption that says what to notice, not what it is.]

Constraints

[No product ownership: messages had to work around a product you couldn’t change. Name the other limits too: channels, character counts, localisation, tooling.]

Decisions and iterations

[Two or three key decisions. For each: the options, what you chose, and why.]

Before
[Before: what was wrong]
After
[After: what changed and why]

[What you tested, what surprised you, what you changed.]

Outcome

[One sentence framing the results. Use ranges or percentages, not absolute numbers.]

[+X%][open or click rate]
[~X%][less production time]
[X][templates adopted by other teams]

Some details are confidential. Figures are rounded and screens are recreated. I’m happy to walk through the full version in a conversation.

Learnings

[What you’d do differently, and how this carries into product design: segmentation, systems thinking, experimentation, working with data.]