<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>Anything we build is due to crumble...</title>
  
  <subtitle>...except when we build up others</subtitle>
  <link href="/atom.xml" rel="self"/>
  
  <link href="http://kevinbrinley.com/"/>
  <updated>2025-08-11T22:52:28.947Z</updated>
  <id>http://kevinbrinley.com/</id>
  
  <author>
    <name>Kevin Brinley</name>
    
  </author>
  
  <generator uri="http://hexo.io/">Hexo</generator>
  
  <entry>
    <title>AI: The Universal Acid</title>
    <link href="http://kevinbrinley.com/AI-The-Universal-Acid/"/>
    <id>http://kevinbrinley.com/AI-The-Universal-Acid/</id>
    <published>2025-08-11T22:51:36.000Z</published>
    <updated>2025-08-11T22:52:28.947Z</updated>
    
    <content type="html"><![CDATA[<h2 id="AI-will-change-everything-and-it’s-up-to-us-to-ensure-it-is-a-change-for-the-better"><a href="#AI-will-change-everything-and-it’s-up-to-us-to-ensure-it-is-a-change-for-the-better" class="headerlink" title="AI will change everything and it’s up to us to ensure it is a change for the better"></a>AI will change everything and it’s up to us to ensure it is a change for the better</h2><p>Imagine for a moment an acid so powerful, so corrosive, that no matter what it comes into contact with, it transforms the other object. Whether it’s glass, plastic, steel, lead, or titanium, it’s transformed from what it was to something entirely different and will make a way through the material. If you had such an acid, what could you do to contain it? No matter what container it’s placed into, the container itself could be transformed. How could you stop such an acid from spreading? How could the universal acid be stopped?</p><p>The short answer is it can’t be stopped. And while thankfully no physical universal acid exists (that we know of), there are concepts that are universal acids. I encountered the concept of universal acids in the book Intrition Pumps by Daniel C. Dennett, which he uses to describe Darwin’s theory of evolution. Taken to the extreme, Darwin’s concept of natural selection has huge ramifications to science, art, history, and philosophy.</p><p>In 2025. Artificial Intelligence, and especially the subset of Generative AI has become a universal acid. It is transforming the way we work, the way we write software, and even the way we drive cars. There is no containing AI. It is here and it is transforming everything. But that doesn’t mean we are doomed to a dystopian future. It is up to us to determine how we will leverage AI, what tasks and agency we choose to give it, and how we partner with it. This 21st century universal acid doesn’t have to be corrosive, but it is up to each of us to learn it and use it responsibly. If we use AI to become a better version of ourselves, we will have gained far more than we lost.</p>]]></content>
    
    <summary type="html">
    
      
      
        &lt;h2 id=&quot;AI-will-change-everything-and-it’s-up-to-us-to-ensure-it-is-a-change-for-the-better&quot;&gt;&lt;a href=&quot;#AI-will-change-everything-and-it’s-up
      
    
    </summary>
    
    
      <category term="AI" scheme="http://kevinbrinley.com/tags/AI/"/>
    
  </entry>
  
  <entry>
    <title>The Agilists Guide to AI</title>
    <link href="http://kevinbrinley.com/The-Agilists-Guide-to-AI/"/>
    <id>http://kevinbrinley.com/The-Agilists-Guide-to-AI/</id>
    <published>2025-07-31T16:07:56.000Z</published>
    <updated>2025-07-31T16:35:27.345Z</updated>
    
    <content type="html"><![CDATA[<p>As Agilists (Scrum Masters, Agile Coaches, Kanban Leads, Release Train Engineers), we serve our teams in many ways, from scheduling and facilitating meetings, doing administrative work following a meeting, and coaching the team. In the following slides, I dive into the many ways in which we can leverage Generative AI to better serve our teams and use it as a thinking tool to improve our teams and ourselves.</p><p>AI, when utilized, has the power to help us get more done with less. But it requires the right mindset and curiosity. To learn more, <a href="https://drive.google.com/file/d/1Ah8iyH1DhbfEpuwouiKVOIVtAlPaBpDV/view?usp=drive_link" target="_blank" rel="noopener">check out my deck on the Servant Leader’s Guide to AI</a>, which I presented at <a href="https://www.cincydeliver.com/Home/Index" target="_blank" rel="noopener">Cincy Deliver</a> on August 1st, 2025.</p>]]></content>
    
    <summary type="html">
    
      
      
        &lt;p&gt;As Agilists (Scrum Masters, Agile Coaches, Kanban Leads, Release Train Engineers), we serve our teams in many ways, from scheduling and f
      
    
    </summary>
    
    
      <category term="AI" scheme="http://kevinbrinley.com/tags/AI/"/>
    
  </entry>
  
  <entry>
    <title>Quantum Meeting</title>
    <link href="http://kevinbrinley.com/Quantum-Meeting/"/>
    <id>http://kevinbrinley.com/Quantum-Meeting/</id>
    <published>2024-12-14T13:18:20.000Z</published>
    <updated>2024-12-14T13:23:12.366Z</updated>
    
    <content type="html"><![CDATA[<h2 id="Resist-the-urge-to-monitor-status-in-meetings-too-frequently"><a href="#Resist-the-urge-to-monitor-status-in-meetings-too-frequently" class="headerlink" title="Resist the urge to monitor status in meetings too frequently"></a>Resist the urge to monitor status in meetings too frequently</h2><p>It was another ‘high stakes’ project. Those types of projects where it felt like, talking to the stakeholders, that the entire future of the company rested on the success of this one project. The work was anything but simple, involving multiple teams and a complex system. Everytime the team meet, more requirements were identified. Leadership became increasingly concerned with status. They joined the team’s daily standups, but a morning update was not enough for leadership, who introduced a second standup at the end of the day to gather additional status updates and remove impediments.</p><p>Unfortunately, I see patterns emerge like this all too often. A project is not progressing according to some plan or arbitrary expectations, so leadership increases the frequency of check- ins. This brings to my mind a quote from the Sci-Fi Cartoon Futurama:</p><blockquote><p>“No fair! You changed the outcome by measuring it.” - Futurama</p></blockquote><p>I term this the ‘Quantum Meeting’. In Quantum Mechanics, the state of a quantum system can be changed just by measuring it. <a href="https://thequantumrecord.com/quantum-computing/observer-effect-why-do-measurements-change-quantum-outcomes/" target="_blank" rel="noopener">The Observer Effect</a> is an interesting challenge in Quantum Mechanics. “The Observer Effect implies the very act of measuring a quantum system by observation can alter its behavior.”</p><p>This sounds a lot like what occurs in our own quantum meetings with a team and leadership ‘observing’. A team under observation by leadership in a meeting will inherently alter their behavior. The extent of the alteration will depend on a number of factors, such as the psychological safety of the team, their relationship with leadership, the leaders themselves, and the personalities of the team members.</p><p>At times, additional meetings are needed as the team rapidly learns, encounters impediments, and needs to stay aligned as a team. Leadership may be able to assist in removing impediments, but remember, leadership’s mere presence in observing the team alters its behavior. Be careful to apply the quantum meeting and carefully consider if the negative consequences of altering the behavior are outweighed by the benefits.</p>]]></content>
    
    <summary type="html">
    
      
      
        &lt;h2 id=&quot;Resist-the-urge-to-monitor-status-in-meetings-too-frequently&quot;&gt;&lt;a href=&quot;#Resist-the-urge-to-monitor-status-in-meetings-too-frequently
      
    
    </summary>
    
    
      <category term="Leadership" scheme="http://kevinbrinley.com/tags/Leadership/"/>
    
  </entry>
  
  <entry>
    <title>Roadmaps and Backlogs</title>
    <link href="http://kevinbrinley.com/Roadmaps-and-Backlogs/"/>
    <id>http://kevinbrinley.com/Roadmaps-and-Backlogs/</id>
    <published>2024-12-01T19:12:01.000Z</published>
    <updated>2024-12-01T19:12:01.850Z</updated>
    
    <content type="html"><![CDATA[<h2 id="A-roadmap-provides-a-visual-statement-of-where-we-are-taking-a-product-and-a-backlog-gets-us-there"><a href="#A-roadmap-provides-a-visual-statement-of-where-we-are-taking-a-product-and-a-backlog-gets-us-there" class="headerlink" title="A roadmap provides a visual statement of where we are taking a product and a backlog gets us there"></a>A roadmap provides a visual statement of where we are taking a product and a backlog gets us there</h2><p>Agile development spends a considerable effort on defining a backlog, but spends little time on roadmaps. This can give the impression that a roadmap is outside of the agile software development lifecycle. But that’s far from reality. A good roadmap sets the vision of a product and a backlog is the actionable expression of work for a team to undertake to achieve the vision.</p><p>In the ideal flow, a roadmap is created, the backlog is populated, development starts, and features are delivered. The each step builds upon the previous step. In the flow of work, we rely on work to be broken down, taking the roadmap and building out a backlog.</p><p>Building a roadmap and building a backlog require two different sets of skills and more importantly, different decisions to be made. A roadmap is typically crafted in conjunction with stakeholders and product/engineering leadership. It requires an understanding of the market the product and business operates within and deciding what opportunities to pursue. Most roadmaps also include a sense or indication of time, and thus require an estimate on effort, either well informed by consulting the engineering teams by analyzing the ask and crafting an estimate based on the understanding. Or, lacking the time or effort, a random guess is applied and the roadmap is adjusted later.</p><p>Building a backlog, by contrast, requires understanding the problem to be solved and enough details of the solution to sequence work and identify dependencies. It’s a collaboration between product and engineering, requiring both parties to contribute, on one side the problem and the constraints around the potential solution, and on the other side a solution that is actionable and solves the given problem.</p><p>Product team members are more heavily involved in upfront activities and transition the knowledge and activities to the engineering team members. Roadmapping is largely a product activity with some engineering consultation. Crafting the backlog is a joint exercise between product and engineering. Development then is a largely engineering effort with some product consultation. Release and support is largely an engineering function with some product consultation as needed.</p><p>Delivery can happen without a roadmap, but it cannot happen without a backlog. Without the collaboration between product and engineering to explore problems and craft solutions, the development team cannot plan yet alone build a solution for the business or customer.</p><p>That’s not to say that a roadmap is completely useless. A roadmap sets the vision for where we are taking a product. This gives the development teams a sense of purpose and direction. It also aids in the solutioning of current work, giving an indication of how the teams may have to evolve the system in the future.</p><p>The key audience for a Roadmap however is the stakeholders. Stakeholders responsible for budgeting decisions. Stakeholders who set organicational direction. Stakeholders who must make marketing plans, training documents, and staffing decisions. A roadmap is a sales pitch and a communication device, meant largely for the broader organization to consume. In many cases, its necessary to receive funding or justify continued investment in a product.</p><p>Roadmaps and backlogs are intricately linked. A roadmap sets the visuion while a backlog organizes the desired roadmap into an executable plan. While it’s rare that a backlog could exist without a roadmap, a roadmap cannot be realised without a backlog. Both are necessary for a well-functioning and evolving product.</p>]]></content>
    
    <summary type="html">
    
      
      
        &lt;h2 id=&quot;A-roadmap-provides-a-visual-statement-of-where-we-are-taking-a-product-and-a-backlog-gets-us-there&quot;&gt;&lt;a href=&quot;#A-roadmap-provides-a-v
      
    
    </summary>
    
    
  </entry>
  
  <entry>
    <title>Nature of Agile Leadership</title>
    <link href="http://kevinbrinley.com/Nature-of-Agile-Leadership/"/>
    <id>http://kevinbrinley.com/Nature-of-Agile-Leadership/</id>
    <published>2024-11-04T22:02:12.000Z</published>
    <updated>2024-11-04T22:02:12.421Z</updated>
    
    <content type="html"><![CDATA[<h2 id="Striking-the-right-balance-takes-skill-and-patience"><a href="#Striking-the-right-balance-takes-skill-and-patience" class="headerlink" title="Striking the right balance takes skill and patience"></a>Striking the right balance takes skill and patience</h2><p>Conventional Leadership wisdom states that one shouldn’t care what people think of them. “You can’t please all people”, nor should you try. When leading, one must focus on providing a direction, lead the way there, and manage the team on the journey.</p><p>This doesn’t mean a leader should be reckless in how they treat their people. If you treat your team poorly, they will leave, stop following you, or become demotivated and accomplish less. A better way to state the conventional wisdom is that you should care about your team’s general sentiment, but you shouldn’t care how individuals feel about you.</p><p>As a leader, your job isn’t to make people like you. Together, we have to get a mission to accomplish. In software development, that’s the delivery of software updates to provide value to the business and the customer.</p><p>Agile leaders find themselves in a predicament. Agile leaders, especially one asked to work permanently with a team in a specific capacity, such as a Scrum Master or Release Train Engineer, lead largely with influence. In order to influence others, one must have a relationship in which one has earned a certain level of trust with the other person. Trust is earned slowly and can disappear in an instant.</p><p>Agile Coaches, brought in for an engagement, are a bit different. While they tend to lead largely with influence, they are “gifted” authority by the leader who brings him or her in for the engagement. The more authority the leader has, the more authority the coach will have. Though, this will deteriorate if the leader disengages or distances themselves from the coach.</p><p>So how can an agile leader build trust without focussing solely on getting everyone to like them? First, it’s important to remember that <a href="/The-Duality-of-Servant-Leadership/">an agile leader is a Servant Leader</a>, which means they have a vision and they serve to that vision. Agile leaders cannot just become servants to the team. Going down that path blindly is like trying to please everyone and ultimately, you may please no one.</p><p>Second, high Emotional Intelligence (EQ), is critical for an Agile Leader. One needs to not only be aware of their own emotions, but also be aware and adept of observing and navigating the emotions of others. As an agile leader, you may have to give bad news or critical feedback. Having high EQ will help in navigating challenging situations like this where people may not like you or like what you have to say, but will respect and trust you for delivering it.</p><p>Finally, I’ve found consistency to be key in building trust. Do what you say you will do. Develop strong routines and be a person that people can rely on. If you are a person who gets things done, people will notice and begin to trust with with larger and larger items. </p><p>When I started my agile leadership journey, I devoted a lot of my time in trying to get everyone on my team to like me. When I sensed someone didn’t like me, I would go out of my way to try to get them to like me, which ultimately made me less effective in influencing and leading the rest of the team. As an agile leader, your job is not to be liked, but to help the team become the best version of itself it can be. The team may not like you for it, but in the end, they will respect you for it.</p>]]></content>
    
    <summary type="html">
    
      
      
        &lt;h2 id=&quot;Striking-the-right-balance-takes-skill-and-patience&quot;&gt;&lt;a href=&quot;#Striking-the-right-balance-takes-skill-and-patience&quot; class=&quot;headerlin
      
    
    </summary>
    
    
      <category term="Leadership" scheme="http://kevinbrinley.com/tags/Leadership/"/>
    
  </entry>
  
  <entry>
    <title>On Agile Certifications</title>
    <link href="http://kevinbrinley.com/On-Agile-Certifications/"/>
    <id>http://kevinbrinley.com/On-Agile-Certifications/</id>
    <published>2024-10-20T23:30:59.000Z</published>
    <updated>2024-10-20T23:30:59.726Z</updated>
    
    <content type="html"><![CDATA[<h2 id="Life-long-learners-meet-an-industry-flooded-with-certifications"><a href="#Life-long-learners-meet-an-industry-flooded-with-certifications" class="headerlink" title="Life-long learners meet an industry flooded with certifications"></a>Life-long learners meet an industry flooded with certifications</h2><p>A collegue once bemoaned that so many agilists collect certifications like baseball cards. With such a proliferation of Agile certifications from Scrum Alliance, Scrum.org, ICAgile, Scaled Agile, and PMI to name a few, it’s easy to see how the agile community garners this impression. And when you encounter a few people who’s email signuature contains more letters after their name than in it, you come face-to-face with the explosion of certifications exists in our industry.</p><p>On one hand, the proliferations of all of these agile certifications is simple economics. Businesses demand agile and Scrum experts and certifications are an easy way to demonstrate knowledge of agile. And if employers are demanding these certifications, then employees (and employers) will pay for them. And if enough demand exists, organizations will rise up to supply.</p><p>The very nature of agile development instills a culture of experimentation and learning. In my experience, most agilists are life long learners and always seek new sources of information and opportunties to learn. Some, like myself, seek that learning from books and first hand experience. Others flourish on conferences and meetup groups. Yet others seek certifications as way to build their resume and brand to the world, seeking outside validation that they possess a specific aspect of knowledge and skills that are useful to an organization.</p><p>For those already with agile certifications, additional certifications provide one more benefit - reminding attendees of the agile basics. We all get caught up in our day-to-day operations and get bogged down in office politics. We become blind to the sacrifices we have made in order to get work done. Sometimes we take shortcuts. Sometimes, we become the evil that we sought to vanguish. At times, it takes returning to the source material on order for us to notice or recognize what we are doing wrong. At other times, we need the energizing interaction that comes from agile certifications, training, or conferences.</p><p>Certifications play a unique role in our industry. They serve a dual purpose in providing training and recognition for the mastery of a topic. They also serve as a marketing tool to help spread a particular framework, mindset, process, or tool. This can be seen most clearly if we go back to the early days of agile, when XP and Scrum were the main frameworks. Scrum embraced certifications as a way to rapidly train new experts in the framework. XP choose to forego certifications, taking a more skeptical view of their usefulness, likely born out of the general negative opinion developers had of certifications in the late 90s and early 2000s. If we look at the landscape now, Scrum is widely embraced and XP exists only in pockets and in specific practices like pair programming.</p><p>Certifications in the agile community is the prevailing standard. Applying for a new Scrum Master or Release Train Engineer position will require a certification. Even XP has made the pivot, with XP certifications now available from the Extreme Programming Alliance. While others may bemoan the state of our industry, it’s up to each of us to decide how we’ll shape our career, embracing the certifications or finding another way to showcase our expertise and our commitment to life-long learning.</p>]]></content>
    
    <summary type="html">
    
      
      
        &lt;h2 id=&quot;Life-long-learners-meet-an-industry-flooded-with-certifications&quot;&gt;&lt;a href=&quot;#Life-long-learners-meet-an-industry-flooded-with-certific
      
    
    </summary>
    
    
      <category term="Certifications" scheme="http://kevinbrinley.com/tags/Certifications/"/>
    
  </entry>
  
  <entry>
    <title>Defining the Acceptance Criteria for your meetings</title>
    <link href="http://kevinbrinley.com/Defining-the-Acceptance-Criteria-for-your-meetings/"/>
    <id>http://kevinbrinley.com/Defining-the-Acceptance-Criteria-for-your-meetings/</id>
    <published>2024-08-06T21:21:31.000Z</published>
    <updated>2024-08-06T21:21:31.357Z</updated>
    
    <content type="html"><![CDATA[<h2 id="Given-the-meeting-has-acceptance-criteria-when-the-last-acceptance-criteria-is-meet-then-the-meeting-ends"><a href="#Given-the-meeting-has-acceptance-criteria-when-the-last-acceptance-criteria-is-meet-then-the-meeting-ends" class="headerlink" title="Given the meeting has acceptance criteria, when the last acceptance criteria is meet, then the meeting ends"></a>Given the meeting has acceptance criteria, when the last acceptance criteria is meet, then the meeting ends</h2><p>In my last post, I talked about the <a href="/Story-Driven-Meetings">utility of defining a meeting as a user story</a>, using the classic ‘As a {who}, I want to {outcome} so that {purpose}’ to convey the meeting’s purpose for existing, what it should achieve, and who benefits. Leveraging this format clearly informs the audience of the important details and also<br>sets a clear vision for you as the meeting organizer. </p><p>We can take the analogy a step further and add an additional tool common to user stories - acceptance criteria. Just like in a user story, a meeting acceptance criteria defines the conditions for when the meeting is over. When all of the conditions have been met, the meeting is over. Too often, meetings run to fill the time allotted. Having clearly defined acceptance criteria for their ending gives a framework for the meeting leader or team to call the meeting early.</p><p>The format in which you write the acceptance criteria can vary. You can try the ‘Gerkin’ format like that I used above that follows the ‘Given - When - Then’ syntax. While this format works well for development user stories, I find it challenging to adapt for a meeting. Instead, I prefer to think of the acceptance criteria for a meeting like a checklist. Once each bullet in the checklist has been completed, the meeting can be considered done and the attendees can move on with their day.</p><h2 id="Examples"><a href="#Examples" class="headerlink" title="Examples"></a>Examples</h2><p>Here are a few examples for a few common meetings:</p><h3 id="Daily-Standup"><a href="#Daily-Standup" class="headerlink" title="Daily Standup"></a>Daily Standup</h3><ul><li>Everyone has discussed their plan for the day</li><li>All impediments that have been identified have a plan to discuss or resolve</li><li>The sprint board has been updated to match the current state</li></ul><h3 id="Sprint-Review"><a href="#Sprint-Review" class="headerlink" title="Sprint Review"></a>Sprint Review</h3><ul><li>Team shares the outcome of the sprint</li><li>Any functional demos are shared</li><li>Any feedback is captured or a plan for discussion has been agreed upon</li></ul><h3 id="One-on-One"><a href="#One-on-One" class="headerlink" title="One on One"></a>One on One</h3><ul><li>All current prerformance and improvement goals have been discussed</li><li>Any feedback for maanger or team member has been shared</li></ul><h2 id="Final-thoughts"><a href="#Final-thoughts" class="headerlink" title="Final thoughts"></a>Final thoughts</h2><p>Just as there are many ways to craft a user story, there are many ways to craft a meeting invite. Don’t get caught up in the nuances of the format, nor with following the analogy of a user story meeting to the full extent. The analogy itself should provide value, and so long as the acceptance criteria is clear and helps us determine if the meeting is over and if it completed its outcome, then the analogy has served its purpose.</p><p>If you haven’t tried this technique, test it out with your next meeting and see if it helps you convey the purpose and outcome to the meeting attendees, keeps the meeting on track, and provide a clear signal that it is over.</p>]]></content>
    
    <summary type="html">
    
      
      
        &lt;h2 id=&quot;Given-the-meeting-has-acceptance-criteria-when-the-last-acceptance-criteria-is-meet-then-the-meeting-ends&quot;&gt;&lt;a href=&quot;#Given-the-meeti
      
    
    </summary>
    
    
      <category term="Facilitation" scheme="http://kevinbrinley.com/tags/Facilitation/"/>
    
  </entry>
  
  <entry>
    <title>Story Driven Meetings</title>
    <link href="http://kevinbrinley.com/Story-Driven-Meetings/"/>
    <id>http://kevinbrinley.com/Story-Driven-Meetings/</id>
    <published>2024-08-04T21:22:28.000Z</published>
    <updated>2024-08-04T21:30:57.207Z</updated>
    
    <content type="html"><![CDATA[<h2 id="As-a-meeting-organizer-I-want-to-provide-meeting-attendees-with-a-clear-concise-statement-of-our-purpose-and-outcome-so-that-they-understand-the-purpose-and-importance-of-the-meeting"><a href="#As-a-meeting-organizer-I-want-to-provide-meeting-attendees-with-a-clear-concise-statement-of-our-purpose-and-outcome-so-that-they-understand-the-purpose-and-importance-of-the-meeting" class="headerlink" title="As a meeting organizer, I want to provide meeting attendees with a clear, concise statement of our purpose and outcome, so that they understand the purpose and importance of the meeting"></a>As a meeting organizer, I want to provide meeting attendees with a clear, concise statement of our purpose and outcome, so that they understand the purpose and importance of the meeting</h2><p>If you were to perform an audit of the meetings on your calendar, how many of them would have an agenda and a description? Of those that did have a description and agenda, how many of them provide a clear indication of the outcome of the meeting, who benefits from the meeting, and the clear steps we’ll follow along the way?</p><p>If you’re like me, most of the meetings on your calendar fail to meet these criteria. Sometimes, that’s because we’re busy and juggling multiple priorities. Other times, it’s because we didn’t put the preparation in for the meeting.</p><p>Meetings are painful, but they don’t have to be. Better meetings starts with preparation. And you can showcase your preparation to the attendees with the first thing they will see about the meeting: the meeting invite.</p><p>The best way I’ve found to capture the outcome and other important details of a meeting is to frame it like a user story, as <a href="https://mattphilip.wordpress.com/2013/03/26/user-story-narrative-for-meeting-invitations/" target="_blank" rel="noopener">suggested by Matt Philip and others over a decade ago</a>. The user story format is one that most teams are familiar with and if it captures enough background and context for development of complex software, can we make it work for complex, collaborative meetings?</p><p>The basic user story format is:</p><blockquote><p>As a {Who}, I want to {Outcome}, so that {Purpose}</p></blockquote><h2 id="Who"><a href="#Who" class="headerlink" title="Who"></a>Who</h2><p>In our meeting as a user story, who could refer to 2 different groups; the group of attendees or the group that ultimately benefits from the meeting in the first place.</p><p>The simplest approach is to find a name to call the group of attendees. This is simple when we’re working with a development team. The next level approach, and a powerful technique, is to consider and name who benefits from the meeting. The audience benefits in some fashion, but who else beyond the audience? Leadership and stakeholders can benefit, but where possible, I like to consider the meeting from the customer’s perspective and frame the meeting in terms of how it benefits them.</p><h2 id="Outcome"><a href="#Outcome" class="headerlink" title="Outcome"></a>Outcome</h2><p>When we’re done with this meeting, what will we have achieved together? Sometimes, this is framed more of an output, such as a list of activites This approach has its place, but where possible I try to capture how we’re impacting the ‘who’ with the work that we are doing. Try to consider beyond the superficial surface activities if you can - those can always be captured further down in the description of the meeting.</p><h2 id="Purpose"><a href="#Purpose" class="headerlink" title="Purpose"></a>Purpose</h2><p>Purpose is the ‘so what’ portion of the user story. Why does this meeting matter? As an attendee, why do I care about the outcome and the person who benefits from it? This isn’t the same as ‘what’s in it for me’, but really more what’s in it for the borader organization. How does what we do in this meeting and achieving the outcome help us collectively achieve a broader goal?</p><h2 id="Examples"><a href="#Examples" class="headerlink" title="Examples"></a>Examples</h2><p>Here’s a couple examples for a few common meetings:</p><h3 id="Daily-Standup"><a href="#Daily-Standup" class="headerlink" title="Daily Standup"></a>Daily Standup</h3><ul><li>As a team, we want to review what we accomplished yesterda, what we plan to accomplish today, and what blockers we have so that we can stay aligned on the goal for the team’s sprint.</li></ul><p>This format lists outputs instead of outcomes. A next level user story for a daily standup would be</p><ul><li>As a team, we want to ensure we are aligned on our plan for the day so that we can monitor our progress on our sprint goal and pivot if necessary.</li></ul><h3 id="Sprint-Review"><a href="#Sprint-Review" class="headerlink" title="Sprint Review"></a>Sprint Review</h3><ul><li>As a stakeholder, I want to review the Team’s progress, provide feedback, and adjust the backlog so that we ensure we’re developing the most valuable solution for our customers.</li></ul><h3 id="One-on-One"><a href="#One-on-One" class="headerlink" title="One on One"></a>One on One</h3><ul><li>As a team member, I want to meet with my manager to discuss current challenges, understand priorities, and talk about career advancement, so that I can grow and better serve the organization and customer.</li></ul><h2 id="Closing-thoughts"><a href="#Closing-thoughts" class="headerlink" title="Closing thoughts"></a>Closing thoughts</h2><p>Writing meeting descriptions in the user story is just the first step. A user story ussually contains acceptance criteria which further defines what is in scope for the user story. We can apply this to our meetings too, giving ourselves and the attendees a clear defintion of when the meeting is over. Approaching a meeting like a user story can help keep a meeting on point while giving us a clear purpose and outcome to work towards.</p>]]></content>
    
    <summary type="html">
    
      
      
        &lt;h2 id=&quot;As-a-meeting-organizer-I-want-to-provide-meeting-attendees-with-a-clear-concise-statement-of-our-purpose-and-outcome-so-that-they-un
      
    
    </summary>
    
    
      <category term="Facilitation" scheme="http://kevinbrinley.com/tags/Facilitation/"/>
    
  </entry>
  
  <entry>
    <title>Curating Better Meetings</title>
    <link href="http://kevinbrinley.com/Curating-Better-Meetings/"/>
    <id>http://kevinbrinley.com/Curating-Better-Meetings/</id>
    <published>2024-07-27T12:44:29.000Z</published>
    <updated>2024-07-27T12:49:36.832Z</updated>
    
    <content type="html"><![CDATA[<h2 id="POWER-through-meeting-preparation"><a href="#POWER-through-meeting-preparation" class="headerlink" title="POWER through meeting preparation"></a>POWER through meeting preparation</h2><p>Museum curators are responsible for collecting artifacts and the information behind them, caring for the artifacts and the stories behind them. Museum curtors then find a creative way to share the story. </p><p>As a meeting facilitator, we too are responsible for collecting and caring for information while finding a way for our meeting attendees to interact with the information, all in service to a purpose and outcome. Key to caring for this information is preparing for the meeting. In doing so there are 5 key items to preparation, captured in the acronym POWER</p><ul><li>Purpose - Why does this meeting exist?</li><li>Outcome - What outcome are we working towards?</li><li>who -who benefits from this meeting and who is necessary</li><li>Execute -How to execute the meeting to accomplish the outcome?</li><li>Role -what role do I play in this meeting? </li></ul><p>This is a start to coneting a better meeting. To learn more, <a href="/docs/CuratingBetterMeetingsDeck.pdf">check out my deck on Curating Better Meetings</a>, which I presented at Cincy Deliver on July 26th, or stay tuned her for more on how to prepare and execute great meetings.</p>]]></content>
    
    <summary type="html">
    
      
      
        &lt;h2 id=&quot;POWER-through-meeting-preparation&quot;&gt;&lt;a href=&quot;#POWER-through-meeting-preparation&quot; class=&quot;headerlink&quot; title=&quot;POWER through meeting prep
      
    
    </summary>
    
    
      <category term="Facilitation" scheme="http://kevinbrinley.com/tags/Facilitation/"/>
    
  </entry>
  
  <entry>
    <title>POWER through meeting preparation</title>
    <link href="http://kevinbrinley.com/POWER-through-meeting-preparation/"/>
    <id>http://kevinbrinley.com/POWER-through-meeting-preparation/</id>
    <published>2024-07-17T15:07:40.000Z</published>
    <updated>2024-07-17T15:12:53.731Z</updated>
    
    <content type="html"><![CDATA[<h2 id="Effective-meetings-require-preparation-and-forethought-from-the-organizer"><a href="#Effective-meetings-require-preparation-and-forethought-from-the-organizer" class="headerlink" title="Effective meetings require preparation and forethought from the organizer"></a>Effective meetings require preparation and forethought from the organizer</h2><p>Ask any Software Engineer what they’re least favorite part of their job is, and on that list will be meetings. Meetings are crucial to bring people together to collaborate, share information, or make decisions, but are universally loathed.</p><p>How can we make meetings better? The key is proper preparation. For novel, important meetings, <a href="/Meeting-Prep/">I will devote anywhere from 1 to 3 times the length of the meeting to prepare for it</a>. So, for a 1 hour meeting, I’ll prepare anywhere from 1 to 3 hours. I don’t follow this rule for recurring meetings, but I do spend some time preparing for each meeting. When establishing a recurring meeting or a novel meeting, I’ll pause to consider 5 important elements: the meeting’s purpose, the outcome, who needs to be involved and who benefits from the meeting, how I will execute the meeting, and the role I will play in the meeting.</p><h2 id="Purpose"><a href="#Purpose" class="headerlink" title="Purpose"></a>Purpose</h2><p>First I consider why the meeting exists in the first place. What larger purpose does the meeting play? What would happen if the meeting didn’t occur at all? When we rush through scheduling meetings, clarifying the purpose the meeting serves is often the first thing we neglect. But if you want the meeting to be valuable, you need to clarify the value it provides both for your attendees and for your self.</p><h2 id="Outcome"><a href="#Outcome" class="headerlink" title="Outcome"></a>Outcome</h2><p>Second I consider what outcome does this meeting need to achieve? Is this an informational sharing meeting? Are we introducing a new change? Are we collaborating on a solution? Or are we making a decision? These are a few of the common outcomes I encounter, but there are many more. Be concrete in what outcome the meeting should achieve, that way you and the attendees know when the meeting is over. Otherwise, with an unclear outcome, the meeting risks filling all of the space we allot for it.</p><h2 id="Who"><a href="#Who" class="headerlink" title="Who"></a>Who</h2><p>Next I consider who benefits from this meeting. Who is the chief benefactor for this meeting? If the purpose and outcome are clear, who benefits from the meeting should be obvious. As a facilitator, it is helpful for me to keep the benefactor in mind as I hold the meeting to center myself and consider how they would think of the progress we are making.</p><p>Also part of ‘who’, I consider who needs to attend this meeting. Who has the information we need in this meeting? Who needs to be present to hear the information? Who must make the decision? Understanding the purpose and outcome first helps us consider who is necessary for the meeting so we can limit the attendee list to the smallest group possible while still achieving the outcome.</p><h2 id="Execute"><a href="#Execute" class="headerlink" title="Execute"></a>Execute</h2><p>With the outcome and the attendee list formulated, I then consider how I will execute the meeting. If collaboration is necessary, how will we engage all of the attendees? What is the journey that I and the attendees must take together in this meeting to ensure we reach the end of the meeting and achieve our objective? What conversations, questions, or decisions need to be made along the way, and how do I best support the group for those discussions?</p><h2 id="Role"><a href="#Role" class="headerlink" title="Role"></a>Role</h2><p>Finally, I consider what my role is in the meeting. As the organizer of the meeting, am I in a pure ‘facilitator’ role, or is there some secondary role that I may play, such as coach? What else must I do to prepare for the role(s) that I will be playing? What dangers may I encounter with the role(s) I am playing and if I am playing multiple roles, what confusion or problems may that cause?</p><h2 id="Conclusion"><a href="#Conclusion" class="headerlink" title="Conclusion"></a>Conclusion</h2><p>Meeting preparation is crucial in setting the ground work for a successful meeting. Preparation will give you, as the meeting organizer, increased confidence stepping into the room that you’re meeting for the right reasons and working towards the proper outcome. For the next meeting you organize, consider POWERing through the preparation to make it a better meeting.</p>]]></content>
    
    <summary type="html">
    
      
      
        &lt;h2 id=&quot;Effective-meetings-require-preparation-and-forethought-from-the-organizer&quot;&gt;&lt;a href=&quot;#Effective-meetings-require-preparation-and-fore
      
    
    </summary>
    
    
      <category term="Facilitation" scheme="http://kevinbrinley.com/tags/Facilitation/"/>
    
  </entry>
  
  <entry>
    <title>Metrics and Intuition</title>
    <link href="http://kevinbrinley.com/Metrics-and-Intuition/"/>
    <id>http://kevinbrinley.com/Metrics-and-Intuition/</id>
    <published>2024-07-14T12:53:00.000Z</published>
    <updated>2024-07-14T12:53:00.524Z</updated>
    
    <content type="html"><![CDATA[<h2 id="A-Metric-without-context-is-just-a-number"><a href="#A-Metric-without-context-is-just-a-number" class="headerlink" title="A Metric without context is just a number"></a>A Metric without context is just a number</h2><p>In the 21st century, metrics are king. What organization isn’t informed or focused on metrics, relying on them to keep score, identify problems, and implement solutions? Metrics allow you to ask better questions, but they require interpretation. A metric without any context is just a number. One cannot make a decision knowing only a metric and without any other information. </p><p>For instance, if you were car shopping and all you knew was Car A had a highway fuel mileage of 32 while Car B had a highway fuel mileage of only 25? With just that information, would you be willing to buy Car A? Hopefully not, especially when I tell you Car A is a <a href="https://en.wikipedia.org/wiki/Ford_Pinto" target="_blank" rel="noopener">1978 Ford Pinto</a>.</p><p>If I said a particular scrum team had a velocity of 9, what use is the number alone? What’s the first thing that comes to mind when we consider that team? Do you, (like me) immediately jump to a conclusion? A better approach is to consider what questions to ask, questions that put the number into context such as</p><ul><li>How many people are on the team?</li><li>How long has the team existed in it’s current form</li><li>What’s the seniority of the team?</li><li>How does the team point stories?</li></ul><p>The answers to these questions may spawn other questions. For instance, if I respond to the last question that each story is pointed as a 1 and the team follows a “No Estimates” approach, you’ll want to know more and consider asking for additional metrics, such as cycle time and cummulative flow to further dig into how the team is perforiming.</p><p>Intuition and context play a huge role with metrics. Metrics should not replace smart people with their intuition nor should we rely solely on our intuition and observations alone. For those on-the-ground working the code, their intuition will point out where the problems lie. Sometimes these problems are obvious in the metrics. For many of the teams I work with, there is a bottleneck in delivery right after development completes. I see it each day looking at our Kanben board and from our conversations. The metrics also back up my observations, though it doesn’t come across as a large of a problem in the metrics as my intuition says it is.</p><p>Metrics also help us see patterns we have not seen before. Paired with our observations, metrics may help us articulate a challenge in ways to influence leadership action. Metrics, paired with intuition and context, can help spur leadership into action. Metrics help us see the consequences of a problem and consequentially, the benefit of fixing the issue.</p><p>Whether you rely on intuition first or metrics first, remember that they are stronger together. While some leaders may be influenced by observations and gut-drawn conclusions on their own, most will want to understand the numbers, not just for themselves but also for their leaders.</p>]]></content>
    
    <summary type="html">
    
      
      
        &lt;h2 id=&quot;A-Metric-without-context-is-just-a-number&quot;&gt;&lt;a href=&quot;#A-Metric-without-context-is-just-a-number&quot; class=&quot;headerlink&quot; title=&quot;A Metric w
      
    
    </summary>
    
    
      <category term="Metrics" scheme="http://kevinbrinley.com/tags/Metrics/"/>
    
  </entry>
  
  <entry>
    <title>Organizational Wildfires</title>
    <link href="http://kevinbrinley.com/Organizational-Wildfires/"/>
    <id>http://kevinbrinley.com/Organizational-Wildfires/</id>
    <published>2024-07-07T13:45:22.000Z</published>
    <updated>2024-07-07T13:45:22.269Z</updated>
    
    <content type="html"><![CDATA[<h2 id="Prioritize-your-wildfires-or-your-entire-organization-will-burn"><a href="#Prioritize-your-wildfires-or-your-entire-organization-will-burn" class="headerlink" title="Prioritize your wildfires or your entire organization will burn"></a>Prioritize your wildfires or your entire organization will burn</h2><p>In spring 2023, thousands of wild fires raged in Canada. Across much of North America, skies were covered in a haze and the smell of burnt wood lingered in the air. With so many fires and so few firefighters, tough decisions had to be made to determine which fires would be controlled and which would be allowed to progress unchecked.</p><p>Not all fires are the same. Some occur in remote regions, making fighting them difficult. Also, due to their remote nature, their impact to human life is minimal. Still other fires occur near population centers and risk lives and property damage.</p><p>Wildfires are a naturally occurring phenomnon. Many are caused by lightning strikes. Still others are caused by careless<br>activity of humans. Environmental conditions and climatic trends play a huge role, as well as land management practices.</p><p>Organizations encounter their own types of wildfires. When was the last time you had a panicked email from a colleague, a last minute project request from your boss, or a meeting appear on your calendar with short notice? All of these are organizational wildfires, requiring you and your colleagues to respond quickly or face consequences. Just like a real wildfire, the consequences will vary. If you don’t respond to that panicked email, nothing may happen. Or a deal could be lost. Reputations impacted. Or not responding quickly may mean your team has to work a long evening or weekend.</p><p>Organizations will have problems and the organization’s culture comes out in how it responds to them. Do you respond quickly and with overwhelming force to each one? Or, are you more selective, choosing which ones to let smoulder while you forcus your efforts on the more critcal and impactful issues? Be careful the precedence you set with your leadership, as your people will look to you on how to respond to these problems. If you respond to every single problem with the same intensity, you risk burning yourself out as well as your team.</p><p>Just like wildfires have both natural and human based sources, organizational wildfires have different sources. There will always be problems that occur. Some problems are unavoidable. Yet others are completely avoidable. Next time you resolve a wildfire, consider if the problem could have been avoided, either through improved risk management, improved training, better expectation setting, or some other means.</p><p>Remember, only you can prevent organizational wildfires.</p>]]></content>
    
    <summary type="html">
    
      
      
        &lt;h2 id=&quot;Prioritize-your-wildfires-or-your-entire-organization-will-burn&quot;&gt;&lt;a href=&quot;#Prioritize-your-wildfires-or-your-entire-organization-wil
      
    
    </summary>
    
    
      <category term="Leadership" scheme="http://kevinbrinley.com/tags/Leadership/"/>
    
  </entry>
  
  <entry>
    <title>Traits of a Good Scrum Master</title>
    <link href="http://kevinbrinley.com/Traits-of-a-Good-ScrumMaster/"/>
    <id>http://kevinbrinley.com/Traits-of-a-Good-ScrumMaster/</id>
    <published>2024-05-27T14:04:23.000Z</published>
    <updated>2024-05-27T14:06:24.474Z</updated>
    
    <content type="html"><![CDATA[<h2 id="A-good-Scrum-Master-is-far-more-than-just-a-servant-leader-and-agile-expert"><a href="#A-good-Scrum-Master-is-far-more-than-just-a-servant-leader-and-agile-expert" class="headerlink" title="A good Scrum Master is far more than just a servant leader and agile expert"></a>A good Scrum Master is far more than just a servant leader and agile expert</h2><p>After years of being a Scrum Master and watching other Scrum Masters at work, there are a number of traits that the best Scrum Masters share. These traits make the Scrum Master effective at serving the team and organization in their agile journey.</p><p>First, let’s set some basic assumptions. I assume every Scrum Master is familiar with the Scrum Guide. They should be able to facilitate the Scrum events, though to be a good Scrum Master, they should be able to facilitate any type of meeting (with some preparation). A Scrum Master should also be able to explain the reason behind why things are done in Scrum, in order to coach reluctant team members. The Scrum Master should know enough of Scrum to mentor the team on it.</p><h2 id="Servant-Leader"><a href="#Servant-Leader" class="headerlink" title="Servant Leader"></a>Servant Leader</h2><p>Servant Leadership has almost devolved into the cliche management terminology world, like ‘strategize’. Servant Leadership looks different to many people, but I prefer to return to the root of the concept, which was inspired from the short novel <a href="https://en.wikipedia.org/wiki/ Journey_to_the_East" target="_blank" rel="noopener">“Journey to the East”</a>. In this novel, one person ‘serves’ a large group as they embark on a spiritual journey. One day, that person vanishes and the group falls apart. Only later does the protagonist of the story realize that subtle leadership that the ‘servant’ provided. Futurama captured this sentiment when they ended an episode with the quote <a href="https://www.youtube.com/watch?v=edCqF_NtpOQ" target="_blank" rel="noopener">“When you do things right, people won’t be sure you’ve done anything at all.”</a> </p><p><a href="/The-Duality-of-Servant-Leadership/">A servant leader combines elements of both words.</a> As aservant, they help the team by being available and helping when asked. But they are also a leader, and specifically help their team by serving them in things that fulfill their vision. A Scrum Master, as a servant leader, will help a team schedule and facilitate a design meeting if asked. A good Scrum Master will place boundaries on these asks. For instance, if asked to facilitate a discussion that would violate one of the core tenants of agile, they should instead coach the team on the importance of those ideas.</p><h2 id="Coachable"><a href="#Coachable" class="headerlink" title="Coachable"></a>Coachable</h2><p>A good Scrum Master is a coach. But to be a good coach, they first must be someone who can be coached. Not every person is open to being coached. Some become set in their ways. Others become so sure of themselves that they shut themselves off to learning. Still others will listen to books, videos, or blogs, but will resist in person coaching. In each situation, a person shuts themselves off from vital resources and potentials for growth.</p><h2 id="Growth-Mindset"><a href="#Growth-Mindset" class="headerlink" title="Growth Mindset"></a>Growth Mindset</h2><p>A Scrum Master must have a growth mindset - the belief that they and those around them can grow and learn - that things can be better tomorrow than they are today. A Scrum Master with the opposite view, fixed mindset will struggle to help their team continuously improve, and may see an end to the team’s agile journey.</p><h2 id="Observant"><a href="#Observant" class="headerlink" title="Observant"></a>Observant</h2><p>To counter resistance to change, I look for a Scrum Master to be observant. They should be able to pick up on subtle hints that things aren’t right and when the timing is appropriate, shine a light on the problem. Observational skills come in many forms - using metrics, reading body language, conversations with the team, and chatting with stakeholders. A good Scrum Master is always collecting data, data that they can later use to coach the team to improve further.</p><h2 id="Drives-relentless-improvement"><a href="#Drives-relentless-improvement" class="headerlink" title="Drives relentless improvement"></a>Drives relentless improvement</h2><p>A good Scrum Master knows that a team’s growth never ends. They will always find ways to improve, even if the team has been together for a long time. They balance their own observations and those that the team identifies. A great Scrum Master may be so subtle in their sharing of their own observations that the team isn’t even aware that the observations came from the Scrum Master.</p><h2 id="Emotionally-Intelligent"><a href="#Emotionally-Intelligent" class="headerlink" title="Emotionally Intelligent"></a>Emotionally Intelligent</h2><p>A great Scrum Master is emotionally intelligent, knowing how to regulate their own emotions while observing the emotions of others. They use these skills to note when things are left unsaid. They help the team understand their own emotions and help them express those emotions and thoughts to stakeholders and leaders in constructive ways.</p><h2 id="Agile-Expert"><a href="#Agile-Expert" class="headerlink" title="Agile Expert"></a>Agile Expert</h2><p>A good Scrum Master will know Scrum inside and out, but will also know when to apply it and when it won’t work. They are aware of other agile frameworks, techniques, and tools and know when best to apply them. For instance, they know that Kanban works better for a production support team than Scrum.</p><h2 id="Specialist"><a href="#Specialist" class="headerlink" title="Specialist"></a>Specialist</h2><p>A Scrum Master beyond an entry level position should have their own area of mastery. This is an area where they possess more skills and knowledge than their peers. This may be based on their natural talents, like building teams or facilitating meetings. It could be from a skill in their previous job, such as software engineering, quality assurance, product ownership, or project management. Having a speciality can help the immediate team, but also the larger agile organization by bringing insight to share with other Scrum Masters.</p><h2 id="Adaptable"><a href="#Adaptable" class="headerlink" title="Adaptable"></a>Adaptable</h2><p>Finally, a great Scrum Master should be adaptable. They should hone their style to the team, not force the team to work within the Scrum Master’s style. A great Scrum Master will also vary the level of their coaching and the type of coaching based on where the team is. An anti-pattern in Scrum Masters is the so- called ‘Scrum Mom”, a Scrum Master who does many things for the team so they don’t have to. This may be useful for a team brand new to Scrum, as it shows the team how to do Scrum. To a well-seasoned team, a Scrum Mom is a bottle neck and has become the lid on the team’s performance - they can’t do any more work than what the Scrum Master can do. A good Scrum Master must embody the very thing they are coaching their teams to do - agility itself.</p><h3 id="Conclusion"><a href="#Conclusion" class="headerlink" title="Conclusion"></a>Conclusion</h3><p>In short, a good Scrum Master is a servant leader, can be coached, possesses a growth mindset, is observant, is relentless in their pursuit of improvement for the team, is Emotionally Intelligent, knows not just Scrum inside and out but also other agile frameworks and tools, they have their own area of competency, and are themselves adaptable.</p><p>If you’re looking to improve your own skills as a Scrum Master, consider how you rank on each of these attributes. Consider how well each of the areas describes you. Beyond that, how likely are you to act according to those descriptions? What’s the percentage of time you exhibit a growth mindset vs. a fixed mindset?</p>]]></content>
    
    <summary type="html">
    
      
      
        &lt;h2 id=&quot;A-good-Scrum-Master-is-far-more-than-just-a-servant-leader-and-agile-expert&quot;&gt;&lt;a href=&quot;#A-good-Scrum-Master-is-far-more-than-just-a-s
      
    
    </summary>
    
    
      <category term="Scrum Master" scheme="http://kevinbrinley.com/tags/Scrum-Master/"/>
    
  </entry>
  
  <entry>
    <title>Experts at Work</title>
    <link href="http://kevinbrinley.com/Experts-at-Work/"/>
    <id>http://kevinbrinley.com/Experts-at-Work/</id>
    <published>2024-05-12T17:45:40.000Z</published>
    <updated>2024-05-12T17:48:45.781Z</updated>
    
    <content type="html"><![CDATA[<h2 id="To-show-up-as-an-expert-know-your-process-and-exude-confidence-in-your-skills"><a href="#To-show-up-as-an-expert-know-your-process-and-exude-confidence-in-your-skills" class="headerlink" title="To show up as an expert, know your process and exude confidence in your skills"></a>To show up as an expert, know your process and exude confidence in your skills</h2><p>There’s a story of a carpenter who was called to fix a squeeky floor. Entering the room, he made a quick inspection, pulled out a hammer, and struck the timbers in a single stroke. He stood, tested the spot, and proved the squeek fixed. After short work, he charged $100 for his efforts. When pressed why it cost so much for such short work, the carpenter replied he charged $5 for swinging the hammer and $95 for knowing where to swing.</p><p>A <a href="https://www.youtube.com/@DrumeoOfficial" target="_blank" rel="noopener">YouTube channel called Druneo</a> has a series of videos where they put drum experts to a daunting test. The setup is simple. Take a drum expert, a full drum set, and a song the drummer is unfimilar with and given them a few minutes to listen to the song once. Then they ask the expert to play the drums to the song.</p><p>One of my <a href="https://www.youtube.com/watch?v=Zd_UcjMusUA" target="_blank" rel="noopener">favorite videos is this video where Larnell Lewis</a>, who is <a href="https://en.wikipedia.org/wiki/Larnell_Lewis" target="_blank" rel="noopener">known for his work with Jazz and Jazz fusion bands</a>, plays Metallica’s “Enter Sandman” after listening to it for the first time. Watching the video, he explains his process as he listens, working to understand the form of the song, the pacing, the rhythm, and the elements of the drum kit he needs to use, when to use them, and how. What just sounds like banging and clashing to me, an expert picks up on the nuances of drums or cymbals used and any flourishes used on the original track. </p><p>Watching a master of their craft at work is a special sight. Through years of experience, an expert has learned how to do their craft well and fast.</p><p>The drum experts on Drumeo aren’t flawless and would change their approach given a second or third run-through of the song. No one expects an expert to flawlessly execute, but an expert does have to exude confidence they can tackle any situation. The drum experts on Drumeo also exude confidence. They don’t fret about the situation they find themselves in, Instead, they approach the challeng with their skills and a practiced list of steps to prepare.</p><p>Are you an expert in your craft? How would you fare if you were placed into an unknown situation and tasked with executing your craft? Are you able to enter the situation and with disciplined, practiced preparation, exercise your skills and produce? If not, what do you need to practice in order to reach that level? Here you outlined foryourself the steps would you follow in order to prepare like a drum expert?</p><p>Experts dazzle us with their skills. If you aspire to be an expert, keep honing your skills until one day you dazzle someone else. Perhaps one day, someone will look at you the way you look at an expert today.</p>]]></content>
    
    <summary type="html">
    
      
      
        &lt;h2 id=&quot;To-show-up-as-an-expert-know-your-process-and-exude-confidence-in-your-skills&quot;&gt;&lt;a href=&quot;#To-show-up-as-an-expert-know-your-process-a
      
    
    </summary>
    
    
  </entry>
  
  <entry>
    <title>Prepare for Meetings like a College Student</title>
    <link href="http://kevinbrinley.com/Meeting-Prep/"/>
    <id>http://kevinbrinley.com/Meeting-Prep/</id>
    <published>2024-05-05T23:31:03.000Z</published>
    <updated>2024-05-05T23:31:03.539Z</updated>
    
    <content type="html"><![CDATA[<h2 id="Follow-a-2-to-1-ratio-to-prepare-for-successful-Meetings"><a href="#Follow-a-2-to-1-ratio-to-prepare-for-successful-Meetings" class="headerlink" title="Follow a 2 to 1 ratio to prepare for successful Meetings"></a>Follow a 2 to 1 ratio to prepare for successful Meetings</h2><p>When in college, time management is crucial. For many students, college is a culture shock. It is the first time they are on their own. One has to learn how to manage their own time amongst the complexity of their classes.</p><p>To guide students through this, a common rule of thumb is to plan to study for a class 2 or 3 times the number of credit hours it’s worth each week. So a student taking a 3 credit hour class should study 6 to 9 hours a week on that class in addition to the class time.</p><p>This handy rubrick has stuck with me over the years. I apply this to any classes I take as an adult. As a meeting facilitator, I’ve taken the novel approach of applying this to meeting preparation. I’ve found a 2 to 1 ratio to be a useful guide to manage my time in preparing and summarizing meetings. </p><p>Applying the rule is simple. Take any meeting and consider how long the meeting itself is. Then I double the time and that is how long I should spend up front to prep for the meeting. So if I have an hour long meeting, I spend 2 hours preparing for it.</p><p>This preparation time includes</p><ul><li>solidifiying and recalling the meeting purpose </li><li>finalizing the agenda</li><li>considering how I want to show up for the meeting</li><li>facilition methods I need to prepare</li><li>consider any landmines I may face in the meeting</li><li>setting up the physical or virtual space</li><li>reserving time for follow up after the meeting</li></ul><p>We can’t apply this role to every meeting we facilitate. If we did, we’d be limited to about 12 hourss of facilitated meetings a week if we did nothing else. If you are struggling in your facilitation, consider if more preparation would help and apply the 2 to 1 rule for your crucial meetings.</p>]]></content>
    
    <summary type="html">
    
      
      
        &lt;h2 id=&quot;Follow-a-2-to-1-ratio-to-prepare-for-successful-Meetings&quot;&gt;&lt;a href=&quot;#Follow-a-2-to-1-ratio-to-prepare-for-successful-Meetings&quot; class=
      
    
    </summary>
    
    
      <category term="Facilitation" scheme="http://kevinbrinley.com/tags/Facilitation/"/>
    
  </entry>
  
  <entry>
    <title>The Duality of Servant Leadership</title>
    <link href="http://kevinbrinley.com/The-Duality-of-Servant-Leadership/"/>
    <id>http://kevinbrinley.com/The-Duality-of-Servant-Leadership/</id>
    <published>2024-04-29T00:14:50.000Z</published>
    <updated>2024-04-29T00:14:50.553Z</updated>
    
    <content type="html"><![CDATA[<h2 id="Being-a-Servant-Leader-is-not-about-being-a-servant"><a href="#Being-a-Servant-Leader-is-not-about-being-a-servant" class="headerlink" title="Being a Servant Leader is not about being a servant"></a>Being a Servant Leader is not about being a servant</h2><p>Servant Leadership is a common strategy employed in software engineering departments. Popularized by the agile movement and the establishment of Scrum Masters and Agile Coach’s as servant leaders for a team or the organization, servant leadership aims to empower teams and aid them in service to the team’s goal. Originally coined by Robert Greenleaf in the 60’s and 70’s, many thought leaders such as Ken Blanchard and John C. Maxwell expanded on the concept. One of my favorite books on the subject, edited by Ken Blanchard and Renee Broadwell is <a href="https://www.amazon.com/Servant-Leadership-Action-Achieve-Relationships-ebook/dp/B076663QPF/ref=tmm_kin_swatch_0?_encoding=UTF8&amp;qid=1714349260&amp;sr=1-2-9e67e56a-6f64-441f-a281-df67fc737124" target="_blank" rel="noopener">Servant Leadership in Action</a> which includes essays from dozens of leaders on different aspects of servant leadership.</p><p>One concept that is overlooked on the subject is the duality of servant leadership. Too often I see people dismiss or poorly implement servant leadership because they focus on the servant part and forget about the leadership piece. Being a servant is about taking orders, doing what is asked of you, and being a support to those around you. These individuals miss the aspects of leadership of having a vision, leading from out front, and being proactive. A servant leader. must serve, but they must also serve according to a vision. A servant leader must posses both sides to be a true, effective servant leader.</p>]]></content>
    
    <summary type="html">
    
      
      
        &lt;h2 id=&quot;Being-a-Servant-Leader-is-not-about-being-a-servant&quot;&gt;&lt;a href=&quot;#Being-a-Servant-Leader-is-not-about-being-a-servant&quot; class=&quot;headerlin
      
    
    </summary>
    
    
      <category term="Servant Leadership" scheme="http://kevinbrinley.com/tags/Servant-Leadership/"/>
    
  </entry>
  
  <entry>
    <title>On Resenteeism</title>
    <link href="http://kevinbrinley.com/On-Resenteeism/"/>
    <id>http://kevinbrinley.com/On-Resenteeism/</id>
    <published>2024-04-22T02:47:05.000Z</published>
    <updated>2024-04-22T02:47:06.005Z</updated>
    
    <content type="html"><![CDATA[<h1 id="Another-new-name-for-an-old-idea"><a href="#Another-new-name-for-an-old-idea" class="headerlink" title="Another new name for an old idea"></a>Another new name for an old idea</h1><p>In recent weeks, a <a href="https://www.foxbusiness.com/lifestyle/job-trend-resenteeism-employees-coasting-workdays-hanging-rather-quitting.amp" target="_blank" rel="noopener">new term has surfaced to describe a trend taking place in corporate America - Resenteeism</a>. Just as with Quiet Quitting, workers who exhibit Resenteeism are putting in less effort than they once did, meaning they aren’t as productive and effective as they once were. The trend resenteeism takes its name from the resentment at the underlying core of the behavior that is observed.</p><p>What separates Resenteeism from Quiet Quitting is that the latter focuses on the end result - doing less work - while the former calls out the cause - resentment for how one is treated at work or as a reaction to one or a series of events. </p><p>In my previous post <a href="/On-Quiet-Quitting">on Quiet Quitting</a>, I outlined three causes: poor work environment, poor return on investment (ROI) for one’s effort given, and one’s purpose lies outside of work. Resenteeism can arrive from either a poor work environment or a low ROI on extra effort expended.</p><p>Poor working environments, which often arises from a lack of respect for people, will often lead to feelings of resentment. While some can suffer from a poor working environment stoicly, others will let months or years of disrespect build into resentment. </p><p>Workers putting in less effort due to a perceived poor ROI may do so for a variety of reasons. It might be due to an emotional response. It could also be a calculated, logical response after working hard for little reward. From the outside, one might attribute the behavior to resentment.</p><p>Resenteeism sounds like a new trend, but it’s just a new interpretation of the ‘Quiet Quitting trend we’ve seen over the past few years. Yet, as I shared in my original post on Quiet quitting, this trend is not new, though is more widespread. Understanding the underlying cause can help go a long way to overcoming this trend, but overcoming it will require concerted effort from leadership.</p>]]></content>
    
    <summary type="html">
    
      
      
        &lt;h1 id=&quot;Another-new-name-for-an-old-idea&quot;&gt;&lt;a href=&quot;#Another-new-name-for-an-old-idea&quot; class=&quot;headerlink&quot; title=&quot;Another new name for an old 
      
    
    </summary>
    
    
      <category term="Leadership" scheme="http://kevinbrinley.com/tags/Leadership/"/>
    
  </entry>
  
  <entry>
    <title>The one skill all good leaders share</title>
    <link href="http://kevinbrinley.com/The-one-skill-all-good-leaders-share/"/>
    <id>http://kevinbrinley.com/The-one-skill-all-good-leaders-share/</id>
    <published>2024-04-12T19:10:39.000Z</published>
    <updated>2024-04-12T19:16:53.622Z</updated>
    
    <content type="html"><![CDATA[<h2 id="One-skill-separates-successful-leaders-from-the-rest"><a href="#One-skill-separates-successful-leaders-from-the-rest" class="headerlink" title="One skill separates successful leaders from the rest"></a>One skill separates successful leaders from the rest</h2><p>People are promoted based on their ability to wow leaders. Their skills at an individual contributor level is impressive enough to lead to a promotion. But success as an individual contributor does not guarantee success at the next level. </p><p>Within a hierarchy, people tend to be ‘promoted to their level of incompetence’. This is known as the ‘Peter principle’, a concept popularized in the late ‘60s and ‘70s by Laurence Peter. In my experience, those who struggle with leadership responsibilities may have the IQ it takes to do the role and their previous role, but lack the EQ, or Emotional Intelligence, that it takes to lead others.</p><p>Make no mistake, stepping into a leadership role requires intelligence and skill. But that’s just the entry fee one is expected to pay to be a leader. But EQ is the one skill that makes the most successful leaders stand out from the others.</p><p>Unsuccessful leaders may appear successful for a time. Being promoted based on their skills may mean that they are adept at managing expections of one’s leaders. This is not a bad skill to have. We should all strive to keep our leaders informed of our movements. But when this is the only skill one brings to the table, that will not lead to long term success.</p><p>It’s been said that we model the behaviors that we observe. Leaders tend to mimic the patterns of communication they themselves observe. If a leader is surrounded by positive examples, then they may make do with the skills they have, for a time.</p><p>A leader with high emotional intelligence, and specifically, high self-awareness, can sense the patterns they are following and can choose to follow a different path. Self-awarenss is crucial in understanding where one’s strengths and weaknesses truly lie. As one leads others, self-awareness is key in gauging one’s progress and improving. The world around you is giving you feedback on your performance and a person with high EQ and self-awareness can leverage that feedback to improve themselves much faster than any manager-lead feedback cycle.</p>]]></content>
    
    <summary type="html">
    
      
      
        &lt;h2 id=&quot;One-skill-separates-successful-leaders-from-the-rest&quot;&gt;&lt;a href=&quot;#One-skill-separates-successful-leaders-from-the-rest&quot; class=&quot;headerl
      
    
    </summary>
    
    
      <category term="Leadership" scheme="http://kevinbrinley.com/tags/Leadership/"/>
    
  </entry>
  
  <entry>
    <title>The Simple Way to Split User Stories</title>
    <link href="http://kevinbrinley.com/The-Simple-Way-to-Split-User-Stories/"/>
    <id>http://kevinbrinley.com/The-Simple-Way-to-Split-User-Stories/</id>
    <published>2024-04-04T13:03:23.000Z</published>
    <updated>2024-04-04T13:03:23.689Z</updated>
    
    <content type="html"><![CDATA[<h2 id="Let-a-little-SPIDR-help-you-break-down-User-Stories"><a href="#Let-a-little-SPIDR-help-you-break-down-User-Stories" class="headerlink" title="Let a little SPIDR help you break down User Stories"></a>Let a little SPIDR help you break down User Stories</h2><p>In modern Software Development, User Stories are ubiquotous. They are the core building block of anything that we build. User Stories are the fundamental item upon our entire backlog is built from. It’s for this reason that a team needs to have the best user stories possible. If teams have poor user stories, everything else they build on top of the user stories will tend to be poor too.</p><p>The first step to crafting the best user stories is to ensure they meet our own definition of a user story. Common industry practice is to ensure that user stories meet the ‘INVEST’ criteria.</p><ul><li>Independent</li><li>Negotiable</li><li>Valuable</li><li>Estimatable</li><li>Sized Appropriately</li><li>Testable</li></ul><p>The second key step is creating user stories that are sized appropriately. This can be challenging, especially since we’re aiming to make them Indpendent and Valuable at the same time. There are many different ways in which we can divide a user story down into smaller parts. Mike Cohn introduced a handy acronym <a href="https://www.mountaingoatsoftware.com/exclusive/spidr-poster-download" target="_blank" rel="noopener">SPIDR</a> that captures the 5 main patterns for splitting a User Story. Any method of dividing a user story that I’ve encountered could be described by the SPIDR acronym, making not only a simple reminder, but also an exhaustive one.</p><h3 id="Spikes"><a href="#Spikes" class="headerlink" title="Spikes"></a>Spikes</h3><p>A Spike is a user story where the output of the work is research. The outcome is increased understanding and reduced risk for further work to come. Teams cannot know every aspect of the system they are building, and so they may decide to take some time to research the system in question.</p><p>Other times, teams understand the system and the problem space, but may have a few different ideas on a solution. Here a Spike to create a Proof of Concept (PoC) can be valuable use of time and help the team to select a path for their solution.</p><p>A good practice that I suggest teams follow is to time box their Spikes. Estimating how long it will take to research a system can be difficult. Research tends to follow many deep rabbit holes. Having a time box for the spike can provide just enough time pressure to ensure the research is valuable.</p><p>Spikes provide a different kind of business value than user stories. They are more about reducing risk and making decisions then they are about delivering a product to a user. As such, they should be used sparingly. Despite Spikes being the first letter in the acronym, I suggest it be the last resort a team reach for when they split out stories.</p><h3 id="Paths"><a href="#Paths" class="headerlink" title="Paths"></a>Paths</h3><p>In many software systems, there are many paths a user can take to complete a given task. When the work is large or complex, it can be useful to split user stories up by these paths, delivering the most common path first and then adding the functionality to other paths in the system later.</p><h3 id="Interfaces"><a href="#Interfaces" class="headerlink" title="Interfaces"></a>Interfaces</h3><p>In complex systems, we often have many different tools that provide the same or similar functionality. Companies may support a website and a mobile application at the same time while having an internal tool that displays the same information or provides the same functionality. Splitting the work by each of these user interfaces can be an effective way at dividing the work into small, actionable chunks of work. </p><p>One can also split user stories by persona, or the user who is doing the work and is impacted by the change. Different personas may use different interfaces to do their portion of work. You may choose to split the work down based on the personas, allowing the team to deliver a solution per persona in an iterative fashion. </p><p>When thinking of interfaces, teams should still strive to craft vertically sliced user stories. This guidance does not suggest that teams split user stories up by the architectural layer of the system that the work needs to touch. Each story that builds out a unique interface should still contain any backend changes that are necessary to deliver the functionality to the user. That said, the first interface will often be larger as it will create some of the common backend functionality that subsequent user stories will leverage.</p><h3 id="Data"><a href="#Data" class="headerlink" title="Data"></a>Data</h3><p>User stories operate on data elements. When we have multiple data elements, creating a user story for each different data element can be an effective way to slice the work into small managelable chunks.</p><p>Leveraging a Data split can be prone to “throw-away” work, as the team will need to progressively build out APIs and other backend systems to deliver each of the data elements. If it is not too much effort, teams could attempt to fetch all of the data elements in the first user story, but care must be taken to keep the initial story small and focused, else teams will fall back into one giant user story with all of the data points.</p><h3 id="Rules"><a href="#Rules" class="headerlink" title="Rules"></a>Rules</h3><p>We have to implement business rules into our system in order for the system to have proper constraints on what the user can and cannot do. When we have many business rules to implement, dividing the work by these business rules can be an effective and simple way to divide a large body of work into small chunks.</p><h3 id="Conclusion"><a href="#Conclusion" class="headerlink" title="Conclusion"></a>Conclusion</h3><p>SPIDR (Spikes, Paths, Interfaces, Data, and Rules) is a simple way to think about dividing work into smaller user stories. Small user stories allow us to iterate faster, deliver faster, and get feedback sooner. Any user story we create is a hypothesis of what the user wants and is only proven valuable until delivered to the user and measured. By crafting small stories and prioritizing based on what we think is most valuable or by what allows us to receive feedback sooner, we can ensure rapid, valuable delivery to the client. All the while, we must remember to keep our stories vertically sliced, so that each story on its own is Independent and Valuable.</p>]]></content>
    
    <summary type="html">
    
      
      
        &lt;h2 id=&quot;Let-a-little-SPIDR-help-you-break-down-User-Stories&quot;&gt;&lt;a href=&quot;#Let-a-little-SPIDR-help-you-break-down-User-Stories&quot; class=&quot;headerlin
      
    
    </summary>
    
    
      <category term="User Stories" scheme="http://kevinbrinley.com/tags/User-Stories/"/>
    
  </entry>
  
  <entry>
    <title>On Quiet Quitting</title>
    <link href="http://kevinbrinley.com/On-Quiet-Quitting/"/>
    <id>http://kevinbrinley.com/On-Quiet-Quitting/</id>
    <published>2024-03-29T00:44:41.000Z</published>
    <updated>2024-03-29T00:45:56.908Z</updated>
    
    <content type="html"><![CDATA[<h2 id="As-John-C-Maxwell-says-everything-rises-and-falls-on-leadership"><a href="#As-John-C-Maxwell-says-everything-rises-and-falls-on-leadership" class="headerlink" title="As John C. Maxwell says, everything rises and falls on leadership."></a>As John C. Maxwell says, everything rises and falls on leadership.</h2><p>We are in the middle of an epidemic, as business news reports. In 2022, “Quiet Quitting” became a hot topic as workers on social media discussed the new trend in the workplace. Then, news media picked it up and spread to most of the major news reporting sites as the big trend impacting labor.</p><p>Quiet quitting, if you are unfamiliar with the term, refers to a worker choosing to put in less effort today then they did yesterday. This can take many forms, such as working fewer hours, doing the bare minimum, or simply no longer going “the extra mile.”</p><p>“Hopefully, it [the Pandemic] will force us to focus on what is trule important to each of us,”</p><p>I wrote that in my journal on March 14, 2020, the day after I was sent to work from home in an effort to “flatten the curve” of Covid cases.</p><p>I see signs around me that many of us did indeed find or rediscover what is truly important to us. Many people picked up new hobbies. I, like many others, rediscovered Bob Ross and the Joy of Pointing. My wife returned to her passion of reading.</p><p>In 2022, we saw 2 trends that continue this theme of pursuing what is important to us: the great resignation and quiet quitting. The great resignation dominated the headlines in the first half of the year and represented a massive shift of people in roles, companies, and industries.</p><p>But my main curiosity is the other major career trend of 2022, Quiet Quitting” - the term used to describe individuals who were putting in less effort at works within their some role. What causes quiet quitting? I See 3 Candidates: work sucks, one’s ‘return on investment’ for their extra effort, and key to my original hypothesis, the pursuit of one’s passions outside of work.</p><h3 id="Work-Sucks"><a href="#Work-Sucks" class="headerlink" title="Work Sucks"></a>Work Sucks</h3><p>Social media and Subreddit, like <a href="https://www.reddit.com/r/antiwork/" target="_blank" rel="noopener">r/antiwork</a> are an outlet for those encountering poor leadership. Bosses who demand remote employees have their cameras on all day while they work, others who require the use of a 1⁄2 PTO day if one works from home. Leaders who state that “we’re like a family” but don’t hesitate to part with family during an economic downturn. Companies that revert pay to minimum wage for workers who quit without a two week’s notice. Governments working to strip unions the right to strike. Bosses who report employees to HR because they did not respond to texts while on vacation. A boss who rewarded hard work with an extra 10 minute break - that has to be Coordinated 24 hours in advance, that can’t be added to a regular break and that expires in 30 days. And all of this on the homepage of the subreddit on one day. </p><p>As a leader and an agilist, I see a common thread in all of this: the lack of respect for people. We all deserve respect as fellow human beings. Of these who have been disrespected by a leader, quiet quitting can be an emotional response to the situation. We each strive to have some balance in our lives. To exert some sense of control. And when we feel slighted, human nature responds with a ‘balancing of the scales’. “You interrupt my personal time, I’ll slack off at work to make up for the time lost.” “You disrespect me, then I’ll give you the same level of respect in return.” </p><p>With those who ‘quietly quit’ because ‘work sucks’ we have a leadership problem and that starts at the top and filters all the way into the front line managers. To combat ‘work sucks’ we need to raise the level of leadership, and that starts with a simple respect for people.</p><h3 id="Return-on-Investment"><a href="#Return-on-Investment" class="headerlink" title="Return on Investment"></a>Return on Investment</h3><p>Every day, people go to work and “go the extra mile”. For some, they are driven by an internal fire. They’re found their calling. For others, they are extrinsically motivated, hoping to get to the next level. But is that next level worth it? For some who choose to go the ‘Quiet Quitting’ route, it may be a very logical decision instead of an emotional one. </p><p>Time is a precious resource, one we only have so much of. Is ‘giving 110%’ in hopes of a potential reward a smart investment? For those who put in the effort, it may be a good use of their time. Others may have done the math and decided their time is better spent else where, with family, with a hobby, or with their own passions.</p><h3 id="Passion"><a href="#Passion" class="headerlink" title="Passion"></a>Passion</h3><p>‘Ryan Daniels was an account executive for a major adentising agency. “and by the time he was forty, he had a very high- paying job that demanded seventy-hour weeks with a bonus of unrelenting stress. […] He moved to a much smaller company where he could, in his own words, “coast” and still excel.” Ryan used this freed up time to explore his passions and spend time with his family.’ And Ryan did all of this before the internet.</p><p>Ryan’s story comes to us from Bob Bufford’s 1994 book “Halftime”. In it, the author spoke of taking our mid-life and heading into halftime to plan and uncover the one thing we decide to “put in the box” and hang our personal passions on for the 2nd half of our life. It speaks of finding our calling, either in our work, through a career change, charity work, or through pursuits outside of work.</p><p>In this last example, he offered the “half speed option”, where one intentionally works less, either by switching to a less demanding and stressful job or by cutting back on one’s efforts at work by volunteering for less, being more efficient with one’s time, or by lowering one’s standards on the work they do, striving for doing acceptable instead of outstanding work. </p><p>I share this because while “quiet quitting” is a new term, it is not a new concept. Inherent in all of us is a choice of what is significant for us. Many choose work as this item of significance. But drastic life changes, like a pandemic, causes one to reasses what is important in life. <a href="https://www.theguardian.com/lifeandstyle/2012/feb/01/top-five-regrets-of-the-dying" target="_blank" rel="noopener">Among the top regrets of the dying</a>, no one said they wish they worked more. In fact, the number three regret is that they wished they worked less!</p><h3 id="Conclusion"><a href="#Conclusion" class="headerlink" title="Conclusion"></a>Conclusion</h3><p>Quiet quitting is not a new concept, but it may be gaining in popularity. I believe there are many cases of this trend and the pandemic served as a catalyst. American culture is shifting, as it always has. Hard work is not valued as highly as it used to be, from my vantage point. And factors such as poor leadership, low ROI on putting in extra effort, and people choosing to follow their passions, have all led us here. </p><p>What can we do about this trend? It starts and ends in enlightened leadership. It starts with leaders who can connect people’s passions to their work and who offer people respect. To punish, bemoan, or micromanage employees because one suspects their people are “quiet quitting’ will only fan the flames.</p><p>To quote John C. Maxwell, ‘everything rises and falls on leadership’. If this problem exists in corporate America, then it was caused by the leaders in corporate America. Yet here too is where the problem can be reversed.</p>]]></content>
    
    <summary type="html">
    
      
      
        &lt;h2 id=&quot;As-John-C-Maxwell-says-everything-rises-and-falls-on-leadership&quot;&gt;&lt;a href=&quot;#As-John-C-Maxwell-says-everything-rises-and-falls-on-lead
      
    
    </summary>
    
    
      <category term="Leadership" scheme="http://kevinbrinley.com/tags/Leadership/"/>
    
  </entry>
  
</feed>
