Ask Consultants How Research Criteria Become a Recommendation

Consultant research teams do not evaluate managers the way managers describe themselves. They have their own methods, timelines, and documentation standards, and a productive relationship starts by understanding those standards instead of leading with your own narrative. When you sit down with a consultant, your job is to find out what questions the research team is actually trying to answer, how a preliminary screen differs from a full recommendation in their process, and what evidence they treat as current instead of stale.

Why This Conversation Goes Wrong

Most consultant relations professionals walk into these meetings ready to talk about their manager's strengths. That instinct is understandable, and it also gets things backward. If you open with your pitch, you teach the consultant nothing about how their own process works, and you waste an opportunity that is hard to get back. Research teams move on their own calendar. A consultant might revisit a category once a year, sometimes less. If you fill that window with talking points instead of questions, you leave with a warmer relationship and no better sense of what actually moves a manager from a screen to a recommendation.

There is a second problem that costs firms just as much. Even relationship professionals who do ask questions tend to accept vague answers. A consultant says the team wants managers with a clear edge, or that they look for organizational stability, and the conversation moves on before anyone defines the term. Vague language sounds like information but is not. It cannot be verified, it cannot be assigned to a source inside your firm, and it cannot be tracked from one meeting to the next to see whether the manager closed the gap.

How To Prepare Before You Ask

Before the meeting, separate what you know from what you assume. Pull the last few notes on this consultant relationship and check whether earlier answers about criteria were ever confirmed or just recorded as heard. If your notes contain phrases such as strong process or good communication with no detail behind them, treat those as open questions rather than settled facts.

Decide what you actually need from this specific meeting. You are not trying to extract the consultant's entire methodology in one sitting. Pick two or three areas, such as organizational stability, capacity, or how the team documents repeatability of the investment process, and plan to press on those until the language is specific enough to act on. Also decide who inside your firm owns each likely topic, so that when the consultant names a concern you already know whether it belongs to the portfolio team, operations, or compliance.

Finally, prepare to hear something you were not hoping for. Some research teams end a review with a decline rather than a request for more material, and that outcome deserves its own response rather than a scramble. If you have not already read our piece on how to Respond Constructively When a Consultant Declines Further Review, read it before this meeting, not after one goes badly.

What To Say When You Ask

Open with a question that puts the consultant's process at the center, not your manager. Something like, when your researchers revisit this category, what do they need to see before they commit time to a deeper review. That question signals you are asking about their standards, not fishing for a compliment.

Here is how that exchange might run. You ask the consultant, "When your team looks again at this space, what makes a manager worth a deeper review instead of a quick pass?" The consultant answers, "We want to see managers with a real edge in how they generate ideas." That sounds concrete, but it is not finished yet, so you do not let it sit. You ask, "What would count as evidence of an edge? The research inputs, the decision discipline, the way ideas get implemented, or something else?" The consultant clarifies, "We are really comparing how durable the process is, and we want to see how decisions get challenged and documented over time, not just a description of the philosophy."

That second answer is worth far more than the first. Now you can go back to your firm and ask specific people for specific material. You can tell the portfolio team that the research group wants documented examples of how ideas are challenged and how decisions get reviewed, not a restated summary of the strategy. You can also ask a scope question in the same meeting, whether this expectation applies to the whole firm or only to this particular strategy. Scope matters because a manager can meet a firm level standard while missing a strategy specific one, and confusing the two wastes everyone's time later.

Mistakes That Undermine The Conversation

The most common mistake is writing down the consultant's exact phrase and treating it as if it were already actionable. Clear edge is not a data point. Neither is strong culture or good communication. If a phrase like that ends up in your notes without a follow up question attached, you have recorded a mood, not a criterion.

A second mistake is assuming that because a consultant named several factors, they carry equal weight. They rarely do. Ask directly whether one item matters more than the others for this category, and let the consultant rank them rather than guessing based on which one they mentioned first.

A third mistake is answering on the spot when you are not sure of the facts. If a consultant asks whether your firm's process includes a specific control or a specific review step, and you are not certain, say so plainly and commit to confirming it. A wrong answer given quickly costs more credibility than an honest pause. Once you are back at your desk, write the research language down exactly as the consultant said it, match every item to a verified owner inside your firm, and flag anything you could not confirm rather than filling the gap with a guess. Our post on how to Write Follow Up Notes That Help a Consultant Researcher covers this step in more detail.

How To Practice And Score It

This conversation is easy to describe and hard to run well under pressure, which is why it benefits from rehearsal before it happens with a real consultant. A manager coaching a consultant relations team can build a short drill around it. Give the rep a vague statement, such as we like managers who show discipline, and ask them to respond with a neutral clarifying question rather than an assumption. Then have them summarize the consultant's answer back in one sentence, and check whether that summary adds any favorable interpretation the consultant did not actually offer.

Score the rep on three things. First, did they ask an open question before offering any pitch of their own. Second, did they press a vague answer at least once until it became specific enough to assign to an owner. Third, did their closing summary match what the consultant said, with no added spin. A rep who scores well on all three walks out of a real meeting with notes the rest of the firm can act on, instead of a page of adjectives.

This kind of rehearsal is what Asset Management practice conversations on DealSpeak are built for. You can run the exchange above against an AI counterpart, get scored on exactly these three points, and repeat it until asking the sharper question becomes automatic.

Treat every consultant conversation as an audit of your own listening, not just a transfer of information about your manager. The firms that get invited back are the ones whose relationship team can repeat, in the consultant's own words, exactly what the research process requires.