Looks Good, Now What – Luka Gray

Creative Work as Argument

"Design is an art of thought directed to practical action through the persuasiveness of objects and, therefore, design involves the vivid expression of competing ideas about social life."
Richard Buchanan

Design isn't taste. It's persuasion. So far, we've stripped that idea down and proven that decoration alone isn't enough. Design has a job: to solve a real problem. By shifting focus—framing the problem—we found a more straightforward path forward.

Now the setup's over. You need to explain why your design works. Not just what you made, but why it matters. Your next task is straightforward: prove that your solution can withstand criticism.

Weathering criticism is where Buchanan's quote steps in. He treats design like public debate, made physical. Every choice you make is an argument. A grid says, "Focus here." A flash of Orange says, "Act now." A headline sets the stakes. And if you can't justify a choice, cut it.

What Design Actually Says

Design school teaches you that every choice carries meaning. It's your job to shape that message through research, observation, and instinct. But messages drift. Slowly, quietly, your design can start saying things you never intended. A soft, human brand starts to feel clinical—a friendly layout shifts into something cold and corporate. And suddenly, the work feels wrong. Not broken, just off. And no one can quite explain why.

That's why starting with perspective, not isolated choices, matters. Perspective provides a common ground for you and your team. It's easier to debate, easier to clarify, easier to align around. It sets the expectation that every part of the design serves a purpose. Not to look good or feel right, but to convey a specific message. When the work feels off, you won't waste time arguing taste. You ask the fundamental question: Does this match the perspective we set? Perspective shifts feedback from opinion to problem-solving. It keeps your decisions sharp and your process intentional.

With a foundation set, it's now time to pressure test its strength. That's where the argument comes in. Your work doesn't just express a point of view. It argues for it. Every decision is a claim. Every choice is evidence, and the whole thing needs to stand up when questioned. Perspective sets direction. Argument proves it, turning vision into something defensible.

From Choice to Argument

Put every design decision on trial. Forget checklists. Build reflexes. Keep the problem statement in view and ask yourself one thing: does this move the goal? If you hesitate, push harder. Is it just visual noise, or does it earn its place? Will the right people feel it? Could a stakeholder tear it apart with valid concerns?

Sometimes you'll end up questioning the foundation, all the parts we have built so far. That is part of our process. An iterative pressure-testing of our thinking exposes weak spots that you may have missed. Treating design as an argument doesn't mean avoiding risk. It means owning it. You're not playing safe; you're pushing boundaries with purpose.

Trust your gut before you reach for a framework. If something feels off, it probably is. Most interesting perspectives don't start as bullet points. They begin as hunches. The framework that follows isn't mine. It's a classic argument structure: claim, evidence, warrant. I'm just applying it to design. Here's your quick, no bullshit way to see if your instincts can hold.

  • Claim: State your choice. No hedging.
  • Evidence: Support it with something tangible, such as research, data, or personal experience.
  • Warrant: Show why it matters. Connect your proof to the bigger goal. Make the link obvious.

Every design argument needs a clear claim, evidence to back it up, and a reason why it matters to the goal.

If this feels familiar, good. It mirrors what we unpacked back in Creative Theory in Design: Purpose, Audience, and Context. Purpose helps shape your claim. Audience builds your evidence. Context completes your warrant. Same thinking. Different scale.

Here's a simple example.

  • Claim: "I believe changing the button to bright orange will help."
  • Evidence: "In testing, the orange button increased clicks by seventeen percent compared to the old blue one."
  • Warrant: "Orange draws attention faster, which supports our goal of driving stronger engagement."

The point isn't that color changes drive traffic by magic. It's that design influences behavior in subtle, measurable ways. And more importantly, the choice can be explained, tested, and defended. That's claim, evidence, and warrant in action. Feel first, prove second. The framework sharpens your instincts. It doesn't replace them. It only works when your inputs are clear and your honesty is brutal. Use it to expose weak points, not to conceal them.

If the process feels clinical, pause. Design is still about emotion, taste, and voice. The framework gives that spark structure and credibility, but it never replaces it. A riot of color can be exactly right when the brand demands it—think early-era MTV. Loud for the sake of loud is just noise. The difference is intent.

And finally, close the loop in writing. One short note is enough. Something you can repeat back if someone questions you later—and sometimes, that person will be you. Record what you chose, why it matters, how you'll measure success, and which options you deliberately left behind. Now your argument's ready. Anyone can question it. You'll be prepared to answer.

Design That Survives Pushback

Pushback is inevitable. Silence usually means you played it too safe. When critique comes, it isn't a crisis; it's your cue to argue for your decision. And you're ready. The note you wrote after each choice already holds the raw material: what you did, why it matters, how success will be tracked, and what alternatives were rejected.

