Most teams think great design is about talent. It’s not. It’s about a standard.
Look around at the stuff people love using. The apps. The pages. The products. None of it happened by accident. Somebody cared about the small things everyone else ignored.
That “somebody” doesn’t have to be a designer. It can be your whole team. An engineer. A support rep. A marketer. Anyone. If they know what “good” looks like and feel free to say when something’s off.
That’s the difference between a company that talks about quality and one that ships it.
And it’s learnable. Not magic. Not a gift you’re born with. Just five simple principles you can build into how your team works every single day – so excellence stops being random and starts being normal.
Get these right, and people will feel it in everything you make. Your product. Your emails. Your reports. Even your slides. They won’t know why it feels better. It just will.
Why This Actually Matters
In most companies, quality depends on one or two people noticing things. The sharp designer who catches the clumsy layout. The detail-obsessed founder who rewrites the awkward email. As long as they’re in the room, the work is good.
But the moment they’re busy, on leave, or stretched thin – standards slip. Quality wasn’t built into the team. It was leaning on a few people. That’s not a culture. That’s a bottleneck waiting to break.
The solution is we stop making “good” one person’s job and make it everyone’s. You give the whole team a shared sense of what well-made looks like, the permission to speak up when something feels off, and simple habits that bake the standard into daily work. Design stops being a department. It becomes a reflex.
The result: Now excellence shows up everywhere – not because you checked it, but because the team can’t help it. The product feels thoughtful. The pages feel clean. The reports, the slides, the support replies – all of it carries the same care.
Customers feel it before they can explain it. And the best part? It holds even when you’re not looking. That’s when “good design” stops being something you do, and becomes who you are.
So here are the five principles that turn “we should care about design” into “we can’t help but make good things.” Read them. Then put them to work.
5 Principles for Better Design
Principle #1: Empathy – Build for the real person, not the one in your head.
Have you ever built something based on what you ASSUMED people wanted? Then, found out the real need was completely different, the moment you actually watched them use it?
I have. And it taught me the most important rule in design.
Most teams start building from a guess.
“Users probably want more options.” “They’ll figure this out.” “This makes sense to me, so it’ll make sense to them.”
Then we ship it, and it flops. Not because the team isn’t smart, but because we designed for the person in our head, not the person on the other end.
So here’s the simplest framework I can give you. Three words:
WATCH → WHY → BUILD.
Watch what people actually do, not what they say.
Why – dig into the reason behind that behavior.
Build the fix for the real need, not your assumption.
Let me make it real.
A software team adds a signup flow with 8 customization steps. Their logic: “More control = happier users.” Makes sense, right?
But signups start dropping. So instead of guessing again, they watch 10 real people try it. They track the steps of the users using their own tracker.
Every single one freezes around step 4, clicks around confused, and half just leave.
They ask why. Turns out people didn’t want control – they wanted to see their result fast. The 8 steps felt like homework.
So they build the fix: cut it to 2 steps, show the result instantly, let people customize after they see value. Signups jump. Same team, same skill. They just stopped guessing and started watching.
Now here’s what most people don’t know:
Asking people what they want is the weakest research you can do. People are terrible at predicting their own behavior. They’ll tell you they want more features, then never touch them. They’ll say a flow is “fine,” then rage-quit it the next day.
The gold isn’t in what they say. It’s in what they do. The step they skip, the field they leave blank, the workaround they invent, the support ticket they angrily type at midnight. That’s the truth. Stated opinions lie. Observed behavior doesn’t.
So leaders, before your team builds the next feature, page, or report, ask one question:
“Have we watched a real person actually do this, does multiple users requested this, or are we still guessing?”
That single question is empathy in action. And it’s where great design begins.
Principle #2: Taste – Know the difference between “good enough” and excellent.
What does “well-made” actually mean to you? And how do you hold that bar high – without crushing your people?
“Excellence” sounds nice on a wall. But in real work, it lives in tiny details most people walk right past. A button that’s two pixels off. A clumsy sentence in a welcome email. One confusing step that makes a customer pause.
Taste is just the ability to notice those things – and care enough to fix them.
But here’s the trap. If you only ever say “make it better,” people get lost. Better how? So here’s the simplest framework I can give you:
NAME IT → SHOW IT → RAISE IT.
Name it – point to the exact thing that’s off. Not “this feels weak.” Say “this headline is vague” or “these three buttons don’t line up.”
Show it – put a good example next to a bad one so people see the difference, not just hear about it.
Raise it – fix it together, so the bar goes up for everyone, not just this one task.
Let me make it real.
A software team ships a settings page. It works. Nothing’s broken. But it feels… clumsy. A weaker leader says, “Make it cleaner,” and walks away – and the team has no idea what that means.
A leader with taste does the opposite.
They name it: “The labels are inconsistent – some say ‘Edit,’ some say ‘Change,’ some say ‘Modify.’ Pick one.”
They show it: “Look at how Stripe does their settings – every action uses the same word.”
Then they raise it: “From now on, one action, one word. Let’s make that our standard.”
Same page. But now the whole team just leveled up – not because the leader was harsh, but because they were specific.
Taste isn’t something you’re born with. It’s trainable. It grows from seeing tons of examples – good and bad – and naming why each one works or doesn’t.
But there’s a catch nobody warns you about: the taste gap. Your ability to recognize great work grows faster than your ability to make it. So your team will start seeing flaws in their own work – and feel like they’re failing. They’re not. That gap is proof that their taste is growing. The job of a leader is to tell them that out loud, so they push through instead of quitting.
So leaders, before you say “make it better,” ask yourself:
“Have I named the exact thing or am I just saying I don’t like it?”
Specific feedback builds taste. Vague feedback builds frustration. That’s the difference between a leader who raises the bar and one who just complains about it.
Principle #3: Iteration – Ship it rough, then make it great.
Have you ever waited too long to “perfect” something, when shipping a rough version first would’ve gotten you there faster?
Most people think great work appears in one shot. It doesn’t.
Behind almost everything that looks polished is an ugly first draft nobody saw. The secret isn’t getting it right the first time. It’s getting it out, then making it better, fast.
But here’s where teams freeze. They sit on work because it’s “not ready yet.” Weeks pass. They’re polishing in the dark, guessing what’s good, instead of letting reality tell them. So here’s the simplest framework I can give you:
ROUGH → REACT → REFINE.
Rough – make the messy first version. Fast. Done beats perfect.
React – put it in front of real people and watch how they respond.
Refine – fix what’s actually broken, then loop again.
Then repeat. v1 → v2 → v3. Each loop makes it sharper.
Let me make it real.
A software team needs a new homepage. The old way: spend three weeks perfecting one version in private, then reveal it like a magic trick. It looks beautiful – but visitors don’t click. Now they’ve wasted three weeks on a guess.
The iteration way: build a rough version in two days. Ship it.
React – watch where people click, where they leave, what confuses them. Turns out the headline’s unclear. Fix it – that’s v2. Now the button’s hard to find. Fix it – v3.
Within the same three weeks, they’ve improved it five times based on real behavior, not opinions. Same effort. Far better result.
Rough work gets you better feedback than polished work. This sounds backwards, but it’s true.
When something looks finished, people hold back. It feels rude to ask someone to redo all that hard work, so they say “looks good!” and stay quiet.
But when something looks like a rough sketch, people feel free to reshape it. They’ll tell you the truth, because nothing feels precious yet.
So polish actually hides problems. It invites politeness, not honesty. If you want real feedback early, keep it rough on purpose.
So leaders, when your team is stuck perfecting something behind closed doors, ask them:
“Can we ship a rough version this week and learn from real people or our teammates – instead of guessing for three more weeks?”
Speed isn’t the enemy of quality. Slow, secret, perfecting is. The teams that improve fastest aren’t the ones who get it right first – they’re the ones who loop the most.
Principle #4: Simplicity – The best design is what you remove.
When something isn’t working, your team’s instinct is to ADD – more steps, more features, more words. But have you ever made something better by removing things away?
We treat “more” as progress. More options. More buttons. More explanation. It feels like we’re improving things.
But usually we’re just making them heavier. The best products, pages, and reports aren’t the ones with the most in them – they’re the ones with nothing extra. Every part that doesn’t earn its place is just in the way.
But subtraction is hard, because removing things feels risky. “What if someone needs that?” So clutter piles up.
Here’s the simplest framework I can give you:
LIST → CUT → KEEP.
List everything that’s in there – every step, field, feature, sentence.
Cut anything that isn’t pulling its weight. Be ruthless.
Keep only what the person truly needs to succeed.
If you’re unsure whether something stays, that’s usually a sign it goes.
Let me make it real.
A software team builds a dashboard. Over time, every request gets bolted on – 12 buttons, 9 charts, 4 menus.
Everyone asked for something, so it all stayed. Now new users open it and freeze. It’s powerful, but nobody can find anything.
A leader who gets simplicity steps in.
They list every element on the screen.
They cut hard – “These 3 charts get used once a year. Hide them. These 5 buttons do almost the same thing. Merge them.”
They keep the 3 things people use every single day, front and center. The dashboard didn’t lose power. It gained clarity.
Suddenly people get it in seconds.
Our brains are basically blind to subtraction. There’s real research on this – a study by Leidy Klotz. When people are asked to improve something, they almost always add, even when removing would obviously work better. We don’t even see the option to take away. It’s a blind spot built into how we think.
That’s why your team will never subtract on their own. It’s not laziness – their brains literally skip past it. So the fix is to ask out loud, every single time: “What can we remove here?” If nobody asks, nobody sees it.
So leaders, in your next review – of a page, a flow, a report, a slide – before anyone adds a thing, ask:
“What can we remove to make this clearer?”
Adding is easy. Anyone can pile more on. The real skill – the thing that signals true craft – is knowing what to cut.
Principle #5: Shared Ownership – Design is everyone’s job, not one person’s.
If “thoughtful and well-made” depends on one person catching every mistake – what happens the day they’re not in the room?
Here’s the trap most companies fall into. They make design “the design team’s job.” Everyone else shrugs and says “not my department.”
So quality lives or dies on a few people noticing problems. The moment those people are busy, on leave, or stretched thin – standards slip. That’s not a culture of excellence. That’s a bottleneck.
Real design DNA means anyone on the team can spot when something feels off and say so. Engineer, CS rep, QA, DA, marketer – doesn’t matter.
So here’s the simplest framework I can give you:
LANGUAGE → PERMISSION → RITUAL.
Language – give everyone shared words for what “good” means, so they can name problems clearly.
Permission – make it safe and expected for anyone to flag something that feels off, no matter their title.
Ritual – build one repeatable habit that bakes the standard into how you work, so it doesn’t depend on memory or mood.
Let me make it real.
A software team has one sharp designer who catches everything – clumsy wording, broken layouts, confusing steps.
The work is great… until the designer goes on leave. Suddenly, the quality drops because nobody else felt it was their job to care.
A leader who gets shared ownership fixes this.
They build language – “Here’s what ‘clear’ and ‘clean’ mean for us.”
They give permission – “If anything feels off, say it. I don’t care if you’re an engineer reviewing a sales page.”
And they add a ritual – one simple question asked in every review: “Does this feel well-made?”
Now the standard lives in the whole team, not one person. The work stays excellent even when anyone’s away.
The most design-driven companies don’t have the most designers. They have the most shared design sense.
When an engineer can say “this flow feels off, and here’s why,” or a support rep can say “this email sounds cold” – design becomes self-correcting.
Problems get caught everywhere, by everyone, automatically. You don’t need a bigger design team. You need a standard that spreads.
And here’s the part that reframes the whole job: as a leader, your goal isn’t to be the best designer in the room. It’s to make the standard so contagious that your team catches mistakes without you.
If everything still depends on you, you haven’t built a culture – you’ve built a dependency.
So leaders, the real question to keep asking is:
“Does my team hold this standard when I’m not looking?”
That’s the finish line. Not work that’s great because you checked it – work that’s great because everyone owns it.
That’s when design finally becomes part of who we are.
That’s all five principles complete: Empathy → Taste → Iteration → Simplicity → Shared Ownership.
What the Masters Say About Design
“Design is how it works.” Steve Jobs – co-founder of Apple. Design isn’t decoration. It’s whether the thing actually does its job for the person using it.
“We try to develop products that seem somehow inevitable.” Jony Ive – Apple’s former Chief Design Officer, who led the design of the iPhone, iMac, and iPod. Great work feels obvious in hindsight. That “of course” feeling is the goal.
“Less, but better.” Dieter Rams – legendary Braun designer whose work directly inspired Apple. Excellence comes from subtraction. Cut what doesn’t earn its place.
“The details are not the details. They make the design.” Charles Eames – mid-century designer behind the iconic Eames chair. The small stuff everyone ignores is exactly where quality lives.
“Design is the silent ambassador of your brand.” Paul Rand – graphic designer who created the IBM, ABC, and UPS logos. Everything you make speaks for you – before you say a word.
The Bottom Line
Great design was never about talent or having the most designers. It comes down to five simple habits any team can build:
Watch real people instead of guessing (empathy), name the exact thing that’s off (taste), ship rough and improve fast (iteration), cut what doesn’t earn its place (simplicity), and make the standard everyone’s job, not one person’s (shared ownership).
Get these right, and excellence stops being random. It becomes normal.
Don’t try to do all five at once. Pick one. This week, in your next review – of a page, a feature, a report, a slide – ask a single question out loud: “Have we actually watched someone use this?” or “What can we remove to make this clearer?”
That one question, asked again and again, is how a value turns into a habit. Then add the next. Small, repeated, on purpose.
Here’s the real test, and it’s the one that matters most: does the work stay great when you’re not looking?
That’s the finish line. Not good because you checked it – good because your team can’t help but make it that way.
Build that, and design stops being something Codalify does. It becomes who we are.
