Notes - Confidential

John Nolan | July 19, 2026

Chapter 1: Transfer Intelligence Community Techniques to the Commercial Sector

Opening Premise: Nothing New Under the Intelligence Sun

A senior faculty member's opening statement to trainee intelligence officers set the tone: despite marginal technical changes over time, the conduct of intelligence operations has remained fundamentally the same for thousands of years. This is illustrated through the biblical account of Moses sending Joshua's twelve spies into Canaan, followed by Joshua sending two men into Jericho to work with Rahab. That episode contains a striking list of "intelligence firsts" still relevant to tradecraft today:

• The first use of operational cover
• The first use of a safe house
• The first use of bona fides
• The first suggestion of a counterintelligence service (working for the king of Jericho)
• The first use of secrecy agreements between an agent and the officer running that agent
• The first (and possibly last) time an intelligence officer actually kept his word regarding an agent's family's safety
• The first use of an escape and evasion plan
• The first record of intelligence reporting to a decision maker

What Does NOT Transfer to Business Intelligence

A key, non-obvious point: with the exception of reporting to a decision maker, virtually none of these classic intelligence "firsts" apply to the Business Intelligence model as practiced by companies today. These remain part of mainstream operational intelligence tradecraft as practiced by nations, but are not — and should not be — part of the Business Intelligence lexicon.

Practical/ethical boundary lines drawn explicitly:

• Recruiting someone to betray their country for money (the heritage that produced the 1980s "Decade of the Spy") has no legitimanalog in Business Intelligence — or shouldn't.
• Developing esoteric operational covers to protect officers' lives and preserve secrecy of international operations is part of the same heritage but is inappropriate and largely unnecessary in the business world.
• No matter how abrasive a boss or business rival, planting "explosive-laden cigars or poisonous doughnuts" is obviously off-limits — used as a memorable warning against transferring the more extreme, coercive, or illegal tactics of state intelligence work into commercial practice.

What DOES Transfer: Legitimate Tools and Techniques

A number of intelligence community tools and techniques are legitimate, effective, and appropriate for direct transfer into the marketplace, and are also found in other disciplines:

• The intelligence cycle as an organized, well-developed process
• Intelligence analysis techniques — link analysis, time-event analysis, conflicting hypotheses, and a dozen or more others
• Intelligence processing — converting rinto a body of knowledge that can be evaluated, analyzed, and distributed
• Intelligence-specific tasking and allocation of collection resources to actually obtain information

Elicitation Techniques

Elicitation is introduced as one of the most valuable transferable skill sets. Though most rigorously developed for intelligence community use, elicitation also appears in literature, film, and television — and once you know what to look for, you can see it occurring naturally, sometimes elegantly, in everyday conversation. Most readers and viewers, however, fail to recognize elicitation techniques even when they are being used right in front of them (in print or on screen), and almost never recognize them when used on them in real, seemingly casual conversation.

Case Study: Sherlock Holmes and "Stacking" of Elicitation Techniques

A passage from Arthur Conan Doyle's "The Sign of Four" is used as a detailed working example of a "stacking of elicitation techniques" — multiple distinct techniques depd in rapid succession within one short conversation.

Scene breakdown: Holmes and Watson track a scent trail with a dog (Toby) to a wharf and a boat-hire house belonging to Mordecai Smith. Smith's young son Jack runs out, followed by his mother, Mrs. Smith, wielding a sponge. Holmes systematically extracts critical information from Mrs. Smith without her feeling interrogated:

1. He compliments and charms Jack the child ("Dear little chap!") and gives him money (escalating from one shilling to two), which builds warm rapport with the mother by praising her son.
2. He states a false/simple reason for approaching ("I wanted to hire his steam launch") rather than revealing his true investigative purpose.
3. When Mrs. Smith reveals her husband is away and she's worried, Holmes expresses disappointment and sympathy rather than pouncing on the lead, keeping the tone casual.
4. He deliberately makes an incorrect guess about the boat's description (color, funnel) even after already knowing details — prompting MrsSmith to correct him and volunteer more precise details than she otherwise would have.
5. He never lets on that any piece of information she's giving is valuable or important to him.
6. Through her, without a single direct interrogative question about the suspects, he learns: the husband left in the steam launch (the Aurora) despite insufficient coal for a long trip, a suspicious "wooden-legged man" with a foreign accent had been visiting and roused the husband in the night, a description of the boat (black with two red streaks, black hull, white band on the funnel), and that the husband and eldest son (Jim) left together at three in the morning without explanation.

Holmes explicitly states the underlying principle to Watson afterward: "The main thing with people of that sort is never to let them think that their information can be of the slightest importance to you. If you do they will instantly shut up like an oyster. If you listen to them under protest, as it were, you are very likely to get what you want."

Non-obvious point emphasized: Sherlock used eight different distinct elicitation techniques during this single short conversation — a level of "stacking" most readers never notice on a first read, and even less so when techniques are used against them in real conversation. Recognizing these techniques serves two purposes: 1) learning to replicate a master's skill in collecting information, and 2) learning to protect your own information when techniques are used against you.

An appendix, "An Annotated Sampler from The Complete Sherlock Holmes," contains further extracts with notes identifying individual elicitation techniques as Holmes uses them throughout several of his adventures.

Practical Application and Credibility Claim

Theseoints, and many more covered in subsequent chapters, are stated to be regularly and routinely taught to hundreds of mid-career federal intelligence professionals each year — a claim grounded in the fact that the training firm behind this material does the teaching itself. Essentially the same training (with portions not suitable for private-sector transfer removed) has been the primary curriculum provided to Business Intelligence professionals for the past decade, delivered both through pubc seminars and in-company training programs nationally and internationally.

Characteristics of Effective Elicitors

Sherlock Holmes's behavior in the wharf scene models several key traits of an effective elicitor:

• Appearing innocent, friendly, and unafraid to make a misstatement (deliberately getting details "wrong" to invite correction)
• Appearing curious, but only within careful bounds and limits
• Overall demeanor that is casually, nonthreateningly curious

Additional characteristics of effective elicitors:

• A natural gift for making friends and establishing rapport
• Being an effective manager of human relationships, with practical psychological insight into social interaction
• Understanding of the subtleties and intangibles of personal relationships
• Appreciation for national and cultural differences that could otherwise block effective elicitation
• Strong listening ability
• Flexibility to adapt to shifts in conversation
• Tact
• A good memory — because pulling out a notepad and visibly taking notes is one of the fastest ways to stunt the progress of an elicitation conversation
• Broad general knowledge, useful for filling conversational gaps with relatively unimportant small talk when needed

Ego Suspension: The Single Most Important Characteristic

Ego suspension is identified as the single most important — and for many people, the most difficult — characteristic to master, warranting separate, dedicated treatment before proceeding further into elicitation structure.

Core principle: regardless of position, the elicitor's job is to collect informatom those who have it — not to impress the other person with intellect, sophistication, experience, education, income, or even the achievements of one's children.

Practical guidance:

• It can occasionally be useful to share something about yourself, but only sparingly, and strictly as an "accelerant" — like adding a small amount of fuel to a fire, not the main fuel source itself.
• Sometimes the most productive posture is to let the other person become "the teacher" and to deliberately as the position of student — even though this can feel arduous, it is highly profitable in the end.
• This may require actively subordinating your own pride (e.g., downplaying a recent promotion or accomplishment) so the other person can enjoy discussing their own achievements or situation.
• You are not meant to be the focus of the conversation — that role belongs to the other person.
• The elicitor's job is to maintain a conversational balance that keeps the other person comfortable enough to stay on the needed topic, even if that requires berate "one-downs-manship" instead of the natural human inclination toward "one-ups-manship."
• Warning/discipline point: save any ego gratification for later — after the information has been collected and the project is done, when you can enjoy the credit from those who "sign your paycheck." In the moment, suspending ego opens far more opportunities to collect information.

Vocabulary Note

Rather than using softer, more politically correct terminology, the text commits to traditional intelligence vocabulary throughout — notably using the word "source" to refer to the person on the other side of an elicitation conversation. Readers may mentally substitute alternate words like "client" or "target," but the traditional term is used deliberately for precision as the discussion moves into how elicitation is used to collect information that becomes useful, timely, effective intelligence.

Closing Analogy: The Vince Lombardi Approach to Mastery

A story from John Madden's book "Hey, Wait a Minute. I Wrote a Book!" describes Madden, in hirst year as offensive line coach for the Oakland Raiders, attending a Vince Lombardi seminar. Lombardi — who had led the Packers to two consecutive Super Bowl wins allegedly using only twelve offensive plays (six running, six passing) — spent eight full hours lecturing on a single play and still hadn't exhausted everything he could teach about it. Lombardi's mastery came from breaking that single play down into all its many component parts, understanding of which led to excellence — Loms only real standard.

This is used as the model for the book's approach: elicitation will similarly be broken down into its component parts, technique by technique, in the chapters that follow, as the path toward excellence in collecting information.

Chapter 2: What Good Does It Do to Ask Questions?

Opening Hook: The Nature of Sensitive Questions

Chapter opens with the deliberately provocative question "How's your sex life?" to illustrate what happens the moment someone asks a question, especially a sensitive one. In casual settings among friends, such a question might be an accepted joke; in a business context it's inappropriate and would trigger a defensive reaction. A defensive response is defined as one that causes the receiver to internally interrogate the situation: "Why is he asking this?" "How will he use my answer?" "Who else will know?" "Why should I answer?" "What's in it for me?" The identity of the questioner matters enormously — the same question from a chum after a basketball game lands completely differently than from a parent.

Contrast this with a low-stakes question like "What's two plus two?" — this produces a pure data response with no higher-level defensive processing, unless, notably, the person asking is your accountant right after filing your tax return with the IRS (context changes everything, even for innocuous questions).

A Question of Sensitivity

The more sensitive the topic, the more guarded the other party becomes — true across business, social, political, and other settings. Professionals with a lete need to extract information (social workers, ministers, doctors, recruiters, bosses, parents, business and government intelligence collectors) routinely face resistant, guarded, or unwilling subjects.

Example: asking an abused or molested child a direct question predictably causes withdrawal, avoidance, or anger — not the intended outcome. The complexity and sensitivity of a question directly drives up emotional loading, guardedness, suspicion, and the number of internal questions a person runs through before answering. en in a business setting where the question isn't as explosive as the sex-life example, the questioner may unintentionally raise the other person's suspicion and concern about motives well beyond what was intended — a warning that even mundane questions can backfire based on framing and context.

Interrogation vs. Interviewing vs. Elicitation

Three distinct information-gathering styles are defined precisely:

