Elisabeth Swan opened the session with a sentence she said she repeats often to the people she coaches: facts and data often fail to move hearts and minds.
The frustration the sentence describes is familiar to anyone who has tried to lead improvement work. A practitioner sees a problem clearly. The data is unambiguous. The case is solid. They present it to colleagues or to leadership expecting the obvious response, and the response doesn't come. The audience doesn't disagree exactly. They just don't act. Or they push back with objections that don't engage with the substance. Or they nod, agree it's a problem, and continue exactly as before.
The practitioner's natural response is to repeat the case more loudly, or to add more data, or to escalate to someone with more authority. None of it usually works. The issue isn't that the data is wrong. The issue is that data alone isn't what moves people, and the practitioner has been trying to win a contest in the wrong arena.
The session that followed was about why this happens — what the human brain actually does when it encounters information, how that processing diverges from what we assume, and what leaders can do to work with the brain's actual machinery rather than against it. Elisabeth drew on research from John Medina ("Brain Rules"), Yuri Hasson on neural coupling, Ethan Kross on inner self-talk, Ned Herrmann on brain wave patterns and creativity, and her own decades of consulting work in Lean transformations across healthcare, manufacturing, and nonprofit settings.
The material came directly from her new book, "Picture Yourself a Leader: Illustrated Micro-Lessons in Navigating Change," which had just launched. The book's structure — 50 short chapters, each a self-contained micro-lesson — reflects something the brain science itself argues for: that meaningful change happens through accumulated small insights rather than through single comprehensive transformations.
Elisabeth Swan has consulted in the business process performance industry for over 30 years. Her experience spans from helping local nonprofits expand their reach to guiding Fortune 100 companies through Lean transformations. She has trained and mentored thousands of people in improvement projects generating millions in savings. She has deep experience coaching problem solvers and facilitating leadership retreats, strategic planning sessions, process walks, and kaizen events.
Elisabeth is the co-designer and lead instructor for the Lean Six Sigma Leadership Course at the University of California, San Diego (UCSD). She is co-founder of Just-in-Time Café and co-host of the Just-in-Time Café podcast with Tracy O'Rourke. She co-wrote "The Problem Solver's Toolkit: A Surprisingly Simple Guide to Your Lean Six Sigma Journey," and her latest book is "Picture Yourself a Leader: Illustrated Micro-Lessons in Navigating Change."
Elisabeth opened her substantive material with a story she initially attributed to a project at Alberta Health Services, then realized partway through preparing the session that she might have first encountered it in Mark Graban's "Lean Hospitals." She let the misattribution stand because the story is real regardless of which hospital it happened at — and a similar version had recently been published about New York Health and Hospital Corporation.
The setup: a hospital was ordering and storing dozens of varieties of gloves with different SKUs, all of them similar enough that ordering caused confusion and overlap. The gloves had a three-year shelf life and a lot of them were being thrown out when they expired. A project lead saw the opportunity and put together an A3 making the case for consolidation.
The reaction wasn't what he expected. Colleagues pushed back. Doctors need different gloves for different procedures. The variety was there for clinical reasons. Was this really worth focusing on? The data was on the project lead's side, but the data wasn't moving anyone.
What he did next was the part of the story that mattered. He went and got one pair of each glove the hospital had on hand. He laid them out on a conference room table. People came in to look at them and immediately saw what the project lead had been trying to explain. The gloves weren't meaningfully different. The variety wasn't clinical. It was the cumulative product of years of independent ordering decisions that had never been examined together. The image of all the gloves on the table did in seconds what the A3 hadn't done in weeks.
He took the table on a road show. Different hospitals in the network. Same display. Same response. The project moved.
The New York Health and Hospital Corporation version, which Mark had forwarded to Elisabeth the morning of the webinar, showed what the consolidation looked like at scale. The system had stocked 20 varieties of rubber gloves in different colors and thicknesses. Their investigation reduced the options doctors could choose from to two. The negotiating leverage that came from consolidating 132,000 cases of annual orders dropped the price from $58 per case to $28 per case — a savings of approximately $4 million per year on gloves alone.
The story is about gloves. The lesson is about what made the case finally land. The data hadn't done it. The image had.
Elisabeth walked through the underlying mechanism, which she credited to John Medina's "Brain Rules."
When the brain reads text, it goes through a process. Each letter is first processed as a small picture. The brain then decodes the picture as a symbol — this is the letter A, this is R, this is E. The symbols get assembled into words. The words get assembled into meaning. The whole process operates at roughly 250 words per minute, regardless of how many years the reader has been reading. The sequence — picture, symbol, word, meaning — doesn't speed up with practice.
When the brain processes an image, it operates in 13 milliseconds. Roughly 60,000 times faster than text. The speed difference exists because human survival historically depended on rapid visual recognition. The ancestors who could spot the tiger in 13 milliseconds had descendants. The ancestors who took 250 words per minute to read about the tiger didn't.
The practical implication for leaders trying to communicate: the same content delivered as an image will register dramatically faster than the same content delivered as text, and the registration will reach parts of the brain that text doesn't. Research consistently shows that most human decisions are driven by emotion rather than by reasoned analysis. Images access the emotional layer. Text mostly doesn't.
Elisabeth illustrated the point with an example from Angela Duckworth's Character Lab newsletter — a piece called "Seeing Is Believing" about teaching children about climate change. The photograph that anchored the piece showed farmers in a growing region pollinating their crops by hand because no bees were left. The photo communicated the consequences of bee population collapse in a way that any amount of text about pollinator decline couldn't. The research finding the piece described: combining photos with information produces substantially greater appreciation for a subject than information alone.
The implication isn't that practitioners should reduce everything to images. The implication is that practitioners who don't have an image are missing the fastest and emotionally most resonant channel they could be using. The question worth asking before any communication that matters: what's the image?
Sometimes the image isn't available. The work is process-shaped, abstract, or otherwise hard to photograph. In those cases, Elisabeth argued, the second-best channel is a story.
Her example was a project at a small child care nonprofit on Cape Cod. The team lead — the office manager — was trying to reduce expenses by $2,000 per month. She had noticed that the centers had dishwashers and dishes but were using paper plates and disposable utensils. People were ordering their own soap and cleaners individually rather than buying in bulk. The data was clearly on her side.
The pushback was familiar. People didn't like the smell of the new cleaner. They thought it irritated their skin. Why was this even being prioritized? How much could plates and soap really cost?
The team lead went to the CEO and asked what to do. The CEO said: I back you, tell me what you need. The team lead thought about that and decided it wasn't right. She didn't want to fight with the teachers. The teachers weren't the enemy. The savings weren't the point.
So she reframed. At the next meeting, she didn't talk about expenses or the $2,000 target. She told the story of what the savings could enable. With the money saved across the organization, they could potentially open another daycare center — reach more kids, serve more families, do more of what the organization existed to do.
The room turned over. The teachers started offering things voluntarily. "I have this phone, I don't actually need it." "We have memory stick subscriptions we're renting that nobody uses." The expense reductions came at them rather than from them, because the story had connected the work back to why anyone was doing it in the first place. They hit the goal in less than a month. They got the new facility. Teachers received bonuses for the first time. The story did what the data hadn't.
The mechanism Elisabeth named for what stories do is called neural coupling. The work is associated with Yuri Hasson, a researcher whose TED talk and writing she pointed audience members to.
When a person tells a story about an experience they actually had, the parts of their brain associated with the emotions they felt during the experience light up again. When a listener hears the story, the same parts of their brain light up — not generically, but specifically the parts that correspond to the speaker's emotional state. Fear in the teller produces fear in the listener. Excitement in the teller produces excitement in the listener. The listener's brain is, in a real neurological sense, mirroring the teller's.
The practical implication: stories don't just convey information. They transport listeners into the teller's experience. The listener doesn't just hear about what happened. They have something like a secondary version of the experience itself.
Elisabeth said this is what she's referring to when workshop participants tell her, weeks later, that the thing they remember most clearly is whichever story she told. The story registered differently from the analytical content because the neural coupling produced a quasi-experiential memory that the analytical content couldn't.
She offered an example from the hospital systems she's working with currently. A common project category is reducing lost patient belongings — dentures, hearing aids, and similar items. The financial case is usually straightforward: replacement costs run over $2,000 per item, the volume adds up, the savings are real. The financial case rarely moves the work as much as expected.
Recently a project lead reframed it. She told the story of a specific patient — a gentleman recovering from a stroke whose hearing aid was lost during his hospital stay. The replacement took three months. During those three months, his rehab stalled because the rehab work depended on his ability to hear instructions. He was a stroke patient who couldn't progress for a quarter of a year because someone couldn't find his hearing aid.
The story did the work the dollar figures hadn't. The team understood what was actually at stake in a way the cost calculations couldn't reach.
Elisabeth offered a practical technique for getting at the why behind any improvement effort. Two questions she's heard colleagues use repeatedly:
"For the sake of what?" A friend of hers asks this whenever Elisabeth describes a piece of work she's doing. It's a quiet way of asking: what's the larger purpose this serves?
"Why should I care?" Another colleague's variant. Functionally equivalent. It surfaces the connection between the work and the audience's actual interests.
Either question, asked of oneself before presenting work to others, tends to produce the story underneath the data. The story is what's needed for the data to land. Without it, the data is just information that the audience can't connect to.
Elisabeth gave Mark a small additional plug here — her view that his "Measures of Success" methodology of plotting metrics over time tells a story visually, even when the metric itself is abstract. A simple time chart with before-and-after data does in one image what a paragraph of narrative struggles to do: it shows the past, the intervention, and the result, all at once.
The session's second major thread was about what happens during conversations — specifically, what happens in the listener's brain while the speaker is talking.
Elisabeth quoted a line from her colleague John Guaspari: "The opposite of talking isn't listening. It's waiting to talk." The line names something most people recognize once they hear it. The listener appears to be listening but is actually rehearsing their response, evaluating what's being said against their own existing views, formulating their next contribution, or otherwise not actually receiving what the speaker is saying.
The mechanism underneath this turns out to be biological. Humans speak at roughly 150 words per minute. Humans understand speech at 400 to 800 words per minute. The gap is enormous. The listener's brain has, on average, more than twice the processing capacity available than the incoming speech requires. The question is what the brain does with the spare capacity.
The default, for most people, is to use the capacity to do something other than listen. Formulating responses. Pattern-matching to prior experiences. Wandering. The listener's experience may feel attentive, but the actual cognitive work being done isn't all attention.
Elisabeth's story about the consulting firm she joined early in her career illustrated one adaptation. The senior consultants in the firm had developed a similar verbal tic — a stuttered repetition of "and, and, and" before each new point. She eventually realized they were using it as a barrier. The stutter created enough verbal forward motion that no one could interrupt. The speaker held the floor by removing the gaps that others would otherwise have filled. The tactic worked. It also meant nobody was really listening to anyone.
The contrast she drew was with her family of storytellers growing up. In that culture, if you were telling a story and someone said "oh yeah," your turn was effectively over. Your older sister had taken the floor. You had to be quick or compelling enough to hold attention against the constant low-grade competition for the conversation.
Elisabeth ran an interactive segment asking the audience how they overcome the waiting-to-talk pattern. The responses came in quickly and ranged across a useful spectrum:
Biting your tongue. Taking notes while you wait. Taking a drink. Holding the expectation that you'll need to reiterate what you heard, which forces you to actually take it in. The acronym WAIT — Why Am I Talking — written on a Post-it or held in mind. Eye contact. Active listening. Trying not to forget what you wanted to say while you focus on listening. Abiding time. Staying quiet. Observing. Breathing. Pausing.
Mark made a distinction worth noting: there's a difference between waiting quietly to talk (which is at least polite) and actually listening. Quiet waiting is better than interrupting, but it isn't the same as receiving what the speaker is saying. The strategies that work are the ones that direct the spare cognitive capacity toward the speaker rather than toward your own internal monologue.
Katie Anderson contributed in the chat: she recognized she had a problem with this — "I'm a teller, I have to stop and listen." The acknowledgment matters because the first step in shifting the pattern is noticing the pattern in oneself.
Elisabeth's own preferred strategy is writing. She tells the people she's listening to that she's writing down what they're saying. Two effects. First, it directs her cognitive capacity toward capturing their words rather than toward composing her own. Second, it signals to the speaker that she's actually listening, which changes the speaker's experience of the conversation and tends to make them more open. The risk she acknowledged: some people find that writing breaks their presence in the moment. The technique that works depends on the person.
The third processing speed Elisabeth introduced was the speed at which humans speak to themselves internally. Roughly 4,000 words per minute. Substantially faster than either spoken or understood external speech. Most of the words a person processes in a day are addressed to themselves.
She credited Ethan Kross's "Chatter" for the work on inner self-talk. The relevant concept Kross develops is the inner naysayer — the voice that runs at 4,000 words per minute talking the person out of things they were considering doing.
The late mentor Ben Zander, in his book "The Genie Within," called this voice "the chattering monkeys." The monkeys have a million reasons not to try something, not to speak up, not to take the risk. They run faster than any external conversation could counter them. By the time someone else has finished saying "you should go for it," the monkeys have produced 500 reasons not to.
The implication for leaders: if you want people to take on new challenges, suggest new ideas, or break out of comfortable patterns, you're competing with their inner monologue, and you're at a 25-to-1 speed disadvantage. The external encouragement matters, but it has to find some traction against an internal voice that has many more words available to use.
Elisabeth shared several strategies from her book's "wisdom of the crowd" section — techniques contributed by various practitioners she interviewed.
List your accomplishments from doing things you almost talked yourself out of. When you look back, you almost never regret the brave choice. The recall of past instances where the chattering monkeys were wrong creates a counterweight to the current monkeys' arguments.
Reframe stress as excitement. Ruth Archer's contribution. The body produces the same chemicals for stress and excitement — elevated heart rate, heightened alertness, increased adrenaline. The interpretation is what differs. Reinterpreting the stress response as excitement converts a paralyzing signal into energy you can use.
Use awful-eyes thinking. Mike Osterling's contribution. Ask: what's the worst that could actually happen? In most cases, the worst is manageable. The chattering monkeys tend to inflate the consequences of action. Naming the actual worst case shrinks it.
Get an accountability partner. Someone you can call to talk through the decision. The technique works because it gets the conversation out of your head and into a different conversational mode — one where you have to articulate the chattering monkeys' arguments out loud, which often reveals how weak they actually are.
The session's final substantive thread was about creativity and ideation. Elisabeth asked the audience to share, in the chat, where they were or what they were doing when they got their best ideas.
The responses came in a flood and showed a consistent pattern: showering, walking, driving (especially driving in silence), running, gardening, doing dishes, cooking, ironing, meditating, sitting outdoors, drifting off to sleep, just after waking up, on a bike ride, in nature, while massaging clients (from a practitioner), while playing with a child.
What conspicuously didn't appear in the responses: in my cubicle at work. In a conference room. In a meeting. In a brainstorming session.
The pattern is universal enough that Elisabeth said she's been asking this question for over 30 years (a practice she picked up from another mentor, Mitch Ditkoff, who wrote "Storytelling at Work") and has never gotten "in a meeting" as an answer. The conventional venues for organized ideation — the conference room, the whiteboard, the structured brainstorming session — aren't where the actual ideas come from.
The brain science underneath this comes from Ned Herrmann's work on brain wave patterns. Four relevant categories:
Beta waves are produced during active engagement — conversation, debate, problem-solving with others, presentations. The brain is fully engaged with external content. It feels productive and often is, but it's not the state that produces breakthrough ideas.
Alpha waves are produced during breaks and during meditation. Slower than beta. Less externally focused.
Theta waves are produced during what Elisabeth called autopilot activities — showering, driving on a familiar route, walking the dog, washing dishes, knitting while talking. The conscious brain is occupied with something simple and routine, which frees other parts of the brain to do the integrative, associative, pattern-finding work that produces new ideas. Theta waves are also produced when drifting off to sleep and just after waking up, which is why so many people report ideas arriving in those moments.
Delta waves are produced during the deepest stages of sleep. Mostly not relevant for ideation, though some practitioners report problem-solving happening during dreams.
The implication: the optimal brain state for generating new ideas is theta, which is largely incompatible with the standard organizational venues for ideation. Conference rooms produce beta. Showers produce theta. Organizations that insist on doing all their ideation in conference rooms are systematically using the wrong brain state for the work they're trying to do.
Elisabeth mentioned the standard brainstorming techniques — reversal exercises, analogies from different industries — that she used to teach. They produce some interesting output. They tend to produce less than experienced facilitators hope, because the conference room environment fights the underlying neurology. The participants are in beta. The work requires theta. The state mismatch limits what's possible.
The practical question is what to do with this knowledge. Elisabeth offered two categories of response.
Capture mechanisms for personal ideation. Keep a notepad by the bed. Use Google Keep or a similar app that syncs across devices. Text yourself messages with reminders, ideas, photos, links. Dictate into your phone when you can't write. Photograph things that prompt ideas. The point is that ideas arrive when they arrive, and the practitioner who doesn't have a fast capture mechanism loses most of them. Memory isn't a steel trap for anyone.
Facilitation techniques that design for theta rather than against it. Spread workshops across two days so participants have an overnight period to engage in autopilot activities and let ideas surface. Send people out for walks between sessions — what Elisabeth referenced as the peripatetic tradition Aristotle ran (his school was named for the practice of walking while talking). Provide tactile objects — fidget spinners, slinkies, Play-Doh — for participants to manipulate during sessions. The objects simulate autopilot activity at small scale, freeing other parts of the brain to engage with the content. The objects need to be silent; noise-making objects irritate everyone. Use brain-writing techniques — give participants the "how can we" question and send them away with it for a period, then reconvene.
Mark suggested an additional cue worth noting: driving in silence rather than with the radio on. The radio fills the spare cognitive capacity that would otherwise drift into theta-state association. Silent driving is one of the highest-yielding autopilot activities for generating ideas. Elisabeth confirmed this from her own practice — when she's stuck on something, a bike ride often does what hours at the desk can't.
The honest assessment Elisabeth offered: this requires forethought. Some of it requires investing in physical materials. Some of it requires designing meetings differently than the default. The investment pays back in the quality of ideation. The default — long meetings in conference rooms producing modest output — is what happens when the design ignores the underlying neurology.
The brain science Elisabeth walked through is fundamentally about how humans think, communicate, and generate ideas. None of it is software. The shift Elisabeth was advocating — toward visual communication, storytelling, genuine listening, designing for theta-state ideation — is about how leaders behave, not about what tools they use.
Where infrastructure connects is in two places.
The first is making the products of brain-aware practice visible across the organization. The hospital glove project's success depended on the visual display of all the gloves on a table. But the lesson from that project — that a visible aggregation of items can reveal patterns invisible in the data — only spreads if other improvement work in other parts of the organization can access and adapt it. The team in another hospital facing a parallel SKU rationalization problem benefits from being able to see how the glove project was framed, what changed people's minds, and how the savings accrued. Infrastructure that holds improvement work alongside the artifacts that made the work successful supports the spread of brain-aware practice.
The second is supporting the asynchronous ideation Elisabeth's brain science argues for. The conference room produces beta. The shower produces theta. Ideas arrive between meetings, not during them. Infrastructure that lets practitioners capture ideas when they actually arrive — from their phone in the parking lot, from their tablet during the morning walk, from their laptop at 3 AM — preserves the ideas that would otherwise be lost. The team's collective intelligence isn't what happens in the conference room. It's what gets captured from everywhere else and aggregated into the shared record.
The brain-writing facilitation technique Elisabeth described — give participants the question, send them away, reconvene — also benefits from infrastructure that holds the question and the responses. The participants thinking about the question while walking the dog need somewhere to put the thought when it arrives. A shared workspace that holds the question and accepts asynchronous contributions makes the technique operational rather than dependent on participants emailing things to a facilitator who then synthesizes by hand.
The visibility of patterns across many improvements also supports the visual-display lesson Elisabeth drew from the glove project. The pattern that's invisible in one project's data becomes visible when 50 similar projects across the organization are viewable together. The "lay all the gloves on the table" technique generalizes when the organization has infrastructure that lets it metaphorically lay all the related work on the same table at the same time.
None of this changes what Elisabeth was teaching. The brain processes images 60,000 times faster than text. Neural coupling makes storytelling fundamentally different from explanation. Inner self-talk runs at 4,000 words per minute and the chattering monkeys win most arguments by sheer volume. Theta-state activities produce the ideas that beta-state conference rooms can't. The implications for leadership are what they are. What infrastructure does is preserve the artifacts of brain-aware practice across the organization so they can spread, and create asynchronous capture mechanisms so the ideas that arrive in the shower don't vanish before anyone can use them.
Why do facts and data often fail to change minds? Because the brain doesn't process information through a purely rational channel. Most decisions are driven by emotion. Data registers in cognitive systems that don't directly engage the emotional layer where decisions actually get made. Leaders trying to persuade with data alone are working in the wrong arena. The complementary channels — visual communication and storytelling — engage the emotional layer in ways that data alone cannot.
Why is visual processing so much faster than text processing? The brain processes text through a sequence — picture, symbol, word, meaning — that operates at roughly 250 words per minute regardless of how skilled the reader is. The brain processes images in roughly 13 milliseconds — about 60,000 times faster. The speed difference exists because human survival historically depended on rapid visual recognition (the tiger in the grass). The image channel was evolutionarily prioritized in ways the text channel never was.
What is neural coupling? The phenomenon in which a listener's brain mirrors the speaker's brain when the speaker tells a story about an experience they actually had. The parts of the speaker's brain associated with the emotions they felt during the experience light up again as they retell it. The same parts of the listener's brain light up as they hear it. The listener doesn't just receive information about the experience. They have something like a secondary version of the experience itself. This is why stories register differently from analytical content — they produce a quasi-experiential memory that pure information can't.
What does "for the sake of what?" do? It's a question Elisabeth's colleague asks her about whatever work she describes. It surfaces the larger purpose underneath the immediate task. The variant "why should I care?" does the same work from the audience's perspective. Asking either question of oneself before presenting work to others tends to produce the story underneath the data — which is what's needed for the data to actually land.
Why does "the opposite of talking isn't listening, it's waiting to talk"? Because humans speak at roughly 150 words per minute but understand speech at 400 to 800 words per minute. The listener's brain has substantial spare capacity that has to go somewhere. The default is for the spare capacity to do something other than listen — rehearsing responses, pattern-matching to prior experiences, wandering. The listener appears attentive but isn't actually receiving most of what's being said. The discipline of listening is the discipline of directing the spare capacity toward the speaker rather than toward one's own internal monologue.
What strategies actually work for genuine listening? The audience response in the session covered a range: biting your tongue, taking notes, holding the expectation that you'll need to reiterate what you heard, the WAIT acronym (Why Am I Talking) as a Post-it or mental reminder, eye contact, drinking water, breathing, pausing. Elisabeth's own preference is writing down what people are saying. The mechanism that works varies by person. The common element is that the spare cognitive capacity gets directed at the speaker rather than at one's own next contribution.
What are the "chattering monkeys"? Ben Zander's term (from "The Genie Within") for the inner voice that runs at roughly 4,000 words per minute talking a person out of things they were considering doing. The voice has a million reasons not to try something, not to speak up, not to take the risk. Ethan Kross's book "Chatter" covers the same phenomenon. The 4,000-words-per-minute speed is far faster than any external encouragement can match, which is why getting unstuck often requires getting the conversation out of your head and into an external mode — an accountability partner, a written list, a reframe of the consequences.
How can you counter the inner naysayer? Several strategies Elisabeth shared from her book's "wisdom of the crowd" section: list past accomplishments from doing things you almost talked yourself out of (the recall of past success creates a counterweight); reframe stress as excitement, since the body produces the same chemicals for both (Ruth Archer's contribution); use "awful-eyes" thinking to ask what's the worst that could actually happen, which tends to shrink the inflated consequences (Mike Osterling's contribution); and get an accountability partner who can hear the chattering monkeys' arguments out loud, where they tend to sound weaker than they did internally.
What are theta waves and why do they matter for ideation? Brain wave patterns associated with autopilot activities — showering, driving, walking, washing dishes, knitting while talking. The conscious brain is occupied with something simple and routine, which frees other parts of the brain to do the integrative, associative, pattern-finding work that produces new ideas. Theta waves are also produced when drifting off to sleep and just after waking up, which is why so many people report ideas arriving in those moments. The implication for leaders: ideation needs theta, but the standard organizational venues for ideation (conference rooms, structured brainstorming) produce beta. The state mismatch limits what's possible in those venues.
Why don't conference room brainstorming sessions produce the best ideas? Because the brain state required for active conversation and structured exercises is beta, and beta isn't the state that produces breakthrough ideas. The cliché answers about where people get their best ideas — the shower, the drive, the walk — aren't sentimental. They reflect the underlying neurology. Organizations that limit their ideation to conference rooms are systematically using the wrong brain state for the work.
What facilitation techniques work better? Spread workshops across two days so participants have an overnight period for autopilot activities. Send people out for walks between sessions (the peripatetic tradition Aristotle's school ran on). Provide quiet tactile objects — fidget spinners, slinkies, Play-Doh — that simulate autopilot activity at small scale during sessions. Use brain-writing techniques: give participants the "how can we" question and send them away with it, then reconvene to share what surfaced. The common theme is designing meetings that let participants spend time outside the meeting in theta-state activities, then capturing what they generate.
How do you capture ideas that arrive in theta state? Whatever capture mechanism works for the person. Notepad by the bed for the middle-of-the-night ideas. Google Keep or similar sync-across-devices apps. Text yourself. Dictate into your phone. Photograph things that prompt ideas. The point is that ideas arrive when they arrive, and the practitioner without a fast capture mechanism loses most of them. Memory isn't a steel trap for anyone.
How do you justify slowing down for ideation in a short-staffed organization? Elisabeth's recommendation: don't try to justify it as time at work. Instead, give people the "how can we" question to take with them, and let them engage with it during their normal autopilot activities outside work — the walk, the commute, the dishes. Reconvene to share what surfaced. The technique doesn't take extra time at work because the thinking happens during activities people were doing anyway.
What's the misconception about leadership and brain science? Elisabeth's observation: leaders often assume their value is in adding things — offering wisdom, contributing ideas, demonstrating expertise. The shift that happens as leaders advance is that value moves from adding to asking. The questions you ask become more valuable than the answers you provide. Edgar Schein's "humble inquiry" framework names this shift. The misconception some leaders carry is that asking more and telling less is somehow being meek, which Schein's military examples directly contradict. The shift from adding to stimulating others is one of the major transitions in leadership development, and many leaders don't see it as a transition that should happen until someone points it out.
.svg)
Copyright © 2026
Privacy Policy