Presenting Design Work by Donna Spencer

Presenting Design Work by Donna Spencer captures everything I’ve learned about that harrowing process of presenting a web design for review and turned it into a six chapter book you can read over two lunch hours.

I am thrilled that this book emphasizes rigor in the craft of creating and presenting designs.

So many times I’ve sat through reviews where the designer couldn’t tell me what the business problem was, why the user needed the changes, how the user would get from place to place, or what the unhappy paths looked like. They failed to take notes (sometimes showing up without even a note-taking device, like, say, a pencil or a laptop), gave me a tour of our components on the page instead of telling me how someone would use it, and thanked everyone when done — but never followed up to let us know what they’d decided. Then, later, they complained that the product manager steamrolled their input on designs or ignored their feedback.

This book demands a lot of the person who wants to be successful. You have to think about your audience, practice presenting, take notes (or find someone who will), understand the problem you’re building against, understand the feedback you’re given, and be rigorous in your feedback decision-making process.

It also works. It works so very well. And it garners trust between us and our business and engineering peers way better than any less-rigorous process is capable of doing.

As soon as I started reading it, I started messaging people I know mentoring designers and said “yeah this book? this is the one you want.”

Quiet in a time of change

You may have noticed that the site has become… well… UX-related book reviews mostly.

That’s not an accident — I’m reading more than I have in decades, and I do my best to review good books because reviews are a driver for sales, and good authors deserve to be rewarded for being good authors.

But it’s also an acknowledgement that I’m not talking about much else in UX right now. Even on The Interconnected, which is my usual ranting locus, the site was virtually silent last year.

Last year, I think we can all agree, was rough.

This year so far is better but that doesn’t mean much. When I walk the half marathon in Virginia Beach, mile 11 over the damned bridge is hell, but it being stupid hard doesn’t suddenly move the finish line closer.

Still, I think there’s a finish line around the corner, so I shall trudge on until I can fall onto the beach and soak my feet in the ocean.

Things that are looking up:

  • I have a new job at Vertex, Inc. where we design software that calculates sales tax and VAT. I am pro-fair-taxes and also pro-make-taxes-easy, and in a lot of places (for better or worse) sales taxes fund lots of important local initiatives, so at least at the moment it feels like a good fit. I’m two months in and I haven’t seriously pissed anyone off yet, but the day is still young.
  • I’m seeing more and more people in our industry concerned about accessibility and making things more equitable for all, regardless of disability. I refuse to say that the pandemic has any silver linings with 500,000 dead in my country alone. I will say that hard-earned lessons are still lessons, and hopefully we’ll come out of this with more accessible jobs, more accessible websites, and more people giving a damn about their own impacts on their neighbors’ ability to survive in an increasingly technical world.
  • While we’re on the subject of survival, there’ll be a review coming up sometime soon on Sustainable Web Design by Tom Greenwood. I’m about halfway through now and already recommending it to coworkers. Many of the goals in the book align with accessibility goals and good information architecture goals, so I think it could become an asset in convincing our higher-ups (especially in enterprise product design) that good web design = good business, both on the surface and within the code.

I’m also working (slowly) on my own accessibility website, trying to bring together information from the WCAG and the Deque online training classes I’m taking, articles that I rely on, other books, etc.. The ultimate goal is somewhere that people can navigate through a list of components and find something that says “Oh, buttons? Here are all the WCAG guidelines, info on how to hit them, and info on how to test them, all in one place.”

That’s taking longer than I thought it would because

  1. pandemic;
  2. constant exhaustion;
  3. I am the world’s worst estimator.

May you also be within sight of the next milestone, and may your strength hold out until you get there.

A deck of accessibility issues

Cross-posted from The Interconnected

Back in February, I wrote about the events that brought about the Alphabet of Accessibility post on The Pastry Box, and I hinted I might have a deck of cards to accompany it soon.

I opened the mail today and discovered that my prototype deck arrived. The Alphabet of Accessibility Deck is a real thing you can purchase with actual money from over at The Gamecrafter.

A box for the accessibility deck, with the deck, with letter z on top

I’m a little overwhelmed. When I wrote the original alphabet back in 2014, I certainly didn’t expect it would ever become a talk, much less a talk, a deck of cards, and a half-formed workshop.

But here we are, dragging the world forward kicking and screaming into the Century of the Anchovy, as Terry Pratchett would put it. And you can buy the deck and share it with your teams or your organizations or whatever you’d like.

Many thanks to Dylan Wilbanks, Jeff Eaton, Sarah Hoffman, Elaine Nelson, and Greg Dunlap (as well as many others!) for encouragement, sanity checks, and pointing me to The Gamecrafter. And all of my friends and family, who will continue to remain nameless, for their love, support, and well-earned right to complain about the things we still don’t get right when we design.

Everyday Information Architecture by Lisa Maria Martin

I’m a three-time failure at reading the Polar Bear Book.

I’m also a Principal Information Architect with 10 years’ experience.

I’m not telling you not to read the Polar Bear Book. I am telling you that if you want a short, direct, and well-structured book on what Information Architecture is, how to get started practicing it, and real-world examples of prior work, Everyday Information Architecture by Lisa Maria Martin is the book to start with.

It is the IA cohort to The Elements of Content Strategy And y’all know I’m a big fan of that book.

I started this book while sitting in a hospital room watching my husband sleep. It’s readable even under extreme stress. The book starts with the LATCH system of organization, which I had learned… but when I’d learned it through the quasi-apprenticeship of a mutual fund company’s design department, it didn’t have a name. So here I was, middle of the afternoon, snoring and beeping filling the room, and ten-year veteran of information architecture, learning things I didn’t know on page 5.

Your milage may vary (YMMV), especially if you’re one of those younger folks for whom information architecture degrees were available. (We had library science but I was too short-sighted to major in it.)

The book is vibrant and well-structured enough that I could put it down for a week at a time if I needed to and pick it up again and keep reading and understand where I’d left off. (Also, YMMV.)

Plus, this book isn’t afraid to use Star Trek, Ravelry, cooking, self-deprecating spreadsheet jokes, and colorful, useful examples.

To sum up, this book is going on the list of books anyone who asks me how to start a career in UX, along with Don’t Make Me Think, How to Make Sense of Any Mess and Universal Principles of Design.