How to write a one-page project kickoff covering purpose, what done looks like, fixed and open constraints, who decides, check-ins and where things live, before the first task is handed over.
A two-minute trim before you paste an email thread into a brief: five things to leave out, how to replace rather than delete, and a one-line note that tells the helper the gaps are deliberate.
A four-question filter for deciding which tasks to hand over whole, which to keep and which to split, so the hard-to-undo, personal and judgment-heavy parts stay with you.
Five steps for a "waiting on me" list that tracks what helpers need from you, sorted by what is blocked, answered in the smallest useful reply and turned into standing rules where answers repeat.
How to hand off email triage safely with three permission levels, a few clear buckets, a daily digest and a one-week audit before you step back.
A five-rung ladder for following up on replies you are waiting for, with dates, reasons and a clear stopping point, plus what to keep for yourself when you hand it off.
A five-step method for sorting requirements into must, should and nice, turning musts into testable lines and asking for options in a simple pass-or-fail table.
How to turn a brief that worked into a reusable template in about ten minutes: labelled blanks, wording kept as it was, a note on what changed last time, fixed versus varying parts, and an owner and date.
Three checks for every point where one step's output feeds the next (shape, completeness and assumptions), plus a four-line handover note and a simple rule for who checks what.
How to set fixed review windows for work you have handed off, decide what may interrupt you in between, and adjust the schedule after two weeks.
Five habits for giving a person, script or AI assistant the access a task needs without spreading secrets: keep them out of text, one key per job, clear names, a short list, and use without reading.
A ten-minute postmortem for a handed-off job that came back wrong: check the brief, the inputs, the fit, the check and the scope in order, and change one thing at a time.
What to put in an away note for work that keeps moving while you are gone: what keeps running, what pauses, what can be decided without you, what must wait, and when you will look at the results.
A six-step setup for keeping several tool accounts pointed at one goal: decide who does what, authorize deliberately, send context with each task, track progress, gather results and reassign.
Five habits for meeting notes that someone who was not in the room can act on: separate decisions, five-part actions, owned open questions, what you decided not to do, and a two-question test.
A twenty-minute weekly routine for reviewing handoffs: list them, mark each one, tally the reasons for rework, choose one change for next week, and decide whether recurring jobs keep, change or stop.
How to write down a repetitive browser chore so anyone can take it over: where it starts, the steps as verbs, what done looks like, what must not happen, and what comes back to you.
A five-part brief for handing off research: the question and the decision it feeds, scope, source rules, the shape of the answer, and what would change your mind, with a full example.
Seven questions to ask before you connect a tool or hand off a task: clear inputs, checkable results, visible progress, minimum access, reversibility, full cost and whether the work recurs.
Five rules for naming files so a colleague, contractor or assistant who inherits a folder can find the current version without asking, plus two habits that make the convention stick.
A six-step pilot routine for repetitive jobs: test the full brief on an easy, a typical and an awkward item, settle ambiguities in writing, then scale up in steps.
Why the first thing to delegate should be a boring, recurring chore with a clear finish line, and a five-step order for setting it up before you schedule it.
When two tools work on one project and finish at different times, the merge is the hard part. Three rules help: one landing place, one report shape and one owner for the merge.
Five things a single starting point for AI and tools has to do to earn the name: take the goal, bring in the right capability, carry the context, keep track and bring results back.
Why the handoffs between your specialist tools eat the day, and how a personal assistant that coordinates connected tools and accounts can take over that go-between work.