Richard Bissell’s Work Algorithms

1. What scarce resource governs the problem?
2. Which incentive or bottleneck will defeat the plan?
3. What institution can coordinate the moving parts without hiding responsibility?

Translate a dramatic problem into flows, constraints, authorities, costs, and decision points before choosing instruments.

constraint map, program memo, decision dashboard

Systems thinking can underweight legitimacy and politics if efficiency becomes the only test.

1. What funds actually exist?
2. Who has authority to spend them?
3. What milestone proves whether to continue, revise, or stop?

Pair unusual ambition with milestones, budgets, and a single accountable owner.

program plan, milestone ledger, budget note

Fast funding can bypass review and leave later investigators with a thin record.

1. Which private partner has the unique capability?
2. What must remain government-owned: purpose, authority, or oversight?
3. What happens if trust replaces verification?

Create a tight customer-contractor compact while preserving government responsibility for risk.

contractor compact, requirement memo, review board

Elite trust can become unchallengeable unless paired with independent technical review.

1. What can a flexible institution do that a bureaucracy cannot?
2. What controls are needed when public power enters?
3. Which informal network must become accountable?

Borrow flexibility from non-government worlds but formalize authority once public stakes appear.

institutional transition note, governance map

Informality that helps innovation can also obscure responsibility.

1. Who is moving the decision through personal access?
2. What is gained in speed?
3. What record prevents the access network from becoming invisible governance?

Use relationships to convene the right people quickly, then force minutes, approvals, and dissent into the file.

access map, approval record, dissent note

Network speed can exclude skeptics and produce social overconfidence.

1. What cannot be known by reports, diplomacy, or open sources?
2. What resolution, timing, and coverage would be enough?
3. Who will use the answer?

Define the information gap before defending the platform.

collection requirement, target-value memo, user brief

A platform can create its own demand even when the decision need is vague.

1. Which experts are independent enough to disagree?
2. What assumption would kill the project?
3. What evidence would change the recommendation?

Use a small advisory circle to test technical claims before committing national authority.

science advisory memo, red-team minutes

Advisory circles can become too small, prestigious, and self-confirming.

1. What is the shortest valid test?
2. Which failure teaches the most?
3. When does speed become recklessness?

Compress development cycles while keeping decision gates visible.

test report, failure log, milestone review

A sprint mentality can normalize risk faster than political leaders understand.

1. How long before the target can detect or defeat the platform?
2. What successor must begin before the current system fails?
3. What warning shows the window is closing?

Manage U-2/OXCART/CORONA-style programs as a lifecycle rather than a one-time breakthrough.

vulnerability timeline, successor plan

Success can mask the need to stop, pause, or transition.

1. What happens if the platform is detected, captured, or publicly displayed?
2. Who owns the diplomatic explanation?
3. Is the intelligence value worth the crisis scenario?

Attach political exposure scenarios to every major technical collection decision.

exposure memo, crisis scenario, authority record

Deniability can become a fantasy when facts will be visible.

1. Who processes the material?
2. What analytic question will be answered?
3. How quickly must the result reach the consumer?

Build the exploitation chain at the same time as the platform.

processing plan, interpretation protocol, executive brief

Collection glamour can starve the less visible analysis chain.

1. Who truly needs to know?
2. Which controls compensate for fewer eyes?
3. What independent review can enter without broad exposure?

Use compact teams for security and speed, with scheduled accountability outside the compartment.

access roster, compartment charter, review schedule

Compartmentation can hide false assumptions from people who could correct them.

1. Is this intelligence, diplomacy, covert action, or policy advocacy?
2. What written authority exists?
3. Who must be notified or able to object?

Convert covert enthusiasm into an authority record and oversight map.

authority note, notification checklist, legal memo

Authorization can be treated as a formality if leadership has already decided.

1. What will observers infer immediately?
2. Which sponsor fingerprints are unavoidable?
3. Does deniability conflict with operational needs?

Test the public story against observable facts before approving the action.

deniability ledger, exposure narrative, press-risk memo

A plan can be too large to deny yet too constrained to succeed.

1. Who does the partner represent?
2. What support exists inside the target society?
3. What conduct would make support indefensible?

Evaluate partner forces through politics, discipline, legitimacy, and post-action governance.

partner assessment, legitimacy matrix, conduct threshold

External sponsorship can inflate confidence and weaken local legitimacy.

1. What must happen if the first step fails?
2. Which support is politically unavailable?
3. Have leaders explicitly accepted the true commitment?

Expose implicit escalation requirements before they become crisis demands.

dependency map, escalation memo, decision brief

