Skip to main content

Well Designed Failure

So last night, while I was out for a social gathering and my partner was out of town, someone appears to have tried to break into our house. They did a moderately good job of disassembling the door handle on our front door, but didn't get any further than that, thanks to the deadbolt lock on the door and the two loud dogs in their beds next to the door. Last night I was pretty upset about it, and I was also being critical of the door handle, but the more I think about it the more I think I'm wrong. I am beginning to think that the door handle itself was really quite brilliantly designed -- it was designed not just to work, but to fail gracefully.

When I got home I found the front door handle had been jimmied somehow, and was loose in the door itself; in addition, the interior handle part had come completely off the door. So I was mildly upset about this, thinking that first, someone had tried to break into my house, and second, that I would have to replace the door handle (at 9PM on a Saturday, which did not sound like the best time to go shopping for door hardware). But actually the door handle did its job brilliantly, and here's why I think that:


  1. Most importantly, the alleged intruders were unable to get into the house. So when the integrity of the handle failed, it still managed (with backup from the deadbolt and the dogs) to accomplish one of its two main design goals: keeping the door shut (the other we'll get to in a subsequent point).
  2. After the alleged intruders departed, when I arrived home I was still able to gain entrance to the house via the front door. This, by the bye, is the other main design goal of the handle: allowing the door to be opened. 
  3. This allowed the handle to accomplish another design goal, which is often ignored: it failed securely, and kept functioning even in failure mode. This was accomplished by various parts all acting in concert even in failure mode (including the length of the haft of the knob, the length and placement of the screws, and the design of the latch mechanism itself). 
  4. In addition, after the failure mode, it was relatively easy to return the handle to full working order -- the recovery process was relatively simple and not time-consuming.
  5. It did all this without any damage to the door itself, the deadbolt, or even the handle and knob mechanisms, meaning it was designed for robustness in its application.
So here we have a really, really good example of designers not just designing for the stated goals, but also taking into account failure and recovery modes. This is also an example of how even old, complicated tech (and a modern lock/latch is pretty complicated) can be designed to fail gracefully and with minimal agita to the user. From an Operational perspective, this handle may be a nearly-perfect design: secure, robust, graceful in failure, silent in normal operating modes, and easy to recover. It is a benefit of having had door knobs and locking latches for a couple of hundred years, including the last 50 or so when CAD methods have allowed for much finer tolerances and more rapid iteration of incremental improvements.

To sum this all up: if you, as a software designer, think not just about the stated goals but about how the tool you're building will be used (and broken by users), you'll have not just a better starting point, but also a better idea of what you'll need to iterate towards for improvement. 

Comments

Popular posts from this blog

Organizing And You: Lessons from Labor History

    I made a joke on Twitter a while ago: Do I need to post the Thomas M Comeau Organizing Principles again? https://t.co/QQIrJ9Sd3i — Jerome Comeau says Defund The Police (@Heronymus) July 15, 2021 and it recently came back up because a member of my family got their first union job and was like "every job should be offering these sorts of benefits" and so I went ahead and wrote down what I remember of what my dad told me. My father had many jobs, but his profession was basically a labor union organizer, and he talked a lot about the bedrock foundation items needed to be serious about organizing collective action. Here's what I remember.    The Thomas M. Comeau Principles of Organizing -- a fundamental list for finding and building worker solidarity from 50 years of Union Involvement. This list is not ranked; all of the principles stated herein are coequal in their importance. Numbering is a rhetorical choice, not a valuation. 1) Be good at your job. Even in an at-will

Activision, Blizzard, Game development, IT, and my personal role in all of that.

 I'm pretty sure if you spend any sort of time at all on Twitter and/or spend any sort of time playing videogames, you are by now at least aware of the lawsuit brought forth by the State of California's Department of Fair Employment and Housing versus Activision Blizzard, Inc., et al. From this point on, I'll add a Content Warning for folks who are sensitive about sexual assault, suicide, and discrimination based on sex, gender, and skin color, as well as crude humor around and about sexual assault , and what the State of California refers to as "a pervasive 'frat boy' culture" around Act/Bliz, especially in the World of Warcraft-associated departments.   Just reading the complaint is hard rowing, even with the clinical legalese in place. The complaint itself is relatively short; 29 pages laying out ten Causes of Action (basically, "these are the legs on which our lawsuit stands"). I'm not sure I have the vocabulary to properly express how a

Money and Happiness as a fungible resource

Money really does buy happiness. Anyone who tells you differently has a vested interest in keeping you poor, unhappy, or both. I know this because I grew up on the ragged edge of poor, and then backed my way into a career in IT, which is where the modern world keeps all the money that isn't in Finance. So I am one of the extreme minority of Generation X that actually had an adulthood that was markedly more financially stable than my parents. And let me tell you: money really does buy happiness. To be clear: at 45 years old, I'm now in a relationship and a period of my life where our household is effectively double-income, no kids. I live in the city, but I own a house, and can only afford to do that because of our combined income. We also have two cars -- one new, one used (though neither of them is getting driven very much these days) -- and we have a small discretionary budget every month for things like videogames, books, and the like. What my brother used to call DAM -- Dic