UX Working & Learning [20 May 2019]

Home / Enterprise Software  / UX Working & Learning [20 May 2019]

I’m recommitting to journaling my experience as a working UX practitioner. I’m not sure exactly why I stopped. Between 2006 and the mid-teens I had a good run with UsabilityBlog. Somewhere along the way I probably got too task-loaded, and I just tailed off.

Here’s the thing, and I doubt it’s just me that has this feeling: it’s hard to start blogging again when you expect that every piece you produce should be worthy of a keynote speaking slot. So join me as I lower both your expectations and mine. And read on for a peek into my ongoing series I’m going to call “UX Working & Learning.”

What I’m Working On This Week

I’ve been working with a Cleveland-based software company for a few months now. This past winter I designed views and workflows for a new set of features they’re rolling out in the beginning of Q3. For the past few weeks I’m helping them redesign information architecture and navigation so their suite of products employs a consistent navigation scheme, structure, and interaction style. Like many enterprise software products, they haven’t had much in the way of a design system or any product line-wide design standards. So their five or so main products, which are increasingly converging to meet target users’ needs, are wildly inconsistent in some areas. The principal designer (actually, only designer) and I were tasked with bringing the products’ navigation and IA together, while not stranding (read: pissing off) the installed user base.

It’s a challenge, but I’ve done this type of thing before. I learned some important lessons when I led the redesign effort at Peachtree Accounting over 10 years ago. My key takeaways then were:

  • You can add a second navigation scheme and system to an existing, inefficient one. But you need to make sure they don’t interfere with each other. You have to ensure you’re not pulling the rug out from the feet of long-time users who are resistant to change, while also providing a more sensible and usable scheme and system to newer and future users who haven’t overlearned the old ways of doing things.
  • Don’t put all your redesign eggs in one basket. Design several competing alternate versions, and test them. Let iterative usability testing be the “design Darwinism” mechanism of identifying the best IA and navigation.
  • Position the design and testing as iteration zero so you can defend against “BDUF” (big design up front) accusations. Agile works great when most of the design direction is known. But UX’ers need more than your standard two weeks for a ground-up redesign or product line convergence.

What I’m Learning This Week

Sometimes I learn a soft skill technique, other times I’m heads-down in a new tool or application. This week I’m learning how to use the prototyping tool UXPin. The lead designer uses it and would like to be able to collaborate on the IA and navigation concepts. So I’m off to watch a few more video tutorials.

No Comments
Post a Comment