26.261 - What Your Position Prevents You From Seeing

“[T]he fine art of drawing someone out, of asking questions to which you do not already know the answer.”

Edgar H. Schein, Humble Inquiry: The Gentle Art of Asking Instead of Telling (2013), p. 2. Excerpt; initial capitalization adjusted.

🪑❓🔍

Edgar H. Schein spent more than six decades at MIT studying what happens beneath the visible surface of organizations.

A social psychologist as attentive to practice as theory, he wrote about organizational culture, careers, helping relationships, leadership, and the assumptions that shape how people work together. Late in his career, he gave a memorable name to a disciplined form of curiosity: humble inquiry.

The idea was not that leaders should pretend to know nothing or surrender responsibility. It was that interdependent work makes us reliant on knowledge held by other people, including people with less formal status. Hierarchy can obstruct that knowledge precisely when it is most needed. Schein's question was therefore relational as much as informational. Can you become genuinely interested in what another person knows, especially when your position makes telling easier than asking? A question can open that possibility. It can also leave the existing distance completely intact.

The View Changes With the Chair

Everyone in the meeting could see the problem except the person asking whether there was one.

At least, that is how the moment looked afterward. During the meeting itself, the evidence was less dramatic. An operations director was presenting a new customer-support intake process. The current system produced duplicate requests, inconsistent records, and too much manual sorting. The revised form promised a cleaner queue. Before a customer could open a case, the form would require the device's serial number.

The requirement looked sensible on the presentation slide. It would connect each request to the correct product, warranty, and service history. The project team had worked for weeks. The launch date had been announced. The director thanked everyone who had helped, reviewed the remaining tasks, and arrived at the final slide.

“Any concerns?”

No one answered.

The silence allowed the meeting to end on time. It also appeared to confirm that the process was ready.

Later that afternoon, a frontline coordinator asked for a private conversation. Customers often contacted support because an installed device had stopped displaying information, the coordinator explained. On some models, the printed serial number sat on the back of the housing, where it could not be seen without removing the unit. The new form would ask some customers for the very information their problem had made difficult to obtain.

The director stared at the diagram. “Why didn't anyone say that in the meeting?”

There may not be one answer. The coordinator may have needed time to connect the requirement with recent calls. Someone else may have assumed that the project team had tested the exception. The meeting may have felt too crowded for a complicated concern. Or the final question may have signaled that the decision was complete and that an objection now required more confidence, evidence, and social risk than agreement.

Silence does not disclose its own cause. It can mean consent, uncertainty, fatigue, calculation, confusion, or simply that a thought has not formed yet. Treating it as proof of agreement gives absence more meaning than it can carry.

Still, the scene reveals a positional difference. The director could see case volume, processing time, launch dependencies, and the burden of duplicate requests. The coordinator could see recurring moments when a customer did not fit the process. One view had breadth. The other had proximity.

Neither view was complete. Only one, however, had been translated into a requirement.

A role directs attention. It places certain information nearby and pushes other information toward the edge. The person approving a policy sees tradeoffs that may be invisible to the person carrying it out. The person carrying it out encounters exceptions the policy-maker may never meet. Different chairs face different parts of the room.

The chair is not a moral diagnosis. Authority does not make a person dishonest, and proximity does not make another person correct. The problem begins when the view available from one position is mistaken for the whole landscape.

Status adds another layer. The director can raise a doubt without first demonstrating loyalty to the project. The coordinator may need to consider whether a concern will sound helpful, resistant, poorly timed, or insufficiently solved. Even an approachable leader can control assignments, evaluations, access, or future opportunities. “Any concerns?” does not remove those stakes.

The view from the top may be wider and farther away at the same time.

That distance creates a hidden dependence. The decision-maker needs information held by people who may be least able to supply it casually. The question is no longer only, “What am I missing?” It is also, “What have I made difficult to tell me?”

Silence can be produced by the cost of correcting the person who asked.

A Real Question Risks a Real Answer

The next morning, the director reopens the conversation with the project team.

The first question that comes to mind is understandable: “Why didn't anyone flag this earlier?” It might uncover a missed review step. Asked first, however, it places the failure everywhere except in the design of the meeting and the status of the person asking.

Not every sentence ending in a question mark is an inquiry.

“We've covered the important exceptions, right?” is a request for endorsement. “Does anyone know the escalation rule?” is a knowledge test. “Did you consider customers who cannot find the serial number?” may be useful, but it contains the category the questioner now knows to seek.

A different question admits a genuine gap:

“Who will have the hardest time using this process, and what can you see in the calls that I cannot see in the dashboard?”

The director cannot answer that question alone. Its wording identifies the limits of the director's view and gives frontline experience a legitimate role in examining the plan. It does not promise that every concern will determine the outcome. It makes room for information that success language and implementation momentum had pushed aside.

