Example: Searching Without Cluttering the Desk

The job

You have a folder with two years of documents in it, and a two-part task:

• First: find which document has the terms you agreed with a certain client.

• Second: update those terms everywhere they appear.

It's the most common case there is: search first, then act.

How it goes without a helper

You ask for the first part and it gets going: opens a document, not the right one; opens another, still no; and so on through twenty. In the end it finds it, and tells you where.

Great. Except now, there are twenty documents on the table, nineteen of which you didn't need the moment it opened them.

And the second part of the job — the one that needs precision, because you're editing contract terms — starts from a table half-full of discarded stuff. Your instructions, which might have said exactly how those terms should be written, now carry a tenth of the weight they did before.

The result isn't a disaster. It's something sneakier: it's a bit worse, and you have no way of noticing.

How it goes with the helper

Same request, but you send the search into another room. And you write it in full, because over there it knows nothing about your conversation:

"Search this folder for which document has the terms agreed with client Rossi. Report only the file name and the exact paragraph."

The helper opens its twenty documents in its own room. It comes back with two lines.

On your table, only the answer arrived. You do the edit the same as before — same tool, same model — but with all the space free and your instructions still front and center.

The detail that makes the difference

Notice this: the helper didn't do the hard part. It did the boring one. The delicate edit stayed where it belonged, in the main conversation, where all the context is.

That's the right way to think about it: you don't delegate what matters, you delegate what makes a mess.

When I wouldn't have done it

If there had been three documents instead of two hundred, I'd have done everything in the main conversation: three files on the table bother no one, and the helper would have cost more than it saved.

The threshold isn't a number: it's the question from the last lesson. Does it look at a lot of stuff and hand back little? If so, send it to the other room.

And now

So far, everything we've done lives inside a folder on your computer. But your work doesn't all live there: there's email, the management software, cloud documents, the calendar.

In the next chapter we open the last bucket: what it's connected to outside.

Did you get it?

Two minutes, no grade. Trying to answer — even getting it wrong — cements the concepts far more than rereading. Not in the mood? Skip it: the lesson still counts as complete.

1In the example, why does the final edit come out better with the helper?

Because the helper does it instead Because it gets done with a clean table instead of one full of useless files Because it uses a more capable model

2What does the request you send the helper need to contain?

One line: it already knows what you were talking about Everything it needs to understand the task on its own, because your conversation doesn't have it