Everybody has that one person in their life who keeps saying “I’m so behind on all this AI stuff.” Maybe it’s a parent. Maybe it’s a boss who still forwards you screenshots of screenshots. I’ve tried explaining Claude to people like that before, and it never lands. Too many words, too much jargon, zero results.
Then I ran into this post from a LinkedIn creator who cracked it in a way I genuinely didn’t expect. His mom asked him, “What the hell is Claude?” He didn’t write an essay. He sent her one image. That image did the work. Twenty minutes later she called back with six more questions, and those six questions turned out to be the best beginner course on Claude I’ve read all year.
I love this because the original poster didn’t invent a curriculum. He just answered his mom honestly, and her confusion mapped perfectly onto everyone else’s confusion. Here’s the whole thing, broken into steps you can actually follow tonight.
Step 1: Fix the blank prompt box
Her first question was the one everybody has but nobody admits: “What do I type in the prompt box?”
The author’s answer is beautifully lazy. Instead of teaching prompt engineering, he handed her a template to fill with her own context:
“I want to [TASK] for [RESULT]. AskUserQuestion.”
Why this works: that last word flips the whole dynamic. Claude asks you 3 to 5 questions. You tap the answers. You’re no longer staring at an empty box trying to guess what a good prompt looks like. The AI interviews you instead. According to the post, she never asked about prompting again after that. One template, question retired.
Step 2: Stop typing, start talking
Her follow-up was pure mom energy: “You expect me to type all that?”
No. The expert’s fix was voice. He pointed her to Wispr, a free dictation tool, so she could just speak to Claude instead.
- Install the voice tool on the device she already uses.
- Open Claude, hit dictate, and talk like you’re leaving a voicemail.
- Let it transcribe, then send.
The rationale: most people speak roughly 4x faster than they type. For anyone who didn’t grow up on a keyboard, that gap is even wider, and typing is the single biggest reason they quit before getting a result. Remove the friction, remove the excuse. The author joked his mom speaks about 400x faster. Sorry, mom.
Step 3: Give your files a home
Next up: “Where did my file go?” A classic. Files get uploaded into a chat, the chat scrolls away, and the file feels lost forever.
The creator’s walkthrough was concrete:
- Open the Claude desktop app.
- Locate “cowork.”
- Open “Projects” and upload all your files there.
Why it matters: a Project is a container. Your files stay put, and Claude keeps the context across conversations instead of forgetting everything the moment you close a tab. His mom dropped in a messy PDF. She got back a clean Excel file, saved right on her computer. She found it herself. That last part is the whole point. Once someone locates their own output once, they stop needing a guide.
Step 4: Understand what a “skill” actually is
Then came “What the hell is a Claude skill?” The post’s author calls that a fair question, and I agree. The term sounds far more complicated than the reality.
His definition is the cleanest I’ve seen: a long prompt turned into a Claude command that runs on its own, every single time.
That’s it. You write good instructions once. You save them. Claude runs them consistently forever, without you re-explaining yourself. Think of it like a saved recipe versus describing the dish from memory every night. Building a solid library of your own takes real time, which is exactly why the loading order matters: get a result first, build skills second.
Step 5: Connect it to your actual life
Her reaction to integrations was suspicion, which is healthy: “It’s reading my emails??”
The answer from this industry pro: only if you let it. Gmail, calendar, meeting notes, all opt-in, all connected on purpose. Her first real test was a single line:
“prep me for tomorrow’s meeting”
She called back just to say “witchcraft.” I was grinning when I read that, because it’s the exact moment the tool stops being a chatbot and starts being an assistant. The jump from “answer my question” to “handle my day” happens the second it can see your real context.
Step 6: Skip the waiting room
Her last question is the one that stuck with me: “Why did nobody tell me this?”
The post’s author drops a stat that reframes everything: roughly 98.75% of people have never tried Claude at all. Not “tried it and struggled.” Never opened it. Everyone’s standing around waiting to feel ready, waiting for a course, waiting for someone to hand them permission.
His mom skipped the waiting entirely. Ten minutes, one image, six questions.
How to use this today
- Send the person in your life one visual, not a lecture.
- Hand them the fill-in-the-blank prompt template so the blank box stops being scary.
- Set up voice input so typing never blocks them.
- Show them Projects so their files have a home.
- Let them run one task that touches their real calendar or inbox.
My honest take: this works because it’s answer-driven, not lesson-driven. Nobody learns software from a tour. They learn it from getting one thing they wanted. The creator’s mom got an Excel file out of a messy PDF, then never looked back.
Save this for your mom. Or your dad, your boss, your friend who keeps saying they’re behind. Ten minutes is the whole entry fee.
Go read the full LinkedIn post for the complete rundown, the original poster tells it far better than any summary can.