“Let your intentions create your methods, and not the other way around.” ~ Peter McWilliams
Now that you’ve been introduced to the idea of updating your website by Designing for Intention, you may be wondering what exactly is meant by the term “Customer Intention.” Further, you may be curious as to how you can get started bringing this type of thinking, and this methodology, into your business. One way to get the ball rolling is to start defining customer intentions for your website.
Before we talk about defining customer intentions, allow me to explain what I mean by the term “Customer Intention”. A Customer Intention is simply: a task a customer aims to complete when coming to a website. It may seem self-explanatory. In fact, it is. However, as you’ll see later on, the term can very often be misunderstood.
When going on to define customer intentions for your website, there is no way around it, you have to start by talking to your most loyal customers. This is truly the key to determining not only customer intentions, but many other facets of customer loyalty.
In regards to intentions, the key information from these conversations you’ll unearth include an understanding of how and when customers interact with your business (i.e. their touch points), and, more importantly, why they interact with each of these touch points. (For example, maybe you find out customers go online to gather research about your products, but they buy brick and mortar because of the customer service.)
After the conversations have concluded, you’ll need to gather and list out all of the website specific Whens, Hows and Whys. Once you’ve listed them, you’ll summarize the list into clear, mutually exclusive, bullet points which each finish the sentence “When a customer goes to the website they intend to…”.
It’s a simple list really. Here is an example we recently created for an e-commerce team redesigning their Dotcom site.
Customer Intentions for the Website
When a customer goes to website they intend to…
Buy an item
Stay up to date
Understand what makes
Understand what does
Find a retailer
Investigate / research a better solution
Return a product
Get questions answered
The list seems pretty straightforward, right? Of course this is what customers go to an e-commerce site for. But, be warned! Getting to the list above isn’t as easy as it may seem. Below is an example of what the list probably looked like before the team checked it against findings from conversations they had with loyal customers:
Customer Intentions for the Website — What Could Have Been
When a customer goes to website they intend to…
Buy an item
Sign up for the Newsletter
Visit the Blog
Update Account Information
Find a retailer
Investigate / research a better solution
Return a product
Get questions answered
Notice something different? Check out the bold items in the second list. Notice how subjective and feature specific they are.
It is highly likely you are going to try to put items like “Sign Up for the Newsletter” on your list. This is normal as often times business owners try to squeeze in feature specific items which represent the parts of the website they wish people were coming online to access, instead of being honest about why customers are really going to their site.
This is why it’s important to talk to your most loyal customers. There’s no disputing actually hearing these intentions first hand. Without this insight, your list will undoubtedly lean towards satisfying business goals, which means your website will be designed for business intention rather than customer intention. This means the odds of your website fostering customer loyalty go way, way down.
Knowing this, your final step is to review and edit your list with an eye toward, and an urge for, actual customer insights and extreme honesty. Your goal should be to keep your list of intentions as objective and non-feature specific as possible. How do you know you’ve done it right?
Ultimately, if your list of customer intentions reflects what you heard in your research, and, makes you a little (or a lot) uncomfortable, you know you’ve defined it well.
Once you have created an honest list of Customer Intentions, you’ve started the process of making your website a place that can assist in cultivating customer loyalty, instead of a place where you inundate customers with information you hope they pay attention to.
What’s next after you have the list defined? You can begin to design a user experience that meets, and hopefully exceeds, Customer Intentions, of course. And, you can be sure there is more information on doing so to come.
In today’s business world having a website is practically equivalent to being in business. There is no question in regards to IF your business should have a website. There is, however, still very much a question in regards to how best to structure and position that website and the information it contains for maximum business and customer benefit.
As an Information Architect, it is my job to help businesses understand purpose. More importantly, it is my job to help others understand how to structure specific information on their websites (and apps, and anything else that has information that needs to be communicated) to meet that purpose.
Recently, we have developed some interesting viewpoints in this endeavor. Before I share those with you, it is important to understand what I mean by the term “structuring a website.” It is also important to understand a bit more about how and why websites are structured today.
Back when the web was first born, there was no rhyme or reason to what information was strewed across it. As more and more information was put on the web (NOTE: By the word “information” I mean content, videos, images… anything.), it became harder for people to find their way around. People not finding their way around meant that they weren’t able to connect with businesses in the ways they needed to become customers, let alone loyal customers. This not only frustrated users, but it was also not so good for business.
This issue birthed the field of Information Architecture. Started in large part by those who studied and worked in Library Sciences, Information Architecture was created in order to help organize all the information that was floating about on the Internet. Since then, Information Architects have been helping businesses figure out which information needs to go where on their websites. They have also been helping to organize and structure said information into nice, neat taxonomies. These taxonomies work to catalog each piece of a company’s information so it can easily be found on the web.
You may have worked with one of these people before, and evidence of their hard work is everywhere. One of the most popular examples, as of late, is the mega menu. Here are some screenshots of the mega menu in use:
These menus are organized to give each piece of a company’s information a “home” in the hopes that customers will seek out and find what they need.
There’s just one problem with these sites, and most other sites regardless if they have a mega menu.
These structures don’t allow the sites to be optimized for their necessary purpose. Instead of helping customers to meet their goals, the structure of the website is actually creating more noise for customers to sift through, which is bad for the bottom line because customers aren’t able to find the information they need in order to complete the transaction.
This brings us back to the customer’s intention.
Focusing on customer intention starts with considering what customers intend to accomplish interacting with a website. Instead of doing things the old way, i.e. designing a site by starting with all the information a company wants to put on their website and organizing a structure around it, we first think about the customer’s intent.
With these intentions in mind, we can then sort through all of the information the company has that can fulfill those intentions. This is ultimately the totality of the information that will live on the website. Being sure to leave out any extraneous company information that simply adds noise to the equation. Because, after-all, the last thing a customer needs in today’s world is MORE information thrown at them.
Structuring for intention is one of the very first steps needed in order to aim your website toward cultivating customer loyalty. The above looks to provide the basic outline of a much grander idea. There is a lot more to the process to share, and you can be sure that I will be doing so soon.
But for now, it’s important for us all to realize that the old way of thinking about what information goes on our websites and how that information is organized no longer works. Yes indeed, it’s time for a change.
There’s something troubling that I’ve noticed happening with many people (not all, maybe not even you) in our industry over the past few years. It’s something that I want to bring to light in hopes that A. I can be enlightened to the necessity or trivialness of this thing, or B. I can help others to enlighten themselves and stop the thing’s progress. So what is the thing? Simply… that we are stuck in our ways, and if we don’t start moving, our industry will never change. I’ve said it before, and I’ll say it again, Newton didn’t lie…
Our World, Today
The current state of where we are is not really a revelation to many of us. We are working doing design or architecture or web “stuff”. Some of us call what we do UX. Some of us claim UX doesn’t exist. Some of us wireframe. Some of us claim we don’t. None of this will be addressed in this piece, for this is what it is, and the arguments will rage on. Instead, I want to point out the bigger issue that I have seen. That is that many of us, no matter what side of the fence we are on in these arguments, HATE where our industry is. We hate our clients (“Two weeks for a complete overhaul of documentation that took us months to put together. #ClientsGottaLoveEm”). We hate our co-workers (“When can you get the UX wireframes done for this project? #UXIsntWireframes”). We hate our careers (“Hired as a UX Strategist, but they just asked me to make a screen ‘better’. #WhatsThePoint”). In short, we hate our state of being, and this causes us so many problems.
What’s the big deal?
First off, in many ways, we aren’t progressing as an industry. What does that mean? It means we spend so much time focusing on the negatives of doing what we do, that we don’t save brain space to focus on how to change the negatives into positives, and, therefore, change ain’t coming.
Secondly, all this negative energy actually zaps our ability to see that WE ARE THE TALENT THAT EVERY BUSINESS NEEDS TO SUCCEED. Obviously, we can’t do it alone, but come on guys, this is our TIME! Everyone wants to be the next Apple. Everyone talks about how facilitating great user experiences will make the business more successful. WE really are in control. But we have beaten the idea of our profession down so much that we believe that we can’t change our environments. We talk to our clients in words that mean nothing to them, and wonder why they don’t “get it”. We take jobs because they show us a glimpse of hope at being the real deal, instead of asking the hard questions that prove we’ll be doing the work we want, and turning down the gig if it’s not the work we want. We blame our lives, our clients, our coworkers, our cities, our companies for holding us back. And, we do this, simply because, we don’t have the energy and courage needed to do something about it.
Third, and perhaps worst of all, we isolate ourselves from other disciplines and industries. This is the gravest problem of all because it means we don’t educate ourselves about what information or context these other disciplines and industries need to really understand where we can be of use. We don’t learn about business (yuck, suits), and then wonder why we get screwed in negotiations. We don’t learn about company process, then wonder why our ideas are labeled as being outside of the process. I can go on.
Four, this all means we perpetuate our cycle (wait did I go back to number one again? That’s meta.) The crappy jobs keep getting resourced with talent (us) that is too good for the jobs. The crappy companies keep getting resources (us) that are too talented and smart to work with people that don’t want to hear how we can help. Then we blame the company, the clients, the co workers for the crappy jobs existing… and the cycle persists. We continue to hate the work that we are supposed to love, and live in misery complaining to each other how bad we have it.
But fear not dear reader, there is hope! And to inspire this hope we turn to none other than Sir Isaac Newton (you may have heard of him). As many of us may remember, Newton was a famous physicist who is known for proving three laws of motion. For our troubles to be cleared, I’d like for us to remember Newton’s first law of motion:
An object at rest will remain at rest unless acted on by an unbalanced force. An object in motion continues in motion with the same speed and in the same direction unless acted upon by an unbalanced force.
Put more simply. Things won’t change unless you act, unless you exert some kind of force. Try this… an object at rest (let’s say the environment we work in, our industry, your clients or your co-workers) will remain as it is unless acted on by an outside/unbalanced force. Here’s the secret… you have to be the force in order for your luck to change.
Now, you may be thinking, “But, wait, what if I don’t WANT to change.” Or “But I have to take these crappy jobs I have a family to support.” Or “I’m not you, Lis, I don’t have the people skills to do it.” Or whatever other argument you can think of. But, I’m here to tell you that all of these are invalid, yes even the family one. Why? Because the definition of the force is flexible. Doing any one of these things can change the environment:
Ask more questions during interviews to discern if the job meets your goals. Things like “How often do you do usability testing and why?”, “What does user centered design mean here and how is it implemented?”, “Does, and how does, my role help bring a user centered focus to the company?” will help you know if they are for real.
Network more with people like you to let people know that you are an awesome person. Go to industry and non-industry events that spark your interest. Talk to people about what it is you want to be doing with your knowledge and skills even if you aren’t doing them “for real” at your current job.
Choose to interview or work for companies whose mission you believe in, and whom believe in a user centered mission. If those companies aren’t in your area, at least start to follow companies whose mission you believe in and try to meet others who work at them when at the next conference or event. Ask these other employees, designer or not, how they got the gig, or get advice on how to manifest your career in the same way.
Choose co-workers who are awesome like you. Obviously we can’t choose who we work with, but we can choose who we cooperate with and provide favors or extra help to, etc. Prop up those co-workers that you see as awesome.
Choose to believe you have a choice in your career, because we are all free beings, and we always have a choice.
Insert any other type of force here.
Further, if you are thinking about how you have already exerted force and created change, but it hasn’t worked… then I would argue that you need to exert a different type of force in order to manifest change in a different way. I’m by no means assuming that none of us are acting, but instead hoping to give you ideas on how to exert force, or act, if you currently are not exerting force, and if you are exerting force and it’s not working, giving you ideas on how to exert force differently.
The main point I want to make is, it’s not all about completely throwing away every part of your career and starting fresh. Instead, it’s simply about using whatever amount of force you can use to affect change in your environment. Even a little force will create some change (it’s a law of physics, remember?!). Of course, Newton’s second law says that the greater the force the greater the change, and that is to be expected. But, the happy news is, the laws of the universe tell us that as long as we are exerting a force, no matter how small, there will be a change in return. Anyone can assess the level of force they are able to exert and then start manifesting change, no matter what your situation is. Newton said so!
It Keeps Getting Better
And, guess what? The more we see the change, the more energy and ideas we’ll have to exert more and better force. It’s a cycle that gets better and better. Then the more force we exert, the more change will come. We’ll venture out and learn more about other disciplines and industries and become better integrated into cultures we like. We’ll stop with the cycle of taking crappy work, complaining about that work, leaving that work only to find more crappy work. We’ll instead force better jobs, ones where we can actually use our talents, to be created. We’ll force jobs that have a better understanding of the help we can provide, thereby using our talents to the fullest. Best of all, with all of us exerting force, our industry gets better. We don’t do it alone! By all of us exerting even a little, itty-bitty bit of force, we are all, in culmination, exerting a lot of force. And, that means, we’ll all see a lot of change and reap a lot of benefits. It means we can finally help in the ways we’ve always known we can.
In the end, it really is about taking responsibility of our fate, and then taking action to change that fate if we are unhappy with where the object is at rest. It really is just about not being the object at rest, if we don’t want to be, but instead being the force that moves that object in the right direction. And once the object is moving, it can’t be stopped… unless, of course, another force is exerted on it :-).
As I pour through my spreadsheet of blog ideas, I keep happening upon (probably not by accident) ideas that I have had over the years around the term UX Designer and, more specifically, whether or not the term makes sense (I.e. means something). Now, I realize that the title UX Designer DOES in fact “mean something” to many people. I think what has sparked this flow of ideas for me, however, is that the title means so many different things to so many different people. This space between the meanings is where I’m finding both internal and external conflict around the title’s purpose. Today, I want to dive into this even further, and, hopefully, get your thoughts and feedback as well (Yes, I’m adding another log to this fire. So, all you old school UXers can stop rolling your eyes now.).
This topic is nothing new. Most of the known digital technology industry walks around having a firm belief in the validity of the term UX Designer. Many people think things like “User Experience is, of course, the most important part of the product AND you need to have a UX Designer to have a ‘good UX’”. Or, other people think things like “UX Designers. Those are the people that make sure the product’s UX (but really they mean interface) is great!”. Or, they may think “UX Designers. Those are the people that are glorified visual designers.”. Whatever anyone thinks, it’s obvious that the title UX Designer is something that exists in a myriad of ways. In the digital design community, many times it’s a lauded profession; one that you acquire after knowing everything there is to know about “the UX” including interaction design, information architecture, visual design, and more. For this last point I can admit that I have also thought that UX Designer was a lauded profession. I bought into this concept… hell, I built a business around this concept! But today, I wonder, is the title UX Designer really all I, and many others (those that think it’s the *ish title), have made it out to be?
Why Lis, Why?
Why am I even pondering beating this dead horse? Well, as I was pouring through said blog idea spreadsheet, I found an idea I had back in early 2013. Seems I was scouring the web (read wasting time) and I found this quote, and I realized I needed to get this thought out of my head.
Although this quote was not targeted at the field of UX Design, it still stopped me in my tracks and caused me to reflect on the profession. Why? Because it brought to the surface, again (at least for me), the question of whether or not an experience can be designed. Of course, this quote that I found is not based on scientific or academic research (although if you have some to share I’d love to see it!), but the meaning of it felt true to me. So I’m going to move forward in this post assuming it is true (this, dear reader, is what is called fair warning).
The debate on whether or not an experience can be designed has been raging on since, what feels like, the beginning of the field. The following are just a few of the many pieces out there on the topic:
The way that I see it, is that each side is looking at the User’s Experience as one of two things. Those that agree with the idea that an experience can be designed often conceive the user experience as an input into a product or service. It is something that happens before the product or service is created and a user uses it, i.e. something they “do” to make a product or service better – “I do UX!”. On the other hand, those that say that experience can’t be designed, but can be designed for, see that the user experience as an output of the product and service, i.e. something that happens because of using a product or service – “How can you do something that happens later?”.
I’ve somehow found myself a part of this debate, and, have recently realized that I firmly agree with the latter, UX is an output NOT an input. Meaning I believe that the user’s experience exists when a user uses a product or service; i.e when they undergo it. I don’t think it can be argued that, to an extent, we can predict when a user will have a better experience if everything and everyone shown here has been accounted for in the creation of that product or service the user is using. However, I no longer believe that User Experience is something we inject into the creation of said product or service.
Given this new realization, I asked myself: If UX is an output and not an input… can the title UX Designer make sense? Can there be someone whose job it is to design the user’s experience IF the user’s experience it not something that goes into the product or service, but something that comes out of it.
I would argue that No, this title does not make sense (I.e. mean something) given this point. And, to be honest with you, I don’t have much more to say on what my new viewpoint means (so I suppose my good friend Donna Lichaw might say that this piece is a cliffhanger).
And Now It’s Your Turn
Either way, I’d love to hear your thoughts and opinions in the battle that never ends. Do you think the UX is an input or an output? Given your opinion does the title UX Designer still make sense to you and why?
Whew ok folks there you have it. Another piece of wood added to this fire. Let the flames rage on!
I keep a list of ideas, buried deep in Google Drive, of blog posts that I mean to write. This is a great way to ensure that I never lose a spark of inspiration. However, this list only works if one takes the time to go back and look at it (which I rarely ever do). But, today I did take the time to go back to that list and I found an idea from almost two years ago that happened to catch my eye. And, even though I have written about this topic before, it has been etched into my brain so deeply, that I decided to write about it again today. What is that idea? That Information Architecture is, and always has been, about creating for the user’s experience.
This idea may not be new to many of you (I hope). UX has been the new IA for some time now, and all of us who started out by calling what we did Information Architecture knew that it involved the user’s experience. Problem was, at least for me, we just didn’t know how to describe it very well, or did we?
Is it IA, or is it UX?
Like what happens to most everyone, when I meet new people they often ask me what I do. For a long time I told them I practiced Information Architecture. Then, as the UX tide came in, I started to surf as a User Experience practitioner. But, more and more I have found myself back riding the Information Architecture wave. I tell you this not to show you what a flake I am, but to show that it’s obvious, and has been obvious, that something was missing in IA before, that enabled one to confidently say “I do Information Architecture which means I model user experiences.”.
And so, two years ago, I think I found that missing statement. I logged it in the back of my mind, as well as in my ideas for blog posts to write, and it has been festering ever since. And, although what I’m sharing with you today about Information Architecture is not all together new, I did want to share the link with you, to hopefully implant the idea of what Information Architecture is in your brains so that it festers and grows.
Of course, all of the material is interesting, but the line that stuck out to me, and that began my road back to IA was this:
“Information architecture relates to science as its models draw on insights and theories of cognition. And its models relate to art as they aim to create a meaningful experience.”
Whoa. There it was, again, in black and white. Information Architecture models aim to create a meaningful experience. Duh! How could I have forgotten this in my aim to describe what I did while saying I practiced Information Architecture? You see, those practicing Information Architecture create models which aim to create a meaningful experience for the users of those models. Brilliant!
Thus, all those years ago, when User Experience came on the scene and sounded so much easier to describe than Information Architecture, I abandoned my IA post for the promised land of UX. However, I realize that the words I was looking for to describe my value were right in front of me all along.
I share these thoughts with you today, dear reader, in the hopes that you begin to understand this:
The User Experience is not an input or a discipline, but is, instead, the result of modeling information in such a way that creates meaning in an experience.
AND, That modeling of information… that’s the job of someone who is practicing Information Architecture.
Some time ago, I was sitting in a client meeting, reviewing the QA version of their website’s check out flow. The development team had just finished putting together all of the changes that I had designed for checkout, and I was looking through to make sure everything matched up. Luckily, many of the items that I had designed were accounted for, and the QA site was looking great. On the flip side, I found a few, smaller items, that had been missed. When I asked the technology lead about them, he replied that we didn’t have time to go back and fix them, and since they weren’t core functionality, we could put them on the backlog for later. This got me thinking ‘How many times have I heard this before?’, and then I thought ‘I know these items would enhance this flow a thousand times over, but I know that they’ll never really get done. We never actually go into the backlog’. Then I got to thinking… why?
Why is it that we forget about the little things? More importantly, why are the details of our designs and ideas being overlooked and missed? I have been in this profession for over 10 years now. This is a trend I saw when I first started, and I still see it today. Those building out our designs, often don’t see every detail, and when we point the smaller details out, they are often not important enough to fix. I don’t know how our current state still includes a lack of getting into this detail.
And not developing and designing to the details causes us some problems. First off, the details are usually where the “delight” of a product is. Follow a site like Little Big Details and you can see all of the many small details that make products so much better to use than their competitors.
The second problem we see when we over look details is that these small details do not usually take a lot of design or development time to make happen. In fact, if we took the small amount of extra time to design and develop the details, we’d see a tremendous payout with the user’s experience with our product. Thus we are forgoing this return of user delight, in order to make a schedule, or stick to a development process.
The third problem is our product experiences are not progressing at a rate that they should. I believe that missing these details is what is stifling experiences across the web. It’s not just the big product ideas that set a website apart. Most times it’s simply the UI and flow around that website that makes the difference. But without the details, and holding others accountable for designing and coding them, we are missing out on our own progression.
The thing here is that I don’t know why this is still happening. Why do we allow designers and/or developers to miss the details? Obviously there is more than just the UX team in play, and it’s a technology community problem, but I’m just not able to see why I’m having the same conversations from 10 years ago still today.
Therefore, I write this piece as a question to all of you. How are we still here, and how do we solve the problem of detailing out delight, and still not seeing our details being designed to and developed for? What am I missing that you are seeing out there in the world that can help me, and all of us get there?
Ultimately my goal is to stop getting these small “enhancements” put on the backlog or “shelf” and to start having my teams get it right the first time. I believe by doing so the products we all work on will be much better off, and our work can progress exponentially because we won’t keep coming back to the same old conversations.
Thus, what are your thoughts on how we can move forward from where we are to getting our details designed and developed correctly the first (or even second) time around?
I just returned from the Interaction 14 conference in Amsterdam, and I’ve been reflecting on the information I learned there. I was honored to be facilitating a full day workshop, Interaction Design Beyond the Wireframe, at the conference. I love and hate facilitating this particular workshop. I love it because I believe in the content and approach, and it’s great to see this affect other designers lives. I hate it because sometimes it feels as if the concepts are old and no longer useful. But, after last Wednesday’s workshop event I realized that this information is still very much useful. Also, as I was watching the participants go through the activities I was reminded of a question that fellow UXer, and friend, Nathan Gao asked me some months ago. He said to me “Do you ever look back on the work you did, and just hate it?”. “What do you mean?”, I asked. “Well I mean now that you have learned a lot more, and you have done a lot more, do you ever look back and realize that the work you did was ugly, not technologically as advanced as it could be… stuff like that?” I paused and thought about this for a moment and responded “Honestly, no. And let me tell you why.”
In this world of UX and Interaction Design, we so often view our work as a work of art. We think of it as a blend of science and art, reflecting both best practices as well as internal purpose, aesthetic, and opinion. It was even mentioned during IxD 14 that we are both science based and art based. I always thought it was interesting to view our work this way… interesting and problematic.
The issue that arises when we think of ourselves as artists, is that we think of our work as art, and this causes pain points. First, we judge and critique our work as art. We judge the “look” of the deliverables, and the savviness of the interaction. We judge the emotional response invoked by the deliverable or the sketch or the prototype or whatever it is we, the interaction designer, provides.
But, at least from my point of view, my solution, which is reflected in, but not defined as, what I deliver, has nothing to do with art, unless I am actually designing the visual look and feel (which I personally don’t do). Strictly speaking of non visual design deliverables then, I see no art reflected in them. Everything that I have included in them is based on factual evidence of either user need, business need or technological constraints. If a user needs a way to view search results by date… I add a sorting control. If they need to find a way to company contact information… I add a contact us link. I also don’t view my wireframes as the final layout and product, I view them as information design. I.e. their purpose is to inform the interface by showcasing information relationships and priorities. Basically I don’t care about how it looks in the end, just that the right information and controls are present. Therefore, nothing I add in my work is based off my own opinion or internal narrative, so I don’t judge my work as art.
Going with this argument then, judging our work as art, means that we must be, in same ways, adding our own opinions and narrative to our work. And, if we are doing that, then we aren’t doing user experience design or interaction design, we are doing art. So the biggest problem with thinking of ourselves as artists is that we think of our work as art and add our own opinions and narrative to it as opposed to keeping it strictly about upholding user needs and business needs.
In order to avoid this problem, then, and to create work that is representative of our user needs, business needs and technology constraints, I believe we need to take the art point of view away for a minute. I KNOW this is going to cause a tear in the universe, but it’s something I’ve been thinking about and wanted to write about for some time.
So, I implore you dear readers to help me to see if I am on the right path with this thinking, completely mad with this thinking, correct with this thinking, or somewhere in between. Is there a cross over between Art and our UX and IxD deliverables (sans visual design), and if so, where is it?
Now that the new year is upon us, I decided I to take the time to think about what it is I want to accomplish in 2014. Yeah, I realize I’m a few days over due for the New Year, but better late than never. With that said, here are a few mantras that I’m going to attempt to stick to in 2014 in order to guide my intended accomplishments.
Do What You Love
I have written about this before, the idea that there is a lack of passion in my work. That’s not to say I don’t love what I do, I do. I enjoy working in UX and consulting a great deal. However, I very often find myself doing things (attending certain events/conferences, writing a certain piece, attending a meeting, working with a certain client, etc) because I feel that I “should” do them. This year, I’m going to have a sharp focus on doing things because I love to do them. Of course, love of stuff doesn’t always pay the bills, but ask yourself this: why can’t it? Or, at least, why can’t it help to? Thus, by following this mantra I hope to do some, or all, of the following in 2014:
• Speak at more non-UX focused conferences and events
• Write for non-UX focused sites and publications
• Start or contribute to some sort of podcast or audio/video blog
• Write more for creative purposes, and more creative pieces
• Collaborate more with trusted and new friends/colleagues on projects, ideas, and more
Find What You Love
Doing what you love to do means that first you have to figure what it is you love to do. Thus, this mantra is about me being aware and in the moment enough to realize when I’m falling in love with something I’m doing. It also means not being afraid to love to do something that others hate, and to not be afraid to get to know myself better. By following this mantra I hope to do more of the following this year:
• Attend and be present at different types of events, classes, etc.
• Meet even more liked minded individuals that I can learn and gain inspiration from
• Continue to fight through any hesitation
Be What You Love
Lastly, I think there is something to be said about embodiment. I’m talking about not just going through the motions of goals and goal setting, but to understand why you are are setting goals for yourself, and then to embody that reasoning both internally and externally. This mantra is about staying true to yourself and your beliefs, working with and for people that remind you of who and why you are, and all the while asking yourself “why am I doing this?” and believing and aligning with the answer.
There you have it folks, my goals for 2014. This list may seem Non-UXy, or too general, but I’m standing behind it 100%, because I believe that by better all aspects of yourself, you will easily better your work.
It may seem a bit early to write an end of year post, however I believe that consistent reflection is one of the best exercises that one can do. And, since I have been reflecting quite a bit lately, I thought I would apply these thoughts to my 2013 and share with you what I have been up to, where I’m going, and what I’ve learned.
One thing I have realized is that this fall and winter I have not had the time to keep up with writing for my Keeping It Real About UX blog. This might normally be a bad thing, however, the main reason I haven’t had time to write here is because I have been busy contributing to some amazing publications such as UX Matters and UX Mastery.
For UX Matters I partnered with Paul McAleer to write to the UX Community about our attempt at a new way to Map Business Value to UX, and to educate our organizational partners while doing so. So far, we’ve gotten some great feedback about the pieces, and we’re always open to hearing more! I’ve included these posts here, in case you missed them:
Many thanks to both UX Matters and UX Mastery for allowing me to be a part of such an esteemed community of writers.
The second thing I realized is that, earlier in the year, myself and my interns (who are now real working world UXers!) did get the chance to contribute some pieces to the Keeping It Real About UX blog. Here you can find the top 5 viewed posts from 2013
Third, as I look into the new year, I also realized I have some amazing speaking opportunities to be excited about for 2014. Top of mind is my full day workshop Interaction Design Beyond the Wireframe that I’ll be facilitating at this year’s Interaction 14 event in Amsterdam! If you plan on attending and are looking to learn all about IxD outside of the interface, I’d love to see you there.
Lastly, one thing I realized in my end of year reflections is quite how busy I, and all of us, have been. Thus, I plan on taking the next few weeks to ease my mind, find, again, some inspiration, and reflect on my goals for 2014. I encourage each and every one of you to do the same. I encourage you to take some time for yourself to reflect on where you have been, where you are going and what you have learned along the way. Only then can you make the next year, even better than this one!
For months I have been trying to write a post about Detroit. Why Detroit? One, because it has been in the news so much. Two because, as an IA, I think the downfall of Detroit is quite obvious. The city is a manufactured city, instead of a natural place of settlement. It was put together to help fuel the auto plants, and now is faltering in a huge way. But, this isn’t surprising to me. It reminds me of all of the new ideas that startups and even large businesses have that just seem so meaningless. Why are they meaningless? Because they have zero to do with natural human behavior.
Scott Berkun wrote this piece about Google Glass, and I couldn’t agree more. I think we get distracted a great deal, by the coolest and newest technology. Sometimes this is important, but many times it takes us away from our roots. These are, understanding and designing for, and to enhance human behavior. We want to make our users lives better, but in a sustainable way, not in a way that will fall apart.
So the next time you see something new and shiny, I’d like you to ask yourself is this meaningful? And if so how will it help people in real life (not just how it could help people, one day, maybe, with a whole bunch of changes). We IAs are no different than city architects. We have a responsibility to our users and our businesses to not throw together ideas without an idea of how they can sustain, but to vet them, to make them better and to make them help people live better lives.