Design Is Not Decoration

There is a version of "design thinking" that has been so thoroughly co-opted by corporate process that it no longer means anything. Sticky notes. Double diamonds. Journey maps for a product nobody uses. This is design as performance.

Real design is a different thing entirely.

The Functional Argument

Design is how something works. This is the Jobsian reading, and it's mostly right. A form that loses user data on back-navigation is badly designed regardless of how it looks. A button that's hard to hit on mobile is badly designed. A loading state that gives no feedback is badly designed.

None of this is decoration.

The Aesthetic Argument

But reducing design to pure function misses something. Aesthetics carry information. A product that looks considered tells you it was built by people who cared. A product that looks careless tells you something about how its builders thought about you.

The aesthetic is not separate from the function. It is part of the communication.

What This Means at a Club Level

WeDesign exists at a school that produces engineers. The temptation is to treat design as the thing that happens after the engineering — the skin stretched over working code. We reject this framing.

Design happens at the schema level. It happens when you name a database column. It happens when you decide what error message to show. It happens when you choose what to log and what to silently fail.

Every decision that affects how a person experiences a system is a design decision. Owning that — taking it seriously — is what this club is for.

The decoration interpretation of design is a way of making it someone else's problem. It isn't. It's everyone's problem, always.