Leadership communication and working relationships
Humble Leadership Summary: Relationships That Help Truth Travel
Humble Leadership argues that complex work depends on open, trusting relationships in which people can contribute knowledge beyond the limits of their formal roles, with humility grounded in their real dependence on one another.
One-Sentence Answer
Humble Leadership argues that complex work depends on open, trusting relationships in which people can contribute knowledge beyond the limits of their formal roles, with humility grounded in their real dependence on one another.
What The Book Is About
The publisher’s second-edition page confirms the subtitle and its focus on relationships, situational humility and a culture that supports collaborative leadership. Peter Schein’s release announcement identifies the 2023 revision and its added attention to culture and groups.
The book’s authorized opening preview names situational humility and Level 2 relationships that acknowledge the whole person. These are more specific than a general recommendation to be a modest or friendly boss. The question is what kind of relationship lets people learn and work together when no participant holds all the necessary knowledge.
The city-museum installation case below is an original editorial application. Its people and events are invented. The five reading practices select from the book’s relationship emphasis; they are not a five-step model attributed to the Scheins.
Who Should Read It
Read this when formal reporting lines work on paper but necessary concerns arrive too late. It suits a department head, project leader or specialist who depends on colleagues’ knowledge and notices that status filters what gets said. A manager seeking a different way to relate to a team will find a closer fit than someone seeking presentation techniques.
Read with care if your workplace equates personal openness with disclosure of private life. Recognizing someone as a person does not entitle a manager to intimacy. Trust also requires fair decisions, credible follow-through and routes for concerns outside a single relationship. A book about relationships cannot by itself remove retaliation, discrimination or unsafe working conditions. Those limits matter when deciding which practices are appropriate and who bears the risk of trying them.
Main Summary
The Scheins place relationships at the center of leadership. People confronting unfamiliar, interdependent work need information and judgment that their job titles cannot supply by themselves. A leader’s willingness to recognize that dependence is part of situational humility. The relationship then matters because colleagues must be able to offer information, concerns and corrections that may challenge the leader’s existing view.
The second-edition chapter preview on personal relationships connects this dependence to sharing knowledge and refining what the group is trying to achieve. Level 2 describes an openness to the whole person, beyond a purely role-defined exchange. The authors explain personization in an interview reproduced by Mobius Executive Leadership: it concerns a relationship between people, rather than customizing a service for an employee.
Consider an original example at a city museum. An exhibition director promises an installation date. A technician notices that a display component will not fit through the service entrance, but assumes the director has already settled the plan with the supplier. The director interprets silence as agreement. The problem is more than a missing dimension: the working relationship has not made it easy to question an apparently final decision.
A different exchange begins with the director naming what remains uncertain and asking the technician to walk through the delivery route. The technician’s knowledge can then influence the plan. Whether that openness lasts depends on what the director does with the concern, how the group makes the decision and whether the next person can raise an awkward fact too.
Read the book as a relationship-and-culture argument illustrated through organizational experience. Its examples should not be treated as a guarantee of improved performance in every setting. The useful application is to examine where information is lost, what relationship conditions contribute and what responsible change could make the next exchange more candid. Better questions help, but the continuing relationship gives those questions their credibility.
Key Ideas
1. Make dependence on other people’s knowledge explicit
Situational humility is tied to the particular task and what you cannot accomplish alone. In the second edition’s account, a leader needs knowledge held by other people. An editorial application is to name the specific uncertainty that makes their contribution necessary. This is more useful than a general announcement that you are humble, approachable or always willing to listen.
At the museum, the director could explain that the supplier’s drawing does not show the route from the loading bay to the gallery. Ask the technician to check that route before confirming delivery. The request identifies why the technician’s expertise matters and which decision it can affect. It does not require the director to pretend ignorance of everything else about the exhibition.
Prepare by separating what you know, what you assume and what another person is better placed to inspect. Ask for the missing contribution early enough to change the plan. Seeking input after signing an irreversible commitment may leave colleagues carrying responsibility without meaningful influence. Explain any fixed constraints so that the invitation is honest about the available choices.
This matters because dependence already exists whether a leader admits it or not. Naming it can make a hidden gap discussable. The next obligation is to respond responsibly when the information is inconvenient. If the technician finds an obstacle, thank them for identifying it and work through the consequence. A request for expertise gains credibility through what follows, rather than through how warmly the leader phrased the opening sentence.
2. Build a working relationship with the person beyond the role
Level 2 relationships acknowledge the whole person. The authors’ term personization emphasizes an open connection between people who might otherwise meet only as a director and a technician, a manager and a report, or an expert and a client. The practical issue is whether each can contribute as someone with experience and judgment, rather than simply performing the expected script of a position.
In the museum, ask the technician how previous installations have worked and what they would want the planning team to understand. Listen to the part of the job that is usually invisible from the director’s desk. Offer relevant context about the exhibition’s commitments in return. The relationship becomes more informative because both participants can understand the work from another perspective.
Keep that exchange voluntary and proportionate. Knowing a colleague as a person can include their professional experience, priorities and preferred ways of collaborating. It does not require discussing family, health, identity or another private subject. The boundaries here are editorial recommendations for applying the relationship model in a workplace with unequal power.
This distinction matters because compulsory personal sharing can imitate closeness while making candor harder. A colleague who declines a social invitation or answers briefly can still be a committed collaborator. Look for whether the working exchange permits questions, correction and disagreement. Do not turn Level 2 into a label you award to employees who behave like friends. A relationship serves the work when both people retain dignity and a meaningful say in how they participate.
3. Treat an inconvenient concern as a contribution to the shared task
The Scheins connect open relationships to information and corrections that a group needs. The editorial application is to examine the first response to an awkward fact. A team can invite concerns in principle while discouraging them through irritation, dismissal or demands that the person raising a problem solve it entirely before speaking.
When the technician explains that the component cannot pass through the doorway, the director can ask to see the measurements and clarify the practical choices. That response keeps the concern connected to the installation. Blaming the technician for the timing, or defending the plan before checking the dimensions, shifts attention toward the cost of speaking up. The director may still need to examine why the obstacle was missed, but that is a separate conversation with a fair account of responsibility.
Make the next action visible. Perhaps the supplier can assemble the component inside the gallery; perhaps the exhibition design must change. State who will investigate and when the group will decide. If the concern proves mistaken, explain the relevant evidence without making the person regret checking. Candid information includes uncertainties that need examination, not only perfectly packaged answers.
This matters because colleagues learn from responses over time. One welcoming meeting does not establish an enduring condition for truthfulness. Follow-through, fair attribution and proportionate investigation are editorial tests of whether the invitation has substance. A leader should also provide other routes for serious concerns. No individual relationship should become the only doorway through which a person can report a problem that affects the organization.
4. Carry openness into group routines and decision records
The second edition gives additional attention to groups and culture. For communication practice, this moves the question beyond whether a director has a good relationship with one technician. A group also needs a repeatable way to combine knowledge and understand how a decision was reached. Otherwise candor can depend on personal access to the most powerful person.
Before the museum confirms the delivery plan, bring the relevant people into a short practical review: installation, visitor access, the supplier contact and the exhibition lead. Ask each what they see from their part of the work. Avoid inviting people merely to endorse a finished answer. Explain which decisions remain open and who is responsible for resolving them.
Record the assumptions that matter, the person checking each one and the next decision date. These are original application suggestions, not a meeting template reproduced from the book. The record helps a colleague who was absent understand why the plan changed. It also gives a later concern somewhere to attach, rather than forcing its owner to reopen the entire argument from memory.
This matters because culture becomes visible in ordinary repeated actions. If the director invites a concern and then deletes it from the record to keep the plan looking tidy, the public invitation has little practical value. If the group keeps the relevant uncertainty visible and resolves it fairly, the behavior can be repeated by someone other than the director. Relationships and routines can support one another without making every task dependent on a charismatic leader’s personal availability.
5. Match the relationship to the work and keep accountability clear
The publisher describes situational humility in the second edition as requiring movement among relationship types. A useful editorial conclusion is that more personal conversation is not automatically the answer to every exchange. The relationship must support the task while respecting professional boundaries, responsibility and the other person’s willingness to participate.
At the museum, an urgent instruction to clear a delivery route may need to be direct. A review of how the planning process missed the doorway needs more time for inquiry. Neither moment is improved by pretending that the director and technician have identical authority. Say who will decide, what input is needed and what must happen immediately. Openness can coexist with a clearly assigned duty.
Likewise, relationship building should not substitute for practical corrections. If the director repeatedly overrules technical warnings and then asks everyone to trust one another more, the problem includes decision behavior. The appropriate change may involve a required technical check, a different approval responsibility or escalation to another authority. A friendly conversation cannot compensate for a process that punishes accurate information.
This matters because the book’s language can be misused as a demand for loyalty or emotional closeness. Apply it to the quality of cooperation, not to whether colleagues like the leader. Review whether people can contribute relevant knowledge, receive a fair response and understand their responsibilities. If those conditions improve, the relationship is helping the work. If they remain absent, name the unresolved obstacle instead of treating a pleasant tone as evidence that leadership has changed.
Practical Takeaways
- Identify one decision that depends on knowledge outside your role, then seek that knowledge before committing.
- Explain which assumptions remain open and which constraints are already fixed.
- Ask colleagues about their experience of the shared task without requiring private disclosures.
- Respond to an awkward fact by checking it and assigning the next action before debating blame.
- Preserve relevant concerns and uncertainty in the decision record.
- Give absent or less-connected colleagues a practical route into the information flow.
- Review responsibilities and formal safeguards alongside the tone of the relationship.
How To Apply It
Choose one interdependent handoff that repeatedly produces late surprises. This original exercise uses the museum installation, but it can apply to a project review or service transition. Start by naming the decision, its owner and the people whose knowledge is necessary. Do not begin by rating colleagues’ personal openness.
Have a short conversation with one person whose work you do not fully understand. Explain the task and the gap in your knowledge. Ask them to show how their part actually happens. At the museum, walking the route can make a constraint visible that an abstract planning meeting missed. Make clear whether observations will be shared with others and for what purpose.
Bring the relevant finding into the group’s decision. Distinguish the fact, its consequence and the available options. The director might explain that the doorway is narrower than the component, ask the supplier about assembly alternatives and name when the revised plan must be chosen. Record the decision and give credit for the useful contribution without turning the technician into a public symbol of bravery.
After the installation, review both the task and the communication. Did the information arrive early enough? Could someone question the plan without having a personal friendship with the director? Did raising a concern create extra punishment or unacknowledged work? Agree on one routine that would improve the next handoff. Keep the review connected to actual behavior. Declaring the team a high-trust culture is less informative than showing what changed when a person supplied information the plan had not allowed for.
Best Related Books
- Humble Inquiry focuses more closely on asking from curiosity in a status-sensitive exchange.
- Helping examines offering and receiving help, including the relationship created by those roles.
- Humble Consulting applies a related relationship emphasis to the work of providing help as a consultant.
Choose Humble Leadership when your question is how the pattern of working relationships affects a group and its culture. Choose these related books when the immediate task is asking, helping or consulting. The books overlap in attitude while addressing different units of work.