Ask by Jeff Wetzler Summary: Find What You Are Missing

Key Ideas

1. Choose curiosity by identifying what could surprise you

The first step asks you to choose curiosity. A practical test is whether an unexpected answer could change your understanding. If your only purpose is to secure agreement, another person's concern may feel like an interruption rather than the information you requested. That does not mean every decision must be open. It means you should be honest about the kind of conversation you are offering.

Imagine a project lead preparing to ask a newer teammate about a delivery plan. Before the conversation, the lead writes down the assumption that the work is straightforward. They also identify what they do not know: whether the teammate has access to the required customer information. The resulting question can explore that dependency rather than ask for general reassurance that the date is fine.

For your own preparation, name one assumption and one plausible answer that would challenge it. During the exchange, follow the surprising detail before defending the plan. You can explain a constraint after you understand the concern. Avoid performing curiosity through a long series of questions whose answers never affect your response. This step matters because the intention to learn becomes visible through what you do with information. A small revision, a clarifying question or an acknowledgment of a mistaken assumption can show that the conversation had a real purpose. Even when the final decision stays the same, your explanation should reflect the information the other person contributed.

2. Make it safe through a credible invitation and response

Make it Safe is Wetzler's second step. For a manager, the invitation matters, but so does the response to the first uncomfortable answer. Saying that everyone can speak freely has limited value if the next concern is met with impatience or an immediate defense. A credible invitation defines what input is useful and responds to it without making the speaker regret participating.

In the project example, the lead asks where the plan depends on an assumption that may be wrong. The teammate identifies an unavailable customer contact. The lead thanks them for the specific information, checks the effect on the timeline and discusses an alternative. This is more informative than announcing appreciation for honesty while treating the concern as evidence of poor commitment.

Apply the step by explaining why you want the input and which parts of the plan it can influence. Choose a setting where the person can answer without unnecessary exposure. Do not promise confidentiality or immunity from consequences you cannot provide. If a concern must go through another process, explain that boundary before inviting more sensitive detail. The value is predictability. People should understand what you will do with an answer, including one you dislike. Safety cannot be manufactured by a phrase, but your response can make future communication more or less likely. Focus on the behavior within your control: hearing the concern, clarifying it and handling it responsibly.

3. Pose a quality question with an answer you do not already own

Pose Quality Questions directs attention to the invitation you create. A question can be grammatically open while carrying a preferred answer. Asking how excited someone is about a plan may make it harder for them to explain a serious concern. A useful question gives the person room to select relevant information rather than merely choose the level of agreement you expect.

For the project lead, compare a general request for confirmation with a question about where the schedule is least reliable. The second gives the teammate a specific task and permits a critical answer. A follow-up about what would make that part workable can then produce options. The questions are useful because the lead does not yet know the dependency or the best remedy.

Prepare one question linked to a real uncertainty. Keep it short enough for the other person to remember. Avoid packing several issues into a single turn, then becoming frustrated when only one is answered. After receiving an answer, follow a detail that matters instead of moving automatically to the next prepared question. This step matters because a high-quality invitation reduces the work the listener must do to understand what you are asking. It also makes disagreement easier to express. The goal is an informative answer, not a display of your interviewing skill. A plain question about a specific uncertainty can reveal more than an elaborate prompt that leaves the person guessing about your intention.

4. Listen to learn before explaining your position

Listen to Learn concerns what happens after the question. An answer can contain information you missed, a proposed remedy you disagree with and an emotion you do not fully understand. You can separate those parts before responding. Listening does not require accepting every conclusion, but it does require finding out what the person means before deciding what to reject.

Suppose the newer teammate says the deadline is impossible and proposes delaying the whole project. The lead can first clarify the blocked work and its effect. It may turn out that only one deliverable depends on the unavailable contact. The proposed delay may be broader than necessary, while the underlying concern is valid. A response that immediately argues against postponement would miss that distinction.

Use a short paraphrase and invite correction. Ask which fact or constraint is most important. If you feel an urge to explain why the plan was reasonable, make a note and return to it after the answer is clear. Do not use paraphrasing as a ritual before delivering the same response you had prepared. Let it improve your understanding. This matters because people can otherwise experience questions as a prelude to correction. When listening changes the description of the problem, later disagreement can become more precise. You may decline the proposed remedy while incorporating the information that made the remedy seem necessary to the other person.

5. Reflect and reconnect with the effect of what you heard

Reflect & Reconnect completes the Ask Approach. It connects a useful conversation to a later decision or action. Reflection helps you distinguish what you learned from your first reaction. Reconnection lets the contributor know how the information was understood and used. Without it, someone may have provided important input and still have no idea whether it mattered.

In the project example, the lead revises the order of deliverables and asks another colleague to help obtain the missing information. A short follow-up explains the change, thanks the teammate for identifying the dependency and states which part of the original deadline remains. The update gives the teammate a chance to correct an interpretation before work proceeds on the wrong assumption.

After a conversation, record the new information, its implication and the action you own. Return at the scale of the issue; a brief message may be enough. If you decide not to act on a suggestion, explain why without pretending that asking created a promise to implement it. Protect sensitive details when reporting a broader pattern. This matters because learning is a relationship over time. A clear return can make the next difficult answer easier to share. It also improves accountability: the conversation ends with an understandable result rather than a warm acknowledgment that dissolves into silence. Reconnection shows what changed and identifies the next question that still needs attention.