Plan a Discussion About Control Materials Around the Customer’s Study Design

A customer asks you which control material will prove their assay works. The question sounds simple, but underneath it sits a much bigger question about whether their experiment will succeed, and that second question is not yours to answer. If you are a field application scientist, you have fielded some version of this before, and how you handle it decides whether you come across as a scientific partner or as someone who overstepped. This is a conversation worth rehearsing before it happens live, whether that rehearsal happens with a colleague or through Biotechnology practice conversations.

Why This Conversation Goes Sideways

Most field application scientists want to be useful, and a researcher asking for reassurance triggers that instinct hard. The problem is that "will this control prove our assay is working" is not really a materials question. It is a question about study design, statistical power, and interpretation of results, and none of those belong to you. They belong to the principal investigator or the study owner.

When you answer as if you are confirming the science, you have quietly stepped into a role you do not hold. If the study later produces a messy result, your words get remembered and sometimes repeated back to you. The opposite mistake is just as damaging. If you retreat into a stiff "I can't comment on that," you look unhelpful and the researcher stops trusting you as a resource at all. The skill here is not choosing between helpful and cautious. It is knowing exactly which parts of the question you can answer with documented fact and which parts belong to someone else.

Get Your Facts Straight Before You Get On The Call

Walk into this conversation already knowing the boundaries of what you can speak to. Before you talk with the customer, do three things.

1. Pull the approved specifications for the control material, including documented storage conditions, preparation steps, and compatibility with the platform the customer is using.
2. Check who the customer's study owner is, if you already know it, and note any local review process that governs the work, such as an institutional review board or a quality assurance sign off.
3. Write down two or three questions that will surface the study design without putting you in the position of evaluating it, things like what the sample groups look like and who will interpret the resulting data.

This preparation matters more at the start of a relationship, when you are still learning how a lab operates. If you have not yet mapped how a customer's samples move from intake through analysis, that groundwork changes how you read a conversation like this one. The article on how to Map Sample Intake Before Proposing a Platform Evaluation covers how to gather that context early, so a question about controls does not catch you flat footed later.

What To Say When The Question Lands

Here is roughly how this plays out with a researcher who wants certainty before the data exists.

Omar, a postdoctoral researcher at a fictional lab, opens with the question you have heard before. "Can you tell us which control will prove our assay is working?"

You do not answer that directly, because you cannot. Instead you separate the material question from the study question. "I can walk you through the approved material information right now. Before I do, tell me about your planned study design. How many sample groups are you running, and who is going to interpret the results once you have them?"

Omar explains that this is a pilot run with several sample groups, and that his principal investigator will make the final call on what the data means. That single detail tells you exactly where the line sits.

"Good, that helps. Here is what I can confirm from our approved documentation, the storage conditions, the preparation steps, and how this control performs against the specification we have on file. Whether that performance answers the question your pilot is asking is something your principal investigator needs to weigh in on, since they know the full study design. Let's get the approved information in front of them so they have what they need to make that call."

Notice what happened. You gave Omar something concrete and useful, the documented material facts, and you handed the interpretation question to the person who actually owns it. You did not dodge the question. You answered the part that was yours.

Mistakes That Cost You Credibility

A few habits turn this conversation from a strength into a liability.

1. Answering the interpretation question directly, even with hedging language like "this should work fine for what you're describing." That sentence sounds like a scientific opinion no matter how you qualify it.
2. Skipping the clarifying questions and jumping straight to documentation, which leaves you guessing at what the customer actually needs and misses the chance to learn their study design.
3. Failing to name who owns the next decision. If you leave the call without identifying the principal investigator or study owner, the researcher walks away without a clear next step.
4. Treating every question as either fully yours to answer or fully off limits. Most questions in this conversation are a mix, and your job is to split them cleanly rather than pick one extreme.
5. Leaving no written record. A verbal answer about approved specifications is easy to misremember a week later, especially once a study is underway and someone is trying to figure out what was said.

Practice The Split Until It Becomes Automatic

The skill in this conversation is drawing a line between fact and interpretation in real time, while someone is looking at you for reassurance. That is hard to do well the first time you try it live, so practice it before a real customer asks.

Have a manager or a colleague play a researcher chasing certainty from a study that is still in its early stages. Have them push, ask you to just confirm the assay will work, and see if you hold the line without sounding evasive. Practice saying something close to, "Let's look at the approved information together and make sure your study owner has what they need to make that decision." Say it out loud until it stops sounding rehearsed.

After the role play, write the follow up email you would actually send. A good one covers three things, plainly.

1. The approved sources you discussed and where the customer can find them.
2. The open questions about study design that still need an answer from their side.
3. The name of the person who will confirm the next step in the experiment.

Score the practice run on whether you actually separated fact from interpretation, whether you asked about the study before offering documentation, and whether you named an owner for the decision. Tools like DealSpeak let you run this exact scenario repeatedly and get scored on those specific behaviors, which matters because this conversation rewards precision, not general friendliness. If you already have a sense of what a strong customer relationship looks like further down the line, the piece on how to Define Core Facility Success Measures Before Setting Adoption Milestones is worth reading alongside this one, since it shows what good looks like once this kind of conversation has gone well repeatedly.

The Point To Remember

You are not the person who decides whether a study succeeds, and pretending otherwise helps no one, least of all the researcher who is relying on you. Give them the documented facts, ask the questions that surface their study design, and send the decision about interpretation to the person who owns it. Do that consistently and researchers will trust you with harder questions later, because they will know exactly what kind of answer they are getting from you.