But as a creator myself, I'm not at what size I would figure out company procedure for death other than canceling/transferring an account.
Maybe the administrators of the organization should have removed Jane from the system?
It looks an awful lot like someone couldn't see a way to delete a member from a family account, and couldn't be bothered to figure it out. So they just edited her name from "Jane" to "Jane (Deceased)".
Political ad/survey text messages also seem to think my number is my late grandfather's, even though my given name isn't the same as his.
This is a wheel that everyone is asleep at it, and they really don't care. If it happened to a mega-rich CEO something might happen, but they have people to handle their mail.
She always talked about that time very fondly and receiving that yearly letter always made her happy. I could never bring myself to inform them about her death and end that yearly tradition.
It seems to me that we're living in a sort of haze, caring about unimportant, downplaying/postponing the really important stuff. Whenever I have this deep realization I can die any minute, I cut tgroygh this haze, I can re-focus on what's (for me) truly important - namely close personal connections, chiefly my family and good friends.
When renewal time came, I received two emails: one to me, and one redirected from my wife's email address. Mine said (names changed for reasons of privacy):
"Dear Herodotus, We hope this email finds you and your family well. It is time to renew your membership...."
The second one said this:
"Dear Jane (Deceased), We hope this email finds you and your family well....."
Not all experiences were this bad, but I did get the feeling that most people building client databases do not give much thought to the one use case that is guaranteed for every entry in the client database: Death.