Define the task and finish line
Measure one repeatable task, not “using AI.” State where the work begins, what acceptable output looks like, who reviews it, and where the finished result goes. A meeting summary and a customer-ready follow-up are different tasks because the second carries another review and consequence.
Count the hidden work
Record time spent finding source material, removing sensitive details, writing the request, waiting, checking, correcting, reformatting, and copying the result into another system. Include time another person spends reviewing or repairing it.
- Total minutes from start to accepted result
- Number and seriousness of errors found
- Rework required after the task appeared finished
- Subscription or implementation cost
- Whether the process depends on one person’s undocumented instructions
Use a keep, change, or stop decision
Run at least three comparable attempts. Keep the method when it produces a reliable gain. Change it when the task is sound but the input, instructions, or checking step is weak. Stop when risk, correction, or coordination costs exceed the benefit.
A small time saving can still matter on frequent work. A large saving on a rare task may not justify another subscription or process to maintain.
Try it yourself
Test the same task three times
Choose a recurring, low-risk task and record the current process before changing it.
- Write the task and date in your own private note.
- Record minutes for preparation, asking AI, checking, fixing, and copying the finished work.
- Record the time for the same task without AI.
- Write down any mistakes and choose keep, change, or stop.
Example answer to check
You have finished when you can check these points
- Did you count review and correction time?
- Were the attempts comparable?
- Is the keep, change, or stop decision supported by the record?
Finish: You have three comparable records that include checking and fixing, plus a keep, change, or stop decision.
Try one small change: Use the same private note for two more comparable attempts. Do not count only the quickest result.
Keep these points
- Measure a defined task, not general AI use.
- Count checking, correction, and rework.
- Keep, change, or stop based on repeated evidence.
Continue for free
Try another task or ask a question.
Get a complete practical task each week in the free newsletter. If you are stuck, ask in the free Skool community without sharing private details.
Optional paid help with Ikram Rana
Get help setting up your repeatable task.
Bring the task, the tools you use, and the point where you want to review the result. Discuss a setup with agreed inputs, checks, and a handover you can follow.
Book a call about your taskAgree on what is included and what it costs before work starts. The guides stay free.