design-intelligence-network

name	design-intelligence-network
description	Use when preparing for a major competitive engagement — product launch, market entry, key negotiation, or strategic partnership — to systematically gather intelligence from multiple source types and convert it into decision-relevant insight
source	Sun Tzu "The Art of War" Ch.9, 13 (Giles trans. 1910; Griffith trans. 1963); US Intelligence Community "Intelligence Cycle" doctrine; Gilad "Early Warning" (2004); Fuld "The Secret Language of Competitive Intelligence" (2006)
tags	["intelligence","competitive-intelligence","win-loss","spies","information-gathering","sun-tzu","art-of-war","yong-jian"]
verified	true

Design Intelligence Network

Map your intelligence needs against the five source types, build a systematic collection process for each, synthesise across sources into a decision-relevant picture, and use the intelligence to change your decisions — not confirm them.

Why This Is Best Practice

Origin: Chapter 13 of The Art of War — Yong Jian (用間, Use of Spies) — is the final chapter and, Sun Tzu argues, the most important: "Foreknowledge cannot be elicited from spirits, it cannot be obtained inductively from experience, nor by any deductive calculation. Knowledge of the enemy's dispositions can only be obtained from other men." (Ch.13, Giles trans.) The five spy types he identifies cover the complete intelligence source architecture: local sources, inside sources, converted sources, disseminated disinformation, and field observers.

Adopted by: Every professional intelligence organisation (CIA, MI6, corporate intelligence teams) structures its collection around multiple source types — HUMINT (human intelligence), SIGINT (signals), OSINT (open source), TECHINT (technical). Fuld & Company, the leading competitive intelligence firm, documents that 90% of the intelligence needed to make strategic decisions is legally and ethically available from public and semi-public sources — the failure is not access to information, but systematic collection and synthesis. Ben Gilad's Early Warning (2004) is the standard text for corporate competitive intelligence programs.

