<?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>#TechLeadership on Home</title>
    <link>https://yakinin.com/en/tags/%23techleadership/</link>
    <description>Recent content in #TechLeadership on Home</description>
    <generator>Hugo -- 0.148.2</generator>
    <language>en</language>
    <lastBuildDate>Wed, 14 May 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://yakinin.com/en/tags/%23techleadership/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Ownership Over Orders: Why Top-Down Management Fails in Tech</title>
      <link>https://yakinin.com/en/posts/20250514-it-team-management-initiative/</link>
      <pubDate>Wed, 14 May 2025 00:00:00 +0000</pubDate>
      <guid>https://yakinin.com/en/posts/20250514-it-team-management-initiative/</guid>
      <description>&lt;p&gt;There are two core approaches to management. Both can work, but one suppresses initiative while the other cultivates it.&lt;/p&gt;
&lt;p&gt;The first is the &lt;strong&gt;&amp;ldquo;Task + Control&amp;rdquo;&lt;/strong&gt; model. A manager assigns a task, monitors its execution, and only requires the employee to do exactly what was asked. Initiative is not part of the equation.&lt;/p&gt;
&lt;p&gt;The second, more common in Western tech circles, is the &lt;strong&gt;&amp;ldquo;Area of Responsibility + Boundaries&amp;rdquo;&lt;/strong&gt; model. Here, you don’t receive a task; you receive a domain. You are given the objective, the resources, and the strategic guardrails. What happens next is your growth zone. You apply your expertise, think critically, and take initiative. Sometimes you make mistakes. But often, you deliver a better outcome than anyone could have prescribed from the top.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
