TeamLogic IT blog

Four Everyday Ways to Get Real Time Back With AI at Work

rwilson@tlitna.com (Randall Wilson) — Wed, 11 Nov 2026 15:00:00 GMT

Most of the writing in a small business is ordinary work: the email about a late order, the notes from this morning's meeting, the procedure nobody has written down. If your company has given you an approved AI tool, that ordinary work is where it can give you real time back. Our earlier article on the five golden rules covered what is safe to put into an AI tool. This one covers how to use it well, with four patterns from Module 2 of our education series, Personal Productivity Wins.

Pattern 1: Emails built on situation, relationship and outcome

A usable email draft starts with three things: what happened, who you are writing to and what the message should achieve. Here is the example from our Module 2 handout:

"Draft an email to a longtime customer explaining their order ships three days late. Warm but professional, take ownership without over-apologizing, offer expedited freight at our cost, under 120 words."

Why does this work? Your AI tool knows nothing about this customer or what you are willing to offer. Leave those details out and it fills the gaps with safe, generic language. Spell them out and every constraint shows up in the draft: the relationship, the tone, the apology, the offer and the length. That makes this pattern most useful on hard messages.

For replies, paste the thread (as long as nothing in it is sensitive) and add "draft my reply — I want to say roughly this..." followed by your point in plain words. Then read the draft out loud before you send it. Reading aloud catches stiff phrasing that silent reading skips.

Pattern 2: One prompt, four outputs from your meeting notes

After a meeting, the job people put off is turning notes into something others can act on. This prompt does that in one pass:

"Here are my rough notes. Produce: (1) a five-line summary, (2) decisions made, (3) action items as a table with owner and due date, (4) a short follow-up email to attendees."

Asking for four specific outputs turns one set of notes into a summary, a decision record, a task list and a follow-up email. Your notes do not need to be tidy. Fragments are fine, because organizing them is the AI's job.

Picture a Monday huddle about a delayed supply delivery. You jot down who is calling the supplier and what the backup plan is. Paste those fragments in and the follow-up is drafted while the details are fresh.

Two cautions. First, check the action table. If your notes named no owner or date, the AI may guess one, and a guessed due date in a follow-up email can quickly become a real commitment. Second, a transcript of a sensitive meeting is still sensitive. Wanting only a summary does not make a personnel conversation safe to paste in.

Pattern 3: Give a skeleton, get two first drafts

A blank page is hard because you are making every decision at once. Instead, give the AI a skeleton: the purpose of the document, who will read it, the three to five points that must appear and a rough length. Then ask for two versions in different structures.

The skeleton covers the decisions only you can make. The AI handles the arrangement. Asking for two versions helps because picking beats writing; it is far easier to react to two options than to invent one from nothing.

Say you need a one-page procedure for handling after-hours calls, written for part-time evening staff. List the points it must include, ask for two versions and choose the clearer one.

Then try the most underused move in AI writing: "Ask me five questions that would make this draft better." The questions point at the gaps in what you provided, such as a missing deadline. Answer them and run it again.

Pattern 4: Rewrite by naming the change you want

"Make this better" means something different to everyone. Name the change instead: "Shorter," "plainer," "for a customer" or "for an executive." A named change gives the AI one clear job and gives you a clear way to judge the result.

Then there is the de-escalation pass. When you have written something in frustration, paste the draft in, ask for the professional version and send that one. You keep your point and lose the heat. Think of the message you typed to a vendor after a third missed delivery: the facts may be right, but the tone could cost you the relationship.

With numbers, add "keep every number exactly as it is" and then check them yourself. Rewrites are where figures quietly change.

Where to start: pick two triggers

Patterns only help if you remember them. The simplest way is to tie each one to a moment that already happens in your day:

About to write anything longer than three sentences: draft with AI first.
Just left a meeting with notes: get the summary and actions before you forget.
Staring at a blank page: use the skeleton prompt and ask for two versions.
About to send something written in frustration: run the de-escalation pass.
Re-reading a long document: ask for a summary, then ask questions.

Pick two triggers and commit to them for two weeks. Habits form more easily around a moment you can recognize than around a good intention.

The rules from our first article ride along with all four patterns. Use the account your company provides. Nothing sensitive goes in, so use made-up sample text when in doubt. AI drafts and you decide; everything gets your review before it goes anywhere real.

