Emotions are arguably the most powerful of human motivators and yet most design projects lack an explicit strategy to use or target them as part of the overall experience design. A truly fulfilling experience is one that balances our logical and emotional needs and wants.
When an experience only satisfies the logical side of our mind we’re often left with little feeling of connection to the experience. When an experience only speaks to our emotional side we’re often left second guessing our choice because we can’t rationally explain our choice to ourselves or others.
A balanced experience that satisfies both parts of our mind are the ones that create deep and lasting connections. These are the experiences that build loyalty with customers creating lasting relationships that survive even the worst of times.
In order to use emotions as both a targeted outcome for the experience and as a strategy to achieve that outcome we must first understand how have an experience. The 4 Stages of Accomplishing Goals provides this insight into HOW we experience everything. These 4 stages are the same for every person, they happen every time, and happen in the same order.
The 4 Stages of Accomplishing Goals also explains where, when and how emotions impact and influence our resulting experience. We’ll learn not only how we experience everything but also WHY we choose to accomplish some goals and not others. Once we’re clear on the 4 stages we can make emotions a strategic part of building a balanced user experience.
In this presentation I talk about the importance of balancing the useful, usable and desirable qualities of a web site to create a great user experience. Through a content out, mobile first, progressive enhancement approach you can reach the greatest number of potential viewers while ensuring the most appropriate experience for each in the process.
The purpose of the holistic approach is to never lose site of the user and what they are really visiting your site for and that is your content. This approach is built on the ideal of radical inclusion. That is to say that nothing we do as designers or developers should ever prevent the user from accessing our content.
As always I’d like to hear your thoughts on that subject. Enjoy.
What Internet retailers should know about responsive web design: InternetReatiler.com
I was asked to write this article in response to a particularly inaccurate article that InternetRetailer.com had run that contain several misleading and just plain incorrect comments about responsive web design. In all fairness, the author of the original article was not a front-end developer and simply quoted others that had poorly represented what responsive is and what it’s responsible for.
Seems there are some folks out there that find designers difficult to work with. An old Quora discussion resurfaced recently that asked the question, “Why are designers harder to work with than engineers?” Speaking as a long-time designer, I don’t know what they’re talking about. I do just fine working with designers. What gives?
I hope this post will offer all non-designers (someone that has not been educated in design) the insight needed to make interacting with designers much less difficult. To be fair I’ll offer some advice to designers on how we can help the situation from our side. To begin I’ll need to dispel certain misconceptions non-designers have about what design is, what designers do and how we do it.
Continue reading The Non-Designer’s Guide to Working with Designers
In typical Karen McGrane fashion she makes a clear case for dealing with content first. Not just for responsive sites, but for any site.
Seems like a lot of people are laboring under the mistaken impression that using responsive design means they can make a mobile website without dealing with their content problem. Where’d they get that dumb idea?
Before you begin your next responsive redesign, or any redesign for that matter, read Responsive Design Won’t Fix Your Content Problem by Karen McGrane.
Given the pace at which things change in the realm of web, when is something a true best practice, merely a current or common convention, or are we all suffering from a “consensual hallucination” as Jeremy Keith says? What was a best practice yesterday may not be tomorrow, or even today for that matter.
Are things moving so fast that best practices don’t really exist any longer or does our use of the term need to change to reflect today’s reality? My goal here is to open up some discussion and thought on how and when we use these terms and how to avoid falling victim to hallucinations.
Continue reading Best Practice, Current Convention or Consensual Hallucination?
A great post on how to “think” about web development. Everyone should read this if they plan for their site to be seen beyond the desktop display. Maybe even more so if don’t think about your site being seen beyond the desktop display.
There is more than a little written about mobile first design. The problem is that most of what’s written is focused on designing for devices and not the people that use them. Here are 7 common mistakes, or misconceptions, I hear people making when approaching web design from a mobile first perspective.
No. 7: Thinking Mobile First is a Design Pattern
Mobile first is way of thinking about design, development, content, usability and experience. Like I said, much has been written and it’s mostly about mobile first “design.” This often leads to the errant assumption that it’s only about the design. It’s not. It’s really a strategic and philosophical way of addressing the challenges we face in this always connected world we live in today.
The term “mobile first” isn’t helping out either. It seems as though the word mobile more often than not makes people think about mobile devices rather the mobile context. To think mobile first means to consider everything that could be at play for the user. Their device is just one small piece of the puzzle.
Continue reading 7 Mobile First Mistakes to Avoid
A couple years ago I had the good fortune to hear Jeremy Keith give a talk at An Event Apart. During his talk he spoke about three important factors that make up our work – Goals, Principles and Patterns. Unfortunately it seems that all too often many of us only tend to the Goals and Patterns of our work. The WHAT we do and the HOW we do it.
What about Principles? The WHY to our HOW and WHAT. Why do principles seem to get overlooked, neglected or all together forgotten in the day to day of our work? Are they really just not important? Or, is it because they, can at times, make our work more difficult?
Continue reading Goals, Principles and Patterns, Oh My