The Latchkey Club Daily Draft — 2026-06-22
Teleprompter / Blog Script
Welcome back to the channel, guys.
Today I wanted to talk about something that sounds like a workplace topic at first, but I think it is bigger than work.
It is the stuff you know that is not written down anywhere.
Every organization has this. Every family has it too.
There is the official manual, and then there is what everybody actually does. There is the process document, and then there is the person who knows which step in the process is technically correct but will absolutely make your afternoon worse if you follow it exactly.
There is the spreadsheet, and then there is the guy who remembers why that one customer always needs a phone call before the email goes out.
There is the map, and then there is the person who knows the road is closed every time it rains because they have been burned by that road before.
That is the kind of knowledge I am thinking about.
The quiet knowledge.
The scar-tissue knowledge.
The stuff you only learn by living through enough mistakes, projects, repairs, deadlines, weird meetings, awkward conversations, and systems that were designed by someone who apparently hated humans.
And the older I get, the more I realize a lot of us in Gen X are carrying more of that than we think.
We are not always great at naming it. We just call it experience and move on.
Somebody asks, “How did you know that was going to be a problem?”
And your answer is something very professional like, “I don’t know. It just smelled funny.”
Which is not exactly a training curriculum.
But that instinct came from somewhere.
It came from watching the same pattern repeat. It came from fixing things that broke on Friday afternoon. It came from being the person who had to answer the phone after the shortcut failed. It came from years of consequences.
And here is what has been rattling around in my head: if we are thinking about retirement, or even just the next season of work, what happens to all of that when we leave?
I saw some articles this week about aging workforces and knowledge transfer. One was about manufacturing companies trying to protect the knowledge of veteran workers as they retire. Another story mentioned efforts to turn master workers’ know-how into AI training data.
And I get why people are interested in that.
Because when a person leaves, you do not just lose a job title.
You lose memory.
You lose shortcuts that were not lazy shortcuts, but earned shortcuts.
You lose the history behind why something is done a certain way. You lose the warning signs. You lose the little phrase somebody says before a project goes sideways, and everyone who has been around long enough knows, “Oh, here we go.”
That does not always show up in a resignation letter.
But it matters.
And I think this is one of those places where AI could actually be useful for people our age, if we use it with some humility.
Not to replace the older worker.
Not to pretend a chatbot has twenty-five years of judgment because it summarized a PDF.
I mean using AI as a capture tool.
A question tool.
A way to pull what is in your head into something another person can actually use.
Because most of us are not going to sit down and write a perfect 200-page training manual. Let’s be honest. We might buy the notebook. We might even label the folder. Then life happens, the inbox catches fire, someone schedules a meeting over lunch, and the notebook becomes a coaster.
But we might talk for ten minutes after solving a problem.
We might record a voice note.
We might tell an AI assistant, “Here is what happened, here is why it mattered, here is what I looked for first, here is the mistake a new person would probably make, and here is what I would check next time.”
Then the tool can help turn that into a checklist, a training note, a decision tree, or a set of questions for the next person.
That is not magic.
That is just taking the messy way experience lives in our heads and giving it a place to land.
I think that matters because a lot of Gen X learned in a pretty informal way.
We figured things out by watching, trying, breaking something, getting yelled at a little, fixing it, and then remembering not to do that again.
At home it was the same. You learned where the spare key was. You learned how to make something edible with a microwave and questionable confidence. You learned which drawer had the batteries, which were usually dead, but spiritually encouraging.
At work, many of us learned by being thrown into the deep end with a password, a phone number, and someone saying, “You’ll be fine.”
And somehow, mostly, we were.
But that way of learning does not automatically transfer well.
Just because I survived the messy version does not mean the next person should have to.
That is a big shift.
When you are younger, sometimes you protect your knowledge because it feels like job security. You want to be the person people need. You want to be the one who knows where everything is buried.
I understand that.
But later in life, I think the question changes.
The better question becomes: who gets stronger because I was here?
That is different from, “Who needs me?”
Needing me can become ego if I am not careful.
Strengthening someone else is legacy.
And this is where age can be an advantage if we do not waste it.
Because people our age have seen enough to know that information by itself is not the same as wisdom.
A younger person can look up the steps. AI can summarize the policy. A search engine can find the spec sheet. But the older person may know which step matters most, which warning to take seriously, which shortcut is safe, and which one is going to come back with teeth.
That is the part worth transferring.
Not just what to do.
Why it matters.
What to notice.
When to slow down.
When to call somebody instead of sending another email into the void.
When the numbers look fine but the situation does not.
That kind of judgment is hard to document, but it is not impossible.
You just have to start smaller.
Pick one recurring problem.
One customer situation.
One family process.
One account you always have to explain.
One home repair ritual that apparently requires three trips to the hardware store and a level of optimism that should be medically monitored.
And after you deal with it, capture the story.
What happened?
What did I notice first?
What did I almost miss?
What would I tell someone doing this for the first time?
What question should they ask before touching anything?
That is the beginning of a playbook.
And if AI can help organize that, great. Let it help. Let it ask follow-up questions. Let it turn your rambling voice note into something readable. Let it make the first draft ugly so you can fix it.
But do not hand it the steering wheel.
Because the value is not the formatting.
The value is the judgment you are putting into the system.
That is the part I think people miss in a lot of AI conversations. Everybody wants to know if the tool can create something from nothing.
But for a lot of us, the better use is creating something useful from what we already know.
That old workaround.
That customer history.
That lesson learned the hard way.
That thing you say every time a new person starts because you wish somebody had said it to you.
Capture that.
Not all at once. Not perfectly. Just start.
Because at some point, whether it is retirement, a job change, a health issue, a family transition, or just getting tired of being the only person who remembers everything, we have to decide what we are going to do with what we have been given.
We can carry it until we walk out the door.
Or we can leave handles for the people coming behind us.
I am trying to think more about the handles.
Not because I have it all figured out. I do not. Some days my own files look like they were organized by a raccoon with Wi-Fi.
But I do know this: if experience stays trapped in my head, it only helps while I am in the room.
If I can turn even some of it into questions, notes, checklists, stories, and training, then it keeps helping after I step away.
And maybe that is one of the better uses of this season.
Not proving we can keep up with every new tool.
Not pretending we are twenty-eight with better lumbar support.
But taking what we have learned, using the tools that are available now, and making it easier for somebody else to carry the work forward.
Anyway, that is what I have been thinking about.
What is one thing you know how to do that nobody has ever really written down?
That might be where your playbook starts.
Video Prompt Script — Questions to Answer Without Reading
Use these as prompts. Don't read them on camera; answer them naturally.
- Opening: What is something you know at work or at home that is not written in any manual?
- Follow-up: Is there a weird little detail you only know because you learned it the hard way?
- Gen X formation: How did Gen X learn things informally — by watching, trying, breaking things, and figuring it out?
- Follow-up: What was good about that, and what should we not pass on exactly the same way?
- Retirement/legacy angle: As you think about retirement or the next season, what happens to the knowledge in your head when you leave the room?
- Follow-up: Who gets stronger because you were there?
- AI usefulness: How could AI help capture experience without pretending to replace judgment?
- Follow-up: Could it turn a voice note into a checklist, decision tree, training note, or question list?
- Practical challenge: What is one recurring problem, customer situation, family process, or home routine that should become a simple playbook?
- Follow-up: What would you tell someone doing it for the first time?
- Closing: What is one thing you know that needs handles so someone else can carry it?
Title Options
- Before You Retire, Capture What You Know
- The Stuff You Know That Isn’t in the Manual
- AI Can Help Gen X Leave Better Instructions
Thumbnail / Onscreen Text Options
- WRITE DOWN WHAT YOU KNOW
- EXPERIENCE NEEDS HANDLES
- DON’T LET YOUR KNOWLEDGE RETIRE WITH YOU
Shorts / Reels Cutdowns
- “The manual vs. what actually happens” — clip the section about official processes versus the person who knows which step will make your afternoon worse.
- “Experience trapped in your head” — clip the line about knowledge only helping while you are in the room unless you turn it into notes, questions, and training.
- “AI as a capture tool” — clip the practical example of talking for ten minutes after solving a problem and letting AI turn it into a checklist.
Viewer Question
What is one thing you know how to do — at work, at home, or in your family — that nobody has ever really written down?