<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel><title>culture | Hugo Ferreira</title>
    <link>https://hugo.ferreira.cc/tags/culture/</link>
    <description>Recent content in Culture by Hugo Ferreira</description>
    <image>
      <title>culture | Hugo Ferreira</title>
      <url>https://hugo.ferreira.cc/hf-bw.jpg</url>
      <link>https://hugo.ferreira.cc/tags/culture/</link>
    </image>
    <generator>Hugo -- 0.124.1</generator>
    <language>en</language>
    <copyright>2000–2024 by Hugo Ferreira · CC BY 4.0</copyright>
    <lastBuildDate>Wed, 18 Dec 2024 01:30:27 +0000</lastBuildDate>
    <atom:link href="https://hugo.ferreira.cc/tags/culture/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>🔗 Warm Handoffs :: Luckymike&#39;s Tech Notes</title>
      <link>https://hugo.ferreira.cc/warm-handoffs/</link>
      <pubDate>Wed, 18 Dec 2024 01:30:27 +0000</pubDate>
      <guid>https://hugo.ferreira.cc/warm-handoffs/</guid>
      <description>Warm Handoffs :: Luckymike&amp;rsquo;s Tech Notes
… generally the guidelines are:
If someone asks a question in the wrong channel, and you know the right channel, link their question in the right channel, tagging them, and explain why you’re making the handoff, along with any additional context you have.
If someone asks a question in the wrong channel, and you’re not sure where it should go, link their question in a shared channel asking who can help, along with any additional context you have.</description>
      <content:encoded><![CDATA[<p><a href="https://luckymike.dev/posts/warm-handoffs/">Warm Handoffs :: Luckymike&rsquo;s Tech Notes</a></p>
<blockquote>
<p>… generally the guidelines are:</p>
<ul>
<li>
<p>If someone asks a question in the wrong channel, and you know the right channel, link their question in the right channel, tagging them, and explain why you’re making the handoff, along with any additional context you have.</p>
</li>
<li>
<p>If someone asks a question in the wrong channel, and you’re not sure where it should go, link their question in a shared channel asking who can help, along with any additional context you have.</p>
</li>
</ul>
<p>That’s it!</p>
</blockquote>
<hr>
<blockquote>
<p>You can’t just <em>recommend</em> them, you have to <em>encourage</em> and <em>reinforce</em> them. They are premised on two values:</p>
<ol>
<li>most people want to help their peers, and</li>
<li>most people want to get their own work done.</li>
</ol>
<p>When inter-team support requests create a conflict between these two values, folks tend to resort to the quickest solution that meets both needs, the Cold Redirect. To break this tendency, you need to establish that a Warm Handoff is expected in lieu of a Cold Redirect, not just preferred.</p>
</blockquote>
<hr>
<p>See also, from <a href="https://luckymike.dev/posts/warm-handoffs-redux/">Warm Handoffs Redux</a>:</p>
<ul>
<li><a href="https://lethain.com/no-wrong-doors/">No Wrong Doors. | Irrational Exuberance</a></li>
<li><a href="/postels-law">Postel’s Law</a> “as sort of an overarching philosophy supporting Warm Handoffs and No Wrong Doors.”</li>
</ul>
]]></content:encoded>
    </item>
    <item>
      <title>🔗 Why Building a Culture from the Top Down Fails</title>
      <link>https://hugo.ferreira.cc/top-down-culture/</link>
      <pubDate>Tue, 19 Mar 2024 11:08:34 +0000</pubDate>
      <guid>https://hugo.ferreira.cc/top-down-culture/</guid>
      <description>Why Building a Culture from the Top Down Fails
Lack of Employee Buy-In Disconnect from Reality Limited Innovation Reduced Employee Engagement Resistance to Change Lack of Adaptability Erosion of Trust Inequality and Hierarchical Structures One-Size-Fits-All Approach Cultural Mismatch High Turnover A culture that emerges organically from the collective values, beliefs, and behaviors of the workforce is more likely to be embraced, enduring, and aligned with the organization&amp;rsquo;s objectives.</description>
      <content:encoded><![CDATA[<p><a href="https://www.linkedin.com/pulse/why-building-culture-from-top-down-fails-quintin-eason/">Why Building a Culture from the Top Down Fails</a></p>
<blockquote>
<ol>
<li>Lack of Employee Buy-In</li>
<li>Disconnect from Reality</li>
<li>Limited Innovation</li>
<li>Reduced Employee Engagement</li>
<li>Resistance to Change</li>
<li>Lack of Adaptability</li>
<li>Erosion of Trust</li>
<li>Inequality and Hierarchical Structures</li>
<li>One-Size-Fits-All Approach</li>
<li>Cultural Mismatch</li>
<li>High Turnover</li>
</ol>
</blockquote>
<hr>
<blockquote>
<p>A culture that emerges organically from the collective values, beliefs, and behaviors of the workforce is more likely to be embraced, enduring, and aligned with the organization&rsquo;s objectives.</p>
</blockquote>
]]></content:encoded>
    </item>
    <item>
      <title>🔗 Management 3.0 practices</title>
      <link>https://hugo.ferreira.cc/management-30/</link>
      <pubDate>Thu, 24 Aug 2023 07:07:28 +0000</pubDate>
      <guid>https://hugo.ferreira.cc/management-30/</guid>
      <description>Management 3.0 Practices Finder | finders
