23.11.2012 Views

Technical b r Report - International Military Testing Association

Technical b r Report - International Military Testing Association

Technical b r Report - International Military Testing Association

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

II<br />

When given the requirement to propose Human Factors-Behavioral Science<br />

research for the coming year, we are faced with a soul-searching situation<br />

in which we must ask ourselves two questions: one, are we really getting<br />

the taxpayers' dollar benefit from the work that has transpired in the past;<br />

and, two, will the research we are asking for be likely to yield productive<br />

results in the future. Another question which also must be scrutinized when<br />

it surfaces is, if we aren't getting a masimum return on our investment in<br />

research, how can KC, as trainers and managers, translate the results of<br />

future research into better returns on our investment dollars? First of all,<br />

d it is not purely 3 translation problem. The process of bridging the gap<br />

between the ccnduct of rcscarch and the implementation of rcscarch, by the<br />

Army trainer, is a continuing one. It begins while the problem is being<br />

defined to both the researchers and the trainers; it continues during the<br />

conduct of the research; it continues while the final report is being<br />

drafted, and it- still continues long after the final report has been published.<br />

Let's b:Rin at the beginning. In avery real sense, utilization begins at<br />

-.<br />

the time tl~c probla to be researched is presented. The training problem must<br />

be carefully defined and documented to insure that both the researcher and the<br />

trainer arc speaking the same language and that the researcher fully understands<br />

the problem that the trainer believes he has. After the trainer submits his<br />

request for rcscnrch, the researcher must then submit a statement to the<br />

trainer on what he views the problem to he and how he intends to seek out the<br />

solution. A common understanding and agreement of the problem to be researched<br />

is essential if a usable end-product is to be the result. The research approach<br />

may have to be modified in the light of continuing support requirements. somctimes<br />

it may have to be recast if the research proposed is not understood by<br />

the trainer to be appropriately responsive to the problem as hc perceives it.<br />

Constant inter&tiodbetween researcher and trainer takes place during the<br />

conduc: of the work. Cor;lmunication is achieved informally on a continuing<br />

$asis through -he USC of interim progress reports, periodic reviews, briefings,<br />

and discussions. The, trainer requesting the research must be kept ccjnstantly<br />

aware of the work taking place_, and the researcher must be kept abreast of<br />

significant military changes within the parameters of training problems. Hopefully,<br />

the interaction and open ccxzmunication will keep the evolving solution<br />

directly aligned with the trainer's problem.<br />

As relevant data becomes available, that is, data which bears upon the<br />

problem, it is provided to the trainer. Such coarmunication involves both<br />

those management functions which can implement cl,ange and those responsible<br />

for actually carrying out the drcision to make the change. Management, simply<br />

dccrccing that change ie made, will not, alone, get the job done; the “notinvented<br />

here” syndrome must be overcome. The "doer" --t!re guy at the working<br />

level--must be convinced t.hat the change is good and that it will be of benefit,<br />

not only to himself, but to the prospective students and to the system, othcrwise<br />

it will be doomed to failure.<br />

97<br />

, : ._<br />

.: .<br />

2

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!