You don't need an art degree to choose colors that work — you need three or four reliable rules, applied consistently. Here's the practical version, without the jargon.
Start from the color wheel, not your gut
The color wheel arranges hues in a circle, and where colors sit relative to each other predicts how they'll feel together. You don't need to memorize the wheel — you just need three relationships from it:
- Complementary — colors opposite each other (blue/orange, red/green) create high contrast and energy. Good for a single accent, overwhelming as a full palette.
- Analogous — colors next to each other (blue, teal, green) feel calm and cohesive, since they share an underlying hue. Safe, harmonious, occasionally a little flat if overused.
- Triadic — three colors evenly spaced around the wheel give vibrant contrast while staying balanced, but need one color to clearly lead so the palette doesn't compete with itself.
One color leads, the rest support
The single most common mistake in an untrained palette is giving three or four colors equal visual weight. Pick one dominant color for roughly 60% of the interface, a secondary color for about 30%, and an accent color for the remaining 10% — buttons, links, the things that genuinely need to grab attention.
Saturation and lightness matter more than hue
Two colors with the "wrong" hue relationship can still look great together if you match their saturation and lightness. This is why muted, desaturated palettes almost always look more sophisticated than a set of pure, fully-saturated colors — it's not really about which hues you picked, it's about restraint in how loud each one is.
Contrast is a rule, not a suggestion
Text needs to be genuinely readable against its background — this is a real accessibility requirement (WCAG), not a style preference. As a working rule of thumb: if you have to squint or guess whether text is legible, the contrast is too low. Check it, don't eyeball it.
Color carries meaning whether you intend it or not
Red commonly reads as urgent, error, or stop. Green commonly reads as success, safe, or go. Fighting these learned associations (making your error state green, for instance) creates friction even when the rest of the design is excellent — pick colors for status and feedback states that align with what users already expect.
A limited palette used with confidence will always beat an ambitious palette used with hesitation.
Steal wisely, then adjust
Looking at palettes from designs you admire and adapting them is a completely legitimate way to work — designers do this constantly. The skill isn't inventing colors from nothing; it's recognizing why a palette works (dominant/secondary/accent balance, consistent saturation) and applying that same structure to your own project.
The takeaway
Pick one dominant color, one supporting color, and one accent. Keep saturation consistent. Respect contrast requirements. Respect the meanings colors already carry. That's most of color theory that actually matters day to day.
Keep reading
Related articles
The Beginner's Guide to Figma: Design Your First Screen
Frames, components, auto-layout and prototyping — everything you need to go from blank canvas to a polished mockup.
Building a Design System That Scales With Your Team
Most design systems start strong and quietly rot within a year. Here's what actually keeps one alive as a team grows.
AI Design Tools: Where They Help and Where They Still Fall Short
Generative AI can produce a decent-looking screen in seconds. It still can't do the part of design that actually matters most. Here's the honest split.
Discussion
Leave a comment
Your email stays private and is never published.