Learn AI from scratch: a 7-day beginner path
Vlad Voronezhtsev · · 6 min read

Learn AI from scratch by starting with one practical task, not a long tool list. A beginner should choose the output format, write a prompt as a short brief, compare the model's answers, and improve the request. That turns AI training into a skill instead of passive tool watching.
- 1.
Start AI training with one small task
The common beginner mistake is opening ten AI tools, watching five lessons, and finishing nothing. For the first step, choose one work-shaped task: a short text, a slide, a product card, a cover image, a short video script, or an email outline. The task should be small enough to finish in one evening. Write down the goal, audience, format, constraints, and quality bar. Not «I want to learn AI», but «in 60 minutes, build one marketplace product card: image idea, title, description, and three promo lines». This kind of AI training shows where the model helps and where human judgment still matters.
Before
I want to understand AI. Recommend tools and tell me what to try.
After
Task: build one marketplace product card in one evening. Audience: gift buyers. Format: image idea, title under 60 characters, 500-character description, 3 promo lines. Quality bar: the difference from similar products is clear.

- 2.
Pick a track: text, slides, or visual work
It's easier to learn AI when you stay on one track. Track one is text: emails, posts, product descriptions, meeting summaries. Track two is presentations: structure, talking points, slides, and speaking notes. Track three is visual and video work: references, covers, ad frames, and short clips. Don't mix them in week one. If you choose an AI course, pick one that teaches a repeatable workflow, not just a tour of apps. A useful module forces you to make an artifact: a slide, landing page, product card, video, or mini-project. Without an artifact, learning becomes watching someone else's screen.
Before
I'll study ChatGPT, Midjourney, Veo, Figma AI, automations, and a few more tools.
After
One-week track: presentations only. Day 1 - task and audience. Day 2 - structure. Day 3 - slide prompt. Day 4 - visual style. Day 5 - revisions. Day 6 - assembly. Day 7 - one finished case.

- 3.
Treat the prompt as a brief
A prompt is a working brief: it should define the goal, context, input material, output format, and constraints. If you write «make it nice», the model guesses the style. If you state the audience, role, tone, format, and limits, the result becomes easier to judge. Practical case: a beginner made a product card in GPT Image 2 and got a pretty but useless image. The mistake was the prompt. It asked for an «advertising product photo» but did not lock the audience, angle, background, or space for text. The fix added `hero product card for handmade ceramic mug`, `target audience: gift buyers`, `dark neutral background`, `top-left empty space for headline`, `no fake logo, no unreadable text`. The next render was portfolio-ready: clear product, clean background, and space for a headline.
Before
Make a product ad card, beautiful, modern, for a marketplace.
After
Hero product card for a handmade ceramic mug. Target audience: gift buyers. Dark neutral background, soft studio light, mug centered, top-left empty space for headline, realistic texture. Constraints: no fake logo, no unreadable text, no extra products.

- 4.
Use a 7-day plan, then save the case
Day 1: choose one task and define the quality bar. Day 2: collect three references. Day 3: write the first prompt. Day 4: compare two or three outputs and find the main error. Day 5: rewrite the prompt without changing the whole task. Day 6: polish the result. Day 7: save the case with the original prompt, the fix, and the final output. Opten is useful at the preflight stage. It helps turn a rough idea into a production prompt, catch missing constraints, and improve the request before you spend generation attempts. Learn the workflow first, then add more tools.
Before
Watch a new lesson every day and try a new tool every day.
After
Move one case forward every day: task, references, prompt, first error, fix, final result, short portfolio note.


