apply-solicited-advice-discipline

name	apply-solicited-advice-discipline
description	Use when someone asks you a specific question, or when you're tempted to offer advice, opinion, or evaluation nobody asked for — answer exactly the scope of what was asked and no more, and don't volunteer advice or judgment unprompted, because unsolicited or over-scoped advice is systematically discounted and can generate resentment, regardless of its quality.
source	荀子 (Xunzi), 勸學篇 (Encouraging Learning), ~3rd century BC — 故不問而告謂之傲，問一而告二謂之囋 (to tell without being asked is arrogance; to answer more than what was asked is verbosity); Bonaccio & Dalal, "Advice Taking and Decision-Making: An Integrative Literature Review", Organizational Behavior and Human Decision Processes (2006); Yaniv, "Receiving Other People's Advice: Influence and Benefit", Organizational Behavior and Human Decision Processes (2004); International Coaching Federation core competencies
tags	["communication","mentoring","feedback","advice-giving","leadership","discretion"]
related	["apply-non-transactional-giving","run-motivational-interviewing","apply-visible-note-taking-elicitation"]

Apply Solicited Advice Discipline

Answer exactly the scope of what was asked, and don't volunteer advice, opinion, or evaluation nobody requested — because unsolicited or over-scoped advice is systematically discounted by the recipient and can generate resentment, independent of how good the advice actually is.

Why This Is Best Practice

荀子 (Xunzi), 勸學篇 (Encouraging Learning, ~3rd century BC):

故不問而告謂之傲，問一而告二謂之囋。

"To tell someone something without being asked is called arrogance; to answer more than what was asked is called being garrulous." The principle names two specific, distinct failure modes in advice-giving: volunteering advice or judgment that wasn't requested at all, and — even when a question genuinely was asked — answering with more scope than the question called for. Both are treated as overreach, regardless of whether the content of the advice is correct or valuable.

Why best: This is not a claim that advice is unwelcome in general — it is a specific, mechanism-level claim about scope and consent: advice delivered outside the scope the recipient actually asked for is processed by the recipient as a status move (the advisor asserting they know better, unprompted) rather than as pure information, which triggers discounting or resistance independent of the advice's actual quality. Advice delivered within the exact scope requested is processed as a direct answer to a request, which the recipient weights far more heavily in their own decision-making. The correction is procedural — match the scope of the answer to the scope of the question, and ask permission before expanding beyond it — not a judgment about whether the advice itself is good.

Bonaccio & Dalal (2006): An integrative review of advice-taking and decision-making research across organizational and clinical contexts, finding a consistent pattern of "advice discounting" — recipients systematically weight received advice less heavily than the advice's objective quality would justify, and this discounting is measurably worse for advice that was not requested by the recipient, compared to advice given in direct response to an explicit request for it.

Yaniv (2004): Experimental research on advice utilization in judgment and decision-making tasks found that when subjects actively solicited another person's estimate or opinion before making their own judgment, they incorporated that outside input into their final decision substantially more than when the same input was volunteered without being requested — establishing that the act of requesting advice itself changes how much weight the recipient subsequently gives it, independent of the advice's content.

International Coaching Federation core competencies: The ICF's professional coaching competency framework, the recognized global standard for coaching certification, explicitly requires practitioners to ask permission before offering direct advice, feedback, or observations rather than volunteering them unprompted — codifying "ask before telling" as a formal professional standard rather than an informal courtesy, specifically because unsolicited advice measurably degrades the coaching relationship and the client's uptake of the input.

Adopted by: The International Coaching Federation's competency framework, the recognized global standard for professional coach certification; motivational interviewing's "ask-offer-ask" structure (used in clinical, coaching, and organizational behavior-change practice) formalizes requesting permission before offering direct advice as a core technique. Impact: Bonaccio & Dalal's review found advice discounting — recipients underweighting advice relative to its objective quality — is a robust, replicated pattern across decision-making research, worsened specifically when the advice was unsolicited; Yaniv's experimental work found subjects incorporated the same outside input substantially more into their own judgment when they had actively requested it beforehand, compared to when it was volunteered unprompted, isolating the act of solicitation itself as a driver of how much weight advice receives.

Steps

