I used to think my work lived inside design software. Figma files, complex prototypes, elaborate presentations. That stuff is the finished surface, the thing you show a client. But it’s not the work. The actual work, the messy thinking, the false starts, the good idea you had at midnight that you forgot by morning, was leaking out everywhere. On napkins, in a half dozen different note-taking apps, scattered across Slack threads. None of it connected. I was losing the thread before I even found it. The project’s story was gone.
The turning point was embarrassingly low-tech. I started keeping a single, running text file for each project. I called it the project log. No formatting, no folders. Just date-stamped entries. I wrote down what I did, why I made a choice, what the client said in a meeting, links to references, questions I couldn’t answer yet. It was a stream of consciousness for the job. Suddenly, I had a memory. I could track the evolution of my own thinking. The real treasure, though, wasn’t just having the log. It was learning how to read it. That’s when I found a method that turned my chaotic notes into a real asset. I learned a lot from reading about how others structure this kind of raw thinking, like the approach shared in the raybee field notes. Seeing how someone else parses their own observations gave me a framework for my own.
Your First Draft Should Be a Secret
We feel pressure to make things look polished too soon. Opening a design file feels like you need to start making rectangles and choosing fonts. A text file has zero visual pressure. You can write “maybe this button is terrible” without having to design the terrible button. It gives you permission to be wrong. This private space for half-baked ideas is where good concepts are born. They need time to breathe before they face the judgment of pixels.
Date Everything, No Exceptions
Every entry gets a date and time. This seems trivial. It is not. When you’re trying to remember why you changed a color palette, being able to scroll back to the Tuesday you had that feedback call is a lifesaver. It creates a timeline. You stop seeing your project as a static “final” thing and start seeing it as a narrative that unfolded over weeks. This timeline becomes your best defense against scope creep and your best explanation for the current direction.
The Client Said What, Exactly?
In meetings, I type quotes directly into the log. Verbatim. “I don’t like blue, it feels corporate.” Later, I can separate the emotional reaction (“feels corporate”) from the literal instruction (“don’t like blue”). My job isn’t to remove all blue. It’s to solve for the feeling of corporate coldness. The raw quote preserves the real problem. My interpretation, which I note separately, is the proposed solution. This distinction prevents so many revision loops.
Keep Your Questions Ugly
In a polished document, questions sound smart. “What is the primary user action?” In my log, questions are messy. “Why is the signup flow so long? Are we scared people will sign up? Is that the point?” The ugly questions are the useful ones. They point directly to assumptions no one has questioned. I make a list of them in the log. Solving a project often means answering just one or two of these ugly questions.
Link to Everything, Judge Nothing
See a terrible website with one interesting hover effect? Paste the link. Read an unrelated article that sparked an analogy? Paste a quote. The log becomes a catchment for inspiration without the need to justify it. You don’t have to write “this is good” or “this is bad.” You just note it. Patterns emerge later. That weird hover effect might solve a feedback problem you have three weeks down the line. The log remembers what your brain forgets.
- Record decisions immediately, with a one-sentence reason.
- Note your own mood or energy; a bad idea on a tired Tuesday might be worth revisiting.
- Use markdown if you want, but basic dashes for lists are more than enough.
- Never delete, only add. You can mark things as ‘abandoned’ but keep the history.
The Weekly Review Is Where the Magic Happens
Every Friday, I skim the last week’s log. This is not deep work. It’s a 10-minute scan. I’m looking for two things: unanswered questions that are now urgent, and forgotten ideas that suddenly seem relevant. This weekly reset means nothing gets permanently lost. It turns the log from a diary into a steering tool. You start to see your own biases and blind spots.
It’s Not a Todo List, It’s a Context List
I tried using this file for tasks. It failed. “Fix header” is a todo. “Header feels disconnected from the hero section because the mood shift is too abrupt. Need to explore transitional elements” is context. The latter goes in the log. It explains the ‘why’ behind the task. When you come back to it, you don’t just know *what* to do, you remember *why* it needs doing. This context makes starting the actual work easier and faster.
The simplicity is the point. It’s just text. That means it’s fast, it’s searchable, and it’s permanent. My design software will change. My text files from ten years ago still open instantly. They contain the story of my work, and in a creative field, your ability to tell the story of how you got there is often as valuable as the final product itself. The log is the raw material for that story.
- Use a plain text editor you like (VS Code, Sublime, even Notepad).
- Store the files in a Dropbox or iCloud folder for automatic backup.
- One file per project, named clearly: “ProjectName_LOG.txt”.
- If you share with a team, keep a separate “Shared Log” for collective notes.