Start with one job, not everything
The biggest mistake in month one is trying to use AI for everything at once. Pick one job that happens every week and is a little annoying. Writing follow-up emails. Turning notes into a first draft. Summarizing a long document. Answering the same five customer questions.
Choose that one job together as a team. Write it down somewhere everyone can see. Say plainly: this is what we are practicing this month.
Everything else can wait. One job done well beats ten jobs half tried.
A quick note on setup: if you have not done it yet, the free AI game plan is a free 15-minute Zoom call where we look at your business and point to where AI helps first. Nothing is set up on that call. It just gives you a clear starting point.
Week one: log in and get comfortable
Week one is about comfort, not output. Ask each person to open their AI account and use it once a day for something small. Rewrite an email. Ask it to explain a term. Draft a short reply.
The goal is that nobody feels awkward typing into the box. That awkwardness fades fast with a few days of use.
What to watch for in week one:
- People forgetting their login. Have them save it or use the same sign-in they use for work.
- Someone trying one prompt, getting a so-so answer, and quitting. Remind them the first answer is a draft, not a verdict.
- Personal accounts sneaking in. Make sure the team is on the company account, not their own.
At the end of the week, ask one question in a team chat: what did you use it for? Keep it light. No reports.
Week two: put the one job into the routine
Now make the chosen job an AI job. If it is follow-up emails, the rule becomes: draft it in AI first, then edit and send. If it is meeting notes, the rule becomes: paste the notes in and ask for a summary before you file them.
Be specific about where AI fits. Vague instructions like use it more do not stick. Clear ones do.
This is also the week to feed it your context. The AI does not know your business on day one. Have the team paste in your service list, your common customer questions, your tone. A short company cheat sheet that people can drop into a chat goes a long way.
Expect some rough answers. That is normal. The fix is usually more context, not a different tool.
Week three: check the work and fix the habits
By week three, people are producing real drafts. Now the team has to learn to check them. AI can be confidently wrong, especially on numbers, names and details. The rule for the whole month and beyond: a person reads it before it goes out.
Spend a few minutes in a team meeting on this. Show one good output and one wobbly one. Ask the group what was missing and how they would have prompted it better. People learn faster from a shared example than from a manual.
Watch for two habits that creep in:
- Copy and paste with no read-through. Catch it early.
- Putting sensitive client files into a public chatbot without thinking. If you are a law, medical or finance office, talk through the options, including zero data retention or private AI on a machine in your office so files never leave.
If someone hits a wall, this is what the support level is for. A real person to text or email with a how do I question.
Week four: widen it a little and write it down
Week four is when you add a second job, now that the first one feels normal. Keep the same pattern: pick it, name it, practice it.
This is also the week to write a short company AI policy. Nothing heavy. A page that covers which account to use, what not to paste in, and that a person always checks the output before it goes to a client. Having it in writing stops arguments later and helps new hires.
Finish the month with a short review. What worked? What felt clunky? What should we drop? Drop the things that did not help. Keep the ones that did.
A normal week by now looks like this: people drafting in AI, editing, sending, and asking it questions through the day. Not dramatic. Just steady.
What to watch out for all month
A few things trip teams up in the first month. Keep an eye out.
- Too many tools. Stick with the one you set up. Do not add more yet.
- No owner. Someone has to be the go-to person, even if it is just you.
- Silent quitters. People who tried once, got a bad answer and stopped. Ask them directly what happened.
- Expecting magic. AI is a helper that drafts and suggests. It is not a replacement for judgment.
- Skipping the check. The single most important habit is reading before sending.
If the team stalls, that is not a failure. It is the normal dip. A coaching session or a support call gets you moving again, and you can move up or down levels anytime.
Keep going past day thirty
Thirty days is enough to build a habit, not to finish. After the first month, keep the routine going: one new job at a time, a short review each month, and the policy updated as you learn.
If you want help keeping it on track, the support level gives you a real person to text or email plus a check-in every month. If you would rather we build and run things, the done for you level covers that.
Either way, start with the free AI game plan if you have not already. It is a free 15-minute Zoom call, no cost, no pressure, and it tells you which level fits. You get your price in writing after the call, before anything starts.