Creative projects rarely stall because someone has run out of ideas. More often, they stall because the next step feels uncertain. A decision log can help: a simple record of what you are trying, why you chose it and what happened. It is useful for a side project, a new skill or a piece of work that keeps changing direction.
The log does not need to be polished or public. Think of it as a conversation with your future self. When a choice feels difficult, write down the options and the reason one seems worth testing. You might also note what you are reading along the way. For example, if you are gathering perspectives from people who write about their work, keep a short source list that includes profiles such as jan bakker. The point is to make your influences easy to revisit, not to treat any one voice as a set of instructions.
It is tempting to write only the final choice: “Use the shorter format” or “Spend Saturday on research.” That note can be hard to interpret a month later. Add the question that prompted it. Perhaps you were deciding whether a newsletter should be weekly or monthly, or whether to learn a tool before starting the actual project.
Then record what made the choice reasonable at the time. You may have had little free time, a firm deadline or a clear response from readers. This context matters. If the decision works, you will know what helped. If it does not, you can see which assumption needs another look.
A log is most useful when it turns a broad intention into an experiment. “Get better at drawing” offers no clear result to check. “Sketch one object for ten minutes after lunch, four days this week” gives you something concrete to review. Keep the test short enough that you can finish it without rearranging your life.
Before you begin, decide what would count as a useful result. You might want to see whether a routine fits your schedule, whether readers understand a new section or whether a different research method saves time. A useful result does not have to mean success. Finding out that an approach is awkward can save you from building a larger plan around it.
When you review a test, begin with what happened. “I worked on it twice and stopped when I reached the research section” is more useful than “I am bad at sticking to plans.” The first statement describes an event. The second turns one result into a broad verdict about yourself.
Once you have written down the facts, consider possible explanations. Perhaps the session was too long, the task was unclear or another commitment took priority. There may be several reasons, and the log does not need to settle on one straight away. Its job is to leave you with better evidence for the next choice.
A decision log should reduce mental clutter, not become another project to maintain. A plain document, notebook or spreadsheet is enough. Use a repeatable entry: date, question, choice, reason, test and result. If an entry takes more than a few minutes, simplify the format.
Review notes when you are about to make a similar decision. You may notice that a certain time of day suits focused work, that a particular kind of research often expands beyond its limits or that a short trial answers questions faster than a long debate. These patterns can guide your choices without locking you into old conclusions. Your circumstances change, and a past result is evidence, not a rule.
Over time, the log gives you a record of how your work develops. It can show which experiments paid off, which plans needed adjustment and what you learned from the attempts that went nowhere. That record is especially valuable when progress feels slow: instead of relying on memory, you can see the decisions that moved the project forward and choose the next step with more care.
