Shadow Work for Operators: A Framework

Every company is, in part, a costume worn by the founder's unexamined material. This is not a metaphor. It shows up in the org chart, in the hiring patterns, in which features get prioritized at 11pm.

We have a working definition of operator shadow: the set of motivations, fears, and unmet needs the founder is unwilling to name in public. The cost of this shadow is observable. It typically manifests as a 22% premium on engineering cycles, a 14% increase in regrettable hires, and one significant strategic decision per fiscal year that no one on the team can fully explain.

We propose a quarterly practice: the founder writes down, in private, the three things they are pretending not to want. They share none of it. They simply notice when those three things begin to appear in the roadmap as features.

We are not therapists. We are allocators. We are, however, allocators who have read enough Jung to recognize a costume when we see one.