Week 5 · Guide 4 of 5

Automation & Agents

Measure Whether Your Workflow Actually Helps

Field Guide

  • 20–30 minGuided walkthrough

Your Business Results Workflow has a Simple success measure, the line that says how you’ll know the workflow is helping. Sharpen it into one signal you can observe, write down how the work goes today, and keep a short log, so after a few real runs you can say honestly whether working this way helped.

You’ll leave with

A success measure you can record in a minute, a starting point you wrote down before the workflow changed anything, and a measure log with your starting point in it, ready for your first run.

What You Need for This Guide

  • Your saved Business Results Workflow, in My Agent Files or wherever you keep it.
  • A recent time you did this work by hand, or the next time it comes up.
  • Your approved AI tool and a plain-text editor.

Build Your Business Results Workflow

Choose the tool you’re allowed to use

Your approved tool

The tool your company approved.

Pick your approved tool above to see the steps and screenshots for it.

Start guide
5 steps · At your own pace
About saved progress

No account needed. Checkmarks save on this browser and device when browser storage is available. If storage is blocked or full, new checkmarks last until you reload or close this page. Progress doesn’t sync to other browsers or devices. Clearing this site’s browser data removes it, and private browsing may not keep it after you close the window.

Step

Check that your measure is a measure

Open your Business Results Workflow and find Simple success measure in section 1. Your workflow also has a Standard, which asks whether the agent did the work well. The measure asks a different question: did doing the work this way actually help? A run can meet every line of its Standard and still save you nothing, if checking and fixing it takes as long as doing the work yourself.

A measure you can use passes three tests:

  • It’s close to this workflow. Something this workflow can change, such as how long one piece of work takes. “Improve productivity” and “increase ROI” are goals, too broad to record after a run.
  • You can observe it without a dashboard. A clock, a count or a yes or no you can record in a minute.
  • It would look different if the workflow weren’t helping. “The update gets done” is true either way. “The update is checked and ready to send by 10 a.m. on Monday” might not be.

Most measures are one of these kinds: the time from the trigger to a result you’ve checked and corrected, how many pieces you still rebuild by hand, whether something arrives before the moment it’s needed, or whether it reaches everyone who owns an action. Pick one. Two is the most worth keeping by hand. Corrections at your checkpoint are worth noting too, but they show where to fix the workflow rather than whether it helps.

If you’re unsure about yours, start a new chat, attach your workflow and send the prompt. It sorts what you wrote and suggests measures tied to your own Business Result, and you choose.

Check my success measure
My Business Results Workflow is attached or pasted below. Help me check its Simple success measure. Do not change the file.

1. Quote my Business Result and each line under Simple success measure, word for word.
2. For each measure line, say whether it is a measure (did doing the work this way help?), a standard (was the work done well?), an output (a thing produced) or a goal too broad to observe, and say why in one sentence.
3. For each, say what I would actually record after a run: a time, a count or a yes or no. If I couldn't record it in about a minute, say so.
4. Suggest up to two measures that pass all three tests: close to this workflow, observable without a dashboard, and different if the workflow weren't helping. Tie each to a line of my Business Result, and say exactly where its clock starts and stops, or what counts as one.

Use only what my workflow says. Do not suggest numbers, targets, a starting point or results.

