In June 2026 I had the chance to present at the Pixel Pioneers event. Here is the corresponding blog post.

Being a designer often comes with the assumption that we can clearly picture the outcome before it exists. We may be expected to have a vision, imagine the outcome, and “see” the solution early on.

But what if you can’t? Not all designers work that way, and in this post, I’ll explore ways to design without relying on mental imagery or a fully formed vision. Drawing from my experience with aphantasia and enterprise B2B design work, I’ll show how replacing imagined outcomes with structure, language, and shared artefacts leads to clearer decisions, better collaboration, and understanding.

As AI develops at a rapid pace, design system documentation is struggling to keep up. Documentation now serves two very different audiences: humans and machines.

Since the rise of design systems, teams have relied on documentation to explain how components, tokens, and patterns should be used. Traditionally, this documentation was written by humans, for humans. It told designers and engineers which tokens to use, how much spacing was required, and which button variant belonged in a particular context.

It is clear to see, even if you do live in a cave, that AI is everywhere. I can’t read a job description or open my phone without being reminded of its pervasive existence. I, like many others, need to learn how to integrate this new-ish technology into my work. This is part one of trying new tools to update my design process.

I started with Lovable because I had a quick page to design and deploy. The task was straightforward; I needed a single static page with buttons that go to external links. It needed to be in keeping with the TriviaPostman brand, and as this was a page most likely found on social media platforms, it needed to be mobile-friendly.