Wolf Schoettner

He traces the OODA loop to U.S.

• Air Force Colonel and fighter pilot John Boyd and his work on air combat, then breaks it into Observe, Orient, Decide, Act and shows what each join is worth on its own: data, analysis, a presentation, or blindness.
• He applies the loop to aerospace and defense, where complex programs, demanding qualification requirements, multiple stakeholders and long lead times leave little room for unnecessary delay.
• His conclusion is that closing the loop faster creates advantage while the information still matters, with the qualification that not every decision needs to be rushed.

The compressed chains in the post, "Observe without Orient = data.

• Orient without Decide = analysis.
• Decide without Act = PowerPoint.
• Act without Observe = blindness," followed by the closing question about where an organization loses the most time: Observe, Orient, Decide or Act.

The two posts carry almost the same body text, so this is one repeated position rather than a developing one; one version adds a short list of substitute activities such as another meeting or another approval loop.

Read original · Original 2

Wolf Schoettner distinguishes four things that are often mixed together: a market signal, an opportunity hypothesis, a qualified opportunity and a committed pursuit.

• Mixing them, he argues, makes a pipeline look impressive while management cannot see where evidence ends and optimism begins.
• Moving an opportunity forward requires evidence in five areas: the customer (defined operational need, clear decision process, realistic timing, credible funding path), the market (accessible demand, program landscape, procurement route, competition), the solution (a credible contribution within a wider system), the position (a meaningful differentiator, customer access, the right role in the value chain, and whether partnering beats competing alone) and execution (ability to qualify, industrialize, deliver and support).
• Missing evidence is permitted, but it must be visible, assigned and connected to a specific next action, with business development, sales, engineering, operations and finance working from one shared view.
• The decision that follows is explicit: validate, shape, pursue, partner, pause or stop.

The rule that unanswered questions must be recorded, owned and tied to a next action rather than resolved by optimism, and the closing choice list ending in "or stop".

Read original

Wolf Schoettner sets out a five-stage cycle: customer insight, focused pursuit, aligned commitment, reliable delivery and compounding trust, after which the cycle starts again from a stronger position.

• In aerospace and defense, he argues, growth is rarely a sequence of isolated transactions: programs create relationships, operational insight, qualification experience, industrial capability and trust, each of which can reduce friction on the next pursuit.
• He keeps the existing tools rather than replacing them, assigning the funnel to conversion, the pipeline to tracking current opportunities and the flywheel to how customer outcomes create cumulative advantage.

The summary line, "A flywheel gains momentum when delivery feeds learning, and learning shapes the next opportunity," and the stage-by-stage example of compounding trust producing repeat business, lifecycle value, partner preference and access to future programs.

Read original

Wolf Schoettner draws these points from the International Institute for Strategic Studies assessment of NATO logistics, which he names and links in each post; the figures and examples below come from that external source, with his own commentary around them.

• Movement comes first: in an Article 5 contingency up to 800,000 NATO troops with equipment, ammunition and supplies could have to transit Germany within 180 days, and the bottlenecks include rail capacity, road-weight limits, bridges, borders, signalling systems and different rail gauges.
• A second post separates logistics capacity from logistics survivability: large-volume movement has been demonstrated, but largely from rear areas without the persistent interdiction, electronic warfare and precision strikes a high-intensity conflict would bring, and railheads, fuel points, field hospitals and ammunition transfer points concentrate materiel and cannot easily disperse.
• A third looks at fuel infrastructure, arguing that the pipeline architecture was built around different Cold War requirements and does not extend far enough into today's eastern flank, so announced long-term construction does not close a near-term readiness gap.

The rail gauge mismatch: most of Europe runs on 1,435 mm while Lithuania operates largely on 1,520 mm, so a military train moving from Poland toward the Baltic states cannot simply continue on the same infrastructure, with the standard-gauge Rail Baltica connection assessed as complete no earlier than 2030. His framing of the question is "Can we keep delivering while someone is actively trying to stop us?", and his summary of fuel logistics is that procurement creates assets, infrastructure creates access, and logistics creates operational effect.

The emphasis shifts across the three posts from movement capacity to the survivability of supply routes to the timing gap between investment and usable capability, while all three return to the same underlying report.

Read original · Original 2 · Original 3

Part one covers what he calls the legal gate: product classification (military equipment, a controlled dual-use item, or a war weapon, with German rules such as the AWG, AWV and KrWaffKontrG as examples), export controls including EU Dual-Use Regulation 2021/821, sanctions, end-use restrictions, authorisations and, where U.S.-controlled items are involved, ITAR and EAR, then security and information handling, ownership of compliance responsibility, and delivery qualification.

