<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:googleplay="http://www.google.com/schemas/play-podcasts/1.0"><channel><title><![CDATA[Sean McStay]]></title><description><![CDATA[Writing about decisions, leadership, and the gap between how things look and how they work.]]></description><link>https://www.seanmcstay.com</link><image><url>https://substackcdn.com/image/fetch/$s_!nKSK!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F4721ae5c-8e30-43b8-b65c-dbb578e96d8a_1829x1829.png</url><title>Sean McStay</title><link>https://www.seanmcstay.com</link></image><generator>Substack</generator><lastBuildDate>Wed, 13 May 2026 17:00:24 GMT</lastBuildDate><atom:link href="https://www.seanmcstay.com/feed" rel="self" type="application/rss+xml"/><copyright><![CDATA[Sean McStay]]></copyright><language><![CDATA[en]]></language><webMaster><![CDATA[seanmcstay@hotmail.com]]></webMaster><itunes:owner><itunes:email><![CDATA[seanmcstay@hotmail.com]]></itunes:email><itunes:name><![CDATA[Sean McStay]]></itunes:name></itunes:owner><itunes:author><![CDATA[Sean McStay]]></itunes:author><googleplay:owner><![CDATA[seanmcstay@hotmail.com]]></googleplay:owner><googleplay:email><![CDATA[seanmcstay@hotmail.com]]></googleplay:email><googleplay:author><![CDATA[Sean McStay]]></googleplay:author><itunes:block><![CDATA[Yes]]></itunes:block><item><title><![CDATA[The first story is usually too small]]></title><description><![CDATA[Why a little information can be more dangerous than none at all]]></description><link>https://www.seanmcstay.com/p/the-first-story-is-usually-too-small</link><guid isPermaLink="false">https://www.seanmcstay.com/p/the-first-story-is-usually-too-small</guid><dc:creator><![CDATA[Sean McStay]]></dc:creator><pubDate>Fri, 08 May 2026 13:59:50 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!nKSK!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F4721ae5c-8e30-43b8-b65c-dbb578e96d8a_1829x1829.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>A founder loses a deal and says the market is not ready.</p><p>A sales leader observes three weak conversations and says the team needs better training.</p><p>A manager has one difficult employee and starts redesigning their hiring profile.</p><p>A board hears from two frustrated customers and suddenly everyone is talking about a shift in the market.</p><p>This is how a lot of bad decisions begin. Not with stupidity or laziness or even a lack of information. They begin with a small amount of information that feels larger than it is. When we have no information, we usually know we are guessing. We are cautious and ask more questions. We leave room for uncertainty because the uncertainty is staring us in the face.</p><p>But when we have a little information, our mindset changes. The analytical part of our brain gets involved. It starts connecting dots, filling gaps, building a story, and defending the story before we have enough evidence to know whether the dots belong together in the first place.</p><p>That initial story can feel incredibly convincing. It feels like pattern recognition, and sometimes it is. But most of the time it&#8217;s a proven default habit of our brains to over index small sample sizes into large conclusions.</p><p>One customer says the price is too high. Maybe the price is too high or the value was not clear. Maybe the person you were talking to was never the buyer or the timing was wrong. Maybe this was the wrong customer. Or maybe they say price is the issue because that is the easiest thing to say.</p><p>One team member misses a deadline. Maybe they lack accountability or the expectation was unclear. Maybe they did not have the authority to get it done or they did not understand why it mattered. Maybe they are overwhelmed. Or maybe you avoided the conversation six weeks ago that would have prevented this moment.</p><p>The point is not that the first explanation is always wrong it is that the first explanation is usually incomplete and incomplete explanations are dangerous because they often contain just enough truth to survive.</p><p>Which is what makes them hard to challenge. A completely wrong idea usually collapses quickly under scrutiny whereas a partially true idea can run a company for months. It can shape hiring decisions, sales strategy, product direction, team structure, and leadership behaviour long before anyone realizes the original diagnosis was built on a sample size of almost nothing.</p><p>The problem is not the data point but rather what we do with it. A single data point should make you curious. It should not make you certain.</p><p>That said leaders are often under pressure to sound certain. The team wants confidence, investors want a story, and customers want conviction. The board wants a clean explanation. Nobody wants to hear, &#8220;I&#8217;m not sure yet, but I&#8217;m paying attention.&#8221;</p><p>So the leader turns a single or small group of signals into a narrative.</p><p>The market is price sensitive.</p><p>The team lacks urgency.</p><p>The candidate pool is weak.</p><p>Customers do not get it.</p><p>The timing is wrong.</p><p>So the question becomes: how do you know for sure?</p><p>Most bad decisions do not happen because leaders fail to think. They happen because leaders think too quickly around the wrong centre. They take the first believable explanation and start building around it. They start breaking down the first available wall between them and where they think they want to go.</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.seanmcstay.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe now&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.seanmcstay.com/subscribe?"><span>Subscribe now</span></a></p><p>Once that happens, the explanation becomes sticky. People start gathering evidence to support it. They notice the next customer who complains about price and ignore the one who bought because the value was clear. They notice the next employee who misses a deadline and ignore the part where the system keeps producing for most employees.</p><p>The mind does this naturally. It wants coherence and for the discomfort to end. It wants a story it can hold. The mind is designed to be lazy.</p><p>Being a leader requires the discipline to stay with the unfinished thought a little longer, but not hiding behind it.</p><p>There is a version of &#8220;we need more data&#8221; that is just avoidance. Leaders use it when they are trying not to make a hard call and they keep researching because acting would make them measurable. They ask for one more report, one more meeting, one more round of input, when everyone in the room already knows enough to move.</p><p>That is not wisdom. That is hiding. The real skill is knowing the difference.</p><p>A weak signal deserves an appropriate amount of attention. A repeated pattern d</p><p>eserves a reasonable level of investigation. A real wall deserves decisive action.</p><p>That is where judgment lives. Not in being cautious all the time or in being bold all the time. In knowing what kind of reality you are dealing with. But you cannot do any of that with fog. Fog just keeps you circling. That is what small samples often create: fog with the confidence of fact.</p><p>The leader&#8217;s job is to slow the conversion from signal to story long enough to ask better questions, collect enough data, and to recognize that a few pieces of information can be just as dangerous as no information.</p>]]></content:encoded></item><item><title><![CDATA[McStay on What Matters - 003 - Glenn Lesko and Judgement in leadership]]></title><description><![CDATA[In the third episode of McStay on What Matters, Sean sits down with Glenn Lesko, a partner at Pender and Howe and executive recruitment specialist with nearly three decades of experience finding and assessing senior leaders, to talk about judgment.]]></description><link>https://www.seanmcstay.com/p/mcstay-on-what-matters-003-glenn-916</link><guid isPermaLink="false">https://www.seanmcstay.com/p/mcstay-on-what-matters-003-glenn-916</guid><dc:creator><![CDATA[Sean McStay]]></dc:creator><pubDate>Fri, 08 May 2026 06:00:00 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/197239337/240aff01f7435e5789e36e2b38900678.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p>In the third episode of McStay on What Matters, Sean sits down with Glenn Lesko, a partner at Pender and Howe and executive recruitment specialist with nearly three decades of experience finding and assessing senior leaders, to talk about judgment. What does it actually mean to use good judgment, and how do leaders develop it over time? Glenn shares how understanding an organization goes far deeper than a job description, why the gap between what companies say they need and what they actually need is where the real work begins, and how the best decisions in hiring and in leadership come from staying human in a process that often tries to be anything but.<br><br>Glenn: https://penderhowe.com/en/<br><br>McStay on What Matters is a biweekly podcast about the decisions leaders carry alone and how they navigate them.<br><br>YouTube Link: https://www.youtube.com/@SeanMcStay</p>]]></content:encoded></item><item><title><![CDATA[Trust is not a feeling, it's a working condition]]></title><description><![CDATA[Most companies treat trust like atmosphere. It's actually infrastructure.]]></description><link>https://www.seanmcstay.com/p/trust-is-not-a-feeling-its-a-working</link><guid isPermaLink="false">https://www.seanmcstay.com/p/trust-is-not-a-feeling-its-a-working</guid><dc:creator><![CDATA[Sean McStay]]></dc:creator><pubDate>Wed, 29 Apr 2026 17:56:53 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!nKSK!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F4721ae5c-8e30-43b8-b65c-dbb578e96d8a_1829x1829.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div class="captioned-image-container"><figure><a class="image-link image2" target="_blank" href="https://substackcdn.com/image/fetch/$s_!lDkI!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F54e5067a-142c-4f05-acd8-36043588cd56_1344x256.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!lDkI!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F54e5067a-142c-4f05-acd8-36043588cd56_1344x256.png 424w, https://substackcdn.com/image/fetch/$s_!lDkI!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F54e5067a-142c-4f05-acd8-36043588cd56_1344x256.png 848w, https://substackcdn.com/image/fetch/$s_!lDkI!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F54e5067a-142c-4f05-acd8-36043588cd56_1344x256.png 1272w, https://substackcdn.com/image/fetch/$s_!lDkI!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F54e5067a-142c-4f05-acd8-36043588cd56_1344x256.png 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!lDkI!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F54e5067a-142c-4f05-acd8-36043588cd56_1344x256.png" width="1344" height="256" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/54e5067a-142c-4f05-acd8-36043588cd56_1344x256.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:256,&quot;width&quot;:1344,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:24931,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:&quot;https://mcstayonwhatmatters.substack.com/i/195899811?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F54e5067a-142c-4f05-acd8-36043588cd56_1344x256.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!lDkI!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F54e5067a-142c-4f05-acd8-36043588cd56_1344x256.png 424w, https://substackcdn.com/image/fetch/$s_!lDkI!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F54e5067a-142c-4f05-acd8-36043588cd56_1344x256.png 848w, https://substackcdn.com/image/fetch/$s_!lDkI!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F54e5067a-142c-4f05-acd8-36043588cd56_1344x256.png 1272w, https://substackcdn.com/image/fetch/$s_!lDkI!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F54e5067a-142c-4f05-acd8-36043588cd56_1344x256.png 1456w" sizes="100vw" fetchpriority="high"></picture><div></div></div></a></figure></div><p>Many leaders say they want people to take ownership. Then they create environments where attempts at ownership end in punishment.</p><p>They ask for initiative but second-guess every decision. They ask for honesty but punish the first person who says the thing everyone else was thinking. They ask for innovation but build approval systems where any meaningful deviation requires permission from five people who are not close to the work.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.seanmcstay.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>Then they look around and wonder why the team has become passive.</p><p>The easy explanation is that people do not care enough. Sometimes that is true. More often, they have learned the system. They have learned that waiting is safer than acting. They have learned that the real meeting usually happens after the meeting, because the official room is too risky for the truth.</p><p>That is not a motivation problem. It is a trust problem.</p><p>Research continues to show that trust is not a soft cultural preference. People in high-trust organizations report more energy, higher engagement, better productivity, lower stress, less burnout, and stronger alignment with purpose than people in low-trust organizations. That is not culture work sitting off to the side of the business. That is the business.</p><p>But trust often gets treated like atmosphere. Something nice to have. Something leaders hope exists or assume exists. Something they talk about when engagement scores drop or too many people leave.</p><p>Trust is more practical than that. In a low-trust environment, people burn energy protecting themselves. They manage optics. They soften the email until the point disappears. They hold back the concern because they are not sure what will happen if they name it. They spend the meeting reading faces instead of solving the problem. None of that shows up as a line item, but it is expensive.</p><p>The work still happens, but it happens through friction. And that friction compounds. A concern does not get raised. A decision gets delayed. A customer issue becomes more expensive than it needed to be. Then the company adds another process, another dashboard, another accountability meeting, as if the issue was a lack of management machinery.</p><p>The issue was not process. It was trust.</p><p>Take information sharing. Uncertainty creates stress, and stress undermines the conditions that support trust and cooperation. When people do not know where the business is going, why decisions are being made, or what is actually true, they fill the gaps themselves. Usually with stories worse than reality.</p><p>People notice what is not being said. They notice when the explanation does not match the behaviour. If leadership does not define reality, people will still build one. It will just be less accurate.</p><p>This is also where most people misunderstand what hard work actually costs. There is a difference between challenge stress and chronic stress. A hard, clear, achievable goal can focus a team. It can bring people together and create energy. But vague pressure, moving targets, hidden information, and impossible expectations do something else entirely. They make people protect themselves.</p><p>People do not usually burn out because the work is hard. They burn out because the work is unclear, the rules keep changing, the truth is hard to access, and the people above them pretend not to see it. Hard work with trust is energizing. Hard work without trust is extraction.</p><p>The return on trust is that people stop spending so much of themselves managing the room. More of their judgment becomes available and more of their honesty becomes usable. Their creativity survives contact with the organization.</p><p>If you want people to think clearly, tell the truth, take ownership, and do hard things together, trust is not the reward you get after performance improves.</p><p>It is part of what makes performance possible.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.seanmcstay.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div>]]></content:encoded></item><item><title><![CDATA[The Risk of Showing Up as Someone Else]]></title><description><![CDATA[Most companies think they're paying for professionalism. They're paying for conformity.]]></description><link>https://www.seanmcstay.com/p/the-risk-of-showing-up-as-someone</link><guid isPermaLink="false">https://www.seanmcstay.com/p/the-risk-of-showing-up-as-someone</guid><dc:creator><![CDATA[Sean McStay]]></dc:creator><pubDate>Tue, 28 Apr 2026 18:25:15 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!nKSK!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F4721ae5c-8e30-43b8-b65c-dbb578e96d8a_1829x1829.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>The gap between who you are and who you&#8217;re performing to be isn&#8217;t free. It costs energy, focus, and output. Most people think of it as professionalism. It&#8217;s actually overhead.</p><p>A lot of that overhead is invisible, which is why leaders underestimate it. It does not show up cleanly on a P&amp;L. It shows up in hesitation. In watered-down opinions. In the meeting after the meeting where people finally say what they actually think. In the extra mental effort required to manage how you are landing instead of simply doing the work. When someone is constantly translating themselves into the acceptable version of themselves, that translation has a cost. Energy spent managing perception is energy not spent on judgment, creativity, conflict, or execution.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.seanmcstay.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>This is not theoretical. Yoshino and Deloitte found that 61% of workers actively hide some aspect of themselves at work. Of those who were covering or hiding, 60 to 73% said it was detrimental to their sense of self. That is a remarkable number. People are not being excluded outright. They are being included on terms that require them to edit themselves to stay.</p><p>That distinction matters. Exclusion is easier to identify and easier to condemn. Conditional inclusion is much harder to name because on the surface everything looks fine. The person is in the room. They are employed. They are participating. The organization can tell itself it is open, fair, and modern. But if belonging depends on constant self-editing, the cost is being paid somewhere else.</p><p>Most organizations say they want innovation. Then they quietly reward the people who are best at reading the room and least likely to disturb it. They say they want challenge, but not too much. They say they want honesty but delivered in a way that never creates discomfort. They say they want diversity of thought, then build informal systems that reward sameness of presentation, sameness of tone, and sameness of risk tolerance.</p><p>That is where performance starts to look like professionalism.</p><p>The cost is groupthink, but even that word can sound too abstract. In practice it means slower learning. It means weaker decisions. It means talented people withholding their best observations because they have learned that accuracy without diplomacy is punished, and diplomacy without accuracy is rewarded. It means the loudest conformity signals get mistaken for leadership maturity.</p><p>And this is where the conversation often goes sideways. As soon as you challenge performative professionalism, people assume the alternative is chaos. Oversharing. Emotional mess. No standards. No decorum. No filters. That is not the argument.</p><p>Google&#8217;s Project Aristotle reached a conclusion many leaders still resist because it sounds softer than they want it to: psychological safety was the single most important factor across high-performing teams. Not talent. Not seniority. Not team composition. The teams that performed best were the ones where people felt safe enough to speak honestly, take interpersonal risk, and show up without spending half their energy managing the room. When safety practices were introduced, project completion improved materially. That is not sentiment. That is operating leverage.</p><p>The argument is not that every thought belongs in the room. The argument is that the gap between your real thinking and your expressed thinking should not be so wide that performance becomes your primary job.</p><p>Professionalism has value. Decorum has value. Self-regulation has value. But they stop being assets when they become disguises. The point of professionalism should be to help people work together effectively, not to force everyone into the same narrow performance of seriousness, polish, and emotional neutrality.</p><p>That requires more from leaders than slogans about authenticity. It requires them to stop rewarding the most socially legible version of competence. It requires them to make room for people who are direct, unusual, intense, awkward, or simply not polished in the company dialect. It requires them to distinguish between someone who is unprofessional and someone who is just not performing the expected script.</p><p>That is a harder distinction than most companies want to make.</p><p>Adler&#8217;s idea of separation of tasks is key here. How other people respond to the real you is their task. Your task is to show up fully and do your work well. Once you reverse that and make managing other people&#8217;s reactions your primary concern, you start bleeding energy in every direction. You become less honest, less useful, and usually less effective. The organization loses too, because it is now paying capable people to self-edit instead of contribute.</p><p>The cost of performance at work is not just personal. It is operational. The more energy people spend editing themselves to fit, the less they have left for judgment, creativity, courage, and truth. The less truth in the system, the worse the decisions. The worse the decisions, the more the organization starts mistaking control for competence.</p><p>Most companies think they are paying for professionalism.</p><p>Very often, they are paying for conformity.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.seanmcstay.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div>]]></content:encoded></item><item><title><![CDATA[McStay on What Matters - 002 - Jason Donkersgoed and Reality in Leadership]]></title><description><![CDATA[In the second episode of McStay on What Matters, Sean sits down with Jason Donkersgoed, a leadership coach and consultant with over 30 years of experience leading teams across retail, finance, and higher education, to talk about reality in leadership.]]></description><link>https://www.seanmcstay.com/p/mcstay-on-what-matters-002-jason-fac</link><guid isPermaLink="false">https://www.seanmcstay.com/p/mcstay-on-what-matters-002-jason-fac</guid><dc:creator><![CDATA[Sean McStay]]></dc:creator><pubDate>Thu, 23 Apr 2026 22:00:00 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/197239338/83504b4751c400f32f1b54fdb9542adc.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p>In the second episode of McStay on What Matters, Sean sits down with Jason Donkersgoed, a leadership coach and consultant with over 30 years of experience leading teams across retail, finance, and higher education, to talk about reality in leadership. What happens when leaders avoid naming what everyone already sees? Jason shares what he has learned about surfacing difficult truths, building the trust required for honest conversation, and why the clearest thing a leader can do is often the kindest.<br><br>McStay on What Matters is a biweekly podcast about the decisions leaders carry alone and how they navigate them.</p><p>YouTube Link: https://www.youtube.com/@SeanMcStay</p><p>Jason: https://www.linkedin.com/in/jason-donkersgoed/</p>]]></content:encoded></item><item><title><![CDATA[The candidate who doesn't fit the template.]]></title><description><![CDATA[Varied is not integrated. How to tell the difference in an interview.]]></description><link>https://www.seanmcstay.com/p/the-candidate-who-doesnt-fit-the</link><guid isPermaLink="false">https://www.seanmcstay.com/p/the-candidate-who-doesnt-fit-the</guid><dc:creator><![CDATA[Sean McStay]]></dc:creator><pubDate>Tue, 21 Apr 2026 18:19:19 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!nKSK!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F4721ae5c-8e30-43b8-b65c-dbb578e96d8a_1829x1829.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Picture this. You are a founder working with your board chair on a VP of Sales role. You have narrowed the pool down to two candidates. Tony has fifteen years of experience in the exact area of the industry that your business works in. Predictable path, linear progression. A straight-line safe candidate. Steve however walked a winding path. Multiple industries, three companies over fifteen years and an impressive but unrelated educational background.<br><br>On paper Tony sounds like the safe bet. They will slot into the organization fast, create the type of work that you are used to seeing and your hiring job is done. But there is something you can&#8217;t quite put a finger on about Steve that interests you. During their interview they answered some of your questions in ways you weren&#8217;t expecting, but that made you think. When they were talking about their career and experience, they connected the stops along their road with clarity and precision. Each step that, from the outside, looked disjointed was actually leading them forward. They have a sophisticated but different way of looking at things than you are used to. Your brain is saying Tony is easier to justify, easier to onboard and will do the job. But you are still thinking about Steve. Why? Because Steve is an Integrator.<br><br>Traditional business thought is that specialists like Tony should be the goal. Experience, training, thought processes all aligned with the candidate profile and the expected path through your industry or vertical. Executives and founders hire specialists because they are easier to evaluate, easier to defend, and faster to onboard. Controllers, VPs of Engineering, heads of Legal these are areas where you want someone with a huge depth of experience in that vertical. Specialists exist for a reason. There are roles where deep mastery of a narrow domain is the job. <br><br>Integrators are primed for roles where it is the ability to move between frames that will lead them to success. A specialist can tell you what is happening inside their frame. An Integrator can tell you when the frame itself is wrong, or when something can be borrowed from another area to improve the current one. Senior commercial leadership, general managers, cross-functional roles requiring judgement under ambiguity. In these types of roles experience from other industries, other companies and even other career paths are often the key ingredient to someone&#8217;s success. In complex, shifting environments, breadth of experience outperforms narrow expertise.<br><br>When you are creating your candidate profile you don&#8217;t just need to know what you want them to be able to do. You need to know how well defined the processes are for doing the work, how much room there is for improvement, and what the value might be of having someone with a fresh take look at these items. Leaders often fall into the trap of hiring people who think and act like they do because it feels comfortable. It is precisely because of this that they owe it to their companies to expand the range of who they think could be a fit when the role has room for flexibility and growth.</p><p>So why don&#8217;t more people already look for Integrators? Because they are underpriced in most hiring processes due to the fact that their value shows up over 18 to 36 months, not in the first 90 days. Specialists produce faster. Integrators produce deeper. If the role is a three-month fix, hire a specialist. If the role is a three-year build, hire an Integrator. If the role plays in a kind learning environment with fixed rules, firm regulations and highly standardized processes then a specialist is the way to go. If the role is in a wicked learning environment where the rules are either highly flexible or don&#8217;t exist, regulations are less of a concern and processes are constantly shifting or in need of improvement, then an Integrator with a breadth of experience can be exactly what your business needs.<br><br>So how do you figure out if someone is an Integrator or just a candidate with a non-linear and unconnected career path? Ask them. Ask questions like: <em>walk me through what the different parts of your career have in common. Not chronologically. Thematically</em>. When discussing a success in a previous role ask what they brought from other areas of their background to make that success possible. If they can articulate a through-line that is specific, credible, and tied to the problems they solve, you are looking at an Integrator. If they give you a vague answer or list unrelated experiences, you are looking at someone whose career was varied without being cumulative. Different candidate, different hire. Not wrong, just not an Integrator.<br><br>Hire Integrators for roles that require judgment under ambiguity. If your senior leadership pipeline only rewards specialization, you will produce specialists. Which is great when you need a specialist. However, when the business needs an Integrator, you will have to hire from outside. In that situation be open to that hire. But to get ahead of that for an even better move, start looking within your own organization for opportunities to develop Integrators you already have. Look in different but related departments when you are doing internal hires. Encourage your staff to upskill and learn in multiple areas, not just their current specialty. Look for the people who are making connections between silos and helping things work better, not just the rock stars in a single discipline. Your team will end up better rounded and more adaptable. That is the competitive advantage specialization cannot give you.</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.seanmcstay.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe now&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.seanmcstay.com/subscribe?"><span>Subscribe now</span></a></p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.seanmcstay.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div>]]></content:encoded></item><item><title><![CDATA[McStay on What Matters - 001 - Chris Ballard and Presence in Leadership]]></title><description><![CDATA[In the first episode of McStay on What Matters, Sean sits down with Chris Ballard, former Ontario cabinet minister turned CEO and consultant, to talk about presence in leadership.]]></description><link>https://www.seanmcstay.com/p/mcstay-on-what-matters-001-chris-011</link><guid isPermaLink="false">https://www.seanmcstay.com/p/mcstay-on-what-matters-001-chris-011</guid><dc:creator><![CDATA[Sean McStay]]></dc:creator><pubDate>Fri, 10 Apr 2026 16:00:00 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/197239339/142ef6c47b9cda280fda4ba74837b922.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p>In the first episode of McStay on What Matters, Sean sits down with Chris Ballard, former Ontario cabinet minister turned CEO and consultant, to talk about presence in leadership. What does it actually look like when a leader is fully in the room versus performing being in the room? Chris shares what he learned about presence through politics, public service, corporate governance, and the transition to consulting.<br><br>McStay on What Matters is a biweekly podcast about the decisions leaders carry alone and how they navigate them.</p>]]></content:encoded></item></channel></rss>