From Diagnosis to Action

Begin with the problem, not the structure

A ministry should not begin by choosing a new unit, platform, or maturity target. It should begin by identifying the responsibility that is not being performed reliably and the binding constraint preventing it.

The same visible problem can require different interventions. Slow response may reflect unclear authority, insufficient staffing, secure-system failure, weak coordination, deliberate caution, or a combination of several constraints. A useful diagnosis separates them.

The Readiness Assessment

The Readiness Assessment is the method for applying the Capability Framework. It is not a public score and should not be used to rank institutions.

A ministry can examine each capability domain through evidence of:

Stated → Documented → Used → Tested → Improved

The progression is qualitative. It does not imply that every institution must move through identical stages or that a public observer can assign maturity from published documents alone.

The Institutional Capability Snapshot

For internal use, the assessment may produce a qualitative, non-comparative profile across the eight domains. It should identify: - the evidence available - the primary bottleneck - the binding constraint - the consequence of inaction - what can be improved with current resources - what requires a leadership decision - what requires investment - what must be tested

A public country profile should continue to use evidence classifications rather than a maturity label. A private institutional assessment can use a qualitative snapshot when it is supported by internal evidence and practitioner participation.

Four action categories

Recommendations should state the category clearly. A report that disguises an investment need as a 'coordination improvement' is not useful.

Three organisational models

The organisational model should follow the capability required. The models are not maturity stages and do not imply that a larger structure is automatically better.

Model 1 — Lean

The Lean model establishes a small, clearly owned capability through existing structures. It may include one senior sponsor, one operational lead, a substitute, a limited mission and cross-functional focal-point network, access to specialist support, and a light operating rhythm.

The Lean model may be suitable when the ministry is small, the capability is emerging, resources are limited, or the immediate objective is to establish a dependable route without creating a large permanent structure.

Its principal risk is fragility. The model can become an unfunded focal-point network, depend on one person, or lose momentum when the sponsor changes.

Minimum Lean outputs include one mandate, one owner, one mission route, common evidence language, one scenario exercise, a short risk and dependency record, and one verified improvement.

Model 2 — Modular

The Modular model creates one operating system from several centres of expertise. Modules may include public diplomacy and strategic communication, cyber and security, AI and data, consular and crisis functions, technology diplomacy, legal and procurement, regional directorates, and mission representatives.

A small central cell maintains the common architecture: mandate, standards, mission connection, shared evidence, operating rhythm, exercises, and learning. Expertise remains in its existing organisational home.

The model may suit a ministry with several established specialist functions that need stronger connection. Its risk is coordination without authority: the central cell may be responsible for coherence and unable to resolve gaps.

Model 3 — Directorate

The Directorate model treats digital-era diplomatic capability as a continuous institutional responsibility with permanent staff, specialist depth, mission support, governance, exercises, implementation, and learning.

It may be suitable where the risk, scale, diplomatic network, technology dependency, or volume of activity requires sustained capacity.

Its risks include over-centralisation, expansion of remit, duplication of existing functions, confidence based on structure rather than performance, and distance from mission reality.

Choosing the right model

The right model is the smallest sustainable structure capable of governing the complete responsibility.

The model should earn permanence through demonstrated use. A new directorate should not be created merely because the framework contains eight domains.

Workforce capability

Capability should not be reduced to new job titles. Most ministries already contain relevant knowledge across diplomats, locally engaged staff, communicators, consular officers, policy planners, cyber and security specialists, legal advisers, data and technology teams, procurement, and diplomatic academies.

The workforce question is which responsibilities require specialist depth, which skills should be distributed, and which functions should be accessible through central or regional support.

Capabilities that should be broadly distributed: - evidence and uncertainty discipline - basic digital and platform literacy - recognition of manipulation and impersonation - safe and approved AI use - mission–headquarters reporting and escalation - protection of official identity and sensitive information - understanding of delegated authority and correction

Capabilities that may require specialist access: - digital forensics and provenance analysis - advanced open-source and network analysis - AI assurance and data governance - cybersecurity and identity recovery - platform and provider engagement - scenario design and institutional evaluation - legal and procurement analysis

A small mission should know how to reach specialist support and what response time it can expect. It should not be expected to maintain every specialist function locally.

The first 90 days

The first 90 days should establish a credible baseline, not complete a digital transformation programme.

Days 1–30: Map and assign

• Name a senior sponsor, operational owner, and substitute.

• Choose one narrow but consequential responsibility or scenario.

• Map the real signal-to-decision route across headquarters and selected missions.

• Identify current roles, informal workarounds, individual dependencies, critical systems, and missing support.

• Reconstruct one recent incident or difficult workflow.

• Identify the first red flags across capacity, authority, infrastructure, coordination, and risk appetite.

The first month replaces institutional assumptions with an evidence-based starting point.

Days 31–60: Define and connect

• Approve a short mandate and scope.

• Select the smallest viable organisational model.

• Define common evidence, uncertainty, and priority language.

• Clarify standing, time-sensitive, shared, and senior decision rights.

• Create one mission signal note and one decision record.

• Review one important AI or external-system use case.

• Create a critical dependency and continuity map.

• Design one realistic mission–headquarters exercise.

The second month turns dispersed capability into a minimum connected operating model.

Days 61–90: Test and commit

• Run the exercise using real roles, channels, time pressure, and authority.

• Record what happened, what helped, what weakened, and which constraint was binding.

• Identify one primary Conversion Deficit bottleneck.

• Agree a short action plan with owners, deadlines, resource requirements, and a retest.

• State what will be deliberately postponed.

• Decide whether the next step is process change, leadership action, additional capacity, infrastructure investment, or a combination.

The final month replaces confidence based on intention with evidence based on institutional use.

What should exist by Day 90

• one named responsibility and owner

• one real process map

• one mission–headquarters authority map

• one common evidence and uncertainty language

• one critical dependency and continuity record

• one completed exercise

• one primary bottleneck statement

• one short implementation plan

• one date for retesting

What should remain outside the first 90 days

• a comprehensive technology replacement programme

• a new directorate unless the evidence clearly supports it

• a universal training campaign before roles and workflows are clear

• a public maturity score

• an attempt to map every minor digital activity

• a declaration that the capability is fully operational because the project ended

Common implementation failures

The DD Field Kit 2026

The companion Field Kit translates the report into six practical, editable tools:

Canonical launch status for all six tools: Public beta · v1.0 · Free and editable · Released for practitioner testing. Canonical names are fixed as listed above; future revisions change the version number, not the asset name.

The tools should be free, versioned, citable, and available in editable formats. Their usefulness is not assumed. It must be tested with practitioners and revised after use.

The central proposition

Diagnosis becomes capability only when the institution chooses a proportionate action, assigns authority and resources, tests the arrangement, and verifies that something changed.