Impact: Decisions made without intelligence are made on assumption. Assumptions about competitor pricing, product roadmap, customer relationships, and strategic intent are consistently wrong in predictable ways (overestimating the incumbent's inertia, underestimating their response capability). A systematic intelligence collection process turns decisions from assumption-based to evidence-based — not perfectly, but materially better.

Why best: The five-source framework is exhaustive without being redundant. Each source type accesses a distinct category of information that the others cannot reach. Local sources access current market conditions; inside sources access competitive intent; converted sources provide disinformation correction; field observers provide ground truth; disseminated information shapes the information environment. Running all five systematically produces a multi-dimensional intelligence picture that no single source can provide.

Sources: Sun Tzu, The Art of War (Giles trans. 1910) — Ch.9 (Army on the March — reading field signs), Ch.13 (Use of Spies); Fuld, The Secret Language of Competitive Intelligence (2006); Gilad, Early Warning (2004); US Army FM 2-0, Intelligence (2019)

Steps

Step 1: Define your intelligence requirements

Before building the collection network, identify the specific decisions the intelligence must inform. Good intelligence is decision-relevant; collection without a decision target produces expensive data without insight.

Write the top 3–5 intelligence requirements in this format:

"I need to know [specific question] because it will change my decision about [specific action]."

Examples:

• "I need to know the competitor's pricing model for their enterprise tier because it will determine our pricing strategy in the Q4 proposal."
• "I need to know whether the incumbent is planning a product launch in the SMB segment because it will determine whether we accelerate our own entry."
• "I need to know the key decision criteria for the committee buying the enterprise deal because it will determine what we emphasise in the final presentation."

Limit to 3–5 requirements. More than five creates collection effort that produces volume without focus.

Step 2: Source 1 — Local agents (market-facing sources)

Who they are: People with direct access to the market environment — customers (current, former, potential), industry analysts, journalists, channel partners, distributors, recruiters active in the space, trade association members.

What they provide: Current market conditions, customer perception of competitors, pricing and packaging intelligence, competitive win/loss context, emerging customer needs.

Collection methods:

• Win/loss interviews: call every customer who chose a competitor and ask specifically what drove the decision. This is the highest-signal intelligence source for product and sales strategy. Ask: "What did [competitor] offer that we didn't?" "What would we need to do to win your business in the future?"
• Customer advisory boards: regular engagement with 10–20 reference customers who share their view of the competitive landscape
• Industry analyst briefings: analysts track competitive positioning as their core function; their assessments of competitor positioning are valuable even when not paid for
• Channel partner intelligence: partners who carry multiple vendors have a complete picture of competitive comparison in the field

Step 3: Source 2 — Inside agents (competitive organisation access)

Who they are: People with legitimate access to or relationships inside the competitor's organisation — shared investors, common board advisors, former employees (in appropriate contexts), shared customers who interact with both sides.

What they provide: Strategic intent signals, leadership changes, internal priorities, product development directions.

Ethical boundaries: This source type must be operated within strict legal and ethical boundaries. Appropriate methods include:

• Conversations with people who left the competitor voluntarily and are not bound by NDAs on the specific information shared
• Relationships with shared customers who volunteer comparative information about their experience with both sides
• Relationships with shared advisors and investors who may have general (not confidential) perspective on the competitor's direction

Not appropriate: Soliciting NDA-protected information, encouraging breach of confidentiality, or accessing proprietary information through third parties. The ethical line is asking about what is generally known and observable, not asking for confidential internal information.

Collection methods:

• Professional network intelligence: LinkedIn connections to former competitor employees who have publicly moved to other roles; conversations in professional settings
• Shared ecosystem intelligence: conversations with partners, investors, and advisors who interact with both organisations on topics of mutual interest (market trends, not confidential strategy)

Step 4: Source 3 — Open source intelligence (OSINT)

Who it is: Public signals — job postings, patent filings, regulatory submissions, press releases, conference presentations, GitHub repositories, social media, court filings, SEC disclosures (for public companies).

What it provides: Product development direction (patents), technology capability (GitHub/open source activity), strategic priorities (executive speeches and conference talks), financial health (SEC filings, credit reports), talent priorities (job postings), customer success (case studies, G2/Gartner reviews).

Collection methods:

• Job postings: The single highest-signal OSINT source for competitive intelligence. What roles are they hiring? Engineering in a new product area = new capability in development. Sales in a new vertical = market expansion. Management of a new function = new strategic priority.
• Patent filings: 18 months before a product launch, patents reveal technology directions. Monitor competitor filings in your relevant technology areas through USPTO/EPO public databases.
• GitHub activity: Open source contributions, public repositories, and star activity reveal technical interests and capabilities.
• Conference talks: What do their engineers and product leaders present at conferences? These are usually 12–18 months behind internal work but reveal what they are proud of.
• Regulatory filings: Public company 10-K and 10-Q filings describe competitive risks, strategic priorities, and major customer concentrations in legally mandated disclosure language.

Step 5: Source 4 — Converted sources (correcting disinformation)

What this source does: Identifies when your intelligence picture is being shaped by intentional or unintentional competitor disinformation — press releases that overstate capability, analyst briefings designed to shape market perception, product announcements that are not matched by shipping reality.

Collection methods:

• Cross-validate every major competitor claim across multiple sources before acting on it. A product announcement without shipping evidence, customer references, or third-party validation is not confirmed intelligence.
• Track the gap between announced and delivered: competitor X announced feature Y six months ago — is it in the product? Ask customers. Check G2/Capterra reviews. Read support documentation.
• Apply the "vaporware filter": how often does this competitor announce capabilities that do not ship on time or at all? Apply a discount factor to future announcements based on their track record.

Why this matters: Competitors are aware that their announcements shape your decisions. An announcement of a feature that is 18 months from shipping may be designed to freeze your customers' buying decisions or deter your roadmap investment.

Step 6: Source 5 — Field observers (surviving spies)

Who they are: Your own people who go into the market and return with ground-truth intelligence — sales engineers who do competitive evaluations, customer success managers who handle at-risk accounts, product managers who talk to churned customers, executives who attend industry events.

What they provide: Real-time field intelligence on competitive positioning, customer sentiment, product reception, and sales battle dynamics.

Collection process:

• Structured debrief after every competitive loss: what did the customer say about the competitor? What features were decisive? What pricing was offered?
• Structured debrief after every competitive win: why did you win? What weaknesses of the competitor did the customer cite?
• Competitive evaluation participation: when a customer runs a formal bake-off, debrief the evaluation criteria and the competitor's presentation approach
• Mystery shopping / competitive testing: systematically evaluate the competitor's product as a new customer would, documenting the experience

Step 7: Synthesise and act

Intelligence has no value until it changes a decision. Build a synthesis process:

1. Collect from all active sources on a regular cadence (weekly or monthly for active competitive situations)
2. Assess each piece of intelligence for reliability (source quality) and relevance (decision impact)
3. Integrate across sources — where do multiple sources converge? Convergence increases confidence. Where do sources conflict? Conflict signals either disinformation (Source 4 applies) or evolving conditions.
4. Brief decision-makers with the intelligence picture before the decision is made, not after
5. Act — change the decision or confirm it with evidence rather than assumption

Rules

• Define requirements before collecting. Intelligence without a decision target is data. Decide what you need to know and why before building collection infrastructure.
• Use all five source types. Each accesses information the others cannot. A single-source intelligence operation will have systematic blind spots.
• Apply the ethical boundary consistently and strictly. Inside source collection must not involve soliciting confidential information, facilitating NDA breaches, or accessing proprietary systems. This is both an ethical and legal requirement.
• Apply the vaporware filter to competitor announcements. Not all intelligence is true. Cross-validate competitor claims before acting on them.
• Brief before the decision, not after. Intelligence delivered after a decision has been made is rationalisation support, not decision support.

Examples

Competitive intelligence before a product launch: Requirements: (1) What is competitor X's pricing for the enterprise tier? (2) When are they launching feature Y? (3) Which customers are at risk of switching to competitor X in the next 6 months?

• Local agents: win/loss interviews with 10 recent losses; channel partner conversations
• Inside agents: conversations with 2 shared investors at industry events
• OSINT: competitor job postings (hiring enterprise sales = moving upmarket); patent filings (new feature direction); G2 reviews (customer satisfaction with current product)
• Field observers: structured debrief from sales team on last 10 competitive evaluations

Win/loss analysis program (systematic field intelligence): Template for every loss debrief:

• Which competitor won?
• What were the three most important factors in the customer's decision?
• What did the competitor offer that we didn't?
• What would we need to change to win this customer's next evaluation?
• What is the customer's assessment of the competitor's weaknesses?

Run this consistently for 6 months; patterns emerge that no individual sales manager can see.

Reading field signs (Chapter 9 — observable intelligence): Sun Tzu's Chapter 9 (Army on the March) is about reading observable signs in the field: "When there is much running about and the soldiers fall into rank, it means that the critical moment has come." Business equivalent: a competitor's unusual volume of conference presentations usually precedes a major product launch. A sudden burst of senior executive hiring in a new function signals a strategic pivot. Visible, observable signals in the market are intelligence available to anyone who is looking.

Common Mistakes

Collecting without intelligence requirements: Building a competitive intelligence function that produces reports without answering specific decision questions. The output is volume, not insight.

Relying on a single source: A competitive intelligence picture built only on OSINT misses strategic intent (inside agents) and field reality (field observers). A picture built only on sales debrief misses technology direction (OSINT) and market perception (local agents). Multi-source collection is not redundant — each source accesses distinct information.

Acting on unvalidated intelligence: Changing roadmap, pricing, or strategy based on a single competitor announcement without validating through additional sources. Apply the vaporware filter.

Not briefing before decisions: The intelligence cycle that produces reports read after the decision is made is an after-action review, not intelligence support. Build the process so decision-relevant intelligence reaches decision-makers before the decision is made.

Treating intelligence as confirmation: Competitive intelligence conducted by people who are looking for confirmation of a pre-existing view produces biased collection and analysis. The intelligence requirement should be "what is true?" not "what supports our current plan?"