<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Mark Kenny | Leadership Keynote &amp; Retreat Speaker | Uncommon Collaboration</title>
	<atom:link href="https://www.markskenny.com/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.markskenny.com</link>
	<description>Mark partners with leaders to create the human shift that restores clarity, trust, and momentum inside organizations.</description>
	<lastBuildDate>Tue, 14 Apr 2026 21:15:30 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.7.5</generator>

<image>
	<url>https://www.markskenny.com/wp-content/uploads/2022/02/cropped-MarkKennyThumbnail-32x32.png</url>
	<title>Mark Kenny | Leadership Keynote &amp; Retreat Speaker | Uncommon Collaboration</title>
	<link>https://www.markskenny.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>My Team Isn’t Telling Me Something</title>
		<link>https://www.markskenny.com/2026/04/14/my-team-is-not-telling-me-something/</link>
		
		<dc:creator><![CDATA[Mark S. Kenny]]></dc:creator>
		<pubDate>Tue, 14 Apr 2026 21:12:26 +0000</pubDate>
				<category><![CDATA[Blog Posts Recent Col 1]]></category>
		<category><![CDATA[Blog Posts Uncommon]]></category>
		<guid isPermaLink="false">https://www.markskenny.com/?p=15812</guid>

					<description><![CDATA[I’ve stepped into a lot of teams where something feels off, but no one is saying it. On the surface, everything looks fine. But underneath, there’s something people aren’t bringing into the room. Here's what you can do about it.
]]></description>
										<content:encoded><![CDATA[<div class="et_pb_section et_pb_section_0 et_section_regular" >
				
				
				
				
				
				
				<div class="et_pb_row et_pb_row_0">
				<div class="et_pb_column et_pb_column_4_4 et_pb_column_0  et_pb_css_mix_blend_mode_passthrough et-last-child">
				
				
				
				
				<div class="et_pb_module et_pb_text et_pb_text_0  et_pb_text_align_left et_pb_bg_layout_light">
				
				
				
				
				<div class="et_pb_text_inner"><p>I’ve stepped into teams before where you can feel it almost immediately.</p>
<p>The leader is capable. The team is talented. On the surface, everything looks fine. But as the conversation unfolds, something is off. People are careful. They choose their words. Certain things don’t get said. You can sense there’s more under the surface, but no one is bringing it into the room.</p>
<p>At some point, the leader will pull me aside and say, “I feel like my team isn’t telling me something. I just don’t know what to do.”</p>
<p>They’re usually right. Because you can feel it, even when no one is saying it.</p>
<p>This is one of the most common forms of fragmentation I see on leadership teams. Everything looks aligned, but underneath, something isn’t being said.</p>
<p><strong>If You Can Feel It, It’s Real</strong></p>
<p>Most leaders assume this is a communication issue. They think the team needs to be more open, speak up more, or take advantage of an open-door policy. But that’s rarely the issue.</p>
<p>When a team is holding something back, it’s because something in the environment is telling them not to say it. And as hard as this is to hear, that environment is shaped by the leader.</p>
<p>This is where the work begins.</p>
<p><strong>This Isn’t About the Team</strong></p>
<p>The easiest answer is to blame the team. We tell ourselves they’re not strong communicators or that they just need more courage. But that line of thinking keeps you stuck, because it puts the responsibility somewhere you can’t control.</p>
<p>The shift happens when a leader asks a different question: “If they’re not saying it, what is it about how I’m showing up that makes not sharing the safer choice?”</p>
<p>That question changes everything. It moves the focus from trying to fix the team to examining your own impact on the environment they’re operating in.</p>
<p><strong>Create the Conditions for Truth</strong></p>
<p>Your job as a leader is not to pull the truth out of people. Your job is to create the kind of environment where truth can actually show up.</p>
<p>That requires a different posture. Not as the person with the answers or the one people report up to, but as someone who is there to serve the team and create the conditions for them to do their best work. People don’t hold back randomly. They hold back when it doesn’t feel safe, when it doesn’t feel useful, or when it doesn’t feel like it will be received well.</p>
<p>If you want truth, you have to pay attention to those conditions.</p>
<p><strong>Make It Visible</strong></p>
<p>If something feels off, don’t ignore it. Everyone already knows.</p>
<p>Say it out loud. Something as simple as, “Something doesn’t feel right. I’d like to understand what I might be missing and what I can do better as a leader,” can shift the tone of a conversation. It lowers the pressure in the room and signals that you’re willing to go first.</p>
<p>And going first matters more than anything in this situation.</p>
<p><strong>Focus on Behavior</strong></p>
<p>This is where most leaders go too broad. They try to “be more open” or “improve communication,” but those ideas are too vague to act on.</p>
<p>The real work is behavioral. A behavior is something someone could see or hear if they were in the room with you. It might be interrupting when someone disagrees, getting defensive too quickly, moving on before something is fully worked through, or unintentionally rewarding agreement over honesty.</p>
<p>These are the signals your team is reading, whether you realize it or not.</p>
<p><strong>Choose One or Two Things to Change</strong></p>
<p>Trying to fix everything at once doesn’t work. It’s far more effective to choose one or two behaviors that, if you changed them, would make it easier for people to speak up.</p>
<p>Then tell people what you’re working on. Let them know you’re trying to get better and that you need their help. That step is important, because it turns this from a private intention into a shared effort. You’re not just asking for truth in theory. You’re inviting it in a specific, observable way.</p>
<p><strong>Get Real Feedback</strong></p>
<p>If your team isn’t telling you something, you can’t rely on passive feedback. You have to go get it.</p>
<p>That might mean asking directly, “What’s one thing I could do differently that would help you or the team be more effective?” It might mean having someone else gather feedback anonymously, or using a structured assessment if that fits your environment (in my experience, making these behaviorally based is critical).</p>
<p>Don’t expect an answer right away. In fact, you may not get one at all the first time you ask. That doesn’t mean there’s nothing to say. It means people are watching. They’re deciding whether it’s actually safe to be honest, and whether anything will change if they are.</p>
<p>That’s why consistency matters.</p>
<p>And the most important part is how you respond. When you do get feedback, don’t explain or justify. Don’t fix it in the moment. Just write it down and say thank you. That’s how you start to change the environment.</p>
<p><strong>Invite Truth and Stay With It</strong></p>
<p>An open-door policy doesn’t work for this. People don’t walk through open doors with hard truths. You have to initiate and invite it, regularly and intentionally.</p>
<p>Ask questions like, “What are we not saying that we need to?” or “What might I be missing?” and then pay close attention to how you respond when someone takes the risk to answer. That moment will determine whether it happens again.</p>
<p>And when something real does surface, don’t rush past it. Most teams get close to the real issue and then move on too quickly. That’s where alignment is either built or lost. Staying in the conversation, especially when it’s uncomfortable, is what allows the team to actually work through what matters.</p>
<p><strong>Go First</strong></p>
<p>Over time, you can create a team where people give each other this kind of feedback. But it won’t start there.</p>
<p>It starts with you. When you model openness, ownership, and a willingness to change, you make it possible for others to do the same.</p>
<p><strong>The Real Question</strong></p>
<p>If your team isn’t telling you something, the question isn’t what they’re holding back. It’s what they’re experiencing from you that makes holding back the safer choice.</p>
<p>The moment <em>that</em> changes, the conversation changes. And when the conversation changes, teams start to move forward again.</p>
<p><strong>Invitation</strong></p>
<p>I see this pattern a lot when I step into leadership teams.</p>
<p>If you’ve felt it in your team, I’d be curious: where do you think people might be holding something back right now? And what do you think they’re reacting to?</p>
<p>Or where do conversations start, but don’t quite get finished? I’d be interested to hear what you’re seeing.</p></div>
			</div>
			</div>
				
				
				
				
			</div>
				
				
			</div>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>7 Ways to Lead Collaboration When Pressure Is High</title>
		<link>https://www.markskenny.com/2026/04/08/7-ways-lead-collaboration-when-pressure-high/</link>
		
		<dc:creator><![CDATA[Mark S. Kenny]]></dc:creator>
		<pubDate>Wed, 08 Apr 2026 20:36:36 +0000</pubDate>
				<category><![CDATA[Blog Posts Recent Col 1]]></category>
		<category><![CDATA[Blog Posts Uncommon]]></category>
		<guid isPermaLink="false">https://www.markskenny.com/?p=15806</guid>

					<description><![CDATA[Collaboration matters more than ever when the pressure is on. Real collaboration helps all of us handle reality better.
]]></description>
										<content:encoded><![CDATA[<div class="et_pb_section et_pb_section_1 et_section_regular" >
				
				
				
				
				
				
				<div class="et_pb_row et_pb_row_1">
				<div class="et_pb_column et_pb_column_4_4 et_pb_column_1  et_pb_css_mix_blend_mode_passthrough et-last-child">
				
				
				
				
				<div class="et_pb_module et_pb_text et_pb_text_1  et_pb_text_align_left et_pb_bg_layout_light">
				
				
				
				
				<div class="et_pb_text_inner"><p>I’m in the middle of facilitating retreats this month, and I’m hearing a similar theme: “We’re under a lot of pressure. Things are changing. And we’re feeling it.”</p>
<p>This is when collaboration matters more than ever. The natural inclination is to retreat into my own work. But real collaboration, the kind I call Uncommon Collaboration, helps all of us handle reality better.</p>
<p>Here are seven practical ways you can lead collaboration in your team, especially under pressure:</p>
<ol>
<li><strong> Make the pressure visible</strong></li>
</ol>
<p>Don’t let everyone carry it privately. Ask:</p>
<ul>
<li>“What’s putting the most pressure on you right now?”</li>
<li>“What’s taking more energy than it should?”</li>
</ul>
<p>You’ll get better collaboration the moment people feel seen.</p>
<ol start="2">
<li><strong> Clarify what matters most right now</strong></li>
</ol>
<p>Pressure creates noise. Collaboration improves when priorities are clear. Your team needs to know:</p>
<ul>
<li>What we own</li>
<li>What matters most right now</li>
</ul>
<p>“If we only get one thing right this week, this is it.”</p>
<ol start="3">
<li><strong> Slow the conversation down</strong></li>
</ol>
<p>Pressure speeds people up. Create intentional space to slow down just enough to think together. Even a short pause without devices can change the quality of the conversation.</p>
<ol start="4">
<li><strong> Make it safe to say what needs to be said</strong></li>
</ol>
<p>You don’t have time to circle back on decisions or chase the wrong problem. You need people to speak up.</p>
<p>That means not reacting when truth shows up, saying “thank you” to feedback, and staying curious when something doesn’t land. It also means inviting dissent early by asking, “What are we missing?” or “Who sees this differently?”</p>
<ol start="5">
<li><strong> Ask for help out loud</strong></li>
</ol>
<p>Everyone carries too much under pressure, especially leaders. Everything changes when leaders model it: “Here’s where I’m stuck. I need your help.”</p>
<ol start="6">
<li><strong> Stay in the conversation when it gets uncomfortable</strong></li>
</ol>
<p>Most teams exit conversations too early. That’s where collaboration breaks.</p>
<p>Lean into the uncomfortable instead of moving past it. Otherwise, it turns into side conversations and lost alignment.</p>
<ol start="7">
<li><strong> Reinforce a belief in people and the path forward</strong></li>
</ol>
<p>Everyone has had a moment where they stopped believing in themselves after a mistake, setback, or tough season. One of the most powerful things you can do under pressure is remind people what they’re capable of and what they’ve already done.</p>
<p>Pressure doesn’t break collaboration, it reveals it.</p>
<p>The teams that move forward aren’t the ones without pressure. They’re the ones who choose how they show up inside it.</p>
<p>&nbsp;</p>
<p>&nbsp;</p></div>
			</div>
			</div>
				
				
				
				
			</div>
				
				
			</div>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Why Some Conversations Never Move Things Forward</title>
		<link>https://www.markskenny.com/2026/04/01/why-some-conversations-never-move-things-forward/</link>
		
		<dc:creator><![CDATA[Mark S. Kenny]]></dc:creator>
		<pubDate>Wed, 01 Apr 2026 22:39:51 +0000</pubDate>
				<category><![CDATA[Blog Posts Recent Col 1]]></category>
		<category><![CDATA[Blog Posts Uncommon]]></category>
		<guid isPermaLink="false">https://www.markskenny.com/?p=15796</guid>

					<description><![CDATA[There are moments when a leader, colleague, or direct report says something that doesn’t come out quite right. What happens next really matters.
]]></description>
										<content:encoded><![CDATA[<div class="et_pb_section et_pb_section_2 et_section_regular" >
				
				
				
				
				
				
				<div class="et_pb_row et_pb_row_2">
				<div class="et_pb_column et_pb_column_4_4 et_pb_column_2  et_pb_css_mix_blend_mode_passthrough et-last-child">
				
				
				
				
				<div class="et_pb_module et_pb_text et_pb_text_2  et_pb_text_align_left et_pb_bg_layout_light">
				
				
				
				
				<div class="et_pb_text_inner"><p id="ember383" class="ember-view reader-text-block__paragraph">There are moments when a leader, colleague, or direct report says something that doesn’t come out quite right.</p>
<p id="ember384" class="ember-view reader-text-block__paragraph">Examples:</p>
<ul>
<li>Someone speaks up in a meeting with an unpopular opinion.</li>
<li>A leader finally says what needs to be said, and it comes out a little sideways.</li>
<li>A colleague from another office seemingly steps on your toes.</li>
</ul>
<p id="ember386" class="ember-view reader-text-block__paragraph">What happens next is what matters.</p>
<p id="ember387" class="ember-view reader-text-block__paragraph">Here’s what usually happens:</p>
<ul>
<li>Someone gets defensive</li>
<li>Someone shuts down</li>
<li>The team moves on quickly</li>
<li>The real issue never gets worked through</li>
</ul>
<p id="ember389" class="ember-view reader-text-block__paragraph">There was a conversation that was close… and then it slipped away.</p>
<p id="ember390" class="ember-view reader-text-block__paragraph">This is where many teams struggle. Not just with saying something real, but with what happens next after that.</p>
<p id="ember391" class="ember-view reader-text-block__paragraph">The antidote? Grace.</p>
<p id="ember392" class="ember-view reader-text-block__paragraph">Grace is the ability to stay in the conversation without punishing how it was said.</p>
<p id="ember393" class="ember-view reader-text-block__paragraph">It says, “That didn’t come out perfectly,” or “That doesn’t seem quite right, but let’s stay with it.”</p>
<p id="ember394" class="ember-view reader-text-block__paragraph">Here are some things we could say in the moment:</p>
<ul>
<li>“Say more about that”</li>
<li>“I don’t think that came out how you meant it, can you try again?”</li>
<li>“There’s something important in there, let’s not lose it”</li>
<li>“Let’s stay with this for a minute”</li>
</ul>
<p id="ember396" class="ember-view reader-text-block__paragraph">The hardest part is letting go of our initial reaction, our instant judgment, and everything the past is telling us in that moment.</p>
<p id="ember397" class="ember-view reader-text-block__paragraph">If teams don’t practice Grace, they stop staying in the conversation. And when that happens, the conversations that move things forward never get finished.</p>
<p id="ember398" class="ember-view reader-text-block__paragraph">Uncommon Collaboration is not about having more conversations. It’s about finishing the ones that matter.</p>
<p>&nbsp;</p></div>
			</div>
			</div>
				
				
				
				
			</div>
				
				
			</div>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>What Teams Need From Each Other (but aren’t getting enough of)</title>
		<link>https://www.markskenny.com/2026/03/25/what-teams-need-from-each-other/</link>
		
		<dc:creator><![CDATA[Mark S. Kenny]]></dc:creator>
		<pubDate>Wed, 25 Mar 2026 14:18:22 +0000</pubDate>
				<category><![CDATA[Blog Posts Recent Col 2]]></category>
		<category><![CDATA[Blog Posts Uncommon]]></category>
		<guid isPermaLink="false">https://www.markskenny.com/?p=15724</guid>

					<description><![CDATA[Most teams don’t need more meetings or tools. They need people to start giving each other what they actually need.
]]></description>
										<content:encoded><![CDATA[<div class="et_pb_section et_pb_section_3 et_section_regular" >
				
				
				
				
				
				
				<div class="et_pb_row et_pb_row_3">
				<div class="et_pb_column et_pb_column_4_4 et_pb_column_3  et_pb_css_mix_blend_mode_passthrough et-last-child">
				
				
				
				
				<div class="et_pb_module et_pb_text et_pb_text_3  et_pb_text_align_left et_pb_bg_layout_light">
				
				
				
				
				<div class="et_pb_text_inner"><p>When teams feel &#8220;off,&#8221; we usually audit the strategy or work on communication. We look at the KPIs. We buy a new project management tool.</p>
<p>But usually, the problem starts much deeper. The team has become guarded<strong>.</strong> When a team is guarded, they stop passing what others need.</p>
<p>So most teams don’t need more meetings, tools, or alignment exercises right away. Those matter. But they don’t work if people aren’t consistently giving each other a few simple things they need.</p>
<p>Here are two of them:</p>
<ol>
<li><strong>Presence</strong>: actually being in someone else’s world, without your own agenda</li>
<li><strong>Truth</strong>: saying and inviting what needs to be said, with care</li>
</ol>
<p>This is harder right now. There is a lot of uncertainty, pressure, overwhelm, and change. If a team is going to feel like a cohesive group working through that together, it takes real intention, not just talking about it.</p>
<p>Without presence, people don’t feel seen or understood.<br />Without truth, teams don’t deal with the real issues or make the right decisions.</p>
<p>When both are there, the dynamic shifts. People feel seen and challenged, cared for and called up.</p>
<p>As a leader, it’s worth asking:</p>
<p>Where could I give more presence?<br />Where could I invite more truth?</p>
<p>Two simple ways to start:</p>
<p><strong>1) The 5-Minute Curiosity Drop-In</strong></p>
<p>Pick one person today and give them five intentional minutes.</p>
<p>No agenda, no fixing, no multitasking. Just step into their world.</p>
<p>You might ask:</p>
<ul>
<li>“What’s taking most of your energy right now?”</li>
<li>“Where are things feeling heavy or stuck?”</li>
<li>“What’s something you wish was going differently?”</li>
</ul>
<p>Don’t solve it. Don’t redirect it. Don’t make it about you. Just listen.</p>
<p>That’s presence.</p>
<p>When everything is a Teams message or a 15-minute sync, leadership becomes a series of transactions. Transactions don&#8217;t build loyalty. Presence does.</p>
<p><strong>2) A Truth Invitation</strong></p>
<p>If you want more truth on your team, you have to invite it.</p>
<p>Try one of these questions, one-on-one:</p>
<ul>
<li>“What’s something I might be missing right now?”</li>
<li>“Where do you see this differently than I do?”</li>
<li>“If you were in my seat, what would you be paying attention to?”</li>
</ul>
<p>Don’t expect an answer right away. Just ask consistently.</p>
<p>And when they answer, don’t defend or explain. Just say, “Thank you for telling me.”</p>
<p>That’s what makes it safe to tell the truth again.</p>
<p>Truth isn’t about being harsh, and it’s not about avoiding things to be nice. It’s about reducing “time to reality.”</p>
<p>A guarded team burns energy on self-protection. A team rooted in truth puts that energy back into collaboration and results.</p>
<p>Most teams don’t need a big reset. They need more moments like this.</p>
<p>Small, consistent passes of presence and truth.</p>
<p>That’s how guarded teams start to open up.<br />That’s how teams start to feel like they’re moving forward together again.</p>
<p>&nbsp;</p></div>
			</div>
			</div>
				
				
				
				
			</div>
				
				
			</div>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Why Polite Meetings Fracture Culture</title>
		<link>https://www.markskenny.com/2026/03/18/why-polite-meetings-fracture-culture/</link>
		
		<dc:creator><![CDATA[Mark S. Kenny]]></dc:creator>
		<pubDate>Wed, 18 Mar 2026 15:52:50 +0000</pubDate>
				<category><![CDATA[Blog Posts Recent Col 2]]></category>
		<category><![CDATA[Blog Posts Uncommon]]></category>
		<guid isPermaLink="false">https://www.markskenny.com/?p=15718</guid>

					<description><![CDATA[Some of the most fragmented teams I’ve seen have the most polite meetings.]]></description>
										<content:encoded><![CDATA[<div class="et_pb_section et_pb_section_4 et_section_regular" >
				
				
				
				
				
				
				<div class="et_pb_row et_pb_row_4">
				<div class="et_pb_column et_pb_column_4_4 et_pb_column_4  et_pb_css_mix_blend_mode_passthrough et-last-child">
				
				
				
				
				<div class="et_pb_module et_pb_text et_pb_text_4  et_pb_text_align_left et_pb_bg_layout_light">
				
				
				
				
				<div class="et_pb_text_inner"><p id="ember63" class="ember-view reader-text-block__paragraph">Your meetings might be too polite.</p>
<p id="ember64" class="ember-view reader-text-block__paragraph">Most of us were taught to be polite, respectful, and not rock the boat. And it might be creating faux collaboration on your team.</p>
<p id="ember65" class="ember-view reader-text-block__paragraph">Some of the most fragmented teams I’ve seen have the most polite meetings. On the surface, everything looks fine:</p>
<ul>
<li>Everyone is respectful.</li>
<li>No one interrupts.</li>
<li>People nod.</li>
<li>Updates are shared.</li>
</ul>
<p id="ember67" class="ember-view reader-text-block__paragraph">The meeting ends.</p>
<p id="ember68" class="ember-view reader-text-block__paragraph">And then the real conversation happens: in the hallway, in a side conversation, in a follow-up call.</p>
<p id="ember69" class="ember-view reader-text-block__paragraph">I’m not suggesting we stop being respectful or start being rude. I’m saying politeness can hide fragmentation. Because fragmentation rarely shows up as conflict. It shows up as<span class="white-space-pre"> </span><strong>what people don’t say.</strong></p>
<ul>
<li>They don’t say they disagree.</li>
<li>They don’t say what they really think.</li>
<li>They don’t say something isn’t working.</li>
</ul>
<p id="ember71" class="ember-view reader-text-block__paragraph">This fractures culture instead of creating true collaboration.</p>
<p id="ember72" class="ember-view reader-text-block__paragraph">This doesn’t fix itself. It’s the leader’s responsibility to create an environment where disagreement, debate, and speaking up are expected.</p>
<p id="ember73" class="ember-view reader-text-block__paragraph">Try one of these:</p>
<ol>
<li>Before moving on, go around the table and ask each person for their view. No interruptions.</li>
<li>Ask everyone to write down their concerns, then have each person read theirs out loud.</li>
<li>Say, “We need a dissenting opinion,” and ask someone to challenge the thinking.</li>
</ol>
<p id="ember75" class="ember-view reader-text-block__paragraph">Most importantly, when someone speaks up, respond with gratitude and curiosity:</p>
<p id="ember76" class="ember-view reader-text-block__paragraph">“Thank you.”</p>
<p id="ember77" class="ember-view reader-text-block__paragraph">“Tell me more.”</p>
<p id="ember78" class="ember-view reader-text-block__paragraph">If you don’t, you won’t hear it again.</p>
<p id="ember79" class="ember-view reader-text-block__paragraph">This is how teams move from polite coordination to Uncommon Collaboration—where clarity increases, decisions improve, and momentum builds as a team.</p></div>
			</div>
			</div>
				
				
				
				
			</div>
				
				
			</div>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Why Good Teams Become Guarded</title>
		<link>https://www.markskenny.com/2026/03/11/why-good-teams-become-guarded/</link>
		
		<dc:creator><![CDATA[Mark S. Kenny]]></dc:creator>
		<pubDate>Wed, 11 Mar 2026 15:51:44 +0000</pubDate>
				<category><![CDATA[Blog Posts Recent Col 2]]></category>
		<category><![CDATA[Blog Posts Uncommon]]></category>
		<guid isPermaLink="false">https://www.markskenny.com/?p=15712</guid>

					<description><![CDATA[I’ve spent a lot of time thinking about fragmentation and what causes it. Usually, it comes down to one thing: guardedness.]]></description>
										<content:encoded><![CDATA[<div class="et_pb_section et_pb_section_5 et_section_regular" >
				
				
				
				
				
				
				<div class="et_pb_row et_pb_row_5">
				<div class="et_pb_column et_pb_column_4_4 et_pb_column_5  et_pb_css_mix_blend_mode_passthrough et-last-child">
				
				
				
				
				<div class="et_pb_module et_pb_text et_pb_text_5  et_pb_text_align_left et_pb_bg_layout_light">
				
				
				
				
				<div class="et_pb_text_inner"><p id="ember63" class="ember-view reader-text-block__paragraph">Last week, I talked about the subtle ways that high-performing teams and organizations still feel fragmented.</p>
<p id="ember64" class="ember-view reader-text-block__paragraph">Perhaps you can relate. Work is getting done. Everyone is busy. Meetings are polite. People nod and agree. And then we all go back to our own work.</p>
<p id="ember65" class="ember-view reader-text-block__paragraph">Yet it doesn’t quite feel like we’re moving forward together toward the same goal.</p>
<p id="ember66" class="ember-view reader-text-block__paragraph">Of course, sometimes this is more overt, with obvious friction, which is actually easier, because it’s staring you in the face. More often, fragmentation is subtle, beneath the surface.</p>
<p id="ember67" class="ember-view reader-text-block__paragraph">I’ve spent a lot of time thinking about fragmentation and what causes it. Usually, it comes down to one thing: guardedness. People start protecting and withholding what others need from them.</p>
<p id="ember68" class="ember-view reader-text-block__paragraph">They withhold:</p>
<ul>
<li>Information the rest of the team needs</li>
<li>Presence when the team is under fire</li>
<li>Responsibility when others are ready to step up</li>
<li>Honest truth that would help the team succeed</li>
<li>Grace when someone lets them down</li>
<li>Encouragement and credit when others deserve it</li>
</ul>
<p id="ember70" class="ember-view reader-text-block__paragraph">It’s not a flaw. Guardedness is a very human response to the pressure and change that most teams and organizations are experiencing these days.</p>
<p id="ember71" class="ember-view reader-text-block__paragraph">We’re just protecting our sense of competence, credibility, and control. We want to feel safe.</p>
<p id="ember72" class="ember-view reader-text-block__paragraph">The problem, of course, is that this builds up invisible walls on the team. Often, we’re not intentionally building up walls, but it’s the natural result of people on the team becoming more guarded.</p>
<p id="ember73" class="ember-view reader-text-block__paragraph">While I’ll share the broader solution next week, here’s a simple way to start loosening guardedness on a team.</p>
<p id="ember74" class="ember-view reader-text-block__paragraph">Try this question at the beginning of your next leadership meeting:</p>
<p id="ember75" class="ember-view reader-text-block__paragraph"><strong>What’s one thing that’s taking more energy than expected right now?</strong></p>
<p id="ember76" class="ember-view reader-text-block__paragraph">Go around the table.</p>
<p id="ember77" class="ember-view reader-text-block__paragraph">One sentence each, without discussion or fixing.</p>
<p id="ember78" class="ember-view reader-text-block__paragraph">The “no-fixing” rule is key. It lets people speak without feeling like they&#8217;ve just handed someone a problem to solve.</p>
<p id="ember79" class="ember-view reader-text-block__paragraph">People might mention a project concern, pressure they’re under, a staffing challenge, or even something outside of work that is affecting their focus.</p>
<p id="ember80" class="ember-view reader-text-block__paragraph">When people feel guarded, they protect what they have.</p>
<p id="ember81" class="ember-view reader-text-block__paragraph">The goal isn’t to solve anything in that moment. It’s simply to create a<span class="white-space-pre"> </span><strong>small moment of openness</strong>.</p>
<p id="ember82" class="ember-view reader-text-block__paragraph">Guarded teams protect what they’re carrying. Healthy teams begin to<span class="white-space-pre"> </span><strong>share it.</strong></p>
<p id="ember83" class="ember-view reader-text-block__paragraph">Fragmentation rarely disappears because of one big conversation.</p>
<p id="ember84" class="ember-view reader-text-block__paragraph">It changes when teams experience small moments where people feel safe enough to lower the walls a little.</p>
<p id="ember85" class="ember-view reader-text-block__paragraph">Later, I’ll share a simple framework I’ve been using with leadership teams to help them consistently pass what their colleagues need.</p>
<p>&nbsp;</p></div>
			</div>
			</div>
				
				
				
				
			</div>
				
				
			</div>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>The Subtle Signs Your Team Is Becoming Fragmented</title>
		<link>https://www.markskenny.com/2026/03/04/subtle-signs-your-team-becoming-fragmented/</link>
		
		<dc:creator><![CDATA[Mark S. Kenny]]></dc:creator>
		<pubDate>Wed, 04 Mar 2026 21:07:07 +0000</pubDate>
				<category><![CDATA[Blog Posts Recent Col 3]]></category>
		<category><![CDATA[Blog Posts Uncommon]]></category>
		<guid isPermaLink="false">https://www.markskenny.com/?p=15694</guid>

					<description><![CDATA[High-performing teams can still feel fragmented. Goals are met. People are capable. The organization is functioning. Stuff is getting done. Everyone is busy. But it doesn’t quite feel like we’re moving forward together.]]></description>
										<content:encoded><![CDATA[<div class="et_pb_section et_pb_section_6 et_section_regular" >
				
				
				
				
				
				
				<div class="et_pb_row et_pb_row_6">
				<div class="et_pb_column et_pb_column_4_4 et_pb_column_6  et_pb_css_mix_blend_mode_passthrough et-last-child">
				
				
				
				
				<div class="et_pb_module et_pb_text et_pb_text_6  et_pb_text_align_left et_pb_bg_layout_light">
				
				
				
				
				<div class="et_pb_text_inner"><p>&nbsp;</p>
<p id="ember162" class="ember-view reader-text-block__paragraph">High-performing teams can still feel fragmented.</p>
<p id="ember163" class="ember-view reader-text-block__paragraph">Goals are met. People are capable. The organization is functioning. Stuff is getting done. Everyone is busy. But it doesn’t quite feel like we’re moving forward together.</p>
<p id="ember164" class="ember-view reader-text-block__paragraph">The signs are subtle:</p>
<ul>
<li>Decisions take longer</li>
<li>Energy fades after meetings</li>
<li>People stop contributing ideas</li>
<li>Side conversations replace meaningful team conversations</li>
<li>Little squabbles consume leadership energy</li>
<li>Topics are revisited over and over</li>
</ul>
<p id="ember166" class="ember-view reader-text-block__paragraph">It’s not dysfunction. It’s fragmentation.</p>
<p id="ember167" class="ember-view reader-text-block__paragraph">When pressure increases, people naturally narrow their focus to their own area. Over time, capable people start protecting instead of practicing collaboration.</p>
<p id="ember168" class="ember-view reader-text-block__paragraph">Nothing is exploding. Momentum just quietly slows down and energy subtly fades.</p>
<p id="ember169" class="ember-view reader-text-block__paragraph">If this resonates, here’s a simple way to test this with your team:</p>
<p id="ember170" class="ember-view reader-text-block__paragraph">Ask this question in your next leadership meeting:<span class="white-space-pre"> </span><strong>“Where are we making progress… but not together?”</strong></p>
<p id="ember171" class="ember-view reader-text-block__paragraph">The conversation that follows will tell you a lot. That&#8217;s where Uncommon Collaboration begins.</p>
<p>&nbsp;</p></div>
			</div>
			</div>
				
				
				
				
			</div>
				
				
			</div>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Why High Performing Teams Still Feel Fragmented</title>
		<link>https://www.markskenny.com/2026/02/25/why-high-performing-teams-still-feel-fragmented/</link>
		
		<dc:creator><![CDATA[Mark S. Kenny]]></dc:creator>
		<pubDate>Wed, 25 Feb 2026 21:00:45 +0000</pubDate>
				<category><![CDATA[Blog Posts Recent Col 3]]></category>
		<category><![CDATA[Blog Posts Uncommon]]></category>
		<guid isPermaLink="false">https://www.markskenny.com/?p=15686</guid>

					<description><![CDATA[Your team is smart, capable, and driven. So why does it still feel fragmented?]]></description>
										<content:encoded><![CDATA[<div class="et_pb_section et_pb_section_7 et_section_regular" >
				
				
				
				
				
				
				<div class="et_pb_row et_pb_row_7">
				<div class="et_pb_column et_pb_column_4_4 et_pb_column_7  et_pb_css_mix_blend_mode_passthrough et-last-child">
				
				
				
				
				<div class="et_pb_module et_pb_text et_pb_text_7  et_pb_text_align_left et_pb_bg_layout_light">
				
				
				
				
				<div class="et_pb_text_inner"><p>&nbsp;</p>
<p id="ember741" class="ember-view reader-text-block__paragraph">Your team is smart, capable, and driven. So why does it still feel fragmented?</p>
<p id="ember742" class="ember-view reader-text-block__paragraph">Most leadership teams I work with are capable. They care about results. They’re solving real problems. They’re working incredibly hard.</p>
<p id="ember743" class="ember-view reader-text-block__paragraph">And yet it still feels fragmented.</p>
<p id="ember744" class="ember-view reader-text-block__paragraph">It’s not a lack of talent or skill. It’s divided attention.</p>
<p id="ember745" class="ember-view reader-text-block__paragraph">In many executive meetings, people are physically in the room and mentally somewhere else.</p>
<ul>
<li>Thinking about the latest fire</li>
<li>Preparing their response instead of listening</li>
<li>Carrying tension from an earlier conversation</li>
<li>Clearing email between agenda items</li>
</ul>
<p id="ember747" class="ember-view reader-text-block__paragraph">No one intends to fragment a team, but divided attention quietly does it.</p>
<p id="ember748" class="ember-view reader-text-block__paragraph">When presence is thin, alignment weakens. When alignment weakens, execution slows. Over time, even high-performing teams start to feel disconnected.</p>
<p id="ember749" class="ember-view reader-text-block__paragraph">Not because they lack skill. Because they lack shared attention.</p>
<h3 id="ember750" class="ember-view reader-text-block__heading-3">Try This This Week</h3>
<p id="ember751" class="ember-view reader-text-block__paragraph">At the start of your next leadership meeting, ask:</p>
<p id="ember752" class="ember-view reader-text-block__paragraph">“Before we begin, what’s pulling your attention away from this room right now?”</p>
<p id="ember753" class="ember-view reader-text-block__paragraph">One sentence each. No discussion. No fixing. Just people naming it.</p>
<p id="ember754" class="ember-view reader-text-block__paragraph">It takes three minutes and changes the room:</p>
<ul>
<li>It clears mental clutter</li>
<li>It normalizes the pressure everyone is feeling</li>
<li>It increases focus</li>
<li>It gives people permission to fully show up</li>
<li>It signals that being fully present matters</li>
</ul>
<p id="ember756" class="ember-view reader-text-block__paragraph">Alignment begins with attention, not strategy.</p>
<p id="ember757" class="ember-view reader-text-block__paragraph">Fragmentation isn’t always about priorities. Sometimes it’s about presence.</p>
<p id="ember758" class="ember-view reader-text-block__paragraph">Passing your presence is where Uncommon Collaboration starts. And presence is always a choice.</p>
<p>&nbsp;</p></div>
			</div>
			</div>
				
				
				
				
			</div>
				
				
			</div>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Why Most Weekly Meetings Don’t Drive Momentum</title>
		<link>https://www.markskenny.com/2026/02/19/why-weekly-meetings-do-not-drive-momentum/</link>
		
		<dc:creator><![CDATA[Mark S. Kenny]]></dc:creator>
		<pubDate>Thu, 19 Feb 2026 15:29:57 +0000</pubDate>
				<category><![CDATA[Blog Posts Recent Col 3]]></category>
		<category><![CDATA[Blog Posts Uncommon]]></category>
		<guid isPermaLink="false">https://www.markskenny.com/?p=15674</guid>

					<description><![CDATA[Lately, I’ve been hearing the same story from leadership teams about meetings. Here's how to change the vibe and effectiveness of your meetings.]]></description>
										<content:encoded><![CDATA[<div class="et_pb_section et_pb_section_8 et_section_regular" >
				
				
				
				
				
				
				<div class="et_pb_row et_pb_row_8">
				<div class="et_pb_column et_pb_column_4_4 et_pb_column_8  et_pb_css_mix_blend_mode_passthrough et-last-child">
				
				
				
				
				<div class="et_pb_module et_pb_text et_pb_text_8  et_pb_text_align_left et_pb_bg_layout_light">
				
				
				
				
				<div class="et_pb_text_inner"><p>&nbsp;</p>
<p>Lately, I’ve been hearing the same story from leadership teams: Everyone gathers for the weekly meeting. Each person shares what they’re working on. Everyone nods. The meeting ends.</p>
<p>And very little actually moves forward.</p>
<p>If divisions or groups are struggling to collaborate, I’ll bet the weekly leadership meeting is part of the problem.</p>
<p>Collaboration doesn’t just happen between meetings. It has to happen inside them. If your main leadership forum isn’t driving clarity, decisions, and forward motion, it can become a reporting exercise instead of a momentum builder.</p>
<p>Last month, I sat in on a meeting after we adjusted the structure. It was a very different vibe. You could feel the difference. After speaking to and coaching teams across industries, here are six practical keys to create Uncommon Collaboration in your meetings.</p>
<p>If you want to change the vibe and effectiveness of your meetings, read on.</p>
<ol>
<li><strong> Report on objectives, not everyone’s activity.</strong></li>
</ol>
<p>Somewhere along the way, teams adopted a default structure: “Go around the table and tell us what you’re working on.”</p>
<p>It feels responsible. It sounds thorough. But it’s usually not very helpful.</p>
<p>It doesn’t matter what everyone is busy with. What matters is whether your most important objectives are moving forward.</p>
<p>Shift the conversation from activity to outcomes. Instead of reporting on tasks, review the handful of objectives that truly matter right now.</p>
<ol start="2">
<li><strong> Rate each objective green, yellow, or red.</strong></li>
</ol>
<p>If your team owns monthly financial reports, onboarding targets, compliance deadlines, or customer response times, together rate how those objectives are actually going.</p>
<p>Green: On track.<br />Yellow: At risk.<br />Red: Off track.</p>
<p>Don’t overcomplicate it. Your team already knows the truth.</p>
<p>Rate them quickly. No long explanations or discussion yet. Just clarity.</p>
<ol start="3">
<li><strong> Only spend time on yellow and red.</strong></li>
</ol>
<p>Your team’s time is valuable.</p>
<p>If something is green, you don’t need a 10-minute update. If something is red but already has a clear plan, you may not need discussion either.</p>
<p>What deserves the team’s time?</p>
<ul>
<li>When a decision must be made</li>
<li>When tradeoffs are required</li>
<li>When coordination across divisions is needed</li>
<li>When something is stuck</li>
</ul>
<p>Look at the yellow and red items and decide which ones actually require this group, today. Then discuss them one at a time.</p>
<ol start="4">
<li><strong> Separate tactical from the strategic.</strong></li>
</ol>
<p>We’ve all seen this happen. Someone raises a big idea or a strategic question. Suddenly, 30 minutes disappear on a topic that isn’t connected to this team’s priorities.</p>
<p>Create a visible “Strategic Parking Lot.”</p>
<p>When a strategic or ad-hoc idea surfaces:</p>
<ul>
<li>Capture it.</li>
<li>Don’t debate it.</li>
<li>Move on.</li>
</ul>
<p>At the end of the meeting, decide whether it actually needs a separate session and who should be in that room.</p>
<p>Most won’t.</p>
<p>This simple discipline protects your tactical meeting and keeps it focused.</p>
<ol start="5">
<li><strong> Track decisions and action items in real time.</strong></li>
</ol>
<p>When a decision is made, write it down. When someone commits to action, write it down.</p>
<p>Not in someone’s notebook, but where everyone can see it.</p>
<p>This seems simple. Many teams don’t do it.</p>
<p>A week later, people remember the decision slightly differently. Or no one is quite sure who owned what. It’s a quick way to lose momentum.</p>
<ol start="6">
<li><strong> Finish the meeting intentionally.</strong></li>
</ol>
<p>Don’t just stand up and leave. Before you close:</p>
<ol>
<li>Review the decisions. Did we agree on what we just decided?</li>
<li>Review action items. Who owns what, and by when?</li>
<li>Clarify communication. Who needs to know what from this meeting?</li>
<li>Schedule: Which ad-hoc or strategic meetings do we need?</li>
<li>Ask: What worked well today?</li>
<li>Ask: What would make the next meeting better?</li>
</ol>
<p>Five minutes of discipline here can save hours of confusion later.</p>
<p>&nbsp;</p>
<p>Meetings are where alignment and momentum either strengthens or erodes.</p>
<p>Fixing meetings is one piece of fixing collaboration across divisions.</p>
<p>Many of these principles were shaped by studying under Patrick Lencioni, putting them into practice with teams, and refining them through my own experience.</p>
<p><em>I’ve put together a simple meeting template that walks teams through this structure. If it would be helpful, just <a href="mailto:mark@markskenny.com">email me</a> and I’ll send it over.</em></p>
<p>&nbsp;</p></div>
			</div>
			</div>
				
				
				
				
			</div>
				
				
			</div>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Why Some Smart Teams Still Struggle to Collaborate</title>
		<link>https://www.markskenny.com/2026/02/10/why-some-smart-teams-struggle-to-collaborate/</link>
		
		<dc:creator><![CDATA[Mark S. Kenny]]></dc:creator>
		<pubDate>Tue, 10 Feb 2026 21:58:11 +0000</pubDate>
				<category><![CDATA[Blog Posts Uncommon]]></category>
		<guid isPermaLink="false">https://www.markskenny.com/?p=15649</guid>

					<description><![CDATA[Even with smart people and clear plans, collaboration breaks down when the past is still running the room.]]></description>
										<content:encoded><![CDATA[<div class="et_pb_section et_pb_section_9 et_section_regular" >
				
				
				
				
				
				
				<div class="et_pb_row et_pb_row_9">
				<div class="et_pb_column et_pb_column_4_4 et_pb_column_9  et_pb_css_mix_blend_mode_passthrough et-last-child">
				
				
				
				
				<div class="et_pb_module et_pb_text et_pb_text_9  et_pb_text_align_left et_pb_bg_layout_light">
				
				
				
				
				<div class="et_pb_text_inner"><p>I keep hearing versions of this:</p>
<p>“We meet, we agree, then retreat back to our own roles.” Or “We have brilliant people who don’t want to collaborate.” Or “I wish my people would stop getting so upset and escalating when it feels like someone is stepping on their toes.”</p>
<p>It’s not just frustration. It’s leaders carrying more tension personally, because they’re the ones expected to hold it all together when collaboration slips.</p>
<p>While better methods, clearer strategy, and improved communication matter, what I see most often isn’t a lack of skill or structure. It’s something human underneath it all.</p>
<p>It begins to shift when we decide to see, believe, and behave differently toward each other.</p>
<p><strong>The Starting Point is Grace</strong></p>
<p>And it starts with grace, because we’ve all been hurt, disappointed, or let down in the past.</p>
<p>Grace breaks the cycle of withholding. It interrupts the reflex to protect or attack instead of engaging.</p>
<p>By grace, I don’t mean being soft or grace<em>ful</em>. I’m talking about something much harder.</p>
<p>Grace isn’t pretending the past didn’t happen.</p>
<p>It isn’t minimizing pain or excusing behavior.</p>
<p><strong>Grace is keeping the past from running the future.</strong></p>
<p>And sometimes that means releasing the score even when we are justified in reacting.</p>
<p><strong>The Grace Toll</strong></p>
<p>When we withhold grace from others, it costs something. I call it the <strong>Grace Toll</strong>:</p>
<ul>
<li>Mistakes never quite die.</li>
<li>People get labeled.</li>
<li>We keep score.</li>
<li>Grudges get dragged into every meeting.</li>
<li>Old stories show up in new conversations.</li>
</ul>
<p>Several years ago, I was working with a leadership team who felt disjointed, guarded, and disconnected. I couldn’t figure out why, at first. Then, in the middle of a meeting, a past wrong came rushing back like it had just happened that morning. The lid blew off.</p>
<p>That team didn’t have a communication problem. Something from the past was still shaping how they showed up. And until they extended grace to each other, nothing would change.</p>
<p>Once grace entered the room, conversations moved forward instead of circling the past.</p>
<p><strong>The Choice</strong></p>
<p>This isn’t about ignoring accountability. It’s about removing the invisible friction that keeps teams from moving forward.</p>
<p>Where might grace be needed right now, so that something better can move forward?</p>
<p>What would happen if everyone on your team, your organization, decided to give grace to each other:</p>
<ul>
<li>When mistakes are made</li>
<li>When that unclear email comes in</li>
<li>When something doesn’t feel right</li>
</ul>
<p>When grace becomes a practiced behavior, not a personality trait, teams stop carrying the past into every decision. That’s where Uncommon Collaboration™ begins. And where clarity, trust, and momentum can finally take hold.</p></div>
			</div>
			</div>
				
				
				
				
			</div>
				
				
			</div>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
