Thursday, March 30, 2017

UI Trend with Modal Windows

You may say that Modal windows are what pop up were 10 years ago. Like them or hate them they have become an essential UI design element for almost any website or application. Recently I have started to see a transition of how these screens are being used. We first started seeing modals about 8 years ago when a developer named Lokesh Dhakar created a Javascript Library called “Light Box”. It was a very simple way of putting focus on one image at a time and graying out everything else.

This became so popular that many people starting to throw anything and everything in these smaller focused screens. Some people call them Dialog boxes, others call them Modals but they really all mean the same thing. The main purpose is to present the user with additional information while putting the main parent page on hold until they are done.

Of course with any UI design element they have been misused and abused in many different ways. I have seen some applications that have more than 3 levels of modals one on top of each other. Or times where the modal includes an extremely complex workflow or wizard that does not allow the user to exit until a set of criteria is fulfilled. Most of the times when modals are used in the wrong way it is because the content owners are trying to inject way to much information in such a small space. Rule of thumb, if you have to consider either a “Next” button or a “Scrollbar” in your design just STOP. It may be better to have a new full page dedicated to that content and not a modal.

With the introduction of bootstrap and other frameworks modals have become pretty standard on how users will interact with them. Usually the grayed out area is a clickable area that allows users to navigate back to the parent screen. Other times we become overly cautious and have “X” icons and “Cancel” buttons to make sure users feel comfortable that they are not stuck on an overlay page and no way to get back. One interesting trend I am seeing lately is moving the “X” button outside of the modal box and into the gray area. Pinterest uses both on their website which to me is a little bit confusing...

If you look at Facebook the close icon is all the way to the top right. This is slightly annoying for the users since they have to move their cursor a pretty far distance on larger screens to close it down. However since the whole gray area is clickable it is not a deal breaker. I would be interested to see some metrics on how often in Facebook users actually click the “X” icon vs clicking on the gray background?

Twitter has the close icon closer to the box which makes it slightly easier for the users to close it down.

Overall the biggest thing to remember is that modals are meant as short term screens to present and capture small bits of additional information that supports the parent screen. They should not be used for presenting heavy content, complex workflows and modals on top of modals. One last thing to consider is that you will need to consider alternative ways of presenting these screens on mobile devices. In most cases they will become full screen take overs due to the limited space available.

Tuesday, March 21, 2017

UCD Process

Over the last couple of years UCD (User Centered Design) has become a buzz word just like RWD (Responsive Web Design). 5 years ago when I wrote my SharePoint Branding book I use to call it the 4D’s of User experience. It included Discovery, Definition, Design, and Development. I had a nice little picture and everything to depict the different phases.

Now the picture is much nicer and clean however, I really don’t think it matters what you call each phase it matters more what you do within them. I have seen so many different variations sliced and diced in different ways. To me it is about adjusting your approach based on the needs of your users and your client. In a more traditional waterfall project you have a tendency to over burden yourself with documentation because there is no chance of going back. Also those types of project are usually the ones where you scope out in the begging a full solution without ever fully knowing what the real need actually is. I would much rather only scope the first couple of phases to really truly understand what you are dealing with before you can even imagine what the technical effort would be.

The biggest shift that I have seen though a more refined UCD approach is really focusing on the first phase which is understanding who the users are, and what are their needs. This is a shift in getting away from just focusing on Functional Requirements but diving deeper and truly understanding individual user needs. In the past I used to focus on how to customize and configure a tool like SharePoint to give the users a somewhat tailored experience. This did not always provide the users what they needed but it was better than nothing. I do have to say it is really refreshing being able to go into a project technology agnostic. To me it sometimes feels like you are trying to put a square peg in a round hole if a technology has already been defined by IT and there is no clear use case or need from the users on how they will use it. This is a clear case where user adoption will become an issue and it will be a big waste of time and money.

One other shift I have noticed over the last few years is that personas have really changed their meaning and purpose. We use to define different personas based on their organizational structure (HR, IT, Sales) or by their permission roles (Admin, Contributor, Reader). We also use to focus more on their demographical information such as (Age, Location, Device Types) which really did not provide much value.

I think due to the fact that I spend more time diving deep through user interviews to gather as much as I can about their day to day activities. Learning more about what their pain points are and identifying commonalities with all that we have met with. This helps drive better insights into who those core personas will be and not just based on a title or a role. These types of personas will help us during the definition phase when we start to translate their user needs on to paper.

