Abstract
Intelligence-led policing (ILP) is a managerial law enforcement model that seeks to place crime intelligence at the forefront of decision-making. This model has been widely adopted, at least notionally, in the United States, United Kingdom, Canada, and Australia. Drawing on interviews with intelligence analysts from two Australian state law enforcement agencies, this article contributes to the relatively small body of literature that has examined ILP in practice. The article identifies three relational themes that inhibit the successful implementation of ILP: analysts and data, analysts and tools, and analysts and decision makers. Furthermore, it calls attention to the need to better understand the structure and operations within law enforcement agencies, including the similarities and differences among organizational units, in order to better understand how these nuances shape the practice of ILP.
Introduction
Intelligence-led policing (ILP) seeks to move from a “reactive” or “prosecution-directed mode” of policing to a more “proactive” style of crime prevention (Innes, Fielding, & Cope, 2005, p. 41; Innes & Sheptycki, 2004, p. 1). This involves a shift away from responding to individual incidents and “threats” in isolation to one that is future orientated and strategic in nature (J. G. Carter, 2013; Ratcliffe, 2016). ILP seeks to achieve this by placing what is often referred to as “crime intelligence” at the forefront of decisions concerning the prevention and control of crime (Guidette & Martinelli, 2009, p. 132; Ratcliffe, 2016, p. 89). 1 Under this model, crime intelligence should guide operations “rather than operations dictating intelligence-gathering priorities” (Ratcliffe, 2016, p. 6). While gaining momentum for some years prior to this point, ILP was widely adopted throughout the United Kingdom following the adoption of the National Intelligence Model (NIM) by the U.K.’s Association of Chief Police Officers in 2000. The NIM, in short, is a “business model” that takes an “intelligence-led approach to policing” (Belur & Johnson, 2016; James, 2013; National Centre for Police Excellence, 2005, p. 8) and in 2004, the U.K. Government legislated that all police forces in England and Wales were to have fully implemented the NIM by the following year. ILP has since been widely adopted in many countries including the United States, Canada, Australia, and New Zealand (J. G. Carter, 2013; Gul, 2009; Ratcliffe, 2016).
Crime intelligence or the intelligence process, more broadly, is often conceptualized in terms of ideal models. The most well-known of such models is the “intelligence cycle.” There are numerous versions of the intelligence cycle; however, they broadly follow the same six stages: planning, collection, collation and evaluation, analysis, dissemination, and feedback (Gill & Phythian, 2013; Warner, 2013). The most common criticism of the intelligence cycle is that the practice of intelligence is much more fluid than as it is depicted in the model. A further criticism is how it views intelligence in isolation, paying no consideration to the broader law enforcement environment in which it sits, including a failure to articulate how intelligence analysis is linked to decision-making. In contrast, Ratcliffe’s (2016) 3-I model seeks to clearly illustrate the role of intelligence within policing. The 3-I model is not necessarily a representation of how intelligence functions within law enforcement currently, but a depiction of how law enforcement organizations should function if they are to be truly intelligence-led. The 3-I model consists of three components (crime intelligence analysis, decision makers, and criminal environment) and three processes connecting these components (interpret, influence, and impact), creating a triangle (Gul, 2009). There are two main differences between the intelligence cycle and the 3-I model, and they primarily relate to the latter two “Is.” The first is the significance placed on crime intelligence analysts having an influence over decision makers. The second, in turn, is for decision makers to actually implement various initiates who do have an impact on crime. This is perhaps the most contentious component of this model and is a key difference from other models that often see the creation of an intelligence product and its dissemination as the conclusion of this process (Coyne & Bell, 2011; Ratcliffe, 2016).
Following the adoption of ILP, at least in principle, by numerous law enforcement agencies in the late 1990s and early 2000s, several studies have examined the use of intelligence analysis within policing (e.g., Cope, 2004; Darroch & Mazerolle, 2013; Ratcliffe, 2005; Sanders, Weston, & Schott, 2015). For example, Cope (2004) conducted a total of 38 interviews with intelligence analysts, research officers, informant handlers, and intelligence managers from both county and urban police forces in the United Kingdom. While it was clear that analysis as a tool for guiding police activity was generally accepted, a poor understanding of what intelligence analysis is among police officers and a limited understanding of policing among analysts had a negative impact on the usefulness of intelligence products. Cope (2004, p. 201) concluded that there is a “chasm between the theory and practice of intelligence-led policing and the current role of analysis.” In a similar study, Ratcliffe (2005) interviewed 50 decision makers and intelligence staff from New Zealand Police, finding that there was a perceived lack of understanding of ILP at senior levels of the organization. Concerns were also expressed about the appropriateness of the training intelligence staff receive and the quality and availability of data, which can significantly impact the practice of ILP.
A number of studies have also highlighted the numerous challenges with implementing ILP (Darroch & Mazerolle, 2013; Fyfe, Gundhus, & Ronn, 2017; Sanders et al., 2015; Sheptycki, 2004). Sheptycki (2004, p. 307) identified 11 “organisational pathologies” that “bedevil” law enforcement information systems, including the lack of interoperability, nonreporting and nonrecording of relevant intelligence, intelligence overload, information silos, and duplication. In a more recent study, Darroch and Mazerolle (2013) conducted a survey of 286 officers and 32 interviews with the members of New Zealand Police to identify the organizational factors, including changes in policy, procedure, training and leadership, that influence the adoption of ILP. Darroch and Mazerolle suggested that leadership is particularly critical to the adoption of ILP, noting that “where leadership lacked a critical mass or was deficient in the command structure, ILP [intelligence-led policing] innovation struggled” (p. 24). This is supported by a detailed examination of the implementation of the NIM in the United Kingdom, which found that opposition from senior commanders had contributed significantly to the NIM’s overall failure to have a “meaningful impact on operational practice” (James, 2013, 2014, p. 79). In a Canadian context, Sanders et al. (2015, p. 711) conducted 86 in-depth interviews and participant observation at six different police services, suggesting that these agencies had rhetorically adopted ILP but have translated “it to mean accountability in a time of austerity.” As Sanders et al. (2015, p. 722, emphasis in original) explained, “analysts are tasked with providing data to both justify current human and financial resources as well as illustrate the need for additional investment.” In other words, they have not actually implemented ILP but instead have translated it into an accountability tool for justifying their expenditures. Finally, it has been suggested by Fyfe et al. (2017) that implementing ILP will challenge the hierarchical chain of command in most law enforcement agencies due to its push for decision-making to be informed by crime intelligence. As such, for Fyfe et al., significant cultural change among police managers is essential for ILP to be successful.
While it is clear that ILP is widely adopted in theory, the extant body of literature illustrates that implementing it in practice is far from straightforward. Each empirical study highlights new challenges that seemingly limit the extent to which police organizations do in fact follow the principles of ILP. It is, furthermore, also evident that empirical research on ILP has not kept up with developments in policy and practice. For example, J. G. Carter (2016) observed that ILP has still received a relatively small amount of scholarly attention compared with others models of policing, such as community-oriented policing. Furthermore, Lewandowski, Carter, and Campbell (2017) suggested that the “nuances” within law enforcement agencies (e.g., cultural differences) are critical to our understanding of intelligence and require further study in a variety of contexts. Without continued examination, the risk, according to Ratcliffe (2016, p. 176), is that “it is easily possible for intelligence-led policing to fall by the wayside and become lost in the history of failed attempts of law enforcement to move away from the traditional focus on reactive, investigative policing.”
This study contributes to the extant literature by providing a detailed qualitative analysis of key impediments to the successful implementation of ILP from the perspectives of intelligence analysts. It draws on in-depth interviews with analysts from two Australian state law enforcement agencies, Victoria Police and New South Wales Police Force (NSWPF). We argue that although important changes have occurred, including greater recognition of intelligence and its value, it would be premature to state that they are truly intelligence-led organizations. In particular, it was evident that a great deal of diversity exists within law enforcement agencies that impact the practice of ILP in different ways. While the focus of this study is from an Australian law enforcement perspective, the findings have implications for all agencies that have adopted ILP.
The remainder of this article is divided into three sections. The first section outlines the methodology adopted for this study. The second section presents the core findings of this study that emerged from the interview data, focusing on three relational aspects that appear to inhibit ILP: analysts and data, analysts and tools, and analysts and decision makers. The third section discusses the main findings of the study, the implications for our understanding of ILP and areas requiring further research.
Data and Method
This article is a part of a larger project that examined intelligence and specific analytical tools within law enforcement. The project involves in-depth interviews with intelligence analysts from the two largest Australian state law enforcement agencies, Victoria Police and NSWPF. Victoria Police (2016) services a population of just under 6 million people across 237,639 km2, has a staff of approximately 17,000, and an annual budget of $2.51 billion (AUD). NSWPF (2016) services just over 7.6 million people across 800,642 km2, has a staff of approximately 20,500, and an annual budget of $3.47 billion (AUD). It should also be noted that law enforcement in Australia is state-based, meaning Victoria Police and NSWPF service not only large municipalities but also small regional towns.
A research proposal was submitted to the relevant committees from Victoria Police and NSWPF, outlining the objectives of the project, requirements from each organization, research conditions, and expected outcomes. Both committees approved the proposal and assigned a liaison officer to facilitate the initial contact with analysts. Purposive sampling was used whereby an e-mail containing the original research proposal was provided to each liaison officer, who then forwarded it to the intelligence analysts from their respective organizations. Initial response rates were low from both organizations (<10). A snowball sampling methodology was subsequently adopted whereby those who had responded were asked to identify any of their colleagues that they thought may wish to take part in the study (see Maxfield & Babbie, 2011). The result was the participation of 27 intelligence analysts: 17 from Victoria Police and 10 from NSWPF. The number of participants is comparable with similar studies in related fields (Chan, Brereton, Legosz, & Doran, 2001; Cope, 2004; Ratcliffe, 2005; Whelan, 2012).
Analysts came from a variety of units, with many having experience in both regional intelligence divisions that are primarily concerned with local crime, and specialist intelligence units/taskforces that are focused on particular groups (such as outlaw motorcycle gangs) or specific crime problems (such as drugs). The level of analytical experience varied among research participants, ranging from just 2 years up to 25 years. However, many had experience in other positions at their agency prior to becoming analysts, including as frontline officers (n = 19). There were also eight analysts in total who were “unsworn” (civilian) members of their organization. 2 As part of becoming an intelligence analyst, each participant had completed at least one internal analyst training program, with the more experienced analysts having completed multiple courses that had been updated over time (n = 19). Most interviewees had also undertaken a number of short courses (1–2 days) often focused on one software program or system. Twelve analysts had also obtained tertiary qualifications both outside their field (in disciplines such as political science) and directly related to intelligence analysis. It should be noted interviewees did not include those involved in non-intelligence roles, such as the collation of crime statistics, but are sometimes referred to as “crime analysts” or similar terms.
Interviews with Victoria Police analysts took place between September 2014 and January 2016 at general regional and metropolitan police stations. Interviews with NSWPF analysts took place over 2 days in December 2015 at their police headquarters and a metropolitan station. Interviews were semistructured and generally ran between 30 and 60 minutes. Each interview was audio recorded and transcribed, with a copy provided to each participant for their approval to ensure the accuracy of the transcript and to have the opportunity to redact any sensitive information that may have been inadvertently shared during the interview. In accordance with the research agreement with each organization involved in the study, participants remain anonymous.
Once the interviews were completed, the transcript was entered into QSR NVivo 11, where a thematic analysis was undertaken. A thematic analysis “is used to classify and organise data according to key themes, concepts and emergent categories” (Ritchie & Lewis, 2003, p. 220) and is “useful in capturing the complexities of meaning within a textual data set” (Guest, MacQueen, & Namey, 2014, p. 10). Each transcript was initially examined with a number of emerging broad themes or categories (e.g., “data”). Interview transcripts were subsequently re-examined and several subcategories identified (e.g., “data sharing”). While saturation occurred for select themes, particularly those associated with data and tools, this was not the case in relation to the need to better appreciate the difference between specialist units and the broader police intelligence division of labor (Sheptycki, 2017b).
There are limitations with the data and methodology applied in this study. Because participants come from only two state law enforcement agencies and the sample size is relatively small, the research is not necessarily representative. As such, generalizing from the findings should be undertaken with care. Although the focus of this article is on ILP at a state level, law enforcement agencies work extremely closely with security and intelligence agencies, particularly when it involves counterterrorism (J. G. Carter, 2013; Whelan & Dupont, 2017). In this study, federal law enforcement agencies are not represented, and nor are specialist units working with federal partners on these cases. As with all interviews, there is also a concern that there may be a difference in what participants say in any interview compared with what they truly think. Nonetheless, the data presented in this article provides valuable insight into the practice of ILP.
Findings
Three relational themes emerged from this study: analysts and data, analysts and tools, and analysts and decision makers. These themes represent core components of the practice of intelligence analysis and ILP.
Analysts and Data
Access to accurate data is an implicit first stage of the intelligence analysis process (Chan & Moses, 2017; NCPE, 2005). However, in line with the previous research (Ratcliffe, 2005; Sheptycki, 2004), interviewees identified a number of issues with their data, including incompleteness (e.g., missing data) and incorrectness (e.g., information entered incorrectly into their internal criminal databases). Several interviewees suggested that they will be inevitably working with incomplete data: We often work with very incomplete information, that’s what intelligence is. It’s not the CSI [Crime Scene Investigation—a television show] button, press one button and find everything out about everyone, that just doesn’t work. So limitations are what we’re able to see, what we are able to get, the information we don’t know, and that’s why it’s just an ongoing process . . . [W]hen you’re dealing with people that don’t want to get caught, it’s not as easy as picking up the breadcrumbs, often you can’t find stuff out, so that’s where its limited. When I talk intel [intelligence] or when we talk intel through what we do as analysts, it’s a grey area, it’s not black and white. . . . The issue with intel is to determine not only what you know but also what you don’t know. We really don’t have too much to base those assessments on. Using just the [name of internal criminal database] system which is only going to show people seen together at the same time, spoken to at the same time, somebody, some cop somewhere happened to think they were connected in some way. Sometimes the information that we have got to assess is not great, . . . just by looking at what we have, the information we have, it’s not really an accurate way of doing it. That’s [information sharing] something we are bringing up constantly. We don’t have established . . . networks within the organisation and also externally. There’s definitely silos [of information] which we are trying to break, . . . just having more open communication across all the different squads because there’s always overlaps, people try to hold onto their work. I think we need to work together a bit more.
A further issue is data or information overload. While there is usually a desire to have access to more information, this can also create a great deal of distraction: I think you can maybe bring in too much information, do you know what I mean? It would be great to bring in all this stuff [information] to do target profiles and know everything about him [offenders]. [But] on the other hand, it will actually bring in a lot of stuff that’s just not relevant to the investigator.
3
there is so much out there now and actually the sheer volume of having to go through it, because yes, you can go through it with your queries [database searches] but you still have to have a human element quite often to just sort of . . . put two and two together. One of the big new things is social media and you can look through peoples’ interactions on social media, depending on their privacy settings, but the problem with that is you might call it the Facebook friend. You might be able to see that someone has 200 friends on Facebook and you might be able to see that their Facebook friends with so and so, and you go, wow. But even from personal experience, you’ve got people that you interact with on social media, there are some people’s friend invites that you just accept because you don’t want to hurt their feelings, but other than that you sort of forget that they are even there, and that’s the problem with social media analysis, it’s very tricky to identify who is a true [friend]. . . . [I]t’s easy to overstate connections between people because we just don’t have the visibility into the quality of that connection.
Analysts and Tools
The “tools” or software and systems required to collect and analyze data were also perceived to be lesser than ideal by interviewees. For example, at the core of the data overload, issue discussed earlier is the capacity of law enforcement software and systems to assist analysts in analyzing growing quantities of data. Almost all interviewees, however, expressed a general concern about the systems available to them: We’ve got horrendous IT systems in [name of law enforcement organisation]. Technology changes daily and we’re still struggling to get information systems to work. They didn’t work when we got them, and we’re still struggling, and the pressure is put on the members. Suitable software that works, that doesn’t crash would be nice.
While software and systems might be regarded as separate from the training analysts receive, in the context of this study, it is evident that they are intrinsically linked. In a similar way to the extant literature (Cope, 2004; Ratcliffe, 2005), interviewees suggested that the training they receive for the software and systems available to them does not meet their needs. In particular, several analysts highlighted their frustration with the inconsistency with which training is available. As one interviewee explains, They [training programs] came in and out of vogue, and weren’t funded at different times. So sometimes we had the [software] licence but no funding for training, and other times there was no licence and no funding, and then at one stage there was. We eventually got to the point where we had licences and training funding, but the training funding was limited, so people had to get in quickly to get what they could. . . . I know there was a lot of angst years ago, when funding came for [name of software program], came and went, the system was available then it wasn’t available again. Then it was available with lots of training which was fantastic, then the training wasn’t funded so we had to run our own internal course and try and show people how we did it. I even think that we’ve got enough, dare I say, it’s always handy to have more human resources but I think we do have a large contingent of analysts out there that would be able to accomplish a lot more on a percentage basis if you gave them the right tools rather than just throwing more bodies at it. Throwing more human resources into things isn’t necessarily the answer and I think that seems to be a default quite often. So skilling them up [training] and giving them the tools that they actually require.
Analysts and Decision Makers
According to Ratcliffe’s (2016) 3-I model, there are many possible clients that analysts need to consider when looking to influence decision makers, including frontline officers (such as patrol officers and detectives), police leadership, regulatory agencies, the general public, and security networks. Interviewees, however, only identified two primary sets of decision makers: police leadership and detectives. 4
It has been suggested that positive working relationships—that is, those characterized by attributes such as mutual respect and reciprocity—lead to improved information sharing (e.g., D. L. Carter, 2009) and increased levels of trust (e.g., Schafer, 2010). In this study, analysts similarly suggested that their working relationships with managers and detectives are critical to achieving their objectives. Several analysts, however, suggested that their working relationship with intelligence managers is not always ideal. For example, one interviewee detailed the importance of what they perceive to be “good intelligence managers”: Having a good intel manager who can say look, that’s really not intel work, that’s busy work, why are you using trained intel’s [intelligence analysts] to do this when you could do that yourself or we could just get that information from anywhere. These guys have skills that should be used in a particular way. Your managers have to be the sorts of managers that can use intel effectively. . . . There are people who are no longer with the organisation who I think intels [intelligence analysts] will be spitting on their graves for the next 20 years to come. I think they [managers] understand its [intelligence] function, functionally where it fits in the process, they know they need the intelligence to advise them so they are better informed to make their decisions. . . . I think our managers have known it for a long time. But their ability to really understand how it works, they still think it’s a little bit of black magic and voodoo, still getting their head around it. I think they understand its [intelligence] importance, but no, they don’t understand it to the degree, again, largely because there probably hasn’t been that exposure to it from the time they start all the way through. . . . So I think there is a real disconnect in their own understanding of how intel works. So that’s something that I think needs to change over a period of time. We need to shift our thinking to that ILP and training from grass roots, pretty much all through our organisation. [Be]cause by the time they are at Senior Sergeant, Inspector level, they start to understand the tasking and coordination process and they know they need the intel [intelligence]. But until then, . . . I think there is a huge knowledge gap in our core element of policing, about their role and [the] function of intelligence. Your collaboration with an investigator is key to making the role of intelligence as successful as it can be. . . . So its providing that analytical support to basically, you know, the key objective of putting those people who’ve committed those crimes in jail through whatever means possible. . . . [I]t’s [intelligence analysis] to me, using everything that is at my disposal to give the investigator the ability to put that person inside. I know that in different squads there is different dynamics between teams. Some are more intelligence-led than others. The operational team that I previously worked with, it was very collaborative in terms of we [analysts] had a lot of financial data that they [investigators] didn’t have but they had a lot of surveillance and human source data. So it was combining those that allowed us to move forward and sort of show us what areas we needed to collect against and the same for them, what areas they needed to target. . . . So it needs to be collaborative. [At] the divisional CIU’s [Crime Investigation Unit] the relationships aren’t that good. It’s not that good with the detectives because they think what the hell do you know, get out. So it’s actually up to us to push our way into investigations. They will have debriefings and not even call us in, and then the boss says, what are you doing [analyst’s name]? Nothing because they’ve not come to me, they haven’t invited me in there, they can shove it up their ass, they’re not getting anything. Sounds silly but some squads you either get totally ignored by the detectives or you’re running around like the coffee lady, the tea lady. Sometimes they [detectives] don’t know what they want or they ask for things that aren’t possible to get. You’ve got a system that does X, Y and Z. No, it does Y, it doesn’t do Z, it doesn’t do X. I’m only generalising here . . . [but] detectives don’t know what we can do for them and that’s critical. And sometimes jobs come in and I go what the hell, you haven’t even come to see us, and yet we could have helped you solve this. Seriously, they don’t know what they can do with phones half of them because phones are a very complex thing. They don’t know about social networking, what we can get from there. There’s a distinction often lost, particularly in policing, . . . is the difference between intelligence and evidence. Intelligence is gathered by a number of means, may or may not be admissible as evidence in a court of law, but is intended to inform decision-making and not boost prosecution. Evidence has very specific laws under which it’s gathered so it can be admitted in court. A difficulty sometimes seen in law enforcement organisations is investigators confuse the two and are dissatisfied with its [intelligence analysis] outputs because they can’t use it in courts of law and they don’t see the value in them as a direction-finding mechanism. In my observation, it depends a lot on how many prior investigations the investigator has worked on where they were supported by an intelligence officer. Many [investigators] will have worked at local area commands on many investigations where they had no input from an intelligence officer or the input was limited to being more or less a data acquisition officer. . . . When an investigator in our area has had only that experience, their expectations, their understanding of what they can get from intelligence staff is different, it’s much more limited, they may commence by only consulting the intelligence officer when they have a data need that they don’t know how to fulfil themselves. Once or twice they might have seen charts of particular types of data . . . and they may see the value in that in presenting what they have learnt as part of a prosecution, but they are only consulting the intelligence officer when the investigation is more or less complete. . . . Then investigators who have been working in major crime and large-scale investigations for a long period of time have been exposed to more intel officers, often incorporate them in the internal planning of the investigation in seeking judgments about what the intelligence officer thinks about the . . . potential for targeting different members of the criminal group subject to the investigation; asking them to estimate the likelihood that they can develop from an intelligence process about certain facts being or certain situations existing or certain eventualities occurring.
Discussion and Conclusion
ILP has existed in theory ever since—if not, before—the introduction of the NIM (National Criminal Intelligence Service, 2000). Nonetheless, research has continued to demonstrate the many challenges involved in implementing ILP in practice, suggesting it continues to be more rhetoric than reality in policing organizations. Many explanations have been put forward as to the current state of ILP, including a poor understanding of what intelligence analysis is among police officers (Cope, 2004), various organizational pathologies (Sheptycki, 2004), and a lack of leadership (Darroch & Mazerolle, 2013; James, 2013). Research has also questioned the potential impact of “police cultures” (Chan, 1997; Whelan, 2016) in terms of resisting change and thereby a reluctance to move away from reactive or intuitive modes of policing (Belur & Johnson, 2016). In this study, we have focused on the impediments to the implementation of ILP, exclusively from the perspectives of analysts themselves. The main impediments to the effective implementation of ILP, as identified by analysts, fall under three categories: data, tools, and decision makers.
Data challenges have been widely acknowledged in the literature. In this study, interviewees concentrated on the accuracy of data (in terms of both incompleteness and incorrectness), the sharing of data (or information), and data (or information) overload. As Innes (2006), for example, notes, intelligence analysis is a field plagued with uncertainty, meaning many of the concerns regarding the accuracy of data cannot be fully addressed. However, it seems many of the issues raised by analysts relate in part to the data standards and practices within police organizations, suggesting at least some of these issues could be overcome with more rigor and scrutiny with regard to how data are obtained and recorded on police intelligence systems (see also Sheptycki, 2004). In terms of data sharing, interviewees repeatedly expressed their frustrations with regard to both the systems they have and their capacity to share information—including interoperability concerns—and the rules restricting how information and intelligence can be shared. In particular, analysts referred to a perceived lack of sharing between some organizational units (Giacomantonio, 2014), which reinforces the need to better appreciate the internal police division of labor (Sheptycki, 2017b). That is, while many have highlighted issues concerning the inter-organizational sharing of information (Whelan & Dupont, 2017), it is not the case that sharing information or intelligence occurs freely within organizations (Tsai, 2002). In this study, we even interviewed select intelligence analysts who were unable to share their products with their line managers because of these security classification requirements. Another interesting observation suggested by intelligence analysts is that, according to them, information overload is becoming a greater problem along with advances in technology but could not offer a solution to this issue. A prominent theme in the research on the rise of so-called big data (Chan & Moses, 2017; Cukier & Mayer-Schownberger, 2013; Sanders & Sheptycki, 2017), it appears the sheer growth in the volume of data is outpacing the capacity of analysts and organizations to meaningfully process and analyze it. What is clear, however, is that further efforts need to be directed toward organizational and technological improvements in the intra- and interorganizational coordination of police intelligence.
By tools, we have referred to the systems and software analysts have available to them to collect, analyze, and disseminate information and the training they receive to use such tools. As noted earlier, research on police databases and systems has repeatedly identified issues concerning the design and functionality of these systems (D. L. Carter, 2009; Ferrara et al., 2008; Sanders & Henderson, 2013). While we have identified many similar issues in this regard to the extant literature, our interviewees tended to lean more toward their perceived lack of training with regard to using the tools available to them. Analysts undertake an initial training course when they first join the organization (in the case of new members) or when they are first appointed as analysts (in the case of existing members), but interviewees referred more to limited opportunities for ongoing training. This lack of ongoing training is particularly problematic as tools change, including updates in existing applications (such as IBM i2 Analyst Notebook, which was used often by analysts in both organizations studied) as well as the introduction of completely new systems. Interviewees felt that the availability of ongoing training for many of these tools needed to improve. Interestingly, according to some analysts, they suggested that more training would produce better outcomes than more staff, which goes to highlight the significance of training as an impediment to intelligence analysis as a practice. As similar recent research has concluded (e.g., Belur & Johnson, 2016), better training for analysts and managers appears to be essential for organizations to truly implement ILP. Not discussed by interviewees, however, were the characteristics that are reportedly needed to be recognized as an effective analyst, including the ability to produce an analytical product, the overall attitude of an analyst (e.g., “can do” attitude), and individual attributes (e.g., confidence); all of which can inhibit the use of intelligence with law enforcement (Evans & Kebbell, 2012).
Influencing decision makers is a key component of ILP. We have concentrated on decision-making with regard to intelligence managers and senior police command and detectives or investigators working on specific cases. What is clear from both categories is that there is a great deal of inconsistency within law enforcement agencies when it comes knowledge of intelligence, including how it is produced and how it can inform decision-making. Interviewees repeatedly suggested that those managers with a greater understanding of intelligence were much more likely to appreciate its value and to therefore use intelligence as the basis of decision-making. In contrast, decision makers with a limited understanding of intelligence were more likely to, intentionally or unintentionally, marginalize analysts, including allocating them much less meaningful tasks. This understanding of intelligence largely comes down to the experience of each manager and detective in question, with interviewees repeatedly suggesting that some units are effectively much more intelligence led than others. Those who have spent time in more specialist units—including dedicated intelligence units as well as units dealing with organized crime and counterterrorism, for example—are much more likely to have a greater understanding of intelligence compared with those who have been limited to routine police operations.
Our analysis therefore suggests that in order to truly understand the role of ILP, we need to better appreciate how it is practiced differently within and between the many organizational units comprising police organizations. As Sheptycki (2017a) recently points out, conceptions of the “police métier” (Manning, 2010) and the formal and informal boundaries within policing organizations shape the function of intelligence in important ways. The vast majority of the extant research on crime analysis or ILP has focused on police organizations as a whole. This has led some to call for greater attention to be placed on the similarities and differences between police organizations (e.g., rural vs. urban police; J. G. Carter, 2013). We argue that there is just as great a need to look further inside police organizations to appreciate the similarities and differences between organizational units and the ways in which they shape the practice of ILP.
Footnotes
Acknowledgments
The authors would like to sincerely thank the anonymous reviewers for their critical input on an earlier version of this article.
