Here’s what I’m doing in UX this week…

What I’m Working On

While I’m still working on the information architecture and navigation redesign project I’ve been on for about 6 months, two old clients came back for user research and workflow design.

Old client 1 is (broadly speaking) in the financial services industry. My design partner Brent Cameron and I redesigned one of their flagship SaaS products about 2 years ago. It provides financial services workers the ability to download reports that are financial and legal in nature. We’re back to solve an interesting design problem: how can the organization increase adoption of reports that are available to their customers, but require an incremental purchase?

It’s an interesting design challenge because their user base may or may not have purchase authority, depending on who they work for. So we need to design for two separate use cases:

  • The user can directly purchase add-on or supplemental reports.
  • The user must route a request for purchase to their organization’s point of contact for the application.

There’s more to the design challenge. We could design in calls-to-action in many areas of the application, but if we add too many CTA’s or we put them in places where users don’t feel they belong, we risk annoying them. We obviously don’t want to do that, so we need to be judicious in our placement of CTA’s. We’re also designing the central repository for available reports – essentially a digital store embedded within the app – but we’re fairly confident we can rely on existing patterns for this area. We’ll need a gallery pattern that organizes the reports in a sensible manner. Ideally we should provide short descriptions that relate why each report is useful and probably what users would find it most useful.

We’re also going to rely on a product page pattern for individual views of each report. Existing patterns are our friends here: more content detail, a preview, possible a download link for a sample report, the works. I’d love to have a recommendation engine dynamically a generate a view of related reports for cross-selling purposes, but for MVP any related report presentation will almost definitely be static and best-guess driven.

Old client 2…things aren’t final with them yet so I don’t want to jinx that gig. But let’s just say I’m really looking forward to it. I’d be conducting user research with developers to better understand their needs around building apps for and connecting to services provided by a high-traffic platform. I’ve spent most of my career side-by-side with developers, and while I would never ever put any code I’ve written (and it hasn’t been much) into production, I like working with developers. Designing tools for them is immensely gratifying.


We’re in week 6 of the two 7-week courses I’m teaching for KSU. So far I’m really pleased with how the roughly 55 students are doing in the introductory class User Experience Design Principles & Concepts and the core course Researching User Experience I. A few observations on teaching UX’ers and soon-to-be UX’ers:

  • Communicating UX research and design should be treated by everyone – including me – as an opportunity for continual self-assessment and improvement. I don’t just mean creating pretty, well-formatted deliverables. As UX’ers, we should always be focused on relating research findings and design decisions in ways that meet the stakeholders more than halfway across the communication chasm. I don’t think that means we need to create our deliverables or artifacts anew for each different audience and situation. But I do believe that we should always prepare our design comm with an understanding of who the audience is. For example, will you be presenting to managers? Executives? Product managers? Blended teams? Adjust your messages accordingly. If you’re presenting to multiple audiences simultaneously – for example, VP’s of Product and Development alongside individual product and dev contributors – then you need to thread the needle, so to speak. My advice in this situation: aim for the VP’s, but have detailed supplemental (or followup) material ready for the contributors. The key is that you’re trying to build alignment up and down the org chart.
  • Some people take naturally to solving design problems, but all UX’ers benefit from a mix of analytic structure and free-form, inspiration-driven creativity. It’s been fun watching students mix these two key UX ingredients in varying proportions as they work on curriculum-based design challenges as well as challenges at their places of work.

What I’m Learning

I’m collaborating with our former students Brian Parsons and Jennifer Sweeney to create an accessibility course. So I’m catching up on the latest developments in access technologies and universal design practices.

Finally, I’m about 70% through Stephenson’s latest. Having heard next to nothing about this book, I was pleasantly surprised to discover that Stephenson ties it back to Reamde and The Baroque Cycle. Given that reading Stephenson is going to be a crash course in anything from architecture to teleology, I’m sure I’m learning…stuff. Can’t tell you what it is quite yet.

Here’s what I’m doing in UX this week…

What I’m Working On

I’m still working on the information architecture and navigation redesign project with the Cleveland-based software company. But a few interesting opportunities came my way last week:

  • An old client from the financial & real estate software world called me. His team want my design partners and I to restart support for new feature research, workflow design, usability testing, and design system updating. This is nice because it means we can essentially pick up where we left off last year for most of the products we supported.
  • A local (as in Cleveland) experience design consultancy asked me to join them on a bid to design and usability test a mobile-based patient check-in system for a regional healthcare organization. Every time I think I don’t have a network to speak of, I need to remind myself about opportunities like this.


As I mentioned in earlier posts, I’m teaching two well-designed classes for KSU during the first half of summer: User Experience Design Principles & Concepts and Researching User Experience I. So far, so good. There’s only been a few minor hitches that were easily remedied through some on-the-fly instruction updates.

What I’m Learning

Honestly I’m so task-loaded this week it doesn’t feel like I’ll be intentionally seeking out new information. But I did learn that Neal Stephenson’s new book goes on sale tomorrow, Technically that counts as learning something, right?

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.