This is the useful tension in Schein's humble inquiry. To ask a question whose answer you do not already know is to accept a temporary dependence. The other person has something you need. Formal authority remains, but the performance of complete knowing loosens long enough for another view to enter.

A real question gives up control over the answer without surrendering responsibility for the decision.

Research offers bounded reasons to take that discipline seriously. Across several studies, greater power was associated with more difficulty taking another person's perspective on specific tasks. The finding does not describe every leader, but it cautions against treating good intentions as a substitute for checking another vantage point. Galinsky et al., 2006

People also attend to how a manager receives input. In one large workplace study, perceived managerial openness was associated with more improvement-oriented voice, with psychological safety helping to explain that relationship. One study cannot show that an open question causes candor. It does reinforce a practical point: people assess the receiver as well as the message. Detert & Burris, 2007

Wording is therefore only the beginning. If the director asks the improved question while checking email, interrupts the first answer, or explains why every proposed change is impossible, the sentence remains open while the exchange closes.

The same is true when consultation occurs after a decision can no longer move. Feedback may still inform a later revision, but people deserve honesty about what is open, what is fixed, and what will happen to their response.

Some settings need more than a better meeting. A private conversation, written review, anonymous channel, accessible format, independent escalation route, or protection against retaliation may be necessary. Direct candor should not become an entrance fee for participation.

Nor should one person be asked to represent an entire group. Proximity creates knowledge, not omniscience. The coordinator can describe recurring calls and specific failures without speaking for every customer or colleague.

A question is not open merely because its grammar is.

Its openness depends on the answers permitted, the risks attached to them, and whether the person asking is prepared to be changed by what becomes known.

Let the Other View Reach the Method

The director returns to the coordinator's concern without asking the coordinator to defend the entire value of the project.

“Let me make sure I understand,” the director says. “The serial number helps us connect a request to the right service record. But for some installed devices, the customer may not be able to reach the label, and the failure itself may prevent the number from appearing on screen. The form could block a legitimate case before anyone sees it.”

The coordinator agrees and describes several recent calls. The director asks what employees currently do when the number is unavailable. Sometimes they search by purchase record. Sometimes they confirm a model and installation address. Sometimes the case requires a specialist. Each alternative creates work and carries its own risks. The original requirement solved a real problem; it also created another.

Now the answer can enter the method.

The team considers an alternate verification route and a small test with frontline staff before the full launch. The director explains which security requirement cannot be removed, who will examine the exceptions, and when the team will hear whether the form will change. The coordinator has not been granted automatic authority over the design. The concern has been given a traceable path through the decision.

That distinction matters because invitation is only the beginning of voice. Research on employee voice and silence shows that people weigh risk, likely impact, relationships, and context before communicating concerns upward. Silence can leave useful information unavailable without revealing one certain motive. Morrison, 2014

Reception has its own distortions. Research has found that managers can evaluate challenging voice less favorably than input that supports existing practices, partly through perceptions of threat and loyalty. This does not make every challenge correct. It shows how an organization can praise speaking up while filtering out information that disturbs its current direction. Burris, 2012

The difficult answer is often the one that tests whether the invitation was real.

Receiving it well does not require immediate agreement. The director may discover that the proposed alternative introduces a larger security problem. Cost, timing, law, safety, or technical limits may constrain the response. Inquiry does not erase the obligation to judge.

It changes what judgment must include.

A responsible response can therefore take several forms: “We are changing the requirement.” “We need a test before deciding.” “We cannot change this portion, and here is the constraint.” “This concern belongs in a protected process rather than this meeting.” What should not happen is for appreciative language to become the place where inconvenient knowledge disappears.

Closing the loop matters even when the decision remains unchanged. It tells people whether their information was understood, what evidence was weighed, and whether future input has a route into the system.

If the answer cannot reach the method, the question was mostly decoration.

Whenever your role gives you influence over a shared plan, it also gives you a particular view. The question that travels beyond this workplace scene is simple: who encounters the consequences from a place you do not occupy?

The person closest to the decision may be farthest from the part of reality the decision will touch. Once another view becomes available, wisdom is measured by what that view is allowed to change.

🪑❓🔍

Practice: The Question You Cannot Answer

Choose one decision, routine, assumption, or process you influence. Select something specific enough to examine and safe enough to discuss. Do not use this exercise to pressure someone into disclosing private, protected, or professionally sensitive information.

1. Decision: What is being decided, changed, continued, or evaluated? Describe the current direction and what remains genuinely open to revision.

Prompt: “The decision or process I influence is __________. The part that can still change is __________.”

2. Position: What does your role make easier to see? What distance might it create from implementation, exception, or consequence? Consider authority, expertise, access, resources, relationships, and information.

Prompt: “From my position, I can see __________. I may be farther from __________.”

3. Witness: Who encounters the decision from another position? Identify one person or role with relevant proximity without assuming that person represents an entire group or already holds the answer.

Prompt: “A person closer to this part of the experience may be __________ because __________.”

