I once had to fight for a quarter-long blackout on my lifecycle flows. No new programs, no new campaigns, just maintenance on what we’d already shipped. The reaction was typically the same: skepticism. It looked like I was trying to take it easy. Nobody really understood the technical debt that constant net-new shipping was quietly stacking up. The blackout got debated. It never fully landed or was sandwiched between other initiatives. That fight is one of the exact conditions lifecycle stalls under. But it’s not where lifecycle actually breaks. Lifecycle breaks at the moment where action is required and there’s no visibility or control to take it.
At Equifax, I saw what that looked like up close.
We had a high volume of users coming in to run verifications: employment history, income checks, things tied to real-world decisions for their customers like leasing an apartment or financing a car. They weren’t browsing. They had an immediate need. The problem was the system didn’t match that urgency.
Before they could run a verification, they had to go through credentialing: a physical address, a secure room with a lockable door, permissible purpose established, multiple steps, some of which required back-and-forth. We built lifecycle communications to set expectations. We told them it could take 3–4 days.
But once they entered credentialing, we lost visibility and control. There were no usable signals, no state-based triggers we could act on. If someone provided an address but missed the secure room requirement, we couldn’t see it, couldn’t trigger anything off it, couldn’t nudge them at the moment they got stuck.
At that point, the journey shifted out of lifecycle and into Service Cloud tickets and human follow-ups.
And that’s where it broke.
A user who needed verification before their renter’s Friday move-in could be sitting in credentialing the following week, sometimes longer. The process could take hours. In reality, it often stretched into days, sometimes weeks. Not because the system was slow, but because every next step depended on the user to act, and on a human team to follow up when they didn’t, and we had no way to intervene in real time between those handoffs.
So what we saw was this: high intent at entry, immediate need, then a gap, then silence. There was often no usage decay, because there was never any usage to begin with.
By the time we could act, the moment had already passed.
This is where lifecycle systems start to break down.
A lot of teams focus on connecting their data and surfacing better lifecycle signals, and that work matters. But once the data is connected, the problem doesn’t disappear, it changes shape. Instead of not knowing what to do, you know exactly what to do and you just can’t do it fast enough.
But lifecycle isn’t failing in those environments. It’s stalling.
It usually starts strong. You build a few good programs from friction points you can act on quickly, they work, you see early wins, metrics move. Then the asks pile up: more programs, more campaigns, more stakeholders. Maintenance doesn’t fit into how marketing work gets planned, everything ladders up to OKRs and forward motion. So instead of stopping to fix what’s already there, teams patch. And that patching creates breakage, breakage creates triage, triage eats the team’s capacity, and a team at reduced capacity moves slower than the customer. The original programs, the ones that were tight and reliable, slowly turn into a house of cards.
And eventually, the execution slows below the speed of customer behavior.
That’s exactly what we were dealing with in credentialing. We had the signals on entry, we knew where users were dropping, but we couldn’t act at the moment it mattered, because we didn’t have visibility or control in that part of the user’s journey.
The fix wasn’t more emails. It was changing the surface.
We pushed toward bringing users into the platform earlier, what we called an “entry foyer.” Instead of completing credentialing entirely outside the experience, users would get immediate access to the platform but with a limited view, a tracker that showed exactly where they stood and what was left to complete.
Think of it like a Domino’s Pizza tracker.
The whole point was better control: show progress in real time, surface what’s missing, give lifecycle a place to act, create a feedback loop inside the experience.
The full version never shipped, but it surfaced what the system actually needed.
That’s the shift. Lifecycle doesn’t just need better signals, it needs control over the moment where those signals matter.
Because the real problem isn’t that teams don’t know what to do. It’s that they’re expected to maintain the system, build what’s next, and act in real time, all at the same time. Without a way to separate those, or a system that allows intervention in the moment, the work never stabilizes long enough to move at the speed the work actually requires.
That fight for a maintenance blackout looked like taking it easy. It was the only piece of capacity that lets lifecycle act before the moment is gone.