Valid selection of tool
<h2>Valid selection of HF tools</h2>
<p>Stanton and Young 1999 provide a decision guide (iterative and closed loop in nature) for selecting from the vast number of tools. The key questions seem to be understanding criteria for anlaysis [what do i need here?]; assessing the pool of methods against the criteria (e.g. by domain of methods) [What can I use here?] and then validating the assessment process based on the output analysis [Did it do what I needed it to do? Can I use the results?].</p>
<p> </p>
<p>I suggest answering the questions provided in the link below will provide you with a good guide on whether HF professional skills are indicated and what sort of approach might be needed.</p>
<p>Then consider best and good practice examples to benchmark your approach. </p>
<p>Then follow any internal organisational processes or checklists.</p>
<p> </p>
<p>This way you won't prematurely narrow your options and constrain what you are looking and through which lens.</p>
<p> </p>
<p>It doesn’t take long to put these questions to the project or design team and reflect.</p>
<p><a class="thought-link" href="brain://l-nXVSj9fUOr6YF0Z5X5pw/QuestionsToAskSelectionOfMethods">Questions to ask - Selection of Methods</a></p>
<p> </p>
<p>If all else gets too hard, keep it simple - start with a basic tool (e.g. data collection or observation, worker consultation, process charting) and then build up the information base with other tools or deeper analysis as you learn more about <em>what you need to know</em> and <em>where you don't know stuff that you should</em> (i.e. knowledge gaps) and <em>where you think you know but you might not be right</em> (e.g. biases, blindspots).</p>
<p> </p>
<p>Take due diligence to ensure you <em>know what you need to know </em>and<em> understand what it is telling you.</em></p>
<p>14 May, 2019, 3:43 PM</p>