White space is commonly referred to as the space between things, such as words of text, or images, or radio frequencies. For a long time I’ve been interested in what’s left out of conversations, design, or print. What are those unspoken messages that we process, information we read between the lines, or visual cues we intuit without actually seeing?

As a web developer, I’ve become very interested in how a user experiences a website, without knowing what’s behind the scenes. Code itself contains a series of spaces (or non-spaces) that define its characteristics, how it displays on a page, and the functionality it enables. When I’m coding a widget or description, I must pay attention to the visual spacing the code will create for the user, as well as the spacing of the code itself (so it remains valid and parses). Luckily, however, as a developer I can validate or parse my code before it goes live; if the spacing is incorrect, I receive an error message:

A website user, unfortunately, doesn’t have the option of validating the messages they’re receiving; they have to make sense of what limited information they’re given to make purchases, find information, or communicate with others. How does a website make a user feel? How does a user figure out how to use a site and its tools? Can we define it?

When I was in college, a few of my English courses focused on post-modernism and deconstruction. One of my professors loosely defined “deconstruction” as explaining or recognizing what’s not being said or talked about in the story. What’s the elephant in the room?

In this blog I’ll attempt to deconstruct — or decode — what’s happening for users in terms of usability and emotional experience. You know, the sound of silence.