The advice arrives with a certain look on people’s faces. You’ve left the career, you’ve got some time and some means, and now, they say, this is the season to think about your legacy. They lean on the word a little. Legacy. As if I’ve been handed a plot of land and a bag of cement, and the only question left is what to put up.

I’ve never liked the word, and I like it less the closer it gets to me. Legacy sounds like a statue. It sounds like a wing of a building with a name on it, or a foundation, or a memoir nobody asked for. It points backward at the person doing the building and asks how he would like to be remembered. Six months out of a thirty-five year career, I’ve discovered I don’t much care how I’m remembered. I care whether the things I make are any use to somebody after I’ve set them down. Those are not the same project, and telling them apart has become the main work of this stretch.

Here is the most valuable thing I’ve built this year. It is a document. It lives in a shared folder, and it explains, in plain order, where everything is. The accounts and who holds them. The passwords. Who to call about the investment accounts, the cars, the policies. What Beth should do first, second, and third if I’m suddenly not here to be asked. What brand of trash bag to set me out at the curb in. It took me a couple of weekends and it is the least romantic object I own.

It is also more of a legacy than anything I’d ever put my name on. If the worst happens, that boring file is the difference between my wife grieving, and my wife grieving while also trying to reverse-engineer twenty years of my filing habits under the worst possible conditions. No statue does that. No memoir does that. A spreadsheet does that. I find I trust the projects that look like that one, and distrust the ones that look like monuments, and that instinct has turned out to be a decent filter for the whole question.

Run the blog through it. I’ve been writing here for eight months, near weekly, and if you’d asked me a year ago I might have dressed it up as building a body of work. That’s the monument version, and it’s mostly vanity. The useful version is smaller and truer. Writing these posts forces the answer out of my head and onto a page where it can be checked, argued with, and once in a while handed to somebody standing where I stood. I wrote a week ago about the questions my sons don’t ask. The value of that post isn’t that it exists under my name. It’s that the answer now lives somewhere outside my own skull, so if one of the boys ever needs it, he isn’t starting from nothing. Same test. Is this for being remembered, or for being used.

The hardest thing on the list is the one you can’t build like a document, and that’s presence. I want to be careful here, because presence is exactly the kind of word that curdles into sentiment if you lean on it, and I’ve read enough retirement essays about being there for the grandkids to know how fast this goes soft. So let me keep it concrete. Jake is now fully engaged in his new life at Arizona State. DJ is a continent away in Nashua. Brandon is in Greenville, and I haven’t seen him in person in over a year. Presence, for me, isn’t a warm feeling. It’s a set of specific, slightly awkward decisions. Pick up the phone when I have nothing to report. Fly out when there’s no occasion. Answer a real question with a real answer instead of the polished one I reach for by default.

And I’m not good at it yet. The same habit that made me useful in a boardroom, the measured non-answer, still fires at my own kitchen table, and I’ve caught myself handing my kids an earnings call when what they wanted was their father. That’s the thing about presence. You can’t ship it and mark it done. It resets every week. Some weeks I build it and some weeks I don’t, and the weeks I don’t are the ones I’d most like back.

There’s the knowledge, too. Thirty-five years of finance, twenty of them at a Big Four firm, and a real question about how much of it transfers to anyone who isn’t sitting in the chair I left. Some of it is genuinely worth passing on. A fair amount is scar tissue that only made sense inside one specific job at one specific company, and would be actively bad advice anywhere else. The trap here is obvious and I watch for it. It’s becoming the man who mistakes his own availability for generosity, who offers four opinions when he was asked for none, who confuses having done something for a long time with knowing something worth teaching. I’d rather share a third as much and have it be load-bearing.

I’ll admit the monument still tempts me. Every few months I catch myself half-drafting the book version of all this in my head, the one with a spine and a cover and my name across the bottom. It’s a nice fantasy and I don’t fully trust it. When I hold it up to the same filter, it fails. Most of the appeal is that it would have my name on it and would sit on a shelf outlasting me, which is the legacy instinct in a slightly more respectable jacket. If the writing is worth anything, it’s already doing its job one post at a time, for free, for whoever needs it. The book would mostly be for me.

Which brings me back to the word I started with. The instruction to go build a legacy is really an instruction to make something about myself, and the closer I look at the projects that actually hold up, the less any of them are about me at all. The document is for Beth. The writing is for whoever’s next in the same spot. The presence is for the boys, on their terms and not mine. The knowledge is worth something only to the degree I can strip my own ego out of it. None of that photographs well. None of it goes on a plaque.

I think the version of this stage that goes wrong is the one that reaches for permanence. You leave the thing that defined you, and the fear underneath is that you’ll be forgotten, so you go hunting for something with your name on it to outlast you. I understand the pull. I just think it’s the wrong build. The things worth making now are the ones that keep working whether or not anyone remembers who made them. A file that saves my wife a nightmare. An answer that outlives the conversation. A phone call my kid didn’t have to ask for.

Set the monument down. Build the useful thing. Nobody has to remember your name for it to have been worth doing.