Does Your Firm Need Biometric Translations…or Other Translations?

When I talk about translation, I’m usually not talking about language translation. Trust me, my French, German, or Spanish isn’t good enough for that type of translation.

But I excel at other types of translation that help my client businesses run more smoothly.

Biometric translations

Bredemarket knows how different biometric systems “talk” differently…and how they can talk to each other.

I’m often talking about translating between different NIST-based biometric interchange standards. Because the FBI system doesn’t exchange biometric data in the same way as the DoD system, or the DHS system, or the RCMP system, or others.

As I stated in July 2025:

“Luckily all the different standards have some basic similarities, but if you have a mobile biometric device that must submit to DOJ and DoD and DHS, you need to switch to the proper profile for each submission….

“But I’ve overcome this frustration over 30 years of immersing myself in all things biometric-translation related.”

And I may immerse myself some more. One of Bredemarket’s clients distributes software that submits to one system. What if that software has to submit to two systems? Or 20? Or 200?

But I deal with other translations too.

Stakeholder translations

Bredemarket knows the players in an identity, biometric, or technology system…and how they can talk to each other.

Any complex project will have a variety of stakeholders, each of whom speak their own “language.” My job at Bredemarket often entails allowing these people to communicate with each other.

To illustrate this, let me share a simplified example of something I shared before.

• Engineers develop a biometric application.

• The application has to conform to forensic standards.

• The application is used by people in the field who may not know engineering or forensics, but who know conditions in the field better than engineers or forensic experts.

OK. Now write the user guide so that the field worker understands what the engineers created and captures what the forensic folks need.

This is where the inexperienced writer suffers from a failure of courage.

Let me tell you a little secret.

Most engineers can’t write the user manual. They’ll go into great detail about how the SDK references this particular process, but they can’t tell the field worker how to capture a fingerprint from a dead body that has been in the woods after a week of rain.

How has Bredemarket approached similar projects?

• By asking the right questions of all the stakeholders—not just the three I mentioned here, but ALL of them including Ontario, California mayor Paul Leon (or whoever the political honcho is on YOUR project).

• Then writing the draft. I won’t go into the “draft 0.5 – draft 1” mechanics here, since I’ve covered them elsewhere.

• Then collaborating on the reviews, giving the draft to the stakeholders and insisting on getting timely feedback.

• Then finalizing a document that allows the field worker to use the product in line with engineering and forensic advice (or advice from whoever) that the field worker understands.

I’ve performed this task—all the cool kids call this “cross-functional collaboration”—numerous times, working with everyone from sales to legal to a client’s own suppliers and end customers.

What do you need translated?

You know that your multi-department project won’t take off until someone glues the pieces together…and ensures that everyone is talking to each other.

At this moment Bredemarket is working on multiple client projects and delivering project management, strategy, writing, and other services.

This often involves translating between the different stakeholders. The outside business head doesn’t care what technical standards my client supports…but you can bet the outside technical head does.

Does your identity, biometric, or technology firm have a product marketing project that requires a lot of people to work together?

Let’s talk (for free) about how I can help. Set up a meeting below.