Doctrine 08 — Tools Change, Concepts Don't
One durable concept: the doctrine lives above the software, and software is the least durable thing in this course.
This is the most important doctrine in the folder, and the most unusual. Every other doctrine teaches you something that will still be true in twenty years. This one teaches you how to know what will still be true in twenty years — and how to stay calm about everything else.
The two layers
Everything in this course lives in one of two layers:
Layer one: the durable concepts. Where the government money lives (Doctrine 01). How solicitations work (Doctrine 02). The shape of the pursuit pipeline (Doctrine 03). The discipline of gates and governance (Doctrine 04). The arithmetic of scoring and pricing (Doctrine 05). The ORBITAL skeleton (Doctrine 06). The Dream → ORBITAL → World lifecycle (Doctrine 07). These are ideas. They change slowly — over decades, if at all. A 1980s capture manager and a 2040s capture manager would understand each other instantly.
Layer two: the tools. The software that holds the records. The portals where solicitations are announced. The AI systems that draft proposals. The specific websites, product names, and interfaces. These change constantly — every few years, on a good day. The tools in use today will be museum pieces by the time you are mid-career.
The core rule of this course: we teach layer one, and we only mention layer two as examples. You will never be tested on a tool. You will be tested on the concept the tool happens to serve at the moment.
Why this is the honest way to teach it
Consider what happens if a course teaches the tools. Every year the course fights the software: the screenshots are stale, the product changed names, the company folded, the interface moved. The students learn a version of reality that no longer exists by the time they graduate. The tools consumed the course.
Consider what happens if a course teaches the concepts. The course is stable. The students graduate with a mental model they can drop onto any tool — the one in use today, the one invented next year, the one they themselves will help build. When the tool changes, nothing about their knowledge breaks; they simply re-map the concept to the new tool. That is the definition of a durable education.
This matters even more for AI. The wider doctrine this course mirrors is now partly encoded in machine-readable form — an AI layer that reads the doctrine and helps draft proposals, score pursuits, and run gates. If the course taught you the machine's file formats, the course would be obsolete with the next version. Instead, the course teaches you what the machine is trying to encode: the concepts. When the AI layer improves, the concepts are still what they are. You will be able to understand what the machine is doing — and judge whether it is doing it right — because you know the doctrine beneath the tooling.
The durable facts, stated plainly
Let us be explicit about what survives, because the whole course rests on it:
- The market. Congress appropriates; agencies spend; the money is public and published. SAM.gov, Grants.gov, the UEI/CAGE/NAICS identifiers, the small-business programs — the institutions endure even as the websites and interfaces change.
- The documents. Agencies will always publish their needs and their rules in advance, and the winner will always be chosen on published criteria. RFP, NOFO, RFI, task order — the names may shift, the posture will not.
- The shape. Pursuits will always pass through some version of sense → qualify → score → pursue → design → audit → submit → deliver → learn, with gates between. The pipeline is the shape of disciplined work, and disciplined work does not go out of style.
- The structure. Every serious pursuit will always need a skeleton with an objective, resources, budget, indicators, a route, activities, and conditions — whatever the ORBITAL is called in whatever system of record holds it.
- The lifecycle. Ideas will always need to be structured before they can gain momentum, and momentum will always compound into entities. Dream → ORBITAL → World is the growth story of everything.
None of these depend on a product. That is what makes them doctrine.
What changes, and why that is fine
What changes is the plumbing: the portal where you submit, the record system where the ORBITAL lives, the AI tool that drafts the first pass, the analytics that estimate pWin. New tools will arrive that are better, faster, cheaper, and more automated. That is good news, not a threat. Every tool improvement is leverage on the same concepts — the concepts do not get harder, the work gets easier.
The professional posture is simple: learn the concepts once, deeply. Learn each tool only as deeply as the job needs, and expect to re-learn it. The person who confuses a tool for the doctrine will be stranded by the next release. The person who knows the doctrine will simply adopt the new tool and keep going.
The one thing that must not change
The doctrine is the shared language between the human side and the machine side of this discipline. When someone says "gate," "pWin," "ORBITAL," or "color team," every part of the organization — human and machine — must mean the same thing. That is why this course is paired with a machine-readable encoding of the same doctrine: not so you can read the machine's files, but so you can trust that the machine and your professor are teaching the same concepts.
So when a tool changes, the doctrine does not get rewritten. The mapping between the doctrine and the tool gets updated — quietly, in the alignment layer — and the course goes on. Concepts are the language; tools are the accent.
What this means for your career
You will spend your career surrounded by rapidly changing software and a few very stable ideas. The people who rise are the ones who can tell them apart. When you interview, the ability to say "I understand the pipeline and the gates; let me learn your system for holding them" is worth more than familiarity with any specific product. The concept is portable; the tool is not.
For the MBA student: the durable asset is the business structure and the market, not the software stack you happened to use. For the MPA student: the durable asset is the public money flow and the rules, not the portal du jour. For the Strategic Initiative student: the durable asset is the doctrine itself — the thing worth encoding, worth teaching, and worth protecting.
Self-check
- What are the two layers of this course, and which one do we test on?
- Name three durable facts from this doctrine that will still be true in twenty years.
- When a tool changes, what gets updated and what must not change?