<?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 Conner Brew on Medium]]></title>
        <description><![CDATA[Stories by Conner Brew on Medium]]></description>
        <link>https://medium.com/@conner.brew?source=rss-5368ea679397------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*pFssWxwVmyYlLNDk3Bzehw.jpeg</url>
            <title>Stories by Conner Brew on Medium</title>
            <link>https://medium.com/@conner.brew?source=rss-5368ea679397------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 15:17:20 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@conner.brew/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[Exploratory Product Development for Data & AI Products]]></title>
            <link>https://medium.com/@conner.brew/exploratory-product-development-for-data-ai-products-e519eb43b9d4?source=rss-5368ea679397------2</link>
            <guid isPermaLink="false">https://medium.com/p/e519eb43b9d4</guid>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Conner Brew]]></dc:creator>
            <pubDate>Thu, 16 Nov 2023 14:17:48 GMT</pubDate>
            <atom:updated>2023-11-16T14:17:48.765Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wNzaVwPusXvwUxD0YlahxA.png" /></figure><h4>Embrace Uncertainty</h4><h4>Follow this guide to identify, evaluate, and resolve unknowns to set your product up for success!</h4><p>If you’re a technology or product leader, then you’re probably looking to capitalize on advances in generative AI and data science — you might even already be working on such a project! The problem is this: Generative AI is non-deterministic. It’s inherently riskier than traditional software and has a much higher degree of uncertainty.</p><p>This article will raise the gaps faced by traditional Agile frameworks when faced with emergent technology and teach you about a new framework specifically designed for <strong>investigating</strong> and <strong>resolving</strong> unknowns: <strong>Exploratory Product Development</strong>.</p><h3><strong>What is Exploratory Product Development?</strong></h3><p>In the dynamic and fast-moving landscape of technology, product leaders have to stay one step ahead of the competition at all times. The release of OpenAI’s ChatGPT in November of 2022 changed the tech landscape in many ways, but one change, in particular, has increased the burden of product practitioners: a growing urgency to strategically ideate and explore the applications of <strong>emergent technology</strong>.</p><p>As product leaders begin to develop prototypes and conduct research into processes for developing new technologies like generative AI, media cycles of the past few months have made one thing clear: <strong><em>developing AI products is risky.</em></strong></p><p>The <a href="https://www.pdma.org/default.aspx">Product Development and Management Association</a> champions a development process that is perfectly suited to the task: <strong>Exploratory Product Development (ExPD), </strong>the purpose of which is to reduce product uncertainty that derives from unknowns, <strong><em>thereby reducing overall risk</em></strong>.</p><p>Traditional Agile frameworks <strong>just don’t cut it </strong>when it comes to developing products with high degrees of uncertainty. When there are more unknowns than knowns, you need a specialized process. ExPD is not for every product. It is, however, highly suited for the uncertainty and complexity that populate AI and Data Science projects. This article will give you the tools to implement ExPD on your teams so that you can generate value while minimizing risk and uncertainty.</p><h3><strong>Agile is Dead. Long Live Agile.</strong></h3><p>But <em>what about Agile</em>?</p><p>For decades now, Agile values and principles have dominated thought surrounding software development. Think tank The Standish Group found in <a href="https://vitalitychicago.com/blog/agile-projects-are-more-successful-traditional-projects/">a 2020 study</a> that Agile-run projects continue to outperform non-agile projects, finding that large projects were twice as likely to succeed when run using an Agile framework.</p><p>There are 4 core values of Agile:</p><ul><li>Individuals and interactions over processes and tools</li><li>Working software over comprehensive documentation</li><li>Customer collaboration over contract negotiation</li><li>Responding to Change over following a plan</li></ul><p>These core tenets lay a strong foundation for discovery and development in a software project where the deliverable is fairly well-known. Although there is room for <em>some</em> uncertainty, Agile frameworks like Scrum and Kanban are <strong>best suited for when engineering teams know what they’re going to build</strong> from the beginning.</p><p>If you have ever worked on, been around, or led a software development project, you know that there is one word that will rear its head every time: <strong><em>Unknown</em></strong>.</p><p>When unknowns emerge, as they often do, how does one balance those unknowns against the backdrop of business value? In many projects, this is solved via a technique known as <a href="https://www.productboard.com/glossary/dual-track-agile/">Dual-Track Agile</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PcrPh28pmIr7AP6P" /></figure><p>In Dual-Track Agile, a software team is divided into two lanes: <strong>development</strong> and <strong>discovery</strong>. The discovery lane performs iterative design and research, typically leveraging user feedback and design-thinking principles to ideate features that are valuable for users and the business. In the development lane, the engineering team builds features that have been sufficiently ideated; typically adopting DevOps practices to continuously integrate and deploy functional releases.</p><p><strong>Even Dual-Track Agile has limits<em>. </em></strong>These practices work most effectively when development processes, tools, and techniques are relatively well-understood. Requirements may change; features may change. But, generally speaking, the technology and processes involved with building a mobile or web application are known and largely predictable.</p><h3><strong>Emergent technology requires a different approach.</strong></h3><p>In fields like Research &amp; Development and frontier Data Science, exploring emergent technologies like Generative AI and Spatial Computing, you have to start somewhere. Likely, there are not enough knowns to design, build, and deploy a fully functional product that is both valuable to users and viable to business stakeholders. <strong>When you look across the field and have nothing but questions, even the flexibility of Dual-Track Agile is not enough.</strong></p><p>To begin such a project, apply an ExPD approach. Though it has existed in various forms and states over recent decades, ExPD was formalized in by scholars Kathy Morissey and Mary Drotar in a 2016 article, <a href="https://medium.com/@kathys2m/an-adaptive-approach-to-product-development-exploratory-pd-expd-955682c2418f"><em>An Adaptive Approach to Product Development</em></a>, and subsequently in their 2022 book <a href="https://www.amazon.com/Learn-Adapt-Development-Innovation-Reduction-ebook/dp/B0B813TW82"><em>Learn and Adapt</em></a>.</p><p>By continuously prioritizing the identification and resolution of risky unknowns, teams become better enabled to create value. This occurs over 3 stages:</p><blockquote><em>Phase 1: </em><strong><em>Strategize<br></em></strong><em>Phase 2: </em><strong><em>Ideate and Select<br></em></strong><em>Phase 3: </em><strong><em>Explore and Create</em></strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_dy2-lDiczGvieCh" /></figure><p><strong>Phase One</strong> necessitates the creation of an overall product strategy: what are the organization’s goals and <a href="https://www.svpg.com/business-strategy-vs-product-strategy/">business strategy</a>, and how do products impact those outcomes? This foundational level ensures that products can be traced back to business KPIs and outcomes — teams should have clear alignment between the goals of their product and the business outcomes their product affects.</p><p><strong>Phase Two</strong> dictates how the organization generates and selects new ideas to move forward into development. There are many ways to effectively ideate and prioritize products through a <a href="https://www.ideou.com/blogs/inspiration/what-is-design-thinking">design-thinking approach</a>; this work should associate products with the overall business strategy. This stage must be done before phase three: product teams should only dedicate time to the exploration of ideas that are valuable to the business and its consumers.</p><p><strong>Phase Three</strong> is the nitty gritty of development: it consists of all those steps required to plan, design, build, test, and ship a product: this is the stage of a product’s lifecycle when theory becomes practice. Because phase three is the most hands-on phase as well as the riskiest, this article will focus its attention here.</p><h3><strong>Explore and Create</strong></h3><p>As we drill into the Explore and Create process, we assume that a general business use-case has been selected for development.</p><blockquote><em>The Explore and Create phase of ExPD consists of </em><strong><em>three stages</em></strong><em>:<br>1. </em><strong><em>Investigate</em></strong><em><br>2. </em><strong><em>Resolve</em></strong><em><br>3. </em><strong><em>Launch</em></strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*erRtT0SaUOrBRNfl" /><figcaption>The Explore &amp; Create process is phase three of the Exploratory Product Development framework. This image has been adapted from <em>Learn &amp; Adapt, a book by </em>Kathy Morissey and Mary Drotar.</figcaption></figure><p>In the Investigate stage, teams identify and triage unknowns. Investigation follows this outline:</p><ol><li>Identify uncertainties</li><li>Evaluate uncertainties</li><li>Prioritize uncertainties</li></ol><p>Consider the uncertainties surrounding an AI product: how will we evaluate the system components individually and in aggregate? How will we safeguard the application from jailbreaking or other abuse? How do we ensure the model’s output is factual and reliable? This is the case for product development leveraging any emergent technology: <strong><em>there will always be more uncertainties than there is time to resolve them</em></strong>.</p><p>Therefore, the uncertainties must be <strong>evaluated</strong>. Teams should conduct preliminary research to understand the extent of uncertainty. Consider asking the following questions:</p><ul><li>What research already exists on this topic?</li><li>What tools or techniques exist to mitigate this uncertainty?</li><li>What is the likelihood of this uncertainty causing risk or harm to the project or the application’s users?</li><li>What is the impact of risk or harm to the project or the application’s users?</li></ul><p>Following this exercise, teams will have a robust understanding of the highest-priority uncertainties, a starting point for resolution (i.e. preliminary research), and a sense of scope for each uncertainty.</p><p>These uncertainties then pile into a <strong>prioritization valve</strong>, in which they are prioritized by likelihood &amp; impact of risk.</p><h4>Consider using a scatterplot to calculate priority in this way:</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YRuHR9OGz4_TNKUZ" /></figure><p>Once uncertainties have been <strong>evaluated</strong> and <strong>selected</strong>, put together a plan for resolution of the uncertainty. Teams may conduct further research or build a small prototype as they begin to resolve unknowns and transform them into knowns.</p><p>This process is iterative: items may go through multiple resolution stages before they become knowns. Consider the following example of a product team conducting <strong><em>three</em></strong> resolution stages:</p><ol><li>During <strong>the Investigate stage</strong>, a team building an AI assistant powered by large language model (LLM) prioritized an uncertainty: how to prevent users from jailbreaking the model.</li><li>For their <strong>first resolution stage</strong>, they conduct background research: they read papers and investigate the state-of-the-art. After doing so, they are not yet confident that the uncertainty has been resolved.</li><li>For a <strong>second resolution stage</strong>, they build a small functional prototype to test various techniques they uncovered in research. At the end of this resolution phase, they find that they feel the uncertainty has been resolved. The unknown is now a known.</li><li>Finally, the AI assistant feature enters <strong>the third resolution stage</strong>, in which it is designed, developed, tested, and launched. This final resolution stage includes traditional kanban techniques, which are valuable now that the requirements are known.</li></ol><p>Resolution stages are highly adaptive, and the functions within a resolution stage will vary depending on the maturity of the idea. On the most immature end of the spectrum, resolution may be as little as refining a concept and eliciting further requirements. Resolution may include desk research, targeted user research, product design, or outright development.</p><p>By stepping back to assess the maturity of the idea, teams can flexibly support the product by whatever means necessary to resolve uncertainty, reduce risk, and create value. It’s also likely that a resolution stage might identify or surface new uncertainties: these items should be documented and returned to the prioritization valve for investigation.</p><h3><strong>Take it Away!</strong></h3><p>In the highly adaptive field of AI and data science, there are simply too many unknowns for Agile development frameworks to be effective. As a technology or product leader, you need the right tool for the right job: when your product is mired in uncertainty and risk, you need a risk-mitigation strategy that helps you investigate, evaluate, prioritize, and resolve unknowns. Next time you’re faced with a quagmire of unknowns, don’t panic: leverage Exploratory Product Development to set your product up for success!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e519eb43b9d4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Improve Your Team’s Knowledge-Sharing]]></title>
            <link>https://medium.com/@conner.brew/your-teams-most-valuable-asset-knowledge-d6d9e8b37ff5?source=rss-5368ea679397------2</link>
            <guid isPermaLink="false">https://medium.com/p/d6d9e8b37ff5</guid>
            <dc:creator><![CDATA[Conner Brew]]></dc:creator>
            <pubDate>Mon, 18 Sep 2023 19:14:56 GMT</pubDate>
            <atom:updated>2023-09-19T12:17:32.989Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Yp1aJQWw-rgpI-FjCm5oGQ.png" /></figure><h4>Leading Innovative Cultures</h4><h4>Follow this guide to break down information siloes and stimulate innovation</h4><p>It’s no secret that, in today’s dynamic market, <em>rapid delivery</em> is the key to success. When teams can move quickly, solve problems creatively, and turn problems into opportunities, organizations thrive. How do the most successful teams do it? It turns out that all teams have access to a secret weapon; a tool that, for many, lies dormant on the shelf: <strong>Knowledge</strong>.</p><blockquote>“The more effectively teams generate and exploit knowledge, the more effectively they can generate value.”</blockquote><p>Countless studies have shown that the more effectively teams generate and exploit knowledge, the more effectively they can generate value. This process, generating value from knowledge, has a more common name: <a href="https://medium.com/@conner.brew/ingredients-of-innovation-a9e3880283e1"><strong>Innovation</strong></a>.</p><p>It’s hardly surprising to consider that more knowledge leads to better innovation. The challenge lies in making it happen: How do leaders ensure knowledge is flowing, not getting bottled up? How do teams remove barriers to work more collaboratively?</p><p>This article will give any leader the tools they need to manage knowledge in their organization, fueling creativity and innovation to help their business grow to new heights. You’ll learn:</p><ul><li><strong>Why</strong> knowledge sharing is <strong>valuable</strong></li><li>The<strong> two stages of knowledge</strong> sharing: transfer and absorption</li><li>Why abosrption fails: <strong>abosrptive capacity</strong></li><li>Common <strong>barriers</strong> to knowledge sharing</li><li>Why <strong>psychological safety</strong> is the most important attribute of a team</li><li>The <strong>role of leaders</strong> in stimulating knowledge sharing</li></ul><h3>The Value of Knowledge</h3><p>In 2022, Vietnamese researchers studied some of the country’s top-performing construction agencies to find out why some projects finished on time or ahead of schedule while others dragged value through the dust (Dang et al., 2022).</p><blockquote><em>They found that </em><strong><em>improving employees’ ability to communicate, learn more job skills, and engage with training opportunities</em></strong><em> directly led to improvements in a vast array of goals across the business:</em></blockquote><blockquote><strong><em>1.</em></strong> Client retention<br><strong><em>2.</em></strong> Long-term financial stability<br><strong><em>3.</em></strong> Firm reputation</blockquote><p>This seems intuitive, doesn’t it? The fact is: When employees feel they are doing meaningful work and have the ability to do it well, they tend to excel. When employees have the opportunity to excel, the business will see it reflected on the bottom line. Engaged and knowledgeable employees retain more clients, make stronger business decisions, and make the company look good!</p><p>As the digital age blends into a new age, rife with artificial intelligence and other futuristic technical achievement, the value of knowledge is greater than ever. Too many leaders have never considered the flow of knowledge in their organization and, at best, allow it to flow inefficiently and ineffectively along unplanned back routes. At worst, leaders actively (if unintentionally) introduce barrier after barrier, grinding the flow of knowledge to a halt.</p><p>If this sounds all too familiar, don’t fret! All problems have solutions — read on to learn more about what knowledge sharing is, what it isn’t, and how to accelerate it toward an all-new competitive edge.</p><blockquote>“At worst, leaders actively (if unintentionally) introduce barrier after barrier, grinding the flow of knowledge to a halt.”</blockquote><h3>What is Knowledge-Sharing?</h3><p><strong>Knowledge sharing</strong> is the most important facet of the knowledge management process. Once knowledge is acquired, it must be shared and subsequently exploited: once knowledge is exploited, it becomes innovation.</p><blockquote><em>Knowledge sharing itself consists of </em><strong><em>two steps</em></strong><em>:</em></blockquote><blockquote><strong><em>1.</em></strong><em> </em>Knowledge <strong>Transfer</strong> <br><strong>2.</strong> Knowledge <strong>Absorption</strong></blockquote><p>Although businesses might have many routes to generating value, this knowledge management process is the most essential: as a mechanism for transforming tacit knowledge into overt knowledge, knowledge-sharing results in the creation of exploitable knowledge that is unique to a particular team, group, or organization.</p><p>The value generated by knowledge sharing cannot be replicated by other organizations — thus, making it the only truly innovative value a business can create!</p><blockquote><strong><em>How do you know</em></strong><em> if knowledge sharing is happening in your organization? </em><strong><em>Try asking these questions:</em></strong></blockquote><blockquote>- Do members of the organization <strong>create and interact with knowledge-based content</strong> (tutorials, documentation, etc)?<br>- Do members of the organization <strong>solve problems creatively</strong>?<br>- <strong>Does information flow efficiently </strong>and quickly throughout the organization?</blockquote><p>If the above is true, then your organization is conducting knowledge sharing. However, you may have read the questions and arrived at a different answer: <em>I don’t know</em>!</p><p>Scholars generally agree that <strong>knowledge sharing creates value in two key ways:</strong></p><p><strong>1.</strong> <strong>Reducing the workload</strong> and time taken by repeated learning (i.e. don’t reinvent the wheel)<br><strong>2.</strong> <strong>Generating creative ideas</strong>; the output of knowledge exploitation being greater than the sum of knowledge transfer</p><h3>Practical Tips: How Knowledge Sharing Happens</h3><p>Knowledge sharing also happens in <strong>two flavors: formal and informal.</strong></p><p><strong><em>Informal knowledge sharing</em> </strong>may be happening around the water cooler, in slack, or via other unplanned and uncontrolled means. <strong><em>Formal knowledge sharing </em></strong>happens in meetings explicitly designed for knowledge sharing or through explicit training and learning &amp; development operations. Healthy organizations need a balance of both.</p><p>Aside from two flavors,<strong> knowledge sharing happens in two directions: vertically and horizontally</strong>. When knowledge is shared vertically, this is called <strong><em>leader-member exchange</em></strong>. It happens when leaders share their vision, goals, and plans, and it also happens when team members provide important information upward like status, risks, or other pertinent information.</p><p>When information flows horizontally, this is called <strong><em>team-member exchange</em></strong>; this occurs when team members share information with each other like tips &amp; tricks, advice on projects, or even just expressing their experiences with one another.</p><blockquote><em>Consider drawing a </em><strong><em>matrix like this</em></strong><em>, and determine what channels exist for knowledge sharing on your team:</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tbXm7P9EAGnblaL5H0hFrg.png" /></figure><h3>Absorptive Capacity</h3><p>Maybe you’ve been trying to share knowledge in your organization, but it just doesn’t seem to stick. You have the <em>knowledge transfer</em> but are lacking the <em>knowledge absorption</em>.</p><p>This is because all organizations have an attribute called <strong><em>absorptive capacity</em></strong>: this <strong>absorptive capacity</strong> limits the amount of knowledge that any organization can effectively absorb and exploit. Consider the image of pouring water into a glass — you can pour the water faster and faster, but the glass can only hold so much water at one time.</p><p>In order to grow your organization’s ability to exploit knowledge, or generate value from knowledge, you have to improve the organization’s absorptive capacity. If no specific thought has been given to this area, your team probably struggles — this is not an attribute that typically improves accidentally or unintentionally.</p><blockquote>“To put it simply, if knowledge is floating around your organization without being absorbed, you might as well be throwing tennis balls at a brick wall.”</blockquote><p>Spanish researchers studied six Spanish businesses in 2016 to determine the extent to which absorptive capacity enabled or limited success: they found that, <strong>with low absorptive capacity, attempts to provide training opportunities or facilitate knowledge transfer had little-to-no effect</strong> (Hernández-Perlines et al., 2016). To put it simply, if knowledge is floating around your organization without being absorbed, you might as well be throwing tennis balls at a brick wall.</p><blockquote><em>Absorptive capacity can be </em><strong><em>improved by incentivizing efforts</em></strong><em> along the following dimensions:</em></blockquote><blockquote><em>1. </em><strong><em>Knowledge Acquisition</em></strong><em>: </em>Incentivize the frequency and variety of sources for knowledge acquisition from both internal and external sources</blockquote><blockquote><em>2. </em><strong><em>Knowledge Value</em></strong><em>: </em>Encourage team members to leverage existing knowledge as a first option rather than a last resort</blockquote><blockquote><em>3. </em><strong><em>Knowledge Exploitation</em></strong><em>: </em>Ensure that team members have clear goals and an understanding of how to contribute to those goals</blockquote><p>Consider the avenues by which you can incentivize your teams to better acquire, recognize, and leverage knowledge on behalf of the organization. Look for opportunities to recognize individuals who have contributed and exploited knowledge, and <strong>find ways to make it easier &amp; faster to access tacit knowledge</strong> that lives throughout the organization. The better your teams absorb knowledge, the more valuable your business will be!</p><h3>Barriers: Why Aren’t People Speaking Up?</h3><p>Let’s say that you’ve done everything right so far. You’ve set up channels for vertical and horizontal knowledge sharing, you’ve provided formal and informal opportunities to do so, and you’ve taken steps to improve and incentivize absorptive capacity. After all that, it still seems that knowledge moves at a crawl. <em>What gives</em>?</p><p>In their book <em>Courageous Cultures</em>, business consultants Karin Hurt and David Dye set out to answer a very specific question: Why does knowledge get left on the shelf? <strong>Why aren’t people willing to speak up?</strong></p><blockquote><strong><em>They found five key reasons</em></strong><em> that people don’t speak up to contribute solutions, suggest innovations, or advocate for their products or customers:</em></blockquote><blockquote><strong><em>1. </em></strong>People think leadership doesn’t want their ideas.<em><br></em><strong><em>2.</em></strong><em> </em>No one asks.<em><br></em><strong><em>3. </em></strong>They lack the confidence to share.<em><br></em><strong><em>4.</em></strong><em> </em>They lack the skills to share effectively.<em><br></em><strong><em>5.</em></strong><em> </em>People don’t think anything will happen, so they don’t bother.</blockquote><p>These problems are directly within the control of leaders! Leaders have the ability to make it known that ideas and contributions are valuable, they can instill confidence and skills through positive reinforcement and strong coaching habits, and they can leverage their leadership authority to facilitate the exploitation of knowledge once it has been shared. By providing <strong>incentives</strong>, <strong>encouragement</strong>, and a <strong>clear vision</strong>, leaders can set the conditions for hospitable knowledge sharing.</p><p>When those conditions don’t exist, it is often reflected in poor <strong>psychological safety</strong>. In Chinese schools, many teachers participate in professional learning communities (PLCs). These PLCs are designed to facilitate knowledge transfer between older, more experienced teachers and their younger counterparts. Likewise, younger teachers may provide innovative insight, especially related to technology, to their older peers.</p><blockquote>“Why share knowledge with people they don’t trust? Why absorb knowledge that came from someone they distrust?”</blockquote><p>In a 2022 study evaluating the effectiveness of PLCs, researchers found psychological safety to be the number one determinant of success or failure (Qu et al., 2022).</p><p><strong>When psychological safety was low</strong>, teachers <strong>weren’t willing to transfer <em>or</em> absorb knowledge</strong>. Why share knowledge with people they don’t trust? Why absorb knowledge that came from someone they distrust?</p><blockquote><em>This </em><strong><em>distrust is exacerbated</em></strong><em> in unhealthy organizations with the following traits:</em></blockquote><blockquote><strong><em>1.</em></strong> Poor communication skills<br><strong><em>2.</em></strong> Inappropriate organizational culture<br><strong><em>3.</em></strong> Lack of management support<br><strong><em>4.</em></strong> Lack of knowledge sharing mechanisms<br><strong><em>5. </em></strong>Lack of familiarity with technology systems</blockquote><p>If these traits sound painfully familiar to you, all is not lost! Once leaders recognize the barriers preventing knowledge sharing, they can begin the process of <strong>replacing those barriers with enablers</strong>: organizational attributes that stimulate and expedite the process of knowledge transfer and absorption. Read on!</p><h3>Psychological Safety: A Foundation of Trust</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*6nYaXFDRQmPywj5X" /></figure><p>Without trust, it is impossible to turn knowledge into value. When individuals don’t trust members of their team, they’re neither willing to give nor receive information. In the earlier-mentioned study of Vietnamese construction agencies, researchers found that <strong>higher trust not only led to greater innovation but overall increases in employee satisfaction and employee retention</strong> (Dang et al., 2022).</p><p>The reality is that <strong>knowledge sharing is risky</strong>: for those transferring knowledge, there is a risk that their ideas may be rejected, ignored, or discarded. For those absorbing knowledge, there is a risk that they may fail. In general, people tend to undervalue the possibility of future value, compared to the risks of the present — this is called <strong><em>discounting the future</em></strong>.</p><p>Because knowledge sharing is an inherently risky activity, it is crucial that individuals feel <strong>psychologically safe to take risks</strong>.</p><blockquote><em>Leadership development consultant Timothy R. Clark, in his book </em>The 4 Stages of Psychological Safety<em>, posits that </em><strong><em>there are four steps</em></strong><em> to pursuing risk-taking innovation in the workplace:</em></blockquote><blockquote><strong><em>1.</em></strong><em> </em><strong>Inclusion</strong> Safety<em><br></em><strong><em>2.</em></strong><em> </em><strong>Learner</strong> Safety<em><br></em><strong><em>3. </em>Contributor</strong> Safety<em><br></em><strong><em>4. </em>Challenger</strong> Safety</blockquote><p>This means that individuals first must feel respected and included. <strong>They have to feel that they belong</strong>. Once a team member feels included, they need <strong>space to learn</strong>. Teams should acknowledge and celebrate mistakes, not attack or vilify them. Eventually, individuals will reach a stage of growth whereupon they can contribute as full members of the team: they achieve new levels of <strong>responsibility</strong> and <strong>accountability</strong>.</p><p>As leaders, we must ensure that team members have ample opportunity to contribute — it may be tempting to default to a state of paternalism or hand-holding in the interest of reducing risk or protecting team members from failure, but this is highly detrimental!</p><p>It is essential for individuals to transition from the “<strong><em>learner</em></strong>” state to the “<strong><em>contributor</em></strong>” state; to contribute distinct value for the team and to feel that their work is meaningful. Once this has occurred, they will begin to journey toward that ultimate pinnacle of psychological safety: challenger safety.</p><p>Once an individual possesses <strong>challenger safety, they will begin to disrupt the status quo</strong>. At this stage, team members will suggest new ways of working, new techniques, new processes, and other innovative ideas. Not all of these ideas will work, but <strong>all of them</strong> are valuable.</p><blockquote>“Knowledge is the secret sauce that makes the whole greater than the sum of its parts!”</blockquote><p>This is why, after studying <strong>180 project delivery teams,</strong> researchers at Google found that the number one determinant of effective team performance was psychological safety. This research, conducted as part of Project: Aristotle, sought to discover what made teams more than a collection of individuals (Schneider, 2017). <strong>Psychological safety enables ideas to flow freely</strong>; knowledge is <strong>transferred</strong>, <strong>absorbed</strong>, <strong>transformed</strong>, and <strong>exploited</strong>. In short, <em>knowledge</em> is the secret sauce that makes the whole greater than the sum of its parts!</p><h3>The Role of the Leader</h3><p>If you’ve made it this far, congratulations! You might be thinking: Now what? Better psychological safety, higher absorptive capacity, more innovation — these things sound great, but how do I make it happen?</p><p>The mantra all leaders must remember is that leaders don’t create value, teams do. Your job as a leader is to be a facilitator: reduce organizational rigidity, leverage networks to stimulate knowledge absorption, and ensure your teams have the resources they need to share knowledge effectively and efficiently. First, take stock of the knowledge sharing channels your team is using: do you have ample opportunity for vertical, horizontal, formal, and informal sharing?</p><p>Second, evaluate the state of psychological safety on your team. Does everyone feel comfortable challenging the status quo with new ideas and innovations? If not, what stage of the psychological safety journey are they on? Look for opportunities to turn learners into contributors and contributors into challengers. If you have challengers already, how do you respond to their challenges? Ensure no idea goes ignored — rejection is better than avoidance!</p><p>Leaders have the opportunity every day to model a culture of participation. Harvard professor Amy Edmondson, author of <em>The Fearless Organization</em>, provides these recommendations to leaders seeking to cultivate psychological safety in their organization (Edmondson, 1999):</p><ol><li>Frame the work as a learning problem, not an execution problem.</li><li>Acknowledge your own fallibility.</li><li>Model curiosity and ask lots of questions.</li></ol><p>If your team grows a powerful culture of safety and recognizes the value of knowledge, then you’re well on your way to transformative creativity. Ensure your team recognizes the value of knowledge acquisition, facilitate channels for the transfer and absorption of knowledge, and cultivate a culture of psychological safety. Then step back and let your teams innovate!</p><h3>References</h3><ul><li>Clark, Timothy R., <em>The 4 Stages of Psychological Safety: Defining the Path to Inclusion and Innovation</em>. Oakland, CA: Berrett-Koehler Publishers, 2020.</li><li>Dang, Chau Ngoc, Long Le-Hoai, and Vachara Peansupap, “Linking Knowledge Enabling Factors to Organizational Performance: Empirical Study of Project-Based Firms.” <em>International Journal of Construction Management</em> 22 (3), 2022. 527–540.</li><li>Edmondson, Amy, “Psychological Safety and Learning Behavior in Work Teams.” <em>Administrative Science Quarterly</em> 44 (2), 1999. 350–383.</li><li>Hernández-Perlines, Felipe, Juan Moreno-Garcia, and Benito Yáñez-Araque, “Using Fuzzy-Set Qualitative Comparative Analysis to Develop an Absorptive Capacity-Based View of Training.” <em>Journal of Business Research</em> 69 (4), 2016.1510–1515.</li><li>Hurt, Karin, and David Dye, <em>Courageous Cultures: How to Build Teams of Micro-Innovators, Problem Solvers, and Customer Advocates</em>. New York, NY: HarperCollins Leadership, 2020.</li><li>McChrystal, Stanley, Tantum Collins, David Silverman, and Chris Fussell, <em>Team of Teams: New Rules of Engagement for a Complex World</em>. New York, NY: Portfolio Publishing, 2015.</li><li>Mutonyi, Barbara Rebecca, terje Slatten, Gudbrand Lien, and Manel Gonzalez Pinero, “The Impact of Organizational Culture and Leadership Climate on Organizational Attractiveness and Innovative Behavior: A Study of Norwegian Hospital Employees.” <em>BMC Health Services Research</em> 22 (1), 2022. 1–19.</li><li>Qu, Yun, Jinjie Zhu, and Roger D. Goddard, “Modesty Brings Gains: Linking Humble Leadership to Knowledge Sharing via Psychological Safety and Psychological Empowerment in Professional Learning Communities.” <em>Educational Studies</em>, 2022. 1–22.</li><li>Rivera, Angel Eustorgio, Lucia Rodriguez-Aceves, and Barbara I. Mojarro-Duran, “Enabling Knowledge Sharing Through Psychological Safety in Inter-Organizational Arrangements.” <em>Journal of Knowledge Management</em> 25 (5), 2021. 1170–1193.</li><li>Salehi, Mahdi and Sami Abdulridha Sadeq Alanbari, “Knowledge Sharing Barriers and Knowledge Sharing Facilitators in Innovation.” <em>European Journal of Innovation</em>, 2023. 1–21.</li><li>Schneider, Michael, “Google Spent 2 Years Studying 180 Teams. The Most Successful Ones Shared These 5 Traits.” <em>INC.</em> 2017. <a href="https://www.inc.com/michael-schneider/google-thought-they-knew-how-to-create-the-perfect.html">https://www.inc.com/michael-schneider/google-thought-they-knew-how-to-create-the-perfect.html</a></li><li>Sun, Yuping, and Jiatao Huang, “Psychological Capital and Innovative Behavior: Mediating Effect of Psychological Safety.” <em>Social Behavior and Personality: An International Journal</em> 47 (9), 2019. 1–7.</li><li>Ye, Pinghao, Liqiong Liu, and Joseph Tan, “Creative Leadership, Innovation Climate, and Innovation Behavior: The Moderating Role of Knowledge Sharing in Management.” <em>European Journal of Innovation Management</em> 25 (4), 2022. 1092–1114.</li><li>Zhao, Shuliang, Yanhong Jiang, Xiaobao Peng, and Jin Hong, “Knowledge Sharing Direction and Innovation Performance in Organizations: Do Absorptive Capacity and Individual Creativity Matter?” <em>European Journal of Innovation Management</em> 24 (2), 2021. 371–394.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d6d9e8b37ff5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Lead Innovation]]></title>
            <link>https://medium.com/@conner.brew/ingredients-of-innovation-a9e3880283e1?source=rss-5368ea679397------2</link>
            <guid isPermaLink="false">https://medium.com/p/a9e3880283e1</guid>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[creativity]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Conner Brew]]></dc:creator>
            <pubDate>Fri, 28 Jul 2023 13:34:29 GMT</pubDate>
            <atom:updated>2023-09-18T19:15:36.785Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0EhrYN-bLA8wZM7EoERJpw.png" /></figure><h4>Leading Innovative Cultures</h4><h4>Three Keys to Create Conditions for Creative Problem-Solving</h4><p><strong>Innovation</strong> is the lifeblood of product teams. When product teams innovate, it keeps organizations on the cutting edge — and it keeps the competition falling behind. What many teams fail to realize, however, is that <strong>innovation doesn’t happen by accident</strong>. This article will answer the following questions:</p><ul><li>What is innovation?</li><li>How does innovation happen?</li><li>How can leaders design environments to spur innovation on?</li></ul><h3>Defining Innovation</h3><p>Like most buzzwords, “<strong><em>Innovation</em></strong>” is one whose meaning is nebulous (at best). Innovation is a blanket term that covers the generation, introduction, and application of new ideas. Ultimately, <strong>innovation is the process by which organizations extract value from knowledge </strong>— typically when that knowledge is used in novel ways to produce a new or improved solution to an existing problem.</p><p>If you’re a product company (or any company, for that matter), you want your people to innovate as often as possible. <strong><em>Innovation behavior</em></strong> can happen through individuals or through teams — it happens when members of the organization consciously and intentionally realize new ideas, generating new value, on behalf of the betterment of the organization. A study published in 2010 in the Journal of Creativity and Innovation Management posits that there are<strong> four stages of innovation</strong>:</p><ol><li>Opportunity Exploration</li><li>Idea Generation</li><li>Championing</li><li>Application</li></ol><p>As a leader, whether over a single product team or many, how can you engineer the conditions to make innovation possible?</p><blockquote><em>While </em><strong><em>leaders might not have control over everything, </em></strong><em>they can control the </em><strong><em>three main ingredients</em></strong><em> for an environment of innovation:</em></blockquote><blockquote><strong><em>1. </em></strong><em>Diverse Teams</em><strong><em><br>2. </em></strong><em>Supportive Leadership</em><strong><em><br>3. </em></strong><a href="https://medium.com/@conner.brew/your-teams-most-valuable-asset-knowledge-d6d9e8b37ff5"><em>Knowledge-Sharing</em></a><em> Processes</em></blockquote><h3>Ingredient Number One: Diverse Teams</h3><h4>Cognitive Diversity</h4><p><strong>Diversity is a fundamental prerequisite for innovation</strong>. In particular, recent scholarly research consistently points to the importance of <strong><em>cognitive diversity</em></strong>. Cognitive diversity encompasses all the different ways we view the world as a result of our experiences, professional and academic backgrounds, and individual human-ness. When people bring<strong> different perspectives</strong> to the table, it supercharges opportunities for exploration and idea generation.</p><p><strong>Consider this</strong>: in a 2009 experiment evaluating the importance of new ideas in problem-solving, researchers divided a group of students into teams of three to solve a murder mystery. After 20 minutes, some groups were joined by a fourth member whose job was to challenge the other three team members’ solutions. Teams who received this injection of new perspective and challenge to existing ideas were <strong>more than twice as likely</strong> to solve the mystery!</p><p>In fact, research shows again and again that<strong> teams with diverse members</strong>, whether it be diversity in life experience, backgrounds, or even just different job titles,<strong> are far better at coming up with innovative solutions</strong> to tough problems.</p><p>Alongside the clear benefits of diversity, however, team leaders must be mindful that <strong>diverse teams can also result in conflict</strong>. When people come together with different ways of working, different habits, and different ideas, it takes time to organize those ideas and settle on shared norms that empower the team to work collaboratively. Teams can overcome these challenges by <strong><em>grounding</em> </strong>— taking intentional time for uncovering unspoken expectations, aligning on ways of working together, and explicitly working to share information and arrive at mutual norms. Once this happens, the team begins to adopt a sense of <strong><em>collective identity</em></strong> that fuels innovation!</p><h4>Collective Identity</h4><p>Identity, as it relates to an organization, has two elements: the identity of the organization itself (its <strong><em>collective identity</em></strong>), and the degree to which individuals within the group feel they are aligned to that identity. This second element is known as <strong><em>person-organization fit</em></strong>. Person-Organization fit is the compatibility between individuals and organizations; it emerges when an individual feels that the organization shares their values — the stronger the sense of shared values, the greater the fit.</p><p><strong><em>Shared values</em></strong> work like a GPS keeping the team traveling together. Over time, a diverse team will drift apart; the values they bring with them from a lifetime of experience will rub against one another and cause conflict with the group’s shared values. The leader plays a key role in this — uncover the team’s shared values through grounding exercises, then periodically check the temperature of these values throughout the lifetime of the team.</p><blockquote><strong><em>A practical idea: </em></strong>after your team’s first <strong>grounding session</strong>, write down a list of the team’s shared values. After every milestone your team shares (for agile teams, sprint retrospectives are perfect for this) have your team rate the current status of each value on a scale of 1–10. This will reveal how your values may be drifting over time so that you can right the ship before it gets off course!</blockquote><p>Shared values are great for keeping a team on a course together — but that course is useless without a destination. That destination is your <strong><em>shared vision</em></strong>, which is absolutely essential to collaborative innovation. The shared vision is a clear definition of what the outcome should be — even in innovation work, teams should understand what the goal looks like. By including your team in conversations about what you’re trying to accomplish and (sometimes even more importantly), what you’re <em>not</em> trying to accomplish, you maximize their ability to work together to solve problems.</p><p>By enforcing a shared vision and shared values on your team, you cultivate a powerful sense of collective identity. When that identity meshes with the individuals on your team, you become unstoppable! But what do you do if individuals on your team don’t always mesh, even after grounding? That’s where supportive leadership skills come into play.</p><h3>Ingredient Number Two: Supportive Leadership</h3><h4>Transformational Leadership</h4><p>Supportive leadership is exactly what it sounds like — a leader who supports you. In particular, research has found a specific leadership style to be particularly effective in cultivating innovation; especially in hybrid and virtual teams: <strong>Transformational Leadership</strong>. Transformational leaders clearly communicate goals and visions, work with individuals one-on-one to cultivate growth, and they bring their authentic selves into every professional interaction.</p><p>Being authentic means being genuine (you are who you say you are), trustworthy (you do what you say you’ll do), and, most importantly of all, you actually care about the individuals you’re leading. You take the time to listen to their goals, expectations, and fears. You work with them to understand how those goals, expectations, and fears impact and are impacted by their work on the team.</p><p>When leaders demonstrate authenticity and compassion, employees grow in their perception of trust. This, in turn, enhances the ability of the group to share ideas both horizontally and vertically, incentivizing individual motivation to pursue innovative behavior for the benefit of the collective as a whole.</p><blockquote>“Autonomy doesn’t mean isolation. Support your team by making sure they have what they need to get the job done.”</blockquote><h4>Supportive Autonomy</h4><p>When under the influence of a transformational leader, teams become empowered to pursue creative innovation. However, this only works to the extent that individuals and teams have the ability to make progress with the resources they have — when they don’t have the right resources, teams experience a significant negative impact on innovation. That’s where <strong>supportive autonomy</strong> comes in.</p><p>Supportive autonomy means that teams have the autonomy to move creatively, but the support needed to actually get things done. It comes down to whether individuals feel like they have choices, or whether they’re being controlled. Whether they have tools or unmet needs. Most importantly, it comes down to whether they feel they are being cared for.</p><p>In a study conducted on performance improvements in a hospital environment, researchers found that employees were able to solve problems far more creatively and effectively when leaders provide “meaningful rationale for doing tasks, emphasize choice over control, and acknowledge employees’ feelings and perspective”.</p><blockquote><em>Some </em><strong><em>practical tips</em></strong><em> for increasing a sense of supportive autonomy on your teams:</em></blockquote><blockquote><strong><em>1. </em></strong>Use one-on-one meetings with team members to review desired outcomes. Make sure everyone understands the vision.<em><br></em><strong><em>2. </em></strong>Reward team members who speak up and challenge ideas, rather than punishing them.<em><br></em><strong><em>3.</em></strong> Instead of attacking failure, acknowledge it as a learning opportunity.</blockquote><p>By pursuing <strong>psychological safety</strong> in the workplace, you create an environment of supportive autonomy that allows your teams to thrive!</p><h3>Ingredient Number Three: Knowledge-Sharing</h3><p>Effective innovation is not only the result of individual brilliance but rather the result of sustained collective action. For innovation to thrive, teams need structures in place to support knowledge-sharing vertically and horizontally — with leaders and peers. These two forms of knowledge-sharing are called<strong> Leader-Member Exchange</strong> and <strong>Team-Member Exchange</strong>, respectively. Leaders should be intentional about designing opportunities for both formal and informal exchange of ideas in both instances!</p><h4>Leader-Member Exchange</h4><p>One of the ingredients of innovation that leaders have the most direct control over is: the relationship employees have with their boss. When employees feel like they have a good relationship with their immediate supervisor, they are far more likely to engage in activities that are good for the organization as a whole. This relationship comes about through a steady flow of information, support, and positive feedback — scholars universally agree that encouragement coming from a direct supervisor is absolutely critical to successful innovation.</p><p>Not only do encouragement and positive feedback contribute to innovation behavior, but research on innovation in online communities has found that even critical and constructive feedback stimulates innovation far more than no response at all.</p><p>So what can you do as a leader to facilitate greater degrees of vertical knowledge-sharing, otherwise known as leader-member exchange? <strong>Here are some practical tips</strong>:</p><ul><li>Have a clear vision. Teams need to know what target they’re aiming at!</li><li>Provide positive feedback and acknowledgment as goals are accomplished, tasks are completed, and teams achieve small wins.</li><li>Even if an innovation doesn’t meet the need, it’s better to provide negative or critical feedback than none at all. Acknowledge the hard work that went into the idea, and encourage the team to keep trying!</li></ul><blockquote>“A guiding coalition made up of only managers — even superb managers who are wonderful people — will cause major change efforts to fail.” ~ John Kotter</blockquote><h4>Team-Member Exchange</h4><p>Possibly the single most important element of team innovation is <strong>knowledge-sharing</strong> within and across teams. When this team-member exchange is high, individuals are able to share expertise, provide feedback to one another, and support each other. Successful organizations recognize that true value doesn’t come from outside the organization (e.g. customers or clients), but the true value comes from inside the organization (from the teams themselves). This cultural emphasis on generating value from the inside out is called an <strong><em>internal market-oriented culture</em></strong>, or IMOC. In an IMOC, organizations prioritize the motivation, inspiration, and encouragement of their teams over the elicitation of value from clients or customers.</p><p>In his seminal work on change management, <em>Leading Change</em>, Harvard Business professor John Kotter wrote that “A guiding coalition made up only of managers — even superb managers who are wonderful people- will cause major change efforts to fail”. Why is that? To put it simply, even the best manager in the organization does not create value. The teams on the ground create value.</p><p>When this simple fact is understood, leaders are better able to orient themselves to focus on crafting an environment that empowers knowledge-sharing, inspiration, and encouragement within and across teams. In a research study conducted on innovation to improve patient care in Norway’s healthcare system, researchers found that employees’ abilities to communicate and implement novel ideas both formally and informally were absolutely vital to improving patient care throughout the hospital.</p><blockquote><em>Here are some </em><strong><em>practical methods</em></strong><em> the employees used to share information:</em></blockquote><blockquote>- Formally organized communities of practice<br>- Informal water-cooler-esque brainstorming sessions<br>- Public transparent communications channels (like Slack)<br>- Shared knowledge repositories (like confluence, notion, or other company ‘wiki’ systems)</blockquote><p>As a leader, you should encourage informal conversations rather than stifle them. It is tempting to want to control the conversation so that the best ideas flow through you — after all, that’s how you get credit, right? But the best thing a leader can do is allow their people to work together by whatever means at their disposal. Foster an environment of open communication, and watch the magic unfold!</p><blockquote>“Leaders Don’t Create Value. Teams do.”</blockquote><h3>Conclusion</h3><p>Leaders operate best when they recognize that value doesn’t come from outside the organization, it comes from within. The best leaders focus on empowering their teams to innovate, leveraging their diverse backgrounds and experiences to solve problems creatively. However, contrary to popular belief, innovation doesn’t just magically happen — leaders have the power to cultivate an environment where innovation can flourish.</p><blockquote><em>To do this, follow these tips:</em></blockquote><blockquote><strong><em>1</em></strong><em>. Build </em><strong><em>diverse</em></strong><em> teams<br></em><strong><em>2</em></strong><em>. Take intentional time to develop and </em><strong><em>foster collective identity</em></strong><em> through shared values and shared vision<br></em><strong><em>3</em></strong><em>. </em><strong><em>Be a transformative leader</em></strong><em> by being an authentic one. Take time to care for your team as real human beings; get to know them, their priorities, and their challenges.<br></em><strong><em>4</em></strong><em>. </em><strong><em>Autonomy doesn’t mean isolation</em></strong><em>. Support your team by ensuring they have what they need to do the job.<br></em><strong><em>5</em></strong><em>.</em><strong><em> Encourage your team </em></strong><em>through regular feedback, and continuously reinforce the vision.<br></em><strong><em>6</em></strong><em>. Foster spaces for </em><strong><em>formal and informal knowledge-sharing</em></strong><em>. Keep your team informed, and allow them to keep each other informed.</em></blockquote><p>Just remember: <strong>Leaders don’t create value. Teams do.</strong> Prioritize your day according to that principle, and let the magic happen!</p><h3>References</h3><ol><li>Becker, Laura. “Leadership in Innovation Communities: The Impact of Transformational Leadership Language on Member Participation.” <em>Journal of Product Innovation Management</em> 39, no. 3 (2022) 371–393.</li><li>Kotter, John P. <em>Leading Change</em>. Brighton, MA: Harvard Business Press, 1996.</li><li>Mutony, Barbara Rebecca, Terje Slatten, Gudbrand Lien, and Manel Gonzalez-Pinero. “The Impact of Organizational Culture and Leadership Climate on Organizational Attractiveness and Innovative Behavior: A Study of Norwegian Hospital Employees.” <em>BMC Health Services Research</em> 22, no. 1 (2022) 1–19.</li><li>Seong, Jee Young, and Jin Nam Choi. “Is Person-Organization Fit Beneficial for Creativity? Moderating Roles of Leader-Member and Team-Member Exchange Quality.” <em>Human Performance</em> 32, no 3–4 (2019) 129–144.</li><li>Shepherd, Dean A., Nicola Breugst, and Holger Patzelt. “A Founding-Team Model of Creating a Venture’s Culture.” <em>Journal of Business Venturing</em> 38, no. 2 (2023) 1–17.</li><li>Snow, Shane. <em>Dream Teams: Working Together Without Falling Apart</em>. Alberta, CAN: Portfolio Publishing, 2018.</li><li>Tate, Kaitlyn, Tatiana Penconek, Bruna Moreno Dias, Greta G. Cummings, and Andrea Bernardes. “Authentic Leadership, Organizational Culture and the Effects of Hospital Quality Management Practices on Quality of Care and Satisfaction.” <em>Journal of Advanced Nursing</em> no. 1 (2023) 1–13.</li><li>Van der Voet, Joris, and Bram Steijn. “Team Innovation Through Collaboration: How Visionary Leadership Spurs Innovation Via Team Cohesion.” <em>Public Management Review</em> 23, no. 9 (2021) 1275–1294.</li><li>Ye, Pinghao, Liqiong Liu, and Joseph Tam. “Creative Leadership, Innovation Climate, and Innovation Behavior: The Moderating Role of Knowledge Sharing in Management.” <em>European Journal of Innovation Management</em> 25, no. 4 (2022) 1092–1114.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a9e3880283e1" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>