Making the invisible parts of design visible

I have always been more interested in how a design comes together than in the final object alone. The finished page may look inevitable, but behind it sit dozens of small decisions: which problem deserves attention, what to remove, where a photograph belongs, and when an idea is not yet good enough. I began recording those decisions because private notes kept disappearing into old project folders. I document my design process in public because publishing them gave the work a durable home and turned scattered notes into a record I can return to.

The site that holds this record started with restraint. It uses ample whitespace, careful typography, a narrow palette and images that can breathe without decoration. That visual calm reflects how I want the process to feel too: deliberate, editable and free of theatre. Public documentation is not a performance of productivity for me. It is a working notebook that happens to be readable by others, offering a transparent view of design as judgement, revision and ongoing curiosity.

Turning decisions into an archive

A useful public process note answers three questions: what was I trying to change, what did I try, and what did the evidence tell me? I write down the brief in plain language, collect references, sketch alternatives and record why one route survived while another was discarded. The result is less like a case study with a heroic ending and more like a chain of small decisions. Anyone can see that a screen did not spring from nowhere.

The notes also preserve uncertainty. I might publish a page with a caption such as “this spacing feels crowded, but I cannot explain why yet.” That sentence is valuable because it marks an open problem rather than dressing it up as a conclusion. A week later, a change in type scale may resolve the issue, and the earlier uncertainty explains the final choice. Without that trail, the archive contains outcomes but little understanding.

This habit makes invisible context easier to manage. When I wrote about stop multitasking now, the subject was not glamorous, yet the process of naming distractions was exactly the kind of work that vanishes from conventional portfolios. Keeping the journal helped me notice which tools, meetings and browser tabs were consuming attention. The public record rewarded honesty about ordinary friction instead of showcasing only immaculate deliverables.

Keeping a record for future me

Future clients and collaborators see a snapshot of the work, but the main beneficiary is often me. Six months after a project, I rarely remember every assumption behind a layout, font choice or sequence of screens. A dated note restores the reasoning that a polished file strips away. It also makes it possible to revisit a successful pattern without repeating the whole experiment, particularly when the same issue appears across several projects.

Keeping that record has changed how I assess my own taste. I can compare a current preference with choices I made earlier and ask whether the difference came from better information or simply a different mood. The archive reveals recurring habits: I tend to overwork opening sections, trust white space more once a hierarchy is clear, and often choose photography that feels more atmospheric than explanatory. Seeing those patterns turns taste from an unexamined instinct into something I can question and refine.

Local observation often supplies the most durable references. A photograph taken in a Melbourne laneway, with a shopfront, passing tram and hard edge of afternoon light, offered more character than a generic stock image of an urban workspace. The same applies to design in the Australian market: references rooted in familiar streets, voices and routines can feel more genuine than imported trends with no local connection. Recording the source makes that intention visible.

Inviting useful outside attention

Working in public creates a low-pressure route for feedback. A reader may notice that a heading repeats a phrase already used in the body copy, or that an image carries emotional weight unrelated to the stated goal. I do not treat every reaction as instruction, but a repeated observation is a prompt to test the design again. The audience becomes an extra set of eyes, not the final decision-maker.

Pacing is part of this practice. Explaining how a decision was reached can reveal whether a project had a sensible rhythm or whether I had compressed a complicated process into a neat story. In my four-day workweek experiment, I found that written reflection created a better boundary around the day than filling every spare moment with more output. Australians often use “arvo” for the afternoon, but the underlying point was not the clock: protected time needed a clear end so work did not leak into everything after it.

There are limits to what should be shared. Comments can be sharp, personal or detached from the brief, and public visibility can make a small experiment feel larger than it is. I separate useful observations from preferences expressed as certainty. “The spacing feels heavy” may be subjective; “the gap is the same height as the type block on three screens” can be checked. This distinction keeps feedback tied to the problem and preserves the responsibility that belongs to the designer.

Showing how a team thinks

Trust rarely comes from displaying a finished interface alone. People also need evidence that decisions were made carefully, constraints were understood and feedback did not cause random changes. A public record of process supplies that evidence. It shows how a brief was interpreted, where trade-offs were accepted and how a team responded when the first plan failed.

Remote collaboration makes this visibility even more valuable. Geography can make communication feel thin: a colleague may be waiting for a train in Sydney while another is heading home in Melbourne, and a third may be starting later in Perth. Written decisions stop each update from disappearing inside a call. That is why my notes on trust in remote teams focus on repeatable habits rather than personality. Clear records, named owners and visible next steps give distant colleagues something concrete to rely on.

The same directness suits the plain-spoken way many Australian teams work. “Send it through” may sound casual, but it still needs a documented version, a deadline and a decision about who can approve it. Publishing the reasoning prevents “send it through” from becoming an ambiguous transfer of responsibility. It turns collaboration into a sequence people can inspect, which is often more reassuring than confidence expressed in a polished meeting.

Keeping the record restrained

Publication needs editing. Not every note helps another reader, and not every client conversation is mine to share. I remove names, confidential details and unfinished arguments that would be misleading without context. With permission, some project material can remain; some should stay in the archive. Restraint is an ethical choice as much as an aesthetic one, especially when a public page is treated as evidence of professional judgement.

The visual system follows the same principle. A page needs one clear purpose, a readable type scale, enough white space to reveal structure and a restrained use of colour. Photographs should clarify a point rather than decorate an empty area. Australian daylight can be severe and colour can shift quickly between a bright ferry terminal in Sydney and a shaded room at home, so editing images for consistency takes patience. The result should feel calm because the content has been made clear, not because complexity has merely been hidden.

A public design journal therefore offers more than a finished portfolio. It gives clients a way to understand the care behind the work, gives other designers a record of methods and arguments, and gives me an honest map of how I think. The pages need not document every minute, and they do not need to present a flawless sequence. They need to retain enough truth to be useful. By publishing the decisions, doubts and revisions in a restrained format, I make the process visible while keeping the work itself at the centre.