[paste your Business Results Workflow here if it isn't attached]

Step

Write down how the work goes today

A measure needs a starting point to compare against. Before your workflow changes anything, write down how this work goes now, from the last time you did it by hand or the next time it comes up.

  1. Decide exactly what counts, so every later run is measured the same way. For a time, say where the clock starts and stops, such as “starts when the meeting ends, stops when I’ve finished reviewing and correcting the follow-up and it’s ready to send.” Include your review, because checking and fixing is where a workflow can lose the time it saves. Stop before anything that waits on someone else, such as an approval or a reply, so a quick run doesn’t look slow. For a count, say what counts as one.

  2. Write down the date, the number and how you got it, in a note for now. Step 3 puts it in your workflow and step 4 starts your log with it. If you timed it or counted it, write “timed” or “counted”. If you’re remembering or guessing, write “estimate”, because an honest estimate is more useful than an exact-looking number nobody measured. If you can’t say at all, time the next run you do by hand, or start your log with your first workflow run and compare the later runs with it.

  3. Work this out yourself. Your agent wasn’t there when you did the work, so any starting point it offers is invented.

Step

Put the measure in your workflow

Write the measure into your workflow, so anyone who reads it, including you next month, knows what success looks like.

  1. Open your Business Results Workflow in your plain-text editor. Under Simple success measure, replace what you had with your measure, where the clock starts and stops or what counts, your starting point and where you keep the log, such as “Logged in Weekly Status Update Measure Log in My Agent Files.”

  2. Under it, add a line that keeps the measure yours: “I record this measure myself. Do not estimate, report or claim time saved or any other result of this measure.” Your agent can’t see your clock or what happened after the chat, so it shouldn’t grade its own impact.

  3. Save the file in place of the old one in My Agent Files, or another folder you’ll find again. If you’ve added your workflow to your AI tool, such as a skill or a Notebook’s References, replace that copy too.

Step

Start your log for your next run

Make a plain-text file in My Agent Files, or another folder you’ll find again, called [your workflow’s name] Measure Log, with one line per run. Each line holds the date, what you measured, the result, whether you timed it or estimated it, and a short note on anything unusual, such as two corrections at your checkpoint or twice the usual notes. Put your starting point on the first line.

  1. Next time the work comes up, start a new chat, attach your workflow and its files, and run it with Run my Business Results Workflow the way you built it. Measure it exactly as you decided in step 2.

    Run my Business Results Workflow
    Use the files I have attached or pasted below for this conversation. My Business Results Workflow says what this work should accomplish, which of my other files and Workflow Cards to use, where to stop for my review and what to return. If my Business Results Workflow is missing, ask me for it before you start. Continue without any other file I've marked "not provided".
    
    MY FILES
    [paste the text of your Business Results Workflow, the Workflow Cards it names, your Safety & Security Rules, Agent Profile and Communication Style Guide here, or attach the files and write their names here. Write "not provided" for a file you don't have yet.]
    
    TASK
    Run my [name of your Business Results Workflow] using the source below.
    [add anything different about this run, or delete this line]
    
    CONTEXT
    [what this run covers, such as which meeting or reporting period, and anything that changed this time]
    
    CONSTRAINTS
    Use the workflow defaults.
    [add a limit for this run only, such as a shorter message, or delete this line]
    
    OUTPUT CHECK
    Use the workflow defaults.
    [add anything extra this run needs, such as one more person to review, or delete this line]
    
    SOURCE
    [paste this run's prepared source here]
  2. Record the run when your clock stops, as you defined it in step 2, not when the agent’s drafts appear. Keep your note to what was different about the run, described the way the data rules allow.

Step

Read your log after a few runs

After three to five runs, compare them with your starting point:

  • It’s helping. Keep going, and describe it with your own numbers, such as “about an hour back each Monday over four runs.” One workflow may save a little time, and several of them, run week after week, add up.
  • No real change. Read your notes for where the time goes. If you spend it correcting the same thing at your checkpoint, change the smallest part of the workflow that explains it, then keep logging.
  • It’s worse. Look before you run it again, starting with your corrections and anything the workflow produces that nobody needs.

For help reading it, fill in the prompt with your measure and log and send it in a new chat. Check each number it gives against your log before you repeat it.

Read my measure log
Here is the measure log for one of my workflows. Help me read it. Do not change it.

My measure: [the measure, with where the clock starts and stops or what counts as one]

Log:
[paste your log lines here]

1. Compare each workflow run with my starting point, using only the numbers in the log. Show your arithmetic.
2. Say whether the runs are trending better, about the same or worse, and how many runs that is based on. If there are fewer than three workflow runs, say it is too early to tell.
3. Point out runs my notes mark as unusual, and say whether the trend changes without them.
4. Quote what my notes say about where time or effort went, such as corrections at a checkpoint.

Treat numbers marked estimate as estimates and say so. Do not invent numbers, causes or savings my log doesn't show, and do not total up time saved beyond what the log supports.

Copy each prompt into a plain-text file in My Agent Files, or another folder you’ll find again, and edit your copies to fit how you work. The next time you build a workflow, write its measure and starting point before its first run.

Measure Whether Your Workflow Actually Helps

Confirm your result

Confirm the outcomes below to finish this guide.

Final checks

Your workflow’s Simple success measure names one or two signals you can record in a minute, with where its clock starts and stops or what counts as one.

Your measure log is saved with your measure, where its clock starts and stops, and your starting point marked timed, counted or estimate, ready for your next run.

Provide Feedback

Thanks. That went straight to the people who write these guides.

Next in Week 5

Set the Stop Points in Your Workflow

Continue in the suggested order, or choose another guide for your task.

View Week 5 guides