Youre Not Behind (Yet)- How to Learn AI in 17 Minutes

EDUCATION AROUND THE WORLD
33 followers
Comments are disabled for this video.
Most people using AI are doing it wrong, which is why it's surprisingly easy to get ahead of 99%
of them. I have spent over 20 years in tech and AI as a CEO, board member, investor, building
billion-dollar companies, and here's what I'm seeing. The gap between people who understand AI
and those who don't is getting wider faster. In this video, I'll give you a clear seven-step
roadmap to master AI like the top 1%. And the best part is you can actually do it in just 30 days,
even if you're a total beginner. Let's dive in. Week one starts with learning what I call
machine English. Most people talk to AI like it's a person, and that's a huge mistake. Why? Because
the generative AI systems like ChatGPT don't actually understand our language. They predict
And that's where most people get stuck. If I said, Humpty Dumpty sat on a... your brain's gonna fire
wall, you knew what was coming. Your brain predicted it. You could have said Humpty Dumpty sat on a roof.
Now, it's accurate, but you knew wall was more likely based on what you've seen before. Think
about Google search. It does autocomplete the same way. Why? Because it has seen so many search queries
before, it has learned from it, and now is giving you the most likely option. AI models like ChatGPT
or Gemini work in a similar fashion, but they're different than search engines because they don't
store any pre-baked answers. They generate the answer on the fly. How do they generate it? Like
at a very high level, AI breaks your text into smaller parts called tokens. Each token is a word
or sometimes a part of a word. Humpty is probably one token. Dumpty could be another token. Sat,
another token. Wall, another token. Then AI converts each token into a list of numbers,
also known as multi-dimensional vectors. Those numbers are placed inside a massive mathematical
space called an embedding space. And in that massive space, similar ideas tend to live closer
together. The system has learned from previous experiences, so it knows that the word Humpty,
egg, wall, and fall will be closer. But they're going to be far from words like motorcycle or
chocolate. Now when it's time to generate the answer, AI looks at the context and predicts the
most likely next token. So when it sees Humpty Dumpty had a great, it weighs all the options.
Humpty Dumpty had a great party. Humpty Dumpty had a great day. Humpty Dumpty had a great chocolate.
And it sees that the word fall is the most likely outcome. So the line is generated and finished.
Not from memory, not from stored facts, but from probability and proximity. That's why AI can feel
so smart, but also so alien. Now I'm skipping a lot of details here, but the important takeaway
here is that when your prompt is vague, this guessing machine called ChatGPT or Gemini will
produce guesses that are also vague. And if your prompt is sharp and targeted, AI will come back
to you with sharp and targeted guesses. That's what I call machine English. It helps AI to compute
your intent, not just try to comprehend it. So what does a sharper prompt look like? I call it
AIM. A for actor. Tell the model who it's acting as. I is for input. Give it the context and data
it needs. And M for mission. What do you want it to do? Instead of typing, let's say, fix my resume,
try typing, hey ChatGPT, you are the world's most sought after resume editor and business writer.
You've reviewed thousands of resumes that led to interviews at top tech companies. You've told
the AI what its persona is, what it's acting as. A. Second line, I'm attaching my resume and the job
description for a senior product manager role at a fintech company. That's your input. Third, mission.
Review it and give me a bullet list of 10 specific ideas on how to improve clarity, measurable impact,
align with the role. Your mission is to help me build the best resume that gets me hired.
That's how you take AIM. It turns a prompt into a structure the model can understand, compute,
and reason with. You can use this three-part structure in almost all prompts. And from now on,
you will start seeing the results to be at least five or ten times better than before. Only when
you learn its language, does AI finally start working for you. Now that you understand how to
speak to AI, we're gonna pick your instrument. Here's the thing, most people start their AI
journey the wrong way. They google top 50 AI tools, they pick 10, and they jump from one to the other,
they skim through all of them. That's a recipe for failure because there's so much out there.
My recommendation, pick one, go deep. Think of learning AI the same way you would learn
an instrument. You know, there is a study in frontier psychology that found that drummers
pick up guitar faster than complete beginners. Drumming is not even about melody and it requires
very different physical skills. But I personally had the same experience. I spent tens of thousands
of hours as a drummer and when I picked up guitar, it wasn't easy but it wasn't uncomfortable
because I already knew how to practice and my brain was trained to see structures and patterns.
The deeper you dig into one foundational model, the faster you will find the rhythm of all the
others. So which one do you pick? If you want the most mature one, pick ChatGPT. If you're deep into
Google Stack and Google's ecosystem, try Gemini. If you want more business and project-based AI,
go with Claude. But really, it doesn't matter what you pick. In the first week, spend time with one
of them and learn its personality, its cadences, its limits, its strengths. The goal is to start
feeling the rhythm. Once you get comfortable, try using the AIM framework that we talked about.
By the end of week one, you should be able to write a structured prompt without thinking.
All right, so we've started using AI. Now let's talk about what actually makes your outputs smart
and that's context. The world's smartest AI will sound clueless unless you feed it context. Every
answer AI gives depends on how it understands the question. If you don't give it context, it has no
grounding. Remember that inside these AI models, there is nothing but a crazy mathematical space
filled with billions of numbers. Context is the map that helps you navigate that space, to tell
AI where to look and what matters. And the best way to build that map is with an acronym I call
MAP. M is for memory, the conversation history or the notes that carry over from previous chat
sessions that you've had with the AI. Now you can repaste the thread or ask the model to summarize
before starting again. That's how you'll start building continuity in your conversations. A is
for assets, the files, data, the resources that you attach or copy paste in your prompt. These assets
help you ground the model in reality. Second A is for actions. Now these are the tools that the
model can call to do work. The action could be search the web or scan your drive or write this
code or create a notion doc. And P is the prompt. And the prompt is the instruction itself. So the
better you get with memory, assets, and external actions, the better context you'll give AI in the
prompt. And the richer the context, the better the AI reasoning and response. Once you start using
these frameworks like AIM and MAP, you have joined the top 10% of AI users. But if you want to hit
that absolute expert level, there's one more thing that you really need. Debug your thinking, which is
step four. When you're not getting the right answer, the problem is not the AI, it's your thinking. I
remember the first time I ever prompted an AI. It was one of those earliest models from OpenAI. And
I spent an entire day trying to make sense of it. And by the end of it, I was super frustrated
because it was random. It was unpredictable. But back then, no one understood. The phrase
prompt engineering hadn't even existed yet. Because prompting isn't typing, it's iterating.
When the output is weak, I assume the fault is mine. Because it is. Did I get it the right persona?
Did I provide the right context? Did I give it the right goal? And sometimes I even ask the model
itself, what did you do? And why did you choose that answer? It will explain its logic. It'll
explain its chain. And that's when the magic starts. You're not just using AI, you're learning how it
thinks. There are three cheat codes I use for that. The first is the chain of thought pattern.
When the answer seems off, I would say, think step by step, show your reasoning,
then give me the final concise answer. The second is the verifier pattern. I would say to the AI,
ask me three questions that would clarify my intent to you. Ask them one at a time,
and then combine what you've learned and try again. And the third is the refinement pattern,
where you're refining your input itself. Before answering, propose two sharper versions of my
question. Ask which one I prefer, so AI will tell me how to ask the right way. And then we continue.
And you have to keep iterating with these patterns, because these loops can teach the
model how to understand you, and teach you how to understand the model. Test, tweak, tune up,
push, until you can tell why something is working and why something is off. That's when it clicks.
You're not talking at AI anymore, you're having an ongoing conversation. You and AI are learning
together from each other. But here's the thing, it's not enough to just debug your mind. If your
post sounds like every other LinkedIn post I see that's pasted from ChatGPT, you still have a
problem. And that's why step five is to steer to experts. When you ask ChatGPT a question,
you're not searching a database of answers. You're sampling from millions of probable ideas that AI
has learned over time, and storing as billions of numbers. Some are brilliant, some are average,
some are completely made up, and some are flat out wrong. If you prompt vaguely, like explain
to make a team more innovative, the model will give you a superficial generic blah answer full
of buzzwords. And you read it and think, yeah, I already knew that. So how do you fix that?
You direct the model away from the middle and toward the sharper edges of its brain.
So instead of that vague prompt, you can say this, explain how to make a team more innovative
using ideas from Pixar's brain trust, Satya Nadella's strategy, and Harvard's research.
Now you pull the model from mediocrity into mastery by navigating it toward experts,
frameworks, depth. What if you want to learn about black holes and you don't know who the experts
are? No problem. Ask AI first. List the top experts, researchers, and research papers,
and current thinking on black holes. Then feed the same thing back to the model and prompt
using these experts and sources, synthesize the original framework that fills the current gap
on the science of black holes or whatever it is that you're after. That's the way you make sure
AI is not an echo chamber anymore. But remember, you're gonna need to verify what you get. That's
our step six. Sometimes AI will tell you things like 68% of Americans are getting divorced. I mean,
you know it's not true. But the scary part is AI will sound just as confident when it's wrong
as when it's right. So you can tell AI a hundred times, stop making stuff up. But all models are
essentially generative by design. Making things up is why they exist. So what do you do about that?
You simply verify. Don't just consume. Critique. There are five ways to separate intelligence from
illusion. Assumptions, sources, counter evidence, auditing, and cross-model verification. Let's take
one at a time. Assumptions, ask. List every assumption you made and rank them each by confidence.
Second is sources. Ask. Cite two independent sources for each major claim that you just made.
Include title, URL, and a one-line quote. Now you can check it yourself. That's the scaffolding
behind the answer. Counter evidence, push it. Find one credible source that disagrees with your answer.
Explain the dependencies. That's where real reasoning lives. Auditing is the fourth one.
Ask. Recompute every figure. Show your math or code. You'll be shocked how often the numbers change
once you make it slow down and start auditing. And finally, cross-model verification. This one's my
favorite. I run the same prompt in ChatGPT and Gemini and Claude. I take the output from one model
and ask another to critique it. Or I feed the claims of one model into the other and say verify
this. That's how you separate noise from knowledge. By the end of your third week, you'll start feeling
more in control of your output. But here's the problem. The best AI output aren't the ones that
sound the most original. They're the ones that sound like you. That's why step seven is about
developing taste. Most people use AI like a vending machine. They push a button, grab the
same junk food output everyone else gets, and call it a day. If you did that, most people would know
you just copy-pasted it. But you are past that now, right? It's your fourth week. It's time to
step into the ring. Treat AI like your sparring partner. Argue with it. Push back. Sharpen your
thinking. Sharpen its thinking. That's where the ocean framework comes in. It's how you turn generic
answers into tasteful insights. Something that sounds like you. O, original. Look at the response.
Is there a non-obvious idea in it? If not, push it. Ask. Give me three angles no one else has thought
about. Label one as risky and recommend the one that you like the most. C, concrete. Are there
names, examples, and numbers that make sense? If not, ask. Back every claim with one real example.
E, is evident. Is the reasoning visible? Is there enough evidence? If not, ask. Show your logic
in three bullets. Provide evidence before you provide final answer. A, assertive. Does it take
a stance you could agree or disagree with? If not, push it again. Don't tell me what I want to hear.
Pick a side. State your thesis. Defend it. And then address the best counterpoint. N, narrative.
What's the story? Does it flow? Is it tight? Guide it. Write it like a story. Hook problem,
insight, proof, actions. Whatever you want in that story. So that's the ocean framework. To add taste
to your output. Now, as you apply this over 30 days, you will start noticing something deeper.
Every prompt you write, every revision you push, every judgment you make, you're not just training
the model. You are training you. AI is coming, whether we like it or not. To some, it might be
triggering lots of deep fears. But I remain a perpetual optimist. I think AI is not here to
replace human work. It's here to restore human worth. If you like this video, don't forget to
subscribe and check out my most recent video here. Thank you and I love you.
