Five prompting habits that make AI useful at work

The difference between "AI is a gimmick" and "AI saved my afternoon" is usually not the tool. It's the instruction. People who get consistent results from AI assistants share a handful of habits. None of them are clever. All of them are learnable in an hour.

The mental model that makes them click: treat the assistant like a capable new colleague who has read everything and knows nothing about your business. You wouldn't hand that person a two-word request and expect a finished deliverable. You'd brief them.

Habit 1: Give it a role and the context

Start by saying who the assistant is and what situation it's in. "You are an operations manager at a small home-services company writing to a customer whose appointment was moved." The role sets tone and expertise. The context sets what matters.

Then give it the material: the facts, the previous email, the notes from the call, the relevant section of your procedures. The output can only be as specific as the input.

Weak: "Write an apology email."

Better: "You are the office manager at a small plumbing company. A customer's Tuesday appointment was moved to Thursday because of a staff illness. Write a short, warm email apologizing, confirming the new time (Thursday, 9 to 11 a.m.) and offering a 10 percent courtesy discount on this visit. Plain language, no corporate phrases."

Habit 2: State the task and the format

Say exactly what you want back and how it should look. Length, structure, headings, bullet points or prose, a table with named columns, a subject line, a particular reading level. Formatting instructions are the cheapest way to save editing time.

Example: "Summarize this meeting transcript as: a three-sentence summary, a bulleted list of decisions, and a table of action items with columns for owner, task and due date. Flag anything that was discussed but not decided."

Habit 3: Show an example of good

If you have a past piece that sounds right, your best proposal, a reply a customer thanked you for, a report your board liked, paste it in and say "match this voice and structure." One example teaches more than a paragraph of adjectives. Three examples will outperform most style guides.

This is also how you build a voice guide for your business: collect five pieces that sound like you, and tell the assistant to use them every time.

Habit 4: Ask for a critique before you edit

Before you read the draft closely, ask the assistant to review its own work: "What's weak about this? What would a skeptical reader push back on? What's missing?" Then ask it to revise. This two-step pattern routinely improves the first draft more than any single clever instruction, and it trains you to read the output critically.

A related habit: ask for options. "Give me three versions: one formal, one friendly, one very short." Choosing is faster than writing.

Habit 5: Iterate, then save what worked

The first answer is a starting point. Tell it what to change: "Shorter. Lead with the decision. Remove the second paragraph. Use 'you' more." Each round takes seconds.

When a prompt produces something good, save it. Keep a shared document of prompts that work for your team's recurring tasks, with the role, context, format and an example filled in, and blanks for the facts that change. Within a month you'll have a library that lets a new hire produce consistent work on day one.

Two things that aren't habits

Facts still get checked. The assistant will state a date, a number or a rule with the same confidence whether it's right or wrong. If it matters, confirm it from a trusted source. Good prompting improves the writing, not the truth.

Sensitive information stays out. Customer financial or health details, employee records, passwords and anything under a confidentiality agreement don't go into a tool that isn't approved for them. If your business doesn't have a written rule for this yet, here's what belongs in one.

Start tomorrow morning

Pick one task you do every day that involves writing or reading. Brief the assistant like a colleague: role, context, task, format, example. Ask it to critique and revise. Save the prompt. Repeat for a week, and the gimmick becomes a tool.