#mainContent { max-width:1100px !important; }
Daniel Joseph Casey


Why we don't strive for "perfect"

I was having a conversation with a client after a wireframe concept pitch not too long ago, and they were very happy with the direction that we were taking their mobile app in. I was excited too, it seemed like both teams were firing on all cylinders and that the design process was being respected and the appropriate time was being taken. They said it felt exactly like what they were envisioning, and that it was "just perfect." When I heard that word, I stopped every other process in my brain at that point. I needed to explore this statement more, so I asked why it was perfect. The response was powerful enough to make me write my first blog post.

"It's got everything we need, and it just looks amazing."

A few things.

1) Needs change.

When my team and I are designing something - whether it's an application, website, identity, etc., we always start with research. We make it a priority to dig deep into the world of people that will be interacting with whatever it is we're designing, and find out how they tick. If we've done our research and design with these people in mind, we've put together a truly informed and user-centered design. But "perfect?" Design is something that is constantly evolving, so to label it as "absolute" or "complete" would be premature.

2) Looks can be deceiving.

People can often get caught up in the aesthetics of a design, but it goes much deeper than that. Let's not confuse a flat design interface as a perfect des

Daniel CaseyComment