How to Start Using AI at Work: A 5-Day Plan for Your First Week

You keep hearing that AI can save you time at work. But when you open a chat window, you're not sure what to type. Or you tried once, got a bland answer, and went back to doing things the old way. This plan gives you one short exercise a day for five days, each on a task you already do. By Friday you'll have edited real emails, summarized long documents, drafted from scratch, solved a spreadsheet or meeting problem, and saved the prompts that worked into a library you can reuse.

Before Monday: pick one tool and three tasks

Use one tool all week. If you switch between tools, you can't tell whether the tool or your prompt made the difference. If your employer provides an approved AI tool, use that one. If you're not sure which assistant fits your work, Which AI Assistant Should I Use? compares the main options.

Here are a few common work setups, as of November 2026:

• ChatGPT Business: OpenAI's team plan. Every seat includes ChatGPT and ChatGPT Work, and paid plans use the GPT-6 Sol model.
• Microsoft 365 Copilot Chat: included at no extra per-user cost with eligible Microsoft 365 plans, with enterprise data protection. It answers using the web, but it can't see your organization's files and email the way the paid Microsoft 365 Copilot add-on can.
• Gemini or Claude: if your company uses Google Workspace or has chosen Claude, every exercise below works the same way.

Next, write down three tasks you do every week that involve reading or writing. Examples: answering customer emails, summarizing meeting notes, writing a weekly status update. You'll come back to these all week, which makes it easy to compare results.

Day 1: Improve an email you already wrote

Start with something low-risk where you already know what good looks like. Pick an email you wrote recently or need to send today. You're not asking AI to write it. You're asking it to edit.

Here is an email I'm about to send to a client who is frustrated about a delayed delivery. I want it to sound calm, take responsibility without over-apologizing, and give a clear next step. Keep it under 150 words. First point out anything that might come across badly, then give me a revised version.

[paste your draft]

Read the revision line by line. Keep what's better and ignore what isn't. Then send one follow-up instead of starting over, such as "Make it a bit warmer" or "Cut the second paragraph." Follow-ups are where much of the improvement happens.

Your goal for today: notice that the more you said about the reader and the situation, the more usable the answer was.

Day 2: Summarize something long, then check it

Pick a long document you'd normally skim: a report, a policy update, a long email thread or a set of meeting notes. Paste it in, if it's appropriate for your tool, and ask for a summary shaped around how you'll use it.

Summarize the document below for my manager, who has two minutes to read it. Give me: 1) three bullet points on what changed or was decided, 2) any deadlines or numbers, quoted exactly, 3) open questions or anything unclear. If something isn't stated in the document, say so rather than guessing.

[paste document]

Now the important part: check the summary against the original. Look at every number, date, name and decision. Did it leave out anything you consider important? Did it state anything the document doesn't actually say?

Day 3: Draft something new with real context

Today you'll start from a blank page. Choose one of your three weekly tasks, such as a status update or a project announcement. The gap between a generic answer and a useful one is usually context. Before you ask, give the tool four things:

• Context: what's going on and why this document exists.
• Audience: who will read it and what they care about.
• Format: length, structure and tone.
• Example: a past version you liked, if you have one.

I lead a five-person customer support team. Write my weekly status update for the operations director, who cares about response times and anything that needs her decision. Format: three short sections (Wins, Problems, Decisions needed), plain language, under 200 words.

Here are my rough notes: [paste notes]

Here is last week's update so you can match the style: [paste example]

If the draft is off, say exactly what's wrong ("too formal" or "the Problems section is vague, use the ticket numbers from my notes") rather than rewriting your whole prompt. Jot down which piece of context made the biggest difference. You'll use that on Friday.

Day 4: Get help with a spreadsheet or a meeting

Spend today on a task that isn't pure writing. Pick whichever option fits your week.

Option A: a spreadsheet problem

Describe your columns and the result you want, and ask for a formula with an explanation. You don't need to paste the whole file. A description, or a few rows with made-up values, is usually enough.

I'm working in Excel. Column A is customer name, column B is invoice date, column C is amount, and column D says whether it's paid (Yes or No). I want one formula that totals the unpaid amounts for invoices older than 30 days. Give me the formula, explain each part in plain English, and tell me how to test it on a few rows.

Before you trust the formula, test it on a few rows where you already know the right answer. If it fails, paste the error message back in and ask what went wrong.

Option B: meeting prep

Paste an upcoming meeting's agenda and your notes, then ask: What questions are likely to come up, who might push back, and what should I have ready? You'll often get one or two questions you hadn't thought of. Treat the list as a starting point, not a prediction.

Day 5: Turn what worked into a prompt library

Look back at the week. Which prompts gave you answers you used with little editing? Those are worth keeping. A prompt library is simply a collection of your best prompts turned into templates with blanks to fill in, so next time you start from something proven instead of an empty box.

To make a template, replace the specific details with placeholders in square brackets. Here's Monday's email prompt, ready to reuse:

Here is an email to [who it's going to] about [situation]. I want it to sound [tone], and it must [main goal, for example: give a clear next step]. Keep it under [number] words. First point out anything that might come across badly, then give me a revised version.

[paste draft]

Aim for three to five templates, one for each recurring task. Then pick a place to keep them:

• A shared document: works with any tool and is easy for colleagues to copy and improve. Group prompts by task, such as email, summaries and reports.
• ChatGPT Projects: a project keeps related chats, files and instructions together, so you don't have to restate background each time. Put standing context, like your role, your team and your preferred format, in the project's instructions. Availability depends on your plan and workspace settings, per OpenAI's Projects help page.
• Your tool's own options: if you use Copilot, Gemini or Claude, check what your organization's version offers for saving instructions or reusable prompts.

Finally, let the AI improve your library. Paste in a template and ask: This is a prompt I use every week. Suggest how to make it clearer, and point out any details I should turn into placeholders.

After week one: what to try next

Repeat the same tasks for another week. Comparing results on familiar work is the quickest way to learn where the tool helps and where it still needs a close eye. Add a new template to your library whenever a prompt earns it.

When you're comfortable, look at bigger features with the same care. As of November 2026, ChatGPT runs on GPT-6 across all plans, so guides that mention GPT-5.x models are out of date. OpenAI also offers ChatGPT Work, an agent launched in July 2026 that pulls context from your apps and files and produces finished documents, spreadsheets, presentations and web apps, with plugins for Slack, Teams, Google Drive and SharePoint. The rule from Day 2 still applies: check what it produces before you share it.

If your whole team is starting at once, try running this plan together and building one shared library. Each person brings their best prompt on Friday, and everyone leaves with more templates than they could write alone. For structured help with that, see team training.

Written with AI assistance and checked against the sources above. AI tools change quickly, so confirm features and prices on each vendor's site.