Plate IThe Phantom Returner — Plate I
Plate IIThe Phantom Returner — Plate II
← Back to the map

The Phantom Returner

Quartum revertus

Wing scales dulled and dusty from a long absence, expression carefully neutral. The Phantom Returner moves through your product like someone visiting a house they used to live in, recognizing the rooms but unsure where the furniture has been moved.

Anywhere they used to be familiar, like settings pages renamed, navigation reorganized, features deprecated or relocated. The Returner gravitates toward whatever workflow they remembered most clearly, which is usually the one your team has changed most.

The Phantom Returner has been away for ninety days or more and arrives confident the product looks the same as the morning they left. It does not. Within the first minute, they have encountered three features they cannot locate and one they cannot identify, prompting the small, dignified pause that is the species' signature.

Some adapt and quietly resume their workflow, while others give up and assume the product has been ruined since they left. The most vocal minority will send long emails to support that begin with the words "I've been a customer since…"

Major UI redesigns shipped without changelog visibility. Deprecated features removed without redirects. An empty state where their previous data used to be.

After ninety days away, the product moved and the user's memory did not. Settings got renamed, navigation got reorganized, and the feature they used most now lives somewhere else. Try finding your way around your own product using last year's menu names. A Summarizer scanner reading sessions from long-absent users writes down what each one came to do and where they got stuck, and a weekly digest to Slack gives you a standing list of what your dormant customers can no longer find.