The one move from Defined to Outcome-led

Defined looks productive. There's a team, a shared inbox, a spreadsheet everyone half-trusts. Renewals mostly happen. Nobody would call it broken.

It's also where most CS functions stay for years, because nothing forces the next step. Outcome-led isn't a mindset you adopt. It's a structure you build.

The one move that gets teams unstuck: separate the account list from the risk list. Defined teams manage one list — every account, reviewed the same way, on the same cadence. Outcome-led teams manage two — the full base, and a shorter list of accounts flagged before renewal, built from a small number of signals checked weekly rather than discovered in the renewal call.

That second list doesn't need machine learning or a data team. Three signals are enough to start: usage trend, support sentiment, and time since last executive contact. Score them, review them weekly, and act on the ones that move.

A team that does this for a single quarter usually finds two or three renewals they would otherwise have found out about too late. That's the whole difference between Defined and Outcome-led — not new tools, a second list.

Where you sit on the five stages, and which of the six dimensions is holding you back, is what the Kent & Co Maturity Model exists to show.