Plenty of people try AI at work by throwing a vague request at it and hoping for magic. “Make my report better.” “Help me with emails.” The results are fine, and then they forget about it by Friday.
There’s a calmer approach, and it works better. Instead of asking AI to do your job, you hand it one repeating task and ask it to find the wasted motion. It’s a simple tip from a Reddit post in r/ChatGPTPromptGenius, and I like it because it’s easy to try and easy to judge.
The key idea
Pick something you already do every week. You know it well, so you can tell right away whether the AI’s suggestion is smart or silly. You also get to measure the result against a standard you set before the AI said a word.
There’s a second benefit that people miss. A weekly task gives you a fresh test every seven days. One bad suggestion doesn’t sink you, because you’ll have another shot next Monday. That low pressure is exactly why this habit sticks when bigger AI experiments fizzle out.
The old way vs. the new way
The old way: open a chat, describe a goal in one sentence, accept whatever comes back, and decide by gut feeling whether it was good. Most teams do exactly this, and it explains why the results feel random. Without a standard, a polished answer and a useful answer look identical.
The new way: define what “done well” looks like first, give the AI your real process step by step, ask for specific improvements, and then check the output against your own written criteria. This approach takes about ten extra minutes up front, and it’s faster overall because you stop second-guessing every answer.
The difference is that you’re the one holding the yardstick. The AI becomes a process consultant, not a mystery box.
The five steps 🧭
- Pick one task you repeat every week. Weekly budget review, status report, client follow-ups, whatever keeps coming back. A good test: if you could do it half asleep, it’s a great candidate. Those tasks hide the most wasted motion because you stopped questioning them long ago.
- Write down what success looks like. Two or three sentences is plenty. Be concrete: “Done in 30 minutes, no missed line items, my boss can read it in two minutes.” Numbers beat adjectives. “Fast” means nothing, but “under 30 minutes” is something you can check.
- Give the AI the details and ask it to suggest a simpler process. List your actual steps, even the embarrassing ones like copying the same figure into two files. The more honest the description, the better the advice. If you skip the messy parts, the AI will optimize a process you don’t really have.
- Test the output against your success notes, not against how impressive it sounds. Run the new workflow once for real and time it. Then ask yourself one question: would I be comfortable sending this without a second look?
- Keep what works. Fix what doesn’t. Run it again next week. Jot down one line about what changed, so in a month you can see the trend instead of guessing.
A prompt you can copy ✍️
Here’s the template from the post, lightly adapted:
“I’m trying to improve this recurring work task: [describe task]. My goal is [desired result]. My current process is [steps]. Identify three ways to reduce unnecessary effort without compromising quality. Suggest a practical workflow and explain what a human should still review.”
That last sentence is the sneaky good part. You’re asking the AI to tell you where it shouldn’t be trusted on its own. That gives you a built-in checkpoint instead of blind faith. If the AI says a human should verify the numbers, that’s your cue to spot-check them every time, no exceptions.
One tweak from the comments 💡
A commenter ran this on their weekly budget review and got a cleaner structure. The bigger win came from adding “ignore past versions” to the prompt. If you’ve done a task the same way for months, the AI can drift toward your old habits. Telling it to start fresh pushes it to question steps you’ve stopped noticing.
You can also try asking for “the laziest reasonable version” of the task. It sounds silly, but it forces the AI to strip out anything that doesn’t change the outcome. You can always add steps back if the result feels thin.
A quick example
Say you send a weekly update to your team. Your current process: pull numbers from three places, paste them into a doc, write a summary, reformat, send. Your success note: “Takes under 20 minutes, covers the same five metrics, nobody has to ask follow-up questions.”
You drop that into the prompt. The AI might suggest a fixed template, a single data pull, and a short summary that always answers the same three questions. You test it for one week. The template saves time, but the summary misses context your team likes. Keep the template, rewrite the summary step, and run it again.
By week three, the update might take twelve minutes instead of forty, and you’ll know exactly which step made the difference. You’ll also know which part still needs your own eyes, because the AI flagged it from the start.
That’s the whole loop. Small, boring, and it adds up over a month.
Your move 🚀
Pick one task today. Write your success criteria before you open the AI. Run the prompt, test the result, and keep only what earns its place. If you tweak the prompt and get something better, I’d love to hear what you changed!
Very simply improving your weekly tasks
by u/LearnVironment in ChatGPTPromptGenius