How to Plan a Focus Block Around One Question

A vague focus block can turn into reading, rearranging, and half-starting. You sit down with good intentions, open a few files, skim old notes, check one message for context, and end the block with a cleaner workspace but no real progress. A question gives the block a job. It turns time into a container for a specific answer.

The question does not have to be profound. It only has to be narrow enough that work can answer it. "Work on the proposal" is a theme. "What should this proposal recommend as the first step?" is a question. The second version tells you what kind of thinking belongs in the block and what can wait.

Write the question first

Write the question before you open the main work. Put it at the top of the document, on a sticky note, or in the calendar event. This small move protects the block from becoming a general work session.

Use a question that can be answered by work: What should this proposal recommend? Which metric changed? What is the smallest usable draft? What decision does the team need by Friday? The answer becomes the output. If the answer would still be vague after an hour, the question is probably too broad.

A useful focus question often starts with one of a few verbs: decide, draft, compare, identify, simplify, explain, or choose. "Decide which customer story belongs in the opening section" is workable. "Think about customers" is not. The verb gives your attention something to do.

If the project is large, resist the urge to make the question carry the whole project. A single focus block should not need to solve the strategy, write the report, and prepare the presentation. It can decide the report structure, draft the introduction, or identify the three facts the presentation must include. Smaller questions produce more reliable progress.

Keep materials close

Open only the files, notes, and references needed to answer the question. Extra context often feels responsible, but it slows the first decision. If the block is about choosing a recommendation, you may need the brief, the latest numbers, and one prior decision. You probably do not need every old chat thread, every related slide deck, and every article you saved months ago.

Before the block begins, make a short materials list. This can be as simple as three filenames. If you notice yourself reaching for another source during the block, ask whether it is necessary for the question or whether it is a way to delay judgment. Sometimes you do need more context. Often you need to use the context you already have.

Close or hide anything that invites a different kind of work. An inbox turns a thinking block into a response block. A dashboard turns a writing block into an analysis block. A long backlog turns a decision block into a planning session. The point is not to create a perfect environment; it is to reduce the number of directions your attention can escape.

It helps to define what "done for now" looks like. For a writing block, done might mean a rough section with headings and examples. For analysis, it might mean one chart and a written interpretation. For planning, it might mean a recommended next step with two rejected alternatives. This definition keeps the block grounded when the work gets uncomfortable.

End with the answer state

At the end, write what you now know, what remains uncertain, and the next action. That makes the block useful even if the whole project is not finished. The closing note can be short:

"Answer: the first recommendation should be a two-week pilot with the support team. Still uncertain: whether Operations can review the intake form in time. Next action: ask Priya for the review window."

This closing step matters because focus blocks are often interrupted by reality. Meetings move, priorities shift, and some questions take longer than expected. If you leave a clear answer state, you can restart later without repeating the same warm-up work.

Do not judge the block only by whether the whole task is complete. Judge it by whether the question moved. If the answer is "we do not have enough evidence yet," that can still be progress if you now know exactly what evidence is missing. If the answer is "the draft is weaker than expected," that is useful if you identified the weak section and the next repair.

Planning around one question is a modest practice, but it changes the feel of focused work. Instead of asking your attention to be generally disciplined, you give it a clear target. The block becomes less about staying busy in silence and more about producing one answer that the rest of the work can build on.