Justifying HF
<h2>Justifying HF</h2>
<p> </p>
<p>Sometimes decision makers just don't get it. Applying HF methods and Human centred design principles makes a huge difference to the quality and function of a system. There will be times when you need a few phrased that help to open people's minds and get your skills 'at the table'. Early design stage is best.</p>
<p> </p>
<p>Bias & Mayhew wrote an excellent book (2005) called cost-justifying usability. It got me started on how to shape a business case or argument to have HF skills and methods included in design and project teams.</p>
<p> </p>
<p>Once you have some business data (e.g. operational revenue; labour, contracts, or injury costs) and credible examples in like industries, it is quite easy to build a case for any astute manager. 3:1 ROI is the stand-by claim that gets management and CFO attention.</p>
<p> </p>
<h3>Some favourite quotes to roll out:</h3>
<p> </p>
<p>if you want to ensure you have a well designed system that lets your people perform their best – then you’ll have to consider human factors throughout the design process (2)reference to be added</p>
<p> </p>
<p> "twenty-first-century safety requires us to understand the increased complexity and interconnectivity between systems and their elements" John Wilson / Patrick Waterson [ check reference]</p>
<p> </p>
<p> It is said to cost over 10 times more to retrofit or change an existing system then to adopt the change in the early design stages (David C. Alexander, 1998)</p>
<p> </p>
<p>a stitch in time saves nine</p>
<p> </p>
<p>let's just pilot this....nothing bad can happen with a pilot</p>
<p> </p>
<p>everyone in the industry [or name of favourite competitor] is doing this ....</p>
<p> </p>
<p><a class="thought-link" href="brain://5UP_W-enTEespXpYiXFZ4g/References">References</a></p>
<p>14 May, 2019, 3:21 PM</p>