When questioned, unpack that note. Rebuild it into the claim, evidence, and warrant model. Your choice is the claim. Your testing results, research, and insight are your evidence. The reason that proof matters to your goal? That's your warrant. From a single note, you now return to a whole argument.

Now the conversation between your director, the client, or a stakeholder shifts. Design decisions that felt instinctive become structured replies. It no longer matters whether the original move was based on gut or data. Your logic is sound, and it can withstand scrutiny. You can reinforce your reasoning in real time.

That is how credibility starts. Not with authority. With clarity. When critique comes, and it will, your work should answer for itself. You're just speaking for it.

What Makes Work Credible?

Credibility isn't a bonus feature. It's the backbone of good work. And you don't get there with clever language or flashy case studies. You earn trust the same way outside the project as you do inside: by being honest. If you're bluffing, hedging, or covering gaps with confidence tricks, it shows in the work and the presentation.

Start with honesty. No exceptions. As Kant said, "Honesty is better than any policy." That's your foundation. Lay out your receipts. Walk people through your thinking. Cite your sources. People don't care about polish if they can't see the structure underneath. Whether your credibility comes from experience, research, or results, state it clearly before you dive into your logic. Trust builds when people know they're getting the full picture.

Credibility also means showing your doubts. Point to precedent. Name your limitations. Let people see where you're working from and what you're still figuring out. This exposure is simply about being transparent, and transparency isn't a weakness. It invites people into the thinking. It signals that you're not just selling; you're collaborating, and that shifts the room.

Credibility is fragile. It takes time to build, and a single mistake can break it. So keep your work rooted in something real. Put your evidence on the table. Own what you know. Mark what's still in progress. That's how trust starts. And how it stays.

Balancing Logic and Emotion

If credibility is your entry ticket, emotion is the main event. Honesty and transparency matter for a simple reason. Design is built to create an emotional response. Trust gets your stakeholders listening, and feeling is what makes your audience care.

Every project begins with an emotional goal. Not a specific emotion, but a reaction that lands. It might be curiosity, contentment, discomfort, even lust or hate. The point is that your work triggers something real. That first spark rarely comes from logic. It starts with instinct. Your design, and all the tools encapsulated within it, are there to shape that reaction into something that is both felt and sharp.

You aren't balancing emotional pull and logical structure. It's a sequence. Emotion comes first. Logic follows. If you lead with numbers, no one will care. If you lead with feeling, logic helps you make that reaction clear, consistent, and defensible. That's why emotion isn't just a garnish to the communication we are providing. A single image can communicate "less chaos, more calm" faster than a page of bullet points. Logic doesn't replace that response. It sharpens it. Logic gives your instinct a structure, keeps your decisions focused, and allows you to explain your thinking when the questions start.

Emotion (Origin and Goal)

  • Ignites the work's purpose
  • Decides what matters most
  • Creates connection and memory
  • Sets the tone and energy
  • Delivers meaning

Logic (Structure and Test)

  • Sharpens and organizes the idea
  • Grounds choices in reality
  • Survives critique and scrutiny
  • Makes work consistent
  • Makes work repeatable
If your design ever feels flat, forgettable, or too clinical, chances are you let logic take the wheel too soon. The work that changes minds, gets remembered, or solves a problem always starts with a feeling and uses logic to make that reaction undeniable. Start with what moves you, then build the argument for why it works. This circular thinking builds us back to trust, because we allowed emotion to take center stage.

Collecting Proof

Proof is what turns a hunch into a decision that can withstand scrutiny. When it is time to justify your moves, do not dump every metric you can find. Bring only evidence that pushes the conversation forward. Keep it tight, on point, and tied to your claim. Too much data will only open the door to more questions. Offer just enough for people to trace your logic and trust it.

Use the sources that show real-world impact. Lay them out clearly. Let people see how your decision connects to the problem you're solving.

Sources of Evidence

User research Get out of your own perspective and watch how real people interact, react, or get stuck. Use this when you need to show that you understand your audience, or when your design addresses a specific pain point.

Competitive analysis Look at what others are doing, then either learn from it or differentiate. This is your proof that you've mapped the landscape and aren't working in isolation.

Performance metrics Lean on complex numbers: click rates, sales, retention, task completion, whatever fits. Metrics matter most when you need to prove impact or improvement, especially after it has been implemented.

Expert opinions Sometimes credibility can be borrowed. A single quote from someone who's lived the problem can carry more weight than a spreadsheet ever will. Lived experience validates in ways numbers can't. Use it when skeptics push back or when your authority won't close the gap.

Choose your evidence to fit the problem, not to impress. Your goal isn't to overwhelm; it's to clarify. Make your case, sharpen your point, and stop when the argument stands.

