|
AI Workflows | Tuesday: Context and harness management
Working backward helps you check whether AI understood the assignment.
Google's general counsel emphasized human judgment in today's Axios interview.
I have a practical way to bring my own judgment back into an AI project: start at the end.
For something I'm writing, I'll read the last sentence first, then the sentence before it. Then I'll read the final paragraph, followed by the next-to-last paragraph, and keep working backward.
|
|
Start at the end.
1. Last sentence
2. Previous sentence
3. Final paragraph
4. Previous paragraph
|
I need that time outside AI to get my own thinking going again. This helps me see whether AI understood the mission. It also helps me reinsert critical thinking into my handling of the finished work.
Try it with a customer proposal. Suppose your assignment was to recommend a small pilot. The closing paragraph asks the customer to commit to a companywide rollout.
Start there. Does that request match the decision you wanted the customer to make? Work backward through the proposal and examine what supports it. You might discover that several sections assume a commitment the customer hasn't made.
Now you have a specific correction: bring the proposal back to the pilot. You can also identify material worth preserving, such as the approved pricing and the customer's stated problem.
That review gives you something useful to carry into Tuesday's skill: context and harness management.
Context is the information AI needs to do the job, including the goal, source material, and decisions you've already made. The harness is the working setup: standing instructions, connected sources, available tools, and the points where you review the work.
Make your review part of that setup.
When you return to AI, have it turn your findings into a short, updated project brief. It should state the intended outcome, what remains approved, and what needs to change. Read that brief yourself before authorizing another revision.
For example, ChatGPT Projects can keep related chats, files, instructions, and connected sources together. Have AI use the material already available in your project to prepare the brief. Save the approved response through its message menu using Save to project or Add to project sources.
Here's an assignment you can adapt after your independent review:
|
Use the current proposal, approved source material, and my review notes to prepare an updated project brief. The goal is a small pilot. Preserve the approved pricing and the customer's stated problem. Identify every passage that assumes a companywide rollout. Show me any conflicts or missing information before revising. After I approve the brief, revise the proposal and provide a short change log. Keep the previous version available. The revised proposal is for my review before it goes to the customer.
|
On the next revision, ask AI to consult that approved brief and flag conflicting instructions. Afterward, read the document forward to check the full argument. Verify factual claims against their sources.
For a manager or business owner, make the review concrete. Ask the person responsible for the work to explain what they changed and why. Keep the approved decisions available with the project so the next person can understand them, too.
Take one AI-assisted document today and read its final sentence first. Before returning to the chat, write down what that sentence needs to accomplish.
|