How to Choose Your First AI Task: Start Small, Low-Risk, and Reviewable
Choose a useful first AI task with four checks and a simple task selection card. Start with safe material, a reviewable draft, and no irreversible action.
You may already know that AI can draft, summarize, compare, and generate ideas. The harder question is more practical: what is the first piece of your own work that you should give it?
One common mistake is to start with an entire proposal, sensitive customer material, or an important decision. Another is to avoid real work completely and use AI only for disconnected experiments. Neither teaches you how AI fits into a work process you still control.
For a first attempt, do not choose your most important task. Choose work you understand, can review yourself, and can stop or revise when the first result is wrong. The goal is not to prove that AI is impressive. It is to learn one small, inspectable work cycle.
Choose one bounded piece of work, not a whole outcome
“Prepare next week's customer proposal” sounds like one task. It actually includes understanding the customer, checking source material, choosing claims, writing, building slides, verifying numbers, and taking responsibility for an external commitment.
Shrink the first attempt until its inputs, output, and review are visible.
| Too broad for a first attempt | A smaller starting point |
|---|---|
| Finish my customer proposal | Use a fictional product brief to suggest three outline options |
| Decide whether we should buy this tool | Use public product pages to list five questions I still need to investigate |
| Process the entire meeting record | Use a short synthetic transcript to identify possible decisions, actions, and unknowns |
| Refactor the whole website | Read one practice folder and explain what each file appears to do |
Reducing scope does not make the exercise pointless. It makes the boundary observable. You can see which material was used, what was produced, and where the result failed.
Use four checks for a good first task
I use four questions when helping a beginner choose a first AI task. This is Aaron's teaching method, not an official task classification from an AI provider.
- Can the material stay small and safe? Use a short public, synthetic, or non-sensitive input. Do not begin with customer data, contracts, personal information, or internal company files.
- Are you asking for a first draft? Classification, a summary, rewrite options, comparison fields, or questions to investigate are useful starting outputs. A final decision is not.
- Can you understand the result? You should know what a roughly useful answer looks like and be able to identify at least one obvious omission or mistake.
- Do you have a review method? You can compare the output with the source, recalculate a value, or ask someone familiar with the work. Asking the AI whether its own answer is correct is not enough.
If one of these checks is unclear, the task may still be suitable later. First narrow the work or prepare safer material.
Reviewable does not mean you must already be an expert
You do not need expert knowledge in every subject before using AI. For this exercise, reviewable means that you can check whether the output stayed faithful to the material and boundary you supplied.
Suppose you write a fictional event notice and ask AI to turn it into a participant checklist. You can compare every date, location, and instruction with your source. You can also spot invented travel advice, costs, or contact details. That is a real review method.
A contract decision, supplier selection, or investment, medical, employment, or legal recommendation is different. The critical judgment may sit outside what you can verify on your own, and a bad result can carry a larger consequence. Do not use those as first exercises.
OpenAI's current ChatGPT Work guidance says that a user can add files and context, describe the task or deliverable, review progress, change direction, and approve important actions. OpenAI's account of how its teams use Codex also recommends beginning with well-scoped work. The second point is a Codex practice, not a universal classification for every AI product.
These official statements do not guarantee a correct output. They support a more limited point: the task remains a process you review, not a request you send away and forget.
Fill in a first AI task selection card
Choose a real type of work you expect to do, but reproduce it with public, synthetic, or clearly non-sensitive material. Complete these five fields before opening an important folder.
| Field | Example |
|---|---|
| Small piece of work | Turn a fictional event notice into a participant checklist |
| Material I will provide | One text file I wrote, with no real contact details |
| First draft I want | A bulleted checklist that adds no facts beyond the source |
| How I will review it | Compare each date, place, and instruction with the original |
| What AI will not do | It will not decide whether to cancel the event or send anything to participants |
Then ask:
- Can I reduce the material to one or two small files or a short passage?
- After reading the first result, can I point to something it omitted, misstated, or added?
- If I stop now, will there be no external commitment, data exposure, or irreversible effect?
If your first two answers are yes and the third is no, the task is a practical starting point. If not, make it smaller or choose work with simpler material.
Useful first-task patterns
Your first task does not need to be novel. Good practice candidates often include:
- rewriting a short passage you wrote for a different reader;
- using public information to list comparison fields and open questions, without asking AI to decide;
- organizing a synthetic meeting excerpt into possible decisions, actions, and unknowns;
- reading a folder that contains only practice files and explaining the likely role of each file.
These tasks are not useful because they are trivial. They are useful because the material, output, and review method are visible.
If meeting notes are your chosen scenario, continue with AI Meeting Notes: Turn Source Text into Decisions and Action Items You Can Review. It develops one complete reviewable example without turning the result into an automatic record of truth.
Next: use the selected task in Codex
Keep the selection card. U2-M2 will use the chosen non-sensitive material to walk from input and task description to a result you can inspect. It has no public URL yet, so this lesson does not link to an unpublished destination.
If your folder, file-edit, approval, or network boundary is still unclear, first review Codex Permission Setup: Choosing a Folder, Approvals, and Network Access.
The important outcome is not a perfect first attempt. It is being able to say what the AI saw, what it did, what it returned, and why you chose to revise or stop.
References
The product workflow statements above are based on OpenAI's current materials. The four task checks and the first AI task selection card are Aaron's cross-product teaching method. They are not a product guarantee and do not replace organizational data, permission, or risk rules.