It's always a pleasure to spend time in the field. Today I was out and about in water production and distribution talking to people about the time it takes to acquire deep knowledge. One common theme from all of the people I met has occurred in similar projects elsewhere. You can have all the process maps and automation you want, but nothing substitutes for knowing the job through experience and there is still a place for manual records. Even if a water treatment plant has more or less identical processes and equipment, even a well qualified engineer would not trust himself to manage it until he had walked the site, and worked there for some months. A field engineer has kept the old inspector reports from the pre-technology days. Handwritten in the main, they contain usable knowledge that should be seen as complimentary to GIS and other like systems. Especially when things are going wrong. I saw someone prevent water being cut off from a set of houses, not through following process, but by "feeling something was not right" as he started to move a valve.
Nothing new here by the way, I have seen variations of all the above in utility companies around the world. It is also true that you learn far more by following people on the job than through interviews. The final point (before I go to bed) is the passion that people in the field have for customers and their job if they have committed a large part of their lives to it.
Comments (3)
I know the feeling. I was honored to spend an overnight shift at the local emergency response center, watching police and fire dispatchers do their jobs. Lots of great insights regarding information sharing among workstations, heroes managing resources despite criminally-inept computer programs, etc.
But the enduring memory comes from watching true professionals using their instincts and experience to keep things working, saving lives, etc. There is no way I would have learned what I did from interviews or anything other than just sitting with them and trying not to get in their way too much.
Posted by John Bordeaux | January 19, 2008 1:01 AM
Posted on January 19, 2008 01:01
Ah, yes indeed. And therein lies the dilemma of any process redesign consultant. The job requires that great respect and humility be applied for the reasons you mention. Yet take that too far and nothing will change...
Posted by Simon Carswell | January 20, 2008 10:06 PM
Posted on January 20, 2008 22:06
This principle is the same one that makes 'reframing' such an important language skill when working with others in any development task.
Reframing any situation being addressed, and what is to be achieved, should enable the useful things from the past to be brought forward. And not just because they are useful... but also because it makes change so much easier and a more positive experience for those who are subject to the change.
Ivan Webb
Posted by Ivan Webb | January 21, 2008 11:23 PM
Posted on January 21, 2008 23:23