Design work is often asked to explain itself in one particular format. There should be a clear problem, an orderly process, a confident solution and an outcome that can fit beneath a polished heading. That structure can be genuinely useful. It helps other people understand decisions, and it can reveal whether the work actually answered the question it began with.
It is not, however, the only reason to make something.
Some projects exist to teach me a tool. Some preserve a story I do not want to lose. Some test one interaction, translate an idea into a shape, or answer a question that may never become a product. A few are simply enjoyable. Forcing all of them into the same professional case-study structure can make the explanation larger than the work.
Different work, different jobs
This website is deliberately not organised around recruitment. That does not mean professional work is unwelcome here, or that conventional portfolios are pointless. A strong case study can be a generous, rigorous account of practice. I just do not want every part of my creative life to audition for the same role.
An experiment can remain an experiment. A note can stay brief. An unfinished study can still show the exact question that made it useful. The measure should match the project’s job.
That has changed the way I think about things such as Perah Lab and the small concepts living in the Build room. They do not all need grand origin stories or invented impact. They need accurate descriptions: what they are, why I made them, what I learnt, and whether they are still moving.
Useful without being complete
There is also a practical freedom in keeping some work small. It becomes easier to share an early model, archive a paused idea or admit that a project taught me something without becoming something itself. The alternative is a cupboard full of work waiting for enough polish to justify its existence.
I am not lowering the standard for work that carries real responsibility. Client work, public tools and research claims deserve care and evidence. I am widening the number of honest endings available to personal work.
A project may become a case study. It may become a product, a story, a reference, a private lesson or a link I send to one curious person. Those are different outcomes, not necessarily a hierarchy. Sometimes the most truthful thing a project can say is simply: this helped me see the next question more clearly.