"What happens when the thing you're doing stops being enough — and the system around you doesn't notice?"

June 2026 brought discussions about what it costs to keep going inside structures that weren't built to see what you're actually doing.

Across sessions on change, conflict, the future, AI, money, knowledge management, facilitation, discernment, neurodiversity, content and design, mindfulness, career transitions, and the nature of sensemaking itself, members kept arriving at the same quiet friction: the gap between knowing something and being able to act on it. Between doing work that matters and having it be recognized as work. Between understanding the system you're in and being able to change it.

What surprised me most this month was how often the answer wasn't to push harder. It was to get more honest about where the effort was actually going.

In our Mindfulness & Modeling session, a member described the feeling of being stuck between two modes: hyperfocused and paralyzed, brilliant under pressure and unable to start an email on a Tuesday. They'd spent years thinking these were character flaws. What came out in the conversation was something more interesting: that both modes were protecting the same thing. A very high standard of quality. And that the standard, not the laziness, was the thing making it impossible to begin.

Of course. Of course that's what it was.

But June kept asking a harder question: what do you do when the system you're operating inside doesn't just fail to recognize your standard — it actively measures something else?

• What happens when your expertise is invisible until the problem it was preventing finally arrives?
• When the work of getting oriented, building comprehension, understanding the room — turns out to be the work, and you've just outsourced it?
• When discernment can't be templated, and you have to make a call right now with the information you have?

Many of the discussions at the Sensemakers Club in June 2026 pointed toward the same realization:

Maybe the gap between knowing and doing isn't a motivation problem. Maybe it's an architecture problem. And maybe the place to start is figuring out what the structure is actually designed to hold.

Below is a recap of the meta themes that we saw across our discussion sessions in June 2026. If you are interested in our upcoming sessions, check out our discussion group list.

#1 Knowing and Doing Are Not the Same Loop

The prompt for Mindfulness & Modeling was about bridging the gap between understanding something intellectually and embodying it practically and what the session surfaced was that this gap shows up differently for everyone, but it shows up for everyone.

Some members move by thinking first and doing later. Others discover what they know by doing it. Several pushed back on the idea that knowing has to come first at all, that sometimes you just go, and the understanding gets built on the way.

What united the conversation was a recognition that the two aren't sequential. They're circular. You stop improving in one when you stop doing the other. And the dread, for most people, doesn't live inside the doing. It lives at the threshold.

This same loop appeared in Career Transitions, where members talked about the gap between knowing they need to reposition and actually doing it. In AI Field Notes, where the question was what you lose when you hand the comprehension work to a machine. In the Analog Leap, where the point of making marks on paper wasn't the output but the thinking that happened during. The knowing-doing gap was everywhere in June — not as a problem to solve, but as a thing to keep noticing.

"You can do one side or the other, but you kind of potentially reach a ceiling. You can't keep going with it unless you're doing both."-Overheard in Mindfulness & Modeling

#2 What Gets Lost When You Optimize for Speed

Multiple sessions circled the hidden cost of moving fast. In AI Field Notes, members talked about outsourcing tasks to AI and found themselves naming what those tasks had actually been doing. The noun harvesting, the slow read-through, the document setup that seemed like grunt work: that was the part where your brain figured out what it was dealing with. When you skip it, the strategic thinking doesn't get better. It gets faster, but it's working with less.

One member described building something with Claude Code and not realizing how bad the idea was until they were deep into the prototype. The tool had kept affirming the direction. Nobody had pushed back.

The same pattern emerged in Making Sense of the Future, but from a different angle. Members talked about mailmen and beat cops, jobs restructured for efficiency and coverage, losing the relational and observational layer that was never in the job description. The mailman who knew everyone on the street and was the glue of the neighborhood. The beat cop who used to walk and now drives past. The efficiency gain was real. The loss was real and unmeasured. When you optimize for what's visible, the invisible things don't disappear. They just stop being tended.

"The future is already here, it's just unevenly distributed. But if you try to speed up the thing where the value lives, you just cut down the value." -Overheard in Making Sense of the Future

#3 Invisible Work and Who Gets to Name It

This was maybe the most consistent through-line of the month. Work that prevents problems doesn't look like work until the problem shows up. Knowledge management, governance, facilitation, information architecture, documentation, stewardship are all fields where people don't notice what you do until it's broken or missing. And by then, the person who knew where everything lived has already left, or the taxonomy has drifted, or the new system has no conventions and nobody is sure who to ask.

Career Transitions held a version of this too. The roles that make things clear and accessible end up making themselves look easy — which is the whole point, and also the problem.

The clarity conceals the effort.

Several sessions returned to the question of how you name and defend work that succeeds by being invisible. The Knowledge Management session noted that organizations don't value it until there's a crisis, and by then they're looking for someone to blame rather than someone who could have prevented it. That's not cynicism. That's just the accounting.

"We make things look easy. That's our job. And the problem is it makes people think it's easy."-Overheard in Career Transitions

#4 Systems That Were Not Designed to Hold Nuance

It emerged across values in tech, career transitions, knowledge management, neurodiversity, facilitation, and AI. The common shape: you are doing humane work inside a structure that measures something else entirely.

• Companies running layoffs every six months while reporting financial health.
• AI tools that flatten minority voices and confidently flatten nuance in the same breath.
• Governance structures that nobody owns.
• Roles that haven't been redefined since they were classified as overhead in the early twentieth century.

One member said that “values feel like a luxury when survival is on the table” and then paused, because they'd just named the thing exactly. It's not that they stopped having values. It's that the structure made them impossible to act on.

The Making Sense of Your Values in Tech session held this tension directly. Members shared situations where they'd had to set aside what they knew was right in order to keep a job, keep peace with a client, keep the lights on. Not because they'd given up. But because the hierarchy of needs doesn't start with values. And the conversation that followed wasn't about what people should have done. It was about how rare it is to be in a system that makes it possible to do the right thing, and what it's worth to find one.

"I don't know if I have the ability to care as much about values at this juncture. I'd love to be able to, but I don't know that I can."-Overheard in Making Sense of Your Values in Tech

#5 Discernment Can't Be Templated

The IA discussion this month was structured as a choose-your-own-adventure: a real information architecture scenario, moving through decision points as a group, voting on which way to go, then discovering what both paths would have led to. What the exercise surfaced, over and over, was that the right answer was always contextual. It depended on the culture, the timing, the personalities, the relationships, the history of the organization, and even what you had for breakfast that day.

That same humility ran through Making Sense of Change, Making Sense of Other Humans, and the Facilitation session.

• How do you read a room you just walked into?
• How do you hold your ground without becoming rigid?
• When do you speak and when do you ask a question instead?

Members kept landing on the same uncomfortable truth: there is no formula.

What you can do is keep showing up to situations that require judgment and get better at noticing what you're doing.

"Discernment means you have to take every part of every single thing into account. It really is down to that level of what is your energy right now?"-Overheard in Discernment: The Ultimate IA Skill

In July our Information Architecture discussion (July 10 at 2 PM ET, members only) will be about Bad Models and what we can learn from them. Not what went wrong, but what the wrongness teaches. Bring your bad model stories. I'll bring mine. Hope to see you there.

— Abby Covert, Chief Sensemaker