<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:dw="https://www.dreamwidth.org">
  <id>tag:dreamwidth.org,2010-05-25:518129</id>
  <title>Rick Scott</title>
  <subtitle>Testing, hacking, and Open Source</subtitle>
  <author>
    <name>Rick Scott</name>
  </author>
  <link rel="alternate" type="text/html" href="https://rickscott.dreamwidth.org/"/>
  <link rel="self" type="text/xml" href="https://rickscott.dreamwidth.org/data/atom"/>
  <updated>2010-05-25T17:13:17Z</updated>
  <dw:journal username="rickscott" type="personal"/>
  <entry>
    <id>tag:dreamwidth.org,2010-05-25:518129:1120</id>
    <link rel="alternate" type="text/html" href="https://rickscott.dreamwidth.org/1120.html"/>
    <link rel="self" type="text/xml" href="https://rickscott.dreamwidth.org/data/atom/?itemid=1120"/>
    <title>Are *you* pointing &amp; calling? Human error and how to reduce it</title>
    <published>2010-05-25T17:00:55Z</published>
    <updated>2010-05-25T17:13:17Z</updated>
    <category term="human error"/>
    <category term="mind hacking"/>
    <category term="systems thinking"/>
    <category term="psychology"/>
    <dw:security>public</dw:security>
    <dw:reply-count>0</dw:reply-count>
    <content type="html">&lt;p&gt;This is more about "mind hacking" than QA or tech, but still,  stuff like this fascinates me:&lt;/p&gt;
&lt;p&gt;&lt;a href="http://en.wikipedia.org/wiki/Pointing_and_calling"&gt;http://en.wikipedia.org/wiki/Pointing_and_calling&lt;/a&gt; &lt;br /&gt;
&lt;a href="http://search.japantimes.co.jp/cgi-bin/ek20081021wh.html"&gt;http://search.japantimes.co.jp/cgi-bin/ek20081021wh.html&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Background: In Japan there's this practice called shisa kanko (指差喚呼), usually translated into English as Pointing &amp;amp; Calling.  It's a  technique that makes sure you actually check critical safety items.   You&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;call out loudly what you're supposed to be checking, &lt;/li&gt;
&lt;li&gt;point at it, &lt;/li&gt;
&lt;li&gt;check it and announce the result. &lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Train drivers are the most conspicuous example; they're actually the ones that started doing this in the first place.  If you were sitting in the cab of a train about to leave Ueno station, you might see the driver  pointing to items and checking them off like this:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;em&gt;(Door indicator light)&lt;/em&gt; "Doa: shimete-aru!"  (Doors: closed!) &lt;/li&gt;
&lt;li&gt;&lt;em&gt;(Signal light)&lt;/em&gt; "Shuppatsu: shinkou!"  (Departure signal: proceed!) &lt;/li&gt;
&lt;li&gt;&lt;em&gt;(Speed limit sign)&lt;/em&gt; "Seigen: sanju-go!"  (Speed limit: 35!) &lt;/li&gt;
&lt;li&gt;&lt;em&gt;(Timetable)&lt;/em&gt; "Ueno: hassha!"  (Ueno: depart!) &lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;This sounds stilted, nerdy, and quite frankly, embarassing.  Does it  really work?&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;"I posed that question to Kazumi Tabata of the Japan Industrial     Safety and Health Association, who showed me research conducted in     1994 ...The combination of pointing and calling reduced mistakes     by almost 85 percent."&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;All of us sometimes have to do tasks where the key challenge is to stay sharp and pay attention to a very routine or boring set of inputs. Driving is a good example.  Sifting through columns of identical-looking numbers searching for an error is another.  We've only got a limited  ability to stay alert, so it's easy to go "on autopilot" during tasks  like these.  We might skip steps in a checklist, or "check" something without really checking it, especially if we're tired or distracted.  How many times have you looked both ways at an intersection and completely failed to see an oncoming vehicle?&lt;/p&gt;
&lt;p&gt;As technical people, it shouldn't come as a great surprise that we focus a great deal on technical tools and techniques.  Will this database tweak make our site run faster?  Will this test tool let us catch more bugs? I think we often neglect ways in which we can upgrade our &lt;a href="http://en.wikipedia.org/wiki/Wetware_%28brain%29"&gt;wetware&lt;/a&gt;, even though it may be the most fruitful place in the system to look for improvement.&lt;/p&gt;
&lt;p&gt;Humans are inherently error-prone and are always going to make mistakes, but that doesn't mean that there's not room for improvement. Any way that we can improve our acuity as individuals reduces the number of mistakes we send downstream for technology, process, or other people to catch.  It's a no-brainer.&lt;/p&gt;&lt;br /&gt;&lt;br /&gt;&lt;img src="https://www.dreamwidth.org/tools/commentcount?user=rickscott&amp;ditemid=1120" width="30" height="12" alt="comment count unavailable" style="vertical-align: middle;"/&gt; comments</content>
  </entry>
</feed>
