This interview is with Carol Grojean PhD, Consultant, Grojean Consulting.
Carol, as a Consultant in professional training & coaching and a social systems scientist, how do you introduce your work and expertise to Connectively.us readers?
I study the human system of leadership: the layer of an organization that was always treated as soft and unmeasurable. This includes trust, alignment, and whether a team genuinely thinks and moves as one under pressure. My work is to make that layer visible and then build it, the way a performance engineer measures and engineers a digital system—same rigor, one layer down.
What makes this urgent now is AI. When intelligence becomes abundant and answers are cheap, the scarce advantage is no longer intelligence; it is coherence. And AI is an amplifier: it scales a team’s incoherence exactly as fast as it scales its output. So the decisive capability of the next decade is not how smart your people are; it is whether they can think together.
I come at this from an unusual intersection. I spent two decades leading billion-dollar transformations at Microsoft, then more than a decade studying how human beings actually change, across neuroscience, initiation, and wisdom traditions on five continents. Most people in this space have the science or the human depth; I work with both, and now, through AI-powered social neurotechnology, I have the data. That became The Coherence Method: a way to measure a team’s coherence and then engineer it inside the work they already do.
I write about all of this in my essay collection on LinkedIn https://www.linkedin.com/in/carolgrojean/recent-activity/articles/
Looking back on 22 years leading transformation at Microsoft and your PhD in Transformative Social Change, what experiences most shaped your path into leadership architecture and organizational performance?
Two things shaped it—one professional and one personal—and they turned out to be the same.
Professionally, I spent those years watching a pattern I could not explain with the tools I had. I was leading billion-dollar transformations inside some of the most capable organizations in the world, full of brilliant people with the best data and strategy, and they still struggled to align, decide, and execute. The constraint was never a shortage of intelligence. Something underneath it was not holding.
Personally, I was living the same fracture. By every external measure I was thriving, and underneath I was running on empty—performing at the highest level while the person inside was quietly starving. That gap between the visible self and the real one is the same gap I now measure in teams.
So I left. I spent more than a decade studying how human beings actually change, across the initiation and wisdom traditions of cultures on five continents. What I learned was that durable change was never about information. It requires structured transition, and modern organizations had stripped those structures out.
When Microsoft brought me back as its first cultural engineer, embedded in Cloud and Quantum engineering, I saw the whole pattern. The strategy was sophisticated. The human conditions required to use it were not. Leaders were moving too fast, their nervous systems were too hijacked to think clearly, and the organization was fragmenting underneath its own speed.
That pulled me deep into neuroscience and human potential. I trained in the neuroscience of consciousness and altered states, and my work on human performance led Steven Kotler to bring me into the Flow Research Collective, where I spent two years coaching CEOs and senior teams on the neuroscience of flow. I left Microsoft for the last time to go all in on it.
That was the missing piece: the science that lets you take the state a person or a team is actually in—something everyone had treated as intangible—and measure it, work with it, and change it. Neuroscience turned the human system from a metaphor into something you can engineer, and that is what The Coherence Method is built on.
From that systems lens, what is one concrete practice you use to detect and rebuild attunement in hybrid teams during a single meeting?
Here is one technique I use in almost every session, and it works because it is based on physiology, not procedures.
To detect attunement, stop focusing on the content and pay attention to where the real conversation is taking place.
In a hybrid meeting, the clearest sign is when the honest exchange leaves the room: people go quiet on camera and start chatting in the chat, in private messages, or in the debrief afterward. The meeting can seem perfectly coordinated, with no one disagreeing, all while the actual discussion moves to a place you cannot see. That movement is your signal. The instant it happens, the team has stopped co-regulating. The disagreement has not gone away; it has simply left the room, where you can no longer work with it.
To rebuild it in the same meeting, name what you are seeing, then work on the condition underneath before you return to the content. I will pause and say plainly, “I think the real conversation is happening somewhere other than here.” Then, instead of forcing it back into the open, I ask the more useful question: “If that is true, what would have to change in this room for us to have it here?” Because the conversation is already happening. The issue is never that it is not. The issue is what is preventing it from happening in the open, and it is almost always one of a few things:
- psychological safety
- trust
- a shared reality that has quietly fractured
- a conflict no one wants to name
That question does two things at once. It settles the group toward a shared nervous-system state, and it surfaces the real condition to work on. Attunement is not restored through better facilitation. It is restored the moment the room becomes safe enough that the real conversation no longer needs to leave it.
This is exactly what our synchrony data captures automatically. However, you do not need technology to notice it. You just need to be willing to observe.
Staying with measurement, when you bring AI-powered social neurotechnology into a team, which leading signals in the first 30 days tell you the system is improving?
The signals that matter most in the first 30 days are not at the team level yet; they are at the individual level, and that surprises people.
A team is a shared nervous system, and it can only be as regulated as the people in it. So the earliest signals we watch are physiological and individual: heart-rate variability, sleep, recovery, movement, and nutrition. These are not wellness metrics; they measure whether a leader’s system has come out of chronic survival enough to think clearly, stay present, and remain in a hard conversation without bracing. When HRV rises, sleep deepens, and recovery steadies, that is the first real evidence the system is changing.
As that individual floor stabilizes, the team signals begin to appear. Heart-rhythm co-regulation across members starts, because synchrony is involuntary and moves before behavior. Attention redistributes: interruptions drop, and quieter voices are followed instead of talked over. And, counterintuitively, the team becomes more honest, not smoother. The disagreement that had been leaving the room comes back into it, which is the clearest sign trust is rebuilding.
Underneath all of it, the gap between what a team believes about itself and what its physiology shows begins to narrow. That gap closing is the leading indicator of the performance that shows up months later. But it starts with the individual. You cannot read a team’s coherence off people whose own systems are still in survival.
https://carolgrojean.com/coherencemethod/
Moving into your Coherence Method (Capacity, Orientation, Activation, Ceremony, Integration), what is the first action you take to correct the most common sequencing mistake you encounter?
The most common mistake in sequencing is that everyone wants to start in the middle. Leaders approach me wanting Activation — new behaviors, redesigned meetings, better decisions — or they seek the transformation of Ceremony, the visible breakthrough. Almost no one wants to begin with Capacity, because stabilizing the nervous system feels slow and gentle compared to urgent problems. However, the five phases are not a menu; they are a sequence. Each phase makes the next one possible. If you try to change behavior in a system still in survival mode, the change will not hold when the pressure returns.
So the first step I take is to refuse to start where they want. I show them why and make the cost of skipping a phase clear. I outline the chronic load the team is already managing and provide data to help the leader see that their people are functioning in survival mode and that no new behavior, structure, or strategy will last under those conditions. The urge to rush ahead often stems from the fear that the real problem is too daunting to tackle. Once a leader realizes the unstable ground they want to build on, they stop asking to skip it. We then begin where the work truly starts: getting the system regulated enough to support everything that follows.
Drawing on your agile and program management background, how do you align PM, Engineering, and Design around a shared reality when strategic complexity and incentives pull them apart?
This is where my two backgrounds meet, because it is both a structural problem and a human one, and most teams only treat the structural half.
Start with the honest diagnosis. When PM, Engineering, and Design pull apart, it is rarely a communication failure. Each function is internally coherent and optimizing for a different thing: PM for scope and time, Engineering for technical integrity and for what it will cost to maintain, Design for the user’s experience. Each one carries a private version of reality it has learned not to say out loud, and misaligned incentives reward exactly that. What looks like conflict is unsurfaced divergence.
So the first move is not to align them. It is to make the divergence visible. I get each function to say plainly what they are actually optimizing for, and where they privately believe this plan will break. You cannot build a shared reality on performative agreement, and you cannot work a gap you cannot see. Almost always, the moment the three real versions are on the table, people realize they have been solving three different problems while believing they were solving one.
Then you deal with the incentives, because no alignment conversation survives contact with a quarter that pays the three functions to want different outcomes. Move the tradeoff decisions to the right level, make them once, together, with clear decision rights, so they are not relitigated in every sprint by whoever is most senior in the room that day.
I would also correct the misconception underlying much of this. Agile was never about going faster. It is about discipline and commitment in smaller chunks, with more frequent checkpoints, so reality gets re-examined before too much is built on a wrong assumption. Faster was never the goal, and treating it as the goal is what produces the largest mistakes. When teams hear agile as “move faster,” they skip the very checkpoints where shared reality is meant to be rebuilt, and the functions drift apart between sprints instead of realigning inside them. Used well, that cadence keeps a shared reality current. Used as a speed mandate, it does the opposite.
Shared reality is not a document everyone signs. It is the state where the tradeoffs are visible, the incentive conflicts are named honestly, and three functions are finally solving the same problem instead of defending three of their own.
At enterprise scale—cloud migrations, AI adoption, or supply-chain redesign—what smallest unit of change do you start with to unlock system-wide performance?
The instinct at a large organization is to begin with a big approach because the problem is significant. Change the processes, switch the technology, redesign the organizational structure. However, when major changes are imposed on an already strained system, they lead to one of two outcomes. At best, they further exhaust and stress the system. At worst, they create a pattern where the organization treats every transformation as background noise—something to endure and ignore. In either case, you end up wasting considerable energy pushing people further from the state they need to be in for true change.
The smallest unit of change that can actually drive performance across the system is the unity of the leadership team guiding it. Sometimes, it’s even smaller: the mindset of the individual leader at the center.
This is why it serves as the critical leverage point, not merely a simple view. An organization functions like a nervous system, co-regulating around whoever holds power. The entire organization, consisting of thousands of people, looks to the small group at the top, whether that group is united or divided, stable or reactive. A cloud migration, adopting AI, or redesigning a supply chain — none of these fail primarily due to technical issues. They fail because the people in charge are moving too quickly, are not aligned on the actual problems they need to solve, and are overwhelmed by the change itself. The technology plan is rarely the main constraint; the state of the leadership team running it is.
So, I focus on that. I help the small group at the top become unified, stable, and grounded in a shared reality. This changes the signal that the entire system reacts to. It’s the smallest intervention that offers the most leverage because everything that follows, such as decision quality, speed, and whether the change withstands pressure, is determined by the unity in that initial group. You don’t scale a transformation by trying to begin everywhere at once. You start with the smallest system that the entire organization already reflects.
You’ve observed that a leader’s nervous system sets the team’s state; what daily regulation ritual do you coach executives to use before high-stakes decisions?
The one I coach is deceptively simple, and it works because it is physiological, not mindset.
Before any high-stakes decision, I have them do three things, and it takes about ninety seconds:
-
Notice the state you are actually in. Most executives walk into the biggest decisions of their week activated, rushed, and slightly braced, and they have no idea because that state has become their normal. You cannot regulate what you have not noticed. So the first move is one honest question: What state am I in right now?
-
Downshift the body before you engage the mind. The fastest lever is the breath, specifically a longer exhale than inhale for about sixty seconds. A longer exhale is not a wellness cliché. It engages the vagal brake and pulls the nervous system out of fight-or-flight, and you can see it in heart-rate variability in real time. A regulated system perceives nuance and holds complexity. An activated one narrows to threat and reacts.
-
Decide the state you want to set, because you are about to set one whether you choose to or not. Your nervous system enters the room before your strategy does, and the team will organize around it. So choose deliberately what you bring in.
None of this holds without a daily baseline. I have executives anchor a short regulation practice every morning, before the phone, so that under real pressure there is something to draw on. The ninety-second reset is the acute version. The daily practice is what makes it available when it counts.
For CHROs and CTOs, what six-week experiment would you run to measurably improve organizational performance in a complex, hybrid environment?
I would run the experiment I use in my pilots, because six weeks is enough to move the leading indicators, and CHROs and CTOs believe what they can measure.
Pick one intact leadership team that owns something high-stakes right now. Not a workshop group, a real team under real pressure. That is your unit.
Week zero is the baseline, and this is the part most organizations skip. Instrument the team the way a CTO would instrument any system before changing it. Record one to three of their actual meetings and read the synchrony in them: turn-taking, shared attention, heart-rhythm co-regulation. Have each member complete a coherence diagnostic, so you also have how the team experiences itself. Baseline the individuals physiologically: HRV, sleep, recovery. Now you have two data streams: what the team believes about itself and what its physiology actually shows. The gap between them is the most valuable number you will get.
During the six weeks, run two things in parallel. Individually, each leader installs a daily regulation practice, and you track HRV and recovery. At the team level, use the baseline to surface divergences people have not said out loud, build one shared reality, and change how decisions are made. Maintain a weekly cadence and log it.
Then re-measure with the same instruments and compare the team to itself—never to an industry benchmark. You will see the leading signals move in order: individual physiology first, then synchrony and trust, then the self-report and the data converging, then decision speed and rework improving.
The discipline that makes it an experiment, not an initiative, is the baseline and the re-read. You are not asking people whether they feel more aligned. You are measuring whether they are, the same way you would measure any system you are accountable for.
One honest caveat: six weeks will give you a real, measurable shift. It will not yet give you a new identity. A shift is a team performing differently. An identity is a team that has become different, so the new way holds when the pressure returns instead of reverting to who they were. Think of the arc in three moves. At week zero, you have the story a team tells about itself. By week six, you have proof it can change. Over the months that follow, that proof becomes identity, the point where coherence is simply who the team is and no longer something they have to hold in place. The six-week experiment earns you the right to that longer arc. It is not a substitute for it.