<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Microeconomics | Keegan&#39;s Time Series</title>
    <link>https://keeganstimeseries.com/tag/microeconomics/</link>
      <atom:link href="https://keeganstimeseries.com/tag/microeconomics/index.xml" rel="self" type="application/rss+xml" />
    <description>Microeconomics</description>
    <generator>Hugo Blox Builder (https://hugoblox.com)</generator><language>en-us</language><lastBuildDate>Mon, 02 Nov 2026 00:00:00 +0000</lastBuildDate>
    <image>
      <url>https://keeganstimeseries.com/media/icon_hucb5343885e062dfd39f0924c6a9ba323_52880_512x512_fill_lanczos_center_3.png</url>
      <title>Microeconomics</title>
      <link>https://keeganstimeseries.com/tag/microeconomics/</link>
    </image>
    
    <item>
      <title>Enterprise Workforce Laboratory</title>
      <link>https://keeganstimeseries.com/project/enterprise-workforce/</link>
      <pubDate>Mon, 02 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://keeganstimeseries.com/project/enterprise-workforce/</guid>
      <description>&lt;h2 id=&#34;a-deliberately-separate-firm-level-model&#34;&gt;A deliberately separate firm-level model&lt;/h2&gt;
&lt;p&gt;Economy-wide labor statistics describe the aggregate outcome of decisions, while enterprise systems record the administrative details of employment relationships. This project uses &lt;strong&gt;synthetic enterprise records&lt;/strong&gt;, not confidential employer data, to demonstrate how those details can be modeled.&lt;/p&gt;
&lt;h2 id=&#34;enterprise-semantic-model&#34;&gt;Enterprise semantic model&lt;/h2&gt;
&lt;figure class=&#34;owas-portfolio-figure&#34; style=&#34;margin: 1.75rem auto 2rem; max-width: 1020px;&#34;&gt;
  &lt;a href=&#34;https://keeganstimeseries.com/images/owas/enterprise-semantic-model.webp&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;
    &lt;img src=&#34;https://keeganstimeseries.com/images/owas/enterprise-semantic-model.webp&#34; alt=&#34;Power BI model diagram with person, job, organization, and date dimensions alongside assignment history, month-end headcount, employment spells, compensation events, leave episodes, and recruiting applications.&#34; loading=&#34;lazy&#34; decoding=&#34;async&#34; style=&#34;display:block;width:100%;height:auto;border:1px solid #ddd;border-radius:8px;box-shadow:0 8px 25px rgba(0,0,0,.10);&#34; /&gt;
  &lt;/a&gt;
  &lt;figcaption style=&#34;font-size:.9rem;line-height:1.55;margin-top:.6rem;color:#586174;&#34;&gt;Synthetic enterprise Power BI model (development snapshot). Dimensions and event/snapshot facts remain separate to preserve their distinct grains. Some date relationships are inactive and must be addressed deliberately in measures.&lt;/figcaption&gt;
&lt;/figure&gt;
&lt;p&gt;The model distinguishes &lt;strong&gt;people, employment spells, assignments, time-bound snapshots, compensation events, leave episodes, and applications&lt;/strong&gt;. These entities represent different analytical units and should not be merged into a single generic employee table.&lt;/p&gt;
&lt;p&gt;The diagram includes:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Dimensions for person, job, organization, and date.&lt;/li&gt;
&lt;li&gt;Employment spell, assignment history, and workforce month-end facts.&lt;/li&gt;
&lt;li&gt;Compensation events, leave episodes, and recruiting applications.&lt;/li&gt;
&lt;li&gt;DAX measures for headcount, hires, separations, and workforce reconciliation.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;analytical-questions&#34;&gt;Analytical questions&lt;/h2&gt;
&lt;p&gt;How sensitive is turnover to the selected separation events and denominator? How do month-end counts differ from exposure-based measures? What changes when a model uses employment spells and time-varying covariates rather than a one-row-per-person extract?&lt;/p&gt;
&lt;h2 id=&#34;modeling-roadmap&#34;&gt;Modeling roadmap&lt;/h2&gt;
&lt;p&gt;The synthetic dataset is intended to support reproducible data-quality tests, descriptive dashboards, survival modeling, and predictive diagnostics. Any reported model performance will require actual fitted results and documented validation.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Status:&lt;/strong&gt; Architecture under development. The diagram demonstrates structure; it does not claim deployed forecasting or prediction performance.&lt;/p&gt;
</description>
    </item>
    
  </channel>
</rss>
