When Bureaucrats Cooperate…and When They Don’t

If you’ve read a few hundred job descriptions, one phrase that you’ll often see is “cross-functional collaboration.” The theory is that the employee (for example, a senior product marketing manager) will seamlessly work with marketing, product, R&D, customer success, sales, finance, legal, and everyone else, all working together for the good of the company.

But the world usually doesn’t work like that. YOUR department is great. The other departments are the bozos.

Google Gemini.

There’s actually a benefit to this when you look at government agencies. If you believe that “the government that governs least” is preferable to Big Brother, then the fact that multiple agencies DON’T gang up against you is a good thing. You don’t want to be chased by the FBI and the CIA and the BBC and B.B. King and Doris Day. And Matt Busby.

But there are times when government agencies work together, usually when facing a common threat. Sometimes this is good…and sometimes it isn’t. Let’s look at two examples and see where they fall in the spectrum.

The Central Intelligence Agency and the Federal Bureau of Investigation in 1972

Normally bureaucrats are loyal to their agency, to the detriment of other agencies. This is especially true when the agencies are de facto competitors.

In theory, and certainly in the 1970s, the Central Intelligence Agency (CIA) and the Federal Bureau of Investigation (FBI) have completely separate spheres of operation. But on the highest level they perform the same function: catch bad people. And each agency certainly wants to take the credit when a bad person is caught. Conversely, if one of the agencies has a bad person, the other one usually works to expose it.

Usually.

A few of you are old enough to remember a third-rate burglary in Washington, DC in 1972. The burglary took place at a political party office in some hotel or another. We now know with the benefit of hindsight that the FBI-CIA rivalry worked. Bob Woodward learned a few days after the break-in that two of the alleged burglars were connected to E. Howard Hunt, a former CIA operative. Who told Woodward?

“Woodward, we now know, had been tipped off by Mark Felt, the deputy director of the FBI. The Bureau had itself become involved in the investigation of a mere burglary because once the police found wiretapping equipment, the investigation fell under its remit.”

Google Gemini.

This is how it should work. Although the mere fact that Hunt knew Bernard Barker and Eugenio Martinez was not a crime, the FBI was certainly bound to investigate the matter.

Until it wasn’t.

“Richard Nixon and senior White House personnel including Chief-of-Staff Bob Haldeman and domestic policy tsar John Ehrlichman devised a strategy to block the investigation. This began to unfold as early as June 23, a mere three days after the break-in. That day, Haldeman proposed to Nixon to “have [Vernon] Walters [deputy director of the CIA] call Pat Gray [director of the FBI] and just say ‘stay the h*ll out of this’ on grounds of ‘national interest.’”

This recorded conversation would become very important two years later, but back in 1972 very few people knew about it. And very few people knew that Gray “destroyed secret documents removed from Howard Hunt’s safe.”

Think about it. If Richard Nixon hadn’t recorded his own conversations, we may have never learned that the CIA partially neutralized an FBI investigation.

But other instances of cross-functional collaboration come to light in other ways.

Immigration and Customs Enforcement and the Transportation Security Administration before 2026

The FBI-CIA episode of 1972 was an aberration. Normally agencies don’t cooperate, even when massive amounts of effort are performed to make them work together.

One prime example was the creation of the Department of Homeland Security (DHS) in 2002-2003. Because it was believed that 9/11 happened because relevant agencies were scattered all over the government, Congress and the President performed a massive reorganization. This affected the Departments of Agriculture, Energy, Health and Human Services, Justice, Transportation, and Treasury.

For our discussion:

  • The Department of Justice lost the Immigration and Naturalization Service (INS), which was broken up into three separate agencies within DHS. One of these is Immigration and Customs Enforcement, or ICE. Perhaps you’ve heard of it.
  • The relatively new Transportation Security Administration (TSA) was moved from the Department of Transportation to DHS.

The theory, of course, is that once all these agencies were under the DHS umbrella, they would magically work together to stop the evil terrorists. However, each of the component agencies had vastly different missions. Here is the mission of the TSA:

“Protect the nation’s transportation systems to ensure freedom of movement for people and commerce.”

Well, “freedom of movement” is not the primary part of ICE’s mission:

“Protect America through criminal investigations and enforcing immigration laws to preserve national security and public safety.”

While these missions are not mutually exclusive, the difference in emphasis is apparent. And the agencies competed.

Some of you may remember air marshals. After 9/11, some airline flight passengers were actually air marshals, but the passengers (and any terrorists) didn’t know which flights had air marshals or who they were.

Google Gemini.

The Federal Air Marshal Service (FAMS) was part of the Transportation Security Administration.

Until it wasn’t.

“Homeland Security Secretary Tom Ridge announced [in September 2003] that the federal air marshals program will move from the Transportation Security Administration to the Bureau of Immigration and Customs Enforcement (ICE).”

The idea was to concentrate all enforcement operations in one agency, to protect FAMS from uncertain TSA funding, and to allow ICE agents to be cross-trained as air marshals. But this didn’t happen, so two years later FAMS moved from ICE back to TSA.

And both agencies went on their merry little ways.

Immigration and Customs Enforcement and the Transportation Security Administration in 2026

Let’s look at a recent Biometric Update article.