A plan may be approved at one risk level while depending on another.

1. Who owns policy?
2. Who owns execution?
3. Who can cancel?
4. Who records dissent?

Separate policy, intelligence, paramilitary, diplomatic, and presidential responsibilities.

line-of-control chart, cancellation authority note

Blurred lanes create shared action but orphaned responsibility.

1. What outcome is being promised?
2. Can the means plausibly produce it?
3. What adversary response is being assumed away?

Compare the political end state with the actual scale, time, legitimacy, and support available.

feasibility memo, adversary-response table

Optimistic scale estimates often survive because they flatter policy desires.

1. Which assumption must be true for success?
2. Who is empowered to say no?
3. What evidence would force redesign?

Build an internal kill-team to test popular support, deniability, partner viability, and escalation needs.

assumption register, red-team report

Red teams fail when their objections are heard as disloyalty.

1. What is the President willing to do publicly?
2. What support will be withheld?
3. Does the plan still work under those limits?

Turn ambiguous political appetite into explicit permissions, prohibitions, and abort criteria.

presidential option memo, risk-acceptance record

Staff can mistake access to the President for clarity from the President.

1. Which support element is mission-critical?
2. Is it politically approved?
3. What is the consequence if it is cancelled?

Mark critical dependencies in red and force a specific go/no-go decision.

critical-dependency sheet, cancellation scenario

A dependency can be minimized until cancellation makes it fatal.

1. Who would rise, where, and why?
2. What repression capacity exists?
3. What evidence is not produced by exiles or wishful thinking?

Treat insurrection forecasts as hypotheses requiring harsh validation.

mobilization evidence table, confidence caveat

Ideological confidence can turn diaspora hopes into operational assumptions.

1. What failed in assumptions, authority, execution, or communication?
2. What did leaders know when?
3. Which lesson changes future structure?

Submit failure to inspectors, commissions, archives, and internal reform.

postmortem memo, lesson register, reform plan

Postmortems can become blame management if access to records is selective.

1. Which programs compete for money, attention, and presidential tolerance?
2. Which risk is correlated across programs?
3. Which project must be slowed or stopped?

Use portfolio review rather than managing each secret project as an isolated special case.

portfolio dashboard, risk heat map

The larger the portfolio, the easier it is for weak signals to disappear.

1. What decision is required now?
2. Which caveat is load-bearing?
3. What must not be simplified away?

Compress technical and covert complexity into options, risks, and explicit assumptions.

executive brief, option table, caveat line

Compression can drift into salesmanship.

1. Where is trust justified by performance?
2. What independent test is still required?
3. Who can challenge the contractor without destroying speed?

Pair extraordinary contractor access with milestone tests and outside review.

contract review, test gate, variance report

Heroic contractor narratives can hide institutional dependence.

1. Who owns the result?
2. What artifact proves progress?
3. Where does ownership end and oversight begin?

Assign responsibility to a compact team with clear deliverables and escalation paths.

ownership charter, handoff memo

Single-owner speed can marginalize dissent and succession planning.

1. What record will survive?
2. Which dissent is documented?
3. Could an outsider reconstruct authority and logic later?

Design records that preserve legality, reasoning, and accountability without exposing unnecessary sensitive details.

decision log, archive packet, declassification note

Over-secrecy can make later accountability depend on memory and memoir.

1. Is the analyst selling an operation?
2. Is the operator shaping the estimate?
3. Where is independent dissent preserved?

Protect analytic estimates from operational and policy pressure.

firewall note, dissent annex, estimate caveat

Bissell’s strengths as a doer also show the danger of merged roles.

1. What public value is lost by secrecy?
2. What oversight compensates?
3. What happens if the secret becomes public later?

Attach legitimacy, alliance, congressional, and historical costs to secret programs.

secrecy ledger, oversight memo

Secrecy can delay accountability until damage is already institutional.

1. Who will experience the action as intervention?
2. What precedent is created?
3. Which resentment or instability might outlive success?

Run a pre-mortem that treats future hostility and legitimacy loss as part of the decision.

blowback premortem, legitimacy ledger

Blowback notes do not matter if leaders treat them as ritual.

1. What is known firsthand?
2. What is inference?
3. What confidence is required for this kind of action?

Prevent weak evidence from becoming strong action through repetition.

confidence table, evidence tag, warning note

Confidence language can be ignored if the narrative is compelling.

1. Who held the decision authority?
2. What boundary failed?
3. What public action restores institutional credibility?

Treat resignation, reorganization, and public record as part of institutional repair.

responsibility memo, succession plan, public-accountability record

Symbolic exits do not substitute for structural reform.