Dear Students,
There’s a moment in every designer’s journey when you realize something important:
You weren’t actually taught how to be a designer.
And neither was I.
We were taught software. (If you were lucky)
We were given projects.
We were introduced to principles.
But the transition between student work and professional practice was often left unspoken.
And for many of us, we learned that gap the hard way.
The First Real Lesson
One of my first design jobs was at MGM MIRAGE in Las Vegas.
I remember building a file and sending it to a printer, completely confident that everything was correct.
The response was simple:
"Your file was not built correctly."
I remember staring at that sentence trying to understand what I had done wrong.
I didn't even know that was something you could get wrong.
So, I did something that changed everything.
I drove to the print shop.
I asked them to show me.
That day I learned how to properly prepare files for production. I learned what separations were and why they mattered.
Not from a lecture.
Not from a textbook.
But from real work in a real environment.
That experience taught me something important:
Design doesn't end when the design is finished.
What Was Missing
Looking back on my undergraduate experience, I learned a lot about design.
Typography.
Layout.
Composition.
Visual communication
What I didn't learn was how design functions in the real world.
I wasn't taught how to choose the right software for different types of projects.
I wasn't taught how files move from designer to printer.
No one explained what happens after you hit "Export."
No one showed me how production requirements influence design decisions.
At the time, I didn't realize those were gaps.
I only discovered them once I entered the workforce.
And honestly, most designers do.
How It Shaped My Teaching
That lesson stayed with me throughout my career.
When I eventually became a design educator, I didn't build courses around what had always been taught.
I built them around what I wished someone had taught me.
I didn't want students learning essential professional skills through confusion, failure, or trial by fire.
I wanted them to understand the foundations before they were expected to perform under pressure.
In graduate school, while preparing to teach my first Introduction to Graphic Design course, I reviewed how students were being introduced to software and technical skills.
I quickly realized that many students were expected to figure out foundational tools on their own.
That experience inspired me to create a course that gave students a strong introduction to Adobe Illustrator, Photoshop, and InDesign before they were expected to use them independently.
My goal was simple:
Give students the knowledge I wished I had received.
The Missing Piece: Context
The more I've taught, the more I've realized that most students don't need more assignments.
They need context.
They need to understand not only what to do, but why it matters.
Design education teaches principles.
Professional practice teaches application.
The challenge is learning how to connect the two.
That's the bridge that transforms a student into a designer.
A Truth About Education
One thing I've learned as both a student and educator is that every design education program is different.
Some focus heavily on concept development.
Others emphasize technical skills.
Some do a better job connecting classroom projects to professional practice.
As a student, it's important to understand those differences before investing your time and money.
Visit the schools you're considering.
Talk to instructors.
Talk to students.
Look at the work being produced.
Ask questions.
The strongest programs don't just teach design.
They help students understand how design works in the real world.
What Being a Designer Really Means
The truth is, becoming a designer doesn't happen when you learn the software.
It happens when you learn how to use your knowledge to solve real problems for real people in real situations.
That's why context matters.
That's why production matters.
That's why understanding the entire process matters.
Because the goal was never just to make things look good.
The goal was to make things work.
To communicate clearly.
To function within real systems.
To meet real expectations.
That's what being a designer actually means.
Final Thought
If you are struggling as a designer, remember this:
Most of what feels difficult isn't a lack of talent.
It isn't a lack of creativity.
It isn't a lack of potential.
More often than not, it's a lack of exposure to how design actually functions in the real world.
And that's something every designer learns eventually.
Some of us just learn it a little later than others.
“The truth is, becoming a designer doesn't happen when you learn the software. It happens when you learn how to use your knowledge to solve real problems for real people in real situations.”
In design truth,
Maggie