Wednesday 10 October 2012

swimlanes

I wonder if a flowchart ever really simplified a human decision-making process, or whether such diagrams always instigated a little aversion and defeat at first glance, regardless of content. Such a tool may be fit for representing, in terms of a more natural language, the input/output of computer programming but I think the collection of conditions and operators presented is just another layer shrouding instinct or bias in many cases. Flow diagrams provide a framework for solving algorithms, which computers can become very good at, but are not exhaustive or predictive of every contingency and are probably best at making snarls, choke-points more apparent.
Humans, I believe, are more apt to respond to a proof or a concrete and universal rule, rather than a passably effective way to work something out. While we are not always afforded the luxury of hard and fast laws for guidance and improvisation is called upon, but I do not think that the absence of established rules calls for the creation of provisional systems that either beggar our worse judgment or second-guess real leadership and such a method is not a substitute for an authentic imperative or thorough reasoning.
Once a system or method gets complicated enough, and I believe such code sketched out in long hand would quickly become too complex for human navigators, it becomes fairly convincing.
The people who design such charts are also fairly keen on the credibility of their work-product, and it can become problematic when inventors get too proud over their schemes and throughput. It’s scary to think that such guidelines (the branching off of process charts is called a swimlane), which is the deft guesswork and approximation of machines and field manuals, might be held not to the same rigour and standards as something inviolate and accepted without question.