1. Before offering advice, opinion, or evaluation, check whether it was actually requested. If not, and it isn't required by a standing role obligation (see When NOT to Use), either withhold it or explicitly ask permission before delivering it, rather than volunteering it directly.

2. When a specific question is asked, identify precisely the scope of what was asked before answering. A question about one tactical decision is not an invitation to a broader review of the person's overall approach, career, or project, however related that broader territory might feel.

3. Answer within that identified scope, and resist the urge to expand into adjacent, unrequested territory. Deliver the direct answer to the specific question first, completely, before considering whether anything else is worth raising.

4. If you believe genuinely important context exists beyond the asked scope, request permission to expand rather than silently including it. A short, explicit check — "there's something related I think is worth mentioning, want me to go into it?" — respects the asymmetry Xunzi's principle and the advice-discounting research both identify, and lets the recipient consciously opt into the larger scope.

5. Treat a large gap between the length/scope of a question and the length/scope of your answer as a signal to trim before delivering it. If a request for a one-line assessment is about to produce several paragraphs of unsolicited analysis, that gap itself is the flag that the response has drifted past the requested scope.

6. When you are the one asking a question, explicitly signal the scope of answer you want. State upfront whether you want a quick take, a full analysis, or something in between — this reduces the ambiguity that leads the other person to guess wrong about what scope is actually welcome.

Rules

• Distinguish sharing a useful fact, resource, or introduction unprompted — a generous act generally welcomed and covered by apply-non-transactional-giving — from offering advice, opinion, or evaluation about a person's choices or work unprompted, which is the specific category this discipline addresses; the two operate under different norms.
• Match the scope of an answer to the scope of the question asked; expanding beyond it without being asked reads as overreach regardless of the advice's actual quality.
• Request explicit permission before expanding into adjacent, unrequested territory, rather than silently including it in the answer.
• When asking for advice yourself, state the scope of answer you want upfront, since the asymmetry runs both ways and a vague request invites over-answering.

Examples

Mentoring: A junior colleague asks a mentor a specific tactical question about how to phrase one email. The mentor answers exactly that question, then separately says, "there's a broader pattern in how you're approaching stakeholder communication that might be worth discussing sometime — want to go into that now, or focus on just this email for today?" rather than immediately launching into an unsolicited lecture on communication strategy.

Consulting: A client asks a consultant for a one-line read on whether a specific metric looks concerning. The consultant gives the direct one-line answer first, then separately flags, "I also noticed something else in the underlying data that might be worth a look — happy to go into it if useful," rather than folding an unrequested secondary analysis directly into the answer to the original question.

Reversed direction: Before a meeting with a senior leader, a team member states upfront, "I just want a quick gut check on this one decision, not a full review of the project" — the leader calibrates their answer accordingly, giving a brief take on the specific decision rather than an extended, unsolicited critique of the broader project the team member didn't ask about.

Common Mistakes

• Answering a narrow, specific question with a broad, unsolicited review of everything adjacent to it. This is the exact pattern Xunzi's principle names as garrulous overreach, regardless of whether the additional content is individually valuable.
• Confusing this discipline with withholding genuinely useful information, resources, or introductions. Sharing a useful fact or connection unprompted is a different, generally welcomed act — see apply-non-transactional-giving — distinct from volunteering advice or judgment about the person themselves.
• Never requesting permission before expanding into adjacent, unrequested territory, even when the additional context feels important. A short permission check is nearly costless and resolves the asymmetry directly, rather than guessing at what scope is welcome.
• As the person asking a question, failing to signal the desired scope of the answer, then reacting negatively when the response over-delivers relative to what was actually wanted. The asymmetry runs both ways — an unscoped request invites an unscoped answer.

When NOT to Use

• When sharing a fact, resource, introduction, or concrete piece of help that isn't advice, opinion, or evaluation about the person themselves — see apply-non-transactional-giving for the different norm governing that category.
• In a formal reporting, auditing, safety, or compliance role where proactively surfacing risks or issues regardless of whether anyone asked is the explicit responsibility of the role — a safety inspector's or auditor's obligation to report a genuine hazard overrides this discipline.
• When an existing, explicit mandate already covers broad, proactive advice-giving (a hired advisor's engagement scope, a coach's agreed-upon broad remit) — the discipline specifically concerns advice given outside of an existing agreed mandate, not advice delivered within one that has already been consented to.