Getting data from your users is a fundamental part of creating great user experiences. Surveys are a great way to get feedback and learn about your users. The problem is everyone has sat through a painful, monotonous survey that asked a series of frustrating and seemingly pointless questions. As with anything in UX, if your users sense they’re in for a painful experience they simply won’t engage with your survey.

A dashboard is often the first screen that a user sees in your UI. The importance of visual design and data visualizations is high. But good looks aside, the dashboard has to meet the users’ needs. Beautiful dashboards are futile if the presented information isn’t useful to the user to accomplish their tasks.

Change is always an interruption. For those switching to an Agile process, the transition doesn’t always go so smoothly. Suddenly, with things moving so quickly, the role of UX gets lost in the shuffle. User experience is often disregarded in Agile development.

The right data can be more effective than words when it comes to telling a story. Even if you have the data, you have to present it in the correct manner. Choosing the right axes, colors and placement are all a big part of putting together a great visualization. Noah Iliinsky demonstrates what goes into creating an effective visualization.

Touch screen devices are commonplace. It’s now expected that your mobile experience work as well as, if not better than, your desktop experience. With faster connection speeds, cameras, GPS, gyroscopes, and accelerometers, we can deliver information to users in new ways. But we can also receive information from them as well.

With mobile, you simply can’t have as much content on your pages as you do on the desktop. Intranet access within enterprises is crucial and accessing it with mobile devices is beneficial. However, the vast amount of pages and content is cumbersome and impractical for a mobile setting. James Robertson asks, what are the few essential things users need while they are away from their desks?

Lean UX can eliminate the contractual obligations inherent with specification documents and other deliverables. Designers and developers find it frustrating to put so much effort into a project then not see it ship at the end. Using the Lean UX process, you’re constantly validating your designs, especially early in the process. This motivates the team to work towards the same end goal.

There’s a belief that user experience insight is lacking in Agile development. Trying to shoehorn UX practices into an Agile process results in a lot of frustration. Often, developers build stuff faster than the designers can design it. The whole process often focuses on the delivery more than the quality of the experience. Anders Ramsay believes that UX and Agile can coexist.

Technologies are often misunderstood at their outset. This misunderstanding leads to a lack of adoption. This lack of adoption leads to the technology not reaching it’s full potential or not being utilized in useful ways. This is essentially what happened to JavaScript. Its detractors said it wasn’t a real programming language, and it’s capabilities were ignored. Dave McFarland notes that Google’s use of JavaScript in Google Maps makes a lot of people take notice.

Mobile is greatly influencing the user experience community. It’s challenging traditional approaches to design, but also bringing with it a host of new opportunities. Being a user experience practitioner in this changing environment is a bit scary. Yet coupling existing skill sets with the constraints of designing in the mobile space makes for an exciting world full of possibility.