The Scrivener's Marginal Note and the Efficiency of the Second Question

You sit down to draft a report, sketch a design, or finally outline that project plan. You know you should start with a question—a good, clean one to guide your work. So you do. ‘What is the core argument?’ or ‘How should this system function?’ It’s a solid start. Yet an hour later, you find yourself deep in the weeds of a minor detail, or worse, staring blankly at a blinking cursor. Your initial question seems to have lost its power, its ability to propel you forward. The problem, I’ve found, isn’t the first question. It’s that we forget to ask the second.

The First Question Directs, the Second Question Unsticks

The first question is your compass bearing. It sets your direction. ‘What is the objective?’ gives you a north star. But when the terrain gets rough—when you encounter a dense thicket of data, a stubborn design flaw, or a paragraph that refuses to cohere—that north star isn’t enough. You need a tool for the immediate ground. That’s the second question.

Think of it as the small, sharp note a medieval scrivener would write in the margin of a manuscript. Not a revision of the main text, but a pragmatic query to himself about the work at hand. The second question isn’t about your goal, but about your next, physical action given the specific obstacle you’ve encountered.

For example, your first question was: ‘What are the three main sections of this proposal?’ You answer it, outlining them neatly. Then you stall. The scrivener’s second question appears in the margin: ‘Do I have the client’s data for Section Two, or must I indicate its absence here?’ It’s not profound. It’s procedural. It pulls you from the fog of ‘writing the proposal’ into the concrete world of ‘finding a file’ or ‘typing a placeholder note.’ Motion resumes.

Your first question was: ‘How does this code module need to interact with the database?’ You start coding, hit a logic snag, and freeze. The marginal note: ‘Can I stub out a fake data return for now and describe the needed query in a comment?’ It’s a permission slip. It allows you to bypass the perfect, unknown solution to commit a useful, temporary one, keeping the work flowing.

This practice transforms the quality of your focus. Instead of a single, broad beam of attention that slowly diffuses, you create a rapid, iterative cycle: a small action, followed by a new, immediate question born of that action’s result. It’s the mental equivalent of a craftsman feeling for the next tool on the bench without looking up from the work. The rhythm is everything.

So, the next time you feel the productive momentum stutter, don’t just stare harder at your original, now-distant question. Don’t berate yourself for losing focus. Instead, imagine a narrow margin beside your work. In it, write the smallest, most specific question you can about the very thing in front of you. Answer it with the smallest, most specific action you can take. That marginal dialogue, between you and the work, is where the real, uninterrupted stuff gets done.

Notes & further reading

A few pages I came back to while writing this: