From Debate to Inquiry: Designing Conversations Worth Preserving | Ep. 21

▶ Watch on YouTube · MIT Sloan CIO Symposium Videos · 1:13:19

In Episode 21 of the MIT Sloan CIO Podcast, Allan Tate and Irving Wladawsky-Berger continue the Collective Sensemaking series with a look at how leaders can design conversations that lead to learning rather than simply reinforce familiar positions. (Part 3 of 4)

They explore the evolution of the Inquiry Framework, a structured approach to stabilizing the question at hand, considering multiple defensible perspectives, testing them against evidence and real-world use cases, and making areas of tension visible without forcing consensus too early.

The conversation also examines the difference between structured uncertainty and indecision. For CIOs and other leaders, inquiry does not replace the need to make decisions. Instead, it can create a stronger foundation for judgment by clarifying assumptions, alternatives, and available evidence.

Listen to Part 3 of this four-part Collective Sensemaking series to hear how better question design can make disagreement more productive and turn important conversations into lasting organizational learning.

— channel description, MIT Sloan CIO Symposium Videos (excerpt; event and community notices omitted)

TL;DR

A ~73-minute episode of the MIT Sloan CIO Symposium’s podcast, published 15 September 2026 and recorded on 2 September. Part 3 of the Collective Sensemaking series with Allan Tate and Irving Wladawsky-Berger. Episode 20 left a question open: since not every conversation produces learning, what makes one worth preserving? This episode’s answer is the Inquiry Framework, which Tate says he “primarily developed” and the two have practised for almost a year. Tate opens by settling the series length: “we started the series thinking it was going to be a three-part series, but in fact, it’s going to be a four-part series” [0:00]. He also says the framework came first and its fit with collective sensemaking was “serendipity” [4:04].

1. Inquiry, not debate (4:04–12:02). Wladawsky-Berger’s model is the research community: a conference or a journal issue carries many points of view because the topic is new. Tate’s version is that this is not an academic framework moved into industry but one “specifically designed uh to be useful to highlevel executives” [6:00]. He brought debates to the symposium pre-event around 2024, from his work with MIT students. Three reasons it did not suit executives [9:00–11:02]:

• A debate starts from a yes-or-no resolution; inquiry wants a richer question explored through lenses.
• A debate looks for the answer; inquiry focuses on the question.
• Poll an audience before and after a debate and “only a fraction” change their mind, so they leave still facing uncertainty and multiple opinions. Inquiry starts from that.

2. Origin: the AI-consciousness conversation (12:02–19:03). Wladawsky-Berger was considering a blog post on AI consciousness; Tate advised against making it a focus, calling much media coverage “clickbait” built on undefined terms. Tate then worked out the framework over many iterations with his AI assistant. Wladawsky-Berger: “I don’t think it was a disagreement. I think it was an exploration.” His reason to drop the topic: “what the hell do we know about consciousness?” That is for philosophers and neuroscientists, and for a CIO audience “AI consciousness is not relevant. What are they going to do with that?” [16:01–17:01]. He contrasts AI in software engineering, a subject the hosts know and the audience needs.

3. Designing the question (19:03–30:02). The first inquiry series was planned as seven parts. Its first question went through rewrites. An early draft, “can machines solve novel problems without explicit human instruction”, was “riddled with uh places for people to get tripped up. You know, what do you mean by novel? What do you mean by human instruction?” The used version: “how do machines approach problems they have not previously encountered?” [20:03–21:01, 30:02]. Rules for a question: its words should be self-evident, it should not be yes-or-no, and it should be stable. Each question gets three lenses, “none of which would be 100% right or wrong”. For the first question these were: applies learned patterns, exhibits behaviors not explicitly anticipated, and frames and solves problems autonomously. The shift is from which side is right to which interpretation best fits the evidence. Wladawsky-Berger adds that concrete cases make the lenses usable: software developers, customer-service staff and researchers give different evidence. He also compares this to prompting: the clearer you are about what you are after, the better a model, or an audience, can help.

4. Running an inquiry (24:01–29:02). The hosts own the question and the lenses. Three lenses is a convention, not “a magic number”. An audience member can propose a fourth, and lenses can each hold “a partial truth”. A session runs: question, lenses, a concrete use case for each, the tensions, and finally why it matters to a CIO, who must decide “in the face of uncertainty”. A volunteer who ran the 2026 pre-event questions adapted the format slightly, which Tate counts as fine.

5. The layer cake (29:02–34:00). The seven-part series was built in tiers: fundamental (what machines can do; four questions), applied (how machine intelligence should be evaluated), advanced (agency, meaning, responsibility; relevant to agentic AI) and an unused speculative tier, where questions such as machine experience, and consciousness, would sit. Wladawsky-Berger’s condition for any speculative question: a CIO or MIT graduate student must know what to do with the answer. Both agree the order matters.

6. Structured inquiry versus indecision (39:00–43:00). Tate’s question: what separates structured inquiry from indecision? Wladawsky-Berger: evidence and use cases; a claim without a concrete case is hard to use. Tate’s summary: the framework explores options, gives evidence and names the tensions “so that the chief… information officer rather can uh take that exploration and make judgments” [42:00–43:00]. In the closing he adds: “this isn’t to say that we want them to evade questions… We do want them to make decisions. We just want them to make informed decisions” [1:06:00].

7. A worked lens: unanticipated behaviour (43:00–50:02). The framework was piloted on the podcast, in an episode on how historians will view our time (Tate thinks episode 13), and then the seven-part series. For the lens exhibits behaviors not explicitly anticipated, Tate’s example: while preparing this episode, the model colour-coded points in red for the hosts’ attention because it had seen Tate do so before. He reads it as newer models being allowed, within safety limits, to infer what a user wants when the step is reversible. He names three layers behind such behaviour: pre-training, the later training for safety and manner, and project context supplied to an instance, with saved state and memories carried from one instance to the next.

8. Collective sensemaking needs an architecture (50:02–1:03:00). Tate draws the line for episode 22: collective sensemaking is “the discovery that the machine can connect the dots across conversations”; doing it at scale is the executive learning architecture, which needs saved and indexed memory records, state handed between threads, and “garbage collection” [50:02–51:02]. It is “an internal tool” not yet exposed to the community. The report is a point in time; the records form “a traceable record” of how views change. Wladawsky-Berger compares it to AI in programming: developers offload what they would have to hold in their heads and keep their judgement for what only they can do. Tate takes the parallel further: task specifications are “a highlevel programming language” for a repeatable process. He then ties the two halves together. The Inquiry Framework “gives people license to change their minds more easily”, and the architecture “reduces the cost of an organization changing direction” because the reasons for decisions survive staff turnover [58:03–59:03]. Whether this scales to an enterprise “remains to be seen”.

9. Close (1:04:01–1:13:19). Tate reports that his wife said hearing about the work made her “less afraid” of AI, which he puts down to its augmenting a human collaboration rather than replacing a task. His summary: inquiry is an alternative to debate, not a replacement; it puts questions before answers; three lenses keep it usable; the framework is “an evolving experiment”, not doctrine; and “the humans remain responsible for framing participation interpretation and action”. Any one conversation is a moment in time: accumulating insight needs memory, provenance, operating principles, governance and human review, the subject of episode 22. Asked what more is needed to turn dialogue into sustained learning, Wladawsky-Berger says he does not know yet: “I want to see the evidence and I want to see the use case.”

Dynamic-capabilities reading

• digital-sensing/digital-scenario-planning — the framework is a method for interpreting an uncertain digital future before formulating strategy: a stable question, three competing lenses tested against evidence, the tensions named, and only then the CIO decision.
• digital-seizing/strategic-agility — Tate’s claim that inquiry lowers the cost of changing one’s mind, and that durable records lower the cost of an organization changing direction, is about accepting redirection and change.

Related in this wiki

• The keynote. Tate’s May 2026 keynote presents the same framework in brief: the debate experiment in 2024, the AI-consciousness origin, the three-step method (frame the question, examine competing interpretations, translate to CIO decisions) and the same first question. Small differences in the telling: the keynote has Tate and Wladawsky-Berger discussing an article; here Wladawsky-Berger was weighing a blog post on the topic. The keynote says the first series ran six structured questions over seven sessions; here the fundamental tier alone has four questions.
• Series. Episode 20 covers what happens to a conversation after it is recorded; episode 19 the editing story Wladawsky-Berger retells here; episode 22 the architecture.

Linked entities and concepts

• Entities: MIT Sloan CIO Symposium, Allan Tate, Irving Wladawsky-Berger.
• Concepts: dynamic-capabilities, warner-wager-process-model.
• Dangling (single-source mention, deferred): The Economist (a recent issue on AI consciousness, mentioned in passing).

Debates and supersession

• No outcome data. The framework’s value is argued from the hosts’ experience. The only measurement mentioned is about debates (few audience members change their mind), and no figures are given.
• Interested party. The symposium presents its own programme format on its own channel.

Caveats and source quality

• Transcript. YouTube auto-captions from the en-orig track, fetched with yt-dlp after the transcript panel failed to render. The video carries several AI-dubbed audio tracks; en-orig is the original English audio. Not ASR-cleaned at Acquire. Names are garbled (“Alan Tate”, “Irving Vadoski Ber”, “the economies” for The Economist). A model version number Tate cites is garbled and not recorded. Quotes fix names only.
• No visuals. Split-screen video call; no stills scan was run.
• Misspoken year. “2027 summer inquiry series” again means summer 2026.
• Recording date vs publication. Recorded 2 September 2026 (stated on air), published 15 September.

What was actually ingested

The full 1:13:19 episode, from auto-captions (~1,473 caption lines), read end to end.