• Part two covers the delivery gate: quality management requirements (ISO 9001, EN 9100, AQAP), military specifications such as MIL-STD-810 and MIL-STD-461, qualification and approval frameworks including EMAR and DEMAR for military and unmanned aircraft, cybersecurity and data requirements such as NIST SP 800-171 and CMMC, and industrial execution covering controlled processes, traceability, qualified suppliers, documented inspections and the ability to scale without losing control of quality, cost or delivery.
• Both parts repeat the same caveat: not every standard, rule or approval applies to every company, and the applicable requirements depend on the specific product, customer, program and contract, so they should be identified before commitments are made.

His statement that a working product is not automatically approved for military use, and the distinction between a successful prototype and consistent, traceable delivery at scale.

Read original · Original 2

One post presents the final stage of a framework called JENNY, covering "Yield Results & Learn": implement, monitor and reflect, track KPIs and milestones, review outcomes and feed what is learned into the next cycle.

• It offers three review questions and a worked example in which a digital transformation is reviewed for adoption, process performance and value realization before the roadmap is adjusted.
• The post offers a free five-page PDF of the full framework in exchange for a comment or direct message and lists shared team contact details for AviaiQ LLC and AviaiQ Europe, showing how a framework is used as the entry point to a conversation.

The three questions a team is asked at this stage: are we achieving the expected results, what is the data telling us, and what should we keep, change or stop.

Read original

It answers what evidence can distinguish a promising lead from a pursuit worth committing resources to.

Schoettner separates a market signal, an opportunity hypothesis, a qualified opportunity, and a committed pursuit.

• He then asks teams to test opportunities across five areas: customer need and funding, market access, solution fit, competitive position, and ability to execute.
• Missing evidence should be visible, assigned, and tied to a next action.
• The post ends with a practical set of choices: validate, shape, pursue, partner, pause, or stop.

For brands planning a campaign

For a defense technology company reviewing its pipeline, use the five evidence areas as a discussion checklist. Label each opportunity by stage, assign owners to evidence gaps, and decide whether to advance, partner, pause, or stop.

It answers how successful delivery, customer learning, and partnerships can strengthen future business development.

This post connects customer insight, focused pursuit, aligned commitment, reliable delivery, and compounding trust in a repeating cycle. Schoettner distinguishes the flywheel from the funnel and pipeline: the funnel measures conversion, the pipeline tracks current opportunities, and the flywheel describes how delivery and learning can improve later pursuits.

For brands planning a campaign

A campaign about pipeline improvement could pair stage qualification with a follow-through measure: whether delivery creates customer insight, trust, or access that helps the next pursuit.

It answers which kinds of legal and organizational questions can affect whether a company is ready to enter a specific project.

Schoettner organizes defense-market entry around five areas: product classification, export controls, information security, compliance ownership, and delivery qualification.

• He gives examples of German, EU, and US rules, while stressing that applicability depends on the product and transaction.
• The post points readers toward identifying relevant requirements before making commitments rather than assuming one checklist fits every company.

For brands planning a campaign

For a market-entry campaign, this can support a careful readiness discussion. Avoid presenting the post as legal advice or implying that every named rule applies; frame the next step as identifying requirements for the company's product and intended transaction.

It answers what can stand between a technically capable supplier and a product that is qualified and deliverable under a particular contract.

The companion delivery post lists five areas to examine before taking on defense work: quality management, military specifications, qualification and approval, cybersecurity and data, and industrial execution.

• Its concrete examples include ISO 9001, EN 9100, AQAP, MIL-STD-810, and MIL-STD-461.
• Schoettner notes that requirements depend on the product, customer, and contract, and distinguishes a working prototype from an approved, consistently deliverable product.

For brands planning a campaign

Use the two-part series to shape a readiness workshop: separate legal and compliance questions from quality, qualification, cyber, and production questions, then confirm which requirements apply to the specific opportunity.

