Annealing

December 30th, 2012
change, time
Flexible and pliable in youth, rigid and set in age. When an organization is founded it usually has a purpose and little else. The founders have some ideas about how to run it, but try many things. Over time, if it succeeds, it settles and solidifies into a stable institution with an inertia that it keeps it consistent and resistant to change. Software systems run through this pattern faster, often going from design to prototype to production to legacy in only a few years. And of course people run through this pattern too as they age.

This process is often seen as negative, where people are exhorted to keep an open mind as they age and large organizations are mocked by agile pivoting startups, but that sells it short. There are far more possible ways to be than anyone can explore, and at the same time you'd rather spend more time in the better places. You need some way to decide whether to accept potential changes that balances the good of staying with the current system against the unknown better systems out there. Decreasing willingness to accept change over time is a good solution that works well over a wide range of problems.

Comment via: google plus, facebook

Recent posts on blogs I like:

Pay For Fiction

Against piracy

via Thing of Things February 29, 2024

When Nurses Lie to You

When the nurse comes to give you the flu shot, they say it won't hurt at all, right? And you trust them. Then they give you the shot, and it hurts! They lied to you. A lot of nurses lie to children about shots and blood draws. Part of it is they probabl…

via Lily Wise's Blog Posts February 28, 2024

How I build and run behavioral interviews

This is an adaptation of an internal doc I wrote for Wave. I used to think that behavioral interviews were basically useless, because it was too easy for candidates to bullshit them and too hard for me to tell what was a good answer. I’d end up grading eve…

via benkuhn.net February 25, 2024

more     (via openring)