Iteration: Difference between revisions

932 bytes added ,  24 January 2023
no edit summary
No edit summary
No edit summary
Tags: Mobile edit Mobile web edit
Line 7: Line 7:
This principle applies whether you are solving new problems, dealing with an unexpected crisis, or building out your system — the [[end-to-end principle]] allows maximum [[iteration]]. Don’t be wedded to the way you’ve been doing things — I know, I know my little eaglets, it is so hard to let go of the comfort blanket of [[precedent]], but you must — try, and expect things to fail. Don’t commit. Scrub them out and try again.
This principle applies whether you are solving new problems, dealing with an unexpected crisis, or building out your system — the [[end-to-end principle]] allows maximum [[iteration]]. Don’t be wedded to the way you’ve been doing things — I know, I know my little eaglets, it is so hard to let go of the comfort blanket of [[precedent]], but you must — try, and expect things to fail. Don’t commit. Scrub them out and try again.


Some uncomfortable truths:
But successful [[iteration]] is ''hard''. The more practice you have at it, the better you will be. The more you understand the systems and subsystems comprising your environment, the better you will be at navigating them. [[Subject matter expert|Expertise]], skill and experience matter. Your itinerant [[school-leaver from Bucharest]] might be cheap and fungible, but she won’t, from the off, be good an expert. She will only get that expertise by [[iterating]].  
*'''Successful [[iteration]] is ''hard'''''. The more practice you have at it, the better you will be. The better you understand the systems and subsystems comprising your environment, the better. [[Subject matter expert|Expertise]], skill and experience matter. Your itinerant [[school-leaver from Bucharest]] might be cheap and fungible, but she won't be good at [[iterating]]. Though she will get better.
 
*'''Iterating won’t always work'''. The thing about [[tail event]]s is they’re hard to predict. On the other hand, an [[iterative]] process will almost certainly be more effective than a [[chatbot]]. And trying something that doesn’t work still yields you information: it is a [[falsification]]: now know that that isn’t the answer. You needn’t fret about what might have been.
Not all iterations ''work''. The thing about [[tail event]]s is they’re hard to predict. On the other hand, an [[iterative]] process will almost certainly be more effective than a [[chatbot]]. And trying something that doesn’t work still yields you information: it is a [[falsification]]: now know that that isn’t the answer. You needn’t fret about what might have been.
 
Iteration is effortful: You have to work at it. It is to acknowledge you have a work in progress. It can be annoying, especially to people who don’t like to admit things are a work in progress.
 
Everything that is not dead is a work in progress.
 
There will be strong impulse ''against'' iteration from people in the organisation:
*Those [[sales|fearful of upsetting client]]s, especially on repeat business, or once a termsheet has gone out: “for god’s sake don’t ''change'' anything!”;
*Those — and they tend to be more senior people — who know what they know and like things how they are (this being the way things were that got them where they are);
*Those who believe in reasoning from settled principles. Lawyers tend to be[[stare decisis|like that]]. The common law is ''predicated'' on being like that.
 
“If it ain’t broke, don’t fix it” is the anti-iteratist’s stance.


===Other articulations===
===Other articulations===