<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Hierarchy on emsenn.net</title>
    <link>https://emsenn.net/tags/hierarchy/</link>
    <description>Recent content in Hierarchy on emsenn.net</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 07 Mar 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://emsenn.net/tags/hierarchy/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Principal-Agent Problem</title>
      <link>https://emsenn.net/library/domains/humanities/domains/sociology/domains/critical-theory/domains/marxism/domains/political-economy/terms/principal-agent-problem/</link>
      <pubDate>Sat, 07 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://emsenn.net/library/domains/humanities/domains/sociology/domains/critical-theory/domains/marxism/domains/political-economy/terms/principal-agent-problem/</guid>
      <description>&lt;p&gt;The &lt;strong&gt;principal-agent problem&lt;/strong&gt; describes a governance structure&#xA;where one party (the principal) delegates work to another (the&#xA;agent), creating information asymmetry: the agent knows more about&#xA;their own actions than the principal can observe.&lt;/p&gt;&#xA;&lt;p&gt;In conventional project management, this structure is pervasive:&#xA;a manager (principal) defines objectives, and workers (agents)&#xA;execute them. Planning tools (Gantt charts, sprint backlogs,&#xA;standups) serve the principal&amp;rsquo;s need for visibility and control&#xA;over the agent&amp;rsquo;s behavior.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
