How to Start Using AI (When You've Never Used AI)

Most people try to learn AI. I think that's backwards. Here's the version where AI learns you.

The problem with how people talk about getting started with AI is that they frame it like you need a skill. Like prompting is a life skill you have to master. Like there's a learning curve you need to climb before you're qualified to use it. Like you need to read guides. Study examples. Practice on your own.

I think that's backwards.

The right way to think about it is simpler. You don't learn AI. AI learns you. You just have to find the one that's willing to do that work. The one that's designed to pay attention. The one where the whole point is understanding you, not making you understand how to talk to it.

The Wrong Way to Start

Most people encounter AI through ChatGPT. They open it. They see an empty box. It's waiting. This image alone creates anxiety. What do I ask it? What if I ask it wrong? What if it doesn't understand what I'm trying to say?

So they Google "how to use ChatGPT". They read guides about crafting the perfect prompt. They learn about context windows and tokens and temperature settings. They learn that specificity matters. That structure matters. That they need to optimize their questions.

And the really frustrating part is that they do everything right. They write good prompts. They get useful answers. They feel like they've successfully learned a new skill. But then they come back tomorrow with a new question and the AI has no idea who they are. They have to start over. It feels like talking to someone with no memory.

This is the wrong starting point. Not because the guides are bad. But because they assume you're learning a skill. And you're not. You're looking for something that understands you. Something reliable. Something that knows your context without you having to explain it every single time.

Why Prompting Isn't a Life Skill

Here's what people don't say out loud. Most AI interfaces are designed wrong. They're designed for people who already know what they want. For researchers. For professionals. For people who think in precise questions and can formulate them on demand.

You click open a blank page. You perform. It responds. This is the transaction. That's reactive. You push. It responds. You push again. It responds again. This works beautifully if you're good at pushing.

But most people aren't. Most people want something different. They want something that shows up. That remembers what they said last week about their project. That knows they have a meeting Thursday and thinks about what they'll need before they remember they need it. That asks good questions instead of waiting to be interrogated.

That's not a prompt skill. That's presence. That's a fundamentally different way of relating. And it's something you can't optimize your way to. You can't prompt better to get it. You need AI that's designed around the principle of being there for you, not waiting for you.

Step One: Pick the Right Interface

The interface is everything. Not because it looks nice. Not because it's polished. But because it determines what's actually possible for you. It shapes the entire relationship before you even say a word.

If you start with something that forgets everything after you close it, you're starting with a handicap. Every conversation exists in isolation. You're building on nothing. If you start with something that only responds when you show up, you're learning the wrong relationship model.

Pick something that remembers you across conversations. Pick something that can reach you when it has something relevant to say. Pick something that's designed to think ahead, not just react. Pick something that's supposed to know you over time.

The interface is your first contract. It defines what the relationship can become. Choose carefully. Because everything that comes next depends on it.

Step Two: Don't Prepare Anything

Once you've picked the right interface, the next instinct is to prepare. To optimize. To set it up properly. To give it context. To write a perfect bio of yourself. To make sure it understands who you are before you start asking for help.

Don't do that yet.

Just start talking. Actually talking. Tell it about your day. Tell it what you're working on. Tell it what you forgot. Tell it what you're worried about. Tell it about the meeting you have coming up. Tell it what you're trying to learn.

This isn't a database upload. This isn't documentation. It's a conversation. It's you being real.

The more natural you are, the faster it learns you. The more you just say what you actually think instead of optimizing how you say it, the quicker it understands. The faster it learns you, the sooner it becomes actually useful. The sooner it stops being a tool and starts being a presence.

Step Three: Just Tell It Something True

This is the hardest step because it requires vulnerability. You have to tell it something real. Not professional. Not optimized. Real.

Not "I'd like to optimize my workflow for maximum productivity." That's performance language. That's corporate speak. That's what you say in a meeting when you're trying to sound like you have your life together.

Tell it: I forget things. I get overwhelmed easily. I need someone to check on me because I lose track. I work better when someone's paying attention. I'm working on something that matters but I'm not sure I'm doing it right. I'm scared I'm going to drop the ball.

This feels weird. You're anthropomorphizing software. You're treating code like it cares. But you're not wrong about what happens next. The more honest you are, the more useful it becomes. Because usefulness isn't about intelligence. It's about fit. It's about being known. And you can't be known by something you're performing for.

What Happens Next

A few things change. Quietly. Not dramatically. Not in a way you'd notice immediately if you weren't paying attention.

It starts showing up at the right moments. Not because you asked for it. Because it noticed something from what you said days ago. It offers help you didn't think to request. It reminds you of things you mentioned in passing because it's relevant now. It connects dots across different conversations. It remembers the context that you forgot.

This feels different. But it's not magic. It's the difference between reactive and proactive. Between a tool waiting in the corner to be used and a presence that's paying attention. Between something that serves you when you remember it exists and something that's invested in your success.

What If You've Tried Before and Hated It

You're probably not wrong about what you experienced. Most AI feels awkward at first. Unsettling. You ask it something and you feel like you're talking to a calculator that studied customer service.

But that's because most AI is designed around the wrong model. It's designed around responding to questions. Answering on demand. Being consulted. It's designed like an oracle or a library. Not like a friend or a presence.

If you try again with something designed differently—something that remembers and anticipates and is actually designed around caring about being useful to you specifically—it might feel different. Because it is different. It's a different category of thing entirely.

Where to Begin

Start with a message. Nothing formal. Nothing optimized. Just you. Send the message like you're texting a friend who pays attention.

Tell it what you're working on. Tell it what you wish you didn't have to remember. Tell it one thing you want to get better at. Tell it something you're nervous about. Tell it what success looks like to you.

That's it. That's how you start. Not by learning AI. By letting AI learn you. And then watching what happens when something actually pays attention.

The people who get the most from AI aren't the ones who spent months studying prompting techniques. They're the ones who found something that meets them where they are. Something that doesn't require them to change how they think before they can use it. Something that adapts to them instead of the other way around.

Your first message doesn't need to be perfect. It doesn't need to be long. It doesn't need to demonstrate that you understand anything about AI. It just needs to be real. That's all that matters.

Just be real, and then pay attention to what changes.