<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Leadership on John Arroyo</title>
    <link>https://www.johnarroyo.com/tags/leadership/</link>
    <description>Recent content in Leadership on John Arroyo</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 14 Sep 2025 22:52:00 -0500</lastBuildDate>
    <atom:link href="https://www.johnarroyo.com/tags/leadership/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Why Stay Hands-On as a Tech Leader in 2025?</title>
      <link>https://www.johnarroyo.com/2025/07/why-stay-hands-on-as-a-tech-leader-in-2025/</link>
      <pubDate>Mon, 07 Jul 2025 09:00:59 +0000</pubDate>
      <guid>https://www.johnarroyo.com/2025/07/why-stay-hands-on-as-a-tech-leader-in-2025/</guid>
      <description>&lt;p&gt;The traditional image of a tech leader often involves someone who&amp;rsquo;s &amp;ldquo;graduated&amp;rdquo; from coding—someone who&amp;rsquo;s moved beyond the keyboard to focus purely on strategy, meetings, and high-level decision making. But in 2025, this approach isn&amp;rsquo;t just outdated; it&amp;rsquo;s counterproductive.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Make Nemawashi part of your design process</title>
      <link>https://www.johnarroyo.com/2024/11/make-nemawashi-part-of-your-design/</link>
      <pubDate>Mon, 04 Nov 2024 09:00:59 +0000</pubDate>
      <guid>https://www.johnarroyo.com/2024/11/make-nemawashi-part-of-your-design/</guid>
      <description>&lt;p&gt;Getting consensus on design decisions is one of the most challenging aspects of any technical or creative project. Too often, teams find themselves caught between two extremes: the chaotic free-for-all of design by committee, or the risky isolation of the lone wolf making decisions in a vacuum. But there&amp;rsquo;s a third way—one that comes from Japanese business philosophy and can revolutionize how we approach collaborative work.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
