Developing the HFI Social & Organisational Domain: Final Report

More documents

Recommendations

Info

HFIDTC/2/WP2.18/3Version 2/14th May 2009comprised land and air representatives from Permanent Joint Headquarters (PJHQ) and arange of industry representatives were identified following a presentation at a MoD-Industry HFI Working Group meeting. Other reviews were undertaken by Dstl OAresearchers (DG Scrutiny P&P), DE&S Human Factors Group and representatives fromthe Defence Academy.3.3.3 MethodFollowing the presentation made at the MoD-Industry HFI Working Group meeting,potential participants and interested parties were identified. They were emailed and askedto participate and this was followed up with a telephone call to discuss the type and levelof involvement required. Other MoD participants were identified from earlier stakeholdercontacts and with the support of the HFI DTC military advisor at Dstl. Those who wereable to participate within the project timescales were emailed a briefing pack thatcontained the following documents:• Briefing note• SOF background information• Instructions for SOF framework review• SOF framework slideshow• Participants were also made aware that the full SOF framework was available inExcel formatSuitable times were then arranged for participants to discuss their feedback either byemail report, telephone conference or face-to-face meetings depending on the time theparticipants had available.3.3.4 Key findingsThe findings are divided into two main areas: 1) relating to the technical content of theSOF and 2) related to application and processes for use.3.3.4.1 Content issuesSub-domains and elementsIt was generally agreed that the detailed level of the framework was a useful repositoryfor associated tools and resources. Some suggestions were made relating to the detailedinformation about sub-domains and elements. The main issues raised were:• The heuristics and characteristics should be re-framed as questions or should simplybe headings.7
HFIDTC/2/WP2.18/3Version 2/14th May 2009• The change management sub-domain should sit vertically across all elements andprovide a means to address the identified issues in the other elements.• The SOF framework tool that contains the more detailed layer of information is onlylikely to be used by those familiar with HF.• The framework tool will require regular review and updates to information based oncurrent research and thinking.Presentation of SOFThe briefing pack materials provided to stakeholders used a PowerPoint slideshow toallow the participants to work through the information. It was highlighted to participantsthat this would not be the final implementation of the material. However, it is recognisedthat whatever format the final implementation takes it must be accessible to a wide rangeof stakeholders and it must follow good usability principles (e.g. navigable, consistentetc).• Stakeholders agreed that the SOF needs to be layered to provide different levels ofinformation to different users. In the first instance the SOF should be a list of corequestions that can be answered by a non-HF specialist. Fundamentally the SOF needsto be simple and straightforward and appropriate for someone with little backgroundor experience of HF or HFI.• Background information is required up front to explain HFI and how SOF fits withinit.ExamplesIt has always been recognised that examples and case studies would be important toillustrate the key points within the framework. A few examples were provided but mostparticipants felt they contained a degree of sensitive information that would make themunsuitable for release into the public domain.• Further work could be undertaken to turn these potential examples into genericexamples.• Other suggestions from stakeholders included:- Examples could also be provided about how each element links to operationaleffectiveness.- A portfolio of worked examples for different types of scenario could be provided.3.3.4.2 Process and application issuesLinks and hooksFor the SOF to be workable it has to have formal and recognised ‘hooks’ and ‘links’ intoother processes and documents. There are potential ‘hooks’ to integrate the SOF withinthe acquisition process and for other activities a ‘generic’ SOF process is proposed thatcan be customised by each stakeholder group (e.g. IPT, personnel, individualcontractors).8
Page 1 and 2: Developing the HFI Social & Organis
Page 3 and 4: HFIDTC/2/WP2.18/3Version 2/14th May
Page 11: HFIDTC/2/WP2.18/3Version 2/14th May

Developing the HFI Social & Organisational Domain: Final Report

Create successful ePaper yourself

Delete template?

Save as template?