Ask for a checkpoint halfway: what a good partial result looks like

You hand over a big job on Monday morning and hear nothing until Wednesday night. Then it arrives, finished, and it is a long way from what you meant. Two days of work went into the wrong shape, and all you can do is say so and start again. (A hypothetical scene, for illustration.)

A checkpoint is a deliberate pause partway through a job: the helper stops, shows what it has so far and waits for a go-ahead or a change of direction. It works for any helper, a colleague, a contractor or an AI assistant, and it turns one big gamble into two smaller bets. A good partial result has five parts:

  1. A slice, not a sketch. Ask for one finished piece of the whole: the first three sections, the first fifty rows, one of the five pages. A complete small piece shows you real quality. An outline of everything only shows you intentions.
  2. The method in two sentences. How the helper is going about the job, and what it has assumed so far. Most wrong turns are visible in the method long before they show up in the output.
  3. What is left. A plain list of the remaining steps, with a rough idea of how long each might take, so you can judge whether the plan still makes sense.
  4. Open questions. Anything that needs your call, written as a question with a suggested answer you can accept in one word.
  5. A decision for you: continue, change or stop. Say in the brief that the helper should wait for your answer at this point, and say how long you will take to give it.

Choose the checkpoint where a change of direction is still cheap. A useful rule of thumb is after the first tenth of the work, or after the first piece you can judge, whichever comes first. For a long report that might be the outline plus one finished section. For a batch of fifty items, it might be the first five.

Two things tend to go wrong. A checkpoint that arrives too late is only a progress report, because you cannot change anything now without waste. And a checkpoint with no question attached invites a vague "looks good", which tells the helper nothing. Ask it something specific, such as "Is this the level of detail you wanted?"

Here is how it might go with forty support emails to be sorted by theme. At the checkpoint you get the first eight sorted, the two rules used to sort them, a short list of themes the helper had to invent and one question: should billing questions get a theme of their own? You answer yes in one word, and the other thirty-two are sorted your way.

Keep the checkpoint short enough to read in a couple of minutes, and keep your reply just as short. If you take a day to answer, you have spent the time the checkpoint was meant to save.

Octuo is a personal assistant and one starting point for work across AI, tools and specialist services. It keeps working on long, multi-step jobs over time, picks them back up and finishes them instead of stopping when the chat closes, and tasks carry forward across sessions, with context that survives the conversation. It reports back when a job is done, and a checkpoint is a good thing to ask for in the brief. Public beta on macOS: https://www.tutuo.ai/en/octuo/

— The Octuo team at Tutuo, Inc.

Comments

Post a Comment

Popular posts from this blog

Start your assistant setup with one boring, recurring chore

Disclosure: This piece was drafted by AI and editorially reviewed by AI. It has had no independent human review. The best first thing to delegate is rarely the most impressive one. It's the boring, recurring chore with a clear finish line: a weekly summary, a morning check, a round of follow-ups. A setup order that keeps it manageable: Pick one chore you do at least weekly. Name the capability it needs: a model, a tool on your computer, an outside service. Grant the minimum access for that one job. Run it once and read the report that comes back. Then schedule it, if you want it to recur. Octuo is built for this kind of growth. Skills, sub-agents, scheduled routines and integrations can be added and changed by you, or by Octuo when you ask. Supported specialist tools on your computer, such as coding agents, can become something Octuo hands work to once you've installed, set up and authorized them, and Octuo can operate outside solutions on your behalf under the permissions you ...
Read more

Design a small app before you ask for it: a weekly review board

Before you ask any assistant to build a small app, spend five minutes designing it on paper. You end up with a better description, and on Octuo's Canvas, a description is all it needs to start. This piece was drafted with AI assistance and reviewed by the Octuo team. What follows is a worked example. It is hypothetical and illustrative, not a report of how anyone uses Octuo. The app is a weekly review board. Step 1: Start from a recurring moment. Good small apps come from something you do repeatedly. Here, every Friday afternoon you look back at the week, list what is still open and decide what carries over. Today that lives in scattered notes and messages. Step 2: List what you keep. Three to five things per item: a short title, an owner, a status (open, waiting, done) and a note. Stop there. Every extra field is one more thing to fill in at five o'clock on a Friday. Step 3: List what you do. Verbs, not nouns: mark done, move to next week, filter by owner, add a note. If you c...
Read more

Schedule a recurring job backwards from the moment you need the result

Most recurring jobs are scheduled from the wrong end. You pick a time that suits the job, and on Monday, five minutes before the meeting, you find that the summary you needed isn't ready, or is ready and unread. Disclosure: This piece was drafted by AI and editorially reviewed by AI. It has had no independent human review. Work backwards instead. Five questions, in this order: When do I need the result, and where will I look for it? Name the moment ("before Monday's team meeting") and the place. When will I review it? A result you first read in the meeting hasn't been reviewed. Leave a gap long enough to read it and send something back. How long does the job take? Use the longest run you've seen, not the average, and add a margin. When do its inputs settle? A job that starts before the last input arrives reports on a version that is already out of date. Start after the inputs settle. When will I look at the schedule itself? Put a review date on it: "Check...
Read more