Ask More Summary: Frank Sesno's Questioning Toolkit

Key Ideas

1. Diagnostic questions reconstruct the problem before naming the cause

Diagnostic inquiry is useful when people agree that something is wrong but offer different explanations. A label such as poor communication can cover late input, unclear ownership or an unavailable decision. Asking for a concrete sequence gives the team information it can compare, instead of another round of opinions about the label.

Consider an original project review. The launch slipped, and one person says engineering took too long while another says requirements kept changing. Ask what was expected at a specific point, what arrived and what happened next. A timeline may reveal that the team began work before a necessary approval. That finding does not automatically absolve anyone. It changes the question from who generally works too slowly to which dependency needs a reliable owner.

Prepare questions about observations, sequence and consequences. Keep interpretation separate until the relevant events are clear. If an answer is vague, ask for one example rather than demanding a sweeping explanation of the entire project. Diagnosis matters because a remedy should fit the problem. More reminders will not solve an unresolved approval route, while a new process may be unnecessary if one commitment was simply missed. Stop gathering detail when you can describe the problem and the important uncertainty. The next useful move may be verification or a decision. A diagnostic conversation should make action better informed, not become an endless reconstruction that nobody can use.

2. Strategic questions expose the conditions behind a plan

Strategic inquiry is useful when a team needs direction rather than a detailed account of the past. A plan can contain many tasks while leaving its purpose and assumptions unclear. Questions about success, dependencies and tradeoffs help people evaluate whether the proposed route is plausible. They also reveal where apparent agreement rests on different definitions of the result.

In an original planning discussion, a team proposes a webinar series. Before choosing topics, ask what change the series is intended to create and how the team would recognize that result. One person wants qualified leads; another wants existing customers to use a feature. Those are different objectives and may require different audiences, examples and follow-up. The question prevents the team from optimizing a format before deciding its job.

Write the outcome, the key assumption and the resource constraint you need to test. Ask about each separately. Avoid a strategic question so broad that nobody knows whether you want a vision, a forecast or a next step. Be clear about which decision the answer informs. This matters because strategy discussions can produce inspiring agreement without a workable choice. A useful question makes the tradeoff visible: which audience takes priority, what the team will stop doing and what evidence could change the plan. Once that is clear, move to a concrete commitment. Do not keep the conversation at the level of possibility when the work requires a decision.

3. Empathy questions make room for experience without demanding disclosure

Empathy questions serve a different purpose from diagnosis. They invite you to understand how a situation is experienced by another person. A factual account can be accurate while leaving out what was difficult, important or unexpected for the speaker. The aim is to learn that meaning, with respect for the person's choice about how much to share.

Imagine an original one-to-one with a teammate who has become quiet during planning. Instead of asking why they have stopped contributing, ask which part of the current work has been hardest to navigate. They may describe uncertainty about priorities rather than a personal problem. Follow the answer they give. You do not need to extract a deeper emotional explanation before their operational concern deserves attention.

Choose a question relevant to the relationship and setting. Allow a brief answer to remain brief. If the person describes a difficult experience, acknowledge what you understood before offering a comparable story or solution. Ask whether a practical response would help when the purpose is unclear. This matters because empathy can become intrusive if the listener treats depth as a goal in itself. A useful exchange preserves the speaker's agency. It can also improve the eventual work conversation by showing which concern needs recognition and which needs a decision. Understanding someone's experience does not require agreeing with every conclusion, and it does not turn their personal account into permission to share it elsewhere.

4. Confrontational questions seek accountability through specific facts

Sesno's account includes confrontational questioning. In a workplace application, the useful function is accountability, not aggression. A question can be direct about a missing answer or commitment while avoiding a broad attack on character. Specificity gives the person an opportunity to explain, correct or accept responsibility for the actual issue.

Consider an original follow-up after a promised report has not arrived. Asking why the colleague never respects deadlines invites a debate about their history and motives. A more useful question identifies the agreed delivery, its current absence and the information needed now: what prevented completion, when the team can rely on the report and which interim decision is required. If the explanation does not answer the question, return to the missing part plainly.

Prepare the relevant facts and check that the commitment was actually shared. Do not imply misconduct before establishing what happened. Keep your tone and wording proportional to the issue, and use the proper process if the matter exceeds your authority. Accountability matters because a conversation can otherwise remain pleasantly vague while the same cost falls on others. A clear question makes the obligation discussable. It also gives you a fair basis for the next step. The goal is an answer the team can act on, not a moment in which the person feels defeated. If they cannot make the commitment, the conversation needs an explicit reassignment, priority decision or escalation rather than another ambiguous promise.

5. Creative questions change an assumption while preserving the task

Creative inquiry is useful when a team keeps generating variations of the same answer. One way to open the discussion is to identify a constraint everyone has treated as fixed and ask what would happen if it changed. The question should still connect to the task; an unlimited invitation to imagine anything can leave people unsure what a useful idea would look like.

In an original workshop, the team wants to improve onboarding but assumes the answer must be a longer presentation. Ask how a newcomer could learn the critical decision without attending any presentation. That question might produce a worked example, a guided task or a short conversation with an experienced colleague. The team can later compare those ideas with the real time and resource limits. Generating an alternative does not mean every constraint has disappeared.

For practice, write the desired outcome and one assumption about the current method. Change the assumption in a question, then give people time to think before evaluating answers. Separate the moment for producing options from the moment for choosing among them. This matters because immediate objections can shut down exploration before an idea is clear, while endless brainstorming can avoid the difficult choice. A creative question is useful when it expands the available options and improves the later decision. Close by naming what is worth testing, what evidence is needed and who will take the next step. Possibility becomes valuable when it connects back to a real problem.