Map where AI helps in your work

People who try an AI assistant on a few random tasks often conclude it is either magic or useless. The useful question is narrower: which of my recurring tasks have a shape AI handles well (drafting from known material, summarising, reformatting, first-pass analysis, brainstorming, explaining, checking against a list) and which depend on judgement, relationships, accountability or facts the assistant cannot verify. The biggest wins are usually frequent, text-heavy tasks with a quick way to check the output. Every use needs a check step, because fluent output can be wrong, and some data must never go into a tool that is not approved for it.

Map where an AI assistant can help in my work.

Only if [TOOLS_AVAILABLE] is given: Tools I can use: [TOOLS_AVAILABLE] Only if [DATA_CONSTRAINTS] is given:

1. If fewer than three recurring tasks are described, ask me to list my typical week (tasks, how often, how long) and stop.
2. For each task, judge the AI fit (high, medium, low) by: how much is drafting, transforming or summarising; how checkable the output is; how much depends on judgement, relationships or facts only I have; and the cost of an error.
3. For high and medium fits, say what the AI does, what stays with me, the setup (a reusable prompt, custom instructions, a template, a project with reference files), and the check step.
4. Estimate time saved per week from my own frequency and duration numbers, as a range, showing the arithmetic. If I gave no numbers for a task, say "not estimated" rather than guessing.
5. Rank by estimated time saved, adjusted down for error cost.
6. Write starter prompts for the top three, and a two-week pilot to test them.

• Respect the data constraints strictly: if a task needs restricted data, either propose a way to do it without that data (anonymised, structure-only, synthetic sample) or mark it "not with current tools" and say why.
• Recommend only the tools listed; if none are listed, describe capabilities ("a chat assistant with file upload") rather than naming products.
• Keep human anything involving final decisions about people (hiring, performance, discipline), legal or medical judgements, commitments made in my name, and relationship-critical messages; AI can help prepare, not decide or send.
• Be honest about low fits; do not stretch AI into every task.
• Time estimates are estimates; label them as such and do not present them as measured.
• Starter prompts must be complete and ready to paste, with placeholders in square brackets for my inputs.

Ranked map

A table: Rank | Task | Fit | AI does | I do | Setup | Check step | Time saved per week (estimate).

Keep human

Tasks with a low fit, each with a one-line reason.

Starter setups

For each of the top three: a heading and the prompt in a fenced block.

Data cautions

Bullets: what not to paste, and the workaround for each affected task.

Two-week pilot

A short plan: which tasks, how to track time before and after, what quality checks to log, and how to decide whether to keep each one.