Wolf Schoettner names John Boyd and the military-aviation origin of OODA, breaks the loop into Observe, Orient, Decide, Act, and illustrates each failure point with a short chain ("Observe without Orient = data...

• Decide without Act = PowerPoint").
• The posts then map the point onto aerospace and defense, where long programs, multiple stakeholders and qualification requirements leave little room for slow decisions.
• Both close by asking readers which of the four steps costs their organization the most time.

A named external framework is explained briefly, applied to the writer's own sector, and ended with a diagnostic question instead of a fixed recommendation.

The two posts carry nearly identical body text, so a reader should treat them as one argument rather than two separate observations.

For brands planning a campaign

A defense technology company can lift the OODA framing into internal review meetings as a shared vocabulary for where its pipeline stalls, and use the closing question to run a quick self-assessment of whether delays sit in observing, orienting, deciding or acting.

Examples: Source 1 · Source 2

It argues that blending these stages makes a pipeline look impressive while hiding where evidence ends and optimism begins.

• It then lists five dimensions that must be evidenced before an opportunity advances: customer (defined operational need, decision process, timing, funding path), market (program landscape, procurement route, competition), solution (credible contribution inside a wider system), position (differentiator, customer access, role in the value chain, whether partnering beats competing) and execution (ability to qualify, industrialize, deliver and support).
• Missing evidence is allowed but must be visible, assigned and tied to a next action.

A stage-and-dimension checklist, with the explicit rule that unanswered questions are recorded rather than ignored, and that business development, sales, engineering, operations and finance work from one shared view. The post ends by listing the possible decisions: validate, shape, pursue, partner, pause or stop.

For brands planning a campaign

This is directly usable by the reader brief: a defense technology company could adopt the four stages and five dimensions as the agenda for pipeline reviews, requiring each opportunity to show which evidence exists, which is missing, who owns it and what the next action is before resources are committed.

Examples: Source 1

It sets out five reinforcing stages: customer insight, focused pursuit, aligned commitment, reliable delivery and compounding trust, then restarts the cycle from a stronger position. It also draws a clear division of labour between three models: the funnel measures conversion to revenue, the pipeline tracks current opportunities, and the flywheel explains how customer outcomes create cumulative advantage.

A named five-stage cycle with a worked example per stage, and an explicit comparison that keeps existing tools in place rather than replacing them.

For brands planning a campaign

For a company whose pipeline reviews are dominated by deal counts and stages, this gives a second lens: after each delivered program the company can ask what relationship, qualification experience, industrial capability or trust it has gained, and record that as an input to the next pursuit.

Examples: Source 1

Part one covers the legal gate: product classification (military equipment, dual-use item or war weapon), export controls including EU Dual-Use Regulation 2021/821, sanctions, end-use restrictions, ITAR and EAR, security and information handling, ownership of compliance responsibility, and delivery qualification.

• Part two covers the delivery gate: quality management standards (ISO 9001, EN 9100, AQAP), military specifications such as MIL-STD-810 and MIL-STD-461, qualification and airworthiness frameworks (EMAR, DEMAR), cybersecurity requirements (NIST SP 800-171, CMMC), and industrial execution covering traceability, qualified suppliers and scalable production.
• Both parts stress that a technically capable company is not automatically a qualified defense supplier, and that not every rule applies to every product or contract.

Two numbered five-point lists written as pre-commitment checks, each ending with a short "the point" summary and an offer to discuss a company's starting position by direct message.

For brands planning a campaign

A defense technology company could use the two lists as a readiness screen before bidding: confirm product classification and export-control exposure first, then confirm quality certification, military-specification testing and industrial execution capacity. The posts also identify where a partner or adviser might be needed, since several requirements depend on the specific product, customer and contract.

Examples: Source 1 · Source 2

The first frames readiness as movement: up to 800,000 NATO troops could transit Germany within 180 days in an Article 5 contingency, and bottlenecks include rail capacity, road-weight limits, bridges, borders and rail gauges, with the Lithuanian 1,520 mm gauge as a concrete example.

• The second distinguishes logistics capacity from logistics survivability, noting that large-volume movement has been demonstrated but not under persistent interdiction, electronic warfare and precision strikes, and lists the fixed targets that cannot easily disperse.
• The third looks at fuel infrastructure, arguing that the pipeline architecture reflects older requirements and that long-term construction does not close a near-term readiness gap, summarized as procurement creates assets, infrastructure creates access, logistics creates operational effect.

Each post starts from a named external report, extracts one or two concrete figures or examples, then states a short conclusion; two of the three close with a direct question to readers.

For brands planning a campaign

For a company selling into defense readiness, these posts show the topics Wolf Schoettner treats as urgent: mobility infrastructure, survivability of supply routes, counter-drone protection for logistics, and the timing gap between announced investment and usable capability. Those are usable angles for a campaign brief aimed at European defense readiness.

Examples: Source 1 · Source 2 · Source 3

It offers three review questions and a worked example about a digital transformation where adoption, process performance and value realization are reviewed before the roadmap is adjusted. The post invites readers to comment for a free five-page PDF or to make contact through the company's shared team address and phone numbers.

A named proprietary framework stage, three check questions and a concrete example, followed by a direct offer of a written resource.

For brands planning a campaign

This is the clearest commercial asset in the reviewed material: a company could request the JENNY PDF to see how the framework is packaged, and use the three review questions as a lightweight post-delivery check on its own programs. The post also shows that Wolf Schoettner and AviaiQ publish structured, named frameworks rather than only commentary, which matters if a brand wants campaign content built around a method.

Examples: Source 1

The posts do not say whether Schoettner owns AviaiQ, is employed by it, or works with it as a contractor; the relationship is unstated.

View example

The material does not state Schoettner's role in either entity.

View example

Schoettner uses the IISS analysis as source material for his own commentary; the posts show no commercial relationship.

View example

Guy Breier's point that traceability is not resilience — you can map every supply-chain dependency and still have no qualified manufacturing capacity — is the same move Wolf Schoettner makes when he separates logistics capacity from logistics survivability and insists that a working prototype is not a qualified defense product. Both write for people who have to build, qualify and deliver, and both anchor an argument in a specific external development.

Guy Breier's field is U.S. manufacturing and supply-chain sourcing, including origin tracing through supplier tiers and the gap between policy intent and capacity, and the posts are short briefings that point to a longer analysis. Wolf Schoettner writes mainly from a European and NATO frame, covering export controls, market-entry gates and business-development process, and develops his points as numbered frameworks rather than brief commentary.

Read original · Original 2

Tobias Kohl argues the first question about future fuels should not be which fuel wins but how the whole vessel system works together, since changing the energy source changes power generation, energy management and safety requirements too. Wolf Schoettner makes the same structural argument when he asks whether a technical capability is a credible contribution inside a wider system, and both judge a proposal by how its parts fit its actual operating environment.

Tobias Kohl stays inside marine engineering and the energy transition, writing short first-person reflections without checklists or stages. Wolf Schoettner works on defense market entry, opportunity qualification and readiness, and typically lays out numbered stages, named standards and an explicit decision to be taken.

Read original · Original 2

Nicolas Sauvage's Usable-Scale Test asks whether a corporate capability is relevant, reachable, owned, backed by evidence and good for a startup's independence, and it comes out of a real portfolio discussion rather than theory.

• Wolf Schoettner does the same thing with opportunity qualification: four stages that must not be blended and five dimensions that must be evidenced before a pursuit is committed, drawn from named external analysis or his own frameworks.
• Both also keep the decision open, ending in validate, shape, pursue, partner, pause or stop rather than a predetermined answer.

Nicolas Sauvage writes as a venture investor about how large industrial companies and deeptech founders work together, and addresses founders and corporate partners. Wolf Schoettner addresses established industrial companies and their business-development, engineering and operations teams deciding whether and how to enter defense work.

Read original · Original 2

Kohl's two posts argue that the wrong first question is which fuel wins, because changing the energy source also changes power generation, energy management, safety and other onboard systems.

• The stated method is to design the system architecture first and then pick components, testing any pathway against the vessel's operating profile, infrastructure, maintenance, regulation, lifecycle and energy management.
• That is a useful spine for a campaign whose buyer is deciding between technical routes, or for an engineering audience that will reject a general pipeline message.

Kohl gives no qualification stages, no pipeline or opportunity model and no defense-market entry material. A brand whose brief is how to separate a qualified opportunity from an optimistic one gets no usable checklist here, and the two posts are a narrow sample rather than a body of method, so the campaign would rest on a small amount of published text.

Examples: Source 1 · Source 2

Breier's post on Executive Order 14415 separates traceability from resilience, notes that a Bill of Material can be traced through supplier tiers back to raw-material origin while the American flag on the factory does not make the chain American, and closes with the argument that you cannot supplier-manage your way out of capacity that does not exist.

• A second post points to Sikorsky's conversion of a UH-60L Black Hawk into an autonomous aircraft and frames it around manufacturing implications, operations transformation and quality certification.
• For a defense technology company whose real constraint is suppliers, qualification capacity or re-shoring, this is closer to the decision than a business-development framework is.

Breier offers no opportunity-qualification method, no stage definitions and no next-action checklist, so a brief built on evidence-based pipeline stages would have to supply that structure from elsewhere. One of the two posts is a short pointer to an external executive briefing rather than self-contained analysis, which limits how much of the argument can be used directly.

Examples: Source 1 · Source 2

Sauvage's TDK Ventures post sets out what is called the Usable-Scale Test — relevance, reachability, ownership, evidence and independence — and pairs it with a concrete case in which TDK helped source and qualify more than 50 components per board for Groq and worked on a power-management roadmap.

• A second post from a founders' dinner in Mumbai uses named examples of companies buying a manufacturer, stepping back from whole-project delivery, or testing a royalty arrangement to ask what a deeptech company must own to scale.
• That maps onto a partnership or investor audience weighing commitments and obligations.

Sauvage's frame is venture investing and startup scaling, not defense procurement.

• The stages describe how a founder evaluates an industrial partner's capability, not how a company qualifies a defense opportunity, so the vocabulary of export controls, military standards and airworthiness requirements is absent.
• A campaign that promises defense-sector pipeline guidance would be stretching this material beyond what the posts support.

Examples: Source 1 · Source 2