How to Say Anything to Anyone Summary: Work Candor

Key Ideas

1. Establish permission before the difficult moment

Harley’s emphasis on prior permission addresses a common gap between knowing a sentence and feeling able to say it. Colleagues may recognize a problem but avoid discussing it because they do not know how the relationship will handle feedback. An advance conversation can make the invitation explicit, especially when it includes what the receiver will do when a concern is raised.

In the original handoff case, the analyst can ask the account lead to flag a report that does not answer the customer’s question. The lead can invite early notice when a promised date becomes unrealistic. Each invitation concerns a concrete part of the work. A broad statement that everyone should be candid is less informative about what happens when the feedback is inconvenient or comes from someone with less authority.

Prepare a short agreement about the kinds of concerns you want raised, a practical way to raise them and how you intend to respond. Keep the invitation reciprocal where the relationship permits it, while recognizing that a manager has more responsibility to make speaking safe in practice. This matters because permission is demonstrated after the invitation. If the first correction produces ridicule or retaliation, the original words will not carry much weight. Review the agreement after an actual exchange. Ask whether the person could raise the issue, whether they were heard and what needs to change before the next concern arrives.

2. Replace obvious-to-me expectations with observable agreements

An expectation can feel self-evident while remaining invisible to the other person. Harley’s approach makes that gap discussable before it becomes an accusation about attitude. A useful agreement describes a behavior, timing and purpose. It gives colleagues a shared reference for later feedback instead of asking them to reconstruct an unstated standard after someone has already been disappointed.

For the handoff, the account lead says they need the analysis by Thursday. The analyst interprets that as a finished report late in the day; the lead needs an early draft to prepare a customer meeting. Clarifying the required stage and time changes the assignment. The team can agree on a draft with known gaps, followed by the finished version. Neither person has to be declared careless for the mismatch to become visible.

Choose one phrase that often creates confusion: responsive, complete, urgent or keep me updated. Ask what it means in the actual work. Include what should happen when the expectation cannot be met. This matters because an agreement without an exception route can encourage people to conceal a problem until the deadline. A clear early-warning practice allows the group to adjust. After the first cycle, check whether the agreement fits reality and revise it together. The purpose is reliable coordination, not collecting rules that one person can later use to prove the other was wrong. An agreement should help both people act before frustration becomes the only signal that something was missing.

3. Ask about working preferences instead of relying on mind reading

Preferences influence how people experience the same behavior. A brief written update may feel efficient to one colleague and insufficient to another who needs a short conversation before deciding. Asking about preferences gives the relationship useful information. It does not mean that every preference becomes an entitlement or that practical work requirements disappear. The next step is to find an arrangement people can actually use.

In the handoff case, the account lead prefers a quick message when a result changes. The analyst prefers to consolidate updates so they can focus. Rather than label one person demanding and the other uncommunicative, ask which changes need immediate attention and which can wait for a scheduled update. The agreement may separate customer-impacting changes from routine progress. The preferences become inputs to a workable process.

Ask how the colleague prefers to receive an urgent concern, what information helps them decide and which communication habits cause avoidable friction. Explain your own needs with equal specificity. Avoid guessing an entire personality from one answer. This matters because preferences can vary by task and context. A person who wants concise email for routine work may prefer a conversation for an ambiguous problem. Record the important agreements briefly and revisit them when the work changes. The value is less guessing about behavior that can be clarified directly, while leaving room to negotiate when two reasonable preferences cannot both be satisfied in full.

4. Receive feedback in a way that keeps the invitation credible

Inviting candor creates a moment of responsibility when the feedback arrives. A receiver who immediately disputes every detail can teach the other person that speaking up is costly even if the invitation sounded sincere. Receiving useful information requires enough space to understand it before deciding which parts you accept. Appreciation for the effort and agreement with the content are different responses.

Suppose the analyst says the account lead’s last-minute requests made the handoff difficult. The lead can acknowledge the information and ask for a specific example. They do not need to agree instantly that every request was unnecessary. They can examine what changed, what the customer needed and whether the timing could improve. Beginning with a defense of how hard the lead works would shift attention away from the coordination problem.

Prepare a response that acknowledges the feedback, clarifies the event and explains when you will follow up if more thought is needed. Avoid making a promise merely to end the discomfort. If you disagree, describe the difference after you understand the concern, using the same specific work standard you would want others to use. This matters because credibility comes from repeated interactions. A colleague is more likely to use the agreed feedback route when it leads to an understandable response. The aim is not permanent agreement, but a relationship in which important information can enter without being treated automatically as disloyalty or disrespect.

5. Address the breakdown with facts and a next agreement

Advance agreements reduce guessing, but they do not prevent every mistake. When a breakdown happens, return to the observable event and the effect on the work. Harley’s emphasis on dealing with situations rather than treating people as problems supports this focus. The practical conversation should identify what changed and what needs to happen next, rather than merely rehearse irritation.

In the handoff case, the draft arrives after the agreed review time. The lead can state the timing, explain that the customer preparation window was lost and ask what prevented the early warning. The analyst may reveal missing data or a misunderstanding about who owned the update. The response should address that information while keeping the original impact visible. A label such as unreliable provides less help in deciding how the next handoff will work.

Close with a specific action and a check on whether the agreement is still realistic. If the problem is repeated, use the repeated facts rather than escalating the adjectives. Clarify which part each person owns and when they will revisit the arrangement. This matters because a candid conversation can feel complete while leaving the operational problem unchanged. A usable next agreement translates the discussion into behavior. At the next handoff, check whether the early warning occurred and whether it gave the lead enough time to adapt. That evidence tells the relationship more than a promise that both people will communicate better in the future.