Name the business result your work should create
In Week 1 you built your Agent Profile, so your agent understands your work. In Week 2 your Communication Style Guide taught it to communicate like you, in Week 3 your Safety & Security Rules set how it works with your information, and in Week 4 your Reusable Workflow Card taught it to follow your process. Nothing you built gets left behind. Company policy and your Safety & Security Rules still govern, and nothing this week weakens either.
This week’s upgrade is “It supports business results.” This week you’ll take the pieces you’ve already built, point them at a result that matters to your work, and decide exactly where you stay in control. Your agent prepares the work, and decisions stay with people.
AI is good at producing things: reports, summaries, emails, plans and slides. Because they look finished, it’s tempting to mistake the thing AI produced for the result the business needed, and a polished output can still miss the point. The output is what AI creates to help. The business result is what gets accomplished. You need both, and they aren’t the same thing.
The session puts five questions in order, using Karen Wolfram, a director of client enablement who runs customer training programs and has finished a customer program meeting. You can download her workflow in step 2.
- Task: What needs doing now? Process this meeting.
- Process: How should this kind of work be done every time? Her Week 4 Post-Meeting Program Follow-Up card owns that.
- Business Result: Why does the business care? The right people are informed and know what happens next.
- Output: What should AI produce to help? Only the follow-up emails that are needed.
- Measure: Did working this way help? The time from the end of the meeting to review-ready follow-up.
The Standard in your Workflow Card asks whether the work was done well. The Measure asks whether doing it this way actually helped. If Karen used to finish a Friday meeting at 2:00 and send the follow-up at 5:00, and now has it out by 3:00, that’s two hours of her Friday back from one recurring piece of work. One modest signal you can observe is enough.
Now choose one recurring piece of work and write down the business result it should create. The workflow you built in Week 4 is a good place to start, or pick another recurring task you know well. Ask why the business needs the output: what should be better, easier or clearer because the work got done? Answers this practical are plenty:
- The right owner sees a decision that’s needed before the deadline.
- The customer receives an accurate update without internal-only information.
- A manager gets a decision-ready summary instead of thirty pages of raw material.
- A weekly report comes out consistently enough that you spend your time reviewing it instead of rebuilding it.
If what you wrote reads like “create the report” or “write three emails,” that’s an output, so ask why once more. Keep it useful, observable and connected to real work rather than a strategy statement. If nothing comes to mind, ask what you’re repeatedly rebuilding, chasing, sorting out or piecing together by hand today, because that’s often where the value is hiding. In the live session, think privately and keep confidential details out of the chat.
Start your workflow: result, trigger, inputs and steps
Now build the workflow around the result you chose. Aim for a first usable version, not a perfect one. The template is deliberately flexible: Karen’s is one example, and yours might support a leadership brief, a customer update, an action plan, a recurring report, a recommendation or a handoff. The structure stays the same, and the business result decides what goes inside it. Use low-risk, permitted information, and where the real work needs information you can’t use with AI, write sanitized placeholders.
Download the template, open it in a plain-text editor and save it in My Agent Files, or another folder you’ll find again, under your workflow’s name, such as Meeting Follow-Up Business Results Workflow. If it opens as a preview in your browser, copy its text into a new plain-text document and save that. Write over each line in square brackets as you go, and leave How I Want My AI Agent to Use This Workflow as it is.
YOUR RESOURCE
Business Results Workflow template
Download fileThe blank Business Results Workflow Raymond uses in Session 5. Fill in its sections for one piece of recurring work: the business result, trigger, inputs, steps, your review checkpoints, standard, output and rules.
For the level of detail, you can also download Karen’s Meeting-to-Action Closeout, the workflow the session runs live. It points the four Workflow Cards she built in Week 4 at one result: everyone who needs follow-up from a customer meeting gets it, without Karen rereading the transcript and rebuilding every message. Hers is long because her work has three checkpoints, so read it beside yours without pasting it into a chat, and write your own.
YOUR RESOURCE
Karen's example: Meeting-to-Action Closeout Business Results Workflow
Download fileKaren Wolfram's completed workflow from Session 5, which turns a customer program meeting into reviewed follow-up using her four Week 4 Workflow Cards. Read it for the level of detail, then write your own.
At the top, replace the name or role and Your Workflow Name with a short name you’ll recognize later that says what the workflow is for, such as Weekly Leadership Decision Brief, Customer Feedback Follow-Up or Monthly Operations Review. Then finish the opening sentence, “This workflow helps me turn [recurring work or situation] into [business outcome].”
Under 1. Business Result, finish “Help me [describe the work] so that:” with the result from step 1, and add a second outcome only if you need one. Under Simple success measure, write one signal you can observe, such as “important decision needs are surfaced before the weekly review” or the time from the end of the meeting to review-ready follow-up. “Improve productivity” and “increase ROI” are goals, too vague to observe. Under Complete when, say what must actually be true before the result counts. Karen’s is complete only when she confirms she has sent the approved messages herself and routed or flagged the remaining actions, because drafts alone aren’t the result.
Under 2. Trigger, finish “Use it when” with the event or situation that tells the agent this workflow applies now, such as after a recurring meeting, when a weekly report is due or when new customer feedback arrives. Under Do not use it when, name where it stops applying: a different workflow fits better, the information isn’t permitted for AI, the work needs a specialist, or the stakes are higher than this workflow was designed for. Keep the How I start it line, with your workflow’s name in it and [current information] replaced by what you’ll give it each time, such as the attached meeting notes.
Under 3. Inputs, name the kinds of current information the workflow works from, such as notes, a transcript, data or a request, and the details that identify a run, such as the customer, project or period. Under Reusable AI assets, list only the files that matter to this result, by name: your Agent Profile, Communication Style Guide, Safety & Security Rules and the Workflow Cards it uses. One instruction, one best home: if a rule already lives in one of those files, the workflow names the file and doesn’t copy the rule. Today’s facts, such as the customer’s name, this week’s deadline or this run’s recipients, stay out of the workflow and go in your Context Sandwich each time (the Task, Context, Constraints and Output Check you give each run).
Under 4. Workflow Steps, keep Before starting, which tells the agent to check its inputs and ask any blocking questions together before it produces anything. Then write the steps with verbs you could check afterward, such as identify, extract, compare, organize, prioritize, draft, verify, route, flag and prepare. If a Workflow Card already covers part of the process, name it rather than copying it. Karen’s first step is to run her Post-Meeting Program Follow-Up card, and her workflow continues from there: identify who actually needs follow-up, then draft only the communications that are required. Your Workflow Card owns how that work is done, and this workflow connects it to the result. Add, remove or reorder steps to fit, and leave out steps that would only make it look sophisticated.
Set your checkpoint, standard, output and rules
A Business Results Workflow tells your agent when to stop as well as what to do. Suppose the agent reads a target date as a commitment, assigns an owner nobody confirmed or treats a recommendation as a decision. If that flows straight into five emails, a report and a leadership brief, the error is multiplied, and the result looks more complete while the mistake is still in it. Put a human checkpoint where a wrong interpretation would change what happens next, so you correct it once, at the foundation.
Under 5. Human Review / Decision Points, fill in the checkpoint’s four lines:
- Pause after: the step or working result where the agent stops.
- Show me: what you review or decide there, such as facts, numbers, dates, owners, approval status, recipients or risks.
- Continue only when: the signal that lets it go on, such as typing Reviewed, choosing an option or confirming the numbers.
- That confirmation does not authorize: what your signal still leaves undecided, such as approvals, commitments or sending.
If your only checkpoint is a final review before you use the result, that’s fine, as long as it’s written down. Copy the checkpoint if your work needs another stop, and delete Additional checkpoints if it doesn’t. Under I remain responsible for, list the decisions, approvals and sending that stay yours. Don’t let one short reply authorize more than you intended.
Under 6. Standard, keep the template’s lines and add the one or two that matter most for this result, such as concise, decision-ready, audience-appropriate or clear about owners and dates. Under Check before presenting, write what the agent must verify before it shows you anything. The Standard asks whether the work was done well, and your success measure asks whether it helped.
Under 7. Output, name the deliverables, their format and their audience, then list them under Order of outputs with any review needed before the next one. Create only the outputs the result actually needs. More AI output isn’t more business value, and a workflow that asks for “follow-up” can come back as a thirteen-page package when three short emails would do. Say what to leave out too, on the Deliverable(s) line or as an Additional rule in 8. Final Rules, such as internal-only information in a customer message or detail the audience doesn’t need.
Read 8. Final Rules rather than rewriting them. They’re the baseline the course has built: don’t invent missing information, keep uncertainty visible, stop at your checkpoints and don’t send, publish or approve anything without permission. Add a rule only if this workflow needs its own, and delete the Additional rule line otherwise.
Under One-Line Workflow Rule, sum up the result and where you stay in control in one sentence. Karen’s ends “Karen reviews and sends.” Yours doesn’t need to sound clever, as long as it captures what the workflow is for.
First usable version: stop and scan the whole workflow. Can you tell what it accomplishes, when it applies, what it needs, what the agent does, where it stops and what your confirmation does and doesn’t authorize, what good looks like and what it returns? If a Workflow Card covers part of the process, check that it’s named rather than pasted in, and that your Safety & Security Rules are named too. Check that no current facts are baked in. Delete any line still in square brackets and save the file. It doesn’t need to be perfect to be usable, and running it in step 4 will show you what needs work.
Run your workflow and stop at your checkpoint
Now run your workflow the way the session’s demonstration does: one current example of the work, a lean Context Sandwich, and your workflow and files carrying the rest. Use something you’re allowed to use, such as permitted notes from a recent meeting or this week’s figures, prepared the way the data rules and your Safety & Security Rules say, with words such as “proposed” and “pending” left exactly as they are. If you don’t have an example you may use, write a short made-up one.
Start a new chat and copy Run my Business Results Workflow. Attach your Business Results Workflow, the Workflow Cards it names, your Safety & Security Rules, Agent Profile and Communication Style Guide, or paste their text under My Files, and write “not provided” for any file you don’t have yet. If the message is too long, attach the files rather than pasting them. If your tool still won’t take them all, send your Business Results Workflow, the Workflow Cards it names and your Safety & Security Rules, and write “not provided” for the others. Under Task, write your workflow’s name, and under Context, say what this run covers. Leave Constraints and Output Check on the workflow defaults unless this run needs a one-time change, then paste your prepared source at the end and send it.
Run my Business Results WorkflowUse 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]
Your agent may ask you questions before it produces anything. That’s the Before starting check in your workflow. Answer in the same chat, or say you don’t have something so it stays marked as missing.
When the agent reaches your checkpoint, it should stop and show you what you listed under Show me. Check it against your source now, before anything is built on it. If a fact, owner, date or status is wrong, correct it in the same chat and ask to see the corrected version. Give your confirmation, such as Reviewed, only when it’s right. If the agent went past your checkpoint without stopping, don’t use what it produced after that point, and note it for step 5.
After your confirmation, check the second stage against the questions the session asks:
- Did it create only the outputs that were actually needed?
- Did each person or audience get only what’s relevant to them, with internal-only information kept out of anything customer-facing?
- Did pending items stay pending, and did any target become a commitment?
- Does everything agree with the version you reviewed?
- Did it claim to have sent, approved or completed anything?
If it asks you to confirm the work is complete, tell it this was a test run and nothing was sent, so the status stays pending. Note anything that fails these checks for step 5.
Diagnose what went off track and fix the smallest part
If something went wrong, don’t solve it by throwing more instructions at the agent. Diagnose first, then change the smallest part of the workflow that explains the failure. These are the eight the session names:
- Your Business Result is really an output: ask why the business needs it, and rewrite it as the effect the output supports.
- The workflow didn’t know when to run, or kept asking for what you thought was obvious: clarify the Trigger and name the inputs it needs.
- It’s become a second copy of your Workflow Card: name the card, and let the card own the detailed process.
- Work was built before you reviewed the foundation, or nobody knew what your confirmation meant: move the checkpoint, and define what the confirmation does and doesn’t authorize.
- Your success measure is vague, such as “improve productivity”: choose one modest signal close to the workflow.
- The output is overbuilt: go back to Output and remove the reports, tables, summaries and emails that don’t help.
- Today’s facts are baked into the workflow, such as a customer’s name or this week’s recipients: move them to your source or Context Sandwich.
- The workflow lets AI approve, commit or decide: rewrite the boundary so the agent prepares and you, or whoever is authorized, decide.
Make any change in your saved file, because a chat doesn’t change it. Then start a new chat, send Run my Business Results Workflow again with your updated workflow, your other files and the same source, and check the checkpoint and the second stage again. If everything checked out the first time, there’s nothing to fix.
Save the workflow in My Agent Files. You can also copy Run my Business Results Workflow into a plain-text file there with your workflow’s name filled in, and edit it to fit how you run this work. Next time the trigger comes up, start a new chat with your files, replace the old details with the new run’s source and review at your checkpoint again.
Then watch your success measure on real runs. Your test shows that the workflow behaves the way you designed it: it stops, it builds on the version you reviewed and it skips outputs nobody needs. Whether it actually helps, such as how long follow-up takes you now, is something you observe over time. Don’t let the agent grade its own business impact because the output looks impressive.
This week’s upgrade, Let Your Agent Interview You for Your Business Goals, has your agent ask what you’re measured on and why until it reaches the business goals underneath, then check your workflow against them.
Confirm your result
Confirm the outcomes below to finish this guide.
Final checks
You have a saved Business Results Workflow for one recurring piece of work, whose business result names what should be better because the work got done, with one simple measure you can observe.
You’ve run it on a current example, and you can point to where it stopped for your review and what your confirmation did and didn’t authorize.
Provide Feedback
Thanks. That went straight to the people who write these guides.