Wireframes call out key moments in design in order to clarify how something should look, feel, and function.

Can an AI learn to write better looking websites than a human? Frighteningly, yes.

Software and web developers often wear many hats, but some lack the knowledge to design or collaborate effectively with UX designers and researchers.

When it comes to data-driven user interfaces, like those utilizing graph data, it’s vital to understand your users and what they’re trying to achieve.

On any given day, we perform numerous searches, many consciously and many without even realizing.

Product owners and stakeholders have a tendency to skip over discovery research and go straight to design and then go right to release.

What are the next big trends in UX? At our recent Expero Summit, we discussed many advances that promise to transform how users interact with technologies. As augmented reality and other technologies take substantive form, it’s more and more about what the user needs from these amazing technologies and less about how cool the technology actually is. It’s a given that the technology is only going to get cooler. What’s not as obvious is whether the user is ready for it.

One of the major hesitations from product stakeholders regarding end-user engagement, specifically user testing, is that they often don’t want anyone to see it till it’s “perfect” or “ready” or “MVP.”

Lean UX and the Agile mind-set are all about efficiency - emphasis on forward progress, no project management bells and whistles, cut the deliverables, go-go-go.

When designing and developing software, it is critical to take into account the limitations of the technology employed, especially hardware—things like computers, boxes and other physical devices. But there’s another aspect to hardware that should be taken into account and is often overlooked: the user.

Visual design is about more than keeping up with popular design trends, especially for complex apps

Business Leader Reading

Achieving user adoption goals for enterprise software can be challenging.

Smartphone and tablet experiences are a major force influencing product development according to an internal survey we recently conducted with our clients.

“Can’t we just…” I know the phrase. I can’t specify the last instance I heard it. And, worst of all, I’ve said it myself. If I close my eyes, I can see the meeting rooms I’ve heard it in…which is every meeting I’ve ever been in.

What do my users want to do with Big Data? How do they want to visualize it, interact with it and manage it? How big is my data, really? How much data can a human deal with at one time, and how much data should we process at one time? How can the UX accommodate data sources that respond at different rates?

Are you a Product Manager looking to show some early design directions to stakeholders and end-users? Are you a Developer needing a little more direction from the design team? Or a UX Designer or Researcher trying to figure out how detailed your designs need to be to communicate your intentions and get valuable feedback from users?

Ever wonder about the best way to visualize your application’s data sets?

A design pattern, as we explained in our January 2015 blog post, is “a good, reusable solution for a common but specific interaction design problem.” In this online seminar, Lynn Pausic and I present design problems that are often seen in applications and sites with large or complex data sets. We also give 10 examples of patterns that can be used to solve those problems–things like how to set up a complex data table to view status at a glance, or when to employ column filtering so users see only what they choose to see.

I’m a fan of Yahoo for news and email, but I’m not a fan of their new “two-tap rule.” The rule states that once a user is in a Yahoo application, it should take only two taps to do anything the user wants to do. Fast-to-use apps are the goal here. The two-tap rule sounds a lot like our field’s misguided “three-click rule,” which Expero cautioned against in 2007.

Several years ago, I attended a neat speech by a young but awesome UX Designer named Golden Krishna, with credentials ranging from product innovating at Samsung, to designing at Zappos, to writing for major publications. The speech was titled “The Best Interface Is No Interface,” and the room was packed—presumably full of user interface designers. It was a great hook.

Is Google’s Material Design for complex software? My first reaction after reading through these new Google guidelines was: no.

Many organizations haven’t embraced UI design patterns, despite their growing popularity among UX professionals. Those organizations are missing out on a ton of benefits for Product Management, Engineering, Marketing, UX and the business as a whole.

Q: I have a new job as a UI designer, and my company just doesn’t understand User Experience. Development runs the show, and they think my job is to design icons and color palettes. What’s the best way to explain UX so that everybody gets it?