The Pocket Question Log: One Month of Chasing What My Work Wanted to Know

On October 15, I started carrying a small notebook in my back pocket. Not for ideas, exactly. For questions. Every time I caught myself wondering something while making, editing, or sharing work, I wrote it down and moved on. No solving. No spiraling. Just a record.

The rule was simple: if the work asked, the log received. Then, once a week, I picked one question and chased it through a tiny creative experiment. Thirty days later, on November 13, I had a messy little document that told me more about my taste than any portfolio review I have paid for.

The rule was smaller than it sounds

I expected the notebook to fill up with grand questions like "What is my artistic purpose?" Instead, I got things like: Why does this photo feel louder than the rest? What am I protecting by keeping this section? Who is this for when I am tired? Why do I keep rewriting the first sentence and never the last?

That was the first useful surprise. The questions my work asked were not abstract. They were specific, petty, and practical. They were the kind of questions that usually get buried under a deadline or a snack break.

Keeping the log separate from the work was important. I did not answer anything in the moment. I just wrote the question down, closed the notebook, and kept going. By the end of week one, I had twenty-three questions. Some were repeats. Some were embarrassing. A few were about fonts.

Week one: the question about volume

My first weekly chase came from a question I had written three times: "Why does this one image feel like it is shouting?"

For the experiment, I gave myself twenty minutes and one rule: make three versions of the same layout, each one quieter than the last. I turned down contrast, removed an accent color, and let more empty space sit around the image. It was not a real project. It was a test.

What I learned was not that quiet is better. It was that I had been using volume as a substitute for confidence. The loud version was not saying more. It was just afraid of being skipped. That is a taste note I can use. I like work that holds attention without grabbing a collar.

Week two: the question I did not want to write down

Around day ten, I noticed a question I kept almost writing and then skipping: "What am I avoiding by calling this finished?"

I did not want to chase that one. So I made it week two's experiment, because that felt like the point. I took one piece I had called done and made a list of everything I would have to change if I took it seriously. Not fix. Change. The list included rethinking the opening, cutting a section I liked, and showing it to someone who does not compliment me by default.

I did two of the three. The third one is still sitting there. But the log made the avoidance visible, which is different from solving it. I now know that "finished" sometimes means "I would like to stop feeling uncomfortable now." That is not a crime. It is just useful information.

Week three: the question about the room

By week three, a pattern had formed around audience questions. Not "Who is my audience?" That one is too big to test. Mine were smaller: "Would a person who does not know me understand why this is here?" and "What would a stranger ask first?"

For the experiment, I sent one piece to three people with a single prompt: "Tell me the first question this makes you want to ask." No feedback. No compliments. Just questions. Two people asked about the same missing piece of context. One asked why a certain detail was there at all.

That was not a mandate to change the work. It was a reminder that the room around a piece is part of the piece. I had been treating context like an apology. It is not. It is a host greeting people at the door.

Week four: the question underneath the others

My last weekly chase came from a question I had written on day two and ignored for almost a month: "What would I make if I did not have to explain it?"

I gave myself one afternoon. No pitch, no caption, no portfolio logic. I made a short, strange series of five images around a single color and a repeated shape. It was not good in the way I usually mean. But it was fast, and it was mine, and I wanted to keep going after the timer went off.

That is the question I am carrying into December. Not because it solved anything, but because it pointed at a project instead of a problem.

What the log actually showed

At the end of the month, I read the whole notebook in one sitting. Three things stood out.

First, my taste is more consistent than I pretend. The same words kept showing up: quiet, clear, warm, specific, lived-in. I did not need a new identity. I needed to stop treating those instincts like accidents.

Second, my avoidances are boringly practical. I do not avoid grand fears. I avoid asking for money, cutting things I like, and sending work to people who might not answer. The log did not shame me out of that. It just made it harder to pretend I did not know.

Third, the projects worth pursuing next were hiding in the questions I wanted to keep asking. The ones about small serial work, context, and making without explanation. Those are not answers. They are directions.

The template I am still using

If you want to start your own pocket question log, keep it small enough to actually use. Mine is a quarter-page per day, at most. Here is the version I am carrying into next month:

• Date and context: Where was I, and what was I doing? One line.
• The question: Write it exactly as it showed up. Do not clean it up.
• The trigger: What was I making, editing, or sharing when it appeared?
• The chase: Pick one question per week. What is the smallest experiment that could answer it?
• The result: What happened? Keep it to three sentences.
• The next question: What does the result make you curious about now?

The notebook is not a planner. It is a listening device. My work has been asking me things for years. This month, I finally wrote a few of them down.

If you try it, start with the question you almost did not write. That is usually where the interesting work is hiding.