Posts

Choosing what to keep human: a four-question filter

You made a list of everything you could hand off, and it came to nearly everything. That is a warning sign, not a plan. Some of that work is the reason you are in the role at all: the call you make when two people disagree, the sentence that says sorry, the decision nobody else can sign. (A hypothetical scene, for illustration.) Handing work off well starts with deciding what stays with you. A four-question filter takes about five minutes per task and works for any helper, whether a colleague, a contractor or an AI assistant. Ask the questions in order and note every yes: Would a mistake here be hard to undo? Sending, paying, publishing, deleting and signing are all hard to take back. A task that ends in one of them can still be prepared by a helper, but the last step stays with you. Does it carry your name in a way that matters to the reader? A thank-you, an apology, a difficult message or a reference. People can tell when a message was routine and when it was meant. Keep these, or at...

Silence is not success: how to notice a routine that did not run

Every Monday a summary lands in your inbox. This Monday it did not. You only notice on Thursday, when someone asks where it is, and you realize that last Monday's never arrived either. The routine did not fail loudly. It stopped, and a missing message looks exactly like a quiet week. (A hypothetical scene, for illustration.) A routine that runs on a schedule, such as a weekly report, a nightly backup or a Friday reminder, has an awkward property. When it works you see a result, and when it breaks you see nothing. Nothing is easy to miss. These five habits turn silence into a signal, and they work whether the routine is run by a colleague, a script or an AI assistant: Write down when it counts as late. "The summary arrives by Monday at 9:00, and at 10:00 it is overdue." Without a stated time nobody can say that a routine has missed, and everybody assumes somebody else has noticed. Ask for a result every time, even when there is nothing to report. "Ran Monday 8:02. No ...

From a rambling voice note to a clear brief: five edits

You talk through a task on the way to your next meeting: who it is for, what you want, the thing you forgot, the other thing you forgot and a deadline you only half recall. The voice note is a good record of what is in your head. It is a poor brief, because whoever receives it has to do the sorting you skipped. (A hypothetical scene, for illustration.) Talking first and editing second is a fine way to start. You get everything out before you worry about order. Five quick edits turn the rambling version into something a helper can act on, whether it is a colleague, a contractor or an AI assistant: Underline the outcome. Find the sentence that says what should exist when the job is done and move it to the top. Everything else supports that sentence. Separate the facts from the wishes. Dates, names, amounts and file names go in a short list of facts. "It would be nice if" goes on its own line, marked optional. Cut the second telling. When you said the same thing twice with diffe...

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: 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. 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." Send the second reminder on the date itself, with the one specific thing and it...

Sort your requirements into must, should and nice before you ask for options

You ask for options for a team offsite and get twelve venues. None is wrong. But six are too far away, four are over budget and two have no room for lunch, and you knew all of that without ever saying it. (A hypothetical scene, for illustration.) Options come back sorted by whatever the helper guessed you cared about. You can steer them by sorting your own requirements first. The method takes ten minutes, works for any helper, and has five steps: Write every requirement on its own line, as it occurs to you, with no ranking yet. Include the obvious ones. What is obvious to you is invisible to everyone else. Mark each line must, should or nice. A must is a dealbreaker: an option that fails it is out. A should is something you would trade for a good reason. A nice is a tiebreaker and nothing more. Put a number or a test on every must. "Close to the office" is a wish. "Under forty minutes by public transport from the main office" is a test an option can pass or fail. Ke...

Before a helper edits your document, make a copy and ask for a change list

A colleague, or an assistant, tidies up your document. It reads more smoothly, which is nice. It also no longer says what you meant in paragraph four, a figure in the table has changed, and you cannot tell how many other things are different because you saved over the original. (This is a hypothetical scene, for illustration.) Editing is one of the most common handoffs and has the least safety net. Five habits give you one, and they work whoever does the editing: Copy first, then hand over the copy. Save the current version under a new name before anyone touches it, and give the helper the copy. The original stays exactly as it was, and every later question can be answered by comparing the two. Say what kind of editing you want. Proofreading, tightening, restructuring and rewriting are four different jobs. "Fix typos and obvious grammar only, and do not change wording or meaning" is a very different request from "make this clearer". Name the parts that are off limit...

Two drafts, one decision: a four-question scorecard for comparing them

You asked for two versions of an announcement, and now both are open side by side. Both are fine. You read the first, then the second, then the first again, and you pick the one you read last. That is not a decision. It is the order you looked in. (A hypothetical scene, for illustration.) Comparing drafts goes better with questions written down in advance, because they take the order of reading out of the result. This scorecard has four questions and takes about five minutes. It works for drafts from a colleague, a template or an AI assistant: Which one says what the reader should do, in the first two lines? Cover everything but the openings and read only those. The draft where the action is clearest has won the most important round. Which one could you send without checking a fact? Mark every claim, figure and name in each draft. The draft with fewer marks is quicker to finish, and a draft with a claim you cannot source is not finished at all. Which one sounds like you on an ordinary ...