How wanting to do less work led to better results

Fine arts degree: dozens of simultaneous projects across painting, sculpture, photography, printmaking — each requiring finished physical work plus a full written process journal. First three years, I worked more hours than the calendar had. No Christmas break, mediocre output across the board, and a portfolio of completely unrelated pieces with no coherence.

The real problem wasn't the workload. It was that I was choosing each project's theme on the day I had to start it — and then brute-forcing my way through with maximum effort and no strategy.

In my fourth year, I stopped. Instead of launching straight into making things, I gathered every project brief from every subject and sat with them. I didn't touch a brush for weeks — well into late November — while I looked for a single underlying concept that could serve all of them at once.

That discomfort of not starting was real. But I pushed through it and found the thread: one conceptual project that could be adapted across all subjects and serve as the theoretical foundation for my final degree project.

The instinct to pause, map requirements, find the underlying structure, and design a system instead of grinding harder — that's been there since before I knew it had a name.

Before

No Christmas. Scattered output. Maximum effort, mediocre results. A portfolio that said nothing coherent.

After

First Christmas in four years. Less physical work, more focused output. A cohesive body of work that fed directly into my final project.

I didn't learn this in a UX course. I figured it out because I was too tired to keep working the same broken way.

I call it the laziness lightning bolt: the moment you realize that working smarter isn't a shortcut, it's just a better way to build.

This is how I approach every complex problem: pause, map the requirements, find the underlying structure, then design the system.