Frozen accidents are chance happenings that have become ad hoc standards because it would take too much effort to switch to another configuration. The term “frozen accidents” is primarily used in discussions of Darwinian evolution. An example: the heart is generally a little to the left of center in a person’s body. There’s no particular reason that evolution didn’t roll the dice differently early on, leading to hearts being a little to the right of center. But once the original configuration was set, it got locked in.
In the abstract space of the working world, frozen accidents are ubiquitous. Even if, in principle, there are fifteen ways to route the paperwork, there’s only one way for which the boss (or the bureaucrats pushing the paper) say, “but THIS is the way it’s done here.” Because a decision was made sometime in the past, it has become an ad hoc standard. Now, the logic behind some decisions made in the past may still be apropos, but we all know situations in which a) the logic employed at the time of the decision is inappropriate in the present context, or b) there wasn’t logic - it was a choice that could have been made by rolling dice or some other chance method.
Sometimes, institutional memory is insufficient to figure out why a decision was made the way it was. Many decisions made in the past can seem like they were accidental choices.
In any event, the decisions have been frozen. I like to call them “frozen accidents” because the idea behind the term is so powerful.
Here’s what it looks like:
- A choice is made between various perceived, available configurations in a very specific context.
- Later, the context has changed, but the choice that was made remains active, a “frozen accident.”
- At this later time, other configurations can be perceived, but they’re no longer “available.”
The idea of “frozen accidents” is helpful in understanding why good ideas sometimes don’t get off the ground. It is part of the reason organizational change isn’t easier.
Here are some examples of frozen accidents in the abstract “space” of work, in the specific context of the university where I work. Some of these are specific to my workplace, others are more general:
- Saturday and Sunday are the weekend days. Need these always be the same? The same for everybody? Do weeks have to be seven days long?
- There are two regular semesters and a summer semester per 12 month period. Other universities have quarters, for example. But it’s rare for a university to switch from one system to the other, although some do.
- Faculty and students interact through “courses” taught within “disciplines.” There are other models besides “courses” for learning. Most people learn much more outside of courses than they do in them. Internships, problem-based learning, etc…
- Student transcripts record pretty much only what “letter grade” a student “earned” in each course. We do it because that’s how it’s been done, it’s simple (although oversimplifying what happened in the student’s learning), and it’s an ad hoc standard that employers understand.
- Courses all begin at the beginning of a semester and end at the end of a semester. Why should all courses/topics have the same duration of treatment? When courses all end at the same time, all the final projects and exams fall at the same time, inefficient at best and a recipe for burnout at worst.
For anyone who perceives the tensions between the way things are and the way they “should” or “could” be, frozen accidents are both interesting and frustrating. They represent the “inertia” of the system, and we know that organizations with too much inertia invariably decline.