“When Transportation Security Administration (TSA) Acting Director Ha Nguyen McNeill was pressed [by the House Committee on Homeland Security] on reports that ICE is using domestic flight passenger information to support deportation operations, she did not deny cooperation. Instead, she defended it as legitimate intra-departmental coordination and framed it as part of DHS’s overall mission set.

“In response to lawmakers’ questions, McNeill said TSA assistance to ICE is ‘absolutely within our authorities’ when it involves sharing passenger information for immigration enforcement operations.”

McNeill effectively said that TSA doesn’t dump its data on ICE, but responds to individual ICE inquiries.

Google Gemini.

Civil libertarians argue that this is mission creep, not the original intent.

“Airport travel…becomes a choke point for detentions – no longer just transportation, but a compliance checkpoint for civil enforcement, re-engineering mobility into an enforcement tool.”

And one more thing…

But I took special interest in McNeill’s contradictory statements that TSA is enforcing REAL ID while simultaneously allowing ConfirmID for those who don’t have a REAL ID.

In the future, it will be interesting to see how inter-agency barriers break down…and why.

What is the Difference Between Short and Medium Content?

Length. 2,400 words give or take.

And cost. For now, $1,500.

Bredemarket: Services, Process, and Pricing.

And, of course, development of the themes. A quick punch, or more elaborate?

Whatever length of content your story needs, Bredemarket can provide it.

Content for tech marketers.

To All the People Who Wanted to Defund the Police

I discussed the whole “defund the police” movement years ago, and now in 2026 we are still depending upon the police to protect us.

According to KARE, here is what happened when the police investigated the death of Alex Pretti…or tried to do so.

“Despite having a signed warrant from a judge, the Minnesota Bureau of Criminal Apprehension (BCA) was denied access to the scene where a man was fatally shot by federal agents Saturday morning in south Minneapolis, according to the BCA.

“Minnesota BCA Superintendent Drew Evans said the department was initially turned away at the scene by the Department of Homeland Security (DHS), so the BCA obtained a warrant from an independent judge. Evans said the judge agreed that the BCA had probable cause to investigate the scene, but DHS officials wouldn’t allow the BCA access to the scene.”

And I might as well say this also…I don’t believe in abolishing ICE either.

Could 1926 Images Support Facial Recognition?

We commonly believe that modern people enjoy an abundance of data that historical people did not have. While this is often true, sometimes it isn’t.

Let’s look at the images we use in facial recognition.

ISO/IEC 19794-5 (Face image data) recommends a minimum inter-eye distance of 90 pixels.

But imagine for the moment that facial recognition existed 100 years ago. Could century-old film cameras achieve the necessary resolution to process faces on adding machines or whatever?

The answer is yes. Easily.

Google Gemini.

Back in the Roaring ‘20s, photographs of course were not digital images, but were captured and stored on film. During the 1920s a new film standard, 35mm film, was starting to emerge. And if you translate the “grains” in film to modern pixels, your facial image resolution is more than sufficient.

Here is what FilmFix says:

“Thirty-five-millimeter film has a digital resolution equivalent to approximately 5.6K — a digital image size of about 5,600 × 3,620 pixels.”

Yeah, that will work—considering that the Google Gemini image illustrating this post was generated at only 1,024 x 1,024 pixels.

Sometimes You Only Need One

A tech journalist, writing on their personal social channels, noted that they recently bought a laptop bag luggage strap…and was immediately added to the company’s mailing list.

Because when you buy one laptop bag luggage strap, you obviously need seven more.

Google Gemini.

But it’s really bad when you buy a refrigerator and the seller thinks you want more of THOSE.

Do You Address Business Audiences, or Technical Audiences? Yes.

As I’ve said before, there may be many different stakeholders for a particular purchase opportunity.

For the purpose of this post I’m going to dramatically simplify the process by saying there are only two stakeholders for any RFP and any proposal responding to said RFP: “business” people, and “technical” people.

Google Gemini.
  • The business people are concerned about the why of the purchase. What pressing need is prompting the business (or government agency) to purchase the product or service? Do the alternatives meet the business need?
  • The technical people are concerned about the how of the purchase. Knowing the need, can the alternatives actually do what they say they can do?

Returning to my oft-repeated example of an automated biometric identification system purchase by the city of Ontario, California, let’s look at what the business and technical people want:

  • The business people want compliance with purchasing regulations, and superior performance that keeps citizens off the mayor’s back. (As of January 2026, still Paul Leon.)
  • The technical people want accurate processing of biometric evidence, proper interfaces to other ABIS systems, implementation of privacy protections, FBI certifications, iBeta or other conformance statements, and all sorts of other…um…minutiae.

So both parties are reading your proposal or other document, looking for these points.

So who is your “target audience” for your proposal?

Both of them.

Whether you’re writing a proposal or a data sheet, make sure that your document addresses the needs of both parties, and that both parties can easily find the information they’re seeking.

If I may take the liberty of stereotyping business and technical users, and if the document in question is a single sheet with printing on front and back, one suggestion is to put the business benefits on the front of the document with pretty pictures that resonate with the readers, and the technical benefits on the back of the document where engineers are accustomed to read the fine print specs.

Google Gemini. It took multiple tries to get generative AI to spell “innovate” correctly.

Or something.

But if both business and technical subject matter experts are involved in the purchase decision, cater to both. You wouldn’t want to write a document solely for the techies when the true decision maker is a person who doesn’t know NFIQ from OFIQ.