Meetings as culture, Part 3: Your behavior matters
At a large nonprofit, the team’s schedules were packed—weekly staff meetings were one of the few times they could connect and align on big priorities. Having just gotten Board approval of an ambitious strategic plan, the leadership team saw this as a high-leverage moment and made bold changes to improve the structure: clear purposes, defined outcomes, and assigned ownership.
But after a high-stakes budget conversation fell flat, it became clear that structure wasn’t enough. The behavior in the room—who spoke, who listened, how decisions were made—mattered just as much.
Every habit embedded in the nonprofit’s culture—good and bad—was showing up somewhere in their meetings. Rather than ignore it, the team used it. They turned meetings into a mirror (and a tool) for culture change.
This is the third post in our Meetings as Culture series. Part 1 explores how meetings reflect your organization’s culture. Part 2 offers practical solutions to five common meeting pitfalls. Now, in Part 3, we focus on the five individual and team behaviors that drive lasting culture change—one meeting at a time.
Meetings as the crucible of culture
Meetings are where your company culture plays out in real time—where it’s tested, transformed, and forged under pressure. The more senior you are, the more meetings you attend. Your behavior in these meetings—whether you’re leading or participating—affects the culture of your organization. Each company has a unique approach to meetings that reflects their culture.
At BTS, we believe meetings are more than just structures—they’re part of your organization’s social fabric. The way people interact, pay attention, and respect each other’s time in meetings reflects your company’s values and mindsets. In short, a single meeting is the culture in concentrated form.
As simple as it sounds, there are five fundamental meeting behaviors:
- Listening
- Participating
- Efficiency
- Accountability
- Focus
These five meeting behaviors – defined in observable terms to ‘see’ what works - can be developed by individuals, teams, and organizations to transform your meeting culture. Individual behavior informs team dynamics, which aggregate to become organizational behaviors. To shift your culture, you need to progressively develop meeting behaviors with individuals, teams, and the organization.
Develop the five meeting behaviors—as individuals, teams, and organizations
Start by looking in the mirror. Individuals have a major impact on meeting productivity and inclusiveness. It starts with you—your actions shape the meeting environment, whether you are leading it or not.
Considering your last meeting, ask yourself: How many times did I reschedule this meeting? Was I on time? How well did I listen? Did I ask questions for clarity, or did I talk over others? Did I come to the meeting having done what I said I would do? Did I leave knowing and committing aloud what I will do next? The fixes are all simple, but not always easy.
- Quick tip: A BTS client aiming to improve their meetings found that reminding individuals of the power of asking more probing questions helped foster better listening, which helped with their strategic goal of building a culture of stronger collaboration. A probing question is one that opens up the conversation, clarifies the discussion for everyone, and increases ideas generation.
Once individuals are aware of and start improving their behaviors, look at how the team works. Here, you will start to notice that individual behaviors seep into team patterns: Are the same voices always leading the conversation? Does everyone feel free to speak up? Do we reward diverse perspectives and debate? How many conversations do we have at the same time? Do the triggers that often derail us have discernable tells?
- Quick tip: Consider how you allocate time during meetings. One team made a rule to save the last five minutes of any important topic for quieter members to speak, sending a strong message: everyone’s voice matters. It’s often easier to change meeting structures (like the agenda) than it is to change behaviors. So, use structures to support the team behaviors you want.
Cumulatively, meetings have a huge organizational impact. If you look closely, you can see how meetings reflect and shape company-wide cultural values. Are your meetings aligned with the strategic priorities of the business and the values you want to see across the organization?
- Quick tip: When the meeting invite and materials you send in advance overtly connect the meeting’s purpose and outcomes to broader business goals, people are more aligned and productive. As a side benefit, people should question any meeting that cannot be tied to a broader business goal—it is the litmus test of a meeting agenda.
Assess your meeting effectiveness
If you’re not paying attention to how you and your team behave during meetings, you won’t have a sense of how effective your meetings are, and they won’t improve.
At the nonprofit in our earlier example, leaders tracked their progress with a simple anonymous post-meeting poll. After each meeting, participants gave a thumbs up if the meeting hit the five fundamental observable behaviors or a thumbs down if it didn’t. This quick feedback helped them stay on track.
Reflect on your most recent meeting using the framework below.
How to do it:
Start with assessing your most recent meeting at Level 1 in the list below. If you can’t answer “yes” to the fundamental meeting behaviors at Level 1, then this is an area to practice intentionally next meeting. To level up to Level 2 and 3, answer “yes” for all five meeting behaviors for three meetings in a row (to ensure it’s not a fluke).
Level 1
Listening: Did we have ‘one conversation’?
Participating: Did everyone stay present – no multi-tasking or checking out?
Efficiency: Did we begin and end on time?
Accountability: Were all the action items clear and claimed?
Focus: Did we stay on topic for each agenda item?
Put it into practice
At the nonprofit, assessing meeting behaviors over time led to better individual behaviors, stronger team results, and a shift in the way staff meetings contributed to the mission. As old behaviors that previously dominated or derailed staff meetings declined, the meetings became an even more valuable time for organization-wide connections and storytelling. This approach and discipline to meetings was adopted by the individual leaders’ meetings. Meetings all around the organization improved. While getting there took longer than predicted, the shifts lasted, and the organization’s outcomes improved. People began to expect good meetings that were productive and contributed to action and success.
Meetings are more than just a tool for getting things done—they’re a powerful reflection of a microcosm of your organization’s culture. When approached with intention, they can drive behavior change, foster collaboration, and align teams with strategic goals. Simply by developing five fundamental behaviors, the way you and your teams show up in meetings can transform how your company works together and accelerates progress. Ultimately, meetings are where culture is built, one conversation at a time.
Related content
Related content
In Part 1, I told you about the three decisions we made two years ago and the simulation flywheel that produced our first Applied AI diamond.
Here’s the field-notes version.
Over 80% of our global business have now adopted a new Applied AI approach for doing simulations in the first eight weeks, across 24 countries and every practice.
The flywheel didn’t stop with simulations. It moved into finance, sales enablement, legal, operations, and client delivery. Teams started building agents and bringing them onto their own org charts. We didn’t plan for any of that. We built the conditions for people to find their own breakthroughs.
What it felt like inside the flywheel.
When the simulation team went live with their first clients on the new way of working, the lead person hit a wall. Their words:
“You’re asking too much. You’re making me be a full-stack developer. Up until this point I did a small part, and I sent it to the team, and they built off the back end, and they brought it back. And now I have to end-to-end soup to nuts, basically alone.”
There was graphic UI work nobody had been trained for, the fear of delivering quality below what BTS expects of itself, and the weight of not having a playbook. This was not the joyful adoption story most consultancies tell.
Then something shifted. Six members showed up for product testing, where the usual was two or three. The work created teamwork I hadn’t seen at BTS in years. The breakthrough was not an instantaneous change from skepticism to celebration. It was a breakdown in confidence, then rally, then bonding. If we didn’t make room for the breakdown, we would have lost the rally.
The other breakthrough was global teamwork; not yet a BTS core strength. Our culture is beautiful: high-freedom and entrepreneurial. But people’s first identities are to their countries. Almost every prior attempt we’ve made at a global initiative has failed. The one exception was Covid. So, when I say what happened next surprised me, I mean it.
I asked to join the simulation team’s Slack channel rather than pulling them into status meetings. What I got to watch in the mornings was someone in South Africa waking up, posting “I tried this and got stuck,” then London adding on, then San Francisco weighing in, then a surprise breakthrough overnight from Tokyo. We didn’t engineer that. Curious and determined BTS’ers did. The problem was interesting enough that the org chart didn’t matter. It was amazing to see and a glimpse into the next evolution of the BTS culture.
The pattern: Explore, expand, institutionalize, renew.
What we’ve now seen play out, both inside BTS and with clients, follows the same four-step pattern. Each step asks a specific decision of the leader.
Explore.
Stay stubborn on the aspiration and fluid on the path. Our breakthrough wasn’t the path we originally took. We changed tools and approaches. Nobody could have foreseen that. And if the team had taken the first six months of learnings from AI as their definitive “this is the detailed path we will follow,” we never would have gotten the disruption. Five different tool combinations were tried before we found the one that worked. Companies that lock into a single path or tool too early are betting against compounding capability that doubles roughly every seven months. That is not a bet I’d take.
Expand.
Run the old way and the new way side by side. When the simulation team’s breakthroughs got real, the instinct was to retreat into more internal testing. We did the opposite. They ran old way and new way in parallel on 6 or 8 live client projects across all three geographies. Every single one ended up going live the new way. The backup was always there. They didn’t need it.
Institutionalize.
Burn the boats. The simulation team committed that no new client work would be done the old way after January 1. The other practice leads then committed to dates within Q1, even though most of them had not yet experienced the new way themselves. They had to trust their colleagues. If you can do it for the most complex thing, you could probably do it for the less complex ones. By February 15, we had approaching 90% global adoption across 24 countries, across all practices. I was shocked and proud. We had spent years failing at exactly this kind of global rollout.
Renew.
Treat your agents as contractors. People on our diamond teams are now managing 30+ agents they built themselves. Our teams give agents performance feedback. We terminate their contracts when they don’t deliver. We expand the responsibility of agents when they outperform. The frontier question we’re wrestling with now is token budgeting. Two friends of mine running engineering-heavy companies believe that within 6 - 9 months, their token cost per engineer will exceed the cost of the engineer. Whether that’s the right framing is open. The question is real, and every CEO will be asked some version of it within the year.
What had to be true for this to scale.
Once we achieved this amazing global innovation, the leadership sat down to figure out what made it work. We named five things. None of them were about the technology.
Real pain points as the starting point. We had so many people frustrated from those ways of working, all the back and forth and all the wasted time, that this was gold for them. The old way was already painful. The new way wasn’t a forced disruption; it was relief. Find the workflow where the pain is loudest and start there.
The diamond unlocked creativity, it didn’t constrain it. This was the most differentiated insight, and the one most leaders miss. It wasn't "here's the new tasks and rules." It was, "once you learn how to do this, the sky's the limit. You can be even more creative." If your rollout feels like a new set of rules constraining your people, you’ve built the wrong thing.
Pair deep expertise with fresh eyes. The disproportionate share of our breakthroughs came from a tenured tinkerer with total command of the work, paired with someone new to the role who hadn’t yet built the muscle memory of how it had always been done. Without that pairing, you get incremental improvements to the work you already know how to do, instead of a reinvention.
Refuse the “people are too busy” reflex. When I brought the rollout to the global leadership team, the excuses came fast. “Our people are too busy. They’re burnt out. Q1 is going to be busy. No one’s going to have time.” My response: “This is a chance to eliminate the tasks you dread and expand what you love. I know it is a short push of extra work, and I think after the fact you and your team will feel joy and pride and say it was the best time we ever spent.” This is the moment most AI rollouts die.
Senior leaders must lead by example and do the work themselves. This is not middle manager’s job. This is not something you delegate. Even though you don’t build simulations anymore, you must know what this is. One of our partners proactively put time on senior leaders’ calendars and forced them to do the work. Once they started building, the excitement grew, and they could advocate for the rollout because they understood it. If your executives haven’t put their hands on the keyboard, you don’t have a rollout. You have a memo.
What we’re seeing across clients.
We’re now running this play with client organizations across industries and geographies. The companies whose flywheels are accelerating paired their A-players with their early-career talent, pulled IT and legal into the working sessions, refused the “too busy” reflex, and put their senior leaders’ hands on the keyboard. The companies whose flywheels are stuck almost always have a leadership pattern at the center of the stall. Not a tooling pattern. Not a governance pattern. A leadership pattern.
If this resonates, let’s talk.
If you read Part 1 and asked yourself whether your flywheel was turning, the question I’d add now is sharper: do you have the conditions in place for a diamond to appear? If yes, you’re already moving. If no, the technology will not save you.
Here's where we're starting with clients: a working session, half day to a full day, with a small group that owns one of your highest-friction processes. Together we map where your first diamond is most likely to land, how to set up the side-by-side trial, and what your version of "burn the boats" should look like.
The destination, if we do this right, is a self-reliant culture of applied AI inside your company. 5, 10, 15 diamonds compounding into a fundamentally different way of operating. From what I have experienced this is a once in a career opportunity for dramatic shareholder value creation if you get that muscle going. I say that because I'm watching it happen, in real time, inside our own company and across our client base.
If you want to get your flywheels spinning and map your first diamond, start here. Bring your hardest workflow. We'll bring the playbook.
Organizations have long wanted to scale coaching, but have been limited by cost and capacity. With AI, that's beginning to change as new platforms make coaching more accessible, flexible, and available on demand, extending support beyond a select group of leaders to entire populations.
For talent leaders, this shift creates both opportunity and complexity. With greater reach comes a new set of trade-offs: how to balance access with depth, flexibility with accountability, and efficiency with meaningful development.
The limits of unlimited (coaching).
Unlimited coaching sounds like the obvious answer. Remove the barriers, give everyone access, let people engage on their own terms. What's not to like?
In practice, quite a bit.
When coaching has no defined structure or cadence, engagement tends to become episodic - people show up when something feels urgent and step back when it doesn't. The coaching relationship never quite deepens. Conversations cover ground but don't build on it. And the development that was supposed to happen keeps getting pushed to the next session, and the next.
Three patterns emerge:
- Sporadic engagement over sustained development. Without a rhythm to anchor the work, coaching becomes reactive. Clients bring whatever is most pressing that week rather than working toward something larger. Progress happens in bursts, if at all.
- Insights that don't compound. Great coaching reveals patterns over time - things a client can't see in one session but can't unsee after several. Without continuity, and without a consistent coaching relationship to hold the thread, each conversation starts close to zero.
- Outcomes that are hard to measure. No milestones. No defined endpoint. No clear way for the organization, or the client, to know whether it's working. Activity fills the gap where impact should be.
The result is a model that's easy to scale and hard to defend. Which is exactly the problem talent leaders are navigating right now.
The relationship is the lever.
Decades of research into what makes coaching work keeps arriving at the same answer: it's the relationship. Not the platform, not the methodology. The relationship.
When a coach and client build trust over time, developing shared language, and returning to the same themes with increasing depth, something shifts. Conversations get more honest. Insights stick. The client starts doing the work between sessions, not just during them. That's when coaching becomes genuinely transformative, and it can't be rushed or replicated in a one-off session.
The ICF and EMCC are clear on this: continuity is what dives outcomes. The coaching engagements that produce lasting change are the ones where each session builds on the last, not the ones that simply offer more access.
Three principles make that possible: Consistency, Continuity, and Completion.
1. Consistency
The foundation everything else is built on.
The temptation when designing a coaching program is to treat flexibility as a feature - let people book when they want, swap coaches freely, engage on their own schedule. But frequent coach changes reset the clock. Every new coach has to earn trust, learn context, and find their footing with the client. That's time spent getting started, not getting somewhere.
A stable coaching relationship works differently:
- The coach starts to see around corners, uncovering patterns the client can't see on their own
- The client stops performing and starts being honest
- The relationship itself becomes a source of accountability, not just the sessions
Consistency doesn't constrain the work. It's what makes the deeper work possible.
2. Continuity
What turns a series of sessions into genuine development.
Without continuity, coaching tends to be additive at best- each session offers something useful, but nothing compounds. With it, the work builds on itself in ways that can't happen in isolated conversations.
What continuity makes possible:
- A limiting belief surfaced in session three becomes a thread that runs through the rest of the engagement
- A behavioral pattern the client couldn't see at the start becomes impossible to ignore by the end
- Space opens up for the harder work - the kind that requires sitting with discomfort across multiple sessions, not resolving it quickly and moving on
That slower, deeper work is where lasting change actually happens. It doesn't come from more sessions. It comes from the right sessions, in the right order, with the same person.
3. Completion
The most underrated principle of the three.
In a world of unlimited access, there's no finish line, and without one, it's surprisingly hard to know what you're working toward, or whether you've gotten there. A defined endpoint changes the entire shape of an engagement.
A clear endpoint creates urgency and focuses every session on what matters most.
- Shifts the question from "what should we talk about this week?" to "what do we need to accomplish before we're done?"
- Gives both coach and client a body of work to look back on, not just a log of conversations
For talent leaders, this is also what makes coaching legible as an investment. Sessions logged is an activity metric. A cohort of leaders who completed a structured engagement and can articulate what changed, that's a result.
Don't just scale it, design it (here’s how)
The opportunity in front of talent leaders right now is significant. The organizations that will get the most from this moment are the ones that treat coaching design as seriously as coaching delivery.
Practical design decisions:
- Define the arc before you launch: set the number of sessions, the cadence, and the goals upfront, not after people have already started booking
- Protect the coaching relationship: Make coach switching the exception, not the default, and design your program to discourage unnecessary re-matches
- Build in milestones: create structured check-ins at the midpoint and end of each engagement so progress is visible to both the coach and the organization
- Separate on-demand support from developmental coaching: Use AI-enabled tools for in-the-moment guidance, and reserve structured engagements for the deeper work
- Measure completion, not just activation: Track how many people finish an engagement, not just how many start one
Questions to pressure-test your design:
- Does every participant know what they're working toward before their first session?
- Can your coaches see enough context about a client's journey to pick up where they left off?
- Would you be able to show, at the end of a cohort, what changed, and for whom?
Access opened the door. Intention is what makes it worth walking through.
Three decisions that changed everything.
Two years ago, we made three deliberate decisions about how BTS would move with Applied AI.
We would become our own Customer Zero.
While others were building strategies, defining governance, and waiting for clarity, we made a different call: we decided not to wait. Not because the stakes were low, but because they were high. And because in a space evolving this quickly, clarity wouldn’t come from planning. It would come from movement.
So instead of starting with a roadmap, we started with three principles:
- No top-down mandate. The people closest to the work figure it out.
- IT must evolve from gatekeeper to enabler - leading AI trials and fast experimentation.
- Don’t wait for certainty.
We set the organization in motion, and once we did, things started to move quickly.
What if we started this company today?
Waiting for certainty is itself a choice, and it’s costing companies more than they realize.
We started where we knew the work best: our simulations. No perfect plan, just teams moving, trying, and iterating.
Simulations are core to who we are at BTS. Companies that simulate don’t just make better decisions; they execute faster and build more engaged cultures.
The team asked a simple question:
"What if we were to start our company today?”
That question started the flywheel.
They asked IT for a few licenses and started building - vibe-coding, writing agents, and testing tools - moving at a pace that would make any VC-backed start-up smile.
The messy middle.
At first, the team was underwhelmed.
The early reports were blunt:
“Not good with math.”
“Poor graph capabilities.”
The team wasn't discouraged. They kept tinkering - jumping between tools, staying on top of new releases, experimenting constantly.
This was a small team, across 24 countries, building off each other’s ideas. Laughing at crazy creations. Breaking things. Iterating in a sandbox alongside real clientwork.
Each cycle produced something:
- A sharper scenario
- A faster build
- A more powerful simulation
The flywheel was turning, and it was generating something real.
When the diamond appeared.
Then something shifted.
The team moved into client trials across five countries. They figured out ISO compliance and built the architecture to handle the complexity, the “spaghetti.”
And what emerged wasn’t incremental:
- What used to take weeks started happening in days.
- Limited creativity started to feel like unlimited innovation.
- Clients became self-serving.
- Agentic simulations were built directly into client systems for real-time updates and preparation.
This was our first AI diamond - a high-impact outcome created by many cycles of experimentation compounding into real value.
It only appeared because we kept the flywheel turning, each cycle increasing the odds that something would break through.
95% adoption in eight weeks.
Then it was time to take the AI diamond global.
BTS is decentralized and highly entrepreneurial. We operate across 24 countries and 38 offices, where local teams have real autonomy.
And historically? That’s meant a low appetite for adopting something built somewhere else and pushed from the center.
So we expected resistance.
Instead, something surprising happened.
In the first eight weeks, we saw 95% adoption across our global footprint.
It felt completely different from our own digital initiatives, ERP implementations, top-down rollouts of the past.
This moved on its own. Why?
We realized it didn’t start with a framework or a model, it started with a feeling.
The feeling of being at the leading edge of one’s craft and profession.
- Joy
- Excitement
- Pride
As we watched this play out across teams it stopped feeling like isolated wins.
There was a pattern to it. A repeatable, organic, innovation motion.
And the flywheel didn’t stop with simulations.
It spread across finance, sales enablement, legal, operations, and client delivery. Some cycles led to small improvements, and others revealed new diamonds.
Not becausewe planned for them, but because we built the conditions for people to find them.
The question I'd ask any CEO right now: Is your flywheel turning, or are you still waiting for the perfect plan?
In part 2, I’ll share the key success factors behind the breakthrough, and what we’re now seeing across more than 120 global clients.