Workplace relationships and communication
How to Work with (Almost) Anyone Summary: Five Questions for Better Collaboration
How to Work with (Almost) Anyone helps colleagues discuss their strengths, preferences, past experiences and repair needs so that the way they work together becomes an ongoing shared responsibility.
One-Sentence Answer
How to Work with (Almost) Anyone helps colleagues discuss their strengths, preferences, past experiences and repair needs so that the way they work together becomes an ongoing shared responsibility.
What The Book Is About
Michael Bungay Stanier’s subject is the working relationship itself. Teams often discuss the task, deadline and budget while leaving expectations about each other unspoken. His alternative is a Keystone Conversation: an intentional exchange about the conditions under which two people can do good work together. The goal is a Best Possible Relationship, described in the book as safe, vital and repairable.
This is a practical workplace communication book rather than a personality test. A useful conversation can surface preferences without turning them into permanent labels. It also creates a reason to return to the relationship when circumstances change. The title’s “almost” matters: the approach is an invitation to improve cooperation, not a promise that every relationship can or should continue.
The author’s book overview, authorized opening chapter and contents and Macmillan’s Page Two edition record establish the scope and edition used here.
Who Should Read It
Read it when you and another person can perform your individual jobs but keep misreading each other’s intentions. A new manager and direct report, two project partners or a client and supplier can all benefit from discussing how they want the relationship to work. It is especially relevant before a handoff, a change in responsibility or a period of unusually close collaboration.
Choose a different starting point if you primarily need a negotiation strategy, a presentation outline or a way to investigate misconduct. An informal relationship discussion does not replace an organization’s reporting process or settle disagreements about contractual authority. People also need room to decline personal disclosure. The book is most useful when both sides can participate meaningfully and can make at least some changes to their own conduct.
Main Summary
The book argues that working relationships deserve deliberate attention. Good intentions and a shared assignment do not automatically produce mutual understanding. Colleagues can bring different expectations about availability, feedback, decisions and respect, then mistake the resulting friction for evidence that the other person is impossible. Bungay Stanier proposes talking about the relationship before simply demanding better performance within it.
The central structure is a Keystone Conversation built around five questions. Their names are Amplify, Steady, Good Date, Bad Date and Repair. They explore what brings out a person’s best, their working preferences, lessons from successful and frustrating relationships, and how the pair will respond when things go wrong. Preparation comes before the exchange; maintenance continues afterward. The questions support a relationship rather than finishing it in a single meeting.
For a concrete application, imagine a community archive hiring a freelance exhibition designer. The archive coordinator needs careful checking of object descriptions. The designer needs clear decisions about layout. Neither preference is inherently unreasonable, but silence about them could turn every revision into an argument about competence. A conversation about their working relationship would let them explain what helps them contribute and agree how to raise a concern.
This guide develops that original example throughout the five questions. It also adds practical limits: a preference is a request to discuss, an agreement should be feasible, and a lower-power participant should not be pressed to disclose personal history. Those are editorial applications, not reported incidents from the book.
The reader’s likely benefit is a clearer shared understanding of how to collaborate and how to repair an ordinary rupture. The test is not whether the meeting feels unusually intimate. It is whether each person can identify an expectation, act on it and revisit it without making the other person the problem. This makes the book a strong companion to task-focused coaching and feedback guides.
Key Ideas
1. Amplify: explain the contribution you want the relationship to support
The Amplify question directs attention to a person’s best contribution. Rather than beginning with a catalogue of irritations, consider what makes collaboration worthwhile. This is not an invitation to deliver a polished personal brand statement. An answer becomes useful when the other person can understand what you do well and how a working arrangement can make room for it.
In the archive example, the designer might explain that she is strongest at turning a complicated visitor journey into a simple sequence. The coordinator might describe his ability to notice inaccuracies before material reaches the public. These contributions could complement each other. They become harder to combine if design exploration is interrupted by constant factual corrections or if accuracy review is postponed until the layout is fixed.
A practical application is to describe one occasion when you contributed effectively, identify the conditions that helped and make a modest request. The designer could ask for one early session to explore alternatives before choosing a direction. The coordinator could ask to review the approved text before it is placed in the final design. Each request concerns the work they will actually do together.
Ask what the other person heard rather than assuming agreement. Their answer may reveal a different idea of what the role requires. This matters because recognizing strengths has limited value unless the relationship supports their use. A useful result is an arrangement that makes good contributions easier, while leaving room to discuss workload, responsibilities and the needs of everyone affected.
2. Steady: turn working preferences into discussable arrangements
The Steady question concerns practices and preferences. Its value is making ordinary habits visible before they are mistaken for disrespect. Someone may think quickly aloud while another person needs a document first. One may expect a prompt acknowledgment, while another treats a message as information until it contains an explicit request. Neither person can reliably infer the other’s assumptions.
The archive coordinator could explain that an unannounced revision arriving late in the afternoon is difficult to check. The designer could explain that repeated short messages interrupt concentrated work. They can then discuss a workable arrangement: a single revision document, a stated review deadline and a separate route for genuinely urgent changes. This is an original application rather than a required channel rule from the book.
Preferences should remain negotiable. A freelancer cannot necessarily promise immediate replies throughout a client’s working day, and a coordinator cannot ignore the museum’s public opening date. Ask which habits matter most, what flexibility exists and what happens when the agreed arrangement is impractical. Accessibility and different time zones can also affect the choices.
Write down only what both people intend to use. A long personal manual that nobody consults may add little. A short agreement about decisions, review windows and urgent issues can be easier to maintain. The point is to reduce guessing while preserving choice. When conditions change, discussing the arrangement again is more constructive than treating an earlier preference as a binding description of someone’s permanent character.
3. Good Date: identify the behavior behind a successful relationship
The Good Date question asks what can be learned from successful past working relationships. Its usefulness lies in moving from a pleasant impression to the conduct that produced it. “We just clicked” does not tell a new colleague what to do. A specific account of reliable decisions, useful feedback or mutual support can reveal practices worth trying together.
The designer may remember a previous client who separated questions from approved decisions. The coordinator may remember a partner who admitted uncertainty early enough for the team to investigate. Neither needs to share private details about named former colleagues. They can describe the relevant working pattern and explain why it helped them participate more effectively.
Translate that history into a request for the present situation. The pair might agree to distinguish an exploratory layout from an approved one, or to flag an unresolved fact before a production deadline. Ask whether the same arrangement makes sense in this project. A practice that worked in a large permanent team may need adjustment for a short contract involving only two people.
This application prevents nostalgia from becoming an unrealistic demand that a new colleague behave exactly like a favorite former one. Good memories are evidence to explore, not instructions that settle the discussion. Each person should have a chance to explain what would work for them now. The value comes from finding an observable behavior that both can understand and reasonably repeat, rather than trying to manufacture instant chemistry or agreement about every preference.
4. Bad Date: learn from friction without conducting a trial
The Bad Date question considers frustrating past relationships. It can help someone explain why an apparently small behavior matters to them. It can also become a complaint session if the conversation focuses on proving a former colleague’s faults. A useful application extracts a lesson about collaboration while protecting other people’s privacy and acknowledging one’s own part in the pattern.
The coordinator might explain that discovering a changed caption after a print deadline previously caused expensive rework. He does not need to name the person involved or infer their motives. The designer might explain that feedback given simultaneously by several people made it impossible to know which instruction had authority. These descriptions establish concerns the current pair can address.
Ask what an early signal of the same problem would look like. Then consider what each person can do before frustration accumulates. A designated decision maker and a visible revision history may be more useful than an assurance that nobody will ever make a mistake. They should also discuss when an unresolved issue needs someone else’s decision.
Participation needs limits. A person may prefer to describe a general working difficulty rather than revisit a painful experience. Accept that choice. This is a conversation about collaboration, not a demand for personal disclosure. Its value is a more accurate understanding of a preventable problem and an agreed response. It should leave both people with greater practical agency, rather than making one responsible for compensating indefinitely for every disappointment the other has experienced.
5. Repair: agree how to raise a rupture while cooperation is still possible
The Repair question gives the pair a chance to discuss what they will do when the relationship becomes strained. Anticipating a problem is different from expecting failure. It acknowledges that even considerate people make assumptions, miss signals or respond poorly under pressure. An agreement about returning to the issue can make a small rupture easier to address.
For the archive project, the pair might choose to raise a concern directly and privately, describe the specific event and propose a time to discuss it. If a deadline is too close for a full conversation, they can separate the immediate decision from the later relationship discussion. This is an editorial example, not the book’s official repair script.
Discuss how to tell whether an attempted repair helped. An apology may matter, but the arrangement that produced the problem may also need changing. If the coordinator repeatedly supplies late corrections, he may need an earlier verification deadline. If the designer overlooks approved instructions, she may need a clearer way to confirm the current version. Repair includes action that the other person can observe.
Some difficulties require a reset, a change in responsibilities or an end to the arrangement. A commitment to repair should not become a requirement to tolerate repeated mistreatment. The practical benefit is a shared route back to discussion, with appropriate boundaries and escalation available. Working relationships stay useful through attention over time; one successful Keystone Conversation does not remove the need to notice changes and renegotiate what cooperation requires.
Practical Takeaways
- Choose one relationship where a better way of working would improve an actual task. Avoid starting with the most hostile situation simply to test the method.
- Explain that the proposed conversation concerns how you work together. Give the other person time to decide and prepare.
- Prepare an example of your best contribution, then identify a condition that helps you make it.
- Describe preferences as requests to explore. Ask what is feasible for the other person rather than expecting automatic accommodation.
- Convert a positive past experience into a present behavior you could try together.
- Discuss a frustrating pattern without naming private third parties or demanding disclosure in return.
- Agree how a concern can be raised, who should hear it and what requires a separate decision maker.
- Revisit an arrangement after using it. Keep what helps, adjust what does not and acknowledge commitments you failed to meet.
How To Apply It
Use a project handoff to discuss the relationship
The archive and exhibition example is an original editorial exercise. Before the project begins, each person privately considers the five question areas. Keep the notes specific to the collaboration: useful contributions, review habits, lessons from other work and a possible repair route. There is no need to create an account of every difficult person in your career.
Invite the other person to a dedicated discussion about how the project relationship can work well. Explain why it matters and offer the questions in advance. If they are uncomfortable with the book’s language, describe the topics plainly. The substance is a reciprocal exchange, not getting someone to participate in a branded exercise.
During the meeting, take turns. When the coordinator discusses accuracy review, the designer can ask what needs verification and when. When the designer discusses uninterrupted work, the coordinator can ask how urgent questions should be handled. Do not use the questions to quietly revise the other person’s role or add obligations that belong in the contract.
Produce a small working agreement. In this example, that might identify the approved text document, the person authorized to request layout changes, a review window and a method for flagging urgent inaccuracies. Record only decisions both understand. Leave unresolved questions visible rather than turning silence into consent.
After the first round of layouts, return to the agreement. Ask which part helped and where it failed. If a review was late, examine what happened before interpreting it as indifference. The coordinator may have lacked a required answer; the designer may not have made the deadline clear. They can still discuss accountability while correcting the arrangement.
A worthwhile result is a relationship that can support honest contributions and ordinary repair. Judge progress by the quality of the next interaction and the reliability of shared commitments. The exercise does not guarantee compatibility, friendship or a successful exhibition. It provides a more deliberate way to work together while both people remain free to identify limits.
Notable Ideas, Paraphrased
Discussing the relationship is part of doing the work. Past experiences can reveal useful expectations without defining the next person in advance. Repair is easier to attempt when a route back to conversation already exists. These are paraphrased themes and editorial conclusions, not direct quotations.
Best Related Books
- The Coaching Habit helps a manager use questions during everyday coaching; it is more focused on the immediate coaching exchange.
- Humble Inquiry develops curiosity and asking for information you do not already possess.
- Difficult Conversations goes deeper into a conversation where accounts, feelings and identity are already in conflict.
Choose How to Work with (Almost) Anyone when your main need is a shared understanding of how to collaborate. Choose a difficult-conversation guide when a specific rupture already needs careful examination. Neither choice removes the need for clear responsibilities and an appropriate decision process.