Discussion about this post

User's avatar
Wahidullah Noorzai | NIDA's avatar

This is a fascinating discussion, particularly because it raises a question that is often missed when security models travel across borders: what happens when doctrine leaves the environment in which it was originally developed?

From a field perspective, security is never simply a package of technology, training, intelligence procedures and institutional structures that can be transferred from one country to another.

The field changes the doctrine.

A surveillance system may work differently in India than in Israel. A counterterrorism doctrine developed in one political and geographic environment may produce completely different results when introduced into another. The same equipment can produce different outcomes depending on the organization operating it, the population among which it operates, the command structure, local knowledge and the legitimacy—or lack of legitimacy—of the security institution.

This is why I find the discussion of “fabrication” particularly useful. Security is not merely constructed at the policy level. It is continuously reconstructed through practice.

There is also a lesson here for counterinsurgency and policing. External expertise can provide tools, concepts and organizational models, but it cannot replace local understanding. The moment imported doctrine encounters the actual field, it is tested—and sometimes corrected by reality.

In my own experience, I have come to see this as a fundamental principle:

Field → Observation → Experience → Analysis → Principle → Doctrine → Strategy → Practice → Outcome → Feedback.

Doctrine that cannot survive this cycle remains theory.

Doctrine that enters the field and learns from its failures becomes something much more powerful.

That distinction is essential when we talk about the global circulation of security practices.

No posts

Ready for more?