Give a Shared Equipment Committee an Evaluation Charter

A shared equipment committee rarely arrives at its first meeting with one question. Scientific users want to know if the platform fits their workflow. The core facility manager wants to know who staffs it and on what schedule. Purchasing wants a defined process. Finance wants a number it can justify later. A research account executive who shows up ready to demonstrate a product before the committee agrees on what it is actually evaluating ends up answering five different questions with one demo, and satisfies none of them. The fix is not a better demo. It is an agreement, made early, about what the group is deciding and who owns each piece of evidence.

Why this conversation goes wrong

Committees form around a shared resource, not a shared question. Three labs might share a piece of equipment, but each lab runs different sample types, different volumes, and different downstream steps. When the account executive lets the first meeting run without structure, whoever speaks first sets the agenda. Usually that is the most vocal scientist, and the conversation narrows to that one lab's workflow. The facility manager, who actually has to staff and maintain the thing, gets pulled in as an afterthought. Purchasing finds out about the evaluation after materials are already circulating. Finance sees a recommendation with no budget context behind it.

Without a written agreement on scope, every answer you give in the meeting becomes an implied promise. Say that the platform handles a certain sample type well, and Dr. Lin's lab hears a commitment about their specific protocol, even if you were speaking generally. That gap between what you said and what the room heard shows up later as a mismatched expectation, and it lands on you.

How to prepare

Before you agree to any demonstration or send any product material, find out what decision the committee is actually trying to make. Is it selecting one platform from a shortlist. Is it deciding whether to add a second instrument alongside an existing one. Is it setting requirements it will use for a formal purchasing process. Each of these is a different evaluation with different evidence needs.

Then map the people in the room to the type of question they carry. Scientific users carry workflow and specification questions. The facility manager carries staffing, maintenance, and throughput questions. Purchasing carries process and vendor questions. Finance carries budget and total cost questions. Write these down before the meeting so you are not sorting them live while someone is talking.

If the committee sits inside a larger consortium or shared governance structure, find out who actually holds the authority to approve a purchase before you invest time gathering evidence for people who cannot say yes. The post on how to Clarify Consortium Decision Rights Before Discussing Shared Tool Terms walks through how to do that without stalling the relationship. If the platform touches shared computing or data infrastructure, also read Scope Research Computing Capacity Before a Platform Evaluationsince capacity questions tend to surface late and derail an otherwise well scoped review.

What to say

Open by asking for the decision, not the demo. In a fictional meeting, Dr. Lin says, we have three labs and we need to know if this platform is the right choice for all of us. The account executive answers, I want to help you build a fair review. Before we look at anything, can we agree on what each lab needs to see. Which sample types and handoffs should each lab describe, and who on this committee will decide whether the platform met those requirements.

The facility manager speaks up and says weekend staffing is thin, so intake timing matters more than raw throughput. The account executive responds, that is exactly the kind of detail I want written down now, not discovered after a purchase. Can we name a person from your side who owns that requirement, so I know who to bring evidence back to.

Purchasing then asks whether a demonstration counts as part of a formal evaluation record. The account executive says, good question, let us decide that today. I would rather we agree on what evidence goes into a real evaluation file before I schedule anything, so nobody has to redo this later. From there, the account executive proposes a one page charter naming the participating labs, the questions each one owns, the evidence being requested, and the date the committee will reconvene to review findings. The committee agrees to circulate the charter for sign off before any demonstration is scheduled.

Mistakes to avoid

Do not answer a specific lab's question with a general claim about the platform. If someone asks whether it handles their sample type, do not say yes in the room. Say you will confirm it against their specific protocol and bring back a written answer. A vague yes in a group setting becomes a commitment that the whole committee remembers, even when it was never accurate for every lab.

Do not let the meeting end without naming an owner for every open question. An unassigned question does not disappear. It resurfaces weeks later as a complaint that nobody addressed it, usually right before a purchase decision is due.

Do not schedule a demonstration before the committee agrees on what the demonstration needs to prove. A demo without a defined purpose turns into entertainment. People watch, form opinions based on whatever caught their attention that day, and the committee ends up right back where it started, with no shared basis for a decision.

Do not treat purchasing and finance as approvers who show up at the end. Bring them into the scoping conversation early, even briefly, so the requirements the scientists write down are ones that a real purchasing process can actually act on.

How to practice and score it

A manager reviewing this conversation should check one thing above everything else. Does every activity the account executive proposed link back to a specific committee question. If a demonstration, a site visit, or a document was proposed, someone in the room should have asked for it, and that request should trace to a named person who will judge the result.

Practice this by roleplaying the opening five minutes of a committee meeting where three or four people raise different questions at once. The account executive should categorize each question out loud, propose an owner for each one, and end the roleplay by drafting the one page charter live. Score the attempt on whether every question raised in the roleplay appears somewhere on that page. If a question got lost, that is the gap to fix before the real meeting.

DealSpeak sets up this kind of multi party scenario so you can practice sorting competing questions before you face them with a real committee. Rehearsing the charter conversation a few times builds the habit of asking for the decision before offering an answer, which is the skill that actually separates a controlled evaluation from a chaotic one.

Closing

A shared equipment committee will move faster once it agrees on what it is deciding, not slower. Write the charter first, name the owners, and let the committee ask you for a demonstration instead of walking in with one. For more scenarios like this, look through the Biotechnology practice conversations built for exactly this kind of multi stakeholder review.