Following up without nagging: a short ladder for replies you are waiting on

You asked three people for their numbers by Thursday. It is now Friday morning and you have two of them. You could write "just checking in" to the third, which sounds like a nag and says nothing, or you could wait and hope. Most of us alternate between the two. (A hypothetical scene, for illustration.)

Following up is a chore that is easy to hand to an assistant, a colleague or a tool, as long as the rules are written down first. A short ladder keeps it polite, specific and finite:

  1. Send the request with a date and a reason. "Could you send the June figures by Thursday at noon? I need them for Friday's review." A date and a reason make every later reminder easy and fair.
  2. Send the first reminder the day before the date, short and helpful. Restate the ask, attach whatever is needed and offer a way to make it easier: "Happy to take a rough number if the final one is not ready."
  3. Send the second reminder on the date itself, with the one specific thing and its consequence. "I need the figures by noon to include them. If they are late, I will show last month's and mark this row as pending."
  4. After the date, change the route, not the volume. A message that went unanswered twice will not be answered a third time in the same place. Try a different channel, or ask who else can answer.
  5. Stop, and write it down. The ladder has a top rung. Note who did not answer, what you did instead and when you will try again.

Three rules keep a ladder from turning into pressure. Send no more than one reminder a day. Always repeat what is needed, so that nobody has to scroll back to find it. And thank people the moment they answer, late ones included. A habit of thanks does more for the next request than any wording in this one. And keep the wording human: a reminder that reads like a form letter tends to be treated like one.

If you hand the ladder to a helper, hand over the dates and the wording rules too, and keep the fourth rung for yourself. Changing the person or the channel is a human call, and it is usually a quick one.

In the hypothetical Friday above, the ladder would have sent a short reminder on Wednesday and a specific one on Thursday morning. By Friday you would be on the fourth rung with a quick call, not on your third "just checking in".

Octuo is a personal assistant and one starting point for work across AI, tools and specialist services. Its skills, sub-agents, scheduled routines and integrations can be added and changed by you, or by Octuo when you ask, and it reports back when a job is done. A follow-up ladder is the kind of recurring routine worth writing down before you hand it over. 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