Watch the Module 2 video and download the handout to keep the example prompts close by. If you would like to talk about how these patterns fit your team's work, let us know.

The Five Golden Rules for Using AI at Work, Explained

rwilson@tlitna.com (Randall Wilson) — Fri, 06 Nov 2026 15:00:00 GMT

AI tools have arrived in most workplaces faster than anyone wrote rules for them. Someone on your team is probably already using one to draft an email or summarize a long report. Most of the time that is a good thing. The trouble starts when nobody has said out loud what is fine and what is not.

Why each rule comes with a reason

These five rules come from Module 1 of our AI training at TeamLogic IT (watch Module 1), and they fit on a single page (the five golden rules handout). We explain each one, because a rule someone understands survives contact with a busy Tuesday. A rule they merely obey does not. So below, each rule appears exactly as it reads on the handout, followed by the reason behind it and what it looks like on an ordinary workday.

1. Use the company account

Use the company account. Work goes through the tools and accounts the company provides. Personal accounts are for personal life.

When you sign in with your work account, your company can see which tools are in use, control who has access and put protections in place behind the scenes. A personal account has none of that. If you leave the company, anything you pasted in leaves with you.

Picture a sales coordinator who polishes a client proposal in a free chatbot on her phone because it was already open. Nothing bad happens that day. But the proposal now sits in an account the business doesn't know about and can't manage. The company account takes the same few seconds and keeps the work where it belongs.

2. Know what never goes in

Know what never goes in. Customer data, pricing, contracts, employee records, passwords, and anything under a confidentiality obligation — unless the tool is approved for it.

Typing something into an AI tool is a lot like sending it to an outside company. Depending on the tool and its settings, what you paste may be stored or kept longer than you expect. For most of your work, that is fine. The items on this list are different. Many are covered by contracts, privacy laws or promises your company has made to its customers.

The closing words matter too. Some tools are approved for sensitive work, and there the rule bends on purpose because someone has checked first.

Say you want help writing a polite late-payment reminder. You could paste in the customer's name, account number and balance. Or you could ask for a template with blanks and fill them in yourself. The second way gets you the same email without the customer's details leaving your hands.

3. Review before it leaves you

Review before it leaves you. Anything sent, published, or acted on gets your eyes first. You own the output.

AI writes with the same confidence whether it is right or wrong. It can misread your request, pick the wrong tone or add something you never asked for. That is harmless on your screen and costly in a customer's inbox.

"You own the output" is the heart of this rule. If an email goes out under your name, the customer will not care which tool wrote the first draft. It is your email.

Imagine a service manager asking AI to summarize a long email thread for the team. The summary reads well, but it drops the one detail that changes the plan: the customer moved the install date. A two-minute read before sending would have caught it.

4. Verify facts that matter

Verify facts that matter. Numbers, names, dates, citations, legal or technical claims — check them against a real source.

AI tools predict what a good answer should look like. Usually that lines up with the truth. Sometimes it produces a figure, a date or a reference that sounds right and simply isn't. The tool will not flag its own mistake, so the check has to come from you.

This doesn't mean fact-checking every word. It means checking the facts that would cause harm if they were wrong.

If AI helps you write a quote and lists a product's warranty as three years, confirm it on the manufacturer's page before the quote goes out. Checking takes a few minutes. Correcting a wrong number after a customer has relied on it takes much longer.

5. Ask when unsure

Ask when unsure. New tool? Odd request? Not sure if data is safe to use? Ask your AI point of contact before, not after.

New AI tools keep appearing, and real work throws up situations nobody planned for. This rule is the safety net under the other four. It only works if asking feels normal, so learn who your AI point of contact is before you need them.

"Before, not after" is the important part. A question asked first costs a minute. The same question asked after the data is in the wrong place turns a quick answer into a cleanup job.

Suppose a new browser add-on promises to summarize every page and email you open. A short message to your point of contact asking whether it is okay to install is the right move. That is much easier than explaining later why the add-on could read your inbox.

Where these rules go next

Taken together, these five rules are your company's acceptable-use policy in draft form. They cover which tools to use, what stays out, who checks the work and where to go with questions. Module 5 is where they become the written one.

Until then, three small steps put the rules to work:

Check that you are signed in to your AI tools with your work account.
Find out who your AI point of contact is.
Keep the handout (five golden rules handout) somewhere you will see it.

If you would like to talk through how these rules apply to your team, let us know. We are happy to help.