Mail

Not every project earns a clear morning, a quiet room, and two uninterrupted hours. Many useful projects have to move through the small gaps between meetings, errands, replies, and ordinary work. The problem is not that short blocks are worthless. The problem is that a vague project takes too long to re-enter.

You can make fragments of time useful by doing the thinking once, then leaving a visible next step for each return.

Describe the finished version plainly

Write one sentence about what done looks like. "Improve onboarding" is too broad. "Publish a one-page onboarding checklist for new contractors" is small enough to start. A clear finish line prevents the project from absorbing every related idea.

Then list the few parts that must exist for it to be finished. For a checklist, that might be gather current steps, ask two people what gets missed, draft the page, test it with one new person, and revise. Do not build a complete plan for every possibility. You are making a map that helps you choose the next ten-minute action.

Prepare tasks that fit real gaps

Break the project into actions that can be started without a long warm-up. "Ask Maya which access request causes delays" is usable. "Research the process" is not. Good small actions begin with a verb, name an object, and have a clear stopping point.

Keep a short list of these actions with the project. When a meeting ends early or you have fifteen minutes before leaving, pick one. You will not complete the project in that moment, but you may collect a missing answer, write the opening paragraph, or choose the next decision. That is genuine movement.

Separate making progress from finishing everything

Small projects often fail because every work session feels too short to count. Replace that test with a simpler one: did this session reduce uncertainty or make the next action easier? A short call that confirms the owner, a note that narrows the audience, or a first rough outline all qualify.

Keep a brief progress note at the top of the project: what changed, what remains uncertain, and what to do next. It takes less than a minute to update and saves much more when you come back days later.

Give different gaps different jobs

For the contractor checklist, a five-minute gap might be enough to send one question to the access owner. Fifteen minutes could produce a rough list of first-day steps. Thirty minutes might let you compare that list with two existing onboarding emails and mark contradictions. These are examples to resize around your work, not promises that every task fits those durations.

Keep requests for other people's input early in the sequence so waiting happens between sessions. Do not split a sensitive review or a task requiring sustained reasoning merely to make it fit a gap. Mark those steps as needing a longer block. Before a short session ends, save the current version and identify exactly which fragment is complete; otherwise the next session may repeat the same work.

Protect one longer block near the end

Fragments can move a project forward, but they are not always enough for the final pass. Once the pieces are ready, reserve one longer block for assembly, review, or decisions that need continuity. By then, the work is smaller and the block has a clear job.

This approach is honest about a crowded week. It does not promise that every project can be completed between calls. It gives small projects a way to stay alive until they receive the attention they need.

Keep the project map visible until the work is done. When a fragment of time appears, you should be able to begin in under a minute, without rediscovering the project or deciding what counts as progress. That low-friction return is what turns scattered effort into a finished result over time.