Solution-Oriented Practice
From theoretical architecture to local implementation. Because theory without implementation is just ambition, and implementation without theory is just activity.
What is solution-oriented practice?
Solution-oriented practice is a paradigm, not a programme. It rests on four foundational claims that, taken together, establish a fundamentally different way of understanding and producing community safety. Where conventional approaches define safety as the absence of crime and organise institutional effort around deficit management, SOP defines safety as the presence of conditions that enable communities to function well, and organises institutional effort around building those conditions.
This distinction is not rhetorical. It generates a different definition of success, a different knowledge base, a different unit of analysis, and a different relationship between institutions and communities. That is a paradigm shift, and the toolkit treats it as such.
The four foundational claims
How this toolkit is organised
The toolkit has two major sections. The briefing sets out the theoretical architecture: the four foundational claims, how they generate one another, and a worked example through Police Scotland that illustrates what the building blocks of solution-oriented community policing would look like. The playbook translates that architecture into an implementation framework structured in six parts, each grounded in one or more of the foundational claims, each producing specific outputs that feed into the others.
The playbook is not a manual. SOP cannot be reduced to procedures because the methodology requires communities to define what good looks like, and that definition will differ by locality, context, history, and aspiration. A manual would impose institutional categories on a process whose entire logic depends on those categories being generated from below. The playbook instead provides scaffolding: structural supports within which locally specific practice can develop.
1. An ontological claim: what safety is
SOP defines safety not as the absence of crime but as the presence of conditions that enable communities to function well. This distinction is foundational, because it determines everything that follows: what counts as success, what gets measured, where resources are directed, and what professional expertise is considered relevant.
The dominant paradigms in policing and community safety are organised around deficit. Problem-oriented policing identifies recurring problems and designs tailored responses. Evidence-based policing evaluates which responses reduce those problems most effectively. Both are valuable, but both define their object of inquiry negatively: safety is the successful suppression or management of harm. The logical consequence is that success is measured by absence (fewer crimes recorded, fewer repeat victims, fewer calls for service) and resources are directed toward locations and populations where that absence has not been achieved.
Prevention, too, remains deficit-oriented in its deeper logic. Even the most upstream prevention programme defines itself in relation to what it prevents. A violence reduction strategy aims to reduce violence. An early intervention programme aims to prevent offending. The orientation is still toward the negative outcome; the intervention simply moves earlier along the causal chain. Prevention shifts the timing of response. SOP shifts the orientation of the entire enterprise.
SOP asks a categorically different question: what conditions need to exist for this community to thrive? The answer might include stable employment pathways for young adults, accessible mental health provision, social networks that enable collective action, institutional responsiveness to community-identified priorities, physical environments that support connection rather than isolation, and trust between residents and the institutions that serve them. None of these are crime reduction strategies. All of them are conditions from which safety emerges.
The measurement implications are substantial. Crime statistics, fear of crime surveys, and reoffending rates are metrics of deficit management. They tell you how well the system is controlling negative outcomes. SOP requires a different measurement architecture entirely: indicators of community capability, institutional responsiveness, social network density, trust, collective efficacy, and the extent to which community-articulated visions of safety are being realised.
The resource implications follow directly. Deficit-oriented systems concentrate resources where problems are most visible. Hot-spot policing is the clearest expression of this logic. SOP would not necessarily disagree with the operational decision to concentrate police presence in high-crime areas, but it would argue that this is a response modality, not a safety strategy. The safety strategy asks why those conditions exist in those places, and what institutional design would need to change for the conditions that produce safety to emerge there.
2. An epistemological claim: how safety is known
If safety is defined as the presence of enabling conditions rather than the absence of crime, then the question of how safety is known becomes analytically prior to the question of how it is achieved. SOP makes a specific epistemological claim: that communities possess forms of knowledge about their own conditions that are not supplementary to institutional data but analytically foundational.
Institutional data systems in policing, health, education, and social services capture what those systems are designed to record. Police data records reported crimes and service calls. Health data records diagnoses and treatment episodes. Education data records attainment and attendance. Each dataset reflects the recording priorities and categories of its parent institution. What none of them capture is the connective tissue between these domains: how a failure in one institutional system creates consequences that appear as demand in another, how harm manifests in forms that no single institutional recording system is designed to see, and how the conditions for collective safety are experienced by the people who live within them.
Communities hold knowledge that is qualitatively different from institutional data. Residents know where people feel unsafe, even when those locations do not appear in recorded crime figures. They know where hidden harms are occurring: exploitation, coercion, and abuse that never enters reporting systems because the conditions for reporting (trust in institutions, belief that reporting will produce a helpful response, absence of fear of retaliation) do not exist. They understand how social networks function in their area, which relationships enable collective action, and which have broken down.
SOP argues that community intelligence is epistemologically prior to institutional data. It requires relational infrastructure (trust, legitimacy, sustained engagement) that enables communities to share their knowledge openly and systematically. Building and maintaining that relational infrastructure is not a preliminary step before the real work begins. It is the methodology.
3. A systemic claim: where the unit of analysis sits
The third claim establishes where SOP locates the unit of analysis, and it is here that W. Edwards Deming becomes properly foundational rather than merely invoked.
Deming's central argument, developed through decades of work in manufacturing, healthcare, and education, was that the overwhelming majority of variation in outcomes is attributable to the system rather than to the individuals operating within it. His frequently cited figure (that 94% of problems stem from the system) was a deliberate provocation against management cultures that blamed workers for systemic failures. But the underlying analytical point was precise: when a system produces predictable patterns of failure, the explanation lies in the system's design, not in the characteristics of the people moving through it.
Applied to policing and community safety, this reframes every major debate in the field. The question is not whether individual police officers exercise good or poor judgment, but what institutional design, training, incentive structures, and accountability mechanisms produce predictable patterns of organisational behaviour. The question is not why individual young people become involved in criminal enterprise, but what systemic conditions create the environment in which such involvement becomes a rational or available pathway.
Deming's System of Profound Knowledge
Deming's framework has four interrelated components, each of which maps directly onto what SOP is doing.
Appreciation of a system
Deming argued that optimising individual components of a system does not optimise the whole; it frequently degrades it. In policing, this explains why individual force-level innovations rarely produce systemic improvement. Each force optimises its own component without reference to the broader system. SOP insists on analysing the system as a whole: the interconnections between policing, health, education, housing, employment, and social services that together produce (or fail to produce) the conditions for community safety.
Knowledge of variation
Deming distinguished between common cause variation (built into the system) and special cause variation (attributable to specific, identifiable factors). Most variation in community safety outcomes is common cause: it arises from how the institutional system is designed. The concept of "cold spots" (communities where harm is occurring but invisible to institutional recording systems) is an expression of this principle. Cold spots are not anomalies. They are predictable products of a system whose data collection architecture creates systematic blind spots.
Theory of knowledge
Deming was sceptical of management decisions based solely on observable data, because data only captures what the measurement system is designed to record. This maps directly onto SOP's epistemological claim. Deming insisted that improvement requires theory tested through planned experimentation. SOP applies this logic: you cannot improve community safety by accumulating more data within existing recording categories. You need a theory of how the system produces its outcomes, and that theory must incorporate knowledge that lies outside institutional data systems.
Psychology
Deming meant understanding what motivates people and the conditions under which they do their best work. He argued that extrinsic motivation (targets, incentives, punishments) undermines intrinsic motivation and produces gaming rather than genuine improvement. Applied to community safety, this corresponds to SOP's concept of prosocial agency: the idea that communities possess the intrinsic motivation and capability to design their own safety futures when institutional conditions enable rather than constrain that capacity.
4. A methodological claim: how safety is produced
The fourth claim translates the preceding three into a methodology. If safety is the presence of enabling conditions, if communities possess the foundational knowledge about those conditions, and if the unit of analysis is the system rather than the individual, then the methodology for producing safety must begin with communities articulating their vision of what good looks like, and work backwards to design the institutional architectures capable of realising that vision.
This is reverse-engineering applied to social systems. It begins with the desired outcome (as defined by the community, not by the institution) and identifies the collaborative pathways, institutional interconnections, and systemic conditions needed to achieve it. The directionality matters. Conventional approaches start with a problem and design a response. SOP starts with a destination and designs a route.
Three modes of community engagement
SOP distinguishes itself from three related but distinct forms of community engagement, and these distinctions have practical consequences.
| Mode | Community role | Direction of design | Institutional function |
|---|---|---|---|
| Consultation | Respondent | Institution sets agenda; community reacts | Validates decisions already taken |
| Participation | Contributor | Community contributes within institutional framework | Incorporates community voice on institutional terms |
| Co-creation | Architect | Community generates knowledge, priorities, and vision | Provides resources and infrastructure to realise community vision |
Within this methodology, the concept of "cold spots" functions as a specific analytical tool. Hot-spot policing directs resources to locations where crime has been recorded at high levels. Cold spot analysis asks a different question: where are harms occurring but not being recorded? Where has trust broken down to the point that communities no longer report to institutions? Identifying cold spots requires precisely the kind of community intelligence that SOP's epistemological claim identifies as foundational.
How the four claims work together
The four claims are not independent propositions that happen to coexist. Each generates the next. If safety is defined positively (ontological claim), then knowing whether safety exists requires knowledge that deficit-oriented data cannot provide (epistemological claim). If the relevant knowledge includes community intelligence about systemic conditions, then the unit of analysis must be the system rather than the individual (systemic claim). And if the system is the unit of analysis and communities hold the foundational knowledge, then the methodology must begin with community-generated vision and reverse-engineer institutional design accordingly (methodological claim).
The practical consequence is that SOP cannot be implemented incrementally within existing institutional logic. You cannot graft a solution-oriented methodology onto a deficit-oriented system and expect it to function. The system's measurement architecture, accountability structures, resource allocation mechanisms, and professional incentives all reinforce the deficit orientation. SOP requires a corresponding redesign of institutional infrastructure.
SOP is distinctive not because any one of its claims is entirely new, but because the combination of all four produces a framework that none of the adjacent approaches, taken individually, provides. Asset-based community development shares SOP's emphasis on community strengths but does not make the systemic claim about institutional design. Public health prevention models share the upstream orientation but retain a deficit logic. Participatory action research shares the commitment to community knowledge but does not typically extend to institutional redesign.
A worked example: Police Scotland
Police Scotland provides an unusually productive context for illustrating what solution-oriented community policing might look like, for several reasons. The Police and Fire Reform (Scotland) Act 2012 establishes that "the main purpose of policing is to improve the safety and wellbeing of persons, localities and communities in Scotland." This statutory purpose already orients policing toward something broader than crime reduction, but "wellbeing" has never been defined in the legislation or in subsequent policy. SOP offers a framework that could give substantive content to that statutory purpose.
Scotland's institutional landscape includes Community Planning Partnerships, a single national force with 13 local policing divisions, and significant precedent through the Scottish Violence Reduction Unit. The six building blocks outlined in the briefing illustrate the scale of the undertaking:
Building block 1: defining what good looks like
The starting point is not "what are the problems here?" but "what would this community look like if it were functioning well?" This requires structured engagement with residents, community organisations, local businesses, schools, health services, and social work to articulate, in specific and situated terms, what the conditions for collective safety and wellbeing would look like. The output might include: young people have visible pathways into employment; people experiencing mental health crises encounter support before they encounter police; families dealing with addiction access services that respond to their expressed needs; neighbours know one another well enough to act collectively. None of these are crime targets. All describe conditions from which safety would emerge.
Building block 2: community intelligence infrastructure
A solution-oriented division would need to develop relational intelligence infrastructure: sustained, trust-based relationships between community policing officers, community organisations, and residents that enable the ongoing sharing of situated knowledge. This is not community engagement as currently practised (periodic, structured, institutionally led). It is a permanent relational architecture through which community knowledge flows continuously into institutional understanding. The distinction is between officers who collect information from communities and officers who create the relational conditions in which communities share their knowledge.
Building block 3: the system as the unit of analysis
This requires the division to analyse community safety as the output of an interconnected institutional system. A systemic analysis asks: what happened in the educational pathways of these young people that produced disengagement? What transitions failed or were absent? Are mental health services accessible? What employment pathways exist? The question put to the Community Planning Partnership is not "how can you help us address youth drug supply?" but "what institutional architecture would need to exist for young people in this locality to have viable pathways into adulthood?"
Building block 4: redefining the wellbeing mandate
Community wellbeing would be understood as the presence of the conditions from which safety and flourishing emerge: social connectivity, institutional responsiveness, collective efficacy, developmental pathways, and trust. A division might achieve significant reductions in recorded crime through enforcement while the underlying conditions for wellbeing deteriorate. Conversely, a division might invest in relational infrastructure without producing immediate crime reductions while the foundational conditions strengthen in ways that will produce safety over time. The measurement architecture must be capable of capturing the second trajectory, not just the first.
Building block 5: professional identity and capability
SOP requires a different professional capability: relational skills, systemic analytical skills, facilitative skills, and collaborative skills. It also requires community policing to be established as a specialist capability with its own professional development pathway and performance framework based on relational quality and contribution to collaborative system design rather than enforcement activity. The community policing officer shifts from a problem-solver deployed to a neighbourhood to a relational practitioner embedded within a community.
Building block 6: governance and accountability
A solution-oriented governance framework would need accountability to the community's articulated vision (not only to managing the problems that arise in its absence) and accountability for the quality of relational infrastructure. If community intelligence depends on trust, and trust depends on the quality of relationships between institutions and communities, then the governance framework should include mechanisms for assessing relational quality: community-assessed indicators of institutional responsiveness, longitudinal tracking of trust and confidence, and qualitative evaluation of whether community knowledge is genuinely shaping institutional decisions.
Before any solution-oriented work begins, the playbook requires an honest assessment of whether the conditions for that work exist. This is not a preliminary formality. It is the single most important determinant of whether the approach will function or be absorbed back into conventional practice within months.
Institutional readiness diagnostic
A structured instrument that senior leadership, governance bodies, and partnership boards use to assess whether the institutional environment can sustain solution-oriented practice. This covers governance flexibility (whether performance frameworks can accommodate non-deficit metrics), resource protection (whether community-facing roles are shielded from routine redeployment), leadership appetite for the discomfort that accompanies genuine system redesign, and the political landscape within which the work will sit. The diagnostic does not produce a pass/fail result. It produces a map of enabling conditions and constraints, allowing leadership to identify what needs to change before, or alongside, operational development.
Community trust baseline
An assessment of the relational starting point in each locality. Where trust in institutions has been damaged by historical experience, the playbook recognises that the first task is not vision-setting but trust repair. This component provides a framework for mapping trust topography: where trust is sufficient for co-creation to begin, where it requires sustained relational investment first, and where the damage is severe enough that attempting co-creation prematurely will reproduce consultation theatre.
Partnership landscape analysis
An assessment of the multi-agency system in the locality, covering which partners are present, how they interact, where statutory obligations create shared ground, where institutional cultures create friction, and whether the partnership infrastructure is functioning as a coordination mechanism or has the potential to become a genuine collaborative design space. The analysis identifies specific partners whose engagement is necessary for systemic work, and assesses their capacity and willingness to participate.
Constraint register
A candid record of what cannot be changed within the current operating environment, at least in the near term. Budgetary constraints, statutory obligations that pull toward deficit-oriented targets, political pressures, workforce capacity limitations, and partnership dynamics that resist collaborative redesign are all recorded. The purpose is not defeatism. It is clarity about the space within which the work operates, so that ambition is calibrated to reality and energy is directed toward what is actually movable.
The knowledge required for solution-oriented practice flows through relationships, not through institutional reporting mechanisms. Part two addresses how those relationships are built, sustained, and protected.
Role design for relational practitioners
Guidance on how community-facing roles are designed to support sustained relational presence. This covers geographic stability, workload protection, supervision arrangements, and the professional identity shift from problem-solver deployed to a neighbourhood to relational practitioner embedded within a community. This applies across agencies: community policing officers, community development workers, housing officers, health visitors, and other frontline practitioners.
Relational practice framework
A set of principles and reflective prompts for practitioners engaged in trust-building. This covers the difference between intelligence gathering (extracting information for institutional purposes) and relational knowing (creating conditions in which communities share their situated knowledge). It addresses how to be present in community spaces without instrumentalising that presence, how to navigate situations where community knowledge reveals harms that trigger professional obligations, and how to sustain relationships when institutional constraints prevent practitioners from responding in the way the community expects.
Community intelligence architecture
A framework for how community knowledge is received, recorded, synthesised, and acted upon. This is distinct from existing intelligence systems and from community engagement records. It describes a system through which situated, contextual knowledge flows continuously from community relationships into institutional understanding, while respecting the trust on which that knowledge depends. The architecture addresses consent, data protection, the boundaries between community intelligence and statutory intelligence obligations, and the governance of how community knowledge is used.
Cold spot identification methodology
A practical tool for identifying areas where institutional data shows low demand but community knowledge suggests unrecorded harm. This combines quantitative indicators (reporting rates significantly below what demographic and socioeconomic profiles would predict) with relational intelligence (what practitioners and community organisations know about where trust has broken down). The output is a composite map that overlays institutional data and community intelligence to identify localities where the system is not seeing what is happening.
Part three provides the framework for the co-creation processes through which communities articulate their vision of what good looks like. This is the operational heart of SOP, and it is also where the approach is most vulnerable to being collapsed back into consultation.
The distinction between consultation, participation, and co-creation
An operational guide to recognising which mode of community engagement is actually occurring, regardless of what it is called. The playbook provides concrete indicators for each mode, so that practitioners and communities can identify when a process labelled as co-creation has drifted into consultation, and what to do about it.
Co-creation process design
A flexible framework for facilitating community vision-setting. This is not a single methodology but a repertoire of approaches suited to different community contexts: large facilitated gatherings for localities with existing social infrastructure, smaller relational conversations for communities where trust is still developing, creative and participatory methods for engaging people who do not participate in institutional formats. The framework specifies core principles: community control of the agenda, genuine openness about what is possible and what is not, and a visible feedback loop showing how community-articulated visions are shaping institutional decisions.
Vision documentation and translation
Guidance on how community-articulated visions are recorded in ways that preserve their specificity and situated character while making them actionable for institutional partners. The risk is that rich, contextual community knowledge gets translated into abstract policy language that strips out everything that made it useful. The playbook provides formats that hold both: the community's own words and priorities alongside the institutional translation needed for partnership action.
Ongoing co-creation governance
Co-creation is not a one-off event. It is a sustained relationship. This component provides governance arrangements for ongoing co-creation: how communities maintain oversight of the vision they have articulated, how institutional responses are reported back, how the vision is revised as conditions change, and how the community exercises genuine accountability over the system that serves it.
Part four translates Deming's systemic claim into operational analytical practice. It provides frameworks for understanding how the institutional system produces its outcomes, and for redesigning that system collaboratively.
Institutional system mapping
A structured methodology for mapping the institutional system at locality level. This identifies which services are present, how they interact, where referral pathways function and where they fail, what data each holds, where recording categories create blind spots, and how thresholds and eligibility criteria in one service create demand in another. You cannot redesign a system you have not described.
Causal pathway analysis
A framework for tracing how institutional system dynamics produce the conditions that generate specific community-identified concerns. This draws on Deming's distinction between common cause variation (built into the system) and special cause variation (attributable to identifiable local factors). The analysis traces the pathway from system design to lived experience, identifying the specific institutional failures, gaps, and interactions that produce the outcome.
Collaborative redesign methodology
A framework for bringing systemic analysis to multi-agency partnerships and generating collaborative responses. This addresses how to present systemic analysis productively rather than accusatorily, how to move from diagnosis to design, how to allocate contributions across partners without defaulting to existing institutional boundaries, and how to maintain collaborative coherence when individual partners face competing pressures from their own organisational hierarchies.
Pilot design and learning architecture
Guidance on designing locality-level pilots that test collaborative responses while generating transferable learning. This includes how to scope pilots, how to protect them from being reabsorbed into conventional institutional processes, how to extract learning that is transferable without being falsely generalised, and how to feed that learning back into ongoing co-creation and system analysis work.
SOP requires a measurement architecture that captures what it defines as its outcome: the strengthening of conditions from which safety emerges. Part five provides the framework for developing that architecture.
Indicator domains
Five domains of measurement corresponding to dimensions of community wellbeing: social connectivity (the density and quality of relationships), institutional responsiveness (the extent to which services respond to community-identified needs), collective efficacy (the community's capacity to act together), developmental pathways (the availability of viable routes through education, employment, and social participation), and trust (the willingness of residents to engage with institutions).
Composite performance framework
A framework for combining solution-oriented indicators with conventional metrics. The playbook does not propose abandoning existing metrics. It proposes supplementing them so that governance bodies can see both: how well the system is managing deficit, and whether the conditions from which safety emerges are strengthening. The framework addresses how to present these together without the deficit metrics overwhelming the solution-oriented ones, which is the gravitational pull of existing institutional logic.
Community-validated measurement
A process through which communities validate whether the indicators being used actually capture what they identified as constitutive of safety. Institutional measurement systems are prone to measuring what institutions find convenient rather than what communities defined as mattering. This component provides a mechanism for communities to review and challenge the measurement architecture.
Longitudinal learning framework
A staged evaluation framework distinguishing early indicators of change (shifts in relational quality, community engagement, partnership functioning) from medium-term indicators (shifts in collective efficacy, institutional responsiveness, cold spot reduction) and longer-term outcome measures (progress toward community-articulated visions, systemic condition change). The early indicators must be credible enough to sustain institutional commitment while the longer-term changes develop.
The final part addresses how solution-oriented practice is governed, who is accountable to whom, and how the approach survives the personnel changes, political shifts, and operational pressures that routinely dismantle reform efforts dependent on individual champions rather than institutional architecture.
Dual accountability framework
Governance arrangements that hold the system accountable in two directions: upward to formal governance bodies and outward to communities whose articulated visions define what the system is for. Neither form of accountability is sufficient alone. Upward accountability without community accountability reproduces institutional self-reference. Community accountability without formal governance accountability lacks the structural authority to compel institutional change.
Protection mechanisms
Institutional mechanisms for protecting solution-oriented practice from the operational pressures that predictably erode it. These include formal agreements on community resource protection, governance-level commitments to evaluating the approach on solution-oriented criteria for a defined period, escalation pathways for when operational pressures threaten the relational infrastructure, and protocols for resolving competing demands between solution-oriented work and reactive operational requirements.
Institutional embedding strategy
A framework for moving solution-oriented practice from pilot to embedded institutional architecture. This addresses incorporation into planning cycles, partnership governance arrangements, inspection frameworks, and workforce development. The strategy recognises that embedding requires the approach to demonstrate sufficient value that governance bodies choose to sustain it, which connects back to the measurement architecture in Part five.
Succession and knowledge transfer
Arrangements for ensuring that the approach does not collapse when key individuals move on. This includes documentation practices, peer learning networks, mentoring arrangements for incoming practitioners and leaders, and governance mechanisms that hold the approach in place independently of individual commitment.
Cross-cutting elements
Three elements run across all six parts and cannot be confined to any one of them.
Reflexive practice
The playbook embeds reflexive prompts throughout: moments at which practitioners, teams, and governance bodies are asked to interrogate whether they are genuinely operating within solution-oriented logic or whether institutional gravity has pulled them back toward deficit orientation. These prompts are analytical tools for detecting when the approach is being co-opted by the very institutional logic it seeks to displace.
Power and equity
Co-creation involves a redistribution of power: from institutions to communities, from professionals to residents, from centrally determined priorities to locally articulated visions. Power is not redistributed simply by declaring it so. The playbook provides frameworks for identifying where power asymmetries persist within co-creation processes, how institutional cultures reproduce dominance even within participatory formats, and how historically marginalised communities can be centred without being instrumentalised.
Adaptation and contextualisation
The playbook is designed for local implementation, which means it must be adaptable to radically different contexts. A rural Scottish locality presents fundamentally different conditions from an urban English locality. The playbook provides the structural framework; the substantive content is generated locally. Each part includes contextualisation guidance that helps practitioners adapt the framework to their specific circumstances without losing the theoretical coherence that gives the approach its analytical power.
How the parts connect
| Part | Grounding claim | Primary output | Feeds into | Depends on |
|---|---|---|---|---|
| 1. Readiness | Systemic | Readiness map; constraint register | All parts | Leadership commitment |
| 2. Relational infrastructure | Epistemological | Trust baseline; cold spot map; intelligence architecture | Parts 3, 4, 5 | Part 1 (protected resource) |
| 3. Co-creation | Methodological | Community-articulated vision; ongoing governance | Parts 4, 5, 6 | Part 2 (relational readiness) |
| 4. Systemic analysis | Systemic | System map; causal analysis; collaborative redesign | Parts 5, 6 | Parts 2, 3 (intelligence and vision) |
| 5. Measurement | Ontological | Composite performance framework; staged evaluation | Part 6 | Parts 3, 4 (what to measure) |
| 6. Governance | All four | Dual accountability; protection mechanisms; embedding strategy | Sustains all parts | Parts 1, 5 (institutional conditions and evidence) |
The connections are not merely sequential. Parts two and three generate knowledge that may require revisiting Part one (the readiness assessment may need updating as the true state of community trust or partnership dynamics becomes apparent). Part four's systemic analysis may reveal that the community vision articulated in Part three requires institutional changes beyond what the current partnership can deliver, which loops back to Part one's constraint register. Part five's measurement development may surface tensions between what communities identify as meaningful indicators and what institutional data systems can support, which loops back to Part four's collaborative redesign work.
What the playbook must not become
The framework is incomplete without an explicit account of the failure modes it is designed to prevent.
A compliance exercise
If the playbook becomes a checklist that institutions work through to demonstrate they are "doing SOP", it has failed. Compliance-oriented implementation produces the appearance of solution-oriented practice while the underlying institutional logic remains unchanged.
A substitute for community voice
If the playbook's frameworks become the dominant structure within which community engagement occurs, institutional categories will have displaced community knowledge under the guise of enabling it. The playbook must hold its own frameworks lightly.
A policing-only tool
If the playbook is adopted by police services without corresponding engagement from health, education, housing, social work, and employment, it will produce a more sophisticated version of unilateral policing rather than the collaborative system redesign the approach requires.
A prescription that forecloses local specificity
The playbook provides structure. It must not provide so much structure that the locally generated content, which is the substance of solution-oriented practice, has no room to develop.
Development pathway
Framework validation
Review by a reference group including practitioners, community representatives, partnership leaders, governance stakeholders, and academic colleagues working on adjacent frameworks. The purpose is structural challenge: does the framework address what practitioners and communities actually need, and does it remain faithful to the theoretical architecture?
Component development
Each part developed in detail, drawing on existing practice, theoretical foundations, and reference group input. Components requiring new instrument development (the readiness diagnostic, cold spot methodology, community trust baseline, composite performance framework) are developed iteratively, with practitioner and community testing built into the process.
Field testing
Testing in at least two localities with contrasting characteristics (urban/rural, high trust/low trust, strong/weak partnership infrastructure). Field testing is not a trial of whether the playbook "works" in a summative evaluation sense. It is a developmental process that generates the learning needed to refine guidance, instruments, and process designs.
Publication and ongoing development
Published as a living document. Solution-oriented practice is developmental by nature; a static playbook would contradict the approach it describes. The publication includes mechanisms for ongoing revision based on practitioner experience, community feedback, and the accumulating evidence base from localities implementing the approach.
SOP Place Diagnostic
Place readiness assessment
For each statement, select the description that most honestly reflects where your locality currently stands. There are no right answers at any stage; the purpose is to map your starting point so that effort can be directed where it will have most effect.
Gap analysis
Outline project plan
Prioritised by assessed need and dependency. The six parts are interdependent: weaknesses in earlier parts constrain what later parts can achieve. Actions are sequenced accordingly.
Theory of change
This theory of change is generated from your assessment. It is iterative (each cycle reshapes the next), emergent (outcomes are shaped by the process), and systemic (change in one component alters the conditions for all others). The linear presentation below is a concession to readability, not a claim about how change works.
Export
Download as PDF report
Generates a formatted report containing the gap analysis, project plan, and theory of change. Uses your browser's print function; select "Save as PDF" as the destination.
Download as spreadsheet
Generates a CSV file containing all assessment scores, gap analysis data, and the project plan in tabular format. This can be opened in Excel, Google Sheets, or any spreadsheet application for further planning work.