<?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:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by John Connolly, MLIS, PMP on Medium]]></title>
        <description><![CDATA[Stories by John Connolly, MLIS, PMP on Medium]]></description>
        <link>https://medium.com/@salientian?source=rss-b1b8c78e1b5f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*EqAMWq8_C42seK0exkATrw.jpeg</url>
            <title>Stories by John Connolly, MLIS, PMP on Medium</title>
            <link>https://medium.com/@salientian?source=rss-b1b8c78e1b5f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 23:01:10 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@salientian/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The Looming Project Management Crisis We’re Not Talking About]]></title>
            <link>https://medium.com/@salientian/the-looming-project-management-crisis-were-not-talking-about-d195fd7a23d1?source=rss-b1b8c78e1b5f------2</link>
            <guid isPermaLink="false">https://medium.com/p/d195fd7a23d1</guid>
            <category><![CDATA[knowledge-management]]></category>
            <category><![CDATA[retirement]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[training]]></category>
            <category><![CDATA[information-management]]></category>
            <dc:creator><![CDATA[John Connolly, MLIS, PMP]]></dc:creator>
            <pubDate>Fri, 16 Jun 2023 14:28:27 GMT</pubDate>
            <atom:updated>2023-06-16T14:28:27.172Z</atom:updated>
            <content:encoded><![CDATA[<p>According to the Project Management Institute’s 2021 <em>Talent Gap</em> report, the global economy needs 25 million new project professionals by 2030. Good news, right? But if you take a deeper look, the numbers aren’t all quite rosy.</p><p>According to PMI, more than half of those 25 million vacancies will not be coming from project management growth, but from the mass retirement of project managers aging out of the field. 13 million project managers are expected to retire from the workforce by 2030.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NVyB-YypE1lHmcpf" /><figcaption>Photo by <a href="https://unsplash.com/@wolfgang_hasselmann?utm_source=medium&amp;utm_medium=referral">Wolfgang Hasselmann</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>A Big Loss?</h4><p>There’s a temptation to view this as <em>more</em> good news: retirements will mean more job opportunities for those coming up behind, and employers might save on salaries to boot. But nobody’s talking about what these companies (and, in a larger sense, the entire discipline of project management) will be losing in this mass exodus.</p><p>Let’s assume that the average project management retiree has 15 years of relevant experience. I believe that’s a conservative figure. <strong>Even at that figure, the total experience loss to the field will be 195 million years of collective experience by 2030</strong>.</p><h4>The Risk of Knowledge Loss</h4><p>If you don’t perceive that this could be a risk to how the profession drives value, then I’d question your acumen at risk management. The project management field currently relies heavily on experience: PMP certification requires 36 months of experience (with a bachelor&#39;s degree) or 60 months of experience (without a bachelor&#39;s degree) just to qualify to sit for the exam. Hiring managers are prioritizing experience.</p><p>Deep experience has dominated the project landscape even as PMI tries to turn the ship and incorporate new leadership and management concepts into its body of knowledge.</p><p>A great deal of what project managers know is at risk of being lost. Project managers are versed in the distinction between tacit and explicit knowledge, and we are expected to capture both as well as we can to inform tomorrow’s projects with the knowledge we have built today.</p><p>But there are struggles, in my opinion, on the execution on that front on a project-by-project basis. Are we really doing a good job focusing on this concept when it comes to the imminent departure of our field’s experienced experts?</p><h4>Gathering Knowledge</h4><p>The risk can be mitigated through two broad steps: knowledge capture and knowledge transmission. The first step is to capture the explicit and tacit knowledge our project managers have. This will take a fine balance, as those project managers are busy, you know, managing projects. Getting involved side-by-side with them to capture tacit knowledge will be difficult and expensive.</p><p>Further, we need to harness the transformational power of explicit knowledge in our field. Are we prioritizing, as a discipline, the gathering of good practices and ways of working that translate across organizations? Even if we are capturing that information, are we standardizing our lessons learned to communicate them? It’s a both-and situation, not either-or. If project managers are doing their jobs in generating lessons learned and project artifacts, there should be loads of raw data available. But as every organization has different approaches and ways of working (and terminology, and structure), the idea of truly digging into this data is daunting at best.</p><p>On the other hand, I haven’t seen a major movement to capture and disseminate tacit knowledge in a formal way at the disciplinary level. Again, the most helpful approach would be one of standardization and categorization. I haven’t seen an existing framework for this in the thousands of articles and presentations available in the PMI ecosystem (if I have missed it, please shoot me a message so I can check it out).</p><h4>Communicating Knowledge</h4><p>The other side of the coin is the dissemination of gathered knowledge. While you can’t share what you don’t have, the converse is true: if you have it but don’t share it, it’s equally useless. You may as well have not gathered all that knowledge in the first place.</p><p>What does this mean? Formalized training that goes beyond the certification system would be a great start. If a standardized, disciplinary lessons learned categorization can be established, not only can we distill good practices that extend beyond approach-based frameworks, we can inform standards for the future.</p><p>The great “force multiplier” would be programs that allow for paired transfer of knowledge: I’d love to see a focus on junior roles pairing with those readying for exit. Mentorships and shadowing would effectively kill two birds with one stone. I’m a proponent of an “all of the above” approach.</p><h4>Acting Before It’s Too Late</h4><p>Who doesn’t deserve a stress-free retirement? The main suggestions I’ve seen as answers to this question would be to transition as many experience project managers into consulting roles. Not only is this unsustainable (nobody lasts forever), it’s also an unfair expectation for a workforce that has earned the right to focus on other things. No, that’s not a fix.</p><p>We have a little bit of time (though maybe not enough to solve the whole problem), but I worry that this time is being wasted in other pursuits: the ongoing debates about predictive vs. adaptive approaches, or concerns about what PMBOK 8 will look like, or the development of Disciplined Agile and selection of ways of working. To be fair, there <em>has </em>been a deeper emphasis on finding and developing new project managers to navigate the talent gap, but I fail to see a comprehensive, strategic approach to making this successful.</p><p>You know, like a project.</p><p>If we can harness experienced knowledge before this groundswell of retirement, it can energize and jump start our discipline. If we fail to act soon, we stand to lose a great deal, even as project management moves into a future dominated by volatility and higher rates of turnover.</p><p><em>John Connolly, MLIS, PMP is a project manager, trainer, author, and consultant. You can </em><a href="https://www.linkedin.com/in/johnconnolly058/"><em>follow him on LinkedIn</em></a><em> and discuss project management approaches, knowledge and information management principles, and a variety of ideas on project practices.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d195fd7a23d1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Project Management Lessons from Mom]]></title>
            <link>https://medium.com/@salientian/project-management-lessons-from-mom-f79d893ba14c?source=rss-b1b8c78e1b5f------2</link>
            <guid isPermaLink="false">https://medium.com/p/f79d893ba14c</guid>
            <category><![CDATA[projects]]></category>
            <category><![CDATA[management-and-leadership]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[lessons-learned]]></category>
            <category><![CDATA[wisdom]]></category>
            <dc:creator><![CDATA[John Connolly, MLIS, PMP]]></dc:creator>
            <pubDate>Mon, 05 Jun 2023 18:00:32 GMT</pubDate>
            <atom:updated>2023-06-05T18:00:32.730Z</atom:updated>
            <content:encoded><![CDATA[<p>We all have lessons and wisdom imparted to us from a young age. The refrains of our parents help shape us. And I have to admit that a lot of my project management habits are traceable back to my childhood formation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*WVubpUmgZ7PBiJOH" /><figcaption>Photo by <a href="https://unsplash.com/@lianamikah?utm_source=medium&amp;utm_medium=referral">Liana Mikah</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>There are quite a few injunctions from my childhood that carry some lessons for the project world. Here are a few that came to mind for me recently.</p><h4>Use “Sir” or “Ma’am” With Your Elders</h4><p>While I don’t know that this is a requirement in its most literal sense, the idea of treating others with respect and courtesy shines forth. Successful project managers know how to use tact and diplomacy, and it’s increasingly rare to find anything resembling success without courtesy and respect.</p><h4>Eat Your Vegetables Before Your Dessert</h4><p>Be a member of the “Clean Plate Club” on your projects! Everything has an order: don’t rush ahead to delivery without clearly-defined requirements. Don’t assign resources without a budget. If you rush to the end instead of planning and following that plan, you’ll be in for a world of hurt.</p><h4>Leave the Room Cleaner Than You Found It</h4><p>It’s easy to get wrapped up in the project, to the point that we say “it’s not my job” to everything outside of the scope of deliverables. However, we’re in an age where project managers aren’t just deliverable experts, we’re change agents as well. And that means finding ways to improve the way we work and deliver value. If we leave the room cleaner than we found it, we’re modeling the behavior we would want to see on the project and in the organization.</p><h4>Say “Please” and “Thank You”</h4><p>Leaders shouldn’t be in the business of dictating work in an overbearing manner. Collaborating with team members and stakeholders will get you a lot further than demanding things or throwing your weight around. And if somebody helps you out, even if it’s part of their job, a word of thinks goes a long way to help forge connection and collaboration.</p><h4>Look Both Ways Before Crossing the Street</h4><p>It’s common sense in real life, right? Don’t get run over because you dashed forward without checking. And that carries over to our projects, too. Keep an eye on risks. Regularly analyze stakeholders. Keep in touch with the project teams. Don’t assume that others will do your job to handle the safety of the project. That’s a good way to get run over.</p><p>What are some of your childhood lessons? Any that apply to project management, like mine? Looking forward to hearing from you in the comments!</p><p><em>John Connolly, PMP is a project manager, trainer, author, and consultant. You can </em><a href="https://www.linkedin.com/in/johnconnolly058/"><em>follow him on LinkedIn</em></a><em> and discuss project management approaches, knowledge management principles, and a variety of ideas on project practices.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f79d893ba14c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[No, Your Life is Not a Project]]></title>
            <link>https://medium.com/@salientian/no-your-life-is-not-a-project-67fc69108a7c?source=rss-b1b8c78e1b5f------2</link>
            <guid isPermaLink="false">https://medium.com/p/67fc69108a7c</guid>
            <category><![CDATA[life]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[living]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[projects]]></category>
            <dc:creator><![CDATA[John Connolly, MLIS, PMP]]></dc:creator>
            <pubDate>Tue, 23 May 2023 12:08:30 GMT</pubDate>
            <atom:updated>2023-05-23T12:08:30.480Z</atom:updated>
            <content:encoded><![CDATA[<h4>Lives should be lived, not managed</h4><p>I have heard, and often, that our lives are great projects. As project managers, we should run our lives as well as our work projects. This has permeated the atmosphere of the enthusiastic online project management community regardless of preferred methodology or framework. It sometimes disturbs me seeing Agile (or predictive) principles applied to an increasing number of life areas where they have no business being.</p><p>Frankly, the notion that lives are projects is bunk. I find the idea as incomprehensible as it is wasteful. There’s no easier way to devalue our lives than to define them in terms of projects.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*CdYFbfDGv8VZ4Wpe" /><figcaption>Photo by <a href="https://unsplash.com/pt-br/@thulfiqarali?utm_source=medium&amp;utm_medium=referral">Thulfiqar Ali</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>Restrictive Definition</h4><p>The widely held definition of a project is a time-limited, finite endeavor that creates value through the production of a unique end state or deliverable. I have no problems with that. And I want to be clear, I’m not devaluing project work in any way, either. Some of the greatest human achievements have been project work: the great pyramids, the moon landings, towering skyscrapers, the list goes on.</p><p>How well do lives fit into the above category? Not very cleanly. I guess our lives are time-limited, but that’s hardly the same as the sense in which the project definition means. We only have so long on this earth, but we really don’t know how long we’ve got.</p><p>And what about that unique end state or deliverable? What’s the one thing each of us is put here to produce? And if we fail to produce it, have our lives been failed projects?</p><h4>A Utilitarian Danger</h4><p>I believe that project management is an inherently materialistic thing. We’re setting out with a goal of producing something economically valuable. We’re usually building something for sale or materially beneficial to a group or organization. This is a necessity for society to function… but is it a solid foundation for running our lives?</p><p>I worry that this point of view will automatically exclude those whose lives aren’t <em>materially</em> valuable to society. The elderly, the very young, and the disabled might not be producing for material value. Does that mean they are failing as projects? Does it mean they’re failing to <em>be</em> valuable?</p><p>It’s a dark path to walk when we’re beginning to define the value of a life lived in terms of material worth. You always end up throwing away some groups as no longer being valuable. This leads to second-class status in society at best, or horrifying mistreatment at worst.</p><h4>Stopping to Smell the Roses</h4><p>Today, there will be thousands of people across the country who sit down and play musical instruments for no material purpose other than that it pleases them. They will never be concert performers, will never get paid to play, and their playing might never even be heard by anybody but themselves.</p><p>Beautiful exercise in human delight? Or horrible waste of “project resources?”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*xhr7qTIguOcogAjp" /><figcaption>Photo by <a href="https://unsplash.com/@sickhews?utm_source=medium&amp;utm_medium=referral">Wes Hicks</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Projects are about efficiency. Why? Because they’re material. We’re investing resources with the intention of maximizing value. The whole point of project management is to get the most value out of the fewest resources to maximize benefit.</p><p>When we apply a project manager’s mindset to our lives, it cuts away at the elements of life that are most human and most spiritually satisfying. We reduce ourselves to human doings rather than human beings. There’s less room to stop and smell the roses. We put pressure on ourselves to produce deliverables and that will necessarily crowd out the softer times where we experience our non-work existence.</p><p>Some people will be happy producing deliverables. But we do a disservice to life when we reduce family and friends to the level of stakeholders. We will lose our way if we see our whole existence as set up to produce a big single deliverable. We’ll rush past beauty and goodness if we’re pressing to stick to a schedule. And we may burn out if we iterate eternally in a quest for optimized everything.</p><p>Live life, seek happiness, and manage projects when they happen. Projects exist for people, not the other way around. Don’t be afraid to be human first. There’s always another project. But there’s not always another chance to experience joy.</p><p><em>John Connolly, PMP is a project manager, trainer, author, and consultant. You can </em><a href="https://www.linkedin.com/in/johnconnolly058/"><em>follow him on LinkedIn</em></a><em> and discuss project management approaches, knowledge management principles, and why frogs are the coolest creatures in the animal kingdom.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=67fc69108a7c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Project Management Has a Desperate Need… for Librarians]]></title>
            <link>https://medium.com/@salientian/project-management-has-a-desperate-need-for-librarians-28c6c408cdbd?source=rss-b1b8c78e1b5f------2</link>
            <guid isPermaLink="false">https://medium.com/p/28c6c408cdbd</guid>
            <category><![CDATA[librarians]]></category>
            <category><![CDATA[libraries]]></category>
            <category><![CDATA[knowledge-management]]></category>
            <category><![CDATA[project-manager]]></category>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[John Connolly, MLIS, PMP]]></dc:creator>
            <pubDate>Sat, 20 May 2023 23:15:50 GMT</pubDate>
            <atom:updated>2023-05-20T23:15:50.941Z</atom:updated>
            <content:encoded><![CDATA[<p>I have a deep interest in how knowledge management can blend with project management. My roots as a librarian have fueled my interest in how knowledge management fills a need in project management. But a recent conversation I had with <a href="https://www.linkedin.com/in/josephjordanpmp/">Joseph Jordan</a> helped clarify just how deeply project managers are still struggling with elementary knowledge and information management issues.</p><p>In one of his 2022 LinkedIn articles, Joseph outlined what he calls the need for a “<a href="https://www.linkedin.com/pulse/search-single-source-truth-joseph-jordan/">Single Source of Truth</a>.” It’s a lofty term for a practical desire for a unified recordkeeping system that is both maintained as up-to-date and controls subsidiary records:</p><blockquote>It finally hit me that I was looking for a Single Source of Truth (SSoT). For any given program, within any given organization, I wanted to know the authoritative source for any given piece of information, and to ensure the integrity and fidelity of that information, through the entire lifespan of that information — including updates and changes — wherever and in whatever format that information was needed.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*SeFD9Ubueb0WUFYU" /><figcaption>Photo by <a href="https://unsplash.com/@siora18?utm_source=medium&amp;utm_medium=referral">Siora Photography</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>In the article, Joseph lays out three pain points in this area:</p><blockquote>1. We cannot find the information we are looking for.</blockquote><blockquote>2. When we do find what we are looking for, we do not know if the information is current.</blockquote><blockquote>3. We end up recreating the information we could not find. (Which in turn may or may not be current — in other words, we become part of the problem, not the solution).</blockquote><p>As I wade deeper into these waters, I have a conviction that this pain is at the intersection of knowledge management and information management. The two are not the same. But you know who deals with key concepts like input standards, metadata and cataloging, efficient retrieval, and serendipitous finding?</p><p>The librarians.</p><h4>Librarians to the Rescue</h4><p>The obvious need is for systems for the generation, governance, maintenance, and transfer of information. Project managers in many organizations and industries struggle with this, and I suspect that many PMOs might struggle with it, too.</p><p>A great number of organizations put minimal investment into information cataloging and retrieval strategies, even ones with elaborate standards for documentation and information generation. The refrain of “it’s on SharePoint… someplace” has become a clarion call across the project landscape.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JuV1fgZaK_NcK4V1" /><figcaption>Photo by <a href="https://unsplash.com/@fallonmichaeltx?utm_source=medium&amp;utm_medium=referral">Fallon Michael</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>The fact is, even with meticulous input standards (which we <em>know</em> are always followed precisely, right?), perfect information is useless if it’s not maintained, updated, and is part of a retrieval strategy. At most basic, we need input standards and metadata standards to ensure thorough cataloging and to promote findability. Moreover, a master record linked to more detailed records would be a must. Artifact storage and retrieval is also on the wish list.</p><p>Enter the librarian.</p><p>Librarians have been handling databases of records for artifact (books, movies, and more) retrieval for decades. The standard library metadata format, MARC, was developed in the mid-1960s. Library catalogs in many environments are quite refined and an elaborate international network of records exchange exists to promote good practices while maintaining the flexibility for specific implementation to be determined by the individual library and its needs. More recently, new standards have been developed that allow for the fluidity of newer technology, such as metadata recordkeeping in XML and flexible standards for digital or physical recordkeeping.</p><p>The point is, the headaches of the project manager are (to our chagrin) fairly rudimentary problems in library science and librarians have good practices in place that can greatly ease those burdens.</p><h4>A Triumvirate of Practices</h4><p>While we make a big deal of noise about the uniqueness of each project, the very concept of lessons learned is predicated on the idea that patterns, ideas, and experiences do in fact transfer from project to project. We need a strategic approach to learning (knowledge management), unified standards of action (information management), in alignment with practical goals in the pursuit of business value (project management).</p><p>Ideally, this would look like a broad cycle of elements that inform and reinforce one another.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eEDzQ0YlhZR8SgpwpoWKZg.png" /><figcaption>A quick graphic depicting an integrated learning cycle. Information management informs project management. Project management informs knowledge management. Knowledge management informs information management. And so on.</figcaption></figure><p>If these three elements can work in tandem to promote genuine learning, then the time and cost savings could be enormous. Project managers I’ve spoken with have largely all expressed frustration with the inability to avoid costly mistakes that have been made in the past.</p><p>Those who fail to learn from history are doomed to repeat it.</p><h4>Find Good Practices, and Tailor Them</h4><p>We’re a good way off from every major project having an embedded librarian. Nevertheless, I think that closer inspection of library and information science disciplines will yield a bounty of pre-existing concepts and standards that would cure what ails the lessons learned landscape.</p><p>In the end, the bridges from knowledge management and information management to project management still need to be built. The resources, disciplines, and theories needed to construct effective learning environments already exist. We need to move toward a new systematic integration that will promote project learning and fuel execution across our endeavors.</p><p><em>John Connolly, PMP is a project manager, trainer, author, and consultant. You can </em><a href="https://www.linkedin.com/in/johnconnolly058/"><em>follow him on LinkedIn</em></a><em> and discuss project management approaches, knowledge management principles, and why frogs are the coolest creatures in the animal kingdom.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=28c6c408cdbd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Project Management Needs to Ditch the Sandbox]]></title>
            <link>https://medium.com/@salientian/project-management-needs-to-ditch-the-sandbox-cc2063ef84a3?source=rss-b1b8c78e1b5f------2</link>
            <guid isPermaLink="false">https://medium.com/p/cc2063ef84a3</guid>
            <category><![CDATA[changemaker]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[project-manager]]></category>
            <category><![CDATA[business-value]]></category>
            <category><![CDATA[projects]]></category>
            <dc:creator><![CDATA[John Connolly, MLIS, PMP]]></dc:creator>
            <pubDate>Thu, 18 May 2023 01:57:31 GMT</pubDate>
            <atom:updated>2023-05-18T01:57:31.529Z</atom:updated>
            <content:encoded><![CDATA[<p>When I was growing up, the playground favorite was the sandbox. The barrier between sand and grass was a hallowed division between hours of fun and imagination and a real world with bedtimes and schoolwork and requirements to eat vegetables with dinner.</p><p>In my sandbox, I was king: I would dig, arrange, and bulldoze as I saw fit. Woe betide the matchbox cars and Ninja Turtle action figures that would dare oppose me.</p><h4>The Project Sandbox</h4><p>I often consider the sandbox as an apt analogy for a certain attitude among project managers. I had a hard time putting my finger on it for the longest while, but like a faint background odor, I knew something was there. After a while, I realized that the attitude is evident in how we speak and think about who we are and what we do.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*fKDgKvTL6k7Yhbbv" /><figcaption>Photo by <a href="https://unsplash.com/@markusspiske?utm_source=medium&amp;utm_medium=referral">Markus Spiske</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Think for a moment about how we discuss <em>stakeholders</em>. Do we really consider them to be vital assets to our goals? Or are they thought of more as inconvenient necessities to facilitate our function? Don’t get me wrong, I’ve been on the wrong side of key stakeholders sometimes, and it’s not fun. But there’s a faint… antagonism in the way we sometimes talk about the executives who hold the purse-strings (and thus, the leash) of the project managers.</p><p>We love to draw clear boundaries, and yes, some of us even jealously guard our positions of knowledge, authority, and power. But I’m here to tell you that the sandbox of project management is a fickle, fleeting illusion. Every project manager will eventually be asked to go home, eat vegetables with dinner, do homework, and go to bed on time. That’s not a problem… it’s just life.</p><h4>Value Over Deliverables</h4><p>We are in the midst of an important, if gradual, sea change in project management. As more projects incorporate a blend of Agile and predictive approaches, we’re also experiencing a new emphasis on <em>value</em> over <em>deliverables</em>. This has seismic implications for the project manager’s mindset and opens a whole world of possibilities… and responsibilities.</p><p>I have, from time to time, been dismayed by the one-track focus in some corners of the project management community. We seem to constantly be balancing our own expertise and understanding of the right path forward with the ability to communicate with the outside world.</p><p>The way we talk about projects belies our attitude to anything outside the project: threats, risks, issues, environmental factors, influences. And although the project requires stability embodied in baselines, we sometimes go too far in seeing every influence as a potential challenge to us and what we do best.</p><h4>Managing in Context</h4><p>Beneath it all, I perceive <em>organizational responsibility</em> as being a key ingredient in how we think about ourselves as project managers. It benefits us nothing if our most perfect projects go unappreciated or unvalued. It’s a ticket on a fast train to irrelevance if we’re producing perfect deliverables on time and under budget that never get used.</p><p>What does organizational responsibility entail? It means embracing our place within an organizational context, understanding the value the organization needs to achieve through the project, and pushing ourselves to align with our key stakeholders.</p><p>Stretching past the confines of project processes and deliverables ensures real value is realized, even from failed projects. In fact, words like <em>success</em> and <em>failure</em> take on whole new meanings if we’re constantly viewing our projects through the organization’s business value goals.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*H0Pj3pP_nqWArpNY" /><figcaption>Photo by <a href="https://unsplash.com/@cobblepot?utm_source=medium&amp;utm_medium=referral">Kit Suman</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>Bringing Our Best Value</h4><p>It’s uncomfortable to think about sometimes, but project managers can and should be change agents, especially on their projects. I know change of baselines is never preferred, but we are in a unique circumstance to understand rapidly developing situations and newly created knowledge that can give our organizations strategic advantages. The best thing for the project might be change… or even closure. Being embedded in our context (truly being a stakeholder as well as the project manager) maximizes our ability to produce valuable results.</p><p>Call me dour, but I’m always looking for every last scrap of value and relevance I can get in my professional life. And I fully recognize that it’s difficult to see things from 100,000 feet when we’re used to the 10,000-foot level. But you have to give something to get something.</p><p>If we can jettison a sandbox mindset, we can upgrade our relevance and value in a huge way. As project stakeholders, we can steer things to optimal value, not just successful delivery. And that can make a world of difference.</p><p><em>John Connolly, PMP is a project manager, trainer, author, and consultant. You can </em><a href="https://www.linkedin.com/in/johnconnolly058/"><em>follow him on LinkedIn</em></a><em> and discuss project management approaches, knowledge management principles, and why frogs are the coolest creatures in the animal kingdom.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cc2063ef84a3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Art, Project Marketing, and Organizational Value]]></title>
            <link>https://medium.com/@salientian/art-project-marketing-and-organizational-value-36af8e4e93c0?source=rss-b1b8c78e1b5f------2</link>
            <guid isPermaLink="false">https://medium.com/p/36af8e4e93c0</guid>
            <category><![CDATA[arts-organizations]]></category>
            <category><![CDATA[project-manager]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[marketing]]></category>
            <dc:creator><![CDATA[John Connolly, MLIS, PMP]]></dc:creator>
            <pubDate>Thu, 04 May 2023 01:31:28 GMT</pubDate>
            <atom:updated>2023-05-04T01:31:28.444Z</atom:updated>
            <content:encoded><![CDATA[<p>Many project managers wouldn’t consider themselves to be the kind of people who get out in front of audiences to entertain and amaze. But we have an integral role to play in the success of our organizations. A little marketing now and then is a healthy thing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*p-IDyRsbFqIu-oMD" /><figcaption>Photo by <a href="https://unsplash.com/@gavrilovsergphoto?utm_source=medium&amp;utm_medium=referral">Sergei Gavrilov</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Once upon a time, I worked at an art museum. While I was there, I gathered a host of lessons that have since informed my approach to life. A major one was the lesson of Michael Kaiser’s <a href="https://www.amazon.com/Cycle-Practical-Approach-Managing-Organizations/dp/1611684005"><em>The Cycle</em></a>. On the surface, Kaiser’s framework would appear to be a marketing approach. But upon closer inspection, I found that it is a method for organizational development and even career or personal growth.</p><p><a href="https://en.wikipedia.org/wiki/Michael_Kaiser">Michael Kaiser</a> is an arts world maven, possessing a genius for taking troubled arts organizations and turning them around into flourishing, relevant community hubs. My mentor gave me one of his books and even persuaded him to come speak for our Board of Directors. I was fortunate enough to be in the room when he visited.</p><p>I’ve found this framework to apply to my life, including my roles as a project manager. The Cycle has four stages, and they map out how to go from a tiny, irrelevant organization to a larger one with a loyal, robust following.</p><h4>Produce Great Art</h4><p>The Cycle is an iterative approach to growing an organization and its member community. There are four stages of each iteration. The first and most critical maxim is to produce great art. If an arts organization isn’t doing anything new, vibrant, thought-provoking, or enjoyable, there isn’t any reason to be a part of it.</p><p>In project management, we all have our art. It’s what we do best, the value we bring. We have to be good at what we do. If we aren’t good at it, then we’re not delivering value. But it’s not enough to just be good at producing deliverables. It’s a component of our responsibility, but deliverables can easily be unmoored from value when produced outside of the organizational strategy.</p><p>As we more closely focus on delivery of value (outside the strict confines of the project) instead of deliverables, the project manager role expands dramatically as what Kaiser would call an <em>institutional marketer</em>. We aren’t just managing a project… we are advocates for the project and the value it delivers.</p><h4>Market Aggressively</h4><p>The second section of The Cycle requires aggressive marketing. For Kaiser, this is made up of <em>programmatic marketing</em> (websites, ads, social media, commercials, flyers, etc.) and <em>institutional marketing</em>. Institutional marketing is the “secret sauce” of Kaiser’s framework. It’s closely tied to understanding and living out your mission and vision statements. It’s getting out and engaging with people where they are, representing all the possibilities and benefits and fun an arts organization can provide. It makes people <em>want</em> to support the organization.</p><p>As project managers, once we step outside the safe boundaries of the project process itself, we are beset by a million relationships to manage. How are we marketing the project (and ourselves)? Are we meeting our stakeholders where they are and demonstrating the value… and potential of the project? Can we market to get them to <em>want </em>to support us?</p><p>And if you think being able to accomplish this for a project might be beneficial, imagine what it can do for your career. Getting write-ups online is nice. Engaging with influential people and showing them the potential benefits of supporting you can transform your outlook tremendously.</p><h4>Grow the Family</h4><p>The heart and soul of Kaiser’s philosophy is that the organization isn’t just selling a product, it’s cultivating a family of supporters. This means that there needs to be a variety of avenues and levels where people can support. Can’t afford a $350 annual membership? There are cheap tickets to experience the performances. Want to make a huge impact? Here are the packages of benefits to make large donations. Can’t give anything? Here’s the lineup of our free educational programming.</p><p>At every turn, the family grows. And it’s incumbent on the leader to welcome everybody to the family. To help them realize the value of being a supporter, even if it’s just the minimal engagement of signing up for an email list. We produced the art. We let people know that the art was available to them. That led people to the organization.</p><p>Project managers orient themselves toward the activity list: we have things to do, and not enough time to do them. But imagine the benefits of growing a supporter base within the organization. We can’t focus on just one project… we need to focus on our position and posture within our organization. More support is powerful. And powerful project managers can help make changes that make the organization better and more valuable.</p><h4>Receive Resources</h4><p>When you follow The Cycle, you go from art, to marketing, to family, to resources. When people are part of your family, they want to support you. And they will give resources to you. For some, this is money. For others, time and expertise. Some will show up to events or programs, even ones they aren’t in love with, just to show support. They will carry a banner for the organization. They’ll invite friends and family to support the organization, too. You’ve created an army.</p><p>This, of course, is the platonic ideal of stakeholder engagement. While we’ll never get there with all our stakeholders, institutional marketing and a healthy focus on growing the project family can transform relationships.</p><p>In our careers, growing support and cultivating connections can quickly lead to valuable resources. Not necessarily a new job (though that happens, too), but valuable time and engagement with influential people and wise mentors will come your way. You will grow a community for yourself.</p><h4>Reinvest and Begin Again</h4><p>The key to The Cycle is in the transition from receiving resources into starting over: it’s critical to reinvest in your art. If you do that, the next iteration will be bigger, the family will grow larger, there will be more resources, and you can invest in even greater art.</p><p>What if your CEO was your target marketing audience? Could you grow your value, your projects, your influence? Can you turn small wins today into incrementally larger ones tomorrow?</p><p>Our art is what we’re best at. Find resources and reinvest in your strengths. Will you be the go-to for getting projects done in your organization? You won’t get there with good art alone. You need to master institutional marketing. This is why presentation and speaking, interpersonal communication, and emotional intelligence are all integral to project management success.</p><p><em>John Connolly, PMP is a project manager, trainer, author, and consultant. You can </em><a href="https://www.linkedin.com/in/johnconnolly058/"><em>follow him on LinkedIn</em></a><em> and discuss project management approaches, knowledge management principles, and why frogs are the coolest creatures in the animal kingdom.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=36af8e4e93c0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[We Manage Everything About Projects… Except Knowledge]]></title>
            <link>https://medium.com/@salientian/we-manage-everything-about-projects-except-knowledge-ca1863be598?source=rss-b1b8c78e1b5f------2</link>
            <guid isPermaLink="false">https://medium.com/p/ca1863be598</guid>
            <category><![CDATA[knowledge-management]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[projects]]></category>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[John Connolly, MLIS, PMP]]></dc:creator>
            <pubDate>Mon, 01 May 2023 20:51:45 GMT</pubDate>
            <atom:updated>2023-05-01T20:51:45.159Z</atom:updated>
            <content:encoded><![CDATA[<p>“They’re not usually Lessons Learned,” an experienced project manager once told me. “They’re just Lessons Written Down.”</p><p>I was surprised. I thought everybody knew how important it is to write down what was learned in a project and pass it on to inform and improve processes on future projects. The idea that this was so readily disregarded was troubling at best.</p><p>What was worse, however, was another reaction I got when delving more deeply into the discipline of knowledge management and how it could apply to project management. When I floated some key concepts to some other project managers online, the reaction was tepid. One person went so far as to assert, “That’s the PMO’s job. Mine is the get the project done.”</p><p>It’s obvious that in some corners, we still have a long way to go toward project managers seeing themselves as true change agents and stewards of good practices for their organizations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ffE4JgefS9KMYgPOAZ1ALg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@wesleyphotography?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Wesley Tingey</a> on <a href="https://unsplash.com/photos/snNHKZ-mGfE?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h4>Getting Into Your Head</h4><p>I totally understand why established project managers would avoid true knowledge management. There are lots of competing priorities and those deliverables aren’t going to deliver themselves! But deep down, I think there are some deeper philosophical fault lines to this topic that show room for growth in the project management field.</p><p>As a former librarian and armchair knowledge management enthusiast, I find the approach to knowledge incorporated into PMI’s standards to be both annoying and outdated. The traditional model objectifies knowledge: it’s viewed as a thing that individuals possess. That thing can be transferred from one person to another through a variety of processes. The most important thing for organizations or projects is to ensure the knowledge in the head of one person can be copied into the heads of other people to ensure operational redundancy as work continues.</p><p>This model is simple and intuitive. It creates clear methodological guideposts for facilitating “knowledge transfer.” Usually, this takes the form of documents, documents, and more documents. Training manuals, user guides, artifact repositories, Lessons Learned, the list goes on and on.</p><h4>The Boundaries of a Limited Model</h4><p>Project management has begun to recognize that there are limits to this model. A wrinkle has been incorporated in the form of the distinction between “explicit knowledge” and “tacit knowledge,” with the former meaning technical how-to knowledge that fits cleanly into repositories, and the latter meaning… everything else. The panacea for “tacit knowledge transfer” is interpersonal communication: face-to-face trainings, job shadowing, and mentorship.</p><p>The above theory is barely adequate to the rudimentary functional requirements of work. At what point are we truly managing project knowledge? What kinds of tacit knowledge are there? Does knowledge simply exist, ready for transfer, in the minds of team members? And what about the creation of new knowledge? How does that factor into our goals and how are we managing that?</p><p>The limitations of the simple “knowledge transfer” model become more apparent as we consider the problem of translation. In theory, we should be able to understand the meaning of Shakespeare’s plays, since they were written down in English. But 500 years takes a toll on context. Scholars now argue about the true meanings and you need an advanced degree to truly understand the many subtle (and, in the day, overt) meanings and slang included.</p><p>I’m certain these points annoy some project managers as being an unnecessary bother when we already have repositories of meticulously-crafted project artifacts. “If somebody really wants to know,” the argument goes, “all they have to do is read what I wrote. It’s all there.” But this is hardly a solution.</p><p>Writing it down doesn’t ensure true understanding. Words on a page are subject to interpretation and nuance that might not have been intended. Once a knower writes down the knowledge and moves on, everybody left with the document must interpret as best as they can.</p><h4>Where We Should Focus</h4><p>The tricky thing about knowledge management is that success is highly context-sensitive. What works really well for one organization might be disastrous for another. As project managers begin to put greater emphasis on business value and their role as organizational change agents, we also need to see ourselves as knowledge stewards. This will be woven into our influence for our teams, our cultures, and our organizations.</p><p>Knowledge can’t be managed directly. Like risk, we manage it indirectly. Knowledge is spread and altered and communicated, usually without permission. “How we work here” simply exists, and it is taught to others because knowledge is a massive (and often hidden) part of organizational culture.</p><p>To exert influence on knowledge, we have to create structures and initiatives to set adequate guardrails for how knowledge is shared. Is a repository of documents enough for certain kinds of knowledge? Yes. But the interpersonal, collaborative, and in-real-time knowledge should be addressed as well.</p><p>Project managers are immensely powerful for their organizations. They hold a wealth of knowledge and create new knowledge throughout the project lifecycle. The timely and thorough sharing of this knowledge can make or break organizations. In this light, good knowledge management is far more vital than mere process improvement is. It’s an ethical responsibility to pass along new knowledge and to ensure it is adequately understood.</p><p><em>John Connolly, PMP is a project manager, trainer, author, and consultant. You can </em><a href="https://www.linkedin.com/in/johnconnolly058/"><em>follow him on LinkedIn</em></a><em> and discuss project management approaches, knowledge management principles, and why frogs are the coolest creatures in the animal kingdom.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ca1863be598" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[No, AI Won’t Kill Project Management… Or Save It]]></title>
            <link>https://medium.com/@salientian/no-ai-wont-kill-project-management-or-save-it-e5f06410b9d8?source=rss-b1b8c78e1b5f------2</link>
            <guid isPermaLink="false">https://medium.com/p/e5f06410b9d8</guid>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[humanity]]></category>
            <category><![CDATA[chatgpt]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[John Connolly, MLIS, PMP]]></dc:creator>
            <pubDate>Fri, 28 Apr 2023 11:41:18 GMT</pubDate>
            <atom:updated>2023-04-28T11:41:18.281Z</atom:updated>
            <content:encoded><![CDATA[<p>My whole world is buzzing with anticipation and dread at the rise of ChatGPT and its host of digital minions. The prognostications are as wild and outlandish as they are far-reaching and dire. My feed is jammed with AI punditry proclaiming the imminent advent of our new robot overlords, eagerly spilling out their technological fever-dream of a day (soon, of course), when machines relegate us to the dustbin of history.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*hKYITR8C9VO8VxBX" /><figcaption>Photo by <a href="https://unsplash.com/@maximalfocus?utm_source=medium&amp;utm_medium=referral">Maximalfocus</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>The apex of my frustrations came in the form of an article proclaiming that in a matter of months, AI will replace project managers and scrum masters. The example of why this was going to be the case was… I’ll be kind and call it misguided.</p><h4>The Fantastical Prophecy</h4><p>In that article, the author showed how he had fed an AI bot a series of scenarios about an Agile project and asked the bot to serve as a “coach” to diagnose the issues. The answers were precise: they targeted the process and how to optimize it. In fact, the bot was able to replicate all the very worst things about Agile coaching while leaving the best elements behind.</p><p>The author proudly admitted at the end of the article that he had used the AI bot to produce over 90% of the article’s content, an infuriating bit of second-rate plagiarism that added insult to a bad case of missing-the-point.</p><p>It’s probably worth clarifying here that while I have a decidedly dim view of AI’s worth in the long run, I recognize ways in which it can speed certain kinds of work. Integrations with Excel spreadsheets could be promising. If it’s ever strong enough to help with quantitative risk analysis on the cheap, that could be mighty useful. And up-to-the-minute schedule and budget tracking would take a load off the shoulders of predictive project managers.</p><p>However, a bot that mimics conversation or aggregates images is a far cry from those things. Call me a Luddite, but when it comes to doing work or playing with the zombie-est of <a href="https://en.wikipedia.org/wiki/Philosophical_zombie">philosophical zombies</a>, I’ll choose the work every time.</p><h4>The Problem Isn’t AI, It’s Us</h4><p>The failure of project management (and Agile) is in obsession over its tools and processes. The heart and soul of projects is humanity. We produce deliverables because people will value them. And we produce them by bringing together people and getting them to pull together toward a common goal.</p><p>The example of the AI Agile coach completely misses this reality about project work being human work. Like so many project managers and scrum masters alike, it falls prey to the mistaken notion that projects are elaborate machines: if we go to the rulebook and follow the process with religious adherence, we will succeed. The AI Agile coach is no leader of a team. The AI Agile coach is a process referee, an enforcer of procedure without a hope of inspiring the team to follow along.</p><p>The rush to adopt AI as the savior of almighty process reveals the fault lines of project management’s biggest struggles. The idea that AI could kill project management is the worst form of indictment of how project managers are perceived, and their work is valued. If all we do is craft schedules and budgets, well… a machine rightly <em>could</em> do that. If we have a one-size-fits-all procedure to sprint retrospectives, there’s no need for a scrum master. Just hand out books and let the team look it up if there’s ever a question.</p><p>If the Scrum Guide or the PMBOK or the Agile Manifesto are to take up status as immutable scripture, then I’m sorry to say that there are hundreds of eager technophiles ready to make AI the high priest of our religious rituals.</p><h4>The Good News</h4><p>The flip side of this coin is the cold, hard truth: project managers of all varieties bear a tremendous human responsibility to lead. Leadership is not a science, but an art. It takes the kindness and patience to build relationships. It takes the communication skills to inspire and achieve. It takes vision and action in broader organizational and cultural contexts.</p><p>Yes, it takes commitment, courage, focus, openness, and respect.</p><p>If we are failing to live up to these ideals as project managers or Agile practitioners, then we’re failing to serve the role our teams, customers, and organizations need from us. While some are hoping to fill the void with a machine, they won’t find it there. It can only be found in people, ready to serve and open to learning and growth.</p><p>AI won’t kill our field, but it won’t save it, either. Only we can do that. And the only path to growing our relevance is to fully embrace the humanity of what we do… and who we are.</p><p>The reduction of people to cogs in a machine will truly be the death of project management and Agile. We can choose to drown in our 49 processes or our ceremonies, bickering endlessly about methodologies and frameworks as the sun sets and the business world moves on. But it doesn’t need to be that way. And if we can successfully remove ourselves from the process-oriented mire and embrace our calling as leaders, we will enjoy success, relevance, and value beyond the wildest fantasies of AI’s champions.</p><p><em>John Connolly, PMP is a project manager, trainer, author, and consultant. You can </em><a href="https://www.linkedin.com/in/johnconnolly058/"><em>follow him on LinkedIn</em></a><em> and discuss project management approaches, knowledge management principles, and why frogs are the coolest creatures in the animal kingdom.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e5f06410b9d8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What’s Even the Point of Agile?]]></title>
            <link>https://medium.com/@salientian/whats-even-the-point-of-agile-1ca2a93b046b?source=rss-b1b8c78e1b5f------2</link>
            <guid isPermaLink="false">https://medium.com/p/1ca2a93b046b</guid>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[knowledge-management]]></category>
            <category><![CDATA[knowledge]]></category>
            <category><![CDATA[agile-methodology]]></category>
            <dc:creator><![CDATA[John Connolly, MLIS, PMP]]></dc:creator>
            <pubDate>Wed, 26 Apr 2023 01:43:54 GMT</pubDate>
            <atom:updated>2023-04-26T01:43:54.133Z</atom:updated>
            <content:encoded><![CDATA[<p>As I’ve wandered among the Agile sections of the internet, I’ve encountered many ideas and perspectives. Many are insightful and wise. Many are inscrutable and baffling to me. And there’s no view so baffling to me as the purist’s dogmatic adherence to an approach or framework.</p><p>I’ve seen Agile practitioners who swear that every human problem can be solved with Agile. When Agile fails to help certain circumstances, the lack of an Agile mindset is readily blamed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O6pKSyvFTloeYv-92_Yuqw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/ja/@annievo?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Annie Vo</a> on <a href="https://unsplash.com/photos/HUuWNQmW58A?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>No, I don’t think Agile is suited to everything, and I don’t pretend that most Agile practitioners think so, either. Nevertheless, the temptation to focus on processes as supreme is deep-rooted in the human psyche. Human beings love ceremonies, traditions, and rituals. We feed on stories and games and group-building. Agile has a lot of human appeal. But it’s not universally applicable.</p><h4>What Are We Doing Here?</h4><p>In practice, I think people get tripped up when they think of an Agile methodology as a way to produce things. I’ve thought about this over and over, and I just don’t think that’s true.</p><p><strong>Agile doesn’t exist to produce the deliverable. It exists to allow learning.</strong></p><p>The fact that this might appear to be a wild idea is a sign of how far afield Agile practitioners have gone. But as somebody with an information studies background, Agile appears to me to be much better suited as a learning device than as a production tool.</p><p>I want to be clear: Agile teams can and do produce things, but their way of working is not the true measure of their agility. Self-organizing teams of members with broad expertise are often useful, but Agile hardly corners the market in valuing these sorts of arrangements.</p><p>The key, of course, is in the feedback.</p><h4>Learn to Iterate, Learn to Learn</h4><p>Think of how you learn a language. You can study grammar, memorize vocabulary, and take classes to teach pronunciation. But we don’t really become fluent unless we use that language. And in doing so, mistakes will be made.</p><p>Another example is in learning to walk. How many times do we fall down before we learn to stand upright? Lots.</p><p>The hallmark of learning is that it takes place through iteration. That looks like this:</p><ol><li>Define a hypothesis</li><li>Experiment to test the hypothesis</li><li>Validate or invalidate the hypothesis</li><li>Revise the hypothesis based on results</li></ol><p>This is the soul of Agile: the scientific method. The scientific method isn’t about technological advancement or inventions that make life better. It’s about learning. And so is Agile. Don’t believe me? Check this out from the 2020 Scrum Guide:</p><blockquote>Scrum is founded on empiricism and lean thinking. Empiricism asserts that knowledge comes from experience and making decisions based on what is observed. Lean thinking reduces waste and focuses on the essentials.</blockquote><p>Agile is a learning tool. It allows learning (feedback) that will inform our production. This helps keep us efficient. And superior knowledge is like a mirror that can be held up to our processes… not to judge and eliminate them, but to improve them:</p><blockquote>Various processes, techniques and methods can be employed within the framework. Scrum wraps around existing practices or renders them unnecessary. Scrum makes visible the relative efficacy of current management, environment, and work techniques, so that improvements can be made.</blockquote><p>To me, this hardly reads as a prescriptivist set of rituals. Rather, this is a thoughtful context for a framework that prides itself on adaptation in the face of newly-created knowledge.</p><h4>The Real Product of Agile: New Knowledge</h4><p>All projects create new knowledge. A critical shortcoming of waterfall approaches is that this fact is not (comparatively) highly valued compared to processes. Enter Agile, a framework dedicated to deliberate generation of new knowledge. The beauty of it is that it incorporates that knowledge into the work quickly and promotes shareability of the knowledge across the team.</p><p>Like every project approach, though, this system hasn’t been optimized to its strengths (at least, not universally). As long as the focus is on the process for governing work, we’re missing the point. Agile isn’t a way of working. It’s a way of learning. Are we paying attention to <em>how</em> we’re learning? Or are we focused on learning fast, blasting through our lessons recklessly?</p><p>Beyond this, Agile practitioners need to discover more than their inner coach: they need to swim deeply in the pool of knowledge management and education. This is an ethical responsibility that goes much further than facilitating Agile practices. The lessons that we learn must be radiated up and out through our organization.</p><p>Through Agile, we can quickly learn about customers and what they value. But we learn many, many more things on the way to that, too. We learn personalities, needs, desires, trends, innovations, and much, much more. Many of these lessons could drive tremendous value to the organization as a whole. Are we <em>sure</em> that we’re not casting aside important things in our rush to “fail fast” and deliver an MVP as quickly as possible? Or are we sacrificing the very thing Agile does best in the interest of production processes?</p><h4>The Agile Knowledge Sharers</h4><p>Knowledge is a tricky thing. It’s not a static item that you can pull out of one person and put in another. It’s alive and growing and fading all at once. It’s both individual and communal. If anybody shirks the responsibility to manage knowledge, the whole thing becomes harder to do.</p><p>Agile is an extremely powerful set of tools, but Agile teams bear a heavy responsibility to manage the knowledge they create, saving and sharing it appropriately as new lessons are generated. As Adam Savage of Mythbusters fame once quipped, “The only difference between screwing around and science is writing it down.” Lessons need to be acted upon, yes, but also shared.</p><p>This perspective shouldn’t worry us that we’re distracting from Agile’s true calling. In fact, I would say that <strong>while I don’t think Agile is universally applicable as a way of working, it’s critically applicable as a way of learning.</strong> In this sense, I think Agile is more important than ever before. We live in a business environment overflowing with data points, information, and knowledge. Agile practitioners are sitting on a phenomenally powerful approach for cutting through the noise and deriving value from what is learned. Imagine if that was harnessed daily to serve everybody, not just the interests of a single product.</p><p>If we can orient ourselves toward the reality that our Agile processes are dynamos of knowledge, a whole host of responsibilities opens up. And this means that we should be accounting for this in our mindset and in our processes. The true callings of Agile practitioners are as learners and teachers. Embracing this role is not a distraction from the work of the Agile team: it’s the final fulfillment of its broader purpose.</p><p><em>John Connolly, PMP is a project manager, trainer, author, and consultant. You can </em><a href="https://www.linkedin.com/in/johnconnolly058/"><em>follow him on LinkedIn</em></a><em> and discuss project management approaches, knowledge management principles, and why frogs are the coolest creatures in the animal kingdom.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1ca2a93b046b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Good Project Managers Ask Great Questions]]></title>
            <link>https://medium.com/@salientian/good-project-managers-ask-great-questions-3c479f3c07c9?source=rss-b1b8c78e1b5f------2</link>
            <guid isPermaLink="false">https://medium.com/p/3c479f3c07c9</guid>
            <category><![CDATA[journaling]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[John Connolly, MLIS, PMP]]></dc:creator>
            <pubDate>Mon, 24 Apr 2023 14:00:55 GMT</pubDate>
            <atom:updated>2023-04-24T14:00:55.971Z</atom:updated>
            <content:encoded><![CDATA[<p>Before I took on management of my first team of more than five people, I was nervous. I wondered if I could successfully provide what the team needed and worried that I wouldn’t possibly have answers for them. One of the things I did to prepare was to open a book by John C. Maxwell called <a href="https://www.amazon.com/Good-Leaders-Ask-Great-Questions/dp/145554809X/"><em>Good Leaders Ask Great Questions</em></a>. It’s an insightful read that I recommend to any leaders in or out of project management.</p><p>The central theme of the book, in its simplest form, is that the best leaders <em>don’t</em> have all the answers. And one of the most critical things you can practice as a leader is being able to ask the right questions at the right time. Teams don’t need a leader to tell them the answers. The team exists to provide solutions. What they need in a leader is help clarifying and framing their questions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Tpn1OieW5xRByAAN1ptK9w.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@gabriellefaithhenderson?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Gabrielle Henderson</a> on <a href="https://unsplash.com/photos/HJckKnwCXxQ?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h4>A Few Good Questions</h4><p>I consider the asking of good questions to be a core “power skill” for project managers. So many good things flow from finding and asking the right questions. As we operate in work environments where we more universally rely on autonomous teams and team members, project managers need to direct the flow of ideas more than the flow of work itself.</p><p>In this context, then, several key concepts emerge. The project manager can’t be prideful. Allowing ourselves to truly serve means having the humility to eschew expert status. Even when we think we know the answer, it can be useful to exercise the humility and patience require to let the team come to an answer independently. Ask good questions instead of giving good answers. The team may surprise you with faster or more elegant solutions than the ones you came up with.</p><p>Another key concept is that project managers must relocate where their work truly “lives” for them. I think that many project managers invest their work into a particular tool, technique, or process. Our work “lives” in a spreadsheet or in Microsoft Project. But as we see ourselves as the servant who focuses the team, our work begins to “live” in our minds. The intellectual work of project management, then, requires non-traditional resources: time alone, silence, reflection, and communal connection with team members.</p><h4>Getting Started With Sample Questions</h4><p>This is all great in theory, but how to get started? I’ve found that the simplest way to begin asking great questions is to absorb great questions from somebody else. Here are some to get you started.</p><ul><li>What are the strengths and weaknesses of our team members?</li><li>Am I working daily to help the team do what it does best?</li><li>Am I delegating where I can?</li><li>Am I giving praise and affirming good performance?</li><li>Why are we doing this project?</li><li>How will we deliver value through this project, and how will I ensure full value is realized?</li><li>Why am I in my role? What satisfies me about my work?</li><li>Why do my stakeholders want what they want?</li><li>Am I building and maintaining relationships across the project landscape?</li><li>Do we understand the needs of the customers/end users of this project?</li><li>Who is part of my “inner circle” to help me make good decisions?</li><li>Am I adequately caring for myself and my wellbeing?</li><li>Am I holding myself accountable in the same way I do my team?</li><li>Am I too attached to one project or work approach over another?</li><li>How am I cultivating diverse opinions and voices on the team?</li><li>What are my values that guide me, and am I reviewing and updating those regularly?</li><li>Do my stakeholders and team trust me and my organization?</li></ul><p>These are simply ideas to get you started, but I think there’s good value in many of these. I also suggest taking time each day (I prefer early in the morning) to sit and ask some of these of yourself. If needed, write these down and write your answers, too (this should be easily incorporated for you daily bullet journalers out there).</p><p>Ask good questions and surround yourself with people who can help you find strong answers. As a question-asker, you will find that you transform your team, your work, and even yourself.</p><p><em>John Connolly, PMP is a project manager, author, and consultant. You can </em><a href="https://www.linkedin.com/in/johnconnolly058/"><em>follow him on LinkedIn</em></a><em> and discuss project management approaches, knowledge management principles, and why frogs are the coolest creatures in the animal kingdom.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3c479f3c07c9" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>