AI: Handing it off (Part 2)

In Part 1, I wrote about talking to AI, staying in the conversation, reviewing every step, treating the first answer as a draft. That's the right mode for most day to day tasks. But it's not the only mode, and tools like Cowork and Claude Code are built for a different one entirely.

Handing it off isn't a lazier version of talking to it. It's a different skill, for a different kind of task, and it comes with its own set of rules.

The shift from steps to goals

Talking to AI means giving instructions one piece at a time. Handing it off means giving a goal and letting the AI figure out the steps. Instead of "write this paragraph," it's closer to "research this topic, pull the relevant data, and put together a summary." You're not writing the recipe anymore. You're describing the dish.

This is sometimes called agentic use. The AI is acting more like an agent working toward an outcome than an assistant responding to a single prompt. It can plan, use tools, and take multiple steps on its own before coming back to you.

Good guardrails matter more than good instructions

When you're talking to AI, a vague prompt just gets you a mediocre answer you can immediately correct. When you're handing something off, a vague goal can send it in the wrong direction for a while before you notice, because you're not watching every step.

This is where clear scope matters. What's in bounds. What's off limits. What "done" actually looks like. The upfront time spent defining that is what makes handing something off safe instead of risky. Skipping it is the single biggest reason a handed off task goes sideways.

Checkpoints, not micromanagement

The instinct when you're nervous about handing something off is to check in constantly, which defeats the purpose. The better approach is building in a few deliberate checkpoints. A point partway through where you review direction before it goes further. A final review before anything is considered finished.

This is still human in the loop, the same principle from Part 1, just applied at a different frequency. You're not reviewing every sentence. You're reviewing at the moments that actually matter.

Review the outcome, not the process

With a handed off task, your job isn't to watch how it got there. It's to evaluate what it produced. Does the summary actually capture the right information. Does the research hold up. Is the output something you'd be comfortable putting your name on.

This is a different kind of scrutiny than editing a paragraph line by line. It's closer to reviewing a colleague's finished work than co-writing it with them in real time.

When to use which mode

Talk to it when the task needs your judgment at every step, tone, nuance, a decision that shifts based on what comes back. Hand it off when the task is bounded, well defined, and doesn't need you steering each individual move, research, data pulls, multi-step tasks with a clear end state.

Knowing which mode a task actually calls for is the real skill here. More than either one on its own.

The bottom line

Handing off isn't skipping the work of talking to AI. It's a different discipline: clear goals instead of clear instructions, guardrails instead of corrections, checkpoints instead of constant review. Get good at both, and you stop asking "how do I prompt this" and start asking the more useful question: does this task need a conversation, or does it need a clear goal and some room to run.

Happy Learning,

KP