Cognitive Load in Student Work and Why “Over-designing” Is Often a Stress Response

When I look back at my first design projects, I don’t see bad work. I see anxious work.

At the time, I didn’t have the language for what was happening. I thought I was being thorough. I thought I was being ambitious. I thought more screens, more features, more annotations meant I was doing design “right.” In reality, I was trying to quiet a constant sense of uncertainty that sat underneath everything I was making.

My earliest projects felt overwhelming before I even opened a design tool. I was learning new software, new terminology, new frameworks, and new ways of thinking about problems, all while being asked to explain my decisions publicly. Every critique felt like a performance. Every deliverable felt like evidence that I deserved to be in the room.

So I responded the only way I knew how: I added more.

More flows, even when users didn’t need them.
More UI states, just in case.
More features to show I had “thought it through.”
More visual detail to make the work feel finished and defensible.

At the time, it felt productive. Looking back, it was cognitive overload showing up directly in my work.

As a design student, your brain is constantly switching contexts. One moment you’re thinking about user needs. The next you’re thinking about critique expectations. Then grading rubrics. Then how your work compares to the person sitting next to you. Then whether your solution is good enough or if you missed something obvious.

Psychologically, that constant context switching is exhausting. Working memory gets taxed quickly. When cognitive load increases, the brain looks for certainty. And in design school, certainty often feels like output. If I was still designing, still adding, still polishing, then I wasn’t wrong yet.

Stopping meant committing. Committing meant being evaluated.

I remember early critiques where the feedback itself wasn’t even harsh, but my body reacted as if it were. A comment about hierarchy felt like a comment about my intelligence. A question about scope felt like a challenge to my legitimacy. My nervous system didn’t distinguish between feedback on the work and judgment of me as a designer.

So instead of simplifying, I compensated.

Overdesigning became a kind of self-protection. If everything was included, nothing could be accused of being missing. If every edge case was covered, no one could say my thinking was shallow. If the interface was dense and complex, it looked like effort, and effort felt safer than restraint.

What I didn’t understand yet was that effort and clarity are not the same thing.

There’s a moment in almost every early student project where the design should stop expanding and start resolving. I didn’t recognize that moment at first. I pushed past it. My projects grew larger and heavier. Flows branched endlessly. Features stacked on top of each other. Visual hierarchy became noisy because everything felt equally important.

I was designing for hypothetical users instead of real ones because hypothetical users can’t push back. They can’t question scope. They can’t reveal that half of what I added wasn’t necessary.

In hindsight, my work mirrored my mental state perfectly. Overloaded thinking produced overloaded interfaces.

It took time for me to realize that cognitive load isn’t just something we manage for users. It’s something designers experience deeply, especially when they’re learning. Design school doesn’t just teach skills. It challenges identity. You’re not only learning how to design. You’re learning whether you trust your own thinking.

That uncertainty creates stress. And stress pushes people toward excess.

Excess feels like insurance.

One of the most important shifts for me came when I started paying attention to why I was adding things, not just what I was adding. If I couldn’t clearly explain why a feature existed, it usually meant I was afraid to remove it. If everything felt important, it usually meant I hadn’t made a real decision yet. If the design felt heavy, it was because I was carrying too much uncertainty into it.

Over time, I stopped seeing overdesigning as a mistake and started seeing it as information. A signal that I didn’t yet trust my judgment.

That reframing changed how I worked.

As I gained more experience, my projects became smaller but stronger. Fewer screens, but clearer flows. Less decoration, but more intention. I wasn’t working less. I was deciding more. I learned that clarity doesn’t come from adding until something feels impressive. It comes from choosing what matters and letting the rest go.

That confidence didn’t arrive all at once. It came from repetition. From being wrong and surviving it. From realizing that critique didn’t erase me. From understanding that design isn’t about solving everything, it’s about solving the right thing.

Now, when I see overdesigned student work, I don’t see incompetence. I see someone holding too much at once. I see someone who cares deeply and hasn’t yet learned that care doesn’t need to be proven through volume.

Reducing cognitive load in design often starts with reducing it in yourself. That means slowing down. Naming the core problem in plain language. Trusting that you don’t need to account for every scenario to create something meaningful.

It means understanding that clarity isn’t a lack of effort. It’s evidence of confidence.

If I could talk to my earlier self, late at night on those first projects, I wouldn’t tell them to do less. I’d tell them they’re not overdesigning because they’re incapable. They’re overdesigning because they’re learning. And learning is messy before it becomes elegant.

Clarity comes later. One decision at a time.