---
title: Four Everyday Ways to Get Real Time Back With AI at Work
description: Four practical patterns for using your company's AI tool on email, meeting notes, first drafts and rewrites, with example prompts you can copy.
---

<https://learn.tlitna.com/blog>

# [Four Everyday Ways to Get Real Time Back With AI at Work](https://learn.tlitna.com/blog/four-everyday-ways-ai-at-work)

 Written by [Randall Wilson](https://learn.tlitna.com/blog/author/randall-wilson) | Nov 11, 2026, 3:00:00 PM

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](https://learn.tlitna.com/blog/five-golden-rules-ai-at-work) 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](https://learn.tlitna.com/share/hubspotvideo/409255083755) and [download the handout](https://learn.tlitna.com/productivity-wins-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.

[View full post](https://learn.tlitna.com/blog/four-everyday-ways-ai-at-work)

```json
{
  "@context" : "http://schema.org",
  "@type" : "BlogPosting",
  "author" : {
    "@type" : "Person",
    "name" : "Randall Wilson"
  },
  "dateModified" : "2026-11-11T15:00:00.990Z",
  "datePublished" : "2026-11-11T15:00:00Z",
  "headline" : "Four Everyday Ways to Get Real Time Back With AI at Work",
  "image" : {
    "@type" : "ImageObject",
    "height" : 630,
    "url" : "https://246175627.fs1.hubspotusercontent-na2.net/hubfs/246175627/blog-title-cards/card-four-everyday-ai-patterns.png",
    "width" : 1200
  },
  "mainEntityOfPage" : "https://learn.tlitna.com/blog/four-everyday-ways-ai-at-work",
  "publisher" : {
    "@type" : "Organization",
    "logo" : {
      "@type" : "ImageObject",
      "height" : 60,
      "url" : "/hs/hsstatic/content_shared_assets/static-1.4092/img/default-amp-logo.png",
      "width" : 60
    },
    "name" : "TeamLogic IT blog"
  }
}
```