<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>Teamwork on Grizzlebit</title>
  <subtitle>Ray Grasso's Blog</subtitle>
  <updated>2026-04-12T13:36:42.230076+08:00</updated>
  <id>https://www.grizzlebit.com/tags/teamwork/feed.xml</id>
  <link rel="alternate" type="text/html" href="https://www.grizzlebit.com/tags/teamwork/"/>
  <link rel="self" type="application/atom+xml" href="https://www.grizzlebit.com/tags/teamwork/feed.xml"/>
  <rights>Copyright © 2026, Ray Grasso</rights>
  <author>
    <name>Ray Grasso</name>
  </author>
  <icon>https://www.grizzlebit.com/images/icon.png</icon>
  <logo>https://www.grizzlebit.com/images/icon.png</logo>
  
  <entry>
    <id>https://www.grizzlebit.com/links/2025/04-19-developing-relationships-across-the-organisation/</id>
    <published>2025-04-19T09:57:27+08:00</published>
    <updated>2025-04-19T09:58:02+08:00</updated>
    <author><name>Ray Grasso</name></author>
    
    <title>Developing Relationships Across the Organisation ↬</title>
    <content type="html" xml:base="https://www.grizzlebit.com/links/" xml:lang="en"><![CDATA[<div>
  <p>Jason Yip:</p>
<blockquote>
<p>Good relationships facilitate future support and creates advocates. Being able to get something done is not just about your individual capability but also about your influence with the stakeholders and teams that you depend on.</p></blockquote>

  <p>
    
    <a href="https://www.grizzlebit.com/links/2025/04-19-developing-relationships-across-the-organisation/">↬</a>
     ∙ Tagged in <a href="https://www.grizzlebit.com/tags/career/">Career</a>, <a href="https://www.grizzlebit.com/tags/leadership/">Leadership</a>, <a href="https://www.grizzlebit.com/tags/teamwork/">Teamwork</a>.</p>
</div>
]]></content>
    <link rel="alternate" href="https://jchyip.medium.com/diy-leadership-development-develop-relationships-across-the-organisation-0155a86f6ce7"></link>
    <link rel="related" href="https://www.grizzlebit.com/links/2025/04-19-developing-relationships-across-the-organisation/"></link>
    
  </entry>
  
  <entry>
    <id>https://www.grizzlebit.com/links/2024/12-08-calling-out-room-dynamics/</id>
    <published>2024-12-08T12:54:13+10:00</published>
    <updated>2024-12-08T13:01:38+10:00</updated>
    <author><name>Ray Grasso</name></author>
    
    <title>Calling Out Room Dynamics ↬</title>
    <content type="html" xml:base="https://www.grizzlebit.com/links/" xml:lang="en"><![CDATA[<div>
  <p>The art of naming what&rsquo;s happening in the room to get things back on track.</p>

  <p>
    
    <a href="https://www.grizzlebit.com/links/2024/12-08-calling-out-room-dynamics/">↬</a>
     ∙ Tagged in <a href="https://www.grizzlebit.com/tags/leadership/">Leadership</a>, <a href="https://www.grizzlebit.com/tags/teamwork/">Teamwork</a>.</p>
</div>
]]></content>
    <link rel="alternate" href="https://leadership.garden/calling-out-room-dynamics/"></link>
    <link rel="related" href="https://www.grizzlebit.com/links/2024/12-08-calling-out-room-dynamics/"></link>
    
  </entry>
  
  <entry>
    <id>https://www.grizzlebit.com/links/2024/06-08-creating-cultures-of-growth/</id>
    <published>2024-06-08T16:27:44+10:00</published>
    <updated>2024-06-08T16:30:53+10:00</updated>
    <author><name>Ray Grasso</name></author>
    
    <title>Creating Cultures of Growth ↬</title>
    <content type="html" xml:base="https://www.grizzlebit.com/links/" xml:lang="en"><![CDATA[<div>
  <p>Mary C. Murphy on the culture around growth mindsets.</p>

  <p>
    
    <a href="https://www.grizzlebit.com/links/2024/06-08-creating-cultures-of-growth/">↬</a>
     ∙ Tagged in <a href="https://www.grizzlebit.com/tags/growth/">Growth</a>, <a href="https://www.grizzlebit.com/tags/teamwork/">Teamwork</a>.</p>
</div>
]]></content>
    <link rel="alternate" href="https://youarenotsosmart.com/2024/03/22/yanss-283-how-to-create-cultures-of-growth-instead-of-creativity-crushing-cultures-of-genius/"></link>
    <link rel="related" href="https://www.grizzlebit.com/links/2024/06-08-creating-cultures-of-growth/"></link>
    
  </entry>
  
  <entry>
    <id>https://www.grizzlebit.com/links/2023/08-29-managing-stakeholders-when-they-want-to-know-when-something-will-be-finished/</id>
    <published>2023-08-29T10:46:29+10:00</published>
    <updated>2023-08-29T10:50:44+10:00</updated>
    <author><name>Ray Grasso</name></author>
    
    <title>Managing Stakeholders When They Want to Know When Something Will Be Finished ↬</title>
    <content type="html" xml:base="https://www.grizzlebit.com/links/" xml:lang="en"><![CDATA[<div>
  <p>Johanna Rothman:</p>
<blockquote>
<p>But instead of placating the managers and trying to estimate, consider starting with this question:</p>
<p>How do you plan to use this information?</p>
<p>That might offer you ways to answer the question that does not require any prediction.</p></blockquote>
<p>Also read <a href="https://www.jrothman.com/mpd/2023/08/how-to-predict-when-the-team-will-complete-a-specific-backlog-item-part-1/">part one</a> and <a href="https://www.jrothman.com/mpd/2023/08/summary-for-how-to-predict-when-the-team-will-finish-a-specific-backlog-item-part-3/">part three</a>.</p>

  <p>
    
    <a href="https://www.grizzlebit.com/links/2023/08-29-managing-stakeholders-when-they-want-to-know-when-something-will-be-finished/">↬</a>
     ∙ Tagged in <a href="https://www.grizzlebit.com/tags/product-development/">Product Development</a>, <a href="https://www.grizzlebit.com/tags/teamwork/">Teamwork</a>.</p>
</div>
]]></content>
    <link rel="alternate" href="https://www.jrothman.com/mpd/2023/08/how-to-steer-the-conversation-when-someone-asks-for-a-specific-backlog-item-prediction-part-2/"></link>
    <link rel="related" href="https://www.grizzlebit.com/links/2023/08-29-managing-stakeholders-when-they-want-to-know-when-something-will-be-finished/"></link>
    
  </entry>
  
  <entry>
    <id>https://www.grizzlebit.com/posts/2023/08-19-the-trusted-advisor/</id>
    <published>2023-08-19T14:54:35+08:00</published>
    <updated>2024-10-09T19:37:55+10:00</updated>
    <author><name>Ray Grasso</name></author>
    
    <title>The Trusted Advisor 📚</title>
    <content type="html" xml:base="https://www.grizzlebit.com/posts/" xml:lang="en"><![CDATA[<div>
  <figure class="half-wide"><a href="https://trustedadvisor.com/books/the-trusted-advisor"><img src="/images/books/the-trusted-advisor.jpg"
    alt="The Trusted Advisor"></a>
</figure>

<p><a href="https://trustedadvisor.com/books/the-trusted-advisor">The Trusted Advisor</a> is a book focused on trust and relationships in professional services but feels applicable to any work partnership.</p>
<p>I&rsquo;ve collected a few choice quotes below.</p>
<h2 id="show-dont-tell">Show, don&rsquo;t tell</h2>
<blockquote>
<p>To make anyone believe something about you, you must demonstrate, not assert. What you claim about yourself, your colleagues, or your firm will always be received skeptically, if it is listened to at all. In Emerson&rsquo;s words, &ldquo;Your actions speak so loudly, I cannot hear what you are saying,&rdquo;</p></blockquote>
<h2 id="listen-first">Listen first</h2>
<blockquote>
<p>We must listen effectively, and be perceived to be listening effectively, before we can proceed with any advisory process. Cutting to the chase without having earned the right to do so will usually be interpreted as arrogance.</p></blockquote>
<h2 id="interruptions-and-reordering">Interruptions and reordering</h2>
<blockquote>
<p>…if the listener breaks up our sense of story (insists on interrupting, or rearranging, or imposing his or her own sense of story line), the meaning we intend is disrupted. It feels inappropriate when someone jumps to a conclusion, or misses a connection, or gets things out of sequence. All these are forms of not &ldquo;getting it.&rdquo; Good listening respects the speaker by respecting the sequence of the story he or she chooses to tell us.</p></blockquote>
<h2 id="listen-for-whats-different">Listen for what&rsquo;s different</h2>
<blockquote>
<p>At the core of earning someone&rsquo;s trust is convincing them that you are dealing with them as a human being, and not as a member of a group or class or subset. Accordingly, as you listen to a client talk, the question on your mind should be, &ldquo;What makes this person different from any other client I&rsquo;ve served? What does that mean for what I should say and how I should behave?&rdquo;</p>
<p>Unfortunately, this is hard work. The natural tendency for most of us is to do the exact opposite: We listen for the situations we recognize, so that we can draw upon past experience to use the words, approaches, and tools that we already know well. It&rsquo;s the way most of us work, but it doesn&rsquo;t always serve us well.</p></blockquote>
<h2 id="sincere-interest-in-others">Sincere interest in others</h2>
<blockquote>
<p>So much of our time is spent focusing on ourselves, and so much of other people&rsquo;s time is spent focusing on themselves, that it is a rare and surprising event whenever someone breaks the veil. Sincere interest in another person comes across strikingly simply because it is unusual.</p></blockquote>
<h2 id="be-sure-advice-is-being-sought">Be sure advice is being sought</h2>
<blockquote>
<p>One of the biggest mistakes that advisors make is to think that their client always wants their advice. This is dangerously wrong.</p>
<p>&hellip;</p>
<p>What the advice receiver wanted was a combination of a sympathetic ear, emotional support, an understanding of the difficulties faced, and the opportunity to collect his or her own thoughts by talking them through in a non-threatening environment.</p></blockquote>
<h2 id="long-term-vs-short-term">Long-term vs short-term</h2>
<blockquote>
<p>It&rsquo;s near impossible for any professional to hide his or her true motives, whatever they may be. And if those motives are rooted in naked self-interest, they will be duly noted and reciprocated. We are not loyal to self interested people we don&rsquo;t trust them. Which means we are always likely to leave them for a better price-or for someone we actually trust.</p>
<p>Which in turn means longterm success is compromised by such behaviour. And since the long term is nothing but a series of short terms, short-term results themselves are being harmed, not improved, by slavish adherence to short-term goals.</p>
<p>The truth is, both long-term and short-term results are maximised by long-term behaviour on our part. The old Goldman Sachs mantra expressed this well: &ldquo;We are longterm selfish.&rdquo; It is in the long-term that our goals and our clients&rsquo; goals merge and that merging reveals itself over a series of short terms.</p></blockquote>
<h2 id="steps-to-develop-trust">Steps to develop trust</h2>
<blockquote>
<p>We suggest that there are five distinct steps in the development of a trusted relationship. In this chapter we will define each of these In the succeeding chapters, we will explore each stage in detail.</p>
<p>Expressed in their simplest form, the five stages are:</p>
<ul>
<li>Engage. “Let&rsquo;s talk about&hellip;”</li>
<li>Listen. “Tell me more&hellip;”</li>
<li>Frame. “So the issue is…”</li>
<li>Envision. “Let’s imagine…”</li>
<li>Commit. “I suggest we…”</li>
</ul></blockquote>

  <p>
    
    <a href="https://www.grizzlebit.com/posts/2023/08-19-the-trusted-advisor/">🔗</a>
     ∙ Tagged in <a href="https://www.grizzlebit.com/tags/books/">Books</a>, <a href="https://www.grizzlebit.com/tags/teamwork/">Teamwork</a>.</p>
</div>
]]></content>
    <link rel="alternate" href="https://www.grizzlebit.com/posts/2023/08-19-the-trusted-advisor/"></link>
    <link rel="related" href="https://www.grizzlebit.com/posts/2023/08-19-the-trusted-advisor/"></link>
    
  </entry>
  
  <entry>
    <id>https://www.grizzlebit.com/posts/2023/07-26-postels-law-for-people/</id>
    <published>2023-07-26T18:58:14+08:00</published>
    <updated>2023-07-26T19:38:04+08:00</updated>
    <author><name>Ray Grasso</name></author>
    
    <title>Postel&#39;s Law for People</title>
    <content type="html" xml:base="https://www.grizzlebit.com/posts/" xml:lang="en"><![CDATA[<div>
  <p>I was having an after-work chat with <a href="https://www.harukizaemon.com/">Simon</a> a while ago. We were discussing how we can cultivate a more resilient culture at work, specifically enhancing the capacity of individuals to constructively handle feedback.</p>
<p>He mentioned that he&rsquo;d been reading <a href="https://www.goodreads.com/book/show/18114120-thanks-for-the-feedback">Thanks for the Feedback</a> which emphasises that, contrary to popular advice, it&rsquo;s better to focus on helping people get better at <em>receiving</em> feedback rather than giving it.</p>
<p>This reminded me of a design principle in software engineering called the <a href="https://en.wikipedia.org/wiki/Robustness_principle">&ldquo;Robustness principle&rdquo; or &ldquo;Postel&rsquo;s law&rdquo;</a>. This principle guides how software systems should be designed to communicate with each other.</p>
<p>It&rsquo;s often summarised as: &ldquo;Be conservative in what you send, be liberal in what you accept&rdquo;.</p>
<p>It felt like when it came to feedback and people working better together we were talking about the same thing, i.e. Postel&rsquo;s law for people.</p>
<p>This makes me wonder what other software design principles might be useful when applied to people.</p>

  <p>
    
    <a href="https://www.grizzlebit.com/posts/2023/07-26-postels-law-for-people/">🔗</a>
     ∙ Tagged in <a href="https://www.grizzlebit.com/tags/communication/">Communication</a>, <a href="https://www.grizzlebit.com/tags/principles/">Principles</a>, <a href="https://www.grizzlebit.com/tags/teamwork/">Teamwork</a>.</p>
</div>
]]></content>
    <link rel="alternate" href="https://www.grizzlebit.com/posts/2023/07-26-postels-law-for-people/"></link>
    <link rel="related" href="https://www.grizzlebit.com/posts/2023/07-26-postels-law-for-people/"></link>
    
  </entry>
  
  <entry>
    <id>https://www.grizzlebit.com/links/2023/05-20-alignment-gets-expensive-dont-skimp-on-it/</id>
    <published>2023-05-20T13:25:27+08:00</published>
    <updated>2023-05-21T12:04:51+08:00</updated>
    <author><name>Ray Grasso</name></author>
    
    <title>Alignment Gets Expensive - Don&#39;t Skimp on It ↬</title>
    <content type="html" xml:base="https://www.grizzlebit.com/links/" xml:lang="en"><![CDATA[<div>
  <p>Jessica Kerr:</p>
<blockquote>
<p>There’s collaboration overhead to get interrelated pieces working together. Design, product, and engineering don’t “coordinate,” they collaborate. They work together every day, on a single output.</p></blockquote>
<p>…</p>
<blockquote>
<p>Then there’s alignment overhead. Alignment means we all know why we’re doing this work. This shared understanding lets us make the thousand detailed decisions of the day in ways that support the real purpose of our shared effort.</p></blockquote>

  <p>
    
    <a href="https://www.grizzlebit.com/links/2023/05-20-alignment-gets-expensive-dont-skimp-on-it/">↬</a>
     ∙ Tagged in <a href="https://www.grizzlebit.com/tags/teamwork/">Teamwork</a>.</p>
</div>
]]></content>
    <link rel="alternate" href="https://jessitron.com/2023/05/17/alignment-gets-expensive-dont-skimp-on-it/"></link>
    <link rel="related" href="https://www.grizzlebit.com/links/2023/05-20-alignment-gets-expensive-dont-skimp-on-it/"></link>
    
  </entry>
  
  <entry>
    <id>https://www.grizzlebit.com/posts/2023/04-22-creating-clarity-in-complex-conversations/</id>
    <published>2023-04-22T16:04:54+08:00</published>
    <updated>2023-04-24T11:13:26+08:00</updated>
    <author><name>Ray Grasso</name></author>
    
    <title>Creating Clarity in Complex Conversations</title>
    <content type="html" xml:base="https://www.grizzlebit.com/posts/" xml:lang="en"><![CDATA[<div>
  <p>Product development is a team sport mostly carried out through meetings and conversations.</p>
<p>Two practical things you can try to help create clarity and reduce chaos in particularly complex conversations:</p>
<ol>
<li>Consolidate progress with a series of summaries.</li>
<li>Crystallise outcomes in writing.</li>
</ol>
<p>These might seem obvious, but they don&rsquo;t happen as often as I&rsquo;d hoped.</p>
<h2 id="consolidate-progress-with-a-series-of-summaries">Consolidate progress with a series of summaries</h2>
<p>Do you find yourself in meetings with multiple people discussing complex topics?</p>
<p>Does a series of tangents and related issues emerge as the conversation progresses?</p>
<p>In the end, are you unsure of where things are at?</p>
<p>Are you confident that you understand the situation but are uncertain if it&rsquo;s the same for others?</p>
<p>Taking complex, meandering conversations and providing clear, structured summaries throughout is incredibly valuable <sup id="fnref:1"><a href="#fn:1" class="footnote-ref" role="doc-noteref">1</a></sup>.</p>
<p>I think of each summary as incrementally locking in consensus or taking a collective step up the ladder of inference, as described in <a href="https://www.amazon.com.au/Crucial-Conversations-Talking-Stakes-Second-ebook/dp/B005K0AYH4/">Crucial Conversations</a>.</p>
<p>Sometimes the state of play seems obvious, and therefore it feels unnecessary to summarise. I suggest pushing through this feeling and doing it anyway to ensure alignment and avoid <a href="https://en.wikipedia.org/wiki/Pluralistic_ignorance">pluralistic ignorance</a>.</p>
<h2 id="crystallise-outcomes-in-writing">Crystallise outcomes in writing</h2>
<p>As soon as you leave the conversation, you are immediately misaligned again <sup id="fnref:2"><a href="#fn:2" class="footnote-ref" role="doc-noteref">2</a></sup>.</p>
<p>You can reduce this misalignment by sharing a written conversation summary including decisions and actions.</p>
<p>Given the volume of conversations leaders tend to be in, capturing the outcomes becomes essential for rebooting context later or remembering which decisions were made and why.</p>
<div class="footnotes" role="doc-endnotes">
<hr>
<ol>
<li id="fn:1">
<p>This can be as simple as listing the facts established to date, assumptions, trade-offs available, or agreed actions.&#160;<a href="#fnref:1" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:2">
<p>It&rsquo;s ok. This is normal. Read more on <a href="https://buildrightside.com/autonomy-alignment">autonomy and alignment from Jean-Michel Lemieux</a>.&#160;<a href="#fnref:2" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
</ol>
</div>

  <p>
    
    <a href="https://www.grizzlebit.com/posts/2023/04-22-creating-clarity-in-complex-conversations/">🔗</a>
     ∙ Tagged in <a href="https://www.grizzlebit.com/tags/communication/">Communication</a>, <a href="https://www.grizzlebit.com/tags/leadership/">Leadership</a>, <a href="https://www.grizzlebit.com/tags/teamwork/">Teamwork</a>.</p>
</div>
]]></content>
    <link rel="alternate" href="https://www.grizzlebit.com/posts/2023/04-22-creating-clarity-in-complex-conversations/"></link>
    <link rel="related" href="https://www.grizzlebit.com/posts/2023/04-22-creating-clarity-in-complex-conversations/"></link>
    
  </entry>
  
  <entry>
    <id>https://www.grizzlebit.com/posts/2023/04-18-come-back-to-me-when-youve-got-a-trade-off-to-discuss/</id>
    <published>2023-04-18T21:37:39+08:00</published>
    <updated>2023-04-18T21:39:47+08:00</updated>
    <author><name>Ray Grasso</name></author>
    
    <title>Come Back to Me When You&#39;ve Got a Trade-Off to Discuss</title>
    <content type="html" xml:base="https://www.grizzlebit.com/posts/" xml:lang="en"><![CDATA[<div>
  <p>It&rsquo;s not particularly useful debating the value of anything in isolation.</p>
<p>Considering programming languages, tools, processes, or product decisions on their own is a mostly philosophical exercise.</p>
<p>Things start to have meaning when we assess them against other available options.</p>
<p>That&rsquo;s where the rubber hits the road, and things get spicy, friends.</p>

  <p>
    
    <a href="https://www.grizzlebit.com/posts/2023/04-18-come-back-to-me-when-youve-got-a-trade-off-to-discuss/">🔗</a>
     ∙ Tagged in <a href="https://www.grizzlebit.com/tags/decision-making/">Decision Making</a>, <a href="https://www.grizzlebit.com/tags/teamwork/">Teamwork</a>.</p>
</div>
]]></content>
    <link rel="alternate" href="https://www.grizzlebit.com/posts/2023/04-18-come-back-to-me-when-youve-got-a-trade-off-to-discuss/"></link>
    <link rel="related" href="https://www.grizzlebit.com/posts/2023/04-18-come-back-to-me-when-youve-got-a-trade-off-to-discuss/"></link>
    
  </entry>
  
  <entry>
    <id>https://www.grizzlebit.com/links/2023/04-16-hermes-document-management-system/</id>
    <published>2023-04-16T10:32:58+08:00</published>
    <updated>2024-11-04T09:50:52+10:00</updated>
    <author><name>Ray Grasso</name></author>
    
    <title>Hermes Document Management System ↬</title>
    <content type="html" xml:base="https://www.grizzlebit.com/links/" xml:lang="en"><![CDATA[<div>
  <p>A tool from Hashicorp for adding document review and collaboration workflows over Google Docs.</p>

  <p>
    
    <a href="https://www.grizzlebit.com/links/2023/04-16-hermes-document-management-system/">↬</a>
     ∙ Tagged in <a href="https://www.grizzlebit.com/tags/teamwork/">Teamwork</a>, <a href="https://www.grizzlebit.com/tags/tools/">Tools</a>.</p>
</div>
]]></content>
    <link rel="alternate" href="https://www.hashicorp.com/blog/introducing-hermes-an-open-source-document-management-system"></link>
    <link rel="related" href="https://www.grizzlebit.com/links/2023/04-16-hermes-document-management-system/"></link>
    
  </entry>
  
  <entry>
    <id>https://www.grizzlebit.com/links/2023/04-16-4-tools-to-keep-meetings-on-track/</id>
    <published>2023-04-16T10:30:35+08:00</published>
    <updated>2024-11-04T09:50:52+10:00</updated>
    <author><name>Ray Grasso</name></author>
    
    <title>4 Tools to Keep Meetings on Track ↬</title>
    <content type="html" xml:base="https://www.grizzlebit.com/links/" xml:lang="en"><![CDATA[<div>
  <p>Dan Rockwell:</p>
<blockquote>
<p>Smart people have lousy meetings. Keeping meetings on track is like organizing a barrel of hummingbirds.</p></blockquote>
<p>I especially like the &ldquo;fill in the blank statements&rdquo; strategy.</p>

  <p>
    
    <a href="https://www.grizzlebit.com/links/2023/04-16-4-tools-to-keep-meetings-on-track/">↬</a>
     ∙ Tagged in <a href="https://www.grizzlebit.com/tags/communication/">Communication</a>, <a href="https://www.grizzlebit.com/tags/teamwork/">Teamwork</a>.</p>
</div>
]]></content>
    <link rel="alternate" href="https://leadershipfreak.blog/2023/03/01/4-tools-to-keep-meetings-on-track/"></link>
    <link rel="related" href="https://www.grizzlebit.com/links/2023/04-16-4-tools-to-keep-meetings-on-track/"></link>
    
  </entry>
  
  <entry>
    <id>https://www.grizzlebit.com/links/2022/10-23-three-types-of-meetings/</id>
    <published>2022-10-23T14:11:16+08:00</published>
    <updated>2023-04-13T20:33:32+08:00</updated>
    <author><name>Ray Grasso</name></author>
    
    <title>Three Types of Meetings ↬</title>
    <content type="html" xml:base="https://www.grizzlebit.com/links/" xml:lang="en"><![CDATA[<div>
  <p>Cam Daigle:</p>
<blockquote>
<p>I&rsquo;m hoping this system helps you have <em>better</em> meetings – that the people running the meeting feel like it&rsquo;s worth their time to run them, and that the people in attendance feel like their presence there <em>matters</em>.</p></blockquote>

  <p>
    
    <a href="https://www.grizzlebit.com/links/2022/10-23-three-types-of-meetings/">↬</a>
     ∙ Tagged in <a href="https://www.grizzlebit.com/tags/processes/">Processes</a>, <a href="https://www.grizzlebit.com/tags/teamwork/">Teamwork</a>.</p>
</div>
]]></content>
    <link rel="alternate" href="https://camdaigle.com/posts/three-types-of-meetings/"></link>
    <link rel="related" href="https://www.grizzlebit.com/links/2022/10-23-three-types-of-meetings/"></link>
    
  </entry>
  
  <entry>
    <id>https://www.grizzlebit.com/links/2022/08-29-prioritization-is-a-political-problem-as-much-as-an-analytical-problem/</id>
    <published>2022-08-29T19:52:48+08:00</published>
    <updated>2024-11-04T09:50:52+10:00</updated>
    <author><name>Ray Grasso</name></author>
    
    <title>Prioritization Is a Political Problem as Much as an Analytical Problem ↬</title>
    <content type="html" xml:base="https://www.grizzlebit.com/links/" xml:lang="en"><![CDATA[<div>
  <p>Richard Mironov:</p>
<blockquote>
<p>Prioritization is more than an analytical/intellectual exercise. It&rsquo;s an organizational challenge with natural disagreements among stakeholders. Product leaders need to think about motivating the right kinds of participation and addressing the emotional issues that arise. Spreadsheets and models are necessary, but not sufficient.</p></blockquote>

  <p>
    
    <a href="https://www.grizzlebit.com/links/2022/08-29-prioritization-is-a-political-problem-as-much-as-an-analytical-problem/">↬</a>
     ∙ Tagged in <a href="https://www.grizzlebit.com/tags/decision-making/">Decision Making</a>, <a href="https://www.grizzlebit.com/tags/teamwork/">Teamwork</a>.</p>
</div>
]]></content>
    <link rel="alternate" href="https://www.mironov.com/pri-politics/"></link>
    <link rel="related" href="https://www.grizzlebit.com/links/2022/08-29-prioritization-is-a-political-problem-as-much-as-an-analytical-problem/"></link>
    
  </entry>
  
  <entry>
    <id>https://www.grizzlebit.com/links/2022/07-16-defensiveness-blocks-teamwork/</id>
    <published>2022-07-16T10:24:41+08:00</published>
    <updated>2023-04-13T20:33:32+08:00</updated>
    <author><name>Ray Grasso</name></author>
    
    <title>Defensiveness Blocks Teamwork ↬</title>
    <content type="html" xml:base="https://www.grizzlebit.com/links/" xml:lang="en"><![CDATA[<div>
  <p>Kara Cutruzzula:</p>
<blockquote>
<p>Why is defensiveness such an obstacle to collaboration? When we get defensive, “we put way more into self-preservation than we do into problem-solving,” Tamm says. “We’re trying to prove that we’re right rather than search for creative solutions.” When this happens in a workplace, it can be a recipe for chaos and failure.</p></blockquote>
<p>…</p>
<blockquote>
<p>OK, now that we understand the dangers of defensiveness, here’s what we can do about it. You can start by learning to spot the warning signs of defensiveness in yourself. When you feel yourself experiencing them, pay attention and take action. According to Tamm, here are the 10 most common warning signs that you may be getting defensive: A spurt of energy in your body; sudden confusion; flooding your audience with information to prove a point; withdrawing into silence; magnifying or minimizing everything; developing “all or nothing” thinking; feeling like you’re a victim or you’re misunderstood; blaming or shaming others; obsessive thinking; and wanting the last word.</p></blockquote>

  <p>
    
    <a href="https://www.grizzlebit.com/links/2022/07-16-defensiveness-blocks-teamwork/">↬</a>
     ∙ Tagged in <a href="https://www.grizzlebit.com/tags/teamwork/">Teamwork</a>.</p>
</div>
]]></content>
    <link rel="alternate" href="https://ideas.ted.com/the-1-block-to-teamwork-is-defensiveness-heres-how-to-defuse-it/"></link>
    <link rel="related" href="https://www.grizzlebit.com/links/2022/07-16-defensiveness-blocks-teamwork/"></link>
    
  </entry>
  
  <entry>
    <id>https://www.grizzlebit.com/links/2022/07-02-were-in-this-together/</id>
    <published>2022-07-02T15:22:25+08:00</published>
    <updated>2023-04-13T20:33:32+08:00</updated>
    <author><name>Ray Grasso</name></author>
    
    <title>We&#39;re in This Together ↬</title>
    <content type="html" xml:base="https://www.grizzlebit.com/links/" xml:lang="en"><![CDATA[<div>
  <p>Jason Yip:</p>
<blockquote>
<ul>
<li>Authority-focus: “Not my job, not my problem.”</li>
<li>Responsibility-focus: “What is the right thing to do? How can I help?”</li>
</ul>
<p>Responsibility-focus reflects the belief that “we’re in it together”.</p></blockquote>

  <p>
    
    <a href="https://www.grizzlebit.com/links/2022/07-02-were-in-this-together/">↬</a>
     ∙ Tagged in <a href="https://www.grizzlebit.com/tags/teamwork/">Teamwork</a>.</p>
</div>
]]></content>
    <link rel="alternate" href="https://jchyip.medium.com/core-belief-were-in-it-together-9c2203e83ca"></link>
    <link rel="related" href="https://www.grizzlebit.com/links/2022/07-02-were-in-this-together/"></link>
    
  </entry>
  
</feed>
