Prioritization without people scoring

Once the relationship map is drawn, time becomes the constraint. You cannot open every route today, and you do not need to. Priority is a decision about work sequence, not a ranking of people’s worth. Tie every route to an unanswered question and a specific decision. If a published paper answers the question, read it first. If an authorized colleague knows the method, ask that colleague before taking an outsider’s time. If a gap remains that calls for someone’s particular experience, outreach becomes reasonable. A good sequence reduces burden on others while making the question more precise.

Use a four-field descriptive matrix: relevance of experience to the gap, strength of the contact context, burden of the request on the recipient, and disclosure boundary. Do not convert these fields into an automatic total score. A highly relevant route may require information you cannot disclose; postpone it or redesign the question. An easy direct contact may be unable to answer; ease does not make that route first. Record evidence in every field. “Published a description of the comparison method” supports relevance. A large follower count does not prove experience with your case. “We worked on a defined project” is a known contact context. “We have a mutual acquaintance” calls for the intermediary’s permission before that name can be used.

Separate “now,” “after a check” and “do not contact.” Now is for a clear question and a context that permits a small request. After a check applies when permission is missing, public material must first be read or disclosure authority is uncertain. Do not contact applies when the need is resolved, relevance cannot be explained, the person has declined or the request would exceed your role. Postponement is not a failure. It may produce a better question or show that contact is unnecessary.

Do not treat a predicted reply as a fact. A previous helpful response may guide your choice of channel, but it guarantees no new response. Senior job title also does not establish authority to speak on this precise subject. Write a sequence such as “Start with the published criterion, then ask the coordinator how she applied it if uncertainty remains.” That can be checked. “Approach the most influential person” identifies neither a gap nor an output.

Two criteria may conflict. A researcher may have ideal subject experience but no connection to you; a colleague may know the setting but lack the researcher’s expertise. First use the colleague to clarify terms without assigning that colleague the researcher’s authority. Then ask the researcher a focused question if needed. If a deadline is tomorrow and there is no respectful introduction route, documenting uncertainty and recommending a later check may be better than urgent mass messaging. Time is a stated constraint, not a reason to bypass permission or confidentiality.

Challenge the matrix with a changed fact. If the public source becomes sufficient, is outreach still needed? If your sequence never changes when the gap changes, you may be ranking people by impression rather than by the task. If the data owner permits a redacted summary instead of the original list, does the disclosure boundary and feasible route change? Record the new fact before changing the decision. Such checks keep the plan responsive to evidence rather than to its author’s first guess.

The final artifact is one page: each route’s question, evidence of relevance, constraint, “now/after check/do not contact” decision and next action. Revise it after the first source or reply. It is not a performance board for counting invitations or rating people. Its test is whether it helps the team gain suitable knowledge or collaboration with the least necessary disclosure and burden, while making stopping reasons as visible as reasons to contact.

“Request burden” needs a concrete estimate. A yes-or-no question may require the recipient to inspect an unfamiliar file, making it a large ask; a question about a decision explained in a public talk may take minutes. Judge the work demanded, not message length alone. If an answer requires formal review, use the institution’s route. For apparently equal routes, ask which answer would change the team’s next step. A route repeating published information comes after reading; a route clarifying a local difference may then take priority. Give every route a stopping rule: a sufficient answer closes the gap, a decline ends contact, and a disclosure issue goes to its owner. Seek missing decision perspectives without asking one individual to represent an entire group.