Management 3.0 moves beyond theory by providing an actionable set of tools and practices that grow leadership skills, encourage innovation, and increase happiness, to name just a few of the potential benefits.
The M30 Finder groups the practices into seven categories:
Tools for Engagement Tools for Effective Feedback Tools for Managing the System Tools to Support Innovation and Change Tools for Exploring Organizational Culture Tools for Team Exploration Tools for Measurement See also Liberating structures.</description>
      <content:encoded><![CDATA[<p><a href="https://gphiliprogers.github.io/finders/m30finder">Management 3.0 Practices Finder | finders</a></p>
<blockquote>
<p><a href="https://management30.com/learn/">Management 3.0</a> moves beyond theory by providing an actionable set of tools and practices that grow leadership skills, encourage innovation, and increase happiness, to name just a few of the potential benefits.</p>
</blockquote>
<blockquote>
<p>The M30 Finder groups the practices into seven categories:</p>
<ul>
<li>Tools for Engagement</li>
<li>Tools for Effective Feedback</li>
<li>Tools for Managing the System</li>
<li>Tools to Support Innovation and Change</li>
<li>Tools for Exploring Organizational Culture</li>
<li>Tools for Team Exploration</li>
<li>Tools for Measurement</li>
</ul>
</blockquote>
<hr>
<p>See also <a href="/liberating-structures">Liberating structures</a>.</p>
]]></content:encoded>
    </item>
    <item>
      <title>📜 Try to learn something about everything and everything about</title>
      <link>https://hugo.ferreira.cc/try-to-learn-something-about-everything-and/</link>
      <pubDate>Sun, 22 Feb 2015 07:07:28 +0000</pubDate>
      <guid>https://hugo.ferreira.cc/try-to-learn-something-about-everything-and/</guid>
      <description>Try to learn something about everything and everything about something.
Thomas Henry Huxley (via Donald Knuth )</description>
      <content:encoded><![CDATA[<blockquote>
<p>Try to learn something about everything and everything about
something.</p>
</blockquote>
<p><a href="http://en.wikiquote.org/wiki/Thomas_Henry_Huxley">Thomas Henry Huxley</a>
(via <a href="http://youtu.be/75Ju0eM5T2c?t=3m41s">Donald Knuth</a> )</p>
]]></content:encoded>
    </item>
    <item>
      <title>📺 Third Wave Objective-C</title>
      <link>https://hugo.ferreira.cc/open-source-building-on-the-shoulders-of-giants/</link>
      <pubDate>Mon, 06 Jan 2014 07:07:28 +0000</pubDate>
      <guid>https://hugo.ferreira.cc/open-source-building-on-the-shoulders-of-giants/</guid>
      <description>Open Source: Building on the Shoulders of Giants
CocoaPods.org &amp;ndash; The Dependency Manager for Objective C Alcatraz : Xcode Package Manager Tooling: Teaching a Computer to Fish
nomad :: world-class command line utilities for iOS development xctool &amp;mdash; replacement for Apple&amp;rsquo;s xcodebuild (via Third Wave Objective-C // Speaker Deck )
( Source: http://cocoapods.org/ )</description>
      <content:encoded><![CDATA[<blockquote>
<p>Open Source: Building on the Shoulders of Giants</p>
<ul>
<li><a href="http://cocoapods.org">CocoaPods.org &ndash; The Dependency Manager for Objective
C</a></li>
<li><a href="http://mneorr.github.io/Alcatraz/">Alcatraz : Xcode Package
Manager</a></li>
</ul>
<p>Tooling: Teaching a Computer to Fish</p>
<ul>
<li><a href="http://nomad-cli.com">nomad :: world-class command line utilities for iOS
development</a></li>
<li><a href="https://github.com/facebook/xctool">xctool</a> &mdash; replacement for
Apple&rsquo;s xcodebuild</li>
</ul>
</blockquote>
<p>(via <a href="https://speakerdeck.com/mattt/third-wave-objective-c">Third Wave Objective-C // Speaker Deck</a> )</p>
<p>( Source: <a href="http://cocoapods.org/">http://cocoapods.org/</a> )</p>
]]></content:encoded>
    </item>
    <item>
      <title>🔗 Watch --- Everything is a Remix</title>
      <link>https://hugo.ferreira.cc/watch-everything-is-a-remix/</link>
      <pubDate>Fri, 17 May 2013 07:07:28 +0000</pubDate>
      <guid>https://hugo.ferreira.cc/watch-everything-is-a-remix/</guid>
      <description>Watch &amp;mdash; Everything is a Remix
Everything is a Remix is produced by me, Kirby Ferguson, a New York-based filmmaker. This site is a companion piece to the four-part video series.
See also Kirby Ferguson: Embrace the remix | Video on TED.com</description>
      <content:encoded><![CDATA[<p><a href="http://everythingisaremix.info/watch-the-series/">Watch &mdash; Everything is a
Remix</a></p>
<blockquote>
<p>Everything is a Remix is produced by me, Kirby Ferguson, a New
York-based filmmaker. This site is a companion piece to the four-part
video series.</p>
</blockquote>
<p>See also <a href="http://www.ted.com/talks/kirby_ferguson_embrace_the_remix.html">Kirby Ferguson: Embrace the remix  |  Video on
TED.com</a></p>
]]></content:encoded>
    </item>
  </channel>
</rss>
