Strategy Documents As User Manuals
Official strategy prose fails normal people when it reads like a sealed room. The book's answer is to read these documents as user manuals: what problem is the state naming, what behaviour is it assuming from the public, and what does it leave unexplained?
This module connects the existing pre-war pivot and deterrence pages to a practical reading method for citizens, founders, migrants, and technologists.
The Three-Pass Reading Method
- Pass one: extract the stated problems, not the rhetoric.
- Pass two: mark the implied jobs for citizens, firms, councils, universities, and investors.
- Pass three: list the unresolved questions and safeguards that remain open.
What Is Stated, Implied, Unresolved
The book's strategy chapter separates stated doctrine from inference. Stated doctrine includes whole-of-society resilience, higher spending ambition, defence as an industrial growth engine, and allied readiness. Implied doctrine includes civilian contribution, procurement reform, private-infrastructure hardening, and a larger role for dual-use firms.
Unresolved issues include implementation capacity, funding honesty, national-service debate, civil-liberties safeguards, and who pays to harden systems that are privately operated but publicly critical.
Plain-English Output
Every strategy page on defence.is should ideally end in a plain-English output: what a reader can understand, what a builder can build, what an investor can support, and what a citizen should keep asking in daylight.