Engineering · 3 min read
How we design
Design is the whole shape of the thing, not a coat of paint at the end. This is how we think about craft.
Design at Flagon isn't the part where someone makes it pretty before launch. It's the shape of the thing itself: what it does, how it behaves when you're confused, what it asks of you and what it does on your behalf. By the time you're picking colors, most of the real design decisions are already made or already blown. We treat design as a way of thinking about the whole product, and we hold it to the same standard as the code underneath it.
Design is the shape, not the skin
You can put a beautiful surface on a confused idea and it's still a confused idea. Layout, flow, the words on the buttons, what happens when nothing has happened yet: those are design, and they're decided long before anything gets styled. So we start with the shape. What is this for, who's in the middle of doing something when they reach it, and what's the shortest honest path through it?
If the underlying model is wrong, no amount of polish saves it. If the model is right, a plain version of it already works. Get the bones right first.
Sweat the parts most people skip
The character of a product lives in the moments nobody demos. The empty state before you've done anything. The error copy when something breaks. The first five minutes, when a person is deciding whether this thing respects their time. Most teams leave those to last, or to nobody. We treat them as the work.
An empty state is a chance to teach instead of a blank shrug. An error message is a chance to tell the truth instead of hiding behind "something went wrong." Spend real attention there, because that's where taste actually shows up. This is the same idea as have a point of view: character comes from caring about the parts most people skip.
Not done until it's unmistakably ours
If a competitor could ship the same screen and nobody would blink, it isn't done yet. The details are where it becomes ours.
Taste is a discipline, not a mood
Taste sounds like something you either have or you don't, but in practice it's a habit: a lot of small decisions made by someone who cared, and who kept asking "is this actually good, or just done?" We treat it as a discipline you practice, not a vibe you're born with. That means looking at the thing with fresh eyes, cutting the option that's there out of habit, and being willing to redo the part that technically works but feels wrong.
It also means having an opinion and being able to say why. "It feels off" is a start; the job is to find what's off and fix it. Taste that can't explain itself is just preference, and preference doesn't hold up under a "why."
Design and engineering are one conversation
We don't hand a finished mockup over a wall and wait for it to come back built. Design and engineering are the same conversation, running from the first sketch to the last edge case. The person building it will find the constraint the mockup ignored; the person designing it will catch the interaction the code got lazy about. Both of those are the work getting better, not someone stepping on toes.
Small changes are how this stays honest. A shape you can see running tells you more than a shape you argued about in the abstract, which is exactly why we ship the smallest useful change and adjust from something real. Design isn't a phase that ends. It's how we build, and it connects straight to how we build: boring where boring wins, opinionated where it counts, and always closer to something you can actually hold.