Lynn Pausic

Webinar presentation on how to combine Graph databases with an iterative, user-driven approach and the latest UI tools to enable your team to start creating valuable user experiences with graph data.

Achieving user adoption goals for enterprise software can be challenging.

Smartphone and tablet experiences are a major force influencing product development, irrespective of industry, according to an internal survey we recently conducted with our clients. Business users want to access their software applications from a myriad of devices, all behaving correctly regardless of form factor.

Unfortunately, I had to miss the live Apple event last week. So I took a little time this weekend to wade through it and came across this rather magical little multi-touch moment from the iPad Pro demonstration. To the untrained eye, simultaneously using a virtual ruler while drawing a line with a stylus may seem like standard fare. As a practitioner who has created multi-touch user experiences involving both stylus and touch inputs, I realize that this moment Apple depicts is not to be taken for granted. Here’s a breakdown of what’s likely happening to make this moment possible:

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?

Producing great user experiences in an Agile environment can be a challenge. As a designer who has been working in the User Experience (UX) field for over 20 years and as part of Agile teams since 2006, I have truly come to embrace Agile. Dare I say, often I prefer it. As the product releases move ever faster, Agile, Kanban and other Lean methods are here to stay. It’s time for the UX field to get better educated on these topics and embrace change. Many aspects of Agile and Lean methodologies are good for UX. Here are a few tenets of going Agile-Lean that we should be using to our advantage:

Ideally, conduct usability studies on both the user interface and the documentation to help you define and prioritize problems with both. The data you gather will help you to measure the benefits in terms of business metrics for both the UI and the documentation.

If management isn’t implementing changes based on usability tests, they might not be convinced of the value of the data you’ve collected.

A Content Style Guide provides rules and examples for how content should be crafted and presented to users, and will ensure that your messaging is consistent and effective.