4. Genuine Question: What can this person answer that you cannot answer for them? Draft one non-leading question that permits disagreement, uncertainty, correction, or refusal.

You might ask:

  • “From where you sit, what is this decision making harder that I may not be able to see?”

  • “Who is least well served by this process, and what evidence would help us understand why?”

  • “What assumption in this plan should we test before treating it as settled?”

Remove wording that contains the answer you want to hear. Avoid “Don't you agree...?” and questions that make someone explain why they failed to speak sooner.

5. Response: Plan how you will receive the answer. What will you reflect back for confirmation? What constraint must you disclose? What next step will you name, and when will you close the loop?

Complete these sentences:

“What I heard was __________. The part this may change is __________. The part that remains constrained is __________. I will return with an update by __________.”

Judge the Practice by whether another view becomes more accurately understood and gains an honest route into the decision, not by whether you accept every suggestion.

If direct speech carries meaningful risk, stop. Consider a safer written or anonymous channel, representation, independent escalation, or a formal reporting process. This is a reflection exercise, not a substitute for safeguarding, accessibility, labor, legal, medical, psychological, or other qualified professional support.

Scientific Summary

Schein defined humble inquiry within a practitioner-oriented account of organizational relationships, hierarchy, and interdependence. The opening quotation is an excerpt from his definition on page 2 of the 2013 edition. His framework distinguishes asking about something one does not already know from using questions to deliver advice, test knowledge, or steer another person toward a preferred answer. It is a conceptual and practice framework, not an experimental demonstration that one style of question creates trust or improves decisions. Schein, 2013

Galinsky and colleagues reported four experiments and a correlational study examining power and perspective-taking. Participants assigned to or associated with greater power showed less perspective-taking on several tasks involving privileged knowledge and recognition of emotional expressions. The findings suggest that power can impede perspective-taking under particular conditions. They do not establish a permanent trait, apply uniformly to every person with authority, or show that one reflective Practice reverses the effect. Galinsky et al., 2006

Detert and Burris examined change-oriented leadership and employee voice in a two-phase study involving 3,149 employees and 223 managers in one restaurant chain. Perceived managerial openness was more consistently related to improvement-oriented voice than transformational leadership, and perceived psychological safety statistically mediated the relationship. The design supports an association among these variables in that setting. It does not prove that asking a particular question causes candor or establish equivalent effects across industries and relationships. Detert & Burris, 2007

Morrison's review describes employee voice and silence as a research area concerned with whether suggestions, concerns, problems, and opinions are communicated upward or withheld. Burris's field and experimental studies add evidence that managers may evaluate challenging voice less favorably than supportive voice, with perceived threat and loyalty involved in the response. These findings justify examining reception as well as invitation. They do not assign silence one motive, require endorsement of every challenge, or show that all dissent receives punishment. Morrison, 2014 Burris, 2012

Together, the sources support a restrained conclusion: position can shape perspective, people assess the risks and likely impact of speaking, perceived openness is associated with voice, and challenging input may be harder to receive. They do not establish a single causal sequence in which authority creates blindness, a question creates safety, disclosure produces action, and action improves the result. The customer-support scene is illustrative, and The Question You Cannot Answer is a Lucivara reflection tool rather than a validated intervention or reporting process. Its invitation is narrower than the evidence: identify the boundary of your current view, ask for knowledge you cannot supply yourself, and give the answer an honest path into what happens next.


Bibliography


Legal Disclaimer: The content published on Lucivara is provided for informational, educational, and reflective purposes only and is not intended to constitute medical, psychological, legal, or professional advice. Lucivara does not diagnose conditions, prescribe treatments, or provide therapeutic or professional services. Readers are encouraged to consult qualified professionals regarding any personal, medical, psychological, or legal concerns. Use of this content is at the reader’s own discretion and risk. Copyright Notice: © 2026 Lucivara. All rights reserved. This content is protected by copyright laws and is intended for individual, personal, and non-commercial use only. No part of this publication may be reproduced, distributed, transmitted, displayed, published, or broadcast in any form or by any means without prior written permission from Lucivara. Acceptable Use: The content published on Lucivara is intended for individual, personal, and non-commercial use only. Readers may access, read, and engage with the content for their own reflective, educational, or informational purposes. Except for such ordinary human use, no portion of this content may be copied, reproduced, redistributed, republished, transmitted, stored, scraped, extracted, indexed, modified, translated, summarized, adapted, or incorporated into derivative works without prior written permission from Lucivara. This restriction expressly includes, without limitation, the use of Lucivara content for training, fine-tuning, prompting, testing, benchmarking, or operating artificial intelligence systems, machine learning models, automated agents, bots, or any other computational or data-driven systems, whether commercial or non-commercial. By accessing or using this site, readers acknowledge and agree to Lucivara’s Terms and Conditions.

Next
Next

26.260 - Mentorship Without Replication