


Every day, the list of names and images grows longer. It used to be Columbine and Virginia Tech. Grainy video images of a high school student with an Uzi. Today it’s the University of Alabama. The Metro Station outside the Pentagon. An IRS building in Austin. Or the handwritten note found in the car of an aging factory worker who brought a gun to work on his 19th employment anniversary – and then used it to kill six of his colleagues and himself.
Rarely obvious to the reporters who cover these stories are the exciting advances at the frontlines of research into how such acts of targeted violence can be prevented within specific communities and environments – such as institutions of higher education (IHEs), large companies with thousands of employees, or entities such as taxing authorities or judicial departments whose mission or model places its stakeholders at elevated risks of being victimized by an aggrieved party or patron.
For those undertaking this research – university research departments, state and federal agencies, and law enforcement organizations with specialized protective missions – the challenge can be acute. That’s because, at its heart, targeted violence-related research focuses on some of the most difficult inputs to measure: human behavior and the potential for “dangerousness”.
As a result of seminal research on this issue undertaken by the U.S. Secret Service and the Department of Education over the last several years, we know that incidents of targeted violence share a critical characteristic in common: they’re usually the end-result of an “understandable and often discernable process of thinking and behavior”.1
In short, they’re not random, sudden or impulsive acts. What’s the implication for prevention? A “discernable” process is one we can identify and interrupt – particularly if we continue to learn more about precisely when, where and how to intercept the “pre-attack behavioral pathway”.
Here’s the rub. To result in findings that are accurate and actionable, targeted violence-related research initiatives must be highly effective at systematically capturing observations from multiple events in a logical and rationale manner. There’s only one best practice way to do that: develop a codebook.
A documented and standardized protocol for recording observations about phenomena of interest.
Defining and characterizing behavior can be open to interpretation and subjective opinion – a crucial outcome-determining challenge that can quickly escalate when multiple researchers and viewpoints are engaged.
Confusion can mount. Definitions of key terms can vary – or be interpreted differently. And both observers and researchers can easily and unconsciously pass inaccurate, inconsistent or inappropriate judgments on the behavior they are charged with cataloguing and analyzing.
When these errors and inconsistencies are allowed to occur at the beginning of the project they can, at minimum, skew key data, cause important data to be overlooked and generate false, misleading or incomplete findings. In some cases, they can undermine the entire project and tarnish the reputation of the study’s authors.
In short, a handful of crucial path-committing decisions early in the codebook creation process can either prejudice the project’s success right out of the gate or establish precisely the right platform to support and drive key study outcomes. These include:
To find out more about targeted violence and other behavior research in your business, contact:
1 Fein, R.A., & Vossekuil, B. (1998). Protective intelligence and threat assessment investigations: A guide for state and local law enforcement officials. Washington, DC: U.S. Department of Justice.
The Hillard Heintze 360° INSIGHT publication is an ongoing and regular series of executive briefings on a wide range of critical and emerging issues at the forefront of best-in-class security and investigative practices today.
Ensure that your code development team is highly knowledgeable and practiced in “hierarchical branching” – i.e., using a top-down approach to develop, pilot and refine codebook questions.
Even the slightest weakness in the definitions of variables can lead to a stream of unwelcome consequences emerging from variation in how the same behaviors are coded or interpreted differently by different researchers. And one more thing: take care to define different types of threats (e.g., direct, veiled, conditional).
First, your codebook must be valid, in that it measures what it was intended to. Second, it must be operationally relevant so that what it measures is of actual importance to sustainable behavioral assessment and violence prevention program activities “on the ground”. Many codebooks developed are inadequate because an academic does not have the right expertise or operational experiences to review criminal case files. On the flip side, many law enforcement agencies do not have the expertise to conduct accurate empirical research. Make sure your codebook development team brings both crucial skill sets to the initiative.