- Google Dev Apologies After Photos App Tags Black People as Gorillas (Ars Technica) — this is how you recover from a unequivocally horrendous mistake.
- IRS Finally Agrees to Release Non-Profit Records (BoingBoing) — Today, the IRS released a statement saying they’re going to do what we’ve been hoping for, saying they are going to release e-file data and this is a “priority for the IRS.” Only took $217,000 in billable lawyer hours (pro bono, thank goodness) to get there.
- Time Series Database Requirements — classic paper, laying out why time-series databases are so damn weird. Their access patterns are so unique because of the way data is over-gathered and pushed ASAP to the store. It’s mostly recent, mostly never useful, and mostly needed in order. (via Thoughts on Time-Series Databases)
- Compiler Errors for Humans — it’s so important, and generally underbaked in languages. A decade or more ago, I was appalled by Python’s errors after Perl’s very useful messages. Today, appreciating Go’s generally handy errors. How a system handles the operational failures that will inevitably occur is part and parcel of its UX.
Personas are a useful tool, almost always used badly.
Register for the UX Design for Growth — Improving User Conversion training session with Laura Klein. In this online, interactive training workshop, Klein, author of “UX for Lean Startups,” will teach you to design for product growth.
Personas have always struck me as a potentially useful tool that is almost always used badly. In theory, they’re great. Who doesn’t love a deliverable that is designed to get everybody on the team more familiar with the ideal user? Why wouldn’t we create something to help us focus our design and engineering efforts around the real people using our products?
Unfortunately, the reality rarely lives up to the hype. Personas, as they are created in many organizations, aren’t nearly as useful as they could be. They’re rarely based on real user insights developed during research. They tend to be overly broad and generalized. They’re descriptive, rather than predictive. And that’s just a few of the things people get wrong. Read more…
:focus'ing on users.
Editor’s note: The author would like to acknowledge her co-author, Brian Kardell, who contributed many insights to the ideas presented here, along with a substantial number of the words.
Web developers and web standards authors alike strive to live up to the promise of “universality” — the idea that the web should be available to all. This concept drives many innovations in web technology, as well as being fundamentally built in to the philosophy of the open standards on which the web is based.
In order to achieve this, we frequently find that having some carefully chosen information about how the user intends to view the content (a concept we’ll refer to in this article as “user context”) allows web developers to create more flexible and useful user experiences. In this post, we’ll lay out a case that it’s time to expand our view of user context to include the concept of modality (how the user is interacting with the page), but before we flesh that out, let’s take a look at “user context”.
We need to provide people with proper access, interaction, and use of technology so that it serves their needs.
Download a free copy of “The New Design Fundamentals,” a curated collection of chapters from the O’Reilly Design library. Editor’s note: this post is an excerpt from “Tragic Design,” by Jonathan Shariat, which is included in the collection.I love people.
I love technology and I love design, and I love the power they have to help people.
That is why when I learned they had cost a young girl her life, it hurt me deeply and I couldn’t stop thinking about it for weeks.
My wife, a nursing student, was sharing with her teacher how passionate I am about technology in health care. Her teacher rebutted, saying she thought we needed less technology in health care and shared a story that caused her to feel so strongly that way.
This is the story that inspired me to write this book and I would like to share it with you.
Jenny, as we will call her to protect the patient’s identity, was a young girl who was diagnosed with cancer. She was in and out of the hospital for a number of years and was finally discharged. A while later she relapsed and returned to be given a very strong chemo treating medicine. This medicine is so strong and so toxic that it requires pre-hydration and post-hydration for three days with I.V. fluid.
However, after the medicine was administered, the nurses who were attending to the charting software, entering in everything required of them and making the appropriate orders, missed a very critical piece of information: Jenny was supposed to be given three days of I.V. hydration post treatment. The experienced nurses made this critical error because they were too distracted trying to figure out the software they were using.
When the morning nurse came in the next day, they saw that Jenny had died of toxicity and dehydration. All because these very seasoned nurses were preoccupied trying to figure out this interface (figure 1-1). Read more…
Raising the banner for a new discipline.
In this excerpt taken from the upcoming book, Front-End Architecture: A Modern Blueprint for Scalable and Sustainable Design Systems, Micah Godbolt details the history of this new discipline and explains why it is such a vital role to embrace in our industry.
With the evolution of the web came changes to the roles of the modern web team. We went from a small group of generalist webmasters to a team of talented specialists. As each of these specialties developed, and members became more proficient in them, the web began to form a new set of roles… or disciplines.
As developers and designers converge, we're seeing an increased focus on the user's perspective.
Editor’s note: The O’Reilly Velocity Conference in Santa Clara was held last week. The event explored the essential trends driving web operations and performance forward. In the post that follows, Mark Zeman digs into recent changes he’s observed in one aspect of Velocity: the role, language, and metrics surrounding user experience.
I’ve attended four O’Reilly Velocity conferences over the last year, and I was struck by a notable shift in the conversations at Velocity in Santa Clara, Calif. Many speakers and attendees have started to change their language and describe the experience of their websites and apps from the user’s perspective.
The balance has shifted from just talking about how fast or reliable a particular system is to the overall experience a user has when they interact with and experience a product. Many people are now looking at themselves from the outside in and developing more empathy for their users. The words “user” and “user experience” were mentioned again and again by speakers.
Here are recent talks from Velocity and other events that highlight this shift to UX concerns. Read more…
Enhance the user experience with the thoughtful use of sound.
It’s definitely a fun toy to play with, but most of us probably couldn’t think of how this might be relevant to our jobs. When I presented 8-bit game music with the Web Audio API at last year’s Fluent Conference, I readily admitted that it was intended to be purely fun rather than practical.
Recently I explored the idea of adding audio to web apps, but I think the big problem isn’t that web developers were unsure how to add audio to their app, but that they don’t think they should add audio to web apps. In this article, I’d like to make the case that you should be considering audio when designing your web application user interface.