We’ve all been there: following a step-by-step YouTube video, perfectly replicating a glassmorphism card or a complex micro-interaction. At the end of the 20-minute video, you have a beautiful screen. But do you have a design?
The uncomfortable truth is that Tutorials are execution; Design is decision-making.
The Difference Between "Copying" and "Building"
When you follow a tutorial, the instructor has already done the hardest part of the job. They have already:
- Identified the user problem.
- Framed the constraints.
- Weighed the trade-offs.
- Selected the visual hierarchy.
You are simply mimicking their clicks. This builds Tool Proficiency, not Design Thinking.
The "Cat" Analogy: Why Patterns Matter
In my guide "How to Design Faster," I talk about how our brains recognize a cat because we have a vast collection of cat images stored in our memory. Design is the same. Speed and skill don't come from following a recipe; they come from a collective knowledge of patterns.
If you only follow tutorials, you aren't building a library of patterns; you are building a library of someone else's solutions.
How to Truly Level Up
- Deconstruct, Don’t Copy: Instead of following a tutorial, take a finished design and try to figure out why the designer made those choices.
- Solve Real Problems: Find a "broken" experience in an app you use and try to fix it.
- Feed Your Brain: Design perception is a combination of what you see and your past knowledge. Feed your brain with diverse ideas, not just UI tutorials.
The Bottom Line: Stop looking for the "Next" button in a video and start looking for the "Why" in a user flow. That is where the designer is born.
Comments