• Interrogation: obtaining what you want from someone who possibly has it, has not admitted having it, and knows who you are and y you want it. Typically adversarial in tone and character, often deliberately structured that way. Authority derives from an institution (e.g., a federal agent's badge implies a demand to cooperate); parental interrogation authority is often even greater.
• Interviewing: obtaining information from someone who probably has it, has more or less admitted having it, and knows who you are and why you want it. Typically nonadversarial in tone, though it can still be adversarial in character (e.g., a "nonstress" job interview vs. a deliberately stressful interview, or a friendly "puff question" media session vs. Mike Wallace and a camera crew showing up at your office door).
• Elicitation: the process, covered as the book's central alternative, that avoids direct questions and uses a conversational style to reduce concerns and suspicions both during the contact and afterward, maximizing information flow. The elicitation target may not have admitted having the information, may or may not be willing to part with it, and may not even know or care who the elicitor is. Elicitation still uses questions at times, but they are asked for specific reasons at planned points in the conversation, not as the default extraction method.

Reactions Under Interrogation

A quoted passage from John le Carré's The Night Manager (le Carré himself a former British intelligence officer) is used as one of the best descriptions of behavior under interrogation: under interrogation nobody behaves normally — stupid people act intelligent, intelnt people act stupid, the guilty look innocent, the innocent look guilty. Occasionally people simply tell the truth as they know it — and those are, ironically, the ones who get caught out, because "there's nobody less convincing... than the blameless man with nothing to hide." Practical implication: interrogation-style questiing distorts behavior so badly that surface impressions of guilt or innocence, honesty or evasion, are unreliable.

Interviewee Response Patterns

Several non-obvious behavioral patterns of interviewees are laid out:

• Most interviewees begin a session uncomfortable, gradually settling into some form of "normalcy" — the degree and speed of this shift depends heavily on the interviewer's skill.
• Depending on what's in it for them, interviewees tend to tell the truth as they know it, but they self-restrict answers to avoid anything that seems to injure their own interests.
• If an answer does injure them, they rarely make that mistake again in a future session — a warning that damaging a source's trust or exposing them to consequences from an answer effectively burns that avenue for future information.
• Interviewees mentally "replay tapes" of past conversations, second-guessing what they should have said differently.
• Cognitive psychology research shows people remember questions far more clearly and for longer than points raised in casual conversation. This matters enormously with uncooperative or guarded interviewees: they specifically remember the pointed questions that provoked responses they wish they hadn'ven.

The Multiple-Contact Problem

This memory effect creates serious practical problems whenever repeat contact with the same person is needed — the default situation in business or government intelligence collection, social work/counseling, media reporting, and undercover law enforcement:

• An intelligence professional finds a previously cooperative contact turning suspicious or uncooperative after having "second thoughts" about how much they revealed in the prior conversation.
• A social worker or counselor finds reluctant client becoming more distant after replaying prior interview tapes mentally and feeling newly vulnerable to someone only marginally trusted.
• A journalist finds a well-placed, previously forthcoming source no longer willing to provide the same caliber of information, on or off the record, because the source reconsidered earlier answers and vowed not to repeat them.
• An undercover officer working a money-laundering case faces literal mortal danger ("dying of lead poisoning of the 180-grain variety") the more directly he questions criminal targets — a stark warning that overly direct questioning in high-stakes covert work isn't just counterproductive, it can be lethal.
• A parent trying to learn what's happening in a teenager's life faces a subject unwilling to leave obvus clues lying around regarding friends and activities.

The Core Argument for Elicitation

Given all these failure modes of direct questioning, the recurring question raised by thousands of professionals across government training facilities, professional seminars, and in-house corporate programs is: "What good does it do to ask questions?" The consistent conclusion: there must be a better way. Elicitation is framed as an additional tool — "additional arrows for the information collector's quiver" — not a wholesale replacement for questions.

How People Respond to Elicitation

Because an elicitation conversation starts off, and continues, as nonthreatening and comfortable, cooperation with the source stays relatively high. There is a declining concern on the source's part about the informatieing shared, precisely because the elicitor visibly attaches little or no apparent significance to it. Using multiple techniques within a single elicitation session further reduces the source's concerns and increases comfort. This sets up the book's forward-looking point (elaborated in chapter 3): in a properly structured elicitation conversation, questions are not eliminated but are intentionally placed at specific, preplanned points to achieve specific purposes — rather than being the blu, front-loaded instrument of interrogation or straightforward interviewing.

Chapter 3: Exploding Old Myths and Succeeding at Elicitation

Opening Premise

Effective information collection is never left to chance. Elicitation, like any systematic process, rests on foundational building blocks: planning a conversation in advance and understanding the human dynamics that drive successful elicitation. Skipping either step undermines the whole effort — comparable to leaving structural blocks out of a house's foundation. Most people never plan an outcome for a conversation or follow a deliberate, step-by-step process, which is precisely why untrained collectors underperform.

The Myth at Conversation Is Innate

A persistent myth holds that conversational skill is an inborn trait — you're either naturally gifted or doomed to social isolation. Thibelief traps people into self-limiting statements like "I'm not very good at conversation," frequently heard from seminar participants whose jobs require gathering information from diverse subjects despite being only moderately comfortable talking even to their own spouses.

• This condition is not permanent, even for people in professions that insulate them from human interaction: scientists, software developers living on caffeine and junk food, accountants, librarians, actuaries, astronomers.
• Highly introverted seminar participants frequently outperform more extroverted counterparts when sent to gather specified information from strangers, returning with more and better information — and greater confidence than expected.
• Introver tend to value order and predesign, which suits a planned approach, and they typically have better-developed listening skills — a trait of major value in elicitation.
• Extroverts tend to thrive in ambiguous, unstructured situations, but even the most naturally gregarious ones show significant improvement in information-collection ability once they deconstruct their natural conversational patterns and organize them deliberately (compared to how Vince Lombardi's naturally talented athletes came champions only after breaking down and understanding their own techniques).

Elicitation itself is defined as a learned behavior: the art of inducing another person to talk by guiding a conversation so innocuously that the other party feels comfortable throughout, keeping the relationship nonthreatening for both sides.

Why Small Talk Works: Bits and Pieces

When a conversation is planned to extract separate component parts of needed information, most sources never realize that the seemingly inconsequential pieces they're providing matter at all — and individually, those pieces often aren't important. Sources rarely perceive the intelligence process at work or see the connection between the small pieces they give up and the larger "puzzle" being assembled.

Case Example: Government Contractor Billing Rates

• A common intelligence objective for a business competing on a federal contract is discovering a competitor's overhead/G&A billing multiplier (e.g., 1.75 for overhead, 0.27 for G&A) — the number used to convert base labor rates into a priced proposal.
• Nobody can be asked directly for this figure: most employees don't know it, and those who do treat it as some of their firm's most closely guarded proprietary information — they would "sooner have their hands and heads chopped off" than reveal it.
• The workaround: extract the roughly 160 underlying variables from people who possess small, individually unimportant facts (benefits costs, insurance contributions, facilities costs, vacation policy, staffing counts for administratictions, etc.), supplemented by Freedom of Information Act documents where available.
• Illustrative examples:
  • An employee sympathetically describes her insurance costs rising from full employer-paid coverage five years ago to $62.50 per pay period now for the most basic plan — she doesn't see this as sensitive, yet it materially shifts the overhead calculation once corroborated against market insurance costs.
  • Another employee complains that paid Christmas vacation dropped from ten days to two under new "bean counterpolicy — again freely shared, again a meaningful downward input to the overhead rate once verified across multiple sources.
• The practical lesson: never ask for the sensitive number itself. Instead, collect scattered, seemingly trivial data points from multiple people, cross-verify them against known market benchmarks, and recotruct the sensitive figure indirectly.

Planning the Conversation

"Planning a conversation" sounds foreign or even manipulative, but communication's actual purpose is to transfer information from one person to another — which makes it fundamentally a matter of economics. Starting with a clear picture of the desired outcome and the steps needed to reach it proces measurably better results than improvising.

• For introverts, having a defined outcome, system, or checklist gives them direction they've never had before and lets them achieve results in conversation they'd previously found unattainable.
• For extroverts, conversation comes so naturally that they rarely bother to analyze its structure — yet when they do dissect and organize their otherwise random patterns, they see significant improvements in their ability to collect information from virtually everyone they deal with.

Shaping the Conversation: Three Sequential Parts

1. Establish the objective. Decide exactly what you want to achieve, then set milestones for what will be covered and match those milestones to specific techniques and to the exploitable human characteristics particular to the individual source.
2. Select elicitation techniques. Choose from the elicitation technique(detailed later, in chapters 6 and 7) matched to the personality of the person across the table; some techniques will feel natural immediately, others should be deferred until more experience is gained.
3. Apply the hourglass structure (detailed below) to organize the conversation itself.

Staying on track: When a conversation drifts off course — which it almost inevitably will — having pre-established objectives lets a practiced elicitor recall what's already been covered and whamains. Without planning, collectors simply forget what they came to gather and the conversation wanders aimlessly.

The Conversational Hourglass

The ideal elicitation conversation is structured like an hourglass: wide at the top, narrowing through the middle, and widening again at the end.

• Top (wide): General, nonthreatening "macro" topics and preselected questions.
• Middle (narrow waist): The conversation narrows toward the specific topics actually being pursued, shaped and compressed using selected elicitation techniques.
• Bottom (wide again): The conversation broadens back out to general macro topics before ending.

Why This Shape Matters — the Cognitive Science Behind It

• Cognitive psychology research (referenced from chapter 2) shows people remember dect questions far more clearly and for longer than they remember the casual conversational content surrounding them.
• Separate research shows people recall the beginning and end of a conversation much more readily than the "muddle in the middle."
• Combined implication: put large, nonthreatening, forgettable macro topics at the beginning and end, and bury the actual target information in the narrow, less-memorable middle. When no importance is signaled around a topic, there is no reason for the source to file it away as significant.

What Goes Into the Hourglass

Beyond the basic shape, a skilled elicitor loads the conversation with:

• The chosen outcome/objective (kept in the back of the mind).
• Elicitation techniques (to be detailed in chapters 6–7) — either newly learned ones or ones proveccessful with this specific source before.
• Human factors/characteristics specific to the source (detailed in chapter 4), or patterns recognized from prior conversations about why this source talks.
• Existing background knowledge about the subject matter being pursued, which helps steer the conversation precisely.
• Previously developed background and personal information about the source.

Warning/insight: The combined mix is described as "very volatile" — it can unlock vastly more iormation than casual, unstructured conversation, but it must be handled with the right questions at the right time for the right purpose, and used to actively avoid questions that would draw undue attention to the real target of interest.

The Target's Own Behavior Helps You

Most often, it is the target — not the elicitor â moves the conversation from macro abstraction down toward specifics. A target encouraged by techniques such as disbelief, naivete, or opposition (covered later) cannot sustain talking in abstractions; the easiest way for anyone to illustrate a point is to describe personal experience — a tendency termed "the lecturer's temptation," the near-irresistible urge to explain things via one's own specific case.

Practical Illustration: Compensation Program Example

To learn about a firm's sales-force compensation program:. Open with general commentary on world economic conditions (inflation, balance of payments) — nonthreatening macro material. 2. Gradually move the conversation downward from macro to micro, from general economic topics to professional and personal specifics. 3. The source (e.g., someone from the sales force) will quickly relate macro abstractions to the only real-world example he actually knows or cares about — his own firm's situation. 4. Combined with techniques that exploit human factors, this reliably surfaces more information than expected.

Seminar Confidence-Building Exercise

Training seminars task participants with collecting highly sensitive personal financial data — income levels, bank balances, home values, bank accumbers, and (for advanced practice) PINs and other access information — not to use or misuse it, but purely to build the collector's own confidence that such information really can be obtained from strangers.

• Students routinely say "No way" when first given the assignment.
• They almost invariably return having successfully collected everything requested and more, confident and "somewhat surprised" at how much people will reveal with minimal provocation when approached with a plan, defin objectives, and practiced techniques.
• This financial-data exercise makes subsequent business-financial elicitation "ever so much easier."

The Detached Observer

Maintaining consistent, apparent detachment throughout the elicitation is essential — described via the boxing metaphor "don't telegraph your punches." Even wellrepared elicitors can undo all their planning by visibly signaling what they're after.

Contrast: The Sales/Marketing Approach (a Cautionary Model)

• Sales and marketing professionals typically move relentlessly toward a single closing objective, and customers frequently walk away "feeling violated" by that single-mindedness.
• When such people gather information, they use the identical approach: extract it and move on. Their objective is nearly always transparent.
• Warning: This approach causes sources to "dry up very quickly" and is a failure pattern found across virtually every field of human endeavor, not just sales — the conversation ends on the very topic pursued, leaving the source acutely aware of what was extracted.

The Skilled Elicitor's Alternative

• Attach no more apparent significance to the sought information than to any other "dross" of the conversation.
• Close the conversation with another preselected, general, nonthreatening topic — using directed questions so the source's lasting memory is of something inconsequential.
• Result: repeat access. The source doesn't feel "as if he's just been through a wringer," preserving the relationship for future collection.

Backward Chaining

Backward chaining — working backward fpreestablished goal rather than bumbling toward an ill-defined one — is a planning technique borrowed from other industries and highly useful in structuring elicitation.

Worked Example: Assessing Effects of Personnel Departures at a Competitor

Goal: understand how the loss of key technical talent ("the real brain trust") is affecting a competitor's ability to develop new technologies, including who left and where they went. Mapped backward as a mental checklist:

• Final Objective: scussion of the internal situation and its effects.
• Step Four: Discussion of the company in relation to its industry.
• Step Three: Discussion of general and specific industry issues.
• Step Two: Discussion of regulatory issues.
• Step One: Give-and-take, question-based discussion of national economic issues.

This illustrates the hourglass in reverse-engineered form: each preceding step is broader/more macro, building toward the narrow, specific final objective.

The Setting and the Situation

A basic, elemental factor frequently overlooked by novice and even experienced collectors alike: choosing the wrong time and place destroys both the immediate opportunity and future collection chances, because the urge to "get the information right now" overrides judgment about context.

Cautionary Examples of Bad Timing/Setting

• Calling someone the way a telemarketer interrupts dinner — guaranteed poor receptiveness.
• Attempting elicitation with a supermarket cashier on the busiest shopping night of the week.
• Trying to draw out a trade-show "booth maven" while he's surrounded by six colleagues all reinforcing the same company talking points.
• None of these settings offer a reasonable chance of success and reflect a total absence of planning.

Practical Rule

One of the very first questions asked at the start of any intelligence meeting is "How much time do we have?" — driven by the reality of last-minute schedule changes even from cooperative sources. The business/phone equivalent: always ask up front whether it's a good time to talk, and if not, offer tll back later. This is framed as more than politeness — it is "the only thing to do," since elicitation inherently takes longer than a quick question-and-answer exchange, and the topic under discussion is rarely so urgent that it justifies imposing on a bad moment.

Measures of Success

Different information-collection professions define success differently:

• Interrogators measure success by signed confessions, jail time for offenders, and closed cases.
• Interviewers measure suess by the quality of articles written, the quality of employees hired, or the social interventions made possible.
• Elicitors measure success differently from both: by how third-party observers and the source directly involved react to the session.
  • If a third-party witness comes away finding the session "singularly boring and inconsequential," that is success.
  • If the source walks away still fully comfortable and unconcerned that anything of real value was communicated, that is success too.

This kind of success is reinforced and amplified when the structural process described in this chapter (the hourglass, planning, backward chaining, setting awareness) is combined with the human factors covered in the next chapter — together dramatically increasing the ability to collect nearly any kind of information from nearly any kind of source.

Chapter 4: Human Characteristics in Elicitation

This chapter catalogs recurring human traits that surface whenever people exchange information, regardless of whether an assignment is domestic or international, corporate or governmental, or whether people involved are highly educated or not. These characteristics are not novel discoveries but ordinary tendencies buried in everyday behavior that become powerful tools once raised to conscious awareness and deliberately applied. They carry no fixed ranking — some depend on individual personality, some are culturally universal — and elicitors should feel free to favor whichever approaches fit their own style.

Desire for Recognition

Most people downplay how much they cravgnition, but experience (backed by extensive research literature) shows that the people who most appreciate being recognized are often the ones least likely to admit needing it. The relevant recognition is not artificial (a plaque, a mention in the newspaper) but personal recognition delivered directly and, ideally, sincerely — though sincerity is not strictly required for it to work, since even manufactured praise designed to flatter someone as "a cut above the rest" produces the same effe. Once someone feels distinguished this way, they tend to talk more freely and at greater length than they otherwise would.

Self-Effacement as a Counterpart

The flip side of recognition-seeking is self-effacement — the "aw shucks" or "weren't nuthin'" response. People uncomfortable taking sole credit will deflect praise byxplaining in detail how a team or other individuals actually accomplished the result, or by describing how easy the achievement was (crediting new financing, new equipment, a kanban replenishment system, a kaizen process, etc.). Both deflection patterns are valuable: the first hands over names of additional sources to pursue; the second reveals substantive operational detail. Each subsequent source interviewed becomes easier to work because of what was already learned about their role and the underlying project from the first conversation. Recognizing and satisfying this need in others is described as a powerful mechanism for encouraging increasingly verbal responses.

Tendency to Correct Others

Ego suspension — previously established as a core elicitor trait — pays off most directly here. If a practitioner's real purpose is gathering information rather than protecting their own reputation for competence, they can deliberately make statements that are wrong or questionable, inviting correction. Teachers, supervisors, inspectors, auditors, coaches, and parents are classic examples of people conditioned to correct errors whenever they hear them. Being willing to appear mistaken, or even to accept correction, causes people with this trait to supplyurate data needed to complete a project.

Tendency to Prove Someone Else Wrong

An extension of the correcting impulse appears in argumentative, "true believer" personality types — found among loyalists of companies, organizations, religious groups, sports/fan clubs, or political causes who are convinced their institution or view is superior to all others. This goes beyond correcting a factual slip; it touches identity and personal investment. Defending their institution, they often wax equent about its superior processes, people, and successes, revealing substantive detail in the process. This approach works well with sources who display a bombastic or messianic style.

Discussing Matters Outside One's Direct Responsibility

People frequently possess information gained incidentally during normal work activities for which they hold no formal responsibility — for example, hearing about a new-product launch from another division while in the cafeteria. Because they have no personal investment in protecting information that isn't "theirs" (even material officially labeled sensitive, which in most cases they were never even told was sensitive), their motivation to guard declines sharply.

Absence of Listening Ears

Bartenders, social workers, and psychologists build careers on listening sympathetically to grievances from disgruntled employees, former employees, rejected job applicants, and losing vendors. Simply being a sympathetic listener in a world full of complaints yields substantial insight into a firm's operations without resorting to distasteful or illegal tactics like theft, bribery, burglary, or "waste archeology" (a polite term for Dumpster diving).

Chronic vs. Situational Dissatisfaction

• Chronic dissatisfaction can support a long-term, mutually beneficial relationship built on repeated conversations over time.
• Situational dissatisfaction appears only occasionally, requiring alertness to catch a transient window of frustration surfacing mid-conversation.

Warning: Dissatisfaction should not be relied upon exclusively, since it won't reliably present itself in every interaction — other characteristics and techniques still need to be in the practitioner's toolkit. More importantly, a disgruntled source's information is not automatically reliable; anger can produce exaggeration that misleads more than it informs. The chapter invokes Ronald Reagan's "ancient Russian proverb" — trust, but verify — as the operative caution.

Tendency to Gossip

Gossip and rumor remain intractable management problems, often prg early signals of mergers, acquisitions, new products, hiring/firing decisions, and financial shifts, both inside and outside a company. Cultural trends — described as the "Springerization of America" — have normalized discussing salacious or lurid details publicly, extending the sense that nothing is off-limits even to proprietary or sensitive information. Cheap phone connections and email act as "electronic water coolers," expanding both the opportunity for information collection and the difficulty of protecting information.

Notable cor-application: Some companies deliberately exploit this same gossip/rumor dynamic to spread false or misleading information to competitors, since informal channels avoid the regulatory scrutiny (e.g., SEC) that would attach to official misinformation.

Inability to Keep Secrets

Referencing Benjamin Franklin's observation that two people can only keep a secret if one of them is dead, this section argues that society is generally becoming more open, leaving fewer real secrets. Several forces drive this:

• A personal desire to be seen as "in the know," which can only be demonstrated by sharing access to secrets.
• A cultural shift where withholding information (e.g., a government official citing "national security") is now read as a cover-up rather than a legitimate justification — unlike decades past when such claims silenced further inquiry.
• The erosion of "Loose Lips Sink Ships"-style discretion culture, replaced by a culture celebrating information transmission.
• In scientific/technical circles, a belief that knowledge should rve mankind broadly and not be confined by borders undermines secrecy efforts.
• Rapid technological obsolescence (today's advanced PC becomes tomorrow's "doorstop or boat anchor") makes information-based advantages feel transient and not worth protecting.
• Declining employee loyalty, especially among those anticipating layoffs and already "shopping" themselves in the job market, further reduces motivation to protect a company's competitive information.

Underestimating the Value of Information Being Shared — and the Recipient's Ability to Understand It

This is described as a two-level tendency:

1. Underestimating the information itself: A source often cannot see the larger analytical picture the way a researcher can, so individually insignificant-seeming details are shared freely because their aggregatemportance isn't recognized. Even sources who understand the value of individual pieces of information often fail to grasp that the aggregate of many small pieces carries far greater significance.
2. Underestimating the recipient's intelligence: A concrete practical example is given from researchers working out of Alabama offices who call sources in the Northeast. Recipients sometimes assume that because the caller's accent or location signals lower intellectual standing, anything said "will be lost" on them, so they say more, believing it's inconsequential. Contrary to the expected response (hanging up), such "intellectually superior" sources tend to stay on the line and provide even greater enlightenment because they've underestimated the researcher. The key practical lesson: checking one's own ego at the door and letting a source feel intellectually superior can dramatically increase the flow of information.

Desire to Be Recognized as an Expert in One's Field

Virtually no one — welders, chief financial officers, secretaries, scientists — believes their role in a company is unimportant. People are rarely reluctant to claim at least partial credit for successes, and rarely reluctant to offer solutions they believe only they are qualified to ose. Everyone tends to believe they are among the best in their discipline, and often believes they have superior answers even outside their discipline — they simply are rarely asked, and when they are, their advice is only sometimes followed. The framing offered is that "what they know would fill a truck if only someone would listen" — meaning simply asking and listening unlocks substantial information.

Occupationally Derived Habits of Advising, Teaching, Correcting, Substantiating, hallenging

Many professionals occupy secondary roles — mentors, union stewards, reviewers of others' work — that condition habitual behaviors: giving advice, teaching what they know, or arguing points as a natural way of engaging. These habits become so ingrained that roughly two out of three sources display this orientationcording to field experience. Because the trait is so pervasive, it is one of the most commonly employed and tested approaches when planning first-time contact with an unfamiliar source.

Indiscretion When Emotions Are Not Under Control

While anger and fear can cause people to speak out of turn, introducing anger or fear deliberately is generally counterproductive because elicitation works best in comfortable, nonthreatening settings — unless handled with rl skill. More useful are positive emotional highs: enthusiasm (e.g., a manufacturing consultant seated next to someone on a flight who can't stop discussing a recent success) or defensive energy (people who perceive their firm under attack from unions, media, or election-seeking legislators can become so energized in defending it that they unconsciously step over lines of propriety). This emotional backdrop is described as especially powerful when combined with elicitation techniques covered in later chapters (6 and 7).

Professionals Sharing Confidences With, or Showing Off Expertise To, Other Professionals

Professionals such as lawyers and doctors are assumed to have the highest discretion and would seem invulnerable to elicitation about their practices — yet this assumption is explicitly rected ("Right."). Doctors, lawyers, and many other supposedly discreet professionals are frequently a "mother lode" of information. Several mechanisms explain why:

• Overconfidence in their own defenses: Being conditioned to deflect direct questions, such professionals may not recognize or guard against indirect elicitation methods, since they can't imagine other approaches exist. Absent direct questioning, they are no more alert than anyone else.
• Third-party orchestration between peers: Merely facilitating or listening to a conversation between two professionals in the same field (medical, legal, scientific, technological, consulting) lets a third party guide them into open discussion neither would otherwise volunteer. A concrete technique: deliberately orchestrate friendly competition between two peers — e.g., two heart surgeons, or two scientists at an international symposium — inviting one to explain an approach and then prompting the other to counter with their own. Absorbed in competitively sharing expertise, they pay little attention to the "moderator."
• Borrowed professional credibility: Being recognized as connected to an industry — for instaning enough of an industry's specialized vocabulary — can get an elicitor treated as a fellow professional even while operating only on the periphery of that discipline. Clinical researchers in pharmaceuticals are cited as one of countless examples where professional courtesy, invoked in the name of science and humanity, accelerates the flow of information.
• Hubris: Some professionals believe ordinary rules don't apply to them, and the pull toward gaining recognition from peers is too strong a lure to resist.

The chapter closes by noting that the discussion of which types of people are most and least susceptible to elicitation continues into the next chapter.

Chapter 5: Who Is Most Susceptible to Elicitation

Framing the Question

Elicitation training programs repeatedly ask two questions: who is most susceptible to elicitation, and who is least susceptible? The answers across thousan of respondents are strikingly consistent — so consistent that the questions are no longer even asked; the standard answers are simply presented up front. Understanding these patterns explains why certain people reveal more than they should, and it can broaden the pool of potential information sources beyond the obvious candidates.

The Most Susceptible Category

The top answers are consistently: factory workers, minor government officials, professors, and sales and marketing people. The mmon thread among all of them is that they generally don't handle especially sensitive information by their employer's estimation, so their organizations rarely invest time in training them to be discreet. Either the employer underestimates the value of what these people know, or the individuals themselves underestimate it. Either way, this lack of awareness — not any personality flaw — is what drives susceptibility.

Factory Workers

Factory-level sources hold a considerable amount of valuable information, though reaching them can be logistically harder since they aren't typically sitting at a phone during work hours (a topic addressed later, in chapter 11). They tend to be proud oeir work and willing to talk about it, in part because management rarely makes them feel important — explicitly or implicitly (e.g., through soliciting their advice). Despite this, they often possess deep, arcane knowledge of a business's inner workings.

By treating them as genuinely important — listening attentively rather than dismissing them as "just" workers — an elicitor can learn a great deal about new equipment, new processes, cost drivers, production rates and problems, inventory issues, and more. Critically, virtually none of these employees have ever been told that the information they handle daily has competitive value or sensitivity.

A real example: one supervisor reported that management explicitly instructed supervisors not to tell employees how valuable their information was, out of fear that employees would "brag" about their importance. This policy backfired completely ithholding a sense of importance, management also removed any employee incentive to stay silent about that information. If workers don't know they hold something worth protecting, they have no reason to protect it.

This "factory worker" category is not limited to blue-collar or unionized labor — it applies just as broadly to white-collar employees. Example: an accountant who works meticulously to produce an excellent financial analysis with supporting spreadsheets, only to be met with indference ("leave it here, I'll call if I have questions" — understood as code for "you'll never hear from me unless something's wrong"). Yet this accountant knows virtually everything about the company, because of the business intelligence principle that "wherever money moves, information moves along with it."

The broader less: many employees across a firm know significant operational details but have never been conditioned to appreciate the value of what they know — a conditioning often reinforced by pay level and position in the corporateierarchy. While managers pursue harmonious relationships with staff for operational efficiency, there's a stronger unstated incentive to build employee trust and encourage independent thinking — echoing the leadership principle "we teach themorrect principles and let them govern themselves."

Minor Government Officials

Lower-level government employees are a uniquely resented population — frequently seen (fairly or not) as lazy, venal, or incompetent, and unable to publicly defend themselves because their superiors instruct them to avoid antagonizing the taxpaying public.

A key practical and psychological challenge for the elicitor: suspending personal disdain or impatience toward a bureaucrat (e.g., after waiting in a long line) in favor of the mission. This requires setting aside not just ego but any "inner fury" toward an unpleasant functionary in service of the larger objective.

Illustrative literary example: a passage from John le Carré's Our Game, in which intelligence officer Tim Cranmer tolerates the bigoted rants of an obious informant, Ockie Hodges, for fifteen years — not out of personal affection, but because the relationship serves "a safer, wiser England." The lesson: professional focus on mission over personality is what enables sustained access to difficult or distasteful sources.

Practical rationale for cultivating minor government contacts: government agencies possess exceptionally valuable information about companies. While the Freedom of Information Act provides access to some records, direct rationships with the people who administer that information — and who have access to non-FOIA-available material — are far more valuable. A further practical point: government promotion systems reliably advance people over time regardless of merit ("largely designed to reward mediocrity"), so a minor official cultivated today hold greater access and responsibility later — making early relationship-building a long-term investment. A footnoted joke acknowledges that any government-employee reader will assume this description applies only to "that person down the aisle," never to themselves.

The chapter draws an explicit parallel: many other bureaucratically-structured roles — in nofits, public-interest groups, or even within one's own industry — share the same conditions of imposed drudgery and low morale that make government workers susceptible, and should be considered as equally exploitable sources.

Professors

Professors are especially susceptible because of a fundamental need to teach — and the more a person appears to be a sincere, student-like inquirer, the more opportunity exists for engagement. This does not require literally posing as a student; simply adopting a genuinely curious, student-like demeanor is enough.

Academic susceptibility is amplified by several converging traits:

• A love of knowledge for its own sake and a desire to be seen as its primary purveyor.
• Resentment of administrative constraints, especially any restriction on the free growth of knowledge or science — this makes many academics dismissive of concepts like proprietary informa- Publish-or-perish pressures and career-advancement dynamics.
• Ordinary faculty ego.

These traits are not unique to academia; readers are encouraged to identify other groups sharing the same orientation and vulnerability. A forward pointer notes that chapter 10 will revisit academic-type sources in more depth, showing that actual professors — not just people who resemble the "professorial type" — can be highly useful as sources.

Sales and Marketing Types

The most common (and superal) explanation offered for this group's susceptibility is simply that "they talk too much" because talking is their job. But deeper factors are at play:

• Sales and marketing professionals often know, well in advance, what is going to happen in their company months or years out, because they must prepare the market ahead of time. They are typically ahead of the information curve, not behind it.
• Their compensation is tied directly to marketplace performance, giving them an incentive to impress the market with insider knowledge of what's coming — a motive that can be secondary to, or overridden by, the drive to demonstrate their own cleverness and connectedness.
• Personality traitshat make them effective at their jobs — high energy, extroversion, low orientation toward careful planning, comfort with ambiguous give-and-take — are the exact same traits that make them vulnerable to a well-planned elicitation approach.

A key non-obvious point: confidence in operating "without notes" (i.e., improvisational skill) is itself a vulnerability against someone who has planned the interaction carefully — an echo of the classical concept of hubris, where confidence in one's own superiority creates blind spots.

The (Supposedly) Least Susceptible Category

A Mark Twain epigraph sets up the section's thesis: "No generalization is worth a damn — including this one." The common belief that lawyers and doctors are the professions least likely to overshare, due to ethical and legal confidentiality obligations, does not hold up in practice. Both groups are especially prone to a prediscussed tendency: professionals confiding in other professionals, particularly where an undercurrent of competition exists between them.

Lawyers

Practical approaches for eliciting from attorneys:

• Learning to speak the profession's common vocabulary is often enough for an attorney to begin treating the conversation as one between peers, which opens them up considerably.
• This does not work easily or reliably in every case, and it essentially never works in an attorney's office or during billable hours — the setting and timing must be chosen carefully, consistent with the situational dependence of successful elicitation discussed earlier in the book.
• It's not difficult to identify which companies are represented by a given law firm; the practical challenge is identifying the right lawyer to approach.
• n-obvious tactical point: it is often better to approach an attorney who is not personally handling the target case, rather than the lead attorney. Reasoning: professionals share confidences with peers more freely, and people with no direct personal or professional stake in a matter tend to diminish its sensitivity and speak more freely about it.
• The overall approach mirrors standard elicitation planning: plan the outcome, plan the approach, plan techniques, and prepare sufficient background knowledge before proceeding.

Doctors

• Physicians met socially, rather than professionally, are described as prime practice subjects for elicitation — specifically for getting them to violate basic patient confidentiality, such as revealing a patient's identity. This is framed as low-risk since the information typically has no practical personal or professional use afterward.
• An important exception is doctors serving as clinicians in drug trials. Despite being bound by non-disclosure agreements, the real question isn't whether NDAs exist but whether they are actually followed — and the implied answer is that compliance is unreliable.
• As with attorneys, building the necessary vocabulary and rapport with doctors requires ongoing social contact rather thanfessional interaction.
• Several psychological levers apply to physicians: most consider themselves scientists, and the earlier-discussed notion that "science knows no boundaries" and exists purely for the good of mankind can be leveraged; the "doctor as teacher/professor" framing (paralleling the professorial susceptibility discussed earlier) is another usable angle.

Broader Takeaway

Groups reputed to be discreet, smart, and hard to elicit — lawyers, doctors, and by extension senior binesspeople, senior government officials, and even national or commercial intelligence officers — share the same underlying class characteristics that create susceptibility once combined with the right elicitation techniques (to be covered in subsequent chapters). No profession or reputation for discretion is truly immune; sceptibility is a function of situational and psychological factors, not job title.

Chapter 6: Your First Six-Pack of Elicitation Techniques

Framing and Approach to Learning

This chapter delivers the first six of roughly three dozen elicitation techniques, chosen because they are among the easiest to learn and master. A companion set of six more complex techniques follows in the next chapter. The recommended approach is incremental: begin mastering the techniques that feel immediately comfortable, then add one or two more as confidence grows. Even seasoned intelligence and law-enforcement professionals often discover they've been using pieces of these techniques instinctively but "in a haphazard and unorganized way" — the goal here is to formalize and sharpen that instinct into deliberate skill. A key long-term objective is technique-stacking: moving fluidly from one technique to another within a single conversation, since repeated overuse of any single technique becomes noticeable and self-defeating.

Technique 1: Provocative Statement

A Provocative Statement can be as short as one sentence or as long as a paragraph or short story, delivered at the start of a conversation or inserted at any chosen point laterDespite the name, it isn't meant to be offensive (though it occasionally can be, deliberately, with specific sources).

It serves two purposes:

• Engendering a question directed at the elicitor — if a source ever becomes suspicious about why a topic is being discussed, the elicitor has a built-in, innocent defense: "You're the one who asked me about X." Most people will genuinely remember it that way.
• Setting up another technique — this is the more common and valuable use. The Provocative Statement is most uently used to launch into Quid pro Quo, Naivete, Disbelief, or Criticism.

Illustrative examples show the mechanics:

• Provocation → Quid pro Quo: A comment about long tenure at a company ("I really wonder why I've stayed so long") invites a reciprocal question, which becomes a springboard into learning about the source'own career history and reasons for staying.
• Provocation → Naivete: Confessing confusion about pricing ("It always seems like black magic to me") draws out an expert (often someone who enjoys teaching/mentoring) to explain cost-accounting details, moving the conversation from macro/abstract to specific, personal detail.
• Provocation → Disbelief: Exping disbelief about a market or regulatory situation invites the source to share a parallel experience from their own company or agency.
• Provocation → Critism: Criticizing a competitor or unrelated party (e.g., poor ISPs) provokes a defensive reaction where the source reveals proprietary details about their own investments (e.g., "we've just put $1.5 million into new hardware").

Warning/consistency principle: Whatever approach is chosen (naive, disbelieving, critical) must be applied consistently throughout the exchange. Breaking character — e.g., suddenly gushing "No kidding? Really? Tell me more!" — destroys the elegance of the approach and can tip off the source.

Technique 2: Quid Pro Quo

Described as an old Roman Legion Intelligence Service technique ("I'll show you mine, if you show me yours"). It works best when preceded by planning and launched via a Provocative Statem offering maximum information with minimal suspicion.

Planning components:

1. Deciding what to disclose and how to transition — the elicitor must plan how to shift focus naturally onto the source (e.g., referencing shared background such as military service to open the door to the source's own career).
2. Backstopping — the practical viability of maintaining a fabricated history if the source tries to verify it. This is described as impractical and largely unnecessary in most. business contexts, and "not for the faint of heart."
3. Knowing your own limits ("how far you'll go") — a real risk scenario ("Turnabout Is Fair Play") is detailed: an elicitor opens with a rehearsed, safe disclosure about their own company, expecting reciprocity, but instead the source turns the tables and asks probing flow-up questions. Without advance planning on what can safely be disclosed, the elicitor is caught flat-footed and risks over-disclosing out of anxiety about appearing suspicious.
4. Topic knowledge — illustrated ba scenario where an elicitor references a fabricated ancestor's Civil War military service, only to be cornered by a source who is a Civil War buff asking for regiment specifics. The lesson: if caught without an answer, simply admit not knowing rather than compounding the error with further fabrication; treat it as a lesson for better preparation next time.

On ethics and legality of misrepresentation: It is stated that misrepresenting one's identity to collect business information is not illegal in the U.S. business world (though it may be unethical, immoral, or distasteful) — a comparison is drawn to headhunters and various other professionals who commonly use ruses. However, a caution is raised about the internal cost to one's own company of institutionalizing misrepresentation/cover stories: companies that have trained researchers in elicitation as an alternative to identity fabrication did so because idealistic researchers objected to ruses on personal grounds and underperformed, or because employees left for competitors over eical disagreements — notably, these objections often surfaced from HR, sales/marketing, and purchasing departments, not just business-intelligence staff. A reference to John le Carré is invoked: no one is less convincing in "our wretched trade" than the blameless person with nothing to hide — implying people are naturally attuned to detecting deception, which counsels caution about full fabrication.

Best practice for cover stories: if a persona or claimed background must be used, itld be built as close to the truth as possible, since professional deception training (used by intelligence/undercover officers) emphasizes exactly this — straying too far from real life multiplies the chance of costly mistakes.

Variant technique — Reflected Quid Pro Quo: Instead of claiming a fabricated personal experie refer to someone else's real experience (a father, grandfather, uncle, neighbor) who actually had the background in question (e.g., military service). This allows the elicitor to legitimately claim ignorance of fine details, reducing the planning burden and risk — since any inaccuracies are naturally explainable and don't require sustained backstopping. This varnt pairs well with subsequent use of Naivete or purposely False/Erroneous Statements as stacked techniques.

Technique 3: Simple Flattery

Grounded in the premise that "everybody enjoys a little [flattery] sometimes, and many would like it all the time" — applicable regardless of job level, from welder to CEO. Flattery is especially potent when stacked with other techniques.

Two ends of a spectrum of response:

• At one extreme (illustrated with a Dilbert-style "pointy-haired manager" reference), the flattered person is oblivious to the transactional nature of the compliment and simply absorbs it as validation of their brilliance/leadership — this type is easy to exploit for further conversation.
• At the other extreme, genuinely deserving, sincere flattery prompts a self-effacing response, where the person deflects credit toward others or toward external factors. This deflection is ally the useful opening: it invites the elicitor to press further ("Come on, that couldn't have happened without someone knowing how to..."), which draws out increasingly specific detail (illustrated in the plant-foreman example, where flattery about production improvements draws out a full narrative including throughput numbers: from 22-hour to 3-hour-20-minute cycle times).

Practical mechanic: The initial self-effacing/minimizing response to flattery should not be accepted at face value — a follow-up push ("attributing credit back to the person") typically converts the deflection into a detailed explanation of exactly how the achievement was accomplished.

Gender dynamics warning (explicitly framed as a generalization, with a caveat citing Mark Twain that "no generalization is worth a damn — including thne"):

• Woman-to-woman flattery draws the least suspicion and greatest acceptance.
• Man-to-woman flattery risks unwanted overtones (described as "leering," which must be avoided) that can derail the nonthreatening, unmemorable nature the technique requires — though it can still work if delivered with deftness inside a stack of techniques (one training video reportedly used nine flattering statements in a row without disrupting the conversation).
• Man-to-man flattery is the most problematic, since men tend to distrust compliments from other men, anticipating a hidden agenda ("Okay, whattaya want?") — success requires extensive rehearsal so the flattery feels wholly natural.
• Woman-to-man flattery is likened (with tongue-in-cheek acknowledgment of dropping political correctness) to "a dog rolling over to have his belly rubbed" — implying strong effectiveness.

Technique 4: Exploiting the Instinct to Complain

Premised on the observation that most people in workplaces gravitate toward griping rather than praise (the "Nation of Whiners and Snivelers" framing) — meaning an already information-rich environment is made richer because so many potential listeners tune out complainers, leaving a receptivpecially valuable ("in the land of the deaf, the one-eared man is king").

Key target populations for this technique extend well beyond current disgruntled employees:

• Retirees who feel "put out to pasture" and want to feel valuable again by sharing expertise.
• Former employees, temps who resent benefit disparities, unpaid suppliers, and real estate agents who lost a deal at the last minute — all are documented sources of competitively valuable information.
• Executives/leadership have a different motivation foromplaining — about boards, unions, regulators, or public-interest groups — and their complaints, though delivered at a "higher level," are often underappreciated as sources of operational insight.

Case study — the retired worker ("Sweet Retirement"): A retiree contacted via a company newsletter's "where are they now" e section turned out to be bitter — not about his own retirement, but because his adult son had been laid off from the same plant. Though the son knew little useful, the father maintained close ties with former colleagues (including a bowling league) and, once treated as a valued expert rather than an outsider, voluntarily toured the plant to gather updated infoation on new equipment and volunteered to continue reporting findings. This "self-recruitment" pattern recurred in seven or eight other cases where former employees maintained ongoing, unsolicited reporting relationships for years — the account notes that information continued flowing via monthly-to-bimonthly calls three years after the original project concluded, and that no one had actively encouraged or discouraged this continuation.

Case study — the departed comptroller: An executive who quietly left a firm (ostensibly "to pursue other interests") had actually resigned rather than continue signing false and misleading financial documents. Because the company made no effort to secure his ongoing silence (no continued compensation, no confidentiality agreement), he felt no loyalty and was willing to speak in detail about the company's true financial condition to a sympathetic listener formation with potential SEC-level implications. The lesson embedded: companies that fail to manage the exit of employees with sensitive knowledge (financially or otherwise) create exactly this kind of high-value, motivated source.

Explicit ethical framing: No claim is made to actively foment discontent or run "fifth column" operations inside a target company — companies are said to do quite enough of that to themselves through poor employee treatment. Information collectors simply idtify and listen to those who already have "an ax to grind."

Technique 5: Word Repetition

Borrowed conceptually from active-listening training (where repeating a partner's key word/phrase signals attentiveness and encourages elaboration) but adapted for elicitation with important modifications.

Why straight repetition is risky in elicitation: Active-listening-style repetition is an overt signal of interest — exactly what elicitation wants to avoid, since drawing attention to the importance of a statement undermines the goal of appeing uninvested. There's also a real risk that a source trained in the same active-listening techniques will recognize the pattern and interpret it as a "management technique," triggering suspicion or condescension.

Elicitation adaptation: Rather than parroting the exact word or phrase, reformulate the idea using synonyms or a paraphrase that captures the same content without the source recognizing their own words reflected back. Example: instead of repeating "advanced degrees" verbatim, respond with something like "Ah, graduate school. A good time had by all." This achieves the same prompting effect while also allowing the elicitor to withhold their own personal details (saving them for a future Quid pro Quo exchange) rather than "wasting" that information immediately.

Silence as an amplifier: After a whimsical or under-elaborated reformulation, deliberately leaving silence (ten, fifteen, even twenty seconds) tends to make extroverted sources rush to fill the gap with elaboration — people, especially extroverts, are described afinding silence acutely uncomfortable.

Emphatic Loading — a sub-variant where the tone or inflection used in the repeated word/phrase itself provokes different responses. Example: repeating "Jim Johnson?" with skepticism about whether he could have won the Congressional Medal of Honor invites either a defense of Johnson's heroism, an awe-tinged elaboration on the award itself, or a defensive/corrective response — the specific emotional coloring (skeptical, awed, dismissive) shaphich direction the source's elaboration takes. The technique's flexibility lies in intentionally choosing which word to emphasize and what emotional tenor to attach to it.

Technique 6: Quotation of Reported Facts

Exploits the modern information glut and the social aversion to appearing to be "the last one to know" — nobodyants to seem uninformed about their own company, industry, or field, since knowledge signals status.

Core mechanism: Reference something purportedly "reported" (in media or elsewhere) about the target topic — regdless of whether the reported information is actually accurate, or even whether it exists at all. What matters is only that the source believes it might be true or already public, which lowers their guard against discussing it.

Contrast with journalism's clumsy version: Journalists are trained to ask directly, "Will you comment on reports that your company is laying off ten thousand employees?" This is criticized as too blunt — it reveals exactly what's being sought, creates a memorable confrontational moment, and the source will recall being directly questioned. Elicitation's version embeds the "quoted fact" within a broader, comfortable conversation, having been set up by other techniques first, so it doesn't stand out as a spotlighted, confrontational question.

Three predictable source-response types (illustrated via a repeated scenario about supposed earnings/production problems at a Kuala Lumpur facility):

1. "In the Know" — a knowledgeable long-tenured employee corrects the "wrong" media figure and volunteers acte specifics (e.g., correcting an 8% figure and redirecting blame to different plants).
2. "Slightly out of the Know" — someone without earnings knowledge but with adjacent operational experience volunteers detailed complaints about a related facility (equipment costs, capability gaps).
3. "Out of the Know" — someone with no knowledge of the specific topic redirects to whatever problems they do know about (different production line issues), rather than admit total ignorance.

ll three cases, the desire not to appear uninformed produces useful disclosure regardless of actual expertise level.

Variants and tactical notes:

• The "quote" doesn't need to come from print media — broadcast/electronic media works too, and accuracy of the quote is often irrelevant; reporters themselves frequently misque or cite vague/unverifiable sourcing when pressed.
• A personal variant — the "my friend John" approach — substitutes a claimed conversation with an acquaintance for a media report, exploiting the same psychologicachanism.
• Tactical sequencing tip: Opening with a genuine, verifiable, moderately-related media quote first establishes credibility ("this person actually reads/pays attention"), which then transfers credibility to a subsequent fabricated or unverifiable "quote," making the source more likely to engage with and comment on it.

Practice and Skill-Building ("Revenge-Based Training")

Practical field-testing is strongly encouraged before applying these techniques in real business settings, framed as low-risk, high-confidence-building exercises. A personal anecdote describes practicing techniques during intelligence training by frequenting working-class bars near factories (steel mill, GM plant, soap factory, distillery) and using patrons as unwitting practice subjects — arriving before shift-change so as not to visibly "penetrate their space," letting them naturally form around him at the bar. The content extracted (money problems, relationships, job gripes) was not itself valuable — the value was purely in the deliberate practice refinement of technique.

Recommended practice targets in seminars: waitresses/waiters, bookstore/department-store clerks, florists, pharmacists, fellow customers in line, even a traffic officer who unwittingly disclosed requested information while issuing a ticket.

Practice goals to extract in exercises: name, age, occupation, employer, likes/dislikes about the job, education, and annual compensation — described as consistently achievable within a single lunch-hour exercise by thlarge majority of trainees, with many extracting all of the target data points.

Key practical guidance: Before practicing (or before any real elicitation attempt), decide specifically what information is being sought and which techniques will be used — attendees consistently report that a few minutes of upfront planning mas the exercise far easier than anticipated. The eventual goal is to build a personal "stable" of techniques matched to one's own comfort and personality, progressing toward stacking multiple techniques within a single conversation so transitions between them feel seamless and natural — comparable to a master strategist moving fluidly between tactics.

Chapter 7: Your Second Six-Pack of Elicitation Techniques

Following practice with an initial set of elication techniques, this chapter introduces six more methods for drawing information out of a target without relying on direct questions. A recurring observation opens the chapter: even seasoned practitioners tend to fall back on ordinary questions more than they realize, and doing so rarely triggers suspicion because targets seldom notice being questioned more than expected. The chapter frames each technique with detailed mechanics, real transcript examples, and cautionary anecdotes.

1. Naivete

Naivete is described as one of the hardest techniques to master specifically because it depends on genuinely suspending ego — resisting the urge to demonstrate education, experience, wisdom, intelligence, or achievements. Three elements make it work:

• Ego suspension as the foundation. The elicitor st be a collector of information, not a collector of ego strokes.
• Feigning, not faking. The goal is to appear less threatening, less accomplished, and less knowledgeable than one actually is — without going so far over the top that it becomes a caricature (the example given: a flirtatious cliché like cooing over an accountant's ability to "remember all those numbers" is dismissed as too obvious to count as real Naivete).
• Naive does not mean stupid. Genuine, believable gaps in wledge exist for everyone — nobody understands every technology, industry, science, or art. It's entirely plausible to know little about a subject like laser optics and carry that gap without shame.
• Paradoxically, effective Naivete requires real background knowledge of the target subject. Enough understanding is needed tfollow where the conversation is going, recognize valuable information when it surfaces, and steer the exchange — even while appearing to know little.

Warning — knowing too much is a real risk. An anecdote recoua seminar attendee who successfully built rapport using Naivete at a trade show, only to blow his cover by using an "industry-common but otherwise unusual jargon phrase" that no genuine naif would know. Both he and his source realized the slip at the same instant, ending the elicitation's credibility. The lesson: staying convincingly on the ignorant side of the line matters as much as building the naive persona in the first place.

Regional accent as an asset. A practical, non-obvious application: trained elicitors from an Alabama office deliberately keep their regional accent when calling people elsewhere in the country, because it accelerates Naivete — particularly with someone (the "New Yorker" archetype in the text) who is inclined to feel superior and therefore lowers their guard while unconsciously "educating" someone they perceive as less sophisticated. The point isn't to take offense at condescension but to exploit it: the job is extracting the client's needed information, not winning respect.

2. Oblique Reference

Oblie Reference goes a step further than merely avoiding direct questions (which is true of nearly every technique in the book) — it involves making comments about a related topic to exploit the natural tendency, described earlier via the "conversational hourglass" concept, for people to move from general/abstract statements to specific, personal ones grounded in their own professional experience.

• Core mechanism: The only way a source can fully describe something is by drawing on theiown actual professional situation. An opening oblique topic works because it seems too unimportant or general to feel threatening.
• Valence doesn't matter. The oblique topic can be raised either positively or negatively — either framing works to trigger the transition to specifics.

Extended example — "OSHA Ain't for ybody": An elicitor opens with a Provocative Statement about being burned out from a Little League coaching assignment, mentioning an assistant coach (a safety engineer) who'd been sidelined for three weeks by an OSHA inspection. The source, an engineer at an electronics manufacturer, volunteers his own OSHA experience — an inspection halting production over a Freon-like chemical, forcing a production line reengineering, costing an estimated $200,000, and delaying a $12 million chip technology contract by a month. The elicitor never asks a direct question about the plant; the target discloses competitively sensitive operational and financial detail purely by following the oblique thread back to his own situation.

Non-obvious point — maintaining consistency is essential. Because showing overt interest in the target's actual answer would tip off what's really being sought, the elicitor must remain "consistently" more interested in the oblique topic (baseball) than the real target (plant operations) — including steering the conversation back to the oblique topic (kids' playoffs) once the needed information has surfaced. The stated objective: the source should leave the conversation believing nothing of substance scussed at all — in the OSHA emple, the target's likely recollection was "five minutes of common talk" plus "baseball," with no memory of having revealed plant operating problems.

3. Criticism

Criticism is most effective on people who have a substantial personal investment in what's being criticized — loyal employees, those with significant career or financial stakes in a firm, or those with limited outside options — though it applies more broadly than that description suggests.

• Rapport is a prerequisite. technique requires enough established rapport to "push on the edges of the envelope," ideally in a jocular tone, and works best when the elicitor already has a read on how the source responds to teasing in unrelated areas (e.g., joking about the safety of a helicopter "constructed of twenty thousand parts assembled by the lowest bidder" as a low-stakes calibration test before escalating).
• Escalating range of criticism. Start casual and inconsequential, then move toward genuinely sensitive "hot buttons" specific to the industry or individual.

Extended example — "The Cable Guy": Before the conversation, background research identified that cable industry professionals' biggest t button is programming/content — not service, competency, or price. The elicitor opens with a Provocative Statement criticizing generally poor local cable service, drawing out an expected defensive question ("What's wrong with it?"). A escalating list of complaints follows (late installers, hygiene, outages) that draws no reaction — until "lousy programming" is added, which finally provokes defensive engagement. As the target defends upcoming content investments, the conversation naturally moves toward the associated cost — a rate hike not yet publicly announced — six months ahead of when the company would formally request approval from the local governing board.

Non-obvious point — background research fuels the approach. Effective Criticism depends on maintained organizational data about individuals, companies, and industries accumulated across prior projects — described as matin Appendix F, "The Job's Not Done Until the Paperwork Is Complete." Knowing a target's industry-specific pressure points in advance is what allows criticism to be aimed precisely rather than generically.

4. Bracketing Techniques

Bracketing is used specifically for eliciting quantifiable information (numbers, dates, rates) and requires advance planning even though its actual deployment moment in conversation is often ambiguous or unplanned.

• The "Goldilocks" range principle — not o big, not too little. The initial bracket should be realistically wide. In the Cable Guy continuation, the elicitor opens the numeric range at $5–$35/month for a rate hike — wide enough to be non-threatening, but bounded by realistic knowledge (no cable company pursues a $2 increase; $50 is implausible; even $35 seems hig- Why width matters — the two failure modes of a narrow bracket: If a narrow range (e.g., $5–$7) is far off, the source has no incentive to correct it toward accuracy; if it happens to be dead-on, the source becohyperdefensive and shuts down the flow of information entirely. A wide initial bracket avoids both traps and, once acknowledged as being "in the right ballpark," sets up narrowing via an interim bracket.
• Narrowing through pressure, not surrender. When the source in the example offers "the lower end" of the $5–$35 range, the elicitor doesn't just accept a modest reduction (e.g., $7) — instead they counter with a challenging middle figure ($15) to force greater commitment, prompting the source to counter more precisely ($10–$11).
• Exploiting personality/background traits for final precision. Knowing the source held an electrical engineering degree, the elicitor leverages a generalization that engineers value precision and are economical (playful jab about polyester clothing from budget retailers), then frames a hypothetical ("if it's ten or eleven, will you personally cover the difference?") that appeals to the source's aversion to out-of-pocket cost — producing a highly specific final answer ($13–$13.50).
• Applicyond price. The technique generalizes to any quantifiable target: product rollout dates, compensation ranges, production rates, personnel turnover, rejection rates, etc.
• Military/shooting analogy for memorability: For those with a sighting-weapons background, Bracketing maps to "Fire Long, Fire Short, Fire for Effect" — successive adjustments converging on the true target.

5. Feigned or Real Disbelief

This technique exploits the near-universal human desire to be believed, regaless of whether the target actually holds high personal standards.

• Mechanism: When someone's veracity is challenged even slightly, a defensive instinct kicks in, and the natural defensive response is to supply more supporting background, data, and detail — precisely the information being sought.
• Related interrogatioprinciple (non-obvious): An old interrogator's trick is cited — falsely accusing someone of an unrelated wrongdoing, because in the act of disproving that specific accusation, the person can inadvertently implicate emselves in the matter actually under investigation.
• Timing matters. Disbelief should not be deployed as an opening move; it works only once rapport has been established, deep enough into the conversation that the confrontation doesn't feel like a direct, out-of-nowhere challenge.
• Delivery flexibility. Feigned Disbelief can be embedded directly in a Provocative Statement, escalated gradually along a preplanned line, or tied to visible emotional investment in the topic.

Extended example — "The Headhunter Two-Step": During a remote psychological profile of a newly hired competitor executive whose prior employer had a strict no-comment policy about him, an elicitor engages a recruiter (not the one who placed this particular executive, but someone in the industry) with escalating skeptical statements ("I can't believe Hogbreath let Jones get away... a techie like that couldn't be the key to turning a company around... I'd think shareholders would be upset"). Each disbelieving statement provokes the recruiter to defend thelaim with more detail, culminating in disclosure that the executive left his prior company due to inappropriate off-hours conduct with summer interns — covered up to avoid a lawsuit.

Underlying principles identified for why this specific source talked:

• The source had no personal stake in the actual placement being discussed, reducing his sense of risk in sharing.
• Professionals in the same trade circle (recruiters) tend to share information with one another as a professional courte/habit — the source had learned the story while filling the resulting vacancy.
• People who know even part of a secret often have a behavioral tendency to reveal it under the right prompting.

6. Purposely Erroneous Statement

Like Naivete, this technique requires ego suspension, but works by deliberately stating something ong to provoke correction rather than by appearing ignorant.

• Psychological levers exploited: the desire to correct someone, the desire to teach, the desire for detail/precision/closure, and behavioral tendencies already seen with Feigned Disbelief.
• Example mechanics: stating a factory "couldn't possibly make more than five hundred units a week" prompts a defensive correction revealing real capacity figures (1,135 units/week with new machinery), which in turn invites further erroneous jabs about high personnel costs and building expenses — each provoking more specific corrective disclosure (a dedicated cost center, competitive rate structure versus ten rival companies, discounted "fire sale" building costs, floor space half that of the main facility, plans to relocate more staff there).

"My Friend John" variant. For elicitors not yet comfortable enough to suspend ego fully for Naivete or a direct erroneous statement, this variant — attributed to psychotherapist Milton Erickson — offers an alternative: ascribe the experience, frailty, misunderstanding, or foolish trait to a third party ("my friend John") rather than oneself.

• Erickson used this to keep professional distance from his clients while still drawing them into openneohn" was never present and never directly involved with the client — a fully detached persona.
• Practical tip: using a real person (with the name changed to protect them) as the fictionalized "friend" gives the story more natural, convincing texture than a fully invented character.
• The variant also provides cover under a related technique (Quid Pro Quo) when the elicitor lacks real expertise to trade — since "my friend" had the actual experience, the elicitor can plausibly claim to know all the details personally.

Practice Anecdotes and Warnings

Two cautionary/illustrative field stories close the chapter, both underscoring the need to prepare for elicitation attempts turning around on the elicitor:

• The FBI officer in Georgetown. A young FBI foreign counterintelligence officer, confident in his social skills, went out alone without preparing for the possibility of being targeted himself. He struck up a conversation with an attractive Russian woman at a bar who, after building rapport for a while, asked what he did for a living — at which point a heavyset man with no neck sat down beside her, was introduced as "her friend Ivan" (also her boss/ntor), and the same question was repeated. The story is presented as a lesson in preparing answers for questions a target might ask in return, since the officer clearly had not planned for being on the receiving end of an elicitation attempt.
• Military intelligence officers at a biker bar. In a bolder counterexample, several officers deliberately chose a high-pressure environment (a biker bar) precisely because falling back on comfortable direct-question habits would be immediately risky there. They reportedly succeeded both in surviving unscathed and in extracting the sought information — plus free beer — attributed by the narrator partly to "excessive confidence."

Standard practice targets. The information categories used in these practice exercises mirror those introduced earlier in the book: name, age, marital status, number of siblings, number of children, birthplace and oridetails, education level and area of study, current employment, job likes/dislikes, salary or compensation, current bank and account number or credit-card number, and — as a bonus challenge — a PIN number. The explicit purpose of collecting this sensitive personal data in training is not to misuse it, but to build the elicitor's confidence in obtaining information that is typically difficult to get.

Chapter 8: Intelligence for Decision Makers

Defining Competitive Intelligence Corly

Competitive intelligence is frequently mischaracterized as simply gathering information about a competitor, analyzing it, and using it to gain advantage. This narrow framing actually describes a subset that should more precisely be called "competitor intelligence." True competitive intelligence is broader: it operates as a cyclical, disciplined process — decision makers ask focused questions, receive timely and reliable processed answers, and use that intelligence to avoid marketplace surprise and to prevail. It differs sharply from industrial and economic espionage (illegal, immoral, unethical practices covered later in the book) and differs from market research, which maps only cusmer buying habits, trends, and opportunities rather than the full competitive landscape.

The Expanded Scope of Competitive Intelligence

Beyond studying competitors directly, the discipline extends across the entire "competitive universe," including:

• Customers, their leaders, and decision makers — using gathered information to shape pricing, delivery, product development, procurement decisions, and business strategy/tactics.
• Merger and acquisition candidates, joint-venture partners, and team partners for competitions ranging from product development to defense and aerospace procurement.
• Regulatory environment factors, to anticipate changes that could profoundly affect an enterprise or entire industry.
• Emerging technologies and their potential impact on the competitive environment and a firm's ability to survive.

National-Level Intelligence Practices as a Model

Business intelligen mirrors the same broad spectrum that national intelligence services monitor for national survival: political, military, economic, and technological — often targeting not just adversaries but allies as well.

Several statements from foreign intelligence officials illustrate how other nations blend national intelligence apparatus with economic interest:

• Pierre Marion, former head of France's DGSE (Direction Générale de la Sécurité Extérieure), echoing Charles de Gaulle's "France has ns; France has only interests," stated that gathering intelligence on economic, technological, and industrial matters from an allied nation is not incompatible with being allies. After public uproar over the DGSE's Service 7 penetrating Texas Instruments in 1992, Marion defended the practice as essential for France to keep pace with international commerce and technology, explicitly noting that while allied in defense, nations remain economic competitors.
• Count Henri de Marenches (DGSE head, 1970–1981) wrote in his memoir that espionage is ineasingly focused on business, economy, science, and industry — and is highly profitable, since it can let one country instantly acquire a process that cost another years and possibly millions of francs to develop. He states plainly this form of espionage occurs among friends as well as enemies.
• A spokesman for Japan's Ministry of Trade and Industry (MITI) commented in 1985 that Japan lost WWII partly due to superior American intelligence networks and strategy, and expressed bafflement that American businessmen fail to replicate that same intelligence discipline against Japan today. Japanese government and industry approach competitive information collection and analysis in an organized, encompassing way precisely because business competition is treated as a form of warfare — with cooperation for the national interest against foreign interests.

A practical detail: Marion himself, prior to leading French intelligence, served as an Air France senior executive in Atlanta and acted as a willing "Honorary espondent" for French intelligence — illustrating how business cover roles can double as intelligence collection posts. This chapter also establishes that "internal sources" and "correspondents" will be used interchangeably throughout the rest of the book.

Why American Business Avoids Government Intelligence Involvement

American business has consistently resisted having the U.S. federal intelligence community actively collect, analyze, or disseminate competitively valuable information, for several converging reasons: Senator Daniel Patrick Moynihan (D-NY), on the Senate Intelligence Committee, challenged a Clinton-era push to assign such duties to the CIA by noting the CIA had been repeatedly wrong on major political and economic questions for a quarter century, questioning why anyone would want their analysis.

• At the operational level, Clandestine Service case officers reportedly told then-CIA Director Robert Gates they would spy or die for the United States, but not for a private company like General Motors — revealing a professional reluctance to ri personal safety for corporate rather than national interests.
• Business leaders who have testified on the matter prefer not having the CIA as a potential liability while operating internationally, based on hard experience that government involvement always carries unwanted strings attached, whether or not that belief is accurate.
• Practical/reputational risk: if evidence surfaced that a company was a front for CIA operations, it would severely damage public/product acceptance — an especially ironic outcome given decades of left-wing accusations that companies were CIA fronts. Further, while a country can tolerate a couple of intelligence officers being declared persona non grata (PNG'd), a company cannot absorb that level of reputational and operational damage, and such an incident risks harming the company's fortunes across an entire region, not just the host country.

The practical conclusion for American business: rather than seeking government intelligence support, firms are far better served building an internal intelligence coetency or engaging a specialized consultancy.

The Society of Competitive Intelligence Professionals (SCIP)

SCIP, founded in Washington, D.C. in 1986, exemplifies how American business responded to the need for a more rigorous understanding of its competitive environment. Key facts and non-obvious details:

• By the end of 1998, membership approached seven thousand active professionals, the majority based in the United States.
• Despite being headquartered near the federal intelligence establishment, SCIP's founding population and majority membership even a decade later did not originate from the intelligence community — instead its initial base came from librarians and MBAs in the commercial sector.
• Over time, former intelligence officers (from U.S., French, German, British, Soviet, and other national servicesgradually entered SCIP, bringing operational and analytical expertise that positively influenced business intelligence practice.
• SCIP's Code of Ethics requires members to: increase respect/recognition for the profession; pursue duties with zeal and diligence while avoiding unethical practices; adhere to company or client policies, objectives, and guidelines; comply with all applicable laws; accurately disclose identity and organization prior to interviews; fully respect confidentiality requests; and promote compliance with these standards among peers and third parties.
• A key practical insight: while the ethics code may appear naive to those who imagine intelligence work as covert "trench coat" operations, professional experience shows that the information a decision maker needs is almost always obtainable by a quick, imaginative, dedicated professional without breaking laws or acting surreptitiously — the vast majority of interview targets agree to be interviewed, and even reluctant subjects often eventually want their "fifteen minutes of fame and importance."
• SCIP had 29 chapters in the United States and 15 in other countries, making it one of the fastest-growing professional societies worldwide.
• Estimated 1997 competitive intelligence expenditus by American firms alone reached roughly $11 billion, demonstrating this practice has outlasted typical management fads.
• A membership breakdown by industry (1994–1997) shows overall growth from 2,422 to 5,229 members, with especially strong growth in Consulting (236→585), Chemical/Pharmaceuticals (221→525), Communications/Telecommunications (194→524), and notable growth in Banking/Finance, Petroleum/Energy, Insurance, and Public Utilities. Growth patterns in telecommunications and s specifically reflect deregulation and other environmental/regulatory shifts driving new competitive dynamics.

Evolution from Secondary to Primary Source Intelligence

Early SCIP practitioners were drawn primarily from secondary-source research — a "clean," noncontroversial approach relying on open, public information sourc, well suited to companies without dedicated intelligence infrastructure. Many original members came from market research and library backgrounds, naturally emphasizing secondary-source exploitation. A number of online subscription services grew rapidly during this period (in advance of the Internet's rise), and several remain important secondary information sources today.

As competitive intelligence gained acceptance as an effective and legitimate business practice, the discipline expanded beyond secondary/open-source reporting to incorporate primary sources — specifically human sources: "people in the know." This mirrors the traditional national intelligence model, which comprises both intelligence collection and counterintelligence. The commercial analog of this complete function is termed Business Intelligence, made up of two components: competitive intelligence and competitive counterintelligence.

Framework Transition

Having established these foundations, the discussion moves into an operational framework for actual intelligence gathering — building on previously covered elicitation techniques and proceeding into specific collection operations.

Chapter 9: Operational Business Intelligence

Framing: Actionable Intelligence

The chapter s by distinguishing "good" actionable intelligence from "bad" actionable intelligence. To Business Intelligence professionals, actionable means information reaches decision makers at the right time, in the right way, with useful conclusions. (A wry aside contrasts this with the legal profession's use of "actionable," which means billable hours because something has gone wrong.) Any presentation of a corporate BI program—especially to technical audiences like engineers, architects, and sciensts—needs to lead with the process itself, or credibility is quickly lost.

The Business Intelligence Collection Model (The Intelligence Cycle)

Most national intelligence services depict intelligence work as a cycle rather than a linear process, and Phoenix Consulting Group's collection, analysis, and reporting approach folls this cyclical model, broken into discrete elements viewed clockwise:

• Tasking: The cycle begins with specific direction from firm leadership about what information matters to a decision maker. The BI practitioner's job is to break large questions/issues down into manageable subtasks, direct questions, and indicators that will produce useful insight.
• Collection Objectives: Refined tasking gets broken further into very specific items—a single senior-leadership question can decompose into major elements and then into thirty or forty specific questions. These get matched to available collection resources. This stage also includes the operational needs assessment: time and financial budgets, additional resources, milestones, and delivery formats.
• Collection Activities: Initial focus is on exploiting secondary sources not for current/reliable data but to build background context (covered further in chapter 10). More operationally important is identifying, contacting, and employing primary human sources—those with the most current and reliable information—using trained researchers.
• Process and Report the Raw Information: Information flows continuously from collectors to collection managers/analysts.ction and processing formally concludes at an agreed information cutoff date, though provisions remain for later-arriving information that hasn't been rigorously analyzed yet. Processing includes managing and validating sources and their information, and storing that information—an especially critical concern given data warehousing, data mining, and knowledge management practices across large and small enterprises.
• Analysis: Collected information undergoes rigorous analysis and comparison against other developed informaon and established assumptions. A critical warning: it is a deadly mistake to seek consistency with pre-existing assumptions. Trying to engineer a predetermined answer undermines project integrity, destroys credibility, and arguably should cost the analyst their job.
• Reporting and Dissemination: Results get reported in both written and oral format, since experience shows unanticipated questions always arise that a written document alone can't answer. Practically and politically, whoever managed the collection effort should be present for follow-on/iterative tasking that almost always results.

Elements Behind the Model

Several supporting practices don't usually appear in textbook cyclical diagrams but are hallmarks of an effective private-sector program:

• Iterative Tasking: Project results routinely surface additional issues not originally considered, driving new tasking on internal or external resources.
• Interim Reporting and Initial Analysis: While collection continues, information is continuously checked against known/postulated data, with regular validity assessments. At set intervals, collection managers brief leadership on interim findings, refining objectives as needed.
• Planning and Budgets: A cultural bias toward instant gratification (blamed partly on 24-hour news and "McNewspapers") leads roughly nine of ten first-time tasking leaders to expect immediate results. The governing rule of consulting applies: a client can have work fast, cheap, or good, but only two of the three. Fast and cheap sacrifices quality; fast and good sacrifices cost. This applies equally to internal corporate intelligence staff, who function essentially as trusted advisers/consultants, not just external providers. Practitioners must insist on dedicated planning time and established time/dollar budgets up front, since few external providers—or internal staff—operate with a blank check.
• Realism: Practitioners must recognize hard limits on what can be collected, including legal limits. If a leader unwittingly requests information that can't legally be oned, it is the intelligence professional's job to say no. If a leader insists on getting it "no matter what," it's time to look for another job or company—the only viable response is to lay out the pros and cons and let the decision stand.

Sidebar: "You Can't Get There from Here"

An illustrative anecdote: a helicopter-traing colleague lost his best student pilot when a general ordered him to fly to a destination beyond the aircraft's fuel range. The pilot's culture didn't permit telling the general "no," and the plane crashed in the desert with an empty tank. The pointed question for readers: does your corporate culture allow you to say no to unreasonable demands? The flip side warning concerns false guarantees—a professional should only guarantee delivery of specific information if they already possess it. Consultants who offer such guarantees are typically just repackaging a prior client's paid-for work at an inflated margin for a new client—not necessarily illegal or even universally viewed as unethical, but crossing a line of professional conduct by selling secondhand work as original custom work.

The Paradox of Intelligence and Operations

The single greatest use of intelligence is surprise avoidance—the "Art of Anticipation"—maximizing the decision maker's lead time and range of flexible response options. But this collides directly with the drive for certainty: waiting for 100% accurate information about a competitor's product (features, pricing, distribution, target market) means waiting until after the product has already launched, by which point lead response options have collapsed. This produces the central paradox: the greater the reliability of intelligence, the fewer options remain available.

This reframes the real decision as a trade-off: is leadership comfortable deciding six months out with 60% of the necessary information at 75% reliability, or would they rather wait for 90% information at 95% reliability just ten days before an event—when the actual response time needed is measured in months? If leadership genuinely requis 100% complete and 100% accurate information, they don't need an intelligence professional; they need a historian, because that information is now history. Leaders who can act decisively on 40% information with 50% confidence are the ones who earn premium compensation, because they can decide while retaining maximum strategic latitude. Critically, information flow must not stop once a decision is made—Colin Powell's dictum that "no strategic plan survives initial contact with the enemy" applies equally to military operations and competitive business strikes: there is no such thing as a static battlefield or a static marketplace.

Levels of Intelligence Use: Tasking and Consumers

So practitioners and organizations believe Business Intelligence belongs solely at the corporate/strategy level. That view holds true for grand strategic projects, but intelligence needs exist at every organizational level down to where "troops are actually being shot at"—the tactical, day-to-day level.

Intelligence has different focus, urgency, and validation/analysis/communication needs at each level:

• A rifleman on the front line cares nothing about grand strategy—only about the immediate opposing threat.
• An infantry company commander needs to know enemy size, weapons, morale, supporting forces, and equipment because 200 lives are directly at risk.
• A product manager similarly cares less about corporate strategic direction or M&A than about a competitor's specific launch date, target price point, or which market segment a rival is pursuing.

A sample chart of intelligence requirements onsumer location illustrates this: Business Unit level concerns include products, direct competitors, pricing, sales, services, customers, and vendors; Group/Sector level covers technology sharing, inter-business-unit trends, common customers, and resource allocation; Corporate level covers worldwide technology trends, long-term domain selection, M&A activity, strategic relationships, and regulatory environment.

The analogy to military rank holds without breaking down (unlike most analogies): Eisenhower as a company captain had entirely different intelligence needs than as a major on division staff, as a general, or later as president. The corollary principle: the lower an organization's level, the less time is available for planning, collection, analysis, and action—and at lower levels, the stakes (lives or procts) are concrete rather than abstract.

A Warning About Strategic Bias

There is a noted disproportionate demand for strategic-level collection work relative to genuinely tactical assignments. Some practitioners can't accept that their work isn't eagerly awaited in the boardroom, so they insist their "real mission" is strategic support—even when their actual deverables address tactical, near-term business issues. One client's candid term for this self-important framing is "SNOW"—Strategic Notion Of the Week—a wry acledgment that in a corporate world obsessed with quarterly earnings, people can convince themselves they're doing grand strategic work when the reality is closer to routine tactical support.

Forward Pointer

Remaining chapters will focus mainly on the collection-activities portion of the cycle, since operations are the book's core subject. Chapter 12 will revisit the Business Intelligence Collection Model in the specific context of trade shows and conferences ("riding the cycle"). The next material moves into what is termed the "Land of a Thousand Sources"—covering both internal and external sources and how to identify and access them.

Chapter 10: Intelligence Begins at Home: Internal Sources

Two Kinds of Information Sourcesll competitive information ultimately traces back to two categories: primary and secondary. Primary sources are people who possess real-time knowledge of what's happening today — not yesterday's headlines. Secondary sources are written, publicly available materials (free online or via paid subscription services) that offer background context and occasional valuable nuggets, but their main function is to help identify which primary sources hold today's information. A key warning: companies rely announce competitively valuable information until it's too late for competitors to act on it, so most published material is historical by nature — by the time it's conceptualized, researched, written, edited, and distributed, its edge has often eroded. Additionally, much of what actually happens never makes it into print at all because of editorial space constraints ("the Ressssst of the Story" — a nod to broadcaster Paul Harvey). Generally, the most valuable 10–20% of information — the part that isn't publicly available — is stible through legal and ethical means by finding the people who know it.

Internal Primary Sources: Three Categories

Business Intelligence practitioners often cite an "80-20 rule" claiming 80% of needed decision-making information already exists inside the company. Whether or not that ratio is precisely accurate, it reflects a real pattern: enormous amounts of usable intelligence sit untapped within firms. The most common response heard from internal people once identified and asked is "Well, nobody ever asked me." Internal correspondents fall into three primary categories:

• Knowledge bearers — employees with specialized skills or contacts that have never been tapped for competitive purposes. They typically have no idea how valuable their expertise could be to intelligence efforts, and often work in siloed divisions with little cross-company interaction. Finding and linking these people across departmental boundaries allows an intelligence-mining exercise that capitalizes on knowledge the company aeady possesses.
• External connections — employees who routinely interact with outside parties through business transactions (e.g., purchasing agents who deal with vendors that also serve competing firms) or through professional affiliations (managers who meet counterparts at conferences and industry meetings).
• Travelers and hosts — employees who travel to competitor and non-competitor companies and make contact with people there, as well as staff who host visitors from outside firms. Both directions of travelose employees to valuable external knowledge. Hosting situations deserve particular attention: sponsors of a visit can be tasked to note what specific topics visiting professionals seem most curious about, and receptionists often turn out to be excellent informal collectors — visiting groups tend to talk candidly in front of reption staff as if they were invisible, before their host or escort arrives.

Four Underlying Principles Driving Internal Collection

• A Migratory Flock — employees moving between companies carry knowledge of foer employers and former competitors with them. An intelligence collector tracks personnel files over time, builds a database of who these people are, meets with and effectively recruits them, evaluates their expertise and contact networks, and tasks them appropriately. The payoff is knowing exactly who to call for what.
• Return on Investment — most companies get essentially zero intelligence ROI from money spent sending employees to trade shows, conferences, and symposia. A collector should identify who attends such events, sensitize them beforehand to specific company information needs, and guide them through collecting in that target-rich environment where competitors, vendors, customers, consultants, and journalists all converge. This should go well beyond demanding a token two-paragraph trip report just to get a travel voucher reimbursed — the topic is significant enough to warrant its own later chapter (chapter 12).
• Treasures, Even Hidden Treasures — professionals across departments (R&D, accounting, facilities manageminancial planning, operations, production) routinely swap notes with peers at other firms about shared problems — benefits, recruiting, and other functional issues. This casual peer-to-peer sharing can reveal costs and profitability signals, hints of new hiring in unfamiliar fields (indicating new products or ventures), and future strategic plans. Training these specialists in nonthreatening elicitation techniques taps into professionals' natural tendency to trade experiences and even confinces with peers, driven by desire for recognition and other motivations.
• Isn't Work All There Is? — employees have personal lives that create additional informal networks: coaching youth sports alongside parents from other firms, college and university classmates now working at target companies, relatives, neighbors, fisng buddies, or old classmates who moved into academia or consulting. These can be identified, gently recruited, and occasionally tasked — described using Mao Tse-tung's metaphor of "fish in the sea."

Illustrative Case: The Professional Development Seminar

During a consulting engagement to build both a collection system and a protection layer for a client, a security director happened to mention a professional development seminar he had just attended onransportation safety and security. His notes and handout, from a presentation by a security manager at a company on the client's collection target list, described in detail three new multiton pieces of machinery being installed at a competitor's plant — including equipment origin (revealing manufacturer and specifications), transport routes (including road-building required to move heavy equipment), and installation details (concrete pads, calibration issues). Within ten minutes of review, this yielded significant insight into the target's new equipment lines. The lesson: had the security director not already understood what the intelligence unit was tasked to collect, he would never have thought to mention the notes, and the intelligence unit manager would never have thought to ask him. The materi would have simply sat filed away in an office. This illustrates how ordinary internal contact and travel produce serendipitous intelligence once employees know what to watch for.

Compensation and Ethical Boundaries

In legitimate business intelligence work, internal correspondents are compensated only as employees — usually just their regular paycheck, occasionally a free meal, sometimes bonus rewards for particularly valuable contributions. Some firms restructure sales-force compension formulas to reward information collection specifically, recognizing that a salesperson's real commodity is time; absent an incentive, most will choose selling over collecting when the two conflict, though customer intelligence and competitor intelligence often overlap and can support the sales pitch itself. External sources, by contrast, are virtually never paid — doing so crosses into bribery, and other classic espionage tradecraft (payment, blackmail, entrapment, cloak-and-dagger signal recognition routines) is explicitly rejected as appropriate and irrelevant to legitimate Business Intelligence practice, distinguishing it sharply from industrial or economic espionage.

Finding Internal Sources: Four Practical Mechanisms

• Intelligence Assessment — a structured evaluation of an organization's Business Intelligence competency, typically beginning with roughly thirty-minute structured interviews of leadership. These interviews reveal both what leadership wants answered and what information channels they already rely on. After the first couple of interviews are conducted by an outside consultant, the process is handed off to an internal team member. Leadership almost universally proves willing to name their trusted internal informants (the classic pattern: "there's Tom Thomas over in engineering... if I ever have a question, chances are good Tom has it") and typically encourages the intelligence team to contact those people directly with the leader's blessing. Occasionally a manager withholds their favorite informant — sometimes due to a personal relationshipmetimes to use that person later as a check on the intelligence team's findings.
• Professional organization membership mapping — identifying which professional associations and outside groups employees belong to through their careers. This not only maximizes return on professional-meeting spending (detailed further in chapter 12) but also reveals the true breadth of a firm's activities, often surfacing "I didn't know we did that" discoveries among team members. Following the money —cking accounting codes for membership fees paid on employees' behalf, records that may sit with HR, PR, investor relations, or training — reliably surfaces potential sources, echoing Deep Throat's advice to Bob Woodward during Watergate ("Follow the money"), reframed as the operating maxim "Where money changes hands, so does iormation." An adjacent operational maxim: no intelligence officer worth their salt spends more than 25% of their time at a desk, or they're functioning as an analyst rather than a collector — though the ratio shifts sowhat in Business Intelligence work given heavy phone and computer-based research.
• Company alumni populations — in industries with high employee turnover between firms or mergers/acquisitions-driven churn, alumni groups form and hold social gatherings at industry events, creating opportunities to learn what former employees are now doing at their new employers. Even without a formal alumni association, tracking where departed employees land has real value: how many retirees move into consulting, and for which firms? Whether a company maintains a system for tracking departing employees, staying in contact with them, and capturing information from departure exit-interviews are all practical questions worth asking.
• Human Resources as a source hub — HR often knows more about employee skills, competencies, and backgrounds than any other function, and this data is described as legitimately obtainable in bulk. Practical example: discovering that the world's leading expert on a specific technology aly works in a sister division, or realizing that a technologist's grad-school best friend now works for a competitor and exchanges daily email, or that an employee has co-authored papers with dozens of people at other companies and universities. This is framed as no different from information the firm already uses for competitive purposes like managing technical proposals, and not a privacy violation since it isn't used against the employee.

Gray Areas and the "It Depends" Standard

Several genuinely ambiguous questions arise around HR-sourced intelligence: is it appropriate to interview new employees within their first week or two about their prior employer's people, projects, and even that employer's own intelligence-collection practices? The only honest answer given is "It depends" — specifically:

• It depends on how genuinely committed ldership is to the intelligence mission; lack of buy-in signals a need for relationship repair before proceeding.
• It depends on how the approach to the employee is made — coercive, intimidating approaches ("we know whe your mother lives") are explicitly rejected as missing the entire point of ethical source development.
• It depends on timing relative to the hiring process. Virtually every company surveyed considered it unethical to involve a BI team member in pre-employment interviews, but opinions diverge widely on what's appropriate once someone is actually hired.

Case Illustration: A COO's View on Timing

An Intelligence Assessment interview with a chief operating officer who had risen through the legal department produced an unexpectedly direct answer to the timing question. Asked how long an employee should work at the firm before being appropriate to interview about their prior job, practices at other companies range from waiting six months, to a year, to three years, to never. This COO rejected all of that: "the day I'm starting to sign some SOB's paycheck is the day that I start owning every bit of what he's got in his head about anything." He drew the line only at the point before actual employment begins, reasoning that interviewing before start date "breeds problems," but considered everything after day one fair game. This is presented not as a universal rule but as evidence that reasonable, ethical leaders can land on entirely different answers to the identical question — reinforcing that these policy calls belong to leadership and should be revisited periodically.

Temporary and Contract Employees: A Double-Edged Sword

Some firms see no ethical problem hiring temporary or contract workers with the explicit intent of debefing them almost immediately — sometimes even paying a bounty specifically for contract workers who most recently worked on relevant projects for a nearest and fiercest competitor, purely to gain the fastest and cheapest insight into how a rival is currently operating. This mirrors the older practice of poaching a rival's bestermanent employees. Both carry the same structural risk: it cuts both ways. As firms increasingly rely on contract labor to control overhead, that same workforce segment tends to be the most disgruntled population with access to a company's secrets — a real warning, reinforced by the fact that the first-ever conviction under the Economic Espionage Act involved a manager of contract employees. The broader modern-workplace erosion of employee loyalty is described as most acute precisely among highly connected, technically skilled, dissatisfied, and transient contract workers who may work for a competitor today and the hiring firm tomorrow (or vice versa).

Functional Departments Worth Mining

A practical checklist of functional areas within a typical organization that can yield internal informants includes: Purchasing, Customer Relations, Environmental Safety, Engineering, Corporate Travel, Production, Operations, Legal, Security, Speaker's Bureau, and Investor Relations. The underlying principle is constant regardless of how a given firm's departments are actually organized: find the people who know, or find the people who know the people who know. A forward-looking note: these same functional contacts should be kept inind later for the flip side of the discipline — protecting a firm's own information — a topic taken up in Part III of the material.

Chapter 11: The World Can Be Your Oyster: External Sources

Three Categories of External Sources

External contacts fall into three classes, mirroring the internal-source framework from the prior chapter:

• Target internal sources — full-time employees of a target company who cooperate with outside contacts for their own reasons, whether or not they realize the value of what e revealing. Researchers approach these people through anything from highly ethical methods (à la Society of Competitive Intelligence Professionals standards) to ruses.
• Sources connected with a target company — vendors, union leadership, subcontractors, distributors, and on-site contract or service workers who do routinusiness with a target company. Some are bound by confidentiality/nondisclosure agreements, others are not.
• Unconnected and uncontrollable sources — people with an interest in a company but no formal relationshipo it: analysts, business writers, public-policy groups, government monitors, chambers of commerce, and government-agency representatives at every level.

Worked Example: Tom's Widget Company

A packaging vendor, Joe, supplies boxes to Tom's Widget Company. Simply talking to Joe about how his own business is going reveals that he expects a "banner year" because of Tom's orders. Deliberately floating an inaccurate production figure about Tom's current 10x10x10 widget line provokes Joe's pride and desire to correct the record — and he lets slip that Tom is shifting to a smaller 5x5x5 widget line because Joe now has to deliver ten million boxes in six months. This single conversation yields the new product, its size, its timing, and its volume, and opens a chain ("skein") of downstream sources — truckers, railroads, and other distribution-channel players.

Non-obvious point: deliberately stating something slightly wrong to a proud vendor is an effective elicitation trick — people can't resist correcting an error, especially about twn operation.

Two Fundamental Collection Principles

"Follow the money" — the most basic organizing principle for finding external contacts:

• Suppliers are often the most complete sources of information, largely because companies don't recognize how much competitive value their own suppliers are sitting on and thus don't protect it.
• Customers of a target's products may be dissatisfied, may want to play one vendor against another, or may simply talk too much — all of whmake them receptive contacts.

"Force multipliers" — leveraging people or organizations who already collect information for their own unrelated purposes and are willing to share it:

• Public-interest groups have agendas built around influencing public policy, so their model is to gather intelligence and broadcast it asidely as possible. Their memberships often include employees of competitor firms. Making yourself a recipient of that information flow (rather than a source they have to seek out) saves substantial time, money, and effort. This has paid off across industries from defense/aerospace to manufacturing to meat production.
• Media people. Complimenting a journalist on a story about a rival's new facility, then wistfully mentioning other angles you wish had been covered, often draws out material the editor cut for space — somimes including things the writer never intended to publish. A reporter's own contact network becomes a force multiplier. Warning/insight: reading the same public articles as every other competitor provides no edge — the value is in extracting what didn't make it into print. Local papers are especially valuable because they track the "big fish in a small pond" far more intimately than national media ever will (a small-town paper may know everything worth knowing about a locally significant company that national outlets have never heard of).
• A circle of competitors. Rather than calling people at the target company (Company A) directly, contact people at Companies B, C, and D — competitors of the target. Because they have no s in protecting the target's information, they undervalue it and share it more freely. This circle includes former Company A employees now at B/C/D, people married to Company A employees ("Pillownet"), people who play softball with Company A staff, or anyone with a peripheral relationship to Company A or its people.
• Government and quasi-government sources. Two distinct types:
  • Bureaucrats respond to formal requests, though not always promptly, "despite what the law says." The Freedom of Information Act (FOIA) is characterized as possibly the single best piece of legislation ever passed for business-intelligence purposes — even though this runs counter to the collector's own instinct (expressed candidly) that some information under FOIA needed more protection than it got. Companies chronically over-report to government agencies, and FOIA requesters can pull far more detail out of those filings than regulators ever intended — including full rosters of personnel supporting specific government contracts as an added bonus. S and local FOIA equivalents extend this same leverage well beyond the federal level (more detail on FOIA from a defensive angle comes in chapter 15).
  • Boosters — local chambers of commerce, economic-development committee members, local dia, and local elected officials — track business activity at the community level rather than the industry level, and often know both what a company is doing locally and who inside that company might make a good contact.

Internal Starting Points for Building an External-Source Network

Before paying for commercial mailing lists (expensive and "tacky"), mine resources already inside your own firm:

• Human Resources. Years of resumes — solicited and unsolicited, from job fairs, campus visits (including former summer interns at target companies), and search-firm referrals — typically sit unused in an HRMIS. These should be systematically folded into an internal source database rather than left to gather dust. A footnoted caution: decide in advance whether to contact a resume-sender immed or wait months, since running fake job postings and having competitive-intelligence staff (rather than HR) conduct the "interviews" edges toward or over the ethical line.
• Finance and Accounting. Applies the "follow the money" principle directly — shared suppliers, vendors, customers, and distributors with competitors are typically already listed by name or firm in accounting records, giving a ready-made starting roster of people who know what's happening at rival firms.
• Operatio. Employees have gone to school with, previously worked alongside, or maintained friendships with people now at competitor firms — reinforced by neighborhood overlap (soccer games, country clubs, swim teams, church, political groups) when a rival is located nearby.
• Membership lists (professional-organization directorieyour own employees belong to) do double duty: they help identify internal sources (per the prior chapter) and provide access to outside contacts through the same rosters. Practical friction: there's rarely a central repository, directories can be hard to borrow, and members may want to keep them for personal use — but leverage can come from the fact that the coany itself usually pays their membership dues.
• Sales force. Salespeople maintain relationships more actively than almost anyone else in a firm — present ployees who used to work at a target company, former target-company employees now elsewhere, and employees of shared customers who came from the target. This pattern is especially common in consulting and telecom, where vendor/research-firm staff transition into customer roles after a period of good performance.

External Starting Points: The Internet as a Source-Identification Engine

Libraries and dedicated information-services businesses remain useful, but the internet is described as the single fastest, most economical, and widest-ranging tool for identifying and developing sources — an "intelligence bonanza" whose scale would have astounded anyone working before roughly 1995.

• Electronic libraries (e.g., The Electric Libry) hold articles, papers, and monographs whose greatest value isn't the content itself but the people named, quoted, or referenced within them — each a potential source.
• News groups / user groups. Searching a company name on a site like Dejanews turns up individual-level (not company-level) posts — people responding in interest-group threads, sometimes posting from a company email address while discussing something completely unrelated (e.g., kayaking or mountain climbing). A sharebby thread is a natural bridge into a conversation about what each party does for a living, from which a source relationship develops organically. This works especially well with technically minded people who are more at ease online than face-to-face.
• Exploiting "internet addicts." People who spend excessive time online, eager for any incoming message that validates that they "have a life," are unusually receptive to a stranger initiating contact with an oblique reference to their real interest — a hook that can be developed over subsequent exchanges (a reply is likely within 24 hours). This behavior pattern is serious enough to be studied clinically (the chapter cites the real-wld Center for On-Line Addiction in Bradford, PA, and its acronym COLA).
• Case example — "Life in the Microsoft Woods." A listserv/email-forum exchange among contract technical writers (via a forum like the Computer Book Writers list) revealed detailed, real-time information about Microsoft's internal contractor policy: a mandated "break-in-service" rule forcing contractors off payroll periodically (with talk of extending it from 31 days toward 90+ days), restrictions preventing contract staff from eating company-funded pizza when working late, and the resulting difficulty Microsoft had recruiting and retaining experienced contract writers/developers. This demonstrates that contract technical writers — often privy to unreleased product details six to nine months out — are commonly treated poorly and are correspondingly willing to vent that information into public forums, making them val competitively significant contacts.
• Company websites. Firms invest heavily in websites that list employee names, divisions, and often email addresses as an implicit status symbol — inadvertently creating a "target-rich environment" for anyone identifying potential contacts.
• Resume/job-posting sites. People actively posting resumes (e.g., on job-search sites) are useful in two ways: even if their information is dated, they can refer you to people still employed at the target; a, counterintuitively, plenty of currently employed people still post resumes publicly despite the risk their own employer might discover the job search — a real and recurring phenomenon recruiters report often (33–50% of contract writers in one market reportedly wouldn't work for Microsoft at all, weighted toward more seniorple, illustrating how a bad employer reputation becomes public knowledge through these same channels).
• Government websites. Rich troves of organizational charts and staff information, motivated by agencies wanting to demonstrate their importance. Some agencies have begun scrubbing this data — not because anything sensitive was being disclosed, but purelyver privacy concerns — yet these sites still hold large amounts of unprotected information reported to them by private firms, none of which is classified.
• Guest books. Visitors to a site who sign a guest book usually leave an email address plus a stated area of interest, question, or comment — both identifying the person and, via the email domain extension (.gov, .mil, .org, .edu, .com), hinting at their institutional affiliation and suggesting how to tailor an approach.
• Case example — vulnerability-assessment guest book. On a military program website deliberately kept sparse on content for protection reasons, the guest book itself became the real vulnerability: of ninety people identified from it, seventy responded to emails about the program's performance characteristics. Most were university researchers or contractor employees rather than government staff, each eager to destheir own piece of the project, and roughly half volunteered names and email addresses of colleagues who knew even more. One contact, unintentionally, developed into a one-sided personal relationship between a researcher on the collection team and one of the online contacts — illustrating that unintended personal entanglements are a real risk of this kind of outreach.

Closing Note on Recordkeeping

Once sources are identified, they must be tracked, managed, and reused systematically ât administrative discipline (record management, retention, reuse over time) is covered separately in an appendix rather than in this chapter, but is flagged as essential rather than "boring stuff to get around to later." The chapter closes with the line: the day of the paperless intelligence office will arrive the same day as the paperless bathroom — i.e., don't expect to escape physical/administrative recordkeeping.

Chapter 12: Trade Show/Conference Intelligence Operations

Why Trade Shows Are a "Target-Rich Environment"

Trade showsnd professional conferences represent one of the richest possible venues for competitive information collection, yet most organizations badly underutilize the opportunity. Companies routinely spend enormous sums on trade shows — some client companies spend up to $20 million at individual shows — but rarely maximize the intelligence return on that investment. Most attendees return with little more than bags of brochures and product samples, sorted through only to satisfy a travel-expense trip report. This is described as "the professional version of hanging out at the mall": attendees make a couple of contacts, wander the exhibit hall, and hope a booth staffer is indiscreet about a new product or price. The core failure is one of direction: nobody tells attendees what the company would find competitively valuable, nobody sensitizes them to what will actually be happening, and nobody challenges them to plan in advance who they'll talk to, about what, where, and when. This gap — summed up as the "Nobody ever asked" principle — meanses who have attended conferences for years may have picked up valuable information without ever knowing where to route it.

Riding the Intelligence Cycle at Trade Shows

Trade show operations should restart the full intelligence cycle.

1. Tasking

The first job is determining, from or for leadership, what information is needed to support real decisions. Requirements take the form of standing intelligence questions (SIQs) or essential intelligence questions (EIQs).

2. Correspondent Network — Selection and Preparation

A recurring operational challenge is simply identifying who from the organization is attending a given event, especially in larger companies where dozens or hundreds of people may travel to conferences with little central direction or planning. Practical ways to surface this population:

• Coact the travel office and explain what support the intelligence program needs — develop travel-office staff as intelligence correspondents, the same way accountants, security managers, HR staff, and facilities managerhave been cultivated elsewhere.
• Mine the travel/finance section for records of who was paid for attending which event in which city.
• Identify professional organizations or associations the company holds corporate memberships in, or pays individual employee dues to — since the company is paying, there's no employee privacy issue, and the company can freely track how its money is spent.
• If there's no central travel/finance office, try the training department, which likely has records of people sent for educational conference attendance.
• Smaller firms may have an easier time: if all travel requires president or divisional GM approval, that approval point becomes the choke point revealing every potential collector.
• Ask who's been to a given event before, who they dealt with previously, what (if anything) of intelligence value came from that contact, and who is willing to serve as a collector.
• Broad methods like bulletin-board notices or company-wide emails yield poor response rates — targeted approaches through gatekeepers worr better.

3. Collector Preparation ("The Correspondents")

Preconference meetings should produce contact books assigning collection duties: who covers which booths and on what schedule, which customers are likely to attend and who is best positioned to deal with them, and reminders about company dress/uniform. Beyond logistics, real preparation includes:

• Matching each collector to prospective sources.
• Making collectors explicitly aware of what should be collected from people they already expect to meet.
• Training in elicitation so information can be drawn out without making sources nervous, suspicious, or defensive.
• Briefing collectors on debriefing schedule, time, and location.
• Equipping collectors with a discreet way to record what they learn between debriefings.

Security warnings for correspondents: do not use voice-activated microcassette recorders (the "Linda Tripp" model); do not pull out a notebook mid-conversation; do not leave notes about sources lying visibly on a booth counter next to the sign-in sheet. These seemingly obvious rules must be explicitly checklisted, because when skipped they produce real fallout that client companies have reported, sometimes with chagrin.

Building a Trade-Show Intelligence Culture — More Than a One-Shot Deal

Trade-show intelligence work should not be a one-time preparation exercise for a single event — it should establish an ongoing organizational culture and repeatable process. Employees have likely been attending professional conferences and symposia for years without anyone ever asking them what they learned.

Leveraging the Conference Volunteer Structure

Professional conferences are typically run by volunteer members of the sponsoring society or association — not by paid staff — meaning employees of your own firm may already be serving (or could be encouraged to serve) as conference chairs, abstract-evaluation committee members, or in other organizing roles. This yields non-obvious intelligence leverage points:

• **Theme and paper selection influencompany employee sitting on a conference organizing committee can help shape next year's program theme, particularly toward areas the firm is strategically interested in. This goes beyond the "45-5 rule" most companies chase for free advertising — where a fifty-minute presentation slot yields five minutes of substance and forty-five minutes of advertising for the presenting company. From an intelligence perspective, shaping the theme lets you engineer invitations to specially skilled or respected individuals at competitofirms, whose accepted papers can reveal where their organization is technically headed.
• Worked example (Call for Papers): An employee helping set an electro-optics conference theme could steer approval of a niche session — e.g., X-ray pulsed lasers — knowing that of perhaps only a dozen people worldwide working in thatcipline, two work for a direct competitor. A personally addressed call for papers to that narrow population makes it highly likely those individuals submit and get approved without reservation, effectively guaranteeing intelligence access to their current work.
• Moderator/session-support role: Someone assigned as a paper's moderator or introducer — an employee or a trusted consultant — can offer to help develop the paper itself (serving as an outsidt of eyes), can plant pointed audience questions the presenter will feel socially obligated to answer even if borderline sensitive, and can loiter after Q&A to note the names and companies of anyone asking particularly revealing follow-up questions (a signal of their own firm's direction).
• Post-session elicitation timing: After a presenter has just finished fielding audience questions, their guard/sensitivity level is at its highest point. The recommended tactic is for the moderator to invite the presenter for a drink or coffee immediately afterward, opening the conversation at that elevated level of engagement (praising the paper's brilliance and reception) rather than starting back at basic questions — leveraging elicitation training directly.

Real-World Collection Techniques ("Tricks othe Trade")

Several field-tested vignettes illustrate non-obvious collection methods:

• The restroom attendant ("Trick #1"): One company employs an older, unassuming, accented part-time employee whose job is handing out paper towels in hotel men's rooms at large conference venues — without a name tag, without attending sessions himself. He is treated as invisible, like other service staff (janitors, window-washers, guards, receptionists) who go unnoticed throughout professional life.his yielded a real payoff: two competitor executives once discussed the benefits of a joint venture between their two firms in his presence, without breaking stride, giving the client company genuine early warning that let them forecast and act preemptively.
• The elevator rotation ("Trick #2"): Another company rotates three or four employees continuously through hotel elevator banks in thirty-minute shifts, riding without conference badges (blending in as ordinary hotel guests). The key psychological insight: people tend not to stop a conversation already underway when someone is already on the elevator when they board, even though they will stop talking if someone boards after them — apparently because they feel they're invading the newcomer's space rather than vice versa. This lets riders overhear especially revealing conversations that ctinue as targets exit onto their floors, sometimes even following to a room door.
• The pregnant collector ("Trick #3"): A visibly pregnant, footsore correspondent wearing a full company badge became one of the most prolific collectors at an entire trade show simply because booth staff instinctively invited her to sit and rest — conversations then stretched to ten-plus minutes despite her badge clearly identifying her employer. "Mothership has its advantages."
• The decoy quarterback ("Trick #4"): A well-known collector deliberately visited a rival's booth and was immediately pulled aside by his counterpart, who spent forty-five minutes on small talk (kids' soccer, hang gliding) to keep him from collecting anything. The rival w pleased with the diversion — but four other members of the same collection team were, at that same moment, having productive, unmonitored conversations elsewhere in the rival's booth. Lesson: a known face can be intentionally sacrificed as a diversion while less-recognized team members do the real collecting.
• Vendors who serve an entire industry (including your competitors) are valuable sources precisely because, in the course of collecting "customer intelligence" for their own sales rposes, they simultaneously acquire competitor intelligence useful to you — though this is explicitly noted as a double-edged sword (they can just as easily leak information about you to others).
• Consultants are both excellent sources and excellent collectors. As collectors, they always have a ready pretext for asking detled questions and are rarely challenged; many retain source relationships from prior employers, creating a force-multiplier effect. Critically, a consultant without a company name badge (or one so established their firm poses no perceived competitive threat) gains access to conversations and booths that a badge-wearing employee cannot — nobody asks a consultantor a client list or who is funding their conference trip.
• Trade publications and publishers reveal competitive intent through advertising-spend patterns; few companies scrutinize what their own ad budget signals about their intentions. A real anecdote: at a security industry conference, a publisher pressed a security-hardware executive about flat advertising spend, and the executive — unprompted, in front of a competitive-intelligence professional he didn't recognize as such — described in full detail a new product family launching nine months later, including target customers, price point, and competitive rationale, entirely because he was explaining a coming increase in ad spend. Media professionals cultivate industry sources, expert commentators, and trend-setters as a normal part of their work, and it is worth preparing to meet writers at their usual haunts (near the pressroom, fave bars) armed with knowledge of their recent published work, while planning what you're willing to disclose so the exchange doesn't become one-sided in the writer's favor.
• "Poster children" — presenters relegated to poster sessions rather than the main podium — are often overlooked by nearly everyone, making them unusually willing conversationalists once someone shows genuine interest, because they otherwise get little audience for their expertise. The skill required here is knowinw and when to end such a conversation gracefully once the useful information has been extracted.

Quarterback vs. Linebacker Operations

Two complementary orientations for on-site trade-show intelligence work, borrowed from football terminology:

• Quarterback operations: on-site collection with central control providing direction, coordination, and initial analysis.
• Linebacker operations: protection and defense-focused, countering rivals' collection efforts against you. Many organizations run an integrated approach covering both.

Quarterback Operations — Logistics and Execution

Location: Choose an operational base near, but not inside, the conference hotel — ajacent hotel gives correspondents easy access while reducing excuses for missed debriefing meetings. Do not try to save money by using exhibit booths or public break areas for debriefing meetings, since these are not secure or private.

Communications: Cell phones/pagers are essential for tracking correspondents down when urgent tasking or warnings need to be passed along, especially given the sheer number of people involved at large events. Warning: bring your own personal phones/pagers rather than rented equipment, particularly if your firm's rental vendor also serves the same city market (implying possible traceability/compromise). Avoid theatrical tradecraft — chalk marks, coded roses, counter-surveillance routines — unless operating literally under "Moscow rules" in a hostile police-state environment; most people who insist on such theatrics are indulging their own sense of mystery er than addressing real risk.

Playbooks: Each correspondent should receive a dedicated playbook built from the outset of planning, containing:

• Background on the conference itself.
• Background on prospective contacts.
• Background on companies targeted by the collection team, broken down by primary/secondary responsibility across rivals, customers, vendors, publishers, consultants, media contacts, conference organizers, and association leaders.
• Lists of hotels, notable restaurants, meeting sites, room numbers, and phone contacts.
• Sanitized/abbreviated reporting from other correspondents already at the conference.
• On-the-ground or home-office analysis of material surfaced so far.
• Additional EIQs generated from other correspondents' reporting.
• Warnings about what rivals have been attempting to collect about your own firm.
• Warnings about specific people correspondents should avoid or handle carefully.

Developing SIQs/EIQs during this planning process frequently reveals that a company already possesses more relevant internal information than realized, which in turn sharpens and refines the questions asked going forward.

Critical playbook security warning: keep playbooks physically confined to the operational meeting site. Do not check them in luggage, do not let correspondents keep copies in their own offices (they will lose them), do not let correspondents carry them onto planes to study en route (fellow passengers may have direct interest in the same information), and do not let them bring playbooks to their hotel rooms to review (they'll end up left in booths or other exposed locations where "decidedly the wrong people" will find them). Control and collect the playbooks before departure for the airport.

Equipment: Standard kit includes a laptop, portable printer (functionality over polish), modem/fax for reporting back to headquarters support staff (analytical, logistical, research). A specific warning: think carefully before routing incoming faxes through the hotel's business center/fax service — hotel sff and even bellmen have routine access to incoming materials, and there is no guarantee copies aren't being made and routed elsewhere, a risk that exists domestically in the United States and in "friendly" countries just as much as anywhere assumed to be more hostile (e.g., France). Also bring paper, flip charts as portable whiteboards, reference materials, file folders, pins/tape, notebooks for debriefing notes, and snacks/beverages — the team leader likely won't leave the debriefing room until the conference ends.

Meings and Debriefings: Arrive a day ahead to establish the debriefing site — ideally a suite, kept close to materials so nothing needs to be carried elsewhere. Arrange an off-site meeting room at a restaurant some distance from the conference hotel for the final pre-conference group meeting the night before the event begins, ere final tasking, requirements, and individual debriefing schedules are locked in. Each correspondent should know the full communications plan: primary and fallback appointment times, contact numbers for everyone including the quarterback, and the debriefing room/hotel location.

Quarterback's own visibility: Whether the quarterback should personally work the exhibit floor depends on whether they are known to competitors. If unknown, direct floor collection is viable; if recognized from professional history, the better role may be directing operations from a distance rather than collecting personally (illustrated by the diversion anecdote above).

Processing the Information

The first question in processing should always be "how much time do we have," followed immediately by locking down the next meeting's time and location — pagers going off or unexpected calls routinely delay or derail follow-up contact, sometimes for days at a time during a busy trade show.

Debriefing style should adapt to the individual: introverted correspondents tend to prefer working through a prepared script/question list in order, while extroverted correspondents tend to want to talk in a stream of consciousness. If it's the first time working with a given correspondt, test both approaches to see which works better, but stick with whatever has already proven effective for that individual. During debriefings, take marginal notes without interrupting, then circle back to earlier points once the correspondent finishes — this demonstrates active listening rather than passive note-taking and tends to be well received.

Encourage correspondents to take contemporaneous notes (rather than relying on memory, which degrades rapidly "three hours and thirty peopleater") and to safeguard those notes carefully. At the end of each debriefing, issue any additional tasking generated by other correspondents' reporting.

Security warning for processing/storage: maids and room service staff often have unfettered access to hotel rooms where materials are stored — storage and transmission intrity is as much a part of processing as the debriefing itself, and familiarity with hotel staff does not automatically confer trustworthiness.

Analyzing the Information

Following intelligence-community practice, collectors should generally not be the ones analyzing their own reporting. The closer someone is to the collection effort and the sources personally developed, the more validity, accuracy, and completeness they will naturally (and sometimes wrongly) attribute to that information — a fresh set of eyes catches errors and biases the original collector cannot see themselves, even if this occasionally creates some friction.

• On-the-ground analysis: First-order analysis performed on-site, in near-real-time, allows a piece of information one correspondent dismissed as unimportant to be recognized as significant because of something another correspondent reported separately — enabling immediate follow-up tasking rather than waiting for after-the-fact debriefs back at the office. This on-site distance from the original collection also avoids the "too close to the forest to see the trees" problem.
• Analysis back at headquarters: Larger organizations may maintain an ongoing link with headquarters-based ants (who typically helped originally develop the SIQs/EIQs) who provide periodic reads on incoming field reporting and can identify additional collection opportunities while correspondents are still on-site and in contact with sources. Smaller/medium businesses without a full analytical staff will likely have collection, analysis, and reporting all falling on one person's shoulders.
• Reporting to a senior executive/boss who also attended the event has real value — but remember to debrief that executive too, since they likelhad their own collection objectives and may have learned things from their own counterpart-level contacts.

Disseminating the Intelligence Product

Distribution decisions should not default automatically to the original requester alone — other stakeholders may benefit. However, this decision should not be made unilaterally byhe intelligence officer; it is safer to brief leadership first and ask, as the final question of the briefing, "who else do you want on distribution for this?" — a lesson many intelligence officers learned only after priously making unwise distribution calls on their own judgment. Leadership debriefs after the event are also an opportunity to learn about senior-level contacts they had with rival leadership — access that can meaningfully contribute to remote psychological profiling efforts through internal peer review.

Linebacker Operations — Defensive/Counterintelligence Side

Defensive trade-show measures deserve attention even before a dedicated countermeasures discussion, since your organization is far from the only one running collection operations at any given event.

• Basic housekeeping: Box up and remove all extraneous papers and notes rather than discarding them in hotel trash — people are frequently observed rummaging through hotel dumpsters near conference venues specifically looking for discarded materials, not out of desperation but as a deliberate collection tactic. Legal and ethical dimensions of this and related practices, domestically and internationally, are addressed separately in Appendix B.
• **"Who's asking what of whom?identifying which rivals are actively collecting at the event, and what they're specifically after, is treated as a core counterintelligence function comparable to what national intelligence agencies do when trying to determine what an adversary wants and why. A rival's specific line of questioning often signals one of two things: they are pursuing the same direction themselves and want to gauge how far along you are (informing their own preemptive market moves), or they've picked up an early indicator worth passing directly to their own collection teams — effectively giving them a brand-new area of interest they hadn't previously pursued.
• Assessing rival collection competence: Observing how well or poorly a competitor collects (organization, training, funding, sponsorship level) helps assess their overall inlligence collection capability against you — a task that recurs in later chapters on protection.
• Preparing your own people: Understanding what rivals are targeting and how competently allows correspondents to be ecifically briefed and hardened in advance of future events.
• Fallback for smaller operations: Organizations without a full quarterback/linebacker structure can still run effective "prebriefing" sessions before departure — one example given is an informal "Eating Your Competitor's Lunch" pizza session where general and specific collection questions are assigned by topic, company, or individual target before the team scatters to the event.
• Building debrief-culture habits: Scheduling a debriefing appointment with each correspondent on the very first morning after they return trains correspondents to expect and prepare for it, and many correspondents are genuinely eager to share their "wins" — additionally relieving them of writing the standard trip report, since the debriefer captures that information instead.

A Day in the Life of the Trade-Show Collector

A illustrative daily rhythm for passive/opportunistic collection at a trade show:

• Breakfast in the hotel restaurant, where competitor teams plan their day out loud o they'll see, what approach they'll take.
• Mid-morning, once early visitors head to sessions and the exhibit floor empties, nearby break areas become gathering spots for louder-than-normal complaining that can be overheard from several tables away.
• Lunch, especially in break areas serving "barely edible sandwiches," draws sore-footed staff who don't want to wander far — complaints and post-mortems about the morning continue at volume.
• Mid-afternoon low-traffic periods prest similar opportunities in break areas.
• Dinner time, when the exhibits floor closes, groups head to hospitality suites or nearby restaurants; late arrivals to a lobby meetup often explain themselves at length (e.g., citing a backlog of emails), revealing what the group discussed while waiting.
• After dinner, the more extroverted staff who gain energy from socializing gravitate to the hotel bar to keep talking about the day and what's coming next — a natural, low-effort venue for continued passive listening.

Chapter 13: DevelopinPersonality and Psychological Profiles

Core Premise: Avoiding Surprise

Competitive intelligence exists largely to avoid surprise in the marketplace, and avoiding surprise depends on the ability to anticipate what business rivals will do. Simply having met a rival a few times or "hallucinating" what he might do falls far short of what General Patton described — deep study of an opponent's history, decision patterns, and influences — or what Napoleon called getting "inside my enemy's decision-making process." Psychological profiling instruments offer a structured way to get inside that decision-making process without direct access to the person.

Why the Myers-Briggs Type Indicator (MBTI)

Over roughly thirty years, various psychological profiling instruments emerged as predictive tools — distinct from therapeutic or clinical instruments — that: predict behavior rather than diagnose it, don't require advanced degrees to administer or interpret, and are flexible enough for varied real-world use. The MBTI stood out as the most easeffectively applied in intelligence work. Originally developed in the early 1940s as a personnel screening/selection tool, it has been continuously refined and validated, is used in over two dozen languages, and is administered to over two million people annually. Within the intelligence community it was used to match people's types to appropriate roles — some types suited to analytical work, others to field/operational work — paralleling the business distinction between, for example, actants and sales/marketing people. There's no "one size fits all" personality type for every assignment.

Institutional Resistance to New Methods

Outside consultants tried repeatedly to bring "emerging human technologies" (like personality instruments) into the intelligence community and were met with resistance, superstition, and xenophobia — partly because the community was already under scrutiny and distrustful of outside help. Leadership solved this by tasking a small internal group of respected, skeptical, veteran operational officers to evaluate the techniques themselves. The logic: if these hardened insiders became convinced a technique had real operational utility, their ownredibility would make the tool's internal adoption far easier — they'd become "agents of influence" persuading their skeptical colleagues, rather than an outsid trying to force change.

The Personal Discovery That Enabled "Remote" Profiling

The breakthrough insight came from a personal, non-professional event: during an adoption-agency screening process, a psychologist administered the MBTI to a husband and wife twice — once with each self-reporting normally, and once with each person answering as they believed their spouse would answer. Despite the couple's own type profiles being very different from each other, their "other-party" predictions of each other's scores matched almost exactly what each person's real self-report showed. This suggested that people who know someone well can accurately predict that person's MBTI profile without that person ever taking the test.

Validating "Rete Psychological Assessment"

This led to structured experimentation:

• A task force of intelligence officers who knew a particular leader answered the MBTI as they believed he would answer himself. Their individually derived profiles converged closely with each other and matched his actual self-reported profile almost exactly.
• The exercise was repeated with ten other subjects, all with the same successful results.
• This established the concept later called "remote psychological assessment": deriving a subject's psychological profile entirely through the reports of people who know that subject, with no direct access to the subject.
• Real-world testing followed on foreign leaders the national leadership wanted to better understand. People who had known these leaders at different times/places were trained in the MBTI (through self-reporting, then second-party reporting) and then asked to answer as the foreign leader would. Consistency held even without any ground-truth score to check against, and the resulting predictive profiles were used to anticipate how these leaders would behave in negotiation or conflict.

Practical Method for Business Use

The same approach translates directly to business rivals, where you obviously cannot hand a competitor's executive an MBTI form and ask him to fill it out, and cannot recruit "reliable sources" the way government operations can. The adapted solution, refined over roughly a decade of hundreds of remote assessments performed annually for business clients:

• You don't need the subject to sit through all 126 questions. Elicitation skills (reformulating direct questions into conversational statements) are used to extract informative responses from people who know the target — potentially 100 to 125 separate informed sources — whose collective input effectively answers most of the questions on MBTI Form G.
• Note: not every one of the 126 questions on Form G is used, since some questions are undergoing revision for future editions.
• Understanding which questions map to which personality characteristics required consible study, including formal certification (e.g., a one-week program at the Center for Application of Psychological Type in Gainesville, Florida), but this competency can also be built inexpensively through independent reading and online resources — an online MBTI-style instrument developed by Michael Kiersey and Marilyn Bates was available at kiersey.com for self-administration and self-study.

Finding the 100+ Sources

Sourcing multiple informed people about a target is treated as a natul extension of elicitation skills already covered earlier:

• People within your own organization who previously worked with or for the target are a strong starting point.
• If the target came from a different industry, people from that earlier career still hold insights into how the target deals with the world, which surface through MBTI-framed conversation.
• The target's social and community network — neighbors, people he coaches soccer with or plays golf with, old fraternity/sorority connections, former professors, and professional-association colleagues — all represent additional sourcing pools.
• Once initial contacts are exhausted, ask those same sources to refer additional pe who know the target; a comprehensive picture builds quickly this way.
• A major side benefit of these conversations: sources spontaneously offer anecdotal, explanatory examples of the target in action — how he reacted in specific situations, how he overcame challenges, who his close confidants are — which puts real substance ("meat on the bones") behind the abstract type designation.

What a Finished Profile Report Should Contain

A complete profile combines the generic MBTI-type description with the anecdotal personal/professional history gathered from sources, and — on a good day — should also include concrete recommendations for how to deal with the target personality in an upcoming negotiation or business situation.

Addressing the Methodological Purist Objection

This approach deviates from strict MBTI administration standards (an uncorrupted, self-administered questionnaire utrolled conditions) and a methodological purist might object. The rebuttal offered: the perfect is often the enemy of the good, and real-world business conditions rarely allow for laboratory-grade sampling. The goal isn't scientific validity for its own sake — it's producing an effectively predictive instrument that helps a client anticipate how a rival will act or react in the marketplace. Practical utility is prioritized over methodological purity.

The Four MBTI Scales and Sixteen Tys

Analysis focuses on four scales: Extraversion–Introversion, Sensing–iNtuitive, Thinking–Feeling, and Perceiving–Judging. Spelling notes are deliberate (not typos): Carl Jung specifically used "Extraversion" rather than "Extroversion," and "iNtuitive" is capitalized on the N to distinguish it from Introversion's "I" in -letter type code. Combining preferences on the four scales yields sixteen possible types (ISTJ, ISFJ, INFJ, INTJ, ISTP, ISFP, INFP, INTP, ESTP, ESFP, ENFP, ENTP, ESTJ, ESFJ, ENFJ, ENTJ). Formal scoring places a person's score at a numerical distance from the midpoint on each scale, and the distance from the midpoint indicates the strength of that preference (not just its direction). Example given: an individual scoring strongly toward Introversion, Sensing, Thinking, and Judging is a strongly-typed ISTJ. As an illustration of how a type translates into predictable behavior, an ISTJ characteristically prefers dealing with few people, relies heavily on his own judgment, focuses intensely on details (sometimes losing sight of the big picture), values logic over emotion, and has a strong drive toward closure and decisiveness rather than delaying decisions for more information.

Case Study: "Jack Jones" at Junipero Corp

A detailed illustrative example (composited/anonymized, drawn from a real ~40-page report) shows the method's practical payoff:

• Setup: Junipero Corp, a profitable electronics-components manufacturer, hired outside executive Jack Jones as its new president, explicitly to move the company in a new strategic direction after the prior president was seen as too tactical and lacking long-range vision. Client Hildegaard Industries, a competitor, wanted to understand how Jones would run Junipero and how to exploit that competitively.
• Background gathered: Jones had only one prior senior leadership role, moderately successful, on a short assignment that ended in an apparently friendly but unexplained departure. He was highly intelligent, articulate, personable, well-liked, inspired loyalty, and had strong work capacity; he thrived on intellectual discussion and diverse opinions, especially novel approaches to old problems; he deferred judgment and decisions until forced by events; he cultivated an "employee first" reputation.
• What the profile plus anecdotes revealed underneath the surface reputation: Jones was long on imagination but short on attention span, bored easily with detail-heavy or unexciting projects, and rarely accepted responsibility when projects failed. His carefully cultivated reputation for valuing people fell apart under scrutiny of situations requiring accountability — he showed strong control needs around decision-making, distrusted subordinates' judgment, and when his own decisions fled, worked to distance himself from blame, at times shifting blame onto the very subordinates who had been most loyal and enthusiastic. Conversely, he moved quickly to claim credit and visibility for successes. His MBTI type emerged as ENFP.
• Practical/strategic consequence: The profile predicted Jones would gravitate toward high-visibility, non-revenue-producing initiatives (child care programs, expanded parental leave, environmental and community relations) at the expense of core, fast-paced, technology-driven decision-making the industry demanded. This prediction proved accurate — his preoccupation with "grand schemes" slowed Junipero's decision cycles and time-to-market, alienated legacy leadership as resource decisions languished, and increased his mistrust of his own team when quarterly targets were missed.
• Competitive exploitation: Knowing this in advance, Hildegaard timed fosed recruiting efforts to capitalize on the resulting internal disaffection and organizational decline at Junipero. Hildegaard also indirectly encouraged state political leaders to recruit Jones into high-profile social/civic initiatives — knowing he would readily accept them — further overloading him and accelerating friction with Junipero's production and engineering leadership, whose support had underpinned the company's prior success.
• Takeaway: A rival's MBTI type (ENFP in thise) combined with corroborating anecdotal evidence gave a competitor concrete, actionable predictive insight into how that leader would behave, allowing deliberate exploitation of those predictable weaknesses.

Application to War-Gaming

Business war-gaming benefits from incorporating this same psychological-type methodology to increase realism. Practical suggestion: if your firm has already been using MBTI internally for team dynamics, apply the same logic when staffing a simulated "opposing team" in a war game — select staff members whose own MBTI types most closely match those of the actual rival executives being simulated, since people who share cognitive/decision-making styles th the real counterparts are more likely to process the simulated scenario the way those counterparts would in reality. This is presented as low-risk and low-cost ("what do you have to lose?"), potentially producing war-game outcomes that are meaningfully closer to real-world results.

Closing Point / Transition

Whether or not a reader chooses to adopt psychological profiling for outward-facing competitive purposes, rivals may already be studying you this way — so at minimum it is worth applying the same self-examination inward, understanding your own organization's psychological profile and vulnerabilities. This sets up the book's shift into its next major section on protecting one's own organization rather than collecting on others.

Chapter 14: Operational Counterintelligence: Keeping Score and Keeping Them Out

Reframing Corporate Counterintelligence

Corporate counterintelligences not a law-enforcement or espionage-thriller activity — no handcuffs, no "shaken, not stirred" theatrics. It is a straightforward business practice, and it is fundamentally different from a security approach in the same way intelligence collection differs from market research. The opening quote captures the mindset shift needed: "If you're constantly putting out fires, chances are that you're working with a bunch of arsonists" — meaning reactive firefighting is a symptom of failing to cipate threats in advance.

The Definition, Broken Down

Corporate Counterintelligence is defined as: active measures, sometimes taken in conjunction with federal agencies, undertaken to identify and neutralize the intelligence-collection activities of a business rival. Each phrase matters:

• "Active measures" — not t disinformation/assassination connotation associated with Soviet-era intelligence services. Here it simply means active rather than passive, and anticipatory rather than reactive/investigative.
• "Sometimes in conjunction with federal agencies" — federal agencies (e.g., under the Economic Espionage Act of 1996) can be partners in investigation and prosecution, but they operate under manpower and resource constraints, and businesses often have legitimate rsons to avoid a public investigation involving a federal agency.
• "To identify" — the emphasis is on identifying threats before a loss occurs, not after.
• "Neutralize" — despite the ominous sound, this just means disabling or preventing an adversary's ability to cause harm before they get the chance, paired with early, pre-event identification.

Three foundational questions structure the discipline: what to protect, how to protect it, and how long to protect it.

What to Protect

A core failure mode: organizations (government and business alike) try to protect everything and end up protecting nothing, wasting resources in the process. Bismarck's warning applies directly: "He who seeks to protect all, protects nothing." Few businesses can afford total secrecy across all opions.

Coca-Cola formula example: Coca-Cola protects its formula aggressively and permanently, yet the product still sits on store shelves where anyone could theoretically reverse-engineer it — because a business cannot simultaneously lock up its product and sell it to customers. The practical lesson: since attacking a company's most fiercely defended asset (like the Coke formula) is a poor use of a competitor's resources, competitors instead target softer, less-guarded fronts — distrion channels, new packaging, co-branding/strategic partnerships, and line extensions. That's the real information worth protecting, because it reveals tactical and strategic direction.

Case example — "Copy, Copy, Who's Got the Copy?": A senior government official managing a major multi-year technology project asked for helprotecting it from Soviet disclosure, only after three years, over 300 people aware of the project, no knowledgeability list, and nearly fifty safes stuffed with technical materials in one room — essentially unprotectable at that point. The (only half-joking) recommendation: photocopy everything, put the copies in new safes, and literally drive them to the Soviet bassy on a truck and abandon them. The paranoid Soviets would assume it was a deception operation and spend far longer than the technology's remaining 18-month timeline trying to authenticate the material — buying time to build real protections. The takeaway: retrofitting security after failing to plan "what to protect" from day one can create a nearly unfixable position; sometimes overwhelming an adversary with unverifiable volume is more effective than trying to lock down an already-compromised secret.

The Value of Cues and Signals

Protection isn't only about big secrets — it's about the small, aggregated pieces of information ("cues and signals") that, when pieced together like a jigsaw puzzle, reveal a competitor's direction. People holding these cues often don't recognize their significance because they don't understand the intelligence process of aggregation and analysis.

Exampltravel reservations as a leak: A competitor's habit of announcing new product launches with fanfare at a particular resort, and booking travel/hotel six months in advance, gave a rival early warning sufficient to counter the product launch.

Example — "The Eyes Have It" (Houston Oilers): Coach Bum Phillips explained his team's porous offensive line by describing how running backs would unconsciously tip off (via facial expressions — a face "white as a sheet," and staring intently at intended gap) exactly which player was getting the ball and where he intended to run, letting the defense react perfectly every time. Direct parallel to businesses that unconsciously "tip their hand" through observable behavior patterns.

Framework for reading competitor cues (attributed to colleague Bill DeGenaro), viewed from three angles:

1. Competitor's situation — Is the rival growing faster, more profitable, or more innovative than seems explainable by visible information alone?
2. What competitors anticipate — Do they see predict and respond to regulatory changes, technology shifts, or customer requirements before you do?
3. Competitor's actions — Do they raply counter your new products, erode your first-to-market advantage, preempt your strategies, attack your high-margin products/territories, exploit your vulnerabilities, or recruit your best people at critical moments?

Case example — "I've Got a Headache" (Tylenol vs. Datril): Bristol-Myers test-marketed its new painkiller Datril in Peoria, IL and Albany, NY — cities they habitually used for test marketing, which became a recognizable pattern (a "cue"). Johnson & Johnson monitored this pattern and learned Datril's planned launch details: an April 15 entry date and a price point of $1.89/bottle versus Tylenol's $2.89. Using this intelligence, J&J moved first — on April 1 — announcing that because Tylenol's development costs had been recovered ahead of schedule, they were passing savings to customers with an immediate price cut to $1.89 plus rebate coupons for recent buyers. This preempike disrupted Datril's entire ad campaign (media wouldn't even take Datril ad space until the campaign was reorganized) and kept Datril to only about a 1% market share a year later — critically, this happened before the Tylenol cyanide poisonings, meaning Tylenol had no strong number-two competitor to lean on when that crisis hit. The chapter poses the counterfactual: had Datril been a strong #2 brand at the time of the murders, the outcome for J&J could have been very different.

Core aom: "There's no such thing as a coincidence." If a competitor is consistently winning in ways that seem to exceed normal explanation, assume it's not luck — consider whether their use of the intelligence process is systematically dulling your competitive edge.

How to Protect It

Before choosing countermeasures, organizatis must wrestle with hard cultural and cost questions: Will new protective rules undermine an open company culture? Will employees feel distrusted? How restrictive can protections be while still letting people do their jobs? How permissive can they be while still protecting what matters? What's the cost-benefit versus alternative countermeasures? These questions must be worked through as part of a defined process (detailed later in the chapter as the Business Intelligence Protection Model), paralleling the collection process described earlier in the book.

How Long to Protect It

Guiding principle: protect valuable assets in the strongest feasible way for exactly as long as necessary — no more, no less. Don't spend excess time or money once the need has passed, but don't tear down protections carelessly either.

Warning — the post-bid disposal mistake: Companies routinely protect competitive bids rigorously while active, then discard everything — the losing bid, notes, storyboard papers — once the contract is awarded, wrongly assuming the information is now worthless. In reality, a losing bid in a smart competitor's hands can reveal pricing, technical, or management approaches useful in future competitions. Companies fail because they thinkout protecting the bid document itself, not its component parts (notes, associated papers, storyboard sheets).

"Waste archeology" (a.k.a. Dumpster diving/garbageology): Exploiting discarded materials is a real collection technique used by adversaries, even though it's not something ethically-bound practitioners (e.g., SCIP members) advocate. Only one person in U.S. history has been jailed over it — a California executive convicted not for the Dumpster diving itself, but for perjury ter denying, then being proven to have used, information obtained by going through a rival's trash in a trade-secret case. The lesson: many collectors have never heard of SCIP's code of ethics, so defenders must think "schizophrenically" — collecting-mindset and protecting-mindset simultaneously — to anticipate this vector, while not practicing it themselves.

Human sources remain a risk after contract loss: Beyond waste archeology, competitors pursue people who know technical, management, or cost details of a proposal. Practical experience shows employees often don't grasp that sensitive information retains value even after losing a competition — the collection cycle doesn't end at contract award. Real example of a dangerous loose-lips moment: an employee complaining a nth after losing a bid, "I don't know how XYZ Company could get their rates down so low… their bid rate was an average of $37.65 an hour. We couldn't get any closer than $46.25, and that was with building a whole new cost center, cutting benefits… and moving to cheaper facilities" — this kind of remark hands a competitor exact competitive-cost intelligence, well after the "danger" seemed to have passed.

The "Warning Notice" Device and Ethical Framing

Because presentations on this topic repeatedly draw questions like "do you actually do this?" or "are you violating legal/ethical standards?", a recurring disclaimer format is introduced, borrowed from old government sensitive-document warning labels (e.g., "WARNING NOTICE: SENSITIVE METHODS AND SOURCES INVOLVED"). The book adopts its own runniel: "WARNING NOTICE: TRY THIS ONLY AT HOME" — a reminder that discussed practices are done against an adversary for a client, not practices the firm itself advocates performing on others.

The Business Intelligence Protection Model (Process Overview)

This is a cyclical process mirroring the earlier-described collection process, but running counterclockwise, and it starts at the top of the organization with leadership tasking. The guiding question shifts from "what keeps you awa at night about your rival's plans?" to "what keeps you awake at night for fear that your rival is going to find out about what your firm is about to do?"

Steps in the cycle:

1. Requirements Definition — Leadership tasking narrows focus onto genuinely critical concerns (continuity-of-business elements), avoiding a "y who cried wolf" dilution of attention across non-critical items. Example requirement questions include: What investments is the firm making in new product development? What new products/services launch within the next year? What is product X's reliability or product Y's quality measurement? Who are strategic partners and what's the nature of those relationships? Who are primary customers and the true nature of those relationships?

2. Define Protection Requirements — Broad tasking gets refined into specific suomponents ("cues"). At this stage you identify exactly where critical information is visible to an outside observer, catalog and matrix it against who has access, and realistically assess how that information is actually handled, stored, and treated by those with access — not just how policy says it should be handled.

3. Assess the Competition — Not a full competitive assessment of the rival's whole enterprise; narrowly focused only on the rival's capability and competency to collect information about your firm and use it to advantage (their internal resources/processes). Tools include four-corners analysis and SWOT analysis.

4. Vulnerability Assessment / Red Team Analysis — Attack yourself using the same techniques yoal is known or reasonably assumed to use. Critical warning: this must be done "outside-in" — using only what an external adversary could plausibly know or discover. Using inside knowledge to shortcut the exercise corrupts the process and produces a false sense of security. If internal resources, time, or inclination are lacking, use a trusted outside consultant — but execute an NDA first, since exposing your weaknesses to a third party carries its own risk comparable to what a rival might

   • Legal payoff of self-testing: The Economic Espionage Act requires demonstrating that a company took countermeasures appropriate to the threat environment and understood the sophistication of threats it faced, including having tested its own defenses. Documented self-testing records help convince a judge that reasonable protective steps were taken — and can inferentially suggest that if a company replicated every legal method an adversary might use and still detect a compromise, the actual breach must have been illegal.

5. Develoand Employ Countermeasures — Should match the vulnerability profile, competitive environment, and internal cultural/operational realities. No universal one-size-fits-all solution (chapter 18 has more specific options).

6. Analysis —t effectiveness, sometimes simply by re-running the Red Team exercise to confirm previous levels of leaked information are no longer obtainable. More sophisticated cases require monitoring how the competition reacts to new countermeasures and adjusting further.

Deception as a legitimate countermeasure — introduced here as an "outcome" that need not be viewed as a dirty or malignant tactic.

Case example — "Who's Afraid of Virginia Lobo?" (Johnson Controls vs. Honeywell): Johnson Controls invested roughly $20 million over three years developing a digitized building-control technology for smaller commercial buildings, code-named "Loba" (after mathematician Nikolai Lobachevsky) to hide it from Honeywell. Honeywell's sales force got wind of the project — but garbled the name to "Lobo" — n probing for details roughly ten months before Johnson's planned launch, enough lead time for Honeywell to close the first-to-market gap if it acted. Management rejected the idea of rushing the launch early to preempt Honeywell. Instead, Johnson Controls ran a deliberate deception: they spent about $500,000 on a loud, splashy ad campaign promoting an unrelated, genuinely minor product upgrade under the "Lobo" name. Honeywell took the bait, dismissed it as a minor upgrade (correctly, for that decoy product), grew overconfident, and slowed its own competing efforts. In February 1990, Johnson Controls launched the real product — the near-flawless Metasys system — on time, on budget, to strong reviews, while Honeywell had squandered the warning window and lost millions in market opportunity. The chapter poses atorical challenge: viewed outside the "intelligence" framing, this would simply be called "smart business" — the ethical character of the tactic doesn't change based on labeling it counterintelligence.

7. Disseminaon — Results of the analysis/countermeasures effort must reach everyone who can use them, not just the leader who originally requested the press. Recipients can include other divisions, groups, or business units; joint-venture or strategic partners (so they can shore up their own defenses and avoid indirectly exposing your organization); and — importantly — your own internal competitive-intelligence collectors. Sharing findings with your own collection team is valuable because there's typically a direct link between what a rival is currently asking about and where that rival intends to go next; feeding this back into active internal collection can help identify a competitor's marketplace intentions faster than almost any other method.

Chapter 15: Who Are Those Guys and Why Are They Doing Such Terrible Things to Us?

From What to Who

Having established which internal topics need protection (Key Protection Topics, or KPTs) and which subelements collectors focus on, attention now shifts from what is being targeted to who iing the targeting. Identifying and assessing your business rivals' capability and orientation toward intelligence collection is the next necessary step in building a protection program.

The Old, Flawed Threat Formula: Capability Equals Threat

For decades, national security thinking used a simplistic formula: if an entity was an adversary and had capability (real or assumed), it automatically counted as a threat — full stop, triggering countermeasures (bigger weapons, currency destabilizion, infiltration of hostile groups). This approach was often paranoid and simplistic, especially among those practicing it themselves. It fell prey to "mirror-imaging" — the well-documented tendency in international relations to assume your opponents harbor the same evil intent and capabilities you would have in their positio

As budgets tightened, smarter questions emerged: "Can they really hurt us?" "Do they really have the capability?" and eventually "If they have the capability, do they also have the intent?" and "What indications show they mean business?" This produced an improved formula: Capability + Indicators = Threat (C + I = T). This threat-assessment model — assessg a rival's capability to collect valuable competitive information and use it against your interests, plus the indicators of their actual intentions and collection activities — frames the rest of the chapter.

Non-Obvious Point: Your Rivals Aren't Just Market Competitors

Threat assessment must extend beyond direct marketplace competitors to any party with an interest in your company's activities and how those activities affect them — labor unions being a prime, underappreciated example.

Case Study: "Wearing the Union Label" — The American Airlines/APFA Strike

This case illustrates an "unlikely" but highly capable intelligence rival.

Background: At 6:00 A.M. on a Monday just before the year's heaviest travel holiday, the Association of Professional Flight Attendants (APFA — under 22,000 members) struck American Airlines. CEO Bob Crandall framed it as a routine management-laboe; APFA saw it as a battle for public opinion that would translate into political pressure on Crandall. APFA anticipated American's likely two-pronged strategy: (1) downplay the strike's impact while projecting "business as usual," and (2) blame inconvenience on a handful of malcontents. American, by contrast, had little insight into APFA's plans or its intelligence capacity — a critical intelligence-gap failure that proved fateful.

Actions/Tradecraft:

• APFA cultivated a wide human-srce network: sympathetic pilots, non-striking flight attendants, baggage handlers, and reservationists.
• Pilots laying over in cities took rooms on hotel top floors to visually track tail numbers of every American flight taking off/landing, reporting observations every 15 minutes to a floor-below command post.
• Local command centers (equipped with PCs and fax machines) relayed pilot observations to APFA's Dallas headquarters hourly.
• When Crandall publicly claimed normal operations continued reliably, APFA countered within an hour with highly accurate, uncontestable detail.
• When Crandall pivoted to claiming flights were fuller than ever (seemingly corroborated by TV footage of full arrivals), baggage handlers' reports revealed a suspicious drop in baggage volume despite full flights. Reservationists then resolved the puzzle: most "passengers" creating the illusion of normalcy were actually off-duty management and their families repeatedly flying city-to-city as pseudo-passengers.
• Airport "runners" fed these statistics to local centers, which relayed them to Dallas, producing consistently accurate numbers that discredited Crandall even when he told the truth — the media and public no longer believed him.
• The White House, despite stating it would stay out of the dispute, was drawn in. Crandall ultimately agreed to terms, framing it as deference to presidential involvement — but APFA quickly revealed to the public that Crandall himself had sought that involvement to disguise a labor defeat as diplomacy, further embarrassing American.

Takeaway: APFA won a Davi-Goliath contest because it anticipated how the battle would be fought, asked precise questions in advance, cultivated the right sources to answer them, built rapid/reliable reporting and analysis chains, and knew how, when, and to whom to disseminate the resulting intelligence. Practical application: identify unconventional or "unlikely" competitors (unions, activist groups, regulators) who may run intelligence operations against you with more sophistication than traditional market rivals.

Assessing Capabilities: A Taxonomy of Intelligence Collectors

Collectors vary widely in method and ethics; four broad categories:

1. Ethical open/legal collectors — abide by the Society of Competitive Intelligence Professionals (SCIP) Code of Ethics, using open, legal, ethically bounded methods.
2. Legal-but-situatnal-ethics collectors — stay within the law but are guided by "whatever it takes" pragmatism rather than a formal ethics code; may or may not use structured intelligence processes (often ex-private investigators). 3Boundary-testing/illegal collectors — approach or cross legal lines: bribery, compromising position tactics. These are the population most eosed to prosecution under the Economic Espionage Act of 1996. Some self-identify as "information brokers" — a label also used by fully legitimate brokers, creating ambiguity.
3. National intelligence officers — collect on behalf of home-country companies using state tradecraft: human-source exploitation of weaknesses/foibles for compensation, plus technical means (satellite imagery, clandestine listening devices, voice/data intercepts).

Practical application: Match your defensive posture to your most aggressive real rival, not your weakest one. Building defenses calibrated to your least threatening competitor leaves you exposed to harder-playing rivals; conversely, over-building defenses against feeble threats wastes money disproportionate to actual risk.

Nuance Within the "Ethical" Category

Even SCIP-adherent firms show a spectrum of aggressiveness — some combine primary anddary source techniques; others restrict themselves to public/open material (patents, technical journals, media). Notably, some ostensibly conservative firms still outsource aggressive collection to independent contractors — sometimes routed through law firms specifically to cloak the work under attorney-client privilege and avoid direct fingerprints.

Three Practical Approaches to Assessing a Rival's Capability

Approach One: Conference and Public-Forum Intelligence

Attend competitivintelligence seminars/conferences (SCIP and similar), or tap your network for someone who has. Speakers — often self-funding their attendance — publicly disclose department structure, budget, and methods, frequently motivated by recognition or self-aggrandizement. Non-obvious warning: the popular belief that intelligence practitioners are especially resistant to elicitation is unfounded; Q&A sessions at these events routinely produce answers more revealing than the presenter intended. A single phone call to a practitioner inside a ta firm can also kick off a capability assessment.

• Cross-border angle: where corporate intelligence needs are served by a home-country's national intelligence service, review published memoirs/interviews of relevant intelligence leaders for policy signals (referenced further in Appendix B).
• Legal-history check: review whether a rival has faced EEA charges or state-law civil/criminal complaints. Warning/non-obvious point: even a company found liable or guilty may not change its behavior if the risk-versus-gain math still favors continued misconduct (the chapter cites the Hitachi–IBM "Adirondack Cookbooks" matter, further discussed in Appendix B, as an example where a firm accepted fines as a cost of doing business).

Approach Two: Debriefing New Employees From Competitors

When hiring someone recently from a rival, systematically ask about that rival's CI operation: who runs it, headcount, reporting lines, number and type of sources/correspondents used, vendor/subcontractor relationships relied upon for information, pastuccesses and failures, training provided to BI staff and correspondents, and whether the rival restricted itself to open sources (magazines, newspapers, newsletters, government filings) or went further. Key point: the rules of engagement for debriefing in "protection mode" should differ from debriefing in "collection mode" — this is presented as an ethical/practical distinction worth deliberately deciding on rather than defaulting to.

Approach Three: Freedom of Information Act (FOI Logs as a Defensive Tool

Government agencies maintain FOIA logs recording every request submitted (who asked, when, what was requested, what was released or withheld and why) — largely for bureaucratic CYA. Non-obvious/practical tactic: these logs are themselves public records and can be requested under FOIA. Requesting andoutinely reviewing your own FOIA log reveals which competitors are filing information requests about your company, how often, and in what subject areas — turning a collection tool into a counterintelligence indicator stem. (The chapter flags more on FOIA's defensive use in Chapter 17.) Supplementary approach: network with peer industry security managers to share intelligence on which firms play close to or over ethical/legal lines, since not all misconduct results in litigation or public record.

Assessing Indicators of Intent

Capability alone doesn't equal threat — intent must also be evaluated, and intent can change suddenly.

Mergers and Acquisitions as an Intent Trigger

A small, previously unthreatening rival ("Alfatah Products") can suddenly gain both competency and intent when acquired by a large company ("Behemoth Industries") with a formidable, well-resourced BI unit. Warning: based on over twenty years of professional observation, security management teams at most companies never track competitors' M&A activity or assess the intelligence capability of an acquiring parent — their attention is fixed on personnel safety, physical security, and guarding plant/materials/documents, not business-side developments. This is presented as a emic blind spot leadership rarely questions.

Trade Show and Communications Indicators

Ask booth staff at trade shows about repeat visitors who ask probing questions or make unusually frequent visits — these are direct behavioral indicators of a rival's active interest. Similarly, track (without eavesdropping on content) which outside phone numbers are calling into your company and which departments/employees are receiving them — patterns from "researchers" or persistent unknown callcan flag active collection interest. The chapter notes most organizations have never even asked employees to report on the nature of such incoming calls.

Case Study: "Indicating Our Intent" — The "Little Guy" / "New Company" Cautionary Tale

An anonymized case (names changed) illustrating that even a large, well-resourced mpetitor's BI unit can miss glaring indicators when they're not tasked to look for them.

Sequence of events:

1. A small, innovative, privately held tech firm ("Little Guy") in a high-tech incubator city is acquired by an aggressive conglomerate ("Large-Time Charles/Behemoth"), including a three-year noncompete clause on the original owner. Large-Time Charles has a well-regarded, senior-placed BI unit, but it plays little role beyond the acquisition itself.
2. Three years later (once the noncompete lapses), Little Guy's original owner starts a new firm ("New Company") nearby, funded partly by proceeds from the earlier sale plus friendly bankers, and aggressively recruits Little Guy's best engineers.
3. Recruited employees maintain regular contact with old colleagues still at Little Guy — frequent calls "just to keep in touch," casual lunches at the old plant, informal walk-throughs of engineering/production areas — gradually extracting technical and product-roadmap information under the guise of friendship.
4. Over roughly five years, Little Guy's technical talent and edge steadily drain to New Company. New Company goes public and triples its opening-day stock price the same year Large-Time Charles installs new management at Little Guy to try toerse declining fortunes.
5. Eighteen months later Large-Time Charles puts Little Guy up for sale; no buyers are interested in a firm stripped of quality people and product, and it is shut down as "a declining market segment."
6. New Company earns the nickname "Little Guy East" (it was located three miles away, on the eastern edge of the same industrial park) due to the sheer visible volume of calls, visits, and hires from Little Guy.

Non-obvious insight: the indicators were blatant and continuous — stated intent to compete in the same market, visible brain drain, and ongoing informal technical reconnaissance — yet everyone inside Large-Time Charles dismissed them as unimportant, trusting instead in the company's deep pockets, "world-class" BI organization, and general market savvy. The only beneficiaries wNew Company's shareholders. Practical warning: organizational overconfidence in resources or reputation can blind even sophisticated players to obvious collection/competitive indicators happening in plain sight.

From Assessment to Action: FUD (Fear, Uncertainty, and Doubt)

FUD is the deliberate introduction of wedges between a competitor and its important relationship partners. It can be used offensively (to disrupt a rival's product launch — referenced as covered in the French case "Mirror, Mirror on the Wall" in apter 18) or defensively, as in the counterintelligence example below.

Case Study: Ramparts Plastics vs. Holt Manufacturing Industries (HMI) and Rubie-Jones LLC

Client firm "Ramparts Plastics" used FUD defensively after its BI consultancy rival "Rubie-Jones LLC" (working for Ramparts' major competitor HMI) reportedly made aggressive, unwanted overtures toward Ramparts' secretarial staff. Ramparts' president, Chuck Ferris, judged direct complaint useless and tasked his protection staff with covertly neutralizing Rubie-Jones without alerting HMI. A plan was approved within a month and executed in three parts:

1. "Poisoning the well": Ramparts deliberately leaked pre-approved but subtly erroneous competitive information through multiple channels — some placed where Rubie-Jones's monitoring would pick it up, some fed to specific Ramparts employees of questionable loyalty (without revealing their unwitting role). The goal was to get enough cross-corroboration through multiple independent-seeming channels that Rubie-Jones's own (weak) source-validation process would treat the false information as verified, feeding it into HMI's decision-making and progressively degrading HMI's trust in both Rubie-Jones and its internaBI department — ultimately reducing HMI's reliance on Rubie-Jones and damaging its internal BI unit's credibility.
2. Seeding distrust via a bogus RFP: Ramparts invited Rubie-Jones — ostensibly one of four bidding firms — to submit a proposal for a fabricated BI project that (carefully, without revealing real business ) also included HMI as a target company. This tested whether Rubie-Jones would honor its presumed exclusive arrangement with HMI by declining, or would prioritize the money by bidding. Rubie-Jones bid, which effectively answered the loyalty question and set up the next phase: portraying Rubie-Jones as an unreliable, disloyal supplier to HMI and to the broader industry.
3. Capitalizing on the doubt: At a professional meeting roughly six months later, Ramparts' BI manager deliberately raised critical comments about Rubie-Jones's proposals (calling them overly boastful or overpriced) to another practitioner, timed and positioned to be overheard by HMI's own BI manager — then feigned surprise and abruptly changed subject upon "noticing" him nearby, adding theatrical credibility.

Outcome: HMI stopped using Rubie-Jones, interpreting the accumulated evidence (declining performance plus the bogus-RFP response) as proof Rubie-Jones was "playing both ends against the middle" and shopping around — including approaching Ramparts — using insider knowledge of HMI's business. HMI's leadership then rejected BI outsourcing altogether, straining its own internal BI unit, which was ultimately downsized under a "what have you done for me lately" standard.

Keaway: through careful, patient application of FUD, Ramparts effectively blinded HMI's leadership — precisely the outcome that defines the goal of counterintelligence: active measures to identify and neutralize a business rival's intelligence collection activities.

Chapter 16: Just How Vulnerable Are You to Your Rival's Collection Activities?

Core Premise: Attack Yourself the Way Rivals Would

Protecting information requires replicating the actual collection methods rivals use, n the methods a firm assumes they use. In military terms, fighting the wrong enemy on the wrong battlefield produces false confidence; the same holds in intelligence work. Testing vulnerabilities without mimicking real rival tradecraft leaves an organization protecting the wrong things from the wrong people.

A key psychological trap is "mirror-imaging" — assuming rivals follow the same ethical constraints your own organization does (e.g., the SCIP Code of Ethics). Countries make disastrous decisions in war by imputing their own motives and lits onto adversaries; companies do the same when assessing competitive threats. It's not enough to inventory a competitor's in-house research capability — a firm must also determine what work that competitor outsources: consulting firms that provide deniability, investigative firms sheltered by attorney worproduct privilege, or a foreign division operating with different legal exposure. Foreign competitors especially often route sensitive collection through separate entities to avoid leaving fingerprints.

Why Active Vulnerability Testing Is Rare — and Legally Necessary

Aggressive, active testing of a company's defenses is uncommon in corporate security, which tends to default to a reactive "gates, guards, guns, and dogs" posture. Reasons include leadership simply not wanting to know the truth, and security departments lacking the mandate or skill to move from passive to anticipatory defense.

Beyond business logic, there is a legal dimension: in a trade-secrets misappropriation lawsuit, a company cannot win relief from a judge unlesit can demonstrate it valued the information enough to actively protect it. Without documented vulnerability testing, there's no way to prove "reasonable measures" were taken consistent with the actual threat environment.

Case Example: SouthTech — Setting Up the Test

A composite case (SouthTech) illustrates the model. The tasking came directly from the CEO (Tim French), who was preparing a major technology investment. When told existing security was "tight enough," he asked which subornates would personally stake their careers on that claim — nobody volunteered, which he treated as proof that security needed re-examination. This produced the key protection topic: protect the project from all domestic and international competitors until product launch.

Five key protection questions were distilled:

• What tenology/technologies are involved?
• How much investment is being made?
• What market value is the new product expected to yield?
• What are the project timelines, including rollout date?
• Who are the strategic partners and what are their technical contributions?

Profiling Five Rival Collectors

Assessing collection capability meant building individual threat profiles for five competitors, each with a distinct collection style:

• Alabaster Technologies (domestic): Business Intelligence unit grew out of the corporate library, led by a librarian; strong technical/open-source collection, virtually no human-source (HUMINT) work.
• PrimeFusion (domestic): Small internal CI staff functioning as project managers overseeing three separate outside consulting firms, each specializing in public sources, primary/human sources, and technical analysis respectively.
• NucoMan Industries (Japanese multinational): Large, strategically valued in-house BI staff plus a 12-person detachment renting space at the U.S. Patent Office to track patents/trademarks via Japan's Ministry of Industry and International Trade. Used a Washington, D.C. law firm for FOIA requests, since as a non-U.S. entity it lacked "U.S. person" status to file directly. Prior litigation showed the firm had been accused of trade-secret misappropriation three times, with documented tactics including ruse interviews, false employment applications, misrepresentation of interests, and violations of joint-project confidentiality agreements.
• Schlitzohr (European): Heavy reliance on American consulting/investigative firms; had previously solicited questionable/inappropriate collection projects; linked to the French intelligence service (DGSE) in an exchange relationship for overseas support assets.
• Kimchi Electronic Products (Korean): A newer, unknown quantity requiring fresh research. Found to have an aggressive Pacific Rim collection history and multiple trade-secret complaints against it. Its U.S. unit, led by a former Korean intelligence officer, grew from 1 to 9 people in under a year and used firms that explicitly rejected the SCIP Code as "Pollyanna-ish," operating on a "whatever it takes" philosophy.

Because this threat environment included players willing to go well beyond ethical collection norms, the vulnerability test itself had to replicate aggressive tradecraft to produce an accurate assessment — while staying within two firm boundaries(1) never publicly identify by name any internal employee-sources, unless illegal activity was uncovered, and (2) never replicate actual illegal acts (breaking and entering, theft, bribery, illicit eavesdropping). Strict secrecy/confidentiality agreements were signed given how compromising the findings could be.

Starting Point: No Inside Help Allowed

To preserve the integrity of the exercise, the client could not brief the test team on any project details — testers had to operate exactly like a genuinely hostile outside competitor, starting cold. The assumption was that open/public secondary sources would be thin (the topic was too new to have been written about), so the priority was identifying human targets who could provide current intelligence rather than historical background.

Leadership Tracking (Warning: aggressive technique)

Testers began from the premise that a project thilarge would be run by one of a small number of senior executives. Roughly ten phone calls identified Jack Isaacson as the only senior executive unaccounted for in the normal executive suite — he'd been largely absent from headquarters for two months. Physical surveillance (an early-morning drive-by of his neighborhood, followed to a different part of the city) led investigators to an unmarked "skunkworks" facility with security guards visible through the glass doors.

From there, roughly 70mployee cars were observed in the lot over a morning; license plates were run through a cooperating private investigator, yielding names and addresses for nearly 60 people overnight.

Literature-trail technique: Once Isaacson's name was known, researchers searched for his published articles/monographs (about 60 found over 25 years), mostly co-authored with a stable group of collaborators from his college years who had scattered into business, government, and academia. Three of these old associates had recently relocated to the same metro area as the company — a strong signal of insider recruitment for the project. One who stayed in government proudly discussed his old colleagues' inresting research (a classic example of over-disclosure by someone with "no stake in the end result" — an elicitation principle: people who aren't personally accountable for outcomes tend to talk more freely).

Names of on-site staff were then run through the same literature-search process, which both hinted at underlying technologies and revealed coauthors working at companies that turned out to be the project's technology partners.

Nontraditional Instruments: Bogus Surveys

Within a week of identifying employee names/addresses/phone numbers from license plates, researchers called employees at home posing as a State Department of Education survey assessing whether local school curricula prepared students for future science/technology careers. This targeted the likely technologist population and had zero real interest in the answers — the survey was purely a pretext to get people talking. echnique note:** Opening with formal survey questions functions like the opening of the "conversational hourglass" — it created an opening to use elicitation techniques that drew subjects into discussing their actual job responsibilities. The survey's closing "demographics" section (education level, whether working in trained field, salary range, marital/family status) fed directly into planning the next round of contact.

Non-obvious point: It often didn't matter whether the actual empyee or their spouse answered — spouses were frequently more willing to discuss a partner's education, position, and compensation than the employee would be. This illustrates a core elicitation principle: people don't guard information that isn't directly "theirs" to protect.

Reaching Out: Getting the Internal Directory

Since the target company had trained switchboard operators to flag suspicious inbound calls asking to be connected to project staff, and had moved to an all-electronic internal phone directory (eliminating the option of phically lifting a paper directory from a lobby), a workaround was needed.

"See Jane Run" — extension-scanning technique: Testers dialed sequeial extensions near the main published number (e.g., 555-5718, 5719, 5720) until reaching a live person. Using a pretext (posing as a small vendor, "Bill Jenkins," chasing an unpaid invoice), and simply asking by name for someone even after being told they'd reached a different person, the target ("Jane Doe") was so eager to help that she voluntarily supplied the internal dial-in number for the automated employee directory — even volunteering the opinion that it was "stupid" the directory wasn't available externally. Within two hours, five researchers reconstructed the entire company directory by dialing in, alphabetically, and letting an automated voice-recording system read off names/extensions, using "press 3 for next" to page through the list.

Warning: researchers explicitly noted they would have resorted to hacking the intranet if the low-tech method hadn't worked, and stated that many perienced, professional hackers do this kind of work "for defensive purposes" — i.e., legitimate vulnerability testers also use hacker skillsets.

Ruse Interviews and Fake Job Offers

Three days later, employees previously profiled via the bogus survey were called at their offices under a fake executive-recruitment pretext — a common real-world tactic outside SCIP ethics. Because demographic/income data was already known from the survey phase, the fake "opportunity" could be tailored prely (slightly higher responsibilities, meaningful pay bump, other incentives) to make targets start "selling themselves," which meant describing their most recent project work in detail — exactly the leverage sought.

Who's Hiring Whom — a second-order lead: One employee, though happy in her job, referred (as headhunters ally ask) another candidate who'd recently interviewed for a project role but hadn't reached agreement — including the candidate's name and city. That candidate was called at home under a "HR quality-assurance survey" pretext (checking on interview experience). He disclosed everything: which headhunter placed him, how thoroughly (or not) his references were checke and his overall impression. Learning that his references were never actually verified before the interview series was the critical finding.

Practical application — planted false candidate: Using this gap in the hiring process, testers built a fully fabricated identity (false name, false university, but consistent with the real associate's actual technical background) for one of their own people and had her scheduled into the next interview round. She had no trouble signing the company's NDA because "she only existed on paper" — the information gained in the interview series far exceeded the cost of building the fake resume/ID.

Waste Archeology (Dumpster Diving)

Junior team members were specifically trained as "waste archeologists" to test whether the company's shredding policy was actually being followed, not just whether it existed on paper.

Findings across two Dumpsters:

• Dumps#1 held properly cross-cut shredded material — nearly impossible to reconstruct — showing that policy compliance existed for at least some material.
• Dumpster #2 held entirely unshredded waste, including financial-planning documents discarded simply because they were photocopied imperfectly (crooked, off-center, poor quality).

Core warning/rule stated directly: "The trash can nearest the photocopy machine is the most dangerous piece of equipment in any company." Unclear, off-center,ra, or badly stapled copies routinely get thrown away as regular trash rather than destroyed according to the sensitivity of their content — the assumption being that anything not "pretty enough for the boss" has no value. Paradoxically, documents torn into pieces (an amateur attempt at destruction) are actually a signal to a wte archeologist that the tearer believed the document had value — making it an even more attractive target, since torn pieces are far easier to reconstruct than cross-cut shredding.

Specific items recovered from unshreed trash included:

• A spreadsheet of employee "burn rates" and staffing needs by research team.
• Internal/external emails.
• The company's internal code name for the project.

NDAs Aren't Worth the Paper They're Copied On

Torn (but reconstructable) copies of signed non-disclosure agreements with eleven different partner companies nationwide were recovered. The mere existence of an NDA between two firms signals something significant and sensitive is underway. Researching each partner company's specialty area opened entirely new lines of inquiry and new candidate sources — and it was straightforward to cross-reference partner-company employees with published technical papers to identify who specifically was involved.

Test Marketing

A discarded copy of a test-marketing proposal from an outside research firm revealed the exact schedule of cities where the prototype would be tested. This let testers insert their own associates as fake participants in the market-testing sessions, from which the marketing firm's own representatives dclosed more about the prototype (design, function, price, size) than they should have — demonstrating that a hired vendor can become an unwitting leak vector.

Black Contracting

Discarded receipts revealed payments to three "consulting companies" for materials and equipment. Two of these consultancies had local addresses but no phone-book listing — one address was recognized as the home address of a senior project employee, and the "consultancy" name matched that employee's initials.s is a cutout structure (called "black contracting" in the private sector, mirroring how government agencies disguise sensitive procurement) — using trusted employees as pass-through purchasing fronts so that outside suppliers never learn what agency/project is actually behind an order, protecting against anyone "followinghe money."

Follow-on technique: Testers called each identified supplier posing as the "consultant," claiming to have lost their purchase records, and asked the supplier to fax replacement copies of the receipts to a public fax line at a local copy shop. Some receipts only listed part numbers/quantities, requiring an additional call for a supplier catalog to decode what was actually purchased. Cross-referencing ordered parts against wasted/discarded prototype components recovered from the Dumpster let technical analysts begin reconstructing what was actually being built.

An Eye for an Eye — Counter-Surveillance Discovery

Systematic Dumpster surveillance established three baseline patterns: when trash bags were deposited (8:30–9:30 PM), when Dumpsters were serviced (Tue/Thu/Sat, 2:30–3:00 AM), and whether security patrols covered the Dumpsters (they did not). One night, an unauthorized non-guard individual was seen entering the shredded-materials Dumpster. Deliberate light counter-surveillance (a car parked in plain view, engine off, radio on) drove him off empty-handed; he then left in a pickup truck that was tailed and identified via license plate as belonging to a licensed private investigator — presumably hired by a rival to raid theash stream.

Two operationally interesting notes: the PI "never paid much attention to people following him" (accustomed to being hunter, not hunted), and he was known to talk too much when relaxed — both weaknesses later exploited.

Deception countermeasure implemented: Rather than blocking the PI outright, the team — with the client's approval — arranged to feed him only pre-screened, sanitized "trash." Surveillance later caught him visiting four other Dumpster locations across-mile radius tied to the client's other buildings before ever reaching the target facility. Once this was known, one additional Dumpster at another client building was placed under internal security screening, and the test team began nightly swaps: removing his access bags and replacing them with pre-vetted decoy trash before he arrived (typically around midnight). After a handful of nights, the PI stopped even bothering with the properly shredded Dumpster, having concluded (correctly, per design) that it never contained anything useful — while remaining unaware he was being fed carefully controlled information the entire time. He remained under surveillance through the final CEO briing and was factored into follow-on recommendations.

E-mail Elicitation

Analysis of headhunter-interview responses identified employees who appeared to have little personal life outside work (based on drive-bys of homes/apartments and condition of vehicles) — an "ideal population" for long-term online relationship-building. Using e-mail naming conventions inferred from previously obtained emails, researchers located these individuals as frequent posters in general-interest online groups (e.g., singles, backpacking, cat-lover forums) and initiated contact there rather than at work, using noncompany/free e-mail addresses. Over time these relationships yielded genuine technical details about the challenges employees were solving day to day.

Chatty Cathy — Stock/Investment Chat Rooms

Public companies attract analysts, disgruntled investors, and proud investors into online financial chooms, all of whom can be engaged simply by expressing interest in the company's stock performance or future prospects. It was in exactly this kind of forum that testers first heard the project's internal code name, from an employee only peripherally connected to the project but eager to "talk up" the company's future — responding strongly to elicitation techniques called "Disbelief" and "Criticism." She eventually stated outright that the project (code-named "Blue Streak") would nearly doue the company's size within 18 months. Key insight stated directly: a code name recovered from trash is meaningless without context from another source to interpret it — "text without context is pretext."

Restaurant Coverage (Physical Eavesdropping)

Because the skunkworks facility had no cafeteria, many employees ate at aingle nearby café. Associates simply arrived before the normal lunch rush and were already seated when employees arrived — appearing unremarkable, since arriving after someone is what looks suspicious, not being thefirst. With little in common besides the project itself, employees' lunch conversation reliably centered on their work. This low-tech "meat-and-potatoes eavesdropping" produced information surprising even to the experienced test team, and deeply unsettling to company leadership when reported.

Strategic Partner Research

Online user groups also proved valuable for profiling small, single-specialty technology partner firms. Non-obvious pattern identified: the smaller and more entrepreneurial a partner company is, the more vulnerable it tends to be — because (1) their narrow technical niche means insiders across the industry already know each other, (2) entrepreneurial culture pushes more employees into informal marketing/evangelism roles, meaning more staff know the company's direction and strategy, and (3) small entrepreneurial firms usually have no dedicated security function at all.

Dance with the One What Brung Ya

In an online jobs-focused user group, a researcher simply asked whether a suspected strategic-partner company ("X") was a good place to work. A recently departed ZYX employee responded within three days, and — despite having left — was not disgruntled and was actually considering returning, because he'd heard from former colleagues that a "very significant cash infusion" was coming into ZYX from the client company and that the technology side was looking especially promising. He freely discussed what ZYX could bring to a partnership and its outlook, all information he'd only picked up peripherally felt no responsibility to protect.

Closing Takeaway

These specific techniques are illustrative, not prescriptive — the goal is to prompt reflection on how real-world collectors actually operate today, well beyond what conventional security functions typically watch for. The chapter frames the needed shift as moving from inward-looking, passive security posture to an active, outward-facing, aggressive one — arguing it is far better to discover vulnerabilities through a controlled, friendly internal test than to learn them the hard wayfter losing a critical product, acquisition, joint venture, or breakthrough technology. The next chapter extends the same SouthTech case to show the aggressive and preventive countermeasures designed to protect the company's most sensitive information.

Chapter 17: Developing Countermeasures for Your Vulnerabilities

Context: Continuing the SouthTech Case

This chapter continues the SouthTech case study (CEO Ted French), picking up from the countermeasures point on the protection model after an assessment revealed that the company's new-product project had already been substantially compromised. Within thirty days of beginning the engagement, investigators identified the company's vulnerabilities, the likely methods rivals could use to attack it, at least one active collector already partway toward compromising the project, and information that would be worth millions to competitors if learned before product launch. The five key protection questions considered during the assessment were: what technologies are involved, how much investment is being made, expected market value of the new product, project timelines including rollout, and the identity/contributions of strategic partners. All five were answered by outside collectors within thirty days — more than French had even thought to ask about.

Reporting: Integrity Over Comfort

An intelligence or protection professional's value rests entirely on integrity and candor when reporting to leadership — the first time a collector or protector is caught fudging resu credibility is destroyed permanently, along with any future good that person could do. Practical implication: if unwilling to occasionally deliver bad news, find another line of work. French set useful ground rules at the outset: no floggings, no witch hunts, and no identification of individual employees who had said more than they should have. Once he had the status report, his focus was on recommendations and solutions rather than blame — a posture that materially improved employee cooperation later.

Recommending Solutions

The recommentions in this case were straightforward because the weakest points were not primarily physical security failures — they were a lack of employee preciation for the risks around them and a lack of cooperation with existing policies. This is described as "nothing unusual" — the most common failure pattern found in companies worldwide. Based on three factors (amount of information at risk, money involved, and the eighteen-month need for continued secrecy), a comprehensive menu of countermeasures was prepared for French to select from:

• Employee awareness training
• Employee participation program
• Document management and accountability
• Follow-up penetration testing
• Physical safeguards
• Active countermeasures
• Electronic safeguards
• A dedicated counterintelligence professional for the project's life
• Elicitation and counterelicitation training
• Background checks on new hires
• Surveillance and countersurveillance
• Close cooperation with the corporate competitive intelligence unit

Warning/caveat: some measures implemented by Fren may seem excessive for other organizations — his degree of seriousness about protecting a major investment was deliberately high, and the measures are described in detail as illustrative, not as a universal minimum (some firms go even further).

Employee Awareness

An all-hands meeting was held for the development group (over 100 people, mixing veteran staff and new hires). Senior VP Paul Kendall opened with French's own words, signaling top-level seriousness. During the roughly 45-minu presentation of findings, some employees reacted angrily, viewing it as invasive; but peer pressure — as observed repeatedly across many prior engagements — deflated that anger as coworkers reframed it as protecting everyone's shared interest. A key mitigating factor: the ground rule that no individual employee would be ideied to management reduced anguish and defensiveness. By the end, employees understood how catastrophic a wholesale compromise of the project could have been. Kendall's involvement in introducing subsequent new procedures (which French had personally approved) reinforced their legitimacy.

Company-Specific Awareness (Not Generic Training)

A critical, non-obvious insight: generic "it happened somewhere else" awareness presentations don't work. Effective awareness must be company-specific and must generate real buy-in leading to active participation — without buy-in, more signs, stronger locks, or bigger guard forces have no practical effect. The goal is protection, not paranoia. Demonstrating exactly how the specific firm's information had been compromised, using approaches actually used by named competitors, was eye-opening — many employees believed such tactics only existed in movies. This transparency, and the fact that leadership considered the problem worth sharing candidly, dramatically increased willingness to participate. Employees who previously felt treated like "mushroom factory" workers (kept in the dark and "covered with fertilizer") responded especially strongly once brought into the light.

Employee Participation Program (Reporting ine)

A dedicated hotline was created for employees to report suspicious contacts via phone, e-mail, fax, or in person — whether encountered on the job, while traveling, or at trade shows/conferences. Employees did not need to judge whether a contact was actually problematic; they simply needed to report anything that seemed off, following four steps:

1. Tell the contact it's not a good time to talk, but offer to follow up.
2. Get the requester's name, company, and phone number.
3. Note theontact information and a description of what information was sought.
4. Call the hotline (local or 800 number if traveling) to report the contact and circumstances.

The Law of Unintended Consequences — Part I

An employee asked, in effect, "if we're this concerned about being targeted, does that mean we do the same thing tother companies?" This became a self-identifying recruitment mechanism: employees who asked such questions, or who came forward afterward, often became valuable additional sources for the company's own emerging Business Intelligence (BI) collection effort.

The Law of Unintended Consequences — Part II (Social Engineering Discovery)

During Q&A, an employee descred being approached by someone claiming to be an internal IT staffer investigating "log-on troubles," who asked him to attempt a log-on at that moment — a classic social-engineering credential-harvesting attempt. The caller became evasive when asked for a callback name/extension. Five other employees reported nearly identical experiences, revealing that an outside party was actively targeting project team members specifically (not just the workforce generally). Notably, none of these five had previously thought to report the contact — showing that awareness training does not automatically translate into universal reporting compliance immediately; adoption is gradual.

Intended Consequences of the Reporting Program

Across more than 100 companies where this kind of program has been implemented, hotline reporting has consistently:

• Identified who is calling and why.
• Identified the specifiestions being asked.
• Made employees far more cautious in responses (often giving no response at all).
• Surfaced new, sometimes creative, variations on approach techniques, which could then be shared organization-wide.
• Built a tracking database usable in later legal action (e.g., injunctions) — without records, there is no legal recourse.
• Provided raw material for more aggressive countermeasures (covered in the next chapter).

Why Knowing "What They're Asking" Matters

A key intelgence principle applied to business: national intelligence services routinely try to learn what a rival's collectors are trying to find out, because this reveals the rival's intelligence gaps, needs, and reliance patterns — telling you precisely what to protect and from whom. Rather than merely hypothesizing about a competitor interests, direct evidence of their questions is far more valuable. Example: if a rival is probing specifically about progress on X-ray lasers (versus high-energy lasers generally), that specificity signals a genuine operational use for the answer, not academic curiosity. Reasons people seek this information include: benchmarking their own progress against yours, positioning to erode your market advantage at product rollout, or avoiding your R&D mistakes to save money. None of these purposes serve your stock price — this framing is offered as caution against employees rationalizing away suspicious inquiries. A footnote example: George Fisher, on taking over Kodak after leading Motorola (one of America's most benchmarked BI organizations), described Kodak's future strategy as being "an aggressive follower" — implicitly relying on watching and learning from competitors' moves.

Practical Guidance for Handling Unidentified or Evasive Callers

If an employee gets more than a fair share of suspicious calls, consider adding caller ID to that line; a blocked caller ID, or a mismatched area code, are indicator flags. Give employees scripted options rather than making them improvise: tell callers that written questions on company letterhead will get an answand frame it as company policy (make it policy if it isn't already). Most companies already route sensitive external inquiries to PR or executive spokespeople — extend that principle to sensitive project matters. Warning: legitimate BI collectors under time pressure will resist having questions put in writing (they don't want a paper trail, and don't want a fax header revealing they aren't who they claim to be) and will resist e-mail requests too because sophisticated collectors already usenonymous e-mail addresses fluently — recognize this reluctance itself as a red flag, not merely an inconvenience. A caveat/counterargument addressed: withholding your own fax numbers to prevent interception is largely symbolic — anyone determined enough to intercept fax traffic will have already war-dialed your company's num to map every fax/modem line.

Extending the Program Beyond Employees

Reporting programs and information-protection expectations should extend to strategic partners, vendors, and their employees, not just your own staff. An NDA alone is insufficient protection: most individual employees at partner firms never signed the NDA themselves, don't know it exists, and don't know its terms — usually only in-house counsel or a manager signed on the company's behf. Practical warning: verify whether partner organizations are actually taking protective measures as rigorous as your own, rather than assuming an NDA covers the gap.

Document Management and Accountability

Much of the compromised information was too available because it wasn't properly stored, controlled, accounted for, or destroyed, and was too widely disseminated to people without a genuine need for it — a very common failure pattern. Concrete measures implemented:

• Marking scheme: two sensitivity tiers, "Company Confidential" (e.g., organization overview documents like manning diagrams) and "Company Private" (documents tied to specific technological, pricing, or production advantages). Employees were trained on the distinction between the two.
• Code names appended to markings: e.g."Company Confidential BLUE STREAK," restricting distribution to those the project manager designated.
• Knowledgeability list ("bigot list"): a formal list of who is authorized to receive information about a given project. Anyone not listed gets nothing. Practical benefit beyond access control: if a compromise occurs, the bigot list gives investigators a clear starting point for inquiry.
• Document accountability/numbering: sensitive drawings, plans, and documents were numbered ("Copy __ of __ Copies") and filled in by hand in blue ink so that unauthorized reproductions would be immediately obvious. CEO also directed use of special stock paper with a yellow line across the middle to prevent illicit copying.
• Overnight secure storage: "Company Private" documents had to be stored in lockable containers overnight; anyone lacking a suitable container (i.e., no lockable desk drawer) had to hand documents to a secretary maintaining master project files — especially enforced for financial, planning, technical drawing, and st-result documents.
• Custodial logging: document custodians (typically program manager's secretaries) maintained logs recording creation date/creator, number of copies made, recipients, signatures, and destruction date/destroyer for "Company Private BLUE STREAK" materials — including electronic medilike diskettes.
• Random searches: random (not targeted) purse, briefcase, and backpack searches were conducted to deter document removal; general counsel approved this specifically because randomness avoided privacy/singling-out concerns.
• 100% shredding: mandated for all R&D facility documents regardless of apparent innocuousness — justified by the earlier "waste archeology" findings, where sticky notes with phone numbers/names, message forms, and outside-organization envelopes had been pieced together into meaningful intelligence indicators.

Follow-up Penetration Testing

Because the project needed to stay concealed for at least eighteen months, French ordered follow-on penetration tests at the 60-day, 120-day, and 180-d marks, after which further testing frequency would be reevaluated based on findings. Critically, employees were deliberately not told that additional testing would occur or when — preserving the validity of the tests. Later rounds examined both previously identified issues and new vulnerabilities arising from project changes over time.

Physical Safeguards

Specific measures ordered: locking Dumpsters (with guards responsible for unlocking them only when removal trucks arrived); guards prolling the property at irregular intervals rather than remaining stationary indoors; guards in plain street clothes instead of uniforms to avoid drawing attention; more secure storage containers; increasing shredders from two to ten; perimeter lighting at night (especially near Dumpsters); and clearing brush near Dumpsters. Non-obvious detail: these physical changes were deliberately delayed thirty days before implementation — to first exploit the existing vulnerabilities for active countermeasure purposes (see below) before closing them off.

Active Countermeasures

French reacted with anger on learning that a private investigator (PI) was routinely searching his Dumpsters, but was assured once shown how this created an opportunity for aggressive counter-response. The concepts of misinformation, disinformation, and deception were explained as distinct tools, and French selected a misinformation approach (detailed under Surveillance and Countersurveillance below).

Electronic Communication Safeguards

• Sniffers were deployed to monitor incoming/outgoing e-mail.
• Software tracked repeat visitors to the company website to help assess competitor activity.
• Broader Internet monitoring covered news, media, and discussion/user/consumer groups, because aggregate online chatter had already begun inadvertently pointing toward the secret project.
• A separate domain (distinct from the company's main domain) was established exclusively for project-related e-mail, isolating sensitive traffic from routine correspondence.
• All project e-mail and attachments were encrypted with commercial PGP, with attachments additionally password-protected via the word processor's built-in protection.
• Any curious or suspicious e-mail was routed to the project's counterintelligence specialist before any reply was sent — mirroring the phone-call reporting protocol — with special attention paid to incoming mail arriving on the project-only domain rather than the general company domain.
• No fax transmissions were permitted between development partners and the R&D facility.
• No pro discussion over cell phones under any circumstances — even the shift from analog to digital didn't guarantee encryption integrity held up; nothing was deemed time-sensitive enough to justify the risk versus waiting for in-person conversation or secure phone lines. Encrypted e-mail was an acceptable but minimized backup for trelers.

Sidebar: "Just the Fax, Ma'am" — Historical Warning

Lutz Erbe, former chief of the East German Signals Intelligence Service, revealed in a 1992 interview that East Germany routinely intercepted West German business/government phone calls. Notably, about half the time a caller who said "we shouldn't discuss this over the phone" would then offer to faxhe sensitive details instead — which the East Germans could intercept just as easily, and which tually saved them the work of transcribing a phone call. Their only real limitation was a chronic fax-paper shortage. Lesson: switching communication channels mid-conversation to "be safer" is often illusory if the alternate channel is equally vulnerable.

Dedicating a Specific Counterintelligence Professional

French assigned one individual, Billie Tolliver, full-time to the project as the single point of contact for all security and intelligence matters for the project's duration, reporting directly to the project lead (Isaacson). Her responsibilities included planning and supervising follow-on testing, developing countermeasures, liaising with the corporate BI unit and corporate security, and ongoing counterintelligence training. She later became central to the operation exploiting the PI identified through waste archeology.

Elicitation and Counterelicitation Training

As employees grew aware of how they'd been approached, follow-on training focused specifically on elicitation techniques used by professional intelligence collectors, framed as the first line of defense. Once employees could recognize these techniques, they could apply countermeasures and — when reporting contacts to the counterintelligence specialist — help assess the collection sophistication of whoever was taing them.

Background Checks on New Hires

Because the project team combined veteran staff and new hires, background checks became critical — reinforced by an earlier incident where an executive search firm placed candidates (including a fabricated test candidate created by the investigators) without verifying references or cdentials at all. Non-obvious statistic cited: some studies find over 75% of educational claims on resumes are exaggerated or entirely fabricated — reinforcing why unchecked credentials are a serious blind spot. SouthTe switched search firms and explicitly communicated stricter vetting criteria to the new recruiter. Practical/strategic constraint: SouthTech still preferred to use outside recruiters rather than advertise openly for unusual skill sets, since open job postings seeking atypical experience/qualifications are themselves a well-known signal that competitive intelligence professionals routinely monitor to infer what new programs a company is launching.

Surveillance and Countersurveillance

Two employees were embedded as staff in the two restaurants nearest the R&D facility, both known locations where employees had previously talked too openly during lunch. The purpose was twofold: verify that the awareness training had actually changed lunchtime conversation habits (it had), and identify any new "regulars" appearing during employee lunch periods (one was found). This new patron, evasive about his workplace beyond vague references to "the neighborhood," was investigated and found to be an associate of the PI conducting the waste archeology.

The PI's surveillance had been underway roughly a month; he appeared satisfied with "chicken feed" being fed to him in preapproved doses following French's briefing — deliberately salted trash bags containing documents about a canceled, unrelated project revived with fictional technologies and personnel. Billie Tolliver then engaged the PI directly at his after-work bar, posing as a friendly acquaintance. Over successive weeks she learned:

• He worked for multiple companies simultaneously, pa for information he "dug up."
• His standard method: paying part-time janitors to leave specifically colored trash bags containing documents from targeted companies' key offices, avoiding the need to search entire Dumpsters.
• He'd overheard a retired police officer acquaintance mention a security-guard job at a "hush-hush operation" — naming SouthTech — which let him locate the skunkworks and begin extracting "hot stuff," reportedly being sold to competitors including a company with "a lot of foreign money," eventually described as buyers "fAsia." Once the PI showed clear signs of relaying disinformation (the fictitious BLACKKNIGHT program) to a real customer, Billie's relationship with him deliberately cooled and ended. Confirmation followed roughly two months later: inquiries about the notional program "BLACKKNIGHT" arrived from multiple company locations; a fake "critical technology partner" front company (with only a registered name and a couple of phone lines) received nearly thirty inbound calls from suppliers, job seekers, and others — all logged via caller ID by a planted receptionist — confirming the deception had reached and been believed by the actual competitor.

Sidebar: "Blind Charlie" — The Case for Not Always Neutralizing a Known Threat

An anecdote from a Special Forces camp in Vietnam: a Vietcong sniper nicknamed "Blind Charlie" routinely shot at helicopters but never hit anything, so he was left alone — until a new camp commander eliminated him, only for the VC to replace him with a far more accurate shooter, causing real subsequent harm. Applied four months into the deception operation, the rival's competitive intelligence unit was reported actively pursuing a technical approach SouthTech already knew to be a dead end, wasting resources for nearly two more years before abandoning it. This illustrates the strategic case, addressed directly, for why the PI, the bribed janitors, and the competitor were not prosecuted under the Economic Espionage Act of 1996: it is often more valuable to keep a known, characterized adversary (whose capabilities and limits you understand and can manipulate) active than to remove them and face an unknown replacement, and marketplace advantage from a successful deception operation outweighs the satisfaction of jailing a minor operative.

Close Cooperation with the Corporate Competitive Intelligence Unit

The chapter closes by underscoring the structural linkage between protection (counterintelligence) and collection (competitive intelligence) functions — a link to be developed further as an "Integrated Business Intelligence Model." Regardlesof company size or whether a formal CI department or aggressive security/counterintelligence capability exists, the competitive nature of the business environment does not change: rules differ by country and company, but intelligence capability increasingly determines competitive advantage. The chapter ends by previewing the next chapter's more provocative territory — misinformation, disinformation, and deception as deliberate, sanctioned business tools.

Chapter 18: Misinformation, Disinformation, and Countermeasures

Framing the Terminology

This chapter opens with a quote from The Soldier's Handbook of the British Army (1869), arguing that platitudes like "honesty is the best policy" are fine for a child's copybook but a fatal handicap for anyone who must act decisively — setting the tone for a discussion of aggressive, sometimes "exotic," countermeasures used to protect sensitive information. For most people, misinformation, disinformation, and deception are treated as synonyms; for an intelligence professional, they are dist categories with different origins and applications:

• Misinformation — Webster defines it as "false or misleading information based on error or ignorance." It arises passively, without any deliberate action by the party who benefits or suffers from it.
• Disinformation — carries a more malicious intent and typically belongs to offensive intelligence operations.
• Deception — often relabeled "perception management" for political palatability — is more common in defensivss intelligence but has a clear offensive dimension when used internationally.

Misinformation: Passive and Unintentional

Misinformation describes misunderstandings or confusing elements that a business rival stumbles into on its own, through its own error or missteps, with no active role played by the target company. Example: if a rival reads a wholly inaccurate newspaper article and you had nothing to do with the reporter's mistake, the rival is simply a victim of misinformation — the fault lies with the reporter and whatever poor sourceed the exaggeration.

• A key non-obvious point: if you notice a rival making mistakes or following a flawed path based on something you know to be wrong, you are under no ethical or legal obligation to correct their misunderstanding.
• Simple prudence dictates that a rival should have investigated all available information themselves; failing to do so creates no liability for you.

Disinformation: Deliberate and Malicious

Disinformation results from an active undertaking by someone who has planned a path and an objective, then deliberately constructs false information and leaks it into a target's communication system — through media or other channels the target is known to trust — specifically to mislead the public.

• It frequently exploits existing stereotypes, prejudices, and biases, especially about a culture, race, or country.
• Prime targets are people at political or social extremes, who have little skepticism or tolerance and will accept even bizarre reporting from unreliable sources.
• The old Soviet KGB is cited as the hiical benchmark practitioner of disinformation, working hand-in-glove with the Novosti Press Agency (the official Soviet press organ) once the disinformation mission was transferred from the Ministry of Foreign Affairs in the 1950s until the USSR's collapse. Its successor, the SVRR, was redirected by post-Soviet leadership to focus on economic and technical targets rather than military and political ones — meaning any commercial enterprise outside of literal goat milking should consider itse a potential target.
• Historical example: the pervasive belief across the developing world that AIDS originated as an American germ-warfare experiment in Africa gone wrong. This narrative thrived throughout Africa in the 1980s–90s specifically because it was propagated via journalists trained at the Patrice Lumumba FreedoUniversity in Moscow, or via "reliable accounts" reprinted in Third World newspapers — carefully engineered so nothing ever traced directly back to the Soviet Union, insulating the campaign from being tied to superpor politics even though that was its exact purpose. American denials had no effect because they could not compete with locally trusted media channels repeating the story.

Case Study: "Mirror, Mirror on the Wall" — Business Disinformation in Practice

An American beauty-care company obtained French regutory approvals to launch a new facial treatment, with a July launch date. A French competitor learned of this through government sources within days and realized it could not bring its own competing version to market before September. When the American product hit French shelves, French media simultaneously ran stories — citing "reputable" Latin American and Far Eastern newspapers — describing horrific burning and disfigurement supposedly caused by the product, and noting that it wasn't even approved for sale in the U.S. The public reaction was so negative that the product sat unsold and was pulled from shelves two months later; because it had been packaged and labeled specifically for the French market, it could not be resold anywhelse. Two months later — in September, exactly when the French competitor's own version was ready — a nearly identical French product launched with no media mention of its matching chemical composition. The French firm ended up owning the entire market. Lesson: disinformation campaigns can be engineered to destroy a first-mover's product launch and clear the field for a slower competitor, using foreign media "reprints" to disguise the true source and avoid any direct traceability.

Decen / Perception Management

Sun-tzu's classic dictum is invoked: "All warfare is based on deception... Offer the enemy a bait to lure him; feign disorder and strike him... Pretend inferiority and encourage his arrogance." The core principle for business application: create conditions where your opponent forms an erroneous impression through his own labor and analysis — because self-derived conclusions are held far more strongly and are more resistant to being overturned by later evidence than conclusions simply told to someone.

• Business exple — Johnson Controls vs. Honeywell: A relatively mild but effective use of perception management, referenced back to the "Loba" code-named technology case (covered in chapter 15). Johnson Controls didn't attempt to mislead anyone until its market entry was actually threatened by Honeywell's collection efforts, at which point they actively managed Honeywell's misunderstanding of the situation.
• The BLACK KNIGHT technique (introduced in the previous chapter) represents a second level of perception management: identifying a threat to your information and responding with carefully selected, narrowly targeted information aimed at only one recipient or recipient population, designed to distract that threat from your actual activities. This depends on deliberately creating the target's error or ignorance, and requires understanding how long you need to sustain the deception.

Case Study: "Adolf's Mysticism" — Deception via Exploited Certainty

Hitler's confidence in his own mystical, intellectual gfor predicting Allied actions was itself exploited by Allied planners preparing the D-Day invasion. Key mechanics:

• Documents were planted on the body of a dead British officer (staged as a plane-crash victim) that washed ashore into Abwehr hands in Portugal, reinforcing Hitler's belief the invasion would strike Pas de Calais rather than Normandy.
• A completely fictitious "notional" Army Group was created near the Pas de Calais launch point, reinforcing his belief that any landing of such scale required top forces under General Patton.
• Compromised, intentionally leaked weather and planning reports nurtured his belief that no attack could occur on June 6, causing him to hold counterattack reserves back.
• His conviction that Normandy was a diversion was so entrenched that even 24 hours after the actual landings, he refused to release reserve forces that could have pushed the Allies back into the sea.
• Every "confirming" detail was meticulously planted through channels that would validate Hitler's existing predisposition — the essence of deception being tknow which channels your target relies on, then feed only those channels the specific information you want believed.

The chapter reframes this via a reverse SWOT lens: rather than accurately assessing your own strengths and weaknesses, deliberately portray them in the opposite way to skew an observer's or analyst's perception of your true capabilities or plans.

The Seven Laws of Deception Projects

A well-developed deception or perception-management plan is far more than telling a few lies and watching for a bite. Seven near-inviolable rules are laid out:

1. First Law — Deception operations are unsuitable for poorly organized teams, people prone to rash decisions and snap solutions, or the faint of heart.
2. Second Law — Before starting, consider the effect on other potential recipients of the information — e.g., a publicly traded company whose poorly planned deception leaks to the wrong audience risks a very bad morning with SEC investigators. Even privately held firms should keep this risk in mind.
3. Third Law âe circle of people aware of the project as small and compartmentalized as any other information you must protect. Telling many people misleading things in hopes that sheer noise carries the message is counterproductive — it distorts the message so badly by the time it reaches the intended recipient that you lose control of what they actually hear, and any hope of steering the rival's behavior evaporates.
4. Fourth Law — Always mix in genuine, valuable, accurate information to lend ibility to the false pieces. A rival won't act on a single data point any more than a serious investor would make a major stock decision on one day's data; a competent intelligence analyst wants corroboration from more than one source before accepting a single data point as fact. Consequently, deception typically requires senior-level approval, since it often means authorizing release of real, valuable information to give the bogus material credibility.
   • Case study — "For Whom the Bell Tolls": A client's repeat customers stopped reorring, citing unanswered calls; internal blame-shifting followed (phones, "lazy" salespeople, suspected bugged conference rooms). During an unrelated visit, consultants noticed the sales VP checking voicemail via analog cell phone during meetings and recommended checking his cell phone rather than just sweeping for bugs. A technical countermeasures team swept headquarters (finding nothing) then tracked the VP's cell phone dialing sequences from outside his home the next morning, capturing the codes he used to access the company's toll-free voicemail. The team called in, listened to and recorded pending messages, then deleted them. The president, informed of this penetration, then executed a deception operation: he recruited four of his oldest, most trusted customers, gave each a newly established, single-use phone line, and had them call the sales line requesting a callback to place an order, leaving the new number. In three of four cases, the callback came not from the client's own company but from a sales rep at one of its most aggressive competitors — proving the competitor was intercepting the voicemail system. Rather than pursue legal action, the client chose a more imaginative resolution and continues to benefit from an arrangement with the other firm.
5. Fifth Law — Define a clear desired outcome: what specifically do you want the rival to do? You must also have the means to determine whether the rival is actually following the trail you've laid, since a deception project can absorb significant time and resou with no way to gauge effectiveness. Equally important: know in advance what you'll do once the target actually takes the bait.
6. Sixth Law — Applies when acting defensively to trace an information leak from within your own organization, noting that leaks frequently happen unwittingly. This requires the ability to trace thflow of information, meaning "poison pill" (planted false) information must be carefully and precisely distributed with a complete record of exactly what was told to whom.
7. Seventh Law — Protect precious sources of information even when it means not using extremely valuable intelligence, echoing Winston Churchill's WWII-era principle: "In wartime, truth is precious that she must always be surrounded by a bodyguard of lies."
   • Historical example — Ultra/Enigma: The Allies obtained a German Enigma machine in 39 through Polish Intelligence efforts, and later a newer model through a heroic recovery from a sinking U-boat in the North Atlantic. Had the Germans learned their "unbreakable" codes were being read daily at Bletchley Park, they would have changed them immediately. This forced extreme judiciousness in using Enigma-derived intelligence — famously extending to Churchill's decision not to warn Coventry (a city of no strategic or tactical value) of an incoming German terror raid, since scrambling defensive aircraft with no prior bombing history near the city would have signaled to Germany that its codes were compromised. Churchill accepted responsibility for roughly 1,500 dead and several thousand wounded, weighing those losses against t tens or hundreds of thousands of lives potentially saved by continuing to read Enigma traffic undetected until it was needed most, just months before D-Day.

Closing Reflections

Business situations rarely involve literal life-or-death stakes, but the underlying lessons about protecting sources, controlling information flow, and managing perception remain directly instructive. The chapter ties these themes back to the Johnson Controls/Honeywell "Loba"/"Lobo" case and the BLACK KNIGHT technique from the prior chapter, both illustrating how misperception can be actively engineered to a rival's disadvantage.

A closing practical note: if concern exists that a company's leadership or workforce might react negatively to the word "intelligence" in a business context due to its political overtones, consider substituting different vocabulary to describe the same processes — it would be counterproductive to disadvantage an enterprise's use of these techniques purely over semantic discomfort.

For further reading on perception-manageme projects applicable to the commercial sector, Group Captain Frederick Winterbotham's book on "The Ultra Secret" and Anthony Cave Brown's Bodyguard of Lies are recommended as inspirational references.

Chapter 19: Putting It All Together

The Integrated Business Intelligence Model

Collection (competitive intelligence) and protection (counterintelligence) are framed as equally important, complementary halves of the same discipline rather than separate functions. Professional intelligence organizations worldwide treat them this way: intelligence is delivered to the decision maker in a timely, accurate form, while counterintelligence protects both the business-operations information itself and the intelligence-collection effort — the latter by applying a mindset distinct from traditional physical/IT security.

This combined approach is named the Integrated Business Intelligence Model. It's depicted as two cycles rotating in opposite but complementary directions, both originating from tasking issu at the corporate leadership level, and both feeding a single, centralized analytical capacity. That shared analysis function serves two roles simultaneously: it is the last stop before intelligence reaches the decision maker, and it also improves the effectiveness of the other cycle (protection informs collection and vice versa).

Why Integration Is a Recent Shift

As recently as five years before writing, this integration was rare. Counterintelligence (CI) departments and security departments were typically separated by organizational level, physical distance, and inclination — often unaware of or actively hostile toward one another, viewed in adversarial terms when they did interact.

That separation is breaking down because:

• Working joint projects makes practical and strategic sense once both functions engage together.
• It reinforces theost-effectiveness of multiplexing (using the same skilled people across complementary projects) discussed earlier in the book — avoiding duplicated effort and internal competition for resources.
• Security practitioners are shedding suspicion that competitive intelligence work is inherently unethical or illegal.
• Competitive intelligence professionals, who htorically saw no protective role for themselves, are recognizing the synergy available.
• Forward-looking leaders on both sides — security executives who've moved toward supporting the profit-generating side of the business and taken on collection responsibilities, and intelligence professionals who see the benefit of centralizing both functions — are driving the change, especially in firms where security had been subordinated to HR, safety, or other overhead departments.

Practical Application for Small and Mid-Sized Organizations

For smaller and medium organizations, the case for integration is even more clear-cut: limited headcount and resources force a combined approach by necessity, particularly once a company realizes it is already caught up in competitive pressures it hadn't fully recognized before.

A key reassurance for organizations without an existing, bias-laden CI department: ting with a "clean slate" is an advantage, not a handicap. Many readers won't build a formal CI department at all — due to size, budget, or preference — and that's acceptable. Instead, the practical goal is to stand up a lean function capable of collecting on competitors quickly, legally, and without heavy investment in staff, office space, or budget.

Core Takeaway

Regardless of scale or formality, the Business Intelligence Process — running continuously in the background organization or a designated function — is what ultimately delivers results. It converts raw competitive information into usable competitive intelligence, which in turn becomes competitive advantage. This is tied directly back to the fundamental purpose of being in business: to prevail against competitors.