What Should You Use AI for First When You’re New to AI?

by

If you're new to AI, the hardest question probably isn't “How do I use it?”

It's “What should I use it for?”

Open any social platform and you'll see people using AI to build entire businesses, analyze spreadsheets, write code, create presentations, automate workflows, generate images, and connect dozens of tools together.

That can make starting feel strangely intimidating.

You might think you need to find the perfect AI use case before you begin.

You don't.

In fact, your first AI experiment should probably be much less impressive than what you see online.

Start with something boring.

The best first AI task is usually something you already know how to do, do repeatedly, and wouldn't mind doing faster.

Here's how to find it.

1. Start With Work You Already Do, Not Something You Want AI to Do

One of the biggest mistakes beginners make is asking:

“What can AI do?”

That's an enormous question.

Instead, ask:

“Which part of my existing work wastes time?”

That question gives you somewhere to start.

Think about the work you repeat every week.

Do you write similar emails?

Do you turn meeting notes into summaries?

Do you create reports from rough information?

Do you repeatedly brainstorm social media ideas?

Do you rewrite documents for different audiences?

Do you spend 20 minutes organizing information before you can actually work with it?

These are much better starting points than trying to build an elaborate AI automation system.

A simple rule is the friction test.

Look for tasks that are:

  • Repetitive

  • Text-heavy

  • Predictable

  • Time-consuming

  • Easy for you to review

For example, if you regularly receive messy meeting notes, you could ask AI to turn them into:

  • Key decisions

  • Action items

  • Responsible people

  • Deadlines

  • Unresolved questions

You don't need to become an AI expert.

You already understand what a useful meeting summary looks like.

AI is simply helping you get there faster.

2. Your First AI Use Case Shouldn't Require Blind Trust

There's an important distinction between AI assistance and AI delegation.

When you're new to AI, start with assistance.

Let AI create a first draft.

Let it organize information.

Let it suggest possibilities.

Let it summarize something you already understand.

Then review the result yourself.

This is much safer than immediately giving AI responsibility for something consequential.

Here's a useful question to ask before choosing your first task:

If AI gets this 20% wrong, can I easily spot and fix the mistake?

If the answer is yes, you've probably found a reasonable beginner use case.

For example, asking AI to draft a routine internal email is relatively easy to review.

Asking AI to make an important financial decision for you is a completely different situation.

Your goal isn't to eliminate your judgment.

It's to eliminate some of the unnecessary work surrounding your judgment.

Think of AI as a capable assistant who can work quickly but still needs supervision.

That mindset will take you much further than treating every AI response as automatically correct.

3. Use the “Before, During, After” Test

Still not sure where to begin?

Take one recurring responsibility and examine what happens before, during, and after it.

Imagine you have a weekly team meeting.

Before the meeting

You might spend time:

  • Reviewing previous notes

  • Collecting updates

  • Creating an agenda

  • Identifying unfinished items

AI could potentially help turn scattered information into a structured agenda.

During the meeting

You might capture:

  • Decisions

  • Questions

  • Ideas

  • Tasks

  • Follow-ups

AI could potentially help organize those notes afterward.

After the meeting

You might need to:

  • Write a summary

  • Create an action-item list

  • Send follow-up messages

  • Update project documentation

Again, there are opportunities for AI assistance.

Notice what's happening here.

We're not asking AI to “run the meeting.”

We're identifying specific pieces of the workflow where repetitive information processing happens.

That's a much better way to think about workplace AI.

Instead of asking:

“How can I automate my job?”

Ask:

“Where does my workflow contain unnecessary friction?”

That's where your first AI win is likely to be.

4. Your First Prompt Doesn't Need to Be Clever

Another reason people hesitate to start is the belief that successful AI users have some secret ability to write perfect prompts.

You don't need that.

Start with five pieces of information:

Context → Task → Desired Result → Constraints → Format

For example:

“I’m preparing a weekly update for my manager. Here are my rough notes. Turn them into a concise professional update. Focus on completed work, current priorities, blockers, and next steps. Don't add information that isn't in my notes. Use clear bullet points.”

That's enough to begin.

And here's the part beginners often miss:

You don't have to get the prompt perfect on the first attempt.

If the response is too formal, tell it.

If it's too long, tell it.

If it missed an important detail, provide the detail.

If you want a different structure, ask for one.

Think of the process as:

Ask → Review → Correct → Reuse.

Eventually, you'll have prompts that consistently produce useful results.

And once you have one that works, save it.

A successful prompt isn't just a conversation.

It's the beginning of a reusable workflow.

5. Once One Task Works, Find the Next Bottleneck

Don't make the mistake of downloading 15 AI tools after your first successful experiment.

You don't need an AI toolbox full of things you never use.

Instead, build gradually.

Start with one task.

Use AI for it several times.

Notice what improves.

Save the prompt.

Then look for the next repetitive task.

Maybe your first workflow helps with meeting summaries.

Your second helps with email drafts.

Your third helps turn research notes into outlines.

Eventually, you aren't merely “trying AI.”

You're building a small personal system for getting work done.

And that's where AI becomes genuinely valuable.

The goal isn't to know every AI feature.

The goal is to have a handful of reliable workflows that remove hours of unnecessary work from your week.

Your First AI Win Should Be Small

If you're completely new to AI, don't start by trying to transform your entire job.

Find one task that is repetitive, slightly annoying, easy to review, and familiar to you.

Then experiment.

Your first AI success might be incredibly ordinary.

Maybe it saves you 10 minutes writing an email.

Maybe it turns 30 minutes of meeting notes into a useful summary.

Maybe it gives you a solid first draft instead of forcing you to stare at a blank page.

That's enough.

Because once you've experienced AI making one real task easier, the question changes.

You stop asking, “Should I learn AI?”

You start asking, “What else in my work could be easier?”

That's the shift that matters.

If you want help making that shift without spending weeks watching AI tutorials or trying random tools, I created AI in a Day: The Non-Technical Professional's Playbook for Automating Work, Looking Smarter.

It's a 25-page practical playbook designed to help non-technical professionals identify useful AI opportunities, write better prompts, and turn simple experiments into repeatable workflows they can actually use at work.

You don't need to become a tech expert.

You need a system for getting started.

Explore AI in a Day here:

1 view

Add a comment

Replies

Be the first to comment