Not every project needs to have a full set of polished personas, but at least some level of understanding who you are designing the application for. For the most part the 4D’s still hold up pretty well but like I said before it really does not matter what you call each phase so long as you are providing value in each one of them.

Thursday, February 9, 2017

New Scrollable Tabs Design Pattern

By nature most people are resistant to change. I have learned the hard way that just because something has been working great for the last 10 years does not mean it is always the best solution now. So much has change with technology not only within the last 3 years but over the last 6 months I have seen drastic evolutions of the art of possible. Users are demanding more and in faster timeframes. We as designers have to keep up with the latest trends, patterns, and interactions or you will be left in the dust.
I recently had a design challenge that required the ability to display a horizontal sub navigation for mobile. Since we already had a main navigation being taken up by the parent hamburger menu I was in a bit of a jam on what to do.
My first instinct was to group all of the navigation elements into some sort of drop down so that when users clicked on the drop down they see the navigation list options. This would have been fine but was more of an old school way of looking at things. Also the animation of the drop down was a bit jarring on a mobile device.
A designer suggested using a new design technique to have the same tabs but allow the users to swipe through them when presented on the mobile responsive view. At first I was hesitant since it would require the user to clearly understand the menu was cut off on one side and all they needed to do was swipe from right to left to see the other options.
After further research this was a design pattern that was introduced through Google’s Material Design Scrollable tabs. See video animation HERE
Overall I think the scrollable tabs is a great new design pattern but only used in moderation and in specific scenarios. I find myself a lot of the time thinking about the old school way of doing things that worked from project to project. However I think we as designers need to push ourselves to think more outside the box. The traditional top or left side navigation is just not going to cut it anymore. We are in a world of younger user types that expect cutting edge design experiences that were limited by technology just a few years ago.

Wednesday, February 8, 2017

UX Tools of the Trade

The tools we use to help define UI experiences is constantly changing. The fact is that Photoshop and Illustrator are no longer the preferred tools in an XD designers tool kit. We have transitioned to more flexible and robust applications that allow both low fidelity sketch like concepts to Pixel perfect high fidelity visual designs. Sketch does a really good job at providing both of these levels as well as the in between. In combination with Zeplin and Invision these three applications provide a pretty solid output for creating great experiences for both desktop and mobile applications. Zeplin has been a great tool to lessen the burden on our visual designers for creating redlines to our developers. It has some really neat features that would take weeks for to pull together in a style guide around spacing, colors, fonts etc. They are even experimenting with providing HTML and CSS outputs from the designs.

When creating wireframes I tend to use both interactions that provide some level of prototyping and annotations that help provide specifications not easily seen through an interaction. For the last couple of years I have been using Axure RP as my workhorse application. I could easily create and update flow diagrams, taxonomies, site maps. It provides amazing prototyping with annotations, show / hide, modal windows, and even complex interactions such as rotators. Axure also provides an easy way for me to share my designs with my clients through an online web viewer.

I have experimented with a few other tools such as Adobe XD, however I still think they have a ways to go with making this a single use tool that provides all the features that I need.

I do see a benefit for all designers to be working on the same tool to easily transition from wireframes to visual comps without too much of a complete rework. However, I would be interested to learn more about how your teams work together and the tools that you use?

Monday, February 6, 2017

Blog Transition from SharePoint to User Experience Design

As time goes on we learn, grow and explore in new areas that make us happy and inspired. I am very lucky to have found that path. Since 2003 I focused on providing great experiences to my clients around a specific tool known as Microsoft SharePoint. I was so invested in this tool that I even wrote a book on how to stretch the limits on customizing it. Over the last couple of years SharePoint has changed to be more stand alone through Office 365.

Within the last few years I have had the pleasure to not only wok for the best company Slalom Consulting but also work for some really amazing clients! My most recent projects have been outside of the world of SharePoint and in all honesty I could not be happier. It is sad to see it go but I think it is time to pass the torch to other great and amazing bloggers that will keep posting technical posts on how to configure and explore new ways of making SharePoint do what they need to present the right information to users at the right time.

My plan is to transition this blog from a technical reference point around a specific technology to a more organic discussion around User Experience Design, Research, and Information Architecture topics. In all honesty this is really what I have been doing for the last 15 years of my career anyways. I am not going to remove or delete any previous post since some of them still can provide value to others that still support SharePoint both in the cloud on Prem.

I have some great UX topics in mind that I think all will gather some insights from. Thanks to all that have supported me over the years and I hope to inspire many others in the future to think outside of the box and create amazing experiences that matter!

Erik Swenson
Principal Experience Designer