I didn't go to design school. What I know came from shipping things wrong, then less wrong.
Somewhere in that process, I compiled a list. Not rules — just truths I wish someone had handed me early. They're not in any syllabus.
We are what we ship. Not what we sketch.
Everyone has good ideas in their sketchbook. The designers who matter are the ones who put their work in front of real users and deal with what happens next. Your sketches are intentions. Shipped work is evidence.
Fight for your users — it's part of your job.
Not every design meeting is a fight. But some are, and in those moments your job is to be the voice of the person not in the room. No one else in the room is there specifically for the user. You are.
Show, don't tell. Let your designs speak.
If you need five minutes of explanation before anyone understands what they're looking at, the design hasn't done its job yet. The goal is to walk in with a prototype, not a presentation about the prototype.
Design is business, but it's also art.
You need to know what the conversion rate is. You also need to care about the quality of experience you're creating. Both matter. Treating it as purely functional is how you get software that works but nobody wants to use. Treating it as purely aesthetic is how you get beautiful things no one needs.
Storytelling is your superpower. Use it.
The best design presentation I've sat in didn't start with screens. It started with a user's journey — what they were trying to do, where they were getting stuck. By the time the designs appeared, everyone in the room already cared. The work landed because the story landed first.
No great design without great tech partners.
Your design is only as good as what gets built from it. That means the relationship with engineering is part of the design process, not a handoff at the end. The earlier you bring engineers into your thinking, the fewer surprises you'll have at implementation.
Adapt your process — it's not always double diamond.
Double diamond is a framework, not a law. Some projects needed six rounds of research, user testing, and iteration. Others needed me to find the closest existing pattern and ship in a week. The designers who ship well know when to compress the process without skipping the thinking.
Master both upward and downward management.
Managing up means knowing when to escalate, how to frame a concern, and what language stakeholders respond to. Managing down — if you're a lead — means protecting your team from noise so they can do the work. Both are design skills. Neither is taught in a course on color theory.
Learn to say no and hold your ground.
This one took me the longest. Saying no requires a specific reason, not just a preference. The more precisely you can articulate why something hurts users, the easier it is to hold that position. "I don't feel good about this" won't work. "This breaks the mental model users already have, and we know from session recordings that it causes drop-off" will.
Build your personal brand.
You are not just the work you do inside your company. The work you share publicly — case studies, frameworks, essays — shapes who you become over time and who finds you. I started late. I wish I'd started earlier.
Document design decisions.
Future you — or the next designer on this product — will thank you for writing down why you made the call. Not just what you decided, but the tradeoffs you considered. A comment in Figma that says "I tried X here but switched to Y because of Z" is more useful than three weeks of the next designer guessing.
Design for the Minimum Desirable Product, not just viable.
MVP is often the floor. MDP asks: what's the minimum that someone would still genuinely want to use? That's a harder question, and it's usually the right one. Viable means it works. Desirable means it's worth someone's time.
80% of designs get discarded. It's the cost of innovation.
I spent three weeks on a feature at MontyCloud that got cut. I was frustrated for a day. Then I realized the exploration itself had changed what the PM understood about the problem. The design got cut. The knowledge didn't.
None of this was in any curriculum. It's the stuff you figure out after you've shipped enough things, watched some of them fail, and had to come back the next day and design something better.
Credits & further reading
- Articulating Design Decisions — Tom Greever (O'Reilly). The best book on presenting design work to people who aren't designers. The "why is this better than the alternative?" framing directly shaped how I think about holding ground in design reviews.
- Lean UX — Jeff Gothelf & Josh Seiden. Where the Minimum Desirable Product framing originates. Reframes the design process around outcomes and desirability, not just deliverables.
- Double Diamond — Design Council UK (2005). Worth learning in full before you learn to deviate from it.
- 10k Designers (Abhinav Chikkara, Ansh Mehra) — many of these lessons sharpened through their curriculum and community.