01 / Business context
Ambiguous signals made every downstream decision less trustworthy.
Lifecycle programs were reacting to ambiguous events instead of what customers had actually done—or were ready to do next.
Walk-in intent could be mistaken for completed service. Declined work could be flattened into generic churn. A duplicated event and property environment made those distinctions harder to trust at scale.
02 / Strategic role
Turn lifecycle execution into a roadmap and data-contract problem.
I treated lifecycle messaging as a product-infrastructure problem: document the event environment, define canonical states, and connect each downstream action to defensible evidence.
The same model shaped recovery journeys, rewards, service history, NPS, and post-service communication.
03 / Product decisions
Intent is not completion
A walk-in request means the customer selected a shop and intended to visit. Rewards, NPS, and history wait for verified paid service.
Declined is not disengaged
A customer who declined work has an unresolved need. Preserve the service, shop, quote, and alternatives so the journey can reopen with context.
Canonicalize the signals
Define stable events for vehicle addition, app entry, signup, order completion, and Rewards activity; consolidate overlapping properties.
Show evidence status honestly
Separate what is live, in development, and still in backlog instead of presenting an evolving platform as a finished campaign.
04 / Evidence + learning
Verified state now determines what happens next.
Declined-services data reached production, event and property consolidation moved into development, and reliable walk-in completion remains in backlog. The result is a safer foundation for personalized journeys without overstating unfinished work.