Handling Criticism Without Falling Apart

Criticism is the price of doing work that gets noticed. If no one's pushing back, the work probably didn't matter. What separates lasting designers from burned-out ones isn't how often they're critiqued. It's how they handle it.

Don't pretend it doesn't sting. Critique hurts because you care. That's normal. What matters is what happens next. Listen carefully, even when the tone is sharp or the feedback feels wrong. You're not there to win the argument. You're there to find the signal inside the noise.

Often, the hardest part is keeping your ego from getting in the way. It's easy to hear feedback as an attack on your talent or your instincts, especially when you care about the work. But feedback is rarely personal, even when it feels that way. More often, it's about the work in front of you, not the person behind it.

Never ignore your internal resistance. If you're struggling to defend a choice, there's probably a good reason. Use feedback, yours and others', as a tool to get the work sharper, not just safer.

Keeping track of how you respond to each round of feedback helps you in the long term. Those notes reveal which instincts pay off and which critiques are just noise. Patterns surface. They show up first in other people's reactions, then in your own. Resilience is quiet, steady, and earned. It marks a creative who treats criticism as fuel, not as a threat.

Practical Illustrations: Argument in Action

Navigating Olympic Tokyo

Tokyo's 2020 brief was blunt: guide millions of visitors who can't read kanji through the world's busiest rail network. Gensler talked with seventy riders, studied past Olympic signage, and built a bilingual icon set that scales from pocket maps to station-tower pylons. Their rallying cry—"one glance, one direction." Live trials proved it: more than 80 percent of travelers reached their stops quicker and felt calmer in Shinjuku's maze. The city kept the system and plans to roll it into every future transit upgrade. Source

Takeaway: State your claim, then make every design choice defend it.

Reassurance in Two Taps: Gojek Safety Center

Indonesia's Gojek discovered that riders decide in the first seconds whether a trip feels safe. Designers mined complaint logs, interviewed frequent users, and reframed the brief around a single emotional goal: reduce fear before wheels move. The new Safety Center allows riders to share live trip details with a trusted contact directly from the booking screen, turning a hidden anxiety into a visible control. Post-launch surveys in Jakarta pushed safety satisfaction from 3.9 to 4.6 out of 5, while driver-match abandonment dropped by twelve percent. The public case study documents the research, wireframes, and metrics, illustrating how Jakarta converted its audience's emotional claim into measurable evidence. Source

Takeaway: Build from emotional needs, then prove impact with real data.

Inclusive Search at Pinterest

When Pinterest's Inclusive Product team noticed that beauty and fashion searches defaulted to a narrow ideal, they framed a bold claim: "If Pinners cannot see themselves, our design is broken." The team audited query logs and conducted diary studies with underrepresented users. It developed a computer vision model that enables users to filter results by skin tone range and, subsequently, by body type. In U.S. A/B tests, the new model increased representation of all body types in fashion searches by 454 percent and drove statistically significant lifts in click-throughs and saves. Pinterest's engineering blog lays out the research and algorithms; a WIRED feature tracks the real-world impact on user trust and engagement. Source

Takeaway: Start with a human claim, test it rigorously, and let real-world data prove the result.

Self-Audit: Finding Your Defense

You've spent this chapter turning choices into arguments, feelings into structure, and evidence into trust. Now it's time to flip the process. Instead of defending existing work, invent something from scratch. Pick a human truth that matters to you, then prove you can design for it.

Finding a Human Truth

  • Name the human truth. One sentence. Something so universally felt or understood that it explains how people think, feel, or behave. Broad enough to resonate, focused enough to guide action.
  • Frame the emotional claim. What should someone feel when they experience your design? Make it visceral. Focus on the reaction.
  • Sketch the design move. Choose one explicit action that creates that feeling.
  • Map the proof plan. What evidence will you use to back this decision? List the research, testing, or data you would gather to support your choice.
  • Stress-test the argument. Ask the most challenging question you can imagine. If you can't answer it, the work isn't ready.
  • Set the success signal. Decide what outcome will tell you the design worked. Define your target before you build.

This exercise helps you move from intuition to a defensible, testable design argument.

Closing Note

Design is an argument disguised as an experience. Emotion sparks the claim, logic builds the evidence, and credibility holds it together. When every choice can be explained in plain language and traced back to a human truth, feedback stops feeling like a fight. It becomes fuel. Proof keeps you honest. Clear reasoning keeps you steady. And resilience lets you push forward when the pressure mounts.

Next, we move from individual decisions to the competitive space. Positioning That Means Something is about claiming mental real estate. Before you choose a color or typeface, you'll learn how to claim mental real estate. We'll map competitors, find the white space, and build a value proposition that design amplifies, not invents.