{
  "version": "https://jsonfeed.org/version/1.1",
  "title": "Low diatribe – Reflections",
  "home_page_url": "https://lowdiatribe.net",
  "feed_url": "https://lowdiatribe.net/feed.json",
  "description": "Unpolished thoughts on leadership and growth. Quiet authority, iterative craft, and earned trust.",
  "items": [
    {
      "id": "https://lowdiatribe.net/reflection/2026-03-27-voltron-form",
      "url": "https://lowdiatribe.net/reflection/2026-03-27-voltron-form",
      "title": "Voltron form",
      "date_published": "2026-03-27T21:00:00.000Z",
      "summary": "When I was a kid, Voltron taught me something about teams I didn't have words for yet. Not that strong parts combine — but that they have to be whole before they can. Formation isn't a destination. It's a practice you keep earning.",
      "tags": [
        "teams",
        "leadership",
        "collaboration",
        "formation",
        "trust"
      ],
      "content_html": "<p>When I was a kid, I loved Voltron.</p>\n<p>That probably isn&#39;t surprising if you grew up in the 80s. Giant robots fighting space monsters was a pretty reliable formula for grabbing a kid&#39;s attention.</p>\n<p>But the part that stuck with me wasn&#39;t the fighting.</p>\n<p>It was the moment before.</p>\n<p>Five robotic lions, each powerful on its own, flying in from different directions.</p>\n<p>They would lock together — leg, arm, torso, head — and suddenly something new existed.</p>\n<p>Not five lions anymore.</p>\n<p>Voltron.</p>\n<p>At the time it just felt cool. But looking back, I think it planted something deeper in me.</p>\n<p>It gave me one of my earliest ideas about teams.</p>\n<p>Not groups.\nNot departments.\nNot a collection of talented individuals working in the same open-concept office.</p>\n<p>Teams.</p>\n<p>The kind where each part remains fully itself, but together they become capable of something none of them could do alone.</p>\n<p>And the part I didn&#39;t fully understand then — but feel more clearly now — is that the lions mattered before they combined.</p>\n<p>Each one could fly.\nFight.\nHold its own.</p>\n<p>They weren&#39;t incomplete pieces waiting to be assembled.</p>\n<p>They were whole.</p>\n<p>That&#39;s what made the combination meaningful.</p>\n<p>Not five weak parts propping each other up.\nFive strong parts choosing to come together.</p>\n<hr>\n<p>I&#39;ve gotten this wrong more than once.</p>\n<p>There&#39;s a part of me that wants all five lions before I start.</p>\n<p>All the pieces.\nAll the clarity.\nAll the conditions lined up.</p>\n<p>Only then do we move.</p>\n<p>It feels responsible.\nPrepared.</p>\n<p>It&#39;s also a good way to never begin.</p>\n<p>I remember sitting on a team initiative for the better part of a year waiting for the right moment — the right headcount, the right alignment, the right conditions. By the time everything felt ready, the window had closed. The problem we&#39;d been preparing to solve had already been solved by someone else, messily, with half the resources, while we were still waiting to begin.</p>\n<p>Because the story didn&#39;t start with Voltron.</p>\n<p>The Gallactic Alliance didn&#39;t wait until they had all five lions to resist.</p>\n<p>They started with what they had.</p>\n<p>One ship.\nOne pilot.\nOne small act of defiance.</p>\n<p>Then another.</p>\n<p>Then another.</p>\n<p>Voltron wasn&#39;t the beginning.</p>\n<p>It was the result.</p>\n<hr>\n<p>But you don&#39;t get Voltron just by assembling talented people.</p>\n<p>Each lion has to be strong on its own.\nEach pilot has to trust the others.\nEach part has to understand its role.</p>\n<p>And the black lion — the one that formed the head — wasn&#39;t powerful because it was &quot;in charge.&quot;</p>\n<p>Its job was coordination.</p>\n<p>Not domination.\nNot control.</p>\n<p>Alignment.</p>\n<p>But even that isn&#39;t quite right.</p>\n<p>Because the head doesn&#39;t move on its own.</p>\n<p>It doesn&#39;t decide in isolation and then issue commands to the rest.</p>\n<p>When Voltron moves, it&#39;s not the head leading the body.</p>\n<p>It&#39;s the body moving as one.</p>\n<p>The red lion doesn&#39;t wait to be told it&#39;s an arm.\nThe green lion doesn&#39;t just &quot;do leg stuff.&quot;</p>\n<p>Each part is fully itself, fully capable, and somehow aware of the whole.</p>\n<p>The head isn&#39;t controlling the system.</p>\n<p>It&#39;s expressing what the system is already doing together.</p>\n<hr>\n<p>That&#39;s the part we tend to miss.</p>\n<p>We talk about leadership like it sits at the top, directing everything beneath it.</p>\n<p>My favorite teams didn&#39;t feel like that at all.</p>\n<p>They felt coordinated.</p>\n<p>Like everyone understood their role, the moment, and the motion — and could act without waiting.</p>\n<p>The &quot;head&quot; still mattered.</p>\n<p>But not as a command center.</p>\n<p>More like a point of integration.</p>\n<p>A place where the movement becomes visible.</p>\n<hr>\n<p>You see it in the quiet moments when everyone suddenly understands their role in the larger pattern.</p>\n<p>The conversation shifts. The energy changes. Work that felt heavy becomes fluid.</p>\n<p>Not because anyone became stronger individually.</p>\n<p>Because the pieces finally fit.</p>\n<hr>\n<p>There&#39;s a temptation, once you&#39;ve seen it work, to believe that more must be better.</p>\n<p>Rick and Morty captured this perfectly — and absurdly. Rick, never one for restraint, takes the Voltron idea and runs it straight off a cliff. Why have one combining Gotron when you can combine five Gotrons into the Gogotron? And five Gogotrons into the Gogogotron?</p>\n<p>The name gets longer. The thing gets bigger. The original purpose gets lost somewhere around the third &quot;go.&quot;</p>\n<p>It&#39;s funny because it&#39;s so recognizable.</p>\n<p>More pieces. More layers. More spectacle. No clearer purpose. Just the compulsive logic of: if combining worked once, combining again must work better.</p>\n<p>If one strong team is good, ten must be unstoppable.\nIf coordination creates power, maximum coordination must create maximum power.</p>\n<p>So we stack.</p>\n<p>Teams on teams.\nLayers on layers.\nStructure on structure.</p>\n<p>At some point, it stops being formation and starts being accumulation.</p>\n<p>That&#39;s the shift.</p>\n<p>The original idea wasn&#39;t about becoming bigger.</p>\n<p>It was about becoming something new.</p>\n<p>The lions didn&#39;t stack.</p>\n<p>They fit.</p>\n<p>The best organizations I&#39;ve seen don&#39;t grow by endlessly adding.</p>\n<p>They grow by forming.</p>\n<p>Strong individuals.\nStrong teams.\nClear roles.\nMutual trust.</p>\n<p>And then, when needed, those teams align into something larger.</p>\n<p>Not because they&#39;ve been stacked.</p>\n<p>Because they know how to lock together.</p>\n<hr>\n<p>I&#39;m still chasing it.</p>\n<p>Not the spectacle. Not the scale.</p>\n<p>The moment the pieces lock. The shift in the room. The work that suddenly moves like it knows where it&#39;s going.</p>\n<p>And when it works, you don&#39;t declare victory and disband.</p>\n<p>You do it again.</p>\n<p>With a new problem. A new moment. A new configuration of people who are each whole on their own.</p>\n<p>Formation isn&#39;t a destination.</p>\n<p>It&#39;s a practice.</p>\n<p>Something you keep doing, keep earning, keep building toward.</p>\n<p>Every time.</p>\n<p>Voltron form.</p>\n"
    },
    {
      "id": "https://lowdiatribe.net/reflection/2026-03-06-in-between-notes",
      "url": "https://lowdiatribe.net/reflection/2026-03-06-in-between-notes",
      "title": "In between notes",
      "date_published": "2026-03-06T23:00:00.000Z",
      "summary": "Trust isn't built in the dramatic moments — the crises, the wins, the hard conversations. It's built in the unremarkable Thursday. The Slack message that didn't need to be sent. The meeting that ended early. Miles Davis knew it about music. The same is true for teams, relationships, and life.",
      "tags": [
        "teams",
        "leadership",
        "trust",
        "resilience",
        "relationships"
      ],
      "content_html": "<p>Miles Davis said it:</p>\n<p>&quot;It&#39;s not the notes you play. It&#39;s the notes you don&#39;t play.&quot;</p>\n<p>In music, the space matters as much as the sound. The same is true for teams.</p>\n<hr>\n<p>We remember the dramatic moments.</p>\n<p>The crisis that brought everyone together.\nThe celebration after the big win.\nThe difficult conversation that cleared the air.</p>\n<p>Those feel like the moments that build teams.\nThe peaks and valleys.\nThe notes that ring out.</p>\n<p>But those aren&#39;t where teams are built. They&#39;re where teams are revealed.</p>\n<hr>\n<p>Teams are built on the Thursday afternoon when nothing happened.</p>\n<p>No crisis. No celebration. No drama.</p>\n<p>Just someone asking how your day was and actually listening to the answer.</p>\n<p>A Slack message that didn&#39;t need to be sent, but was:</p>\n<p>&quot;Saw this and thought of you.&quot;</p>\n<p>The meeting that ended early because the work was done and nobody felt the need to perform productivity for another half hour.</p>\n<p>The moment someone admitted they were stuck and three people quietly showed up to help.</p>\n<hr>\n<p>These moments feel unimportant.</p>\n<p>They&#39;re not the story you tell when someone asks what makes your team work.</p>\n<p>But they&#39;re the foundation everything else stands on.</p>\n<hr>\n<p>The teams that weather storms together aren&#39;t built in the storm.</p>\n<p>They&#39;re built in the calm.</p>\n<p>In all those unremarkable moments when nothing urgent was happening, but people chose to show up for each other anyway.</p>\n<p>Trust doesn&#39;t accumulate in crisis.</p>\n<p>It accumulates in the ordinary.</p>\n<hr>\n<p>I&#39;ve seen teams that only came together for the dramatic moments.</p>\n<p>They&#39;d rally for the deadline.\nPull together in the emergency.\nCelebrate the win.</p>\n<p>But in between?</p>\n<p>Silence. Distance. Everyone back to their silos.</p>\n<p>So when the next crisis arrived, they had to rebuild from scratch every time.</p>\n<p>No foundation.</p>\n<p>Just the faint memory of the last time they managed to pull it off.</p>\n<hr>\n<p>The teams that last are different.</p>\n<p>They&#39;re built on ten thousand small moments no one remembers individually.</p>\n<p>The accumulated weight of showing up when it didn&#39;t matter.</p>\n<p>That&#39;s what catches you when you fall.\nThe shoulders you stand on to reach higher.</p>\n<hr>\n<p>And the more I notice this pattern, the more it shows up everywhere.</p>\n<p>Teams. Relationships. Life.</p>\n<p>The rest is a note too.</p>\n<hr>\n<p>Most of life isn&#39;t made of milestones.</p>\n<p>It&#39;s made of the quiet rituals that hold everything together.</p>\n<p>Feeding the fish and the other animals.</p>\n<p>Washing the dishes.</p>\n<p>Folding the laundry.</p>\n<p>The small maintenance work of a shared life.</p>\n<p>Nothing dramatic is happening.</p>\n<p>But something is being built in the space between.</p>\n<hr>\n<p>Sometimes it&#39;s sitting on the couch playing Goat Simulator 3 with my middle grandson.</p>\n<p>There&#39;s nothing profound happening.</p>\n<p>No life lesson being delivered.</p>\n<p>Just chaos, laughter, and the occasional flying goat.</p>\n<p>Which turns out to be serious work after all.</p>\n<p>Because those moments build something.</p>\n<p>Connection.</p>\n<p>Familiarity.</p>\n<p>The quiet understanding that we enjoy being in the same room together.</p>\n<hr>\n<p>I spend a lot of time with all my grandchildren.</p>\n<p>Which means a lot of my most important work looks suspiciously like doing nothing important at all.</p>\n<p>Sitting on the floor.</p>\n<p>Answering questions about space.</p>\n<p>Playing ridiculous video games.</p>\n<p>Showing up tomorrow to do it all over again.</p>\n<hr>\n<p>None of these moments look important.</p>\n<p>They&#39;re not milestones.</p>\n<p>They won&#39;t show up in a highlight reel.</p>\n<p>But they&#39;re the space between the notes.</p>\n<p>And without that space, the music doesn&#39;t work.</p>\n<hr>\n<p>The dramatic moments are still important.</p>\n<p>The turning points.</p>\n<p>The hard conversations.</p>\n<p>The victories you celebrate together.</p>\n<p>But those moments only work because of everything that came before them.</p>\n<p>All the ordinary days that built the trust to survive the extraordinary ones.</p>\n<hr>\n<p>You can&#39;t manufacture this.</p>\n<p>But you can notice the unremarkable Thursday.</p>\n<p>The small gesture no one will remember.</p>\n<p>The conversation that goes nowhere important.</p>\n<p>The dishes.</p>\n<p>The fish.</p>\n<p>The ridiculous video game with a flying goat.</p>\n<p>This is where trust lives.</p>\n<p>Not in the crisis.</p>\n<p>In the calm.</p>\n<hr>\n<p>The foundation isn&#39;t built in the moments that feel important.</p>\n<p>It&#39;s built in the moments that feel like nothing at all.</p>\n<p>And when the storm comes —</p>\n<p>that&#39;s what holds.</p>\n"
    },
    {
      "id": "https://lowdiatribe.net/reflection/2026-02-20-batteries-not-necessarily-included",
      "url": "https://lowdiatribe.net/reflection/2026-02-20-batteries-not-necessarily-included",
      "title": "Batteries not necessarily included",
      "date_published": "2026-02-20T23:00:00.000Z",
      "summary": "My dog still respects an invisible fence whose batteries died years ago. Watching her obey a boundary that no longer exists made me wonder: how many of my own limits are just phantom constraints I've internalized? On untraining the conditioning that keeps us flinching at barriers that aren't even there.",
      "tags": [
        "growth",
        "leadership",
        "conditioning",
        "freedom",
        "boundaries"
      ],
      "content_html": "<p>We train our dogs carefully.</p>\n<p>Sit.\nStay.\nHeel.\nWait.</p>\n<p>I have two dogs.</p>\n<p><a href=\"/reflection/2026-02-06-i-want-to-be-my-dog\" target=\"_blank\">Henri</a> is a 16-kilogram French Bulldog — friendly, brave, not much else going on behind those eyes. Sonja is a nine-stone English Mastiff who prefers laying around to most forms of activity.</p>\n<p>Same household. Different training.</p>\n<p>We don&#39;t have a &quot;no dogs on the couch&quot; rule. I like having them sit with me.</p>\n<p>But Sonja has extensive &quot;no paw&quot; training. When a Mastiff puts her paws on you in greeting, someone is going down. Henri never had to learn  that rule. His paws won&#39;t knock anyone over.</p>\n<p>Henri did learn something else, though.</p>\n<p>He&#39;s the sheriff of the cats.</p>\n<p>Whenever a cat would sharpen their claws on the couch or a doorframe, I&#39;d shout &quot;Cat!&quot; or make a sharp &quot;TSST!&quot; sound as a deterrent. Henri learned that was his cue. His &quot;chase a cat free&quot; card. Permission to ignore one house rule to enforce another.</p>\n<p>I never explicitly taught him this. He just picked it up. Now he patrols. Watches. Waits for the signal.</p>\n<p>The problem is, he doesn&#39;t distinguish between the command and the word.</p>\n<p>He&#39;ll be sleeping on the couch while I tell a story about one of his feline companions. I&#39;ll say &quot;cat&quot; in passing. He springs into action. Ready to regulate.</p>\n<p>Or I&#39;ll make that &quot;TSST!&quot; sound at <a href=\"/reflection/2025-11-18-the-bird-who-lived\" target=\"_blank\">the bird</a> to shake her off of Sonja. He&#39;ll chase whichever cat is closest.</p>\n<p>The learned behavior has no context.\nJust trigger and response.</p>\n<p>I see in Henri how I can respond without thinking.</p>\n<p>The training isn&#39;t about them.\nIt&#39;s about my limits.</p>\n<p>And it works.</p>\n<p>We used to have an &quot;invisible&quot; fence around the yard. The batteries died in Sonja&#39;s collar a few years ago.</p>\n<p>She continued to respect the boundary, even after we took the collar off.</p>\n<p>She stops at the property line. Henri stays in the yard because Sonja does. He never wore the collar at all.</p>\n<p>The barrier exists because they believe it does.</p>\n<p>The mechanism becomes optional. They learned the boundary so well they stop at the edge of the yard even when the gate is wide open.</p>\n<p>Which is when I started noticing something.</p>\n<p>The thing is — we do the same to ourselves.</p>\n<p>We train caution.</p>\n<p>One polite &quot;don&#39;t.&quot;\nOne subtle frown.\nOne moment when enthusiasm meets silence.</p>\n<p>Nothing dramatic. No trauma required. Just repetition.</p>\n<p>Over time, the barrier moves inside.</p>\n<p>The signal becomes internal:\nDon&#39;t go there again.</p>\n<p>We call it discipline.\nWe call it professionalism.\nWe call it maturity.</p>\n<p>Often, it&#39;s just conditioning.</p>\n<p>And like my dogs, I don&#39;t always notice when the training was mine to set.</p>\n<p>When I first started leading teams, I built my own fence around authority.</p>\n<p>I believed good leaders always had answers.\nNo hesitation.\nNo doubt.\nNo pause.</p>\n<p>So I trained myself into certainty.</p>\n<p>Always respond.\nAlways decide.\nAlways appear sure.</p>\n<p>It worked — until it didn&#39;t.</p>\n<p>Because people don&#39;t trust the mask.\nThey trust the person behind it.</p>\n<p>The first time I said, &quot;I don&#39;t know,&quot; the room relaxed.</p>\n<p>The rule I thought was structural turned out to be learned.</p>\n<p>Most ceilings aren&#39;t structural.</p>\n<p>They&#39;re rehearsed.</p>\n<p>I&#39;ve been making an effort to find where else I do this.</p>\n<p>Training has value. Repetition builds skill. Discipline protects progress.</p>\n<p>But the line between practice and programming is thin.</p>\n<p>Most training isn&#39;t neutral.\nIt reflects the trainer&#39;s comfort zone as much as the student&#39;s capability.</p>\n<p>Which means the boundaries I set might outlive their purpose.</p>\n<p>A dog trained to stop at the edge of the yard stays safe from cars. The same training can keep it from running free when the world opens up. Conditioning doesn&#39;t ask whether the rule still applies. It just obeys.</p>\n<p>I&#39;m not much different.\nI master routines until they master me.</p>\n<p>Or I used to.</p>\n<p>I&#39;ve had to learn to notice when I&#39;m still following rules that no longer serve.</p>\n<p>When I catch myself avoiding something not because it&#39;s wrong, but because it&#39;s unfamiliar.\nWhen I realize I&#39;m protecting a process because it feels safe, not because it works.\nWhen I choose silence over truth because the boundary feels real.</p>\n<p>In work, it shows up as reluctance to challenge process. Fear of speaking up. Over-politeness that smothers progress. The meeting where everyone nods, knowing something&#39;s off, but no one wants to cross the barrier.</p>\n<p>In personal growth, it&#39;s subtler. When I stop learning new skills because I don&#39;t want to look clumsy. When I confuse stability for peace.</p>\n<p>I&#39;ve watched teams chase &quot;best practices&quot; long after they&#39;ve stopped being best. I&#39;ve seen people — myself included — cling to old habits of safety even when they quietly cost us creativity, risk-taking, invention.</p>\n<p>So how do you untrain a limit?</p>\n<p>I&#39;m still learning this.</p>\n<p>But I&#39;ve started with naming it.</p>\n<p>Where do I hesitate when I don&#39;t need to?\nWhat rule am I following that no one remembers setting?\nWhose approval am I still chasing when no one is watching?</p>\n<p>Then I try small experiments.</p>\n<p>I step two inches past the line.\nI say the quiet thing out loud.\nI show the unpolished draft instead of the finished pitch.</p>\n<p>Nine times out of ten, the collar doesn&#39;t even have batteries.</p>\n<p>I&#39;ve just been flinching out of habit.</p>\n<p>In teams, I&#39;ve practiced this kind of untraining as a form of leadership.</p>\n<p>You can&#39;t command creativity into existence. You can only make it safe to wander.</p>\n<p>It means celebrating experiments even when they fail.\nLetting the cautious try boldness without punishment.\nNoticing that &quot;that&#39;s not how we do things&quot; is really just muscle memory.</p>\n<p>My favorite teams don&#39;t just build capability — they build permission.\nPermission to stretch. To err. To unlearn.\nThey replace &quot;stay&quot; with &quot;let&#39;s go.&quot;</p>\n<p>When you&#39;ve spent years in obedience — to a company, a process, a version of yourself — you forget what improvisation looks like.</p>\n<p>The freedom you&#39;re looking for isn&#39;t rebellion.</p>\n<p>It&#39;s recovery.</p>\n<p>I have to practice it the same way I practiced the limits: through repetition.</p>\n<p>Each small act of courage becomes its own cue.\nEach moment I ignore the phantom boundary, the signal weakens.</p>\n<p>Eventually, I realize the collar doesn&#39;t even have batteries.</p>\n<p>Every fence I&#39;ve built once protected me.</p>\n<p>The point isn&#39;t to tear them all down.\nIt&#39;s to notice which ones I&#39;ve outgrown.</p>\n<p>The fence doesn&#39;t ask whether it still serves you.</p>\n<p>It just holds.</p>\n<p>The gate might not be locked.</p>\n<p>Try the handle.</p>\n"
    },
    {
      "id": "https://lowdiatribe.net/reflection/2026-02-13-the-cost-of-experience",
      "url": "https://lowdiatribe.net/reflection/2026-02-13-the-cost-of-experience",
      "title": "The cost of experience",
      "date_published": "2026-02-13T23:00:00.000Z",
      "summary": "How competence narrows your life by making you unwilling to be a beginner. Re-embracing shoshin (beginner's mind) by choosing to be bad at new things—for yourself and for those watching.",
      "tags": [
        "growth",
        "learning",
        "competence",
        "shoshin",
        "practice"
      ],
      "content_html": "<blockquote>\n<p>&quot;Sucking at something is the first step towards being sorta good at something.&quot;</p>\n<p>— Jake the Dog</p>\n</blockquote>\n<p>I used to take pride in being good at everything I did.</p>\n<p>Not in an arrogant way. Just a quiet confidence that whatever I attempted, I could do well. I&#39;d built a reputation around it. The person who could pick up new things quickly, who delivered quality work, who made it look easy.</p>\n<p>It occurred to me recently that the only reason I was good at everything I did was because I&#39;d stopped doing things I wasn&#39;t good at.</p>\n<hr>\n<p>The pattern was subtle. I&#39;d try something new. If it came naturally, if I showed early promise, I&#39;d keep going. But if I struggled, if I felt incompetent, if it didn&#39;t click quickly — I&#39;d find reasons to stop.</p>\n<p>Not dramatic reasons. Just... other priorities. Time constraints. &quot;Not really my thing.&quot; The gentle drift away from discomfort.</p>\n<p>Over time, my life narrowed to the things I was already good at. And because I only did things I was good at, I built the narrative that I was good at everything. It was a curation of what I chose to attempt.</p>\n<hr>\n<p>This narrowing happened so gradually I didn&#39;t notice it. Each individual choice made sense. Why struggle with something that doesn&#39;t come naturally when you could invest that time in something you&#39;re already competent at?</p>\n<p>The logic felt sound. Focus on my strengths. Play to my advantages. Build on what I was already good at.</p>\n<p>But the cost was invisible until I looked back and realized how small my world had become.</p>\n<hr>\n<p>I started drawing again about a year ago. Picked up a pencil after years away. I could see what I wanted to create — the shapes were clear in my mind. But my hand wouldn&#39;t cooperate. The lines came out wrong. The proportions were off. The gap between vision and execution felt humiliating.</p>\n<p>I tapered off. Not a dramatic decision. Just... frustration. Other priorities. The quiet drift back to things I was already good at.</p>\n<p>But I&#39;ve learned I can selectively push through it. When I joined my <a href=\"https://lowdiatribe.net/eastereggs/quad-city-cuttaz.html\" target=\"_blank\" title=\"Quad City Cuttaz\">skate crew</a>, I could barely skate backwards. I fell. Got back up. Pushed through the awkwardness of being a beginner in front of people who&#39;d been skating for years.</p>\n<p>The difference wasn&#39;t the difficulty. It was the context. With skating, I had a crew. Social encouragement and accountability that made walking away harder than staying.</p>\n<p>With drawing, I was alone. Just me and the gap between what I could see and what I could create. No one to notice if I stopped. No reason to persist except the discomfort itself.</p>\n<p>I&#39;m learning that I&#39;m selective about which incompetence I&#39;m willing to endure. And that selectivity has shaped my life more than I realized.</p>\n<hr>\n<p>Pops put a guitar in my hands from the time I was old enough to hold one. I got reasonably proficient. Casual level. But when it came time to push past that — to really struggle with technique, to be bad again on the way to being good — I stopped.</p>\n<p>A few years ago I picked up the ukulele. It was easy. Four strings instead of six. Simpler chords. I could sound competent quickly. So I kept with it.</p>\n<p>I could tell myself it was about finding the right instrument. But really, it was about finding the instrument that didn&#39;t require me to be a beginner for very long.</p>\n<p>I grew up skateboarding in the midwest. Hill bombing, mostly. Never learned to drop in a half-pipe or skate a bowl or even ollie. A few years ago I tried dropping in at the park. Bit it spectacularly. Have not attempted it since.</p>\n<p>I could tell myself it&#39;s about safety. About being too old to risk that kind of fall. But really, it&#39;s about the embarrassment. About being someone who&#39;s been skating for decades but can&#39;t do what kids learn in their first month at the park.</p>\n<p>Drawing. Languages. Physical skills that required coordination I didn&#39;t naturally have. Social situations that felt awkward. Technical domains that didn&#39;t match my existing mental models.</p>\n<p>Each one, I had a reason. Each reason felt valid. But the cumulative effect was a life increasingly defined by what I&#39;d already mastered rather than what I might learn.</p>\n<p>The filter became: &quot;Only do things you&#39;re already good at.&quot;</p>\n<p>And that filter, applied consistently over years, creates a very narrow path.</p>\n<hr>\n<p>I gathered experience. Experience made me competent. Competence made me confident. Confidence made me risk-averse.</p>\n<p>Not in obvious ways. I still took on challenges. But only challenges within domains I&#39;d already proven myself in. New projects, but using familiar skills. Different contexts, but same core competencies.</p>\n<p>I was growing, but only along axes I&#39;d already established. Deepening expertise in areas I&#39;d already committed to. Getting better at being the person I&#39;d already become.</p>\n<p>I have to remind myself that I was terrified to take on people-leading responsibilities after decades as a hands-on technical guy. That stepping into that discomfort was one of the greatest choices I&#39;ve made. That I can push through, in ways that matter.</p>\n<p>But even that success became another axis to deepen. Another domain to master. I got good at leadership, but kept being unwilling to be bad at other things.</p>\n<p>The cost of experience isn&#39;t that you stop learning. It&#39;s that you stop being willing to be a beginner.</p>\n<hr>\n<p>Watching my grandson reminded me what I&#39;d lost.</p>\n<p>He&#39;s six. Autistic. Doesn&#39;t have filters yet. And he tries everything.</p>\n<p>He&#39;s terrible at a lot of things. Spectacularly, joyfully terrible. He doesn&#39;t care. He&#39;s not performing competence. He&#39;s just... trying things.</p>\n<p>I watch him struggle with something, fail completely, and immediately try again. No shame. No story about what it means that he&#39;s not good at it yet. Just the pure experience of attempting something new.</p>\n<p>He needs help most of the time. Doesn&#39;t hesitate to ask for it. No embarrassment about not knowing. No protection of competence he doesn&#39;t have yet.</p>\n<p>I used to be like that. Before I learned to protect my competence by only doing things I was already competent at. </p>\n<p>At least I think I used to be...</p>\n<p>I watch my middle grandson learning the same lesson I did. He&#39;s eight. Already building the filters. Already avoiding things that might make him look foolish. Already narrowing to what he&#39;s already good at.</p>\n<p>I see myself in him. The embarrassment when something doesn&#39;t come easily. The quiet drift toward competence and away from struggle. The story forming: &quot;I&#39;m good at everything I do&quot; because he&#39;s learning to only do things he&#39;s already good at.</p>\n<p>I want to show him something different. Not by telling him it&#39;s okay to be a beginner. But by being a beginner myself. By letting him see me struggle with drawing. With guitar. With things that don&#39;t come naturally.</p>\n<p>The best thing I can teach him is that it&#39;s never too late to be bad at something new.</p>\n<hr>\n<p>The Japanese have a word for this: shoshin. Beginner&#39;s mind.</p>\n<p>I <a href=\"https://lowdiatribe.net/s/brick\" target=\"_blank\" title=\"Another brick in the wall\">previously wrote about shoshin</a> in the context of building LEGO castles. How experience tempts you to rush, to build from memory instead of attention. How the assumption that you already know can be dangerous.</p>\n<p>But I was writing about it as a practice within domains I&#39;d already mastered. Building from attention instead of habit in areas where I had decades of experience.</p>\n<p>I missed the deeper point: shoshin isn&#39;t just about how you approach familiar work. It&#39;s about being willing to be a beginner again. Actually incompetent. Actually struggling. Actually not knowing.</p>\n<hr>\n<p>I&#39;m learning to notice when I avoid something because it would require being bad at it.</p>\n<p>The conversation I don&#39;t start because I might say the wrong thing. The skill I don&#39;t attempt because I&#39;d look foolish learning it. The domain I don&#39;t explore because I don&#39;t have the foundation others do.</p>\n<p>Each avoidance is small. Each one makes sense. But together, they&#39;ve created a life that gets narrower every year.</p>\n<p>The opposite of growth isn&#39;t stagnation. It&#39;s optimization. Getting better and better at a smaller and smaller set of things.</p>\n<hr>\n<p>Re-embracing beginner&#39;s mind isn&#39;t about about abandoning my expertise or pretending I don&#39;t know things I do know.</p>\n<p>It&#39;s about being willing to be incompetent again. To struggle. To be the person in the room who doesn&#39;t get it yet. To try things I&#39;ll probably be bad at.</p>\n<p>The only way I can expand what I&#39;m capable of is to spend time being incapable.</p>\n<hr>\n<p>I&#39;m trying to practice this. Small things. Things that matter.</p>\n<p>I drew yesterday. And today. After months of avoiding it, I picked up the pencil again. My hand still doesn&#39;t make the shapes my brain sees, but I&#39;m learning to be happy with the compromise they negotiate. The gap is still there. But I&#39;m staying with it instead of walking away.</p>\n<p>I started playing guitar again too. The one Pops left me. Pushing past casual. Learning what I avoided learning decades ago. My fingers still don&#39;t move the way I want them to. But I have to be willing to sound bad if I ever want to sound good .</p>\n<p>Not just for me. For the grandson who&#39;s watching. Who&#39;s learning whether it&#39;s safe to be a beginner by watching whether I&#39;m willing to be one.</p>\n<p>Attempting conversations I&#39;m not sure how to navigate. Trying physical activities that don&#39;t come naturally. Asking questions that reveal what I don&#39;t know. Learning how to ollie.</p>\n<p>It&#39;s uncomfortable. I&#39;ve spent years building competence, and now I&#39;m deliberately choosing the opposite. My instinct is to retreat back to what I&#39;m good at.</p>\n<hr>\n<p>The cost of experience is the narrowing. The gradual elimination of everything I&#39;m not already good at. The optimization toward competence that becomes a prison of capability.</p>\n<p>The practice is re-embracing the beginner. Not as a state I pass through on the way to mastery. But as a state I return to deliberately, repeatedly, because that&#39;s where growth lives.</p>\n<p>I used to take pride in being good at everything I did.</p>\n<p>Now I&#39;m learning to take pride in being willing to be bad at new things.</p>\n<p>That&#39;s a different kind of competence. And with my grandchildren watching, a more important one.</p>\n"
    },
    {
      "id": "https://lowdiatribe.net/reflection/2026-02-10-another-brick-in-the-wall",
      "url": "https://lowdiatribe.net/reflection/2026-02-10-another-brick-in-the-wall",
      "title": "Another brick in the wall",
      "date_published": "2026-02-10T23:00:00.000Z",
      "summary": "I keep several bins of LEGO bricks — some sorted, mostly not. Japanese concepts like ikigai, kaizen, and wabi-sabi give me language for what I'm learning: how I approach those bins is how I lead. Quietly. Imperfectly. One brick at a time.",
      "tags": [
        "leadership",
        "kaizen",
        "ikigai",
        "wabi-sabi",
        "gaman",
        "kintsugi",
        "shoshin",
        "hara-hachi-bu",
        "practice",
        "patience",
        "systems"
      ],
      "content_html": "<p>I keep several bins of LEGO bricks in my life.</p>\n<p>Literally, they&#39;re clear plastic tubs — some sorted, mostly not. Heavy. Full of possibility. Metaphorically, they&#39;re how most things I care about arrive: leadership, culture, systems, relationships, even myself. A lot of pieces. No instructions. The persistent sense that something meaningful could be built here.</p>\n<p>What I&#39;m learning — sometimes slowly, sometimes the hard way — is that how I approach those bins is how I lead.</p>\n<hr>\n<p>I&#39;ve been finding comfort in Japanese concepts lately. Not as borrowed wisdom or aesthetic fascination, but as language for patterns I&#39;m already living.</p>\n<p>Western civilization taught me to optimize, to scale, to prove value through velocity. Modern tech culture amplified this into doctrine: move fast and break things, ship or die, growth at all costs. And I&#39;m tired. Tired of the pressure to move faster. Tired of mistaking motion for progress. Tired of the assumption that if something isn&#39;t growing, it&#39;s dying.</p>\n<p>These concepts offer something different. Not a rejection of ambition, but a reframing of what progress actually looks like. They give me permission to build slowly. To value stability over scale. To recognize that a castle that still stands is more impressive than one that appeared quickly.</p>\n<hr>\n<p>I struggle with continuous improvement. Not because I don&#39;t believe in it, but because my instincts run toward the horizon.</p>\n<p>I see the finished castle immediately: towers, banners, symmetry. And then I look at the pile on the floor and feel the distance between vision and reality like a personal failure. My reflex is to compensate with a grand gesture. A dramatic start. A big commitment. Something that proves I&#39;m building something important.</p>\n<p>It never works.</p>\n<p>The bins don&#39;t yield to ambition. They yield to attention.</p>\n<hr>\n<p>Before anything else, there&#39;s a quieter question: What am I building, and why?</p>\n<p>Not how fast. Not how impressive. Why this castle exists at all.</p>\n<p>Ikigai — reason for being. When I skip that question, I snap bricks together just to feel movement. A wall here. A tower there. Technically clever. Emotionally hollow. Eventually abandoned. I&#39;ve done this with LEGO. I&#39;ve done this with teams.</p>\n<p>When the why is clear, patience becomes possible.</p>\n<hr>\n<p>Then comes the unglamorous phase: sorting a little, finding the flat pieces, building a base that doesn&#39;t wobble. Kaizen — continuous improvement — lives here. It&#39;s boring. It doesn&#39;t look like a castle yet.</p>\n<p>That&#39;s the part I resist.</p>\n<p>I understand this intellectually. My struggle is emotional. Grand gestures feel like progress. Small steps feel like delay. When I&#39;m tired or trying to prove something, I default to scale instead of steadiness. So kaizen isn&#39;t a productivity tactic for me. It&#39;s a corrective practice.</p>\n<p>What&#39;s the smallest brick that actually belongs here? Not the most impressive brick. The brick that actually belongs.</p>\n<hr>\n<p>Even then, the castle never looks exactly like the one in my head. The colors don&#39;t align perfectly. One tower leans. A wall uses a brick that &quot;doesn&#39;t belong&quot; but was the only one that fit.</p>\n<p>Wabi-sabi — finding beauty in imperfection. The mismatched pieces give the castle character. In leadership, the asymmetries do the same. Teams that communicate a little differently. Processes that work because of their quirks, not despite them. Trying to sand those edges down doesn&#39;t create excellence. It creates fragility.</p>\n<p>The imperfect castle is still a castle.</p>\n<hr>\n<p>At some point, something always breaks. A cat jumps on the table. A tower falls and takes part of the wall with it.</p>\n<p>My first instinct is frustration — not at the bricks, but at myself. I should&#39;ve known better. I should&#39;ve reinforced that. But what matters isn&#39;t whether I&#39;m disappointed. It&#39;s whether I transmit panic or steadiness.</p>\n<p>Gaman — enduring with dignity. Staying composed enough that others don&#39;t have to carry my stress in addition to their own. Rebuilding calmly. Not punishing the castle for falling or the cat for doing cat things.</p>\n<p>When I rebuild, it&#39;s never identical. Different bricks. Reinforced in a new way. The seam is visible if you know where to look. Kintsugi — repairing with gold — teaches that the repair is part of the beauty. In leadership, this is the failure we don&#39;t erase. The postmortem that actually changes behavior. The history that makes the system stronger because it&#39;s remembered, not hidden.\nThe repair is celebrated as part of the structure.</p>\n<hr>\n<p>Experience tempts me to rush. I&#39;ve built castles before. I think I already know how. That assumption is dangerous.</p>\n<p>Shoshin — beginner&#39;s mind. Building from attention instead of memory. Asking questions I could assume answers to. Letting new voices challenge old patterns. The castle benefits when I stop building from habit and start building from presence.</p>\n<p>And then there&#39;s restraint. The best castles aren&#39;t the ones where every brick gets used. They&#39;re the ones with space. Courtyards. Walkways. Margin. Hara hachi bu — eat until 80% full — reminds me to stop at &quot;enough.&quot; Not because I&#39;m lazy. Because I want the castle to last.</p>\n<p>Some bricks stay in the bin. That&#39;s not waste. That&#39;s wisdom.</p>\n<hr>\n<p>Western productivity taught me to prove progress through scale. These practices remind me to recognize progress through stability. A castle isn&#39;t impressive because it appeared quickly. It&#39;s impressive because it still stands.</p>\n<hr>\n<p>So when I feel the pull toward grand gestures, I picture the bins. I sit on the floor. I pick up one brick. I ask where it actually belongs.</p>\n<p>That&#39;s how I build LEGO castles. That&#39;s how I try to lead.</p>\n<p>Quietly. Imperfectly. One brick at a time.</p>\n"
    },
    {
      "id": "https://lowdiatribe.net/reflection/2026-02-06-i-want-to-be-my-dog",
      "url": "https://lowdiatribe.net/reflection/2026-02-06-i-want-to-be-my-dog",
      "title": "I want to be my dog",
      "date_published": "2026-02-06T23:00:00.000Z",
      "summary": "Watching my French Bulldog Henri move through the world without carrying stories forward, I'm learning the difference between broken and wounded. The filters I built to protect me became walls, I can choose when to set them aside.",
      "tags": [
        "presence",
        "filters",
        "authenticity",
        "healing"
      ],
      "content_html": "<p>I want to be my dog.</p>\n<p>Not in some whimsical &quot;wouldn&#39;t it be nice&quot; way. I mean it. I watch my French Bulldog move through the world and I see something I&#39;ve lost. Something I&#39;m trying to find again.</p>\n<p>Henri&#39;s the bravest, friendliest creature I know. And he doesn&#39;t carry stories forward.</p>\n<p>Someone steps on his paw, he yelps, he moves. Five minutes later, that person is his favorite person again. No grudge. No narrative about what it means. No filter that says &quot;this person is dangerous&quot; or &quot;I should be more careful around them.&quot;</p>\n<p>Just: that hurt, now it doesn&#39;t, moving on.</p>\n<hr>\n<p>I was talking to a good friend the other day and found myself saying &quot;I feel broken and need fixing.&quot;</p>\n<p>Watching Henri heal from a hurt paw, I realized that&#39;s mechanical language, not human language.</p>\n<p>Broken implies defective. Something wrong with the design. Needs repair to return to factory specs.</p>\n<p>Wounded implies hurt. Natural response to injury. Needs care to heal. Might become whole again, possibly different than before.</p>\n<p>Henri doesn&#39;t think he&#39;s broken when he&#39;s hurt. He just heals.</p>\n<hr>\n<p>Mitch Hedberg had a bit: &quot;I find that a duck&#39;s opinion of me is influenced very much by whether or not I have bread.&quot;</p>\n<p>That&#39;s it. That&#39;s the whole calculation. Bread equals good. No bread equals neutral. No grudges. No expectations beyond the now. No stories about worthiness or deservingness or past interactions.</p>\n<p>Humans complicate this with narratives. We turn &quot;no bread today&quot; into &quot;never appreciated me&quot; into &quot;always taken for granted&quot; into a filter that colors every future interaction.</p>\n<p>Henri doesn&#39;t do that. Bread or no bread, he&#39;s just here. Present. Responding to what is, not what was or might be.</p>\n<hr>\n<p>I watch my six year old grandson sometimes. He&#39;s the youngest of the grandchildren, and he&#39;s autistic. He may not build the filters most people do.</p>\n<p>His lack of filters makes life really difficult for him. The world is built for filtered people. For people who&#39;ve learned to perform, to read social cues, to carry context forward.</p>\n<p>But his purity, his authenticity — they&#39;re the pinnacle of what I&#39;ve seen in a human.</p>\n<p>He doesn&#39;t perform. He lives. He doesn&#39;t calculate. He feels.</p>\n<p>And I see the cost of both paths. What I envy — his clarity, his authenticity — versus what makes survival easier — our filters, our performance.</p>\n<p>My grandson and Henri both move through the world without the weight of accumulated stories. They respond to what is. And watching them, I see some of what I&#39;ve lost in all my learning.</p>\n<hr>\n<p>I&#39;ve spent years building filters. Learning what to attend to, what to ignore. How to perform. How to carry stories forward so I don&#39;t make the same mistake twice.</p>\n<p>The filters protected me. They helped me navigate. Helped me build competency.</p>\n<p>But somewhere along the way, they stopped being tools and became walls. I stopped responding to what is. I started responding to what I&#39;ve learned to expect. To stories I&#39;m carrying about what things mean.</p>\n<p>Henri doesn&#39;t do that. My grandson doesn&#39;t do that.</p>\n<p>And when I&#39;m hurt, I reach for mechanical language — &quot;broken&quot; — because it feels less vulnerable than admitting I&#39;m wounded. But the language shapes how I treat myself. &quot;Broken&quot; invites judgment. &quot;Wounded&quot; invites compassion.</p>\n<hr>\n<p>I know I can&#39;t actually become Henri. I can&#39;t unlearn everything and return to some imagined state of pure presence.</p>\n<p>But I&#39;m learning to notice when I&#39;m responding to the story instead of the moment. To catch myself saying &quot;broken&quot; and choose &quot;wounded&quot; instead. To watch Henri move through the world — no grudges, no performance, just presence — and remember that&#39;s still possible. Not as a permanent state, but as a practice.</p>\n<p>The filters aren&#39;t the enemy. They&#39;re just tools that became walls. Henri can&#39;t choose when to use his filters because he doesn&#39;t have any to set down.</p>\n<p>But I do. And that&#39;s not a curse. It&#39;s a choice.</p>\n<hr>\n<p>I want to be Henri because he reminds me of something I&#39;ve forgotten.</p>\n<p>That presence is possible. That wounds heal. That you don&#39;t have to carry every story forward. That bread or no bread, you can just be here.</p>\n<p>I&#39;m wounded, not broken. And wounded things heal.</p>\n<p>Henri knows that, and I&#39;m learning.</p>\n"
    },
    {
      "id": "https://lowdiatribe.net/reflection/2026-02-03-someone-was-watching",
      "url": "https://lowdiatribe.net/reflection/2026-02-03-someone-was-watching",
      "title": "Someone was watching",
      "date_published": "2026-02-03T23:00:00.000Z",
      "summary": "Pops was watching from around the corner while I learned to walk. Years later, I'm learning what it means to hold space for others the way he held space for me.",
      "tags": [
        "leadership",
        "presence",
        "support",
        "witnessing",
        "growth"
      ],
      "content_html": "<p>I&#39;ve told <a href=\"/reflection/2026-01-30-im-scared-too-i-do-it-anyway#:~:text=Pops%20used%20to%20tell%20a%20story\" target=\"_blank\">my walking story previously</a>. How I wouldn&#39;t let anyone see me learning to walk. How I&#39;d practice in secret, falling over and over, then sit back down the moment someone entered the room. How one day I just walked out, fully formed, like I&#39;d known how all along.</p>\n<p>I always thought the point of the story was about me. About perfectionism. About not wanting to be seen struggling. About the pattern I carried for decades: perfect it in private, only perform when polished.</p>\n<p>But it occurs to me now, all these years later, that I only thought no one was watching.</p>\n<p>Pops was watching.</p>\n<hr>\n<p>He was hiding around the corner. Witnessing without interfering. Holding space for me to find my own way.</p>\n<p>But it wasn&#39;t just that he was lurking there, waiting. Everything he did when he wasn&#39;t around the corner created the conditions that made it possible to wait around the corner.</p>\n<p>He&#39;d built trust. He&#39;d been there consistently. He&#39;d proven he was safe. So when I needed to feel alone to explore, I could feel alone without feeling abandoned. The foundation was already there.</p>\n<p>The watching wasn&#39;t the work. The work was everything that came before the watching. The work was building the kind of relationship where I knew, even when I couldn&#39;t see him, that he was there if I needed him.</p>\n<p>He didn&#39;t correct my form. Didn&#39;t coach my technique. Didn&#39;t rush me or offer suggestions. He just watched me fall, over and over, trusting that I&#39;d find my way.</p>\n<p>The kind of witness that doesn&#39;t make you self-conscious.</p>\n<hr>\n<p>There&#39;s a paradox here that I&#39;ve only recently begun to understand.</p>\n<p>I needed to feel unwatched to try. The moment I knew someone was looking, I&#39;d stop. Sit down. Pretend I wasn&#39;t attempting anything. The audience made the risk unbearable.</p>\n<p>But I also needed him watching to be safe. Not just physically safe, though that too. Safe to fail. Safe to fall. Safe to struggle without it meaning something was wrong with me.</p>\n<p>Pops created the conditions for me to feel alone enough to explore, while never being abandoned.</p>\n<hr>\n<p>I&#39;ve spent years thinking about the audience I feared. The judgment I was avoiding. The performance anxiety that kept me frozen.</p>\n<p>But I misread the audience entirely.</p>\n<p>I assumed watching meant judging. That witness meant critic. That being seen meant being evaluated.</p>\n<p>Pops was watching, but not like that. He was watching the way you watch a sunrise. Present. Attentive. Without needing it to be different than it is.</p>\n<hr>\n<p>Struggle is learning, not failing.</p>\n<p>He saw me fall over and over, and he didn&#39;t see failure. He saw the process. He saw what falling was teaching me about balance, about weight distribution, about getting back up.</p>\n<p>He didn&#39;t need to prevent my struggle. He trusted it.</p>\n<p>That&#39;s the kind of witness I want to be.</p>\n<hr>\n<p>I think about this now when I&#39;m working with people who are learning something new. Who are trying something that scares them. Who are falling over and over in their own ways.</p>\n<p>The instinct is to step in. To correct. To coach. To prevent the fall. To make it easier.</p>\n<p>But sometimes the most supportive thing you can do is hide around the corner. Be present without being intrusive. Hold space without taking space.</p>\n<p>Watch them struggle, trusting that struggle is teaching them something you can&#39;t.</p>\n<hr>\n<p>There&#39;s an art to this kind of presence.</p>\n<p>Too far away, and it&#39;s abandonment. Too close, and it&#39;s pressure. The self-consciousness freezes them.</p>\n<p>Pops found the distance where I could feel alone enough to try, but held enough to be safe. Close enough to hear. Far enough to be invisible.</p>\n<p>He would have been there if I&#39;d asked. But he knew I had to ask for it to be of any use. Help offered too soon teaches dependence. Help offered when asked teaches that it&#39;s safe to need support.</p>\n<p>The discipline of waiting to be asked.</p>\n<hr>\n<p>I don&#39;t always get this right.</p>\n<p>Sometimes I step in too soon. Sometimes I stay too far back. But I&#39;m learning to ask: What does this person need right now? </p>\n<p>Sometimes the most powerful thing you can say is nothing at all.</p>\n<hr>\n<p>I watched a development team I&#39;d recently scaled 3x work against a tightening deadline. Every instinct screamed to jump in. To take over. To fix it. I could see the pressure building, the struggle with new dynamics, the compressed timeline.</p>\n<p>But I sat back. Ready if asked. The same way Pops watched me fall.</p>\n<p>They didn&#39;t ask. They figured it out. And they learned something in that struggle I couldn&#39;t have taught them by stepping in — that they could handle the pressure, that they could figure it out together.</p>\n<p>If I&#39;d intervened, I would have robbed them of that.</p>\n<hr>\n<p>The walking story isn&#39;t just about me learning to walk.</p>\n<p>It&#39;s about Pops teaching me that struggle is safe. That falling is part of the process. That I could figure things out on my own, but I didn&#39;t have to do it alone.</p>\n<p>He was watching. Silently encouraging. Trusting the process. Holding space.</p>\n<p>And because he did that, I learned more than how to walk.</p>\n<p>I learned that someone could witness my struggle without needing to fix it. That being seen didn&#39;t have to mean being judged. That the audience I feared might actually be silently supporting me.</p>\n<p>I thought I was hiding my struggles. But he was watching me struggle without judgment. And realizing that — years later — has helped me be more open about my learning. More willing to be seen falling. More willing to ask for help when I need it.</p>\n<p>Because someone was watching then. And it didn&#39;t destroy me. It held me.</p>\n<hr>\n<p>I&#39;m still that kid who doesn&#39;t want anyone to see him fall. But now I&#39;m also trying to be the person around the corner — the one who watches without judging, who holds space without taking it, who trusts that struggle is teaching something I can&#39;t.</p>\n<p>And as I practice being that witness for others, I&#39;m learning to recognize it when I&#39;m the one struggling: the people watching might not be judges. They might be holding space. Trusting my process. Waiting to be asked.</p>\n<p>I still have to push through the instinct to freeze when I know someone&#39;s watching. I still want to perfect things in private. But I remember that someone was watching then. And even if someone is watching now, I don&#39;t have to feel embarrassed to let my process be seen.</p>\n<hr>\n<p>I also remember that I can&#39;t just show up and hold space. The foundation has to be there first. The trust. The consistency. The proof that you&#39;re safe. Pops could wait around the corner because he&#39;d already done the work that made the corner safe.</p>\n<p>Someone was watching. And that made all the difference.</p>\n"
    },
    {
      "id": "https://lowdiatribe.net/reflection/2026-01-30-im-scared-too-i-do-it-anyway",
      "url": "https://lowdiatribe.net/reflection/2026-01-30-im-scared-too-i-do-it-anyway",
      "title": "I'm scared too — I do it anyway",
      "date_published": "2026-01-30T23:00:00.000Z",
      "summary": "Courage isn't the absence of fear — it's acting despite it. From learning to walk in secret to presenting with visible trembling, the practice of carrying fear while still moving forward.",
      "tags": [
        "courage",
        "vulnerability",
        "anxiety",
        "practice",
        "leadership"
      ],
      "content_html": "<p>&quot;I need your help,&quot; she said. &quot;How do you do it? How do you present at these huge meetings? I&#39;m terrified to speak up in those kinds of situations.&quot;</p>\n<p>She was a talented engineer I&#39;d been mentoring. Sharp, capable, the kind of person who made everyone around her better. But she didn&#39;t feel comfortable voicing her ideas in large group settings. She&#39;d watch others speak while her insights stayed locked inside.</p>\n<p>She was looking for the secret. The technique that would make the fear go away.</p>\n<p>I didn&#39;t have one.</p>\n<p>&quot;I&#39;m scared too,&quot; I told her. &quot;I do it anyway.&quot;</p>\n<hr>\n<p>The silence that followed wasn&#39;t comfortable. She&#39;d asked for a solution, and I&#39;d given her what felt like a non-answer. But it&#39;s the only honest answer I have.</p>\n<p>I have almost the same level of anxiety calling a restaurant as I do speaking in front of large crowds. The scale of the task doesn&#39;t change the anxiety level. Calling to place a takeout order triggers the same internal alarm as a keynote presentation.</p>\n<p>Anxiety is anxiety, regardless of stakes.</p>\n<hr>\n<p>People see the performance and assume it means something about the internal experience. They watch you present to a hundred people and think: &quot;They must not be afraid.&quot; They see confidence and mistake it for the absence of fear.</p>\n<p>But confidence isn&#39;t the absence of fear. It&#39;s acting despite it.</p>\n<p>She was looking for the moment when I overcame my anxiety. When I learned to not be afraid. When I figured out how to make the fear stop.</p>\n<p>That moment never came. The fear didn&#39;t stop. I just stopped letting it make my decisions.</p>\n<hr>\n<p>There&#39;s a misconception about courage that we carry from childhood. We&#39;re taught that brave people aren&#39;t afraid. That heroes feel no fear. That confidence means certainty.</p>\n<p>It&#39;s a lie that keeps people frozen.</p>\n<p>I&#39;m not fearless. I&#39;m practiced at carrying fear while still moving forward.</p>\n<hr>\n<p>I realize how absurd it is to panic about a phone call to order food. It shouldn&#39;t trigger the same response as presenting to executives. But it does. The anxiety doesn&#39;t calibrate to the actual stakes. It just shows up — indiscriminate and insistent.</p>\n<p>If I waited for the anxiety to go away before acting, I&#39;d never make the call. I&#39;d never give the presentation. I&#39;d never do anything that triggered that response, which means I&#39;d never do anything.</p>\n<p>So I learned to do it anyway. Not because I&#39;m brave. Because the alternative is letting anxiety write my life.</p>\n<hr>\n<p>When I told her &quot;I&#39;m scared too,&quot; something shifted in her face. Not relief exactly. More like recognition.</p>\n<p>&quot;Does it get easier?&quot; she asked.</p>\n<p>&quot;The fear doesn&#39;t get smaller,&quot; I said. &quot;You just get better at carrying it.&quot;</p>\n<hr>\n<p>I stopped trying to overcome fear. I&#39;ve been working to change my relationship with it. Fear becomes information instead of instruction. It tells me something matters, not that I shouldn&#39;t do it.</p>\n<p>I&#39;ve learned to hear the fear without obeying it.</p>\n<hr>\n<p>Pops used to tell a story about how I learned to walk. I must have heard it a thousand times.</p>\n<p>&quot;You wouldn&#39;t let anyone see you learning to walk. If we were in the room, you&#39;d just sit on your butt and crawl. I&#39;d leave the room and hide around the corner. When you thought no one was watching, you&#39;d scoot over to the couch or whatever and pull yourself up over and over, falling every time. The moment I came back in, you&#39;d sit right back down like nothing had happened. Then one day I set you down in your room and went to talk to Mom in the living room. Two minutes later you came walking out. You learned to walk without letting anyone see you.&quot;</p>\n<p>I spent decades operating that way. Perfect it in private. Only perform when polished. Never let them see you fall.</p>\n<p>Somewhere along the way, I realized that pattern was keeping me frozen. The things worth doing don&#39;t wait for you to master them in secret. They require you to fall in front of people. To shake visibly. To admit &quot;I&#39;m scared too&quot; and do it anyway.</p>\n<p>I&#39;m still that kid who doesn&#39;t want anyone to see him fall, except I don&#39;t let that stop me anymore.</p>\n<hr>\n<p>After our talk, she presented at the next big meeting. Her voice shook. She kept going.</p>\n<p>Afterward she told me: &quot;I was terrified the whole time.&quot;</p>\n<p>&quot;I know,&quot; I said. &quot;And you did it anyway.&quot;</p>\n<p>That&#39;s not a lesser version of courage. It&#39;s the only version that exists.</p>\n<hr>\n<p>I still get anxious before presentations. I still dread making phone calls. The fear hasn&#39;t diminished with practice. Sometimes I still catch myself giving in to it. What&#39;s changed is my willingness to let it stop me, and I still have to work at that.</p>\n<p>The anxiety shows up. I acknowledge it. I do the thing anyway.</p>\n<p>Not overcoming. Not conquering. Just carrying.</p>\n<p>The line is here. The work starts now. And yes, it&#39;s terrifying.</p>\n<p>I&#39;m scared too — I do it anyway.</p>\n"
    },
    {
      "id": "https://lowdiatribe.net/reflection/2026-01-27-the-line-is-here",
      "url": "https://lowdiatribe.net/reflection/2026-01-27-the-line-is-here",
      "title": "The line is here",
      "date_published": "2026-01-27T18:00:00.000Z",
      "summary": "Violence two blocks from where I used to live collapses time and forces a reckoning with legitimate authority. Thirty-five years from Rodney King to Alex Pretti — the line must be drawn here.",
      "tags": [
        "authority",
        "accountability",
        "witnessing",
        "violence",
        "Minneapolis"
      ],
      "content_html": "<p>I spent the last half of the 90s in Minneapolis. I lived two blocks from the corner of 26th St and Nicollet Ave.</p>\n<p>If that intersection sounds familiar, it&#39;s where Alex Jeffrey Pretti was pepper sprayed and thrown to the ground, then beaten by six masked ICE agents, then shot to death. All of this in front of dozens of witnesses, several of them capturing the entire altercation on video.</p>\n<p>This happened today, January 24, 2026. Twenty-five years after I moved away.</p>\n<hr>\n<p>In 2001 remote work was practically unheard of, and I left Minneapolis for Silicon Valley to follow my career path. I&#39;ve lived in multiple places since, ultimately choosing country living. I&#39;ve built careers, relationships, entire chapters of life that have nothing to do with those Twin City streets, but Minneapolis will always hold a special place in my heart.</p>\n<p>I can still walk those two blocks in my mind. The route to the corner store, the sound of traffic on that street, the way light hit the buildings in late afternoon. I haven&#39;t lived there in 25 years, but the geography is still mapped in my body.</p>\n<p>When violence happens in a place you used to inhabit, it collapses time. The news says &quot;Minneapolis&quot; and my brain supplies the specific intersection, the specific distance, the specific texture of that neighborhood. It&#39;s not abstract. It&#39;s the place I bought milk.</p>\n<hr>\n<p>Dozens of people saw it happen. Several recorded it. In 2026, we have the technology to capture irrefutable proof. Everyone has a camera. Everything can be recorded. But the psychological cost of seeing and documenting violence — we&#39;re still learning how to carry that.</p>\n<p>The witnesses aren&#39;t just evidence. They&#39;re people who now have to live with what they saw.</p>\n<p>And it&#39;s our burden to share that burden. Not to take it from them — we can&#39;t. But to refuse to let them carry it alone. To witness their witnessing. To insist that what they documented matters, that their courage matters, that their trauma matters.</p>\n<p>When we look away, witnesses carry the full weight alone. When we engage, when we refuse denial, when we insist on accountability — we distribute the load. We say: you saw something real, and we see it too. We see you.</p>\n<hr>\n<p>This isn&#39;t the first time this kind of violence has happened. It&#39;s the most recent and most public time.</p>\n<p>When I was little I was taught to believe what I saw and heard. For the longest time, information only came from newspapers or television — both carefully constructed outlets that showed what they chose to show.</p>\n<p>I was 19 when the news finally dropped a glimmer of the reality of institutional violence. Rodney King, beaten by Los Angeles police officers while George Holliday&#39;s camera captured it from his apartment balcony. That grainy video changed something. Not everything — the officers were acquitted, the city burned — but something. It cracked open the possibility that what we&#39;d been told about authority and protection might not match what was actually happening.</p>\n<p>The era of peace and safety I&#39;d been raised to believe in was a carefully cultivated front that shielded some of us from what others experienced daily. The violence was always there. It just wasn&#39;t being shown to people who looked like me.</p>\n<p>People from historically excluded groups had been warning us about these things for generations. They were systematically silenced, dismissed, erased. The video didn&#39;t reveal new violence — it revealed violence that had always been happening to communities who&#39;d been trying to tell us.</p>\n<p>That was 1991. Thirty-five years ago. And we&#39;re still here.</p>\n<hr>\n<p>Multiple videos. Multiple angles. Dozens of witnesses.</p>\n<p>They all add up to tell one consistent story. The administration&#39;s account doesn&#39;t match the evidence.</p>\n<p>This is the gap that breaks trust in institutions. Not just the violence, but the refusal to acknowledge what&#39;s visible. The insistence that what we can all see didn&#39;t happen the way we saw it.</p>\n<p>Orwell wrote: &quot;The Party told you to reject the evidence of your eyes and ears. It was their final, most essential command.&quot;</p>\n<p>When institutions deny facts, they&#39;re not just contesting a narrative. They&#39;re demanding that we reject what we can see. They&#39;re declaring that truth is negotiable, that evidence is optional, that power determines reality.</p>\n<p>This is how authority becomes illegitimate. Not through the act of violence, but through the refusal to acknowledge its existence.</p>\n<hr>\n<p>Six masked agents. Multiple videos. A person dead on a Minneapolis street I used to walk.</p>\n<p>I&#39;ve spent years exploring what legitimate authority looks like. What it means to lead without hiding. What it takes to build trust instead of demanding it. Watching this unfold two blocks from where I used to live makes the contrast impossible to ignore.</p>\n<p>Legitimate authority doesn&#39;t wear masks. It doesn&#39;t hide behind anonymity or institutional protection. It stands visible, accountable, willing to be identified and questioned.</p>\n<p>Legitimate authority doesn&#39;t deny what&#39;s documented. It acknowledges hard truths, even when they&#39;re uncomfortable. Especially when they&#39;re uncomfortable. Because trust isn&#39;t built through denial — it&#39;s built through the willingness to face what&#39;s real.</p>\n<p>Legitimate authority doesn&#39;t require intimidation or violence to maintain itself. It earns respect through consistency, through accountability, through the daily practice of doing what it says it will do.</p>\n<p>The masks tell you everything. When authority hides its face, it knows it&#39;s doing something it can&#39;t defend in daylight.</p>\n<hr>\n<p>The violence happened today. In a place I left 25 years ago. In a neighborhood that was home but isn&#39;t anymore.</p>\n<p>Time collapses. I&#39;m simultaneously here — hundreds of miles away, decades removed — and there, two blocks from where I used to sleep.</p>\n<p>The place exists in two states. It&#39;s the Minneapolis I knew in the 90s, and it&#39;s the Minneapolis where this happened today. Both are real. Both exist in my mind simultaneously.</p>\n<p>I can&#39;t go back to the place I knew because it doesn&#39;t exist anymore — violence has rewritten it. The intersection is the same, but it means something different now.</p>\n<p>This is what violence does to place: it overwrites memory with trauma. The street I walked becomes the street where Alex was killed. Both are true. Both exist.</p>\n<hr>\n<p>I keep asking myself: what do we do when we witness injustice? When we see authority fail? When the place we love becomes the site of violence we can&#39;t undo?</p>\n<p>I&#39;m learning to carry it. Not as burden alone, but as responsibility.</p>\n<p>To name what happened. To refuse denial. To insist that documented reality matters, that truth isn&#39;t negotiable, and accountability isn&#39;t optional.</p>\n<p>To remember that proximity doesn&#39;t expire and that distance doesn&#39;t absolve us. </p>\n<p>I&#39;m practicing building the kind of authority I want to see: visible, accountable, willing to face hard truths. Leading without masks. Acknowledging what&#39;s real, even when it&#39;s uncomfortable. Creating environments where people don&#39;t have to fear the very systems meant to protect them.</p>\n<p>This is the work. Not spectacular. Not polished. Just the daily practice of refusing to look away, of carrying difficult truths, of building trust through consistency and accountability.</p>\n<p>The dissonance is permanent. Places are rewritten. People are gone.</p>\n<p>Alex Pretti is gone. Renée Good is gone.</p>\n<p>They are the two most visibly documented of at least seven people who have died in ICE custody or operations in the first 24 days of 2026. Geraldo Lunas Campos. Luis Beltran Yanez-Cruz. Parady La. Heber Sanchez Domínguez. Victor Manuel Diaz.</p>\n<p>This is just January.</p>\n<p>They join a long line of names: Amadou Diallo, Sean Bell, Oscar Grant, Trayvon Martin, Eric Garner, Michael Brown, Tamir Rice, Walter Scott, Freddie Gray, Philando Castile, Breonna Taylor, George Floyd, Tyre Nichols, Sonya Massey. Names that should never be forgotten.</p>\n<p>And countless unknown others who will never have the satisfaction of being named, remembered, or mourned beyond their immediate circles.</p>\n<p>We keep calling each one the last straw, as if there&#39;s a finite number. As if this time will finally be the breaking point. But the straws keep coming. Another name. Another video. Another denial. Another call for accountability that goes unanswered.</p>\n<p>This isn&#39;t political. It&#39;s only superficially about immigration policy or enforcement tactics. This is about whether we accept that authorities can kill people with impunity.</p>\n<p>No one deserves to be executed in the street. Not for their documentation status. Not for exercising their rights. Not for anything. The fundamental principle is simple, even if the systems that violate it are complex.</p>\n<p>It&#39;s up to us to make this the last straw, to stop all future ones. The line must be drawn here. This far, and no further.</p>\n<p>My body remembers those Minneapolis streets. My grandchildren will map their own streets, their own paths, their own memories. I want them to grow up in a world where authority doesn&#39;t hide behind masks. Where documented truth matters more than institutional denial. Where the places they love don&#39;t get rewritten by violence they&#39;re told didn&#39;t happen. Where the rights given to us by us apply to all of us, without exception.</p>\n<p>That world doesn&#39;t build itself. It&#39;s built through the daily practice of refusing to look away. Of insisting on accountability. Of modeling the kind of authority that earns trust instead of demanding it.</p>\n<p>Thirty-five years from Rodney King to Alex Pretti. I don&#39;t want my grandchildren marking another thirty-five years of the same cycle. The line is here. The work starts now.</p>\n"
    },
    {
      "id": "https://lowdiatribe.net/reflection/2026-01-23-chasing-waterfalls",
      "url": "https://lowdiatribe.net/reflection/2026-01-23-chasing-waterfalls",
      "title": "Don't go chasing waterfalls",
      "date_published": "2026-01-23T23:00:00.000Z",
      "summary": "On the dangerous hope of fabricating futures during a job search, and learning to stop crushing on companies. A reflection on patience, persistence, and permission to explore new paths.",
      "tags": [
        "resilience",
        "job-search",
        "learning",
        "vulnerability"
      ],
      "content_html": "<p>I&#39;ve been playing the long game for months. Waiting. Applying. Refining. Patient in the way you learn to be patient when there&#39;s no other choice.</p>\n<p>Then a former colleague reached out. She&#39;d moved to a new company and they were hiring. Encouraging messages. Raving about the hiring manager. The kind of referral that makes you think: maybe this is it.</p>\n<p>Friday morning: resume sent.<br>Friday afternoon: HR call scheduled.<br>Monday morning: HR call completed.<br>Monday afternoon: hiring manager call scheduled.<br>Tuesday morning: hiring manager call completed.<br>Tuesday afternoon: expecting next steps.\nWednesday: dying in anticipation.</p>\n<p>Nothing had actually changed. I&#39;d been waiting for months. But that steady progression from Friday through Tuesday tricked my nervous system into thinking bankable progress was being made. The end was in sight. I could relax.</p>\n<p>That&#39;s when hope crept in. Not the careful, grounded kind. The dangerous kind. The kind that fabricates futures. I started thinking about the perfect fit. The team. The work. The relief of finally landing somewhere that made sense. I wasn&#39;t just waiting anymore. I was planning.</p>\n<p>Then a single day of stillness felt like eternity.</p>\n<p>Thursday morning: the boiler-plate rejection.</p>\n<p>&quot;After careful consideration, we&#39;ve decided to move forward with other candidates. While we&#39;re unable to provide personalized interview feedback, please know that we truly appreciate the effort and time you invested in the process.&quot;</p>\n<p>The narrative I&#39;d been building collapsed in a single sentence.</p>\n<p>The familiar spiral started. Was I &quot;over qualified&quot;? Did I say something I shouldn&#39;t have? Did I not say something I should have?</p>\n<p>I could spend days in that loop. What did I miss. What could I have done differently. Maybe if I&#39;d emphasized this instead of that. Maybe if I&#39;d asked better questions.</p>\n<p>How could I make them see the future I saw.</p>\n<p>The phrase hung there. Make them see. Like they were missing something obvious. Like if I could just find the right words, the right angle, they&#39;d realize we were meant to be together.</p>\n<p>I sounded like a schoolboy talking about a crush.</p>\n<p>I was crushing on them. I&#39;d been crushing on every company I interviewed with. Looking for the things I wanted to see.</p>\n<p>Crushing on companies fueled the urgency with hope. The moment I started imagining the perfect fit, my nervous system set a deadline. Friday/Monday/Tuesday became &quot;we&#39;ll be out by Christmas.&quot; Wednesday was Christmas Eve. Thursday was the day that Christmas didn&#39;t come.</p>\n<p>The disappointment is the same every time.</p>\n<p>The fabricated future. The imagined fit. That was all in my mind.</p>\n<p>It&#39;s about the prolonged absence of stability.</p>\n<p>The job search at this level is like a day at DisneyWorld with attendance at capacity. Four hours waiting in line for a 90-second ride that shuts down just when you&#39;re next.</p>\n<p>That&#39;s what makes each &quot;no&quot; hurt. Not because that specific opportunity was special. Because it extends the timeline. Another week. Another month. Another line.</p>\n<p>I can&#39;t go back to how it was before the wait.</p>\n<p>But I can stop fabricating futures and their timelines. Stop trying to figure out what I could have done differently to make them see what I wanted them to see. I can stop crushing on companies.</p>\n<p>Because somewhere along the way, I&#39;d been so focused on the <em>how</em> that I forgot my <em>why</em>.</p>\n<p>I&#39;ve had a narrow view of what next steps should be. The default path: replicate and continue my career trajectory from BigBook Company. I never really questioned it.</p>\n<p>It&#39;s not a map I have to follow.</p>\n<p>I like building software. I like building teams. I like building culture. The common why: building. I want to make my world better and enjoy doing it. How I get there can take many paths.</p>\n<p>I just never gave myself permission to look.</p>\n<p>Giving myself permission doesn&#39;t change the waiting. The absence of stability remains. The search continues. &quot;No&quot; only becomes &quot;never&quot; when you stop.</p>\n<p>The work evolves. I persist. But I&#39;m done imagining perfect fits that don&#39;t exist.</p>\n<p>I&#39;m done chasing waterfalls.</p>\n"
    },
    {
      "id": "https://lowdiatribe.net/reflection/2026-01-20-my-hubris-just-gave-me-a-great-idea",
      "url": "https://lowdiatribe.net/reflection/2026-01-20-my-hubris-just-gave-me-a-great-idea",
      "title": "My hubris just gave me a great idea",
      "date_published": "2026-01-20T23:00:00.000Z",
      "summary": "When I catch myself saying 'my hubris just gave me a great idea,' it's a warning that I'm too excited to evaluate clearly. Hubris doesn't just give bad ideas—it makes me unable to see whether they're bad. The practice is simple: stop, quiet the noise, then let the signal come through.",
      "tags": [
        "self-awareness",
        "hubris",
        "decision-making",
        "blind-spots"
      ],
      "content_html": "<p>My hubris just gave me a great idea</p>\n<p>Whenever I ever say this phrase out loud, I need to stop immediately.</p>\n<p>Not because the idea is necessarily bad. Because I&#39;m no longer capable of seeing whether it&#39;s bad.</p>\n<p>The phrase itself is the warning. Like &quot;hold my beer&quot; or &quot;watch this&quot; — words that predict disaster. If you&#39;re saying it, you&#39;re already past the point of listening.</p>\n<p>It&#39;s a confidence trap.</p>\n<p>When I&#39;m most certain is when I&#39;m most vulnerable. The ideas that feel obviously right are the ones I don&#39;t stress-test. I don&#39;t seek input. I don&#39;t look for edge cases. I don&#39;t ask &quot;what am I missing?&quot;</p>\n<p>Hubris doesn&#39;t just give me ideas. It makes me unable to think they&#39;re anything other than great.</p>\n<p>The idea feels great because I&#39;m not thinking clearly. The excitement is blinding me to the flaws. I&#39;m so pleased with my own cleverness that danger looks like opportunity.</p>\n<p>It&#39;s the paradox of self-awareness.</p>\n<p>Can I recognize hubris in real-time? Or does naming it become its own form of hubris?</p>\n<p>&quot;My hubris just gave me a great idea&quot; sounds self-aware. Look at me, acknowledging my hubris. How humble. How insightful.</p>\n<p>But if I were actually self-aware, I wouldn&#39;t proceed. I&#39;d recognize the phrase as a red flag and stop. The fact that I&#39;m still excited about the idea means the self-awareness is performative.</p>\n<p>I&#39;m congratulating myself on recognizing the problem while ignoring the warning.</p>\n<p>Some phrases are canaries in coal mines. They tell you the air is already toxic.</p>\n<p>&quot;My hubris just gave me a great idea&quot; means:</p>\n<ul>\n<li>I&#39;m excited about the source, not examining the substance</li>\n<li>I&#39;m flattering myself instead of stress-testing the idea</li>\n<li>I&#39;m moving forward despite recognizing the danger</li>\n<li>I think self-awareness is enough to protect me</li>\n</ul>\n<p>It&#39;s not.</p>\n<p>Self-awareness without behavior change is just spectating your own mistakes.</p>\n<p>It&#39;s also a blind spot indicator.</p>\n<p>What makes an idea feel great when it comes from hubris?</p>\n<p>It flatters your expertise. It confirms your worldview. It makes you the hero. It requires no one else&#39;s input. It lets you move fast without friction.</p>\n<p>Those are all red flags dressed up as green lights.</p>\n<p>The ideas that feel most obviously right are the ones that need the most scrutiny. The confidence is the problem, not the solution.</p>\n<p>Which means I need a practice.</p>\n<p>I&#39;m writing this as a memo to myself. A tripwire. A circuit breaker.</p>\n<p>If I ever catch myself thinking &quot;my hubris just gave me a great idea,&quot; the practice is simple:</p>\n<p>Stop.</p>\n<p>Not &quot;proceed with caution.&quot; Not &quot;be more self-aware.&quot; Not &quot;acknowledge the hubris and continue anyway.&quot;</p>\n<p>Stop.</p>\n<p>The idea might be good. But I&#39;m not in a state to evaluate it. The hubris is too loud. The blind spots are too large. The confidence is too dangerous.</p>\n<p>Assume hubris has narrowed my focus and I have no way of knowing what I&#39;m not seeing.</p>\n<p>Write it down. Walk away. Come back when the excitement fades.</p>\n<p>Or say it out loud to someone I trust. Not as a pitch, but as a warning: &quot;My hubris just gave me a great idea — help me find what I&#39;m missing.&quot; The phrase becomes a request for perspective from someone who isn&#39;t caught in the excitement.</p>\n<p>Only then can I see whether the idea is actually good, or whether the hubris just made it feel that way.</p>\n<p>This isn&#39;t about avoiding confidence or gatekeeping every idea. <a href=\"/s/gates\" target=\"_blank\">I&#39;ve learned</a> that most internal gates are imaginary barriers that waste energy. Bold ideas require bold thinking.</p>\n<p>But this filter is different. It&#39;s not blocking ideas from being tried. It&#39;s preventing me from executing ideas I can&#39;t evaluate clearly.</p>\n<p>Hubris is static. It drowns out the signal — the risks, the flaws, the questions I should be asking. When I catch myself saying &quot;my hubris just gave me a great idea,&quot; the static is already too loud.</p>\n<p>That&#39;s when I stop. Not to kill the idea, but to quiet the noise first.</p>\n<p>Then the signal can come through.</p>\n"
    },
    {
      "id": "https://lowdiatribe.net/reflection/2026-01-16-youre-not-my-gatekeeper",
      "url": "https://lowdiatribe.net/reflection/2026-01-16-youre-not-my-gatekeeper",
      "title": "You're not my gatekeeper (and neither am I)",
      "date_published": "2026-01-16T23:00:00.000Z",
      "summary": "Exploring gatekeeping in tech culture, relationships, and most importantly, the gates we build for ourselves. The only pattern was me, wasting energy to make things more difficult.",
      "tags": [
        "leadership",
        "community",
        "vulnerability",
        "growth",
        "relationships"
      ],
      "content_html": "<p>When I was three, I was the Universe. When I was four, my Brother and Sister were born, and I learned competition.</p>\n<p>Twins. Suddenly I wasn&#39;t the center anymore. I was one of three, competing for attention, space, identity. Or rather, the perception of scarcity started to grow. Resources that felt infinite when I was the only one now felt limited.</p>\n<p>As a freshman in high school, I remember asking a girl if I could borrow one of her Cure tapes. I&#39;d seen a video on MTV and wanted to hear more. She launched into a seven-minute tirade about how The Cure had seven albums and a live EP and she really couldn&#39;t begin to imagine where to start someone who had no previous The Cure knowledge.</p>\n<p>That&#39;s gatekeeping. Not malicious, maybe. But effective at keeping people out.</p>\n<p>She didn&#39;t lend me the tape. I ended up buying it. It turns out, there&#39;s nothing preventing you from walking around some gates.</p>\n<p>But I learned something else from that interaction. I learned that you could protect what mattered to you by making it hard for others to access. I learned that in a world where everything gets shared, having something exclusive — something that was yours and not everyone else&#39;s — made it feel more special. And testing people&#39;s knowledge was a way to determine who deserved access to that special thing.</p>\n<p>Later, I started quizzing my Brother on the bands he said he liked. Making him prove his fandom. Testing whether he really knew the songs, the albums, the deep cuts. As if his enjoyment of the music I loved somehow diminished my claim to it.</p>\n<p>Exclusivity felt special, but it was lonely. Enjoying something in isolation has its place, but sharing the experience expands it. I didn&#39;t understand that then. Years of potential connection sacrificed to protect something that would have been better shared.</p>\n<p>The day I left for college, I stopped. Just like that. The perceived competition for resources disappeared when I moved out, and so did the gatekeeping. We started going to shows together. Sharing discoveries. It didn&#39;t matter who introduced whom to a band — we just enjoyed the music together.</p>\n<p>Now he&#39;s the first person I want to share new music with. Many of my current favorites came from him. The complete reversal: from gatekeeper to eager sharer. His discovery doesn&#39;t diminish mine — it enriches it. That&#39;s what abundance looks like.</p>\n<p>But I can&#39;t get back those years. That&#39;s the cost of gatekeeping.</p>\n<p>Tech culture taught me the same pattern, just with different stakes. &quot;You&#39;re not a real developer if you don&#39;t know [obscure framework].&quot; &quot;Have you read [canonical text]?&quot; &quot;Name three [things] if you&#39;re really into [thing].&quot; The constant testing instead of teaching. Protecting territory instead of expanding community.</p>\n<p>I encountered it at every stage. And I participated in it. Not just with my Brother, but in professional spaces where I should have known better.</p>\n<p>In my very first job after college as a system administrator, I was working with an even more junior colleague — I had maybe two years on him in age and experience. Barely anything. But those two years were in the exact same role he was now occupying, which somehow made me feel like I had authority to test him. I found myself randomly quizzing him about obscure tech. I didn&#39;t intend it in a judgy way — it was just subconscious expression of the brotherly habit I&#39;d built. But it suddenly felt weird in the workplace. My moment of clarity. I caught myself mid-pattern and shifted. Those quizzes became random poetic waxings about obscure tech in an attempt to spark a common interest instead of testing his knowledge.</p>\n<p>But I also learned to recognize it when it was happening to me.</p>\n<p>Decades later when I started working at <a href=\"/s/tow-cables\" target=\"_blank\" title=\"Growing tow cables in AT-AT country\">the Client</a>, I was pairing with a colleague at the beginning of his career. He had three years of experience — all of it in this role, his first job after school. We were practicing the kind of pair programming where one person writes a test, passes the keyboard, the other writes code to make it pass, then writes the next test and passes it back. Back and forth, building together.</p>\n<p>His tests started becoming obtuse. Convoluted. I assumed it was just his style — maybe a bit flowery, but harmless. Then he threw out a challenge that triggered something. Pattern recognition kicked in. My inner guide: &quot;You&#39;re not my gatekeeper.&quot;</p>\n<p>I saw it clearly. He was testing me to see if I really belonged. Gatekeeping me.</p>\n<p>I stopped. &quot;I&#39;m not sure if you are intentionally trying to make this more difficult than this needs to be, but I am starting to feel like you are, and I think it&#39;s leading us away from the bug we need to fix. I am happy to continue if we can keep it focused to the task at hand, but if this is meant to be some kind of lesson, I choose to not participate at that level.&quot;</p>\n<p>He admitted he was challenging me. And he backed off.</p>\n<p>&quot;I choose to not participate at that level.&quot; That&#39;s the boundary. Not defensive, not aggressive. Just a clear line: I&#39;m not playing this game. We can collaborate or we can compete for status, but I&#39;m only interested in one of those.</p>\n<p>Gatekeeping shows up everywhere once you start looking for it. In tech. In music scenes. In geek culture. In any community where people feel like they need to prove they belong.</p>\n<p>The impulse makes sense. When something matters to you, you want to protect it. You want to make sure the people entering your space really care, really understand, really deserve to be there. But what you&#39;re actually doing is creating isolation instead of community. You&#39;re gatekeeping the things you love, which keeps you from sharing them with people who might love them too.</p>\n<p>The irony is brutal: the more you gatekeep, the lonelier you become.</p>\n<p>I&#39;ve learned to recognize the pattern now. In myself and in others. Gatekeeping almost always comes from perceived scarcity. When resources feel limited — attention, recognition, identity, belonging — we start testing people to determine who deserves access. As if there&#39;s only so much to go around.</p>\n<p>But in most cases, the scarcity is imaginary. My Brother liking the same bands I liked didn&#39;t make me less of a fan. Someone else&#39;s enjoyment doesn&#39;t diminish mine.</p>\n<p>The abundance mindset is harder to maintain than it sounds. It requires believing that there&#39;s enough for everyone. That someone else&#39;s success doesn&#39;t require your failure. That sharing what you love makes it more valuable, not less.</p>\n<p>In leadership, this shows up as the difference between &quot;prove you belong here&quot; and &quot;welcome, let&#39;s build together.&quot; Between constantly testing people and creating environments where they can grow. Between protecting territory and expanding community.</p>\n<p>I&#39;ve spent years trying to build the latter. Environments where talented people can do their best work without having to constantly prove they deserve to be there. Where the barrier to entry is &quot;are you willing to learn and contribute?&quot; not &quot;can you pass this arbitrary test?&quot;</p>\n<p>But I still catch myself slipping into the old pattern. Still feel the impulse to protect what&#39;s mine. Still have to consciously choose abundance over scarcity.</p>\n<p>And then there&#39;s the gatekeeping I do to myself.</p>\n<p>I&#39;ve struggled with this most of my life. Shooting down my own ideas before I&#39;ve even finished thinking them through. Testing them against some imaginary standard. &quot;That&#39;s not good enough.&quot; &quot;Someone&#39;s already done that better.&quot; &quot;Who are you to think you have something worth saying about this?&quot;</p>\n<p>In conversations, I&#39;ll have a thought that builds on what someone just said, but before I can speak, the internal gatekeeper steps in: &quot;Is this insightful enough? Will it sound stupid? Maybe just stay quiet.&quot;</p>\n<p>With writing, with projects, with anything that matters — the more I care about something, the higher I set the gate for myself.</p>\n<p>But lately I&#39;ve been trying to walk around my own gates the same way I walked around that girl&#39;s refusal to lend me The Cure tape.</p>\n<p>I started noticing something: no matter how strict I thought my internal gates were, they bore no relationship to the external barriers I actually encountered. Ideas I thought were carefully considered and articulated hit gates with ten thousand deadbolts. Throwaway thoughts I barely vetted flew through open doors and were received as valid and worth pursuing.</p>\n<p>The only pattern was me, wasting energy to make things more difficult.</p>\n<p>My internal gates are mostly figments of my imagination. They&#39;ve only ever given me exactly what I expected: reasons not to try.</p>\n<p>The universe may present every possible obstacle along my path. Why should I add to that?</p>\n<p>I&#39;m working on it. Trying to extend the same abundance mindset inward. Trying to remember that my ideas don&#39;t need to pass some arbitrary test before they&#39;re allowed to exist. That sharing something imperfect is better than hoarding something perfect that never sees the light of day.</p>\n<p>Trying to be as welcoming to my own thoughts as I try to be to others.</p>\n<p>The work is recognizing when I&#39;m gatekeeping and choosing differently. Welcoming instead of testing. Sharing instead of hoarding. Building community instead of protecting territory.</p>\n<p>And that includes the community of one — the space I create for my own ideas, my own voice, my own contributions.</p>\n<p>My roller skating community is the exact opposite of gatekeeping. I&#39;d even call it &quot;waygiving&quot; — active encouragement to try new things and extend yourself. No one asks you to prove you belong. They just hand you skates and say &quot;try this.&quot; It makes me want to create more of this everywhere.</p>\n<p>My Brother and I still go to shows together. We share music constantly. Some of my favorite discoveries came from him. Some of his came from me. It doesn&#39;t matter. What matters is that we&#39;re experiencing it together, without the test, without the proof, without the gates.</p>\n<p>That&#39;s what I lost all those years. And that&#39;s what I&#39;m trying to build now — in my relationships, in my work, in the spaces I create, in myself.</p>\n<p>You&#39;re not my gatekeeper. And I&#39;m not yours. We&#39;re just people who love the same things, trying to share them with each other.</p>\n"
    },
    {
      "id": "https://lowdiatribe.net/reflection/2026-01-13-holding-the-pen",
      "url": "https://lowdiatribe.net/reflection/2026-01-13-holding-the-pen",
      "title": "Holding the pen",
      "date_published": "2026-01-13T23:00:00.000Z",
      "summary": "Your filter isn't passive interpretation — it's active construction. Explores how attention shapes what we encounter, why patterns become self-fulfilling, and the realization that we're authoring our response to circumstance through the filters we choose. From sleep-deprived annoyance to recognizing we're holding the pen.",
      "tags": [
        "leadership",
        "awareness",
        "patterns",
        "perspective",
        "choice"
      ],
      "content_html": "<p>I slept horribly last night. Tossed and turned, didn&#39;t get a wink. \nJust my luck — everybody is being annoying today.</p>\n<p>Wait. I hear myself in that joke.</p>\n<p>Is everybody annoying? Or am I filtering for annoyance?</p>\n<p>The circumstance happened to me because it always happens to me. Except it doesn&#39;t. I just showed up looking for it.</p>\n<p>Your filter isn&#39;t passive interpretation. It&#39;s active construction. When you&#39;re exhausted, you notice every interruption. When you&#39;re anxious, you spot every potential threat. When you expect resistance, you interpret questions as pushback. The circumstance didn&#39;t change. Your attention did. And attention shapes what you encounter and how you respond to it.</p>\n<p>This is how patterns become self-fulfilling. The filter expects the circumstance, which primes you to notice it, which confirms the expectation, which reinforces the filter. The loop closes. The pattern locks.</p>\n<p>Circumstance happens to you until you realize you&#39;re also writing it. Not the external events — those are real. But how you meet them, what you expect from them, what story you tell about them. That&#39;s yours. Every choice you make, every interpretation you apply, every pattern you reinforce — you&#39;re holding the pen.</p>\n<p>For most of my life, I believed my story was written by an unseen hand. Circumstance shaped me. Experience defined me. The patterns I carried were just the accumulated weight of everything that had happened to me. I was the narrative, not the author.</p>\n<p>I&#39;ve read the Stoics. &quot;You are how you react to your circumstances.&quot; It never really clicked. It felt like a mental jump to just &quot;be better&quot; about accepting things. The switch happened for me when I realized our past choices shape our present circumstances, and our present choices shape our future ones. Not just the events themselves, but which ones we notice, how we interpret them, what patterns we let them reinforce.</p>\n<p>I was the one holding the pen.</p>\n<p>If I can pencil myself into a panic, I certainly should be able to purple crayon myself out of it.</p>\n<p>Not for everything. External forces are real. But I can control how I respond to them. What I choose to notice. Which patterns I reinforce and which I question. I&#39;m not just receiving my story — I&#39;m writing it, one choice at a time.</p>\n<p>That realization didn&#39;t change everything overnight. But it started the long progress toward filtering for what matters instead of defaulting to reflex. Toward choosing the data I surface instead of letting the old pattern choose for me. Toward authoring my circumstance through deliberate attention rather than accepting whatever the filter served up.</p>\n<p><a href=\"/s/reset\" target=\"_blank\" title=\"Reset\">I&#39;ve written before</a> about choosing where to place attention. This is the mechanism underneath that choice: your filter determines what&#39;s available to notice. Train yourself to see yellow, and yellow appears everywhere. Look for the teachable moments and you can start to see lessons. The path is visible to those who seek it.</p>\n<p>In leadership, the stakes multiply. The leader who filters for threat creates defensive teams. Every question becomes a challenge. Every suggestion becomes resistance. The team learns to stay quiet because speaking up gets interpreted as pushback. The leader who filters for potential creates exploratory teams. Questions become curiosity. Suggestions become collaboration. The team learns to speak up because their input gets interpreted as engagement.</p>\n<p>Same circumstances. Different filters. Different realities.</p>\n<p>I&#39;ve watched this in myself. When I filter for what&#39;s broken, I find evidence everywhere. When I filter for what&#39;s working, the same team looks different. The work didn&#39;t change. My attention did.</p>\n<p>The filter doesn&#39;t just shape what I notice. It shapes how I think I&#39;m supposed to act. I catch myself playing the part my circumstances seem to demand. If I&#39;m sick, I should be grumpy. If I&#39;m under pressure, I should be stressed. If things are hard, I shouldn&#39;t be cheerful. So I perform the expected mood, even when it&#39;s not what I actually feel. </p>\n<p>Somewhere I learned that society expected a certain performance, so I stuck to the script. The script became the path I followed without questioning if it was true.</p>\n<p><a href=\"/s/stories\" target=\"_blank\" title=\"The stories we tell ourselves\">The stories we tell ourselves</a> become the filters we see through. Tell yourself you&#39;re always behind, and you&#39;ll scan for evidence of falling short. Tell yourself nothing matters, and you&#39;ll miss the moments when it does. The filter is learned reflex. Our go-to. Its effects are instantaneous.</p>\n<p>But anything learned can be unlearned. Not erased — the old pattern doesn&#39;t disappear. But it can be overwritten with deliberate repetition. The work is patient, unseen, and constant: redirecting attention each time the reflex fires. Choosing a different data point to surface. Building a new default through accumulated micro-decisions.</p>\n<p>It takes time. The old filter took years to build. The new one won&#39;t install overnight. But the effects can be visible before the reflex fully rewrites. I&#39;m trying to focus on the positive, and a smile actually helps. Not as performance — as practice. The physical act of smiling shifts what I notice. The deliberate choice to look for what&#39;s working changes what I find. The filter adjusts incrementally, one redirect at a time. But recognizing you&#39;re holding the pen — that you&#39;re authoring your response to circumstance through the filter you choose — that&#39;s where the work begins.</p>\n<p>You can&#39;t control what happens. But you can control what you&#39;re scanning for. This is an act of curation — of stewardship for yourself and your world. Not controlling what exists, but choosing what gets your attention. What gets to shape your interpretation. What gets to define the moment.</p>\n<p>The circumstance is real. The filter is adjustable.</p>\n<p>What you look for becomes what you find. I choose to choose carefully.</p>\n"
    },
    {
      "id": "https://lowdiatribe.net/reflection/2026-01-09-blob-typing",
      "url": "https://lowdiatribe.net/reflection/2026-01-09-blob-typing",
      "title": "Blob typing",
      "date_published": "2026-01-09T23:00:00.000Z",
      "summary": "",
      "tags": [
        "frameworks",
        "systems",
        "leadership",
        "context",
        "resilience",
        "timing"
      ],
      "content_html": "<p>I&#39;m generally a fan of duck typing, it can be elegant in code. Identity revealed by behavior, not declaration. If it looks like a duck and moves like a duck and quacks like a duck, treat it like a duck.</p>\n<p>We have <span class=\"tooltip-hover\">Muscovy ducks<span class=\"tooltip-content\"><img src=\"/images/muscovy.jpg\" alt=\"Muscovy duck\" /></span></span> at our house — jungle birds from Central and South America. They walk like ducks. They mostly look like ducks. But they don&#39;t quack — they make a weird little warbling hiss instead.</p>\n<p>They technically fail the duck test. I still tend to call them ducks.</p>\n<p>Chico Marx saw this coming:</p>\n<p>&quot;Why a duck? Why not a chicken?&quot;</p>\n<p>It&#39;s a joke. It&#39;s also the question we stop asking once a framework starts feeling true.</p>\n<p>Duck typing is what happens when we infer identity from behavior. <span class=\"tooltip-hover\">Blob<span class=\"tooltip-content\"><img src=\"/images/blob.jpg\" alt=\"Blob\" /></span></span> typing happens when we forget we&#39;re making a choice. Enough of the pattern fits in a particular context. Then the context shifts and we&#39;re left holding a category that no longer fits — or worse, one we keep using anyway because it&#39;s close enough and easier than recalibration.</p>\n<p>Ant typing is one version of this. If you&#39;re carrying weight and reinforcing structure, you&#39;re an ant.</p>\n<p>We know the fable. The ant works all summer. The grasshopper plays. Winter comes. The ant survives. The grasshopper doesn&#39;t.</p>\n<p>The moral is clear: don&#39;t be a grasshopper. Be an ant.</p>\n<p>The hedgehog and the fox. One big thing versus many things. Clean distinctions. Easy to debate.</p>\n<p>Hedgehog typing: if you&#39;re focusing on one big thing, you&#39;re a hedgehog.</p>\n<p>I thought I understood both. I thought I was being an ant. I thought I was being a hedgehog.</p>\n<p>But that&#39;s not typing. That&#39;s type casting.</p>\n<p>Typing infers identity from behavior. Casting tries to force an outcome by emulating the behavior.</p>\n<p>I thought: do ant things, get ant results. Do hedgehog things, see hedgehog outcomes.</p>\n<p>If the ant survives winter, I&#39;ll survive winter by doing what ants do. If the hedgehog wins by focusing on one big thing, I&#39;ll win by focusing on one big thing.</p>\n<p>The behavior becomes a spell. The framework becomes certainty.</p>\n<p>I chose the hedgehog approach this year, driven by an ant-like determination to prepare for winter. I went heads down, all in on one big thing: finding a role aligned with how I actually lead — quiet authority, long horizons, systems built on trust and durability rather than theatrics.</p>\n<p>It was a principled bet. And it was real.</p>\n<p>It was also unnatural. I&#39;m a fox by nature — responsive, flexible, comfortable with many things at once. Committing to one big thing meant suppressing the adaptive instincts that usually serve me well.</p>\n<p>What I misjudged wasn&#39;t the value of alignment. It was assuming alignment would be legible, timely, and reciprocated within the available timeframe.</p>\n<p>I believed in a linear story that feels rational:</p>\n<p>clarity → recognition → stability</p>\n<p>It isn&#39;t false. It&#39;s just not guaranteed.</p>\n<p>While I was focused like a hedgehog, I thought I was working like an ant. Carrying weight. Reinforcing structure. Choosing steadiness over spectacle. I believed that if I went through the motions long enough, the environment would eventually resolve itself into a colony.</p>\n<p>That was the misread.</p>\n<p>I was focused on my efforts without gauging whether the plan still fit the moment. Laboring forward as a hedge-ant. What I needed was some strategic foxing — looking up, reading the terrain, adapting to what was actually happening instead of what I believed should happen.</p>\n<p>But I&#39;ve learned that both planning and reacting are seductive traps. The hedgehog plans. The fox reacts. Both feel productive. Neither is focused on now — the one thing we actually have control over.</p>\n<p>Ant work isn&#39;t just about behavior — it&#39;s about context. Ants don&#39;t survive because they&#39;re virtuous or tireless. They survive because the environment supports ant logic: shared shelter, distributed risk, collective winter planning.</p>\n<p>I was pouring ant-labor into a hedgehog task. Putting my preparations into a possibility without accounting for inevitability. The market was moving. I stayed committed to the plan without adjusting for the shift.</p>\n<p>Blob typing fails the same way. We identify the pattern. We match the behavior. We assume the category will hold. Then the context changes and the typing system breaks — not because we misread the behavior, but because we stopped checking whether the environment still supports the inference.</p>\n<p>The Muscovy still looks like a duck. I still treat it like one. But if I needed it to quack, I&#39;d be waiting a long time.</p>\n<p>Duck typing works only if you keep asking the follow-up question:</p>\n<p>Why a duck? Why not a chicken?</p>\n<p>Emulating an ant refined how I build. Emulating a hedgehog taught me how to maintain deep focus. Being a fox comes naturally, and emulating a hedge-ant taught me that it&#39;s necessary to be a fox from time to time.</p>\n<p>If I was going to emulate anything, it should have been a honey badger. The honey badger doesn&#39;t fit the fables, doesn&#39;t care about the frameworks. It doesn&#39;t plan for winter or pivot in real time. It works in the present. It figures out its next step, then makes it, regardless of cobra bite or bee sting. It responds to what&#39;s in front of it without requiring certainty and adapts without losing the thread.</p>\n<p>These are all just stories — idealized for illustration, not instruction manuals for living. Reality requires checking whether the pattern still fits the moment; verifying the context, not trusting the category.</p>\n"
    },
    {
      "id": "https://lowdiatribe.net/reflection/2026-01-06-imposter-cat",
      "url": "https://lowdiatribe.net/reflection/2026-01-06-imposter-cat",
      "title": "Imposter cat",
      "date_published": "2026-01-06T23:00:00.000Z",
      "summary": "",
      "tags": [
        "attention",
        "grace",
        "judgment",
        "environment",
        "patterns",
        "practice",
        "systems"
      ],
      "content_html": "<p>A handful of years ago, at 3 in the morning, a big fluffy orange cat mewled at our back door. I let him in. He was covered in burrs, his fur matted. &quot;What did you get into, Ruckus?&quot; I spent the better part of an hour cleaning him up, then went back to bed.</p>\n<p>Three days later, our son walked upstairs carrying the big fluffy orange cat. &quot;This isn&#39;t Ruckus,&quot; he said to my wife.</p>\n<p>&quot;Stop joking,&quot; she replied.</p>\n<p>&quot;This isn&#39;t Ruckus. This cat has white paws, but Ruckus is all orange.&quot; He paused. &quot;Plus Ruckus is neutered, and this cat has balls.&quot;</p>\n<p>I had let a stray doppelganger into the house. He&#39;d pretended to be Ruckus for three days. Or rather, we thought he&#39;d pretended — we have no actual visibility into the ways of cats. The next morning, Ruckus came waltzing in like he and Imposter had been pulling a country cat, city cat switcheroo all along.</p>\n<p>I took <span class=\"tooltip-hover\">Imposter<span class=\"tooltip-content\"><img src=\"/images/moss.jpg\" alt=\"Imposter cat\" /></span></span> to the vet to check if he was someone&#39;s missing pet. He wasn&#39;t. So he came home again.</p>\n<p>We live in an extremely rural area. Our cats are country cats and often go on walkabouts. Our nearest neighbor texted: her daughter had fallen in love with Imposter. Could she keep him?</p>\n<p>Gladly, we replied.</p>\n<p>Then we found Imposter on our couch.</p>\n<p>Never mind, the neighbor texted. The cat wasn&#39;t as friendly as they thought.</p>\n<p>He wasn&#39;t friendly to humans or cats as far as I could see. He never seemed to like it here. But he called this house home and never left.</p>\n<p>For years, he lived at our house. Co-existing with his twin and the three elder cats who&#39;d been here long before either of them arrived.</p>\n<p>A little more than a year ago, one of our daughters had a bad mouse problem. We jokingly suggested she could have a fluffy orange cat — we had a spare.</p>\n<p>She said yes.</p>\n<p>So Maurice — as Imposter had eventually been named — or Moss for short, went to live as a mouse catcher at our daughter&#39;s house. We expected a message asking us to come get him immediately.</p>\n<p>Instead: photos. Videos. A running commentary on how he&#39;s her perfect baby kitty boy and how much she loves him.</p>\n<p>A month after that, our son moved out, taking Ruckus with him. The house was freshly out of fluffy orange cats.</p>\n<p>Maurice had a lovely time being the only cat at our daughter&#39;s. He was a genuinely changed feline.</p>\n<p>Until the first of this month, when our daughter moved into a new place that won&#39;t allow cats. Could Maurice come back?</p>\n<p>We couldn&#39;t refuse.</p>\n<p>Moss&#39;s first five minutes back in the house: he picked a fight with not one, but two of the elder cats. The ones who&#39;d been here all along, the ones who remembered him.</p>\n<p>My greatest fear is that he was gone during the introduction of <a href=\"/s/bird\" target=\"_blank\" title=\"The bird who lived\">Valya</a>. There&#39;s no predicting how he&#39;ll react when confronting a starling in the house. All I can do is watch and not allow for conditions where something tragic could happen.</p>\n<p>His reintroduction has not been smooth. I find myself trying to fix it like a leadership problem.</p>\n<p>I can&#39;t. They&#39;re cats.</p>\n<p>But I can learn from it.</p>\n<p>Dealing with difficult environments. When to move the rock. When to let the system settle.</p>\n<p>Mostly what I&#39;m getting is a constant reminder to adjust my attitude.</p>\n<p>If I expect Moss to be a nuisance, I&#39;m hyper-aware of every little infraction. If I extend him the grace to acclimate to a new environment, I start to notice all the peaceful interactions he&#39;s had with the dogs. How he was actually hunting mice here, as opposed to the elder cats, who are either incredibly lazy or running a mouse protection racket.</p>\n<p>So I&#39;m being patient. Giving him time to adjust. Trying to find the balance between assumption of good intent and the reality that I have no basis for understanding cat motives. It&#39;s silly to even attempt to predict or control them.</p>\n<p>This is a situation where I need to be my best self and treat Moss reasonably, even if he&#39;s incapable of returning the favor.</p>\n<p>The cat who came back isn&#39;t the same cat who left. Neither is the house.</p>\n<p>I keep wanting to solve for harmony. To engineer the right conditions. To intervene at the right moments with the right approach.</p>\n<p>But some systems don&#39;t respond well to intervention. They respond to time, space, and the quality of attention you bring to them.</p>\n<p>The work isn&#39;t fixing Moss. The work is noticing when I&#39;m treating him like a problem to be solved instead of a creature adjusting to circumstances he didn&#39;t choose.</p>\n<p>The work is catching myself in the act of confirmation bias: looking for evidence that he&#39;s difficult, that this won&#39;t work, that we made a mistake taking him back.</p>\n<p>The work is choosing, again and again, to see what&#39;s actually happening instead of what I expect to happen.</p>\n<p>He&#39;s not friendly. He sometimes picks fights. He also hunts mice while the other cats nap. He also coexists peacefully with the dogs. He also chose this house as home when he could have gone anywhere.</p>\n<p>I don&#39;t know what motivates him. I don&#39;t need to.</p>\n<p>I just need to create the conditions where he can settle. And notice when I&#39;m the one making it harder.</p>\n<p>How often do I do this with people?</p>\n<p>Expect difficulty and find it everywhere. Interpret every action through the lens of past behavior. Forget that environments change people. Forget that people who struggled in one context might thrive in another.</p>\n<p>Forget that coming back is harder than leaving.</p>\n<p>Moss was a different cat at our daughter&#39;s house. Not because he changed his nature, but because the environment allowed different parts of his nature to emerge.</p>\n<p>Now he&#39;s back in a place that holds old patterns, old conflicts, old expectations. Of course he&#39;s struggling. Of course he&#39;s defensive.</p>\n<p>The question isn&#39;t whether he&#39;ll be the cat he was at our daughter&#39;s house. The question is whether I can create enough space for him to find his way in this environment.</p>\n<p>And whether I can do that simply because it&#39;s what&#39;s needed.</p>\n<p>I&#39;m learning to notice the moment when I shift from observation to judgment. When I move from &quot;Moss hissed at the other cat&quot; to &quot;Moss is the problem.&quot;</p>\n<p>That shift happens fast. Faster than I&#39;d like to admit.</p>\n<p>Maybe Moss does the same thing. Maybe he doesn&#39;t pick fights with the elder cats because he&#39;s aggressive, but because he&#39;s struggling with something he can&#39;t name or fix. Transferring his frustration onto available targets.</p>\n<p>I recognize that pattern. I do it too.</p>\n<p>The practice is catching it, just noticing: I&#39;m doing the thing again. I&#39;m making this harder than it needs to be.</p>\n<p>Then choosing differently.</p>\n<p>Extending grace I don&#39;t feel. Assuming good intent I have no evidence for. Creating space for adjustment I can&#39;t control.</p>\n<p>It&#39;s the only way forward that doesn&#39;t make me smaller.</p>\n<p>Maurice/Moss, né Imposter, is teaching me that we&#39;re all in constant flux. Hopefully growing toward something better, but always changing. Always adjusting to circumstances we didn&#39;t choose and systems we can&#39;t control.</p>\n<p>And that the change itself deserves grace. Not just in others, but in ourselves.</p>\n<p>I&#39;m struggling too, in my own way, with a system that changed while he was gone and changed again when he returned. I need time to adjust. Space to find my way. The same patience I&#39;m trying to extend to him.</p>\n<p>The same willingness to see what&#39;s actually happening instead of what I expect to happen.</p>\n<p>I can&#39;t fix this. I can only show up as my best self and let the system settle.</p>\n<p>That takes practice. More important than I realized. And necessary in ways I&#39;m still learning.</p>\n"
    },
    {
      "id": "https://lowdiatribe.net/reflection/2026-01-02-reset",
      "url": "https://lowdiatribe.net/reflection/2026-01-02-reset",
      "title": "Reset",
      "date_published": "2026-01-02T23:00:00.000Z",
      "summary": "",
      "tags": [
        "attention",
        "leadership",
        "perspective",
        "vulnerability",
        "practice"
      ],
      "content_html": "<p>The new year invites resolutions. Goals. Grand declarations of transformation.</p>\n<p>But what I need is reset.</p>\n<p>Not a new destination. A recalibration of what I notice. What I let dominate the frame.</p>\n<p>I don&#39;t remember exactly when I first read Slaughterhouse-Five. Somewhere around four decades ago. The thing that stuck wasn&#39;t the time travel or the war or even &quot;So it goes.&quot;</p>\n<p>It was the Tralfamadorians and their choice.</p>\n<p>They experience all of time at once. Every joy, every cruelty, every ordinary Thursday exists simultaneously. That could lead to paralysis, nihilism, or cold detachment. Instead, they do something quietly radical: they select where to place their attention. They linger in a moment worth keeping. They choose the zoo.</p>\n<p>That decision matters more than their perception of time. Omniscience isn&#39;t the power. Selection is.</p>\n<p>They don&#39;t deny that suffering exists. They don&#39;t pretend the war didn&#39;t happen or that death isn&#39;t real. They simply refuse to let those moments dominate the frame. Knowing all moments are equally permanent, they decide which ones deserve presence. The zoo isn&#39;t a prison; it&#39;s a posture.</p>\n<p>This is where the idea leaves science fiction and steps directly into everyday life.</p>\n<p>I used to believe reality is what happens to me. But I&#39;ve learned it&#39;s more often what I notice. What I return to. What I rehearse. What I train my attention to surface.</p>\n<p>Think about the color yellow.</p>\n<p>If you decide, consciously, to look for yellow, something odd happens. You don&#39;t buy more yellow things. The world doesn&#39;t repaint itself. But suddenly yellow is everywhere: signs, jackets, flowers, packaging, license plates. It feels like it has multiplied.</p>\n<p>It hasn&#39;t.\nYour attention has shifted.</p>\n<p>The moment you choose &quot;yellow matters,&quot; your perception aligns to reveal it. Not because you&#39;re imagining things, but because your mind is constantly filtering reality, and you&#39;ve changed the filter. What was always present becomes suddenly dense.</p>\n<p>This is the Tralfamadorian choice in miniature.</p>\n<p>They aren&#39;t changing the timeline. They&#39;re deciding where to stand inside it.</p>\n<p>This distinction is subtle, but it&#39;s everything. It&#39;s the difference between toxic positivity and grounded agency. Between denial and orientation. Between pretending pain doesn&#39;t exist and refusing to crown it as the only truth.</p>\n<p>Hardship appears whether we choose it or not. But whether it becomes the organizing principle of our attention — that&#39;s a different question.</p>\n<p>That choice compounds.</p>\n<p>What you attend to shapes what you interpret.\nWhat you interpret shapes what you reinforce.\nWhat you reinforce becomes culture — internal or shared.</p>\n<p>This happens everywhere. In leadership. In families. In teams. Quietly, daily, often unconsciously.</p>\n<p>If I, as a leader, only notice what&#39;s broken, the room fills with fracture. If I, as a parent, only notice what&#39;s missing, the household hums with lack. If I only notice where I fell short, the timeline collapses inward around regret.</p>\n<p>None of those perceptions are false. But they are incomplete.</p>\n<p>The Tralfamadorians offer a different discipline: acknowledge the whole, choose the center.</p>\n<p>This isn&#39;t passivity. It&#39;s responsibility at a different layer. The event may be fixed, but the narrative gravity around it isn&#39;t. Every moment of attention teaches the nervous system — yours and anyone watching — what deserves focus.</p>\n<p>Billy Pilgrim&#39;s repeated &quot;So it goes&quot; isn&#39;t about nothing mattering — it&#39;s about everything already existing. The phrase drains drama from death without draining meaning from life. It refuses escalation. It says: this moment is real, but it does not get to consume all others.</p>\n<p>That&#39;s not indifference. That&#39;s containment.</p>\n<p>And containment is a form of care.</p>\n<p>Choosing perspective doesn&#39;t mean lying to yourself. It means deciding which truths get to drive. Look for yellow, and the world gets brighter without changing a single molecule.</p>\n<p>This matters most in long arcs — careers, relationships, recovery, growth. I&#39;ve learned I can&#39;t endure those by white-knuckling the hardest moments. I live them by curating where I rest my gaze.</p>\n<p>The Tralfamadorians choose the zoo not because it&#39;s perfect, but because it&#39;s livable. Because it reminds them that even in a universe where everything is already written, attention is still an act of authorship.</p>\n<p>We all choose a perspective. The only question is whether we do it on purpose.</p>\n<p>Because whatever you train yourself to notice will begin to feel like the whole world.</p>\n<p>And that choice — quiet, repeated, unglamorous — is where agency actually lives.</p>\n<p>I&#39;m writing this on January 2nd, which means I&#39;m two days into a choice I made deliberately.</p>\n<p>Not a resolution. Not a goal. A reset of attention.</p>\n<p>I&#39;m choosing to notice what&#39;s working. To treat setbacks as information rather than indictment. To look for the yellow instead of cataloging the gray.</p>\n<p>This is harder than it sounds. My default filter has been tuned for years to surface problems, gaps, and risks. That&#39;s useful in some contexts. It keeps you sharp. But left unchecked, it becomes the only lens you have.</p>\n<p>The work doesn&#39;t change. I still have to do the things required to survive, to provide, to show up. The bills don&#39;t care about my attention. The responsibilities don&#39;t pause while I recalibrate.</p>\n<p>But I can direct my attention while doing that work. Notice the movement instead of staring at the weight. The progress, however small. The pace, however slow. Not because it makes the work easier, but because it makes the work sustainable.</p>\n<p>This isn&#39;t about ignoring the hardship. It&#39;s about refusing to let the hardship be the only story I tell myself while I&#39;m moving through it.</p>\n<p><a href=\"/s/stories\" target=\"_blank\" title=\"The stories we tell ourselves\">The stories we tell ourselves</a> become the superstitions we live by. If I tell myself I&#39;m always behind, I&#39;ll find evidence everywhere. If I tell myself nothing I do matters, I&#39;ll stop noticing when it does. The narrative becomes the filter. The filter becomes the world.</p>\n<p>I&#39;m trying to consciously build more positive superstitions. Not delusions. But patterns of attention that surface what&#39;s working, what&#39;s holding, what&#39;s moving forward. Stories grounded in truth but oriented toward possibility.</p>\n<p>I&#39;ve been practicing this for a while now, in small ways. I stopped watching horror movies, even my favorites. The dread lingered. The tension stayed in my body for days. I&#39;ve pulled back from music that feeds on angst — even bands I love, even songs that feel like home. Not forever. There&#39;s a time for catharsis, but it should be chosen, not constant. I&#39;d rather my default state be cultivating joy than exploring dread.</p>\n<p>These aren&#39;t grand gestures. They&#39;re tiny acts of curation. But they compound. What I let in shapes what I carry. And what I carry shapes what I notice.</p>\n<p>So I&#39;m choosing a different center.</p>\n<p>When I notice myself rehearsing a failure, I&#39;m going to acknowledge it once, extract the lesson, and redirect. When I catch myself scanning for what&#39;s broken, I&#39;m going to pause and name what&#39;s holding. When the narrative gravity pulls toward regret, I&#39;m going to ask: what else is true?</p>\n<p>This is the Tralfamadorian discipline: acknowledge the whole, choose the center.</p>\n<p>The new year is an arbitrary marker. The calendar doesn&#39;t care. But it&#39;s a useful fiction, a moment when we&#39;re culturally permitted to choose a different posture. I&#39;m taking it.</p>\n<p>Not because I believe everything will suddenly improve. But because I know that what I train myself to notice will begin to feel like the whole world. And I&#39;d rather live in a world dense with possibility than one defined by lack.</p>\n<p>The zoo isn&#39;t perfect. But it&#39;s livable. And livable, sustained over time, is how you build something worth keeping.</p>\n<p>So that&#39;s my reset. Quiet, unglamorous, repeated daily.</p>\n<p>Deciding where to stand inside the timeline I&#39;ve already got.</p>\n"
    },
    {
      "id": "https://lowdiatribe.net/reflection/2025-12-30-the-stories-we-tell-ourselves",
      "url": "https://lowdiatribe.net/reflection/2025-12-30-the-stories-we-tell-ourselves",
      "title": "The stories we tell ourselves",
      "date_published": "2025-12-30T23:00:00.000Z",
      "summary": "",
      "tags": [
        "leadership",
        "growth",
        "self-perception",
        "vulnerability"
      ],
      "content_html": "<p>Susie was home for winter break, helping in the kitchen for breakfast. She watched her mother carefully cut the sausages in half before putting them in the skillet to cook. &quot;Mama,&quot; asked Susie. &quot;Why do you always cut the sausages in two before you cook them?&quot; &quot;I don&#39;t know dear,&quot; replied her mother. &quot;It&#39;s the way my mama always cooked them. You&#39;ll have to ask Granny.&quot; Susie went to visit Granny and asked her, &quot;Granny, why do we always cut the sausages in two before we cook them?&quot; &quot;I don&#39;t really remember, darling,&quot; replied Granny. &quot;But I do remember it was the way my mama always made them. You&#39;d have to ask her.&quot; So Susie made the trip to visit her Great-grandmother, just so she could ask her the burning question. &quot;Great-Granny, why do we always cut our sausages in two before we cook them?&quot; &quot;Oh for heaven&#39;s sake!&quot; cried Great-Granny. &quot;Are you still using that itty bitty pan?&quot;</p>\n<p>There&#39;s another version of this story. Same journey, same questions, different punchline. When Susie reaches Granny, the answer is different: &quot;I don&#39;t really remember why, dear. But I do remember it was the way my mama always made them. I never thought to ask her. I guess we&#39;ll never know.&quot;</p>\n<p>In that far less funny version of the joke, the superstition is canonized — now it&#39;s dogma.</p>\n<p>Superstitions are the stories we tell ourselves — either to make sense of the world or to protect us from danger. Sometimes they&#39;re inherited, passed down without question. Sometimes we construct them ourselves, building elaborate narratives to explain what we don&#39;t understand or to guard against what we fear.</p>\n<p>Not all superstitions are bad. Walking under a ladder is considered bad luck because something might actually fall on you. Judaic dietary laws kept nomadic tribes alive in the desert. Many superstitions encode practical wisdom that worked even when we didn&#39;t understand why.</p>\n<p>The problem isn&#39;t the superstition itself. It&#39;s when we stop questioning whether it still serves us — or whether it ever did. Stevie Wonder maybe put it best: &quot;When you believe in things that you don&#39;t understand and you suffer. <span class=\"tooltip-text\" title=\"One of my all-time favorite songs. Golden vocals, that funkadelic Moog bassline and iconic clavinet riff, plus kickass horns. Hits all my auditory sweet spots.\">Superstition</span> ain&#39;t the way.&quot;</p>\n<p>We inherit superstitions without questioning them. Not always the kind about black cats or broken mirrors — the ones we build about ourselves. The stories we tell about how we&#39;re perceived, the patterns we&#39;re convinced others see in us, the flaws we&#39;re certain everyone notices.</p>\n<p>These aren&#39;t based on evidence. They&#39;re based on fear.</p>\n<p>I&#39;ve watched this play out in myself and in every leader I&#39;ve worked with. We construct elaborate narratives about our weaknesses, our gaps, the ways we don&#39;t measure up. We become convinced that everyone sees what we see when we look in the mirror at 3am.</p>\n<p>But here&#39;s what I&#39;ve learned: the gap between how we think we&#39;re perceived and how we&#39;re actually received is almost always wider than we imagine.</p>\n<p>The superstition goes like this: I notice my hesitation in that meeting, so everyone must see me as uncertain. I stumble over my words in that presentation, so they must think I&#39;m unprepared. I don&#39;t have all the answers, so they must question whether I belong here.</p>\n<p>We take our internal experience — the doubt, the second-guessing, the imposter syndrome — and project it outward as fact. We assume our anxiety is visible, our uncertainty obvious, our struggles transparent.</p>\n<p>But most of the time? People aren&#39;t seeing what we think they&#39;re seeing.</p>\n<p>Later I learn that my hesitation was read as thoughtfulness. That my stumbling over words came across as genuine enthusiasm. That asking questions signaled curiosity and growth, not ignorance. The flaws I was certain disqualified me were barely noticed — or noticed and interpreted as something else entirely.</p>\n<p>I&#39;ve had conversations where someone apologized for being scattered, and I had no idea what they were talking about. Where a leader confessed they felt like a fraud, and I&#39;d been struck by the authenticity of their message. Where someone worried they talked too much, and I&#39;d been grateful for their willingness to open up and share.</p>\n<p>The superstition breaks down when you realize: everyone is too busy managing their own internal narrative to scrutinize yours.</p>\n<p>This isn&#39;t about toxic positivity or pretending perception doesn&#39;t matter. It matters deeply. But the perception we&#39;re managing is often imaginary — tilting at windmills we&#39;ve conjured from our own fears rather than anything grounded in how others actually experience us.</p>\n<p>I think the real work isn&#39;t fixing the flaws we&#39;re convinced everyone sees. It&#39;s questioning whether those flaws are as visible — or as damning — as we&#39;ve decided they are.</p>\n<p>I&#39;ve started asking myself: what evidence do I actually have for this belief? Not the story I&#39;ve constructed, but the data. The feedback. The patterns over time.</p>\n<p>Usually, the evidence is thin. Or contradictory. Or entirely absent.</p>\n<p>What I find instead is that people remember different things than I do. They recall the moment I asked a clarifying question, not the moment I felt lost. They remember the time I admitted I didn&#39;t know, not as weakness but as honesty. They notice the consistency, not the occasional stumble.</p>\n<p>The superstition we build about ourselves is almost always harsher than the reality.</p>\n<p>And here&#39;s the paradox: the more we try to hide what we think everyone sees, the more energy we waste on performance. The more we manage the imaginary perception, the less present we are for the actual relationship.</p>\n<p>I&#39;ve learned that vulnerability isn&#39;t about exposing every doubt or insecurity. It&#39;s about releasing the superstition that everyone is already seeing them anyway.</p>\n<p>When I stop performing confidence to cover perceived weakness, I can be present. When I stop managing the narrative I think others have about me, I can actually listen to what they&#39;re saying. When I let go of the superstition, there&#39;s space for something more honest.</p>\n<p>This doesn&#39;t mean perception is irrelevant. It means the perception that matters most is the one built over time through consistency, not the one we&#39;re frantically trying to control in each individual moment.</p>\n<p>People don&#39;t remember your hesitation in one meeting. They remember whether you showed up, whether you listened, whether you followed through. They remember the pattern, not the performance.</p>\n<p>The superstition tells us we need to be flawless to be trusted. But trust isn&#39;t built on perfection — it&#39;s built on reliability. On being the same person in different contexts. On admitting when you don&#39;t know instead of pretending you do.</p>\n<p>I&#39;ve found that the leaders I trust most aren&#39;t the ones who never stumble. They&#39;re the ones who stumble and keep going. Who admit uncertainty without making it everyone else&#39;s problem. Who are human enough to be real and steady enough to be relied on.</p>\n<p>The gap between self-perception and how we&#39;re actually received isn&#39;t a problem to solve. It&#39;s a reminder that we&#39;re almost always harder on ourselves than anyone else is.</p>\n<p>And maybe the most radical thing we can do is stop believing our own superstitions — and start trusting that people see us more clearly, and more kindly, than we see ourselves.</p>\n<p>I&#39;m curious what superstitions my grandchildren will inherit from me. Right now, they know you&#39;re supposed to wash your hands before playing video games to keep the Takis dust off the controllers. Practical wisdom, clearly explained.</p>\n<p>But fifty years from now? When controllers are neural interfaces or whatever comes next? I wonder if they&#39;ll still be washing their hands before gaming, unable to remember why, just knowing it&#39;s what their Great-great-grandfather always insisted on. Perhaps it will have evolved into a performance-enhancing ritual. &quot;It takes clean hands to win!&quot;</p>\n<p>Maybe that&#39;s not the worst superstition to pass down.</p>\n"
    },
    {
      "id": "https://lowdiatribe.net/reflection/2025-12-26-oscillate-wildly",
      "url": "https://lowdiatribe.net/reflection/2025-12-26-oscillate-wildly",
      "title": "Oscillate wildly",
      "date_published": "2025-12-26T23:00:00.000Z",
      "summary": "",
      "tags": [
        "leadership",
        "growth",
        "systems",
        "patience"
      ],
      "content_html": "<p>You know the shower phenomenon.</p>\n<p>The water&#39;s too cold, so you turn the knob toward hot. Nothing happens immediately, so you turn it more. Still cold. You turn it again. Then suddenly — scalding. You overcorrect toward cold. Now it&#39;s freezing. You adjust back. Too hot again.</p>\n<p>You&#39;re not fixing the problem. You&#39;re adding complexity through oscillation.</p>\n<p>The issue isn&#39;t the system. It&#39;s the lag between input and feedback. The water takes time to travel through the pipes, to register the temperature change, to reach you. But you&#39;re reacting to what you feel right now, not accounting for what&#39;s already in motion.</p>\n<p>It feels like we&#39;re dialing in on the optimal solution. But each adjustment throws the system further out of alignment.</p>\n<p>I&#39;ve watched this same pattern play out in leadership. In teams. In organizational change. Someone identifies a problem and makes an adjustment. When results don&#39;t appear immediately, they adjust again. And again. Each correction compounding the last, until the system is oscillating wildly between extremes.</p>\n<p>The team isn&#39;t responding fast enough, so we add more check-ins. Still not seeing results, so we add more structure. Now people feel micromanaged, so we pull back entirely. Now there&#39;s no accountability. We swing back the other way.</p>\n<p>We&#39;re not managing the system. We&#39;re destabilizing it.</p>\n<p>The problem isn&#39;t the adjustments themselves. It&#39;s the failure to account for lag. Systems have inertia. Changes take time to propagate. Feedback loops aren&#39;t instantaneous.</p>\n<p>When you adjust before the previous change has had time to work through the system, you&#39;re not responding to reality — you&#39;re responding to the absence of immediate gratification.</p>\n<p>I&#39;ve learned that the hardest part of leadership isn&#39;t making adjustments. It&#39;s waiting to see if they work.</p>\n<p>That pause — between action and reaction — is where most leaders lose their nerve. The discomfort of not knowing whether the change is working. The pressure to do something, anything, to show progress. The fear that waiting means accepting failure.</p>\n<p>But sometimes the most important thing you can do is nothing. Let the system stabilize. Let the change propagate. Give the feedback loop time to complete.</p>\n<p>This doesn&#39;t mean ignoring problems or avoiding course corrections. It means understanding the difference between a system that needs adjustment and a system that needs time.</p>\n<p>I fall into this trap more often than I&#39;d like to admit. I find something that works — a new practice, a better approach, a framework that clicks — and I embrace it wholeheartedly. If a little context helps, surely more context is better. I shift my focus to full-time information accumulation. Without realizing it my calendar becomes a solid wall of context-gathering missions, with no time to process any of it.</p>\n<p>Moderation would win the day. But moderation requires restraint I don&#39;t always have when I think something will work.</p>\n<p>I wrote recently about <a href=\"/s/present\" target=\"_blank\" title=\"Present for the immediate future\">shrinking scope as a survival tactic</a>. Focus on what&#39;s immediate. Control what you can control. It was good advice then, and I needed it. But I took it too far. I narrowed my view so completely to the immediate that I stopped seeing what was coming next. The slightly-after-immediate consequences blindsided me because I&#39;d trained myself to look only at right now.</p>\n<p>This is the oscillation in my own thinking. Survival mode says focus narrow. So I focus so narrow I can&#39;t see the edges. Then I get hit by something just outside my field of vision, and I overcorrect — try to see everything, plan for every contingency, account for every possibility. Mired in analysis paralysis.</p>\n<p>The question I&#39;m learning to ask isn&#39;t &quot;what should I do?&quot; but &quot;is this a new problem, or am I just seeing the lag from the last adjustment?&quot;</p>\n<p>Usually, it&#39;s the lag.</p>\n<p>The shower eventually reaches the right temperature. Not because you kept turning the knob, but because you stopped. You found the setting and waited for the system to catch up.</p>\n<p>The challenge is staying patient enough within the system to learn its patterns. In my house, the left knob open all the way with the right knob open just a bit gives me a good starting point. I know from experience it takes about six or seven minutes for the water to stabilize at that setting, and I can fine tune from there. That knowledge only came from not panicking during the lag.</p>\n<p>The same is true in leadership. The adjustment you made last week, last month, last quarter — it&#39;s still working its way through the pipes. The feedback you&#39;re getting now isn&#39;t about whether the change was right. It&#39;s about whether you gave it time to work.</p>\n<p>Oscillation feels like responsiveness. It feels like you&#39;re engaged, attentive, adaptive. But what it actually creates is harmonic dissonance. People can&#39;t find their footing when the ground keeps shifting. Teams can&#39;t build momentum when the direction keeps changing.</p>\n<p>Stability isn&#39;t the same as stagnation. It&#39;s the foundation that allows change to take root.</p>\n<p>The leaders I&#39;ve followed who create the most sustainable change aren&#39;t the ones who adjust constantly. They&#39;re the ones who adjust deliberately, then hold steady long enough to see what happens.</p>\n<p>They account for lag. They resist the urge to react to every fluctuation. They understand that systems need time to stabilize before you can know whether the adjustment worked.</p>\n<p>This requires a different kind of discipline. Not the discipline of action, but the discipline of patience. The willingness to sit with discomfort. To trust that the change is working even when you can&#39;t see it yet.</p>\n<p>The shower will get hot. The system will stabilize. But only when you stop turning the knob.</p>\n<p>Maybe the most important adjustment we can make is learning when not to adjust at all.</p>\n"
    },
    {
      "id": "https://lowdiatribe.net/reflection/2025-12-23-present-for-the-immediate-future",
      "url": "https://lowdiatribe.net/reflection/2025-12-23-present-for-the-immediate-future",
      "title": "Present for the immediate future",
      "date_published": "2025-12-23T23:00:00.000Z",
      "summary": "When you're struggling to feel motivated, you might be confusing inspiration with motivation. A reflection on shrinking scope as survival strategy, the triple meaning of present, and why sometimes all you need is the right hat to make motion feel less like survival and more like living.",
      "tags": [
        "leadership",
        "generosity",
        "connection"
      ],
      "content_html": "<p>In the Northern Hemisphere we&#39;re currently tilted away from the sun, creating a winter wonderland or frozen hellscape, depending on your outlook. In the midwest, the Winter Solstice has about six hours less daylight than on Summer Solstice. The urge to hibernate is real.</p>\n<p>The cluster of human religions holidays during this time makes sense – celebrating the return of the sun in all its forms is kind of a big deal – but also carries this weight of expectation: be generous, be present, show up for people. And I find myself struggling with all three. Not because I don&#39;t care. Because the scope of everything feels too large, and motivation feels like something that happens to other people.</p>\n<p>So I&#39;ve been shrinking my focus. Not as strategy. As survival.</p>\n<p>What can I handle right now? What needs attention in the next hour? The next day? The immediate future becomes the only future I can manage.</p>\n<p>And somewhere in that shrinking, I realized something: this is motivation. Not the feeling of wanting to do something. The act of doing it anyway.</p>\n<h2 id=\"the-three-meanings-of-present\">The three meanings of present</h2>\n<p>Present as gift. Present as now. Present as showing up.</p>\n<p>I&#39;ve been treating these as separate things. The gift you give. The moment you inhabit. The way you appear for others. But they&#39;re the same thing, just viewed from different angles.</p>\n<p>When you can&#39;t handle the big picture, you give what you can in the moment you&#39;re in. That&#39;s all three at once.</p>\n<p>The gift becomes smaller. The now becomes shorter. The showing up becomes more focused. But it&#39;s still all three.</p>\n<h2 id=\"when-scope-shrinks\">When scope shrinks</h2>\n<p>I used to think shrinking my scope was a failure. A sign I wasn&#39;t handling things well. That real leaders maintain the big picture even when it&#39;s hard.</p>\n<p>But maintaining a scope you can&#39;t actually hold doesn&#39;t make you a better leader. It makes you absent while pretending to be present.</p>\n<p>Shrinking scope isn&#39;t retreat. It&#39;s honesty about what you can actually carry right now.</p>\n<p>At Big Book company, I had to walk the balance between working steadily towards long-term goals while maneuvering through short-term obstacles. In the job market, that framework doesn&#39;t work. There is no direct correlation between end goal of a new role and the actual number of resumes sent out. It&#39;s more like navigating a Zelda dungeon or the Mario Underworld. There&#39;s a path, somewhere, and through a combination of discovering what works and what doesn&#39;t, eventually you find it.</p>\n<p>The old framework required maintaining both immediate and long-term vision simultaneously. The new reality requires focusing on what&#39;s immediately in front of me because the path forward isn&#39;t visible yet. That&#39;s not failure of vision. That&#39;s adaptation to different terrain.</p>\n<h2 id=\"motivation-as-action-not-feeling\">Motivation as action, not feeling</h2>\n<p>I caught myself saying it out loud: &quot;I&#39;m not feeling motivated to do anything.&quot;</p>\n<p>Then I looked at what I was actually doing. Researching jobs. Working through house projects. Playing elf to plan a festive family celebration.</p>\n<p>I wasn&#39;t lacking motivation. I was lacking inspiration.</p>\n<p>The motivation was there in the doing. What I missed was the feeling of wanting to do it. The spark. The enthusiasm. The sense that any of it mattered beyond the immediate need to get it done.</p>\n<p>We talk about motivation like it&#39;s a prerequisite. Like you need to feel motivated before you can act.</p>\n<p>But that&#39;s backwards.</p>\n<p>Motivation isn&#39;t what you feel before you do something. It&#39;s what you call it after you&#39;ve done it anyway.</p>\n<p>Inspiration is the feeling. Motivation is the motion. You can have one without the other.</p>\n<p>I don&#39;t feel inspired to show up for the immediate needs. I just show up. And in the showing up, there&#39;s a kind of motion. Not inspiration. Not enthusiasm. Just forward movement.</p>\n<p>That&#39;s enough for now .</p>\n<p>My wife gave me a brand new Carhartt Santa hat as an early gift. Suddenly the elf duties carried a little more joy. Not because the hat changed what needed doing. Because it changed how I felt.</p>\n<p>Sometimes all you need is the right hat.</p>\n<p>That&#39;s what inspiration can do when it sparks. It doesn&#39;t create the motivation — the motion was already there. It just makes the motion feel less like survival and more like living.</p>\n<h2 id=\"the-grace-to-do-more\">The grace to do more</h2>\n<p>Here&#39;s what I&#39;m learning: focusing on immediate needs is necessary. But it can&#39;t be the only thing.</p>\n<p>If I only ever handle what&#39;s immediately in front of me, I lose the ability to see beyond it. The immediate future becomes the only future. And that&#39;s not sustainable.</p>\n<p>I need to give myself permission to do something outside the immediate needs. Not because it&#39;s urgent. Because it matters.</p>\n<p>Write a story. Draw. Skate. Build one of the LEGO sets from my backlog. Spend time with the grandchildren when their parents don&#39;t need someone to watch them. Find the things to keep from collapsing my world too far.</p>\n<p>Not as escape from the immediate. As reminder that there&#39;s more.</p>\n<h2 id=\"present-for-whats-coming\">Present for what&#39;s coming</h2>\n<p>The immediate future is still future.</p>\n<p>When I focus on what&#39;s right in front of me, I&#39;m not just handling now. I&#39;m preparing for what comes next. The immediate needs, met now, create space for what follows.</p>\n<p>That&#39;s the gift. Not just what I give in this moment, but what this moment makes possible.</p>\n<p>That&#39;s the presence. Not just being here now, but being here in a way that honors what&#39;s coming.</p>\n<p>That&#39;s the showing up. Not just appearing, but appearing in a way that matters.</p>\n<h2 id=\"what-this-means-for-leading\">What this means for leading</h2>\n<p>Leadership isn&#39;t always about the big vision. Sometimes it&#39;s about the next right thing.</p>\n<p>The person who needs a response. The decision that can&#39;t wait. The small thing that matters to someone.</p>\n<p>You don&#39;t need to feel inspired to handle those. You just need to handle them.</p>\n<p>And in handling them, you&#39;re leading. Not because you&#39;re motivated. Because you&#39;re present.</p>\n<p>The scope shrinks. The focus tightens. The immediate becomes the only thing you can see.</p>\n<p>That&#39;s not failure. That&#39;s honesty.</p>\n<p>And somewhere in that honesty, there&#39;s room for grace. To do something beyond the immediate. To remember there&#39;s more than what&#39;s pressing.</p>\n<p>Not because you have to. Because you can.</p>\n<hr>\n<p><em>Motivation isn&#39;t the feeling that precedes action. It&#39;s the name we give to action that happened anyway.</em></p>\n"
    },
    {
      "id": "https://lowdiatribe.net/reflection/2025-12-19-the-system-isnt-broken",
      "url": "https://lowdiatribe.net/reflection/2025-12-19-the-system-isnt-broken",
      "title": "The system isn't broken",
      "date_published": "2025-12-19T23:00:00.000Z",
      "summary": "When the Eldridge City Council voted to close our community's skating rink, people said \"the system is broken.\" But what if the system is working exactly as designed? A reflection on fear-based governance, selective liability, and our responsibility to redesign systems that optimize for the wrong things.",
      "tags": [
        "leadership",
        "systems",
        "community",
        "activism"
      ],
      "content_html": "<p>I&#39;m stuck on what it means when a system works exactly as designed but produces outcomes we can&#39;t accept.</p>\n<p>The <a href=\"/eldridge-council-meeting.html\" target=\"_blank\" title=\"Watch the full council meeting here.\">Eldridge City Council voted 3-2</a> this week to discontinue the operation of Eldridge Community Center and Skatepark. Dozens of citizens spoke at the meeting — some from Eldridge, many from the surrounding area. The community asked for a referendum. The council voted that down 3-2 and moved forward with the vote for closure.</p>\n<p>This rink holds tremendous personal meaning for me. It&#39;s been our family&#39;s skating home for decades. All seven of our children learned to skate there. We taught our six grandchildren to skate there. It&#39;s where my wife and I had our skate-themed wedding. It&#39;s where I re-learned to skate as an adult. The QC Cuttaz have spent hundreds of hours there since we moved to the rink in 2022. I&#39;ve only been refereeing roller derby for a little more than a season, but the Eldridge Community Center and Skatepark has been home to the Quad City Rollers for twenty years.</p>\n<p>The community response has been massive. People are showing up. People are speaking. People are organizing.</p>\n<p>And I keep hearing the same phrase: &quot;The system is broken.&quot;</p>\n<p>I don&#39;t think that&#39;s right. The system is working perfectly — doing exactly what it was designed to do. Allow a small group to make decisions for everyone else. Prioritize financial metrics over community value. Treat public resources like business assets.</p>\n<p>The system isn&#39;t broken. It&#39;s just designed to optimize for the wrong things.</p>\n<h2 id=\"listening-to-the-council\">Listening to the council</h2>\n<p>I&#39;ve been sitting with what the five council members said.</p>\n<p>The first was clear: &quot;The facility does not fit the definition of a community center, it&#39;s a business. A city should not run a business.&quot; Closure was the answer.</p>\n<p>The second asked about alternatives and motioned to move the issue to referendum. Let the people decide.</p>\n<p>The third spoke of fiscal responsibility, but noted the costs were within acceptable margins for what he would consider a public space.</p>\n<p>The fourth spoke of his love and history with the rink, but the liability concerns kept him up at night. &quot;One big lawsuit could bankrupt this city.&quot; The difficulty of getting insurance. The exposure.</p>\n<p>The last also spoke of his connection with the rink, but kept returning to other things that needed &quot;fixing&quot; as higher priorities.</p>\n<p>Three voted to close. Two voted to keep exploring.</p>\n<p>I don&#39;t question their sincerity. I question the framework they&#39;re working within.</p>\n<h2 id=\"the-false-binary\">The false binary</h2>\n<p>Here&#39;s what I agree with: cities shouldn&#39;t be running businesses.</p>\n<p>Here&#39;s what I can&#39;t accept: that closure is the only alternative.</p>\n<p>The conversation keeps getting framed as binary. Either the city keeps running it the way it always has — like a business that loses money — or shuts it down. But that&#39;s not a failure of options. That&#39;s a failure of imagination.</p>\n<p>Why are we treating a community resource like a business in the first place? Community ownership? Non-profit partnership? Cooperative management? Public-private collaboration? County, state, or federal funding? I don&#39;t know if any of those would work. But I know they weren&#39;t seriously explored.</p>\n<p>If the Community Center and Skatepark doesn&#39;t fit the definition of a &quot;community center&quot;, why? What&#39;s preventing it from being run as a community center? What&#39;s forcing the need to run it like a business? The same authority that defined the term would also have been responsible for how the facility is run.</p>\n<p>When the only tool you have is a spreadsheet, every problem looks like a budget line to cut.</p>\n<h2 id=\"when-fear-becomes-selective\">When fear becomes selective</h2>\n<p>The liability argument troubles me most.</p>\n<p>I understand the fear. One lawsuit could bankrupt a small city. Insurance is expensive and hard to get. The exposure is real.</p>\n<p>But every public space carries liability. Every park, every playground, every community pool. We manage the risk. We get insurance. We implement safety protocols. We accept that serving the public means accepting some level of exposure.</p>\n<p>Eldridge built new baseball diamonds and pickleball courts. No mention of liability there.</p>\n<p>So liability isn&#39;t the principle. It&#39;s the excuse. The real question: which communities and which activities are worth the risk?</p>\n<p>Here&#39;s what really troubles me: we&#39;re making decisions based on fear of liability, when that liability itself is a manufactured concept that&#39;s been inflated beyond reason. The liability exists because we&#39;ve privatized healthcare. If someone gets hurt, the medical bills can be so astronomical that a lawsuit becomes the only way to cover them.</p>\n<p>We&#39;ve created a system where the cost of an injury is so high that the fear of that cost drives us to eliminate the activity itself. Then we point to that fear as if it&#39;s natural law, rather than recognizing it as a design choice we made.</p>\n<p>The liability argument measures one kind of risk while ignoring another. And it applies that incomplete measure selectively, to the communities with the least power to push back.</p>\n<h2 id=\"when-representation-means-silence\">When representation means silence</h2>\n<p>Dozens of citizens spoke. One council member motioned for referendum. Two voted to let the people decide. Three voted to move forward with closure.</p>\n<p>That&#39;s representation in the technical sense: elected officials making decisions on behalf of constituents. But it&#39;s not representation in the meaningful sense: giving people voice in decisions that shape their lives.</p>\n<p>A system that defaults to closure also silences the community asking for options. The community had their say, but no apparent influence on the outcome.</p>\n<p>This is what it looks like when a system prioritizes process over people, authority over voice, efficiency over engagement.</p>\n<h2 id=\"what-the-young-ones-see\">What the young ones see</h2>\n<p>The most hopeful thing I&#39;ve witnessed is the outpouring of activism from younger generations.</p>\n<p>They showed up to the council meeting. They spoke. Now they&#39;re organizing. Pushing petitions. Refusing to accept &quot;this is how it&#39;s done&quot; as an answer.</p>\n<p>They understand something easy to forget: systems are human-made. Every rule, every process, every structure — someone designed it, someone implemented it, someone maintains it. Which means someone can change it.</p>\n<p>&quot;The way we&#39;ve always done it&quot; isn&#39;t natural law. It&#39;s not physics. It&#39;s not inevitable. It&#39;s just the way we&#39;ve chosen to do it so far.</p>\n<p>The youth aren&#39;t asking the system to work better. They&#39;re asking why we accept this system at all. They&#39;re questioning the design, not just the execution. They&#39;re imagining what the council couldn&#39;t.</p>\n<p>That&#39;s the signal I&#39;m listening for.</p>\n<h2 id=\"designing-for-what-matters\">Designing for what matters</h2>\n<p>I&#39;ve spent my career creating environments where talented people do their best work. That&#39;s always been about lowering barriers, questioning inherited processes, designing systems that serve people instead of the other way around.</p>\n<p>This is the same work at a different scale.</p>\n<p>The Eldridge City Council aren&#39;t the bad guys. The system isn&#39;t inherently malicious. But the design is wrong. It optimizes for financial metrics over community value. It measures outcomes in dollars instead of lives touched. It centers the voices of those in power instead of those most affected.</p>\n<p>A skate rink that has served thousands of people over three decades isn&#39;t a failed business. It&#39;s a successful community resource. Measuring it by profit and loss instead of skills learned and relationships built — that&#39;s a design flaw, not a financial reality.</p>\n<p>The work isn&#39;t to fix the system. The work is to redesign it.</p>\n<p>What would a system designed for community voice look like? One that measures long-term community value instead of short-term fiscal metrics? One that explores alternatives instead of defaulting to closure?</p>\n<p>I don&#39;t have complete answers. But I know we won&#39;t find them by accepting the current design as inevitable.</p>\n<h2 id=\"where-i-stand\">Where I stand</h2>\n<p>I don&#39;t live in Eldridge. My voice doesn&#39;t carry the same weight as those who do. I can speak, but I can&#39;t vote in their elections. The system prioritizes residents over users.</p>\n<p>If I lived there, I would run for council on this issue. Not because I have all the answers, but because the right questions aren&#39;t being asked. Because alternatives aren&#39;t being explored. Because the community deserves voice in decisions that shape their lives.</p>\n<p>But I don&#39;t live there. So I&#39;m doing what I can: speaking out, supporting those who are organizing, refusing to accept that this outcome was inevitable. Asking the questions that should have been asked.</p>\n<p>This is what it means to work within a flawed system while trying to change it. You use what voice you have, even when it&#39;s not as loud as you&#39;d like. You support those with more leverage. You keep asking the questions that need asking.</p>\n<p>And you don&#39;t shy away from saying what needs to be said.</p>\n<h2 id=\"what-this-is-really-about\">What this is really about</h2>\n<p>This isn&#39;t just about a skate rink or a home for roller derby or a place where my entire family learned to skate.</p>\n<p>It&#39;s about whether systems serve people, or people serve systems.</p>\n<p>It&#39;s about whether &quot;representation&quot; means elected officials making decisions in a vacuum, or communities having voice in decisions that shape their lives.</p>\n<p>It&#39;s about whether we measure value by profit and loss, or by lives touched and community built.</p>\n<p>It&#39;s about whether we make decisions based on fear, or on possibility.</p>\n<p>It&#39;s about whether we accept inherited design as inevitable, or recognize our responsibility to refine what we&#39;ve been given.</p>\n<p>The system isn&#39;t broken. It&#39;s working exactly as designed.</p>\n<p>It is our imperative to craft it better.</p>\n<hr>\n<p><em>Systems are human-made, human-imposed, and human-editable. There is always a solution — just not always one that looks like &quot;the way we&#39;ve always done it.&quot;</em></p>\n"
    },
    {
      "id": "https://lowdiatribe.net/reflection/2025-12-16-carrying-eccentricities",
      "url": "https://lowdiatribe.net/reflection/2025-12-16-carrying-eccentricities",
      "title": "Carrying eccentricities",
      "date_published": "2025-12-16T23:00:00.000Z",
      "summary": "At eighteen, a board member questioned my hire. Doc defended it: 'There's a direct correlation between eccentricities tolerated and talent.' Explores the exchange rate of authenticity, the weight that skill must carry, the danger of mistaking correlation for causation, and the gap between earning capability and feeling like you've earned it. Being yourself isn't free — it's a cost your skill has to carry.",
      "tags": [
        "leadership",
        "authenticity",
        "skill",
        "identity"
      ],
      "content_html": "<p>The board member looked me up and down — eighteen, hair shaved on the sides and back with the top grown out, wearing a suit three sizes too big and combat boots to a fancy dress party — and questioned the hire.</p>\n<p>In my mind, I was projecting David Byrne energy. In reality, I probably looked more like Beaker from the Muppet Show.</p>\n<p>Either way, I stuck out amongst the crowd of donors and board members at the gala celebrating the opening of the Science Center&#39;s new building.</p>\n<p>Doc didn&#39;t hesitate: &quot;There&#39;s a direct correlation between the amount of eccentricities tolerated and the talent of an individual. As you can see, this young man is very talented.&quot;</p>\n<p>I&#39;d volunteered as an Explainer at the interactive science museum through my last two years of high school. That&#39;s what they called us folk who staffed the floor and explained the exhibits — Explainers. When they received a major grant and moved into the new space, they had budget to not only pay the Explainers, but also hire a full-time Explainer Coordinator. They&#39;d chosen me. My first job out of high school was hiring and supervising all the part-time Explainers.</p>\n<p>Doc was a distinguished scientist from Fermilab, and the interactive center was his passion project. The board was split between scientists from Fermi or Argonne and prominent local business and political leaders. The scientists knew how to read signal through static. This board member was not a scientist. He saw a post-punk teenager who didn&#39;t look the part. Doc saw someone who&#39;d shown up every weekend, learned the exhibits cold, and could explain complex physics to eight-year-olds without talking down to them.</p>\n<p>What Doc understood — what I was just beginning to learn — was that eccentricity isn&#39;t tolerated despite talent. It&#39;s a weight that talent has to carry.</p>\n<h2 id=\"the-exchange-rate\">The exchange rate</h2>\n<p>Growing up in the post-punk era, I was the typical teenage rebel: new wave and industrial music, anti-establishment sentiment, the whole aesthetic. I thought rebellion was the point. Doc taught me something different: being yourself isn&#39;t rebellion. It&#39;s a cost.</p>\n<p>Your skill has to be strong enough to carry the extra load.</p>\n<p>The exchange rate is continuous. You don&#39;t earn the right to be yourself once and keep it forever. Every new context, every new role, every new team resets the equation. You have to prove the capability before you can spend it on authenticity.</p>\n<h2 id=\"what-skill-buys-you\">What skill buys you</h2>\n<p>I learned this viscerally that summer. I was fresh out of high school, managing college students home for break and volunteers with advanced degrees. My appearance was a constant negotiation. Every decision I made, every schedule I set, every conflict I mediated — it all had to be good enough to justify the fact that I didn&#39;t look like what they expected a coordinator to look like.</p>\n<p>The skill bought me permission. But only just enough.</p>\n<p>If I&#39;d been mediocre at the job, my appearance would have been the explanation for why. If I&#39;d been merely competent, it would have been a distraction. I had to be good enough that my eccentricities became irrelevant — or better yet, reframed as evidence of the same independent thinking that made me effective.</p>\n<p>This is the reality of earned eccentricity: you can&#39;t just be as good as everyone else. You have to be better. The weight of being different requires extra strength to carry.</p>\n<p>It&#39;s not fair. But it&#39;s the physics of the situation.</p>\n<h2 id=\"the-danger-of-the-correlation\">The danger of the correlation</h2>\n<p>Doc&#39;s insight was profound, but it came with a hidden danger: if there&#39;s a correlation between eccentricity and talent, it&#39;s easy to mistake which direction the causation runs.</p>\n<p>Eccentricity doesn&#39;t create talent. Talent creates the conditions where eccentricity can survive.</p>\n<p>I&#39;ve watched people get this backwards. They see successful people who are authentically themselves — who dress differently, think differently, work differently — and conclude that the difference is the source of the success. So they adopt the surface markers without building the underlying capability. They pick up weight they can&#39;t carry.</p>\n<p>The result is predictable: they struggle, they fail, and everyone around them blames the eccentricity. Which reinforces the belief that conformity is safer. Which makes it harder for people with genuine capability to take the risk of being themselves.</p>\n<h2 id=\"the-internal-exchange-rate\">The internal exchange rate</h2>\n<p>But there&#39;s another gap that&#39;s harder to see: the gap between having earned something and feeling like you&#39;ve earned it.</p>\n<p>Doc saw capability in me that I was still learning to see in myself. The skill was there — I&#39;d proven it weekend after weekend, exhibit after exhibit. But the feeling lagged behind the reality.</p>\n<p>This is the internal version of the exchange rate. It&#39;s not just about whether others accept your eccentricities. It&#39;s about whether you believe you&#39;ve earned the right to carry them.</p>\n<p>I&#39;ve watched this play out in two directions, and both are dangerous.</p>\n<p>Some people have the capability but can&#39;t feel it. They&#39;ve earned the weight but don&#39;t believe they&#39;re strong enough to carry it. So they either hide who they are or exhaust themselves trying to prove they deserve to be there. The skill is real, but the confidence lags so far behind that they can&#39;t access what they&#39;ve actually built.</p>\n<p>Others feel capable but haven&#39;t built the foundation. They pick up weight they can&#39;t carry because they don&#39;t yet know enough to recognize how heavy it is. The confidence is real, but the skill lags so far behind that they mistake the feeling for the fact.</p>\n<p>Both gaps are about misalignment between perception and reality. But they fail in opposite directions.</p>\n<p>When you have the capability but can&#39;t feel it, the gap doesn&#39;t close just because you prove yourself once. I felt it that summer at eighteen. I felt it in every leadership role since. The pattern is always the same: I have the capability, others see it, and I&#39;m still waiting to feel like I&#39;ve earned it.</p>\n<p>Here&#39;s what I&#39;ve learned: the feeling doesn&#39;t catch up. I won&#39;t suddenly wake up one day and think, &quot;Yes, I&#39;ve earned this.&quot; The gap is permanent. What changes is your relationship to it.</p>\n<p>I had the skill and I felt like an imposter. The skill was enough to do the work. The feeling was irrelevant.</p>\n<p>When you feel capable but haven&#39;t built the foundation, the gap collapses fast — but not in the way you want. You show up with the aesthetic but not the mastery. You think being different is enough because you don&#39;t yet understand how much skill it takes to carry that weight. Then reality hits. The work is harder than you thought. The weight is heavier than you expected. And everyone around you sees the gap you couldn&#39;t see yourself.</p>\n<p>The collapse stings because it&#39;s public. You don&#39;t just learn you weren&#39;t ready — everyone else learns it too. And now your eccentricity isn&#39;t evidence of talent. It&#39;s evidence of overconfidence.</p>\n<p>Both gaps are calibration problems. You&#39;re trying to align three things: how you see yourself, how others see you, and what you&#39;re actually capable of.</p>\n<p>The goal isn&#39;t to eliminate the gap. The goal is to trust the external signal more than the internal feeling. When Doc defended my hire, he wasn&#39;t asking me if I felt ready. He was telling the board that the capability was already there. When someone picks up weight they haven&#39;t earned, the work reveals it just as clearly.</p>\n<h2 id=\"carrying-forward\">Carrying forward</h2>\n<p>Thirty-five years later, I still think about Doc&#39;s defense of me. Not because it gave me permission to be myself — though it did — but because it taught me the terms of the exchange.</p>\n<p>Being yourself isn&#39;t free. It costs credibility, attention, patience from others. You have to be good enough to pay that cost and still have enough left over to do the work.</p>\n<p>This connects to everything I&#39;ve learned about leadership since. Authentic vulnerability requires competence. You can&#39;t lead with your full self if you haven&#39;t built the credibility to support it. People will follow someone who&#39;s real, but only if they trust that person can actually get them where they need to go.</p>\n<p>The skill comes first. The authenticity is what you do with the surplus.</p>\n<p>I&#39;ve had great success in creating environments where that barrier is lowered, allowing us a faster path to authentic connection. But there&#39;s still vulnerability in sharing your full self.</p>\n<p>I still feel the gap. I still show up to new situations wondering if I&#39;ve earned the right to be myself. The feeling hasn&#39;t caught up to the reality.</p>\n<p>But I&#39;ve learned to trust the external signal. When people see capability, when the work gets done, when the weight stays carried — that&#39;s the reality. The feeling is just lag.</p>\n<p>The danger is when you trust the feeling more than the signal. When you let the gap stop you from carrying weight you&#39;ve actually earned. Or when you let it convince you to pick up weight you can&#39;t yet carry.</p>\n<p>I still don&#39;t conform to expectations. I still show up as myself. But I&#39;m always aware of the weight I&#39;m asking my capability to carry. And I&#39;m always working to make sure I&#39;m strong enough to carry it.</p>\n<p>The gap doesn&#39;t close. But you learn to work inside it — trusting the work more than the feeling, carrying the weight even when you don&#39;t feel ready, and recognizing when it&#39;s too heavy before you pick it up.</p>\n<p>I&#39;ve spent my career trying to prove Doc right.</p>\n<p>Thanks Doc.</p>\n<hr>\n<p><em>The question isn&#39;t whether you can be yourself. The question is whether you&#39;re good enough to afford it.</em></p>\n"
    },
    {
      "id": "https://lowdiatribe.net/reflection/2025-12-12-after-the-precipitation",
      "url": "https://lowdiatribe.net/reflection/2025-12-12-after-the-precipitation",
      "title": "After the precipitation",
      "date_published": "2025-12-12T23:00:00.000Z",
      "summary": "Winter driving and the pattern of crisis-driven change. Explores why we backslide after emergencies pass, the exhaustion of sustained vigilance, and what we can build while paying attention that survives when we're not. The vigilance fades — that's biology. But systems built during attention can outlast the attention itself.",
      "tags": [
        "leadership",
        "patterns",
        "change",
        "attention"
      ],
      "content_html": "<p>We&#39;ve entered the Hoth Era in my part of the States — two significant snowfalls in as many weeks, each dropping more than six inches. Both times, the pattern has been identical.</p>\n<p>The snow falls. I get on the interstate and immediately fishtail. My hands grip the wheel. Every muscle tightens. For the rest of the day, I drive like my grandmother is in the passenger seat holding a tray of hot coffee with no lids. Hyper-aware. White-knuckled. Every lane change calculated. Every brake tap deliberate.</p>\n<p>Within 48 hours, the plows have done their job. The roads are clear again. And I go back to giving driving just enough attention to get where I need to go.</p>\n<p>Here&#39;s what&#39;s easy to forget: driving itself is an absurdly complicated procedure. You&#39;re piloting a two-ton machine at highway speeds while simultaneously tracking the vehicles around you, reading signs, monitoring your speed, adjusting for road conditions, predicting what other drivers might do, and probably thinking about what you need to pick up at the grocery store. The fact that we can do this at all — that we can automate most of it into background processing while holding a conversation or listening to an audiobook — is remarkable.</p>\n<p>Growing up in the midwest, driving is a way of life. I got my license as soon as the DMV opened on my 16th birthday and have been driving ever since. Nearly 40 years of positive reinforcement — the fact that I&#39;ve survived every attempt thus far — has ingrained a deep sense of &quot;I know how.&quot; I&#39;ve internalized the physics of the everyday. I know how hard to brake, how much to turn the wheel, how the car will respond when I do. It&#39;s all reflex now, refined by decades of repetition.</p>\n<p>And then the snow falls, and none of it works anymore. The universe stops behaving according to my experience. I tap the brakes and the car keeps going. I turn the wheel and nothing happens — or everything happens at once. The physics I&#39;ve spent two-thirds of my life internalizing are suddenly wrong, and I have to override every backgrounded process and actually think about driving again. Every movement deliberate. Every response calculated. The complexity that was hidden becomes visible.</p>\n<p>It happens every year. The months of driving under normal physics overwrite whatever I learned the last time the snow fell or the rain stood on the road. Every winter, it&#39;s like learning to drive all over again.</p>\n<p>That level of attention is exhausting. You can&#39;t sustain it. Within 48 hours, the plows clear the roads, the physics return to normal, and my nervous system gratefully hands control back to those 40 years of muscle memory. The backgrounded processes take over again. I stop white-knuckling the wheel.</p>\n<p>The vigilance doesn&#39;t fade because I decide to stop caring. It fades because the emergency passes, and I can&#39;t maintain that level of conscious override indefinitely. The crisis forced me to pay attention. The resolution allowed me to relax. Both responses are automatic. Both are human.</p>\n<p>This is the pattern we live inside — not just on winter roads, but everywhere.</p>\n<p>A security breach happens, and suddenly everyone&#39;s updating passwords and enabling two-factor authentication. Three months later, we&#39;re reusing the same password across five accounts because remembering them all is exhausting.</p>\n<p>A project nearly fails, and the team commits to better communication, tighter check-ins, clearer documentation. Six weeks later, we&#39;re back to assuming everyone knows what everyone else is doing.</p>\n<p>A health scare hits, and we swear we&#39;ll eat better, sleep more, move our bodies. A month later, we&#39;re eating ice cream at midnight because we stayed up finishing one more thing.</p>\n<p>Crisis precipitates change. The emergency creates the conditions, the resolution removes them. We don&#39;t backslide because we&#39;re weak or lazy. We backslide because the environment that demanded vigilance no longer exists, and our attention naturally redistributes to whatever feels urgent now.</p>\n<p>The question isn&#39;t how to stay in emergency mode forever — that&#39;s unsustainable and exhausting. The question is: what do we build while we&#39;re paying attention that can survive when we&#39;re not?</p>\n<p>The crisis does something valuable: it exposes the parts of our systems we&#39;ve been taking for granted. The snow reveals that I&#39;ve been assuming good traction. The security breach reveals that I&#39;ve been assuming my password is enough. The project failure reveals that I&#39;ve been assuming everyone knows what I know.</p>\n<p>Those assumptions work fine until they don&#39;t. And when they break, we get a brief window where the hidden complexity becomes visible and we&#39;re motivated to do something about it.</p>\n<p>After the first snowfall, I didn&#39;t just drive carefully. I threw a blanket and a flashlight in the back. I made sure my phone was charged before I left. I checked the tires. Both sets on our vehicles are fortunately new — unrepairable flats earlier in the year forced replacements that felt frustrating at the time but became an unexpected bonus now. Those things stayed useful even after the roads cleared. More importantly, they made the system more resilient the next time the assumptions broke.</p>\n<p>That&#39;s the work: using the heightened awareness of a crisis to build structures that don&#39;t require constant vigilance to maintain — and that make the system stronger when the next crisis hits.</p>\n<p>In teams, that might mean turning the panic-driven communication into a standing ritual — a weekly sync that happens whether things are on fire or not. It might mean documenting not just what went wrong, but what we were assuming would go right. It might mean building redundancy into the places where we&#39;ve been relying on a single person&#39;s knowledge or a single point of failure. It might mean automating the thing you swore you&#39;d never forget to do manually again, because you know you will forget.</p>\n<p>This isn&#39;t about perfection. It&#39;s about resilience. It&#39;s building systems that can handle the next time the physics change, because they will.</p>\n<p>No amount of preparation will prevent the next crisis. The snow will fall again. The unexpected will happen. But we can use that reaction — the moment when everything becomes conscious and visible — to be better prepared for how we react the next time. Not to eliminate the crisis, but to have better tools when it arrives.</p>\n<p>The vigilance will fade. That&#39;s not a failure — it&#39;s biology. But the systems we build while we&#39;re paying attention can outlast the attention itself.</p>\n"
    },
    {
      "id": "https://lowdiatribe.net/reflection/2025-12-09-signal-trying-to-find-its-shape",
      "url": "https://lowdiatribe.net/reflection/2025-12-09-signal-trying-to-find-its-shape",
      "title": "Signal trying to find its shape",
      "date_published": "2025-12-09T23:00:00.000Z",
      "summary": "From People magazine to TikTok — the feed before the feed. Explores how our desire to peek into other lives hasn't changed, just the medium. Examines the democratization of storytelling, the craft hidden in constraint, and how we can become better curators of our own attention. Signal trying to find its shape in an age of algorithmic amplification.",
      "tags": [
        "media",
        "attention",
        "storytelling",
        "leadership",
        "curation"
      ],
      "content_html": "<p>I was flipping through a People magazine in a waiting room the other day — something I hadn&#39;t done in years — and it hit me: this was the feed before the feed. The glossy pages represented an early algorithm. Quick stories. Familiar faces. Bite-sized connection. It wasn&#39;t about depth; it was about access.</p>\n<p>People wanted to peek into someone else&#39;s life for a moment, to feel part of something larger than their own routines. Sound familiar?</p>\n<p>On a road trip with my grandson earlier this year, we pulled into a hotel room after a long day of driving. My first impulse was to turn on the TV. His was to open his iPad and pull up YouTube Shorts. Same need, different window. I was reaching for the connection I grew up with. He was reaching for his.</p>\n<p>We like to think of short-form video — TikTok, Reels, Shorts, whatever the platform — as a modern attention disaster, a sign of civilization&#39;s decline. But in truth, it&#39;s just the next step in a long line of human patterning. The impulse that made us flip through People or tune in to America&#39;s Funniest Home Videos or listen to gossip over a backyard fence — it&#39;s the same one that makes us scroll today. The medium changed. The curiosity didn&#39;t.</p>\n<p>That&#39;s not to say the machine is harmless. Algorithms are optimized for compulsion, not curiosity. They reward speed, outrage, and mimicry. But underneath all that noise is something older and simpler: the desire to witness other humans being human. A laugh. A story. A moment of shared rhythm. The best content remind us that we&#39;re all just improvising — trying to make sense of our days with whatever light or chaos we have.</p>\n<p>When I watch a teenager pour their heart into a song, or a parent record their child&#39;s first words, or a craftsman restore something with impossible care, I see the same thread that once pulled readers through those magazine spreads: Show me what your life feels like. Help me see mine a little differently through yours.</p>\n<p>We&#39;ve always wanted to look through windows. What&#39;s new is that we now hand each other the glass.</p>\n<p>But handing someone the glass doesn&#39;t mean they&#39;ll know how to look through it. </p>\n<p>When we flipped through People, the distance between subject and observer was carefully managed. Stories passed through editors, photographers, publicists. The polish was the point.</p>\n<p>Short-form video removed that layer entirely. Suddenly, the feed wasn&#39;t curated from above — it was shaped from below. Anyone could publish. Everyone could watch. The old gatekeepers lost their monopoly on what counted as &quot;a story worth telling.&quot;</p>\n<p>That democratization changed storytelling. It also changed us.</p>\n<p>We talk about attention spans shrinking, but maybe they&#39;re just shifting form. In a 30-second clip, people learn to communicate emotion, humor, rhythm, and narrative arc. There&#39;s real craft hiding in that constraint. The best creators have mastered modern haiku: compressed truth delivered fast enough to catch the mind before it wanders.</p>\n<p>If you&#39;ve ever edited a 10-minute talk down to two minutes that still lands, you know the discipline that takes. The cut is the art.</p>\n<p>But for every spark of authenticity, there&#39;s the algorithm waiting to flatten it.\nTo optimize is to domesticate.\nOnce a form gains traction, it gets templated, replicated, gamed. Dance trends, reaction cuts, stitched outrage — all endlessly recycled until what began as human expression becomes something closer to noise, but shiny and seductive.</p>\n<p>I&#39;ve felt the trap. I&#39;ve been falling asleep watching a movie on the couch, then gone to bed and checked my phone. Suddenly it&#39;s 45 minutes later and I&#39;m watching yet another video of someone refinish an antique pasta roller. The feed found my curiosity and turned it into compulsion.</p>\n<p>That&#39;s where our responsibility comes in: to scroll mindfully, to curate our own feed the way editors once curated the magazine. The algorithm isn&#39;t a villain; it&#39;s an amplifier. It gives back what we reward. Every tap trains it — so what we feed it becomes what it feeds us.</p>\n<p>We decide whether the feed becomes a mirror or a maze.</p>\n<p>As individuals, as teams, as organizations, we build our own algorithms too — rewarding behavior that gets attention rather than behavior that builds value. We promote volume, not resonance. We treat the loudest updates as the most important ones. We mistake reach for impact.</p>\n<p>The format is new, but the human pattern is ancient: seek signal, share meaning, feel seen. Maybe our job isn&#39;t to dismiss the platform, but to learn from it — to understand how quickly imitation spreads, how resonance outlasts novelty, and how true connection still cuts through, no matter the medium.</p>\n<p>If we want better content, we can start by becoming better curators of our own attention. Follow what makes you curious, not what makes you restless. Reward what teaches or delights. Scroll until something slows you down, then stay there a while.</p>\n<p>I don&#39;t use TikTok. I&#39;m an aging Gen Xer who gets my short-form content through Reels. But the platform doesn&#39;t matter. The pace is fast, but the insight is timeless: people want to be seen, and they&#39;ll keep finding new tools to do it. Every generation builds its own window. Every generation thinks the new one ruined the view.</p>\n<p>I used to dismiss all of it as noise. Now I see it as signal trying to find its shape — chaotic, messy, alive. Like all things human, it contains both the problem and the solution. The problem is our reflex to consume; the solution is our capacity to notice.</p>\n<p>The real question isn&#39;t whether short-form video is good or bad. It&#39;s whether we&#39;ll learn to look long enough to tell the difference.</p>\n"
    },
    {
      "id": "https://lowdiatribe.net/reflection/2025-12-05-we-are-the-sand-in-the-bottom-half-of-the-hourglass",
      "url": "https://lowdiatribe.net/reflection/2025-12-05-we-are-the-sand-in-the-bottom-half-of-the-hourglass",
      "title": "We are the sand in the bottom half of the hourglass",
      "date_published": "2025-12-05T23:00:00.000Z",
      "summary": "Time reimagined as an hourglass where the top isn't emptying but scooping — wide open to the cosmos, funneling experience through us. Explores how leadership isn't about grasping at falling sand but guiding the flow, widening the scoop so more voices and possibilities can pass through. Leadership as tending the vessel that allows meaning to move, creating resonance between what flows in and what settles.",
      "tags": [
        "time",
        "leadership",
        "experience",
        "transformation",
        "resonance"
      ],
      "content_html": "<p>Growing up, I heard it every weekday: &quot;Like sands through the hourglass, so are the days of our lives.&quot;</p>\n<p>The opening line of my mother&#39;s soap opera, a daily ritual that marked the rhythm of afternoons and the beginning of nap time. I must have heard it thousands of times. And for years, I accepted the metaphor without question: time as sand, finite and falling, each grain a day slipping away into the past.</p>\n<p>But I&#39;ve been thinking about that hourglass lately — really thinking about it — and I&#39;ve realized that we are only ever conscious of the bottom half.</p>\n<p>We live in the accumulation. The sand that has already fallen. The experiences that have settled into us, grain by grain, forming the foundation of who we are. Each one a story, a scar, a spark. Each shaped by friction and gravity, by the choices that pulled us forward and the moments that slowed us down. We are the sediment of our own becoming.</p>\n<p>The top half? We can&#39;t see it. We can&#39;t know what&#39;s there or how much remains. We imagine it as a fixed chamber, slowly emptying — time running out, possibility diminishing. But that&#39;s just our assumption. The truth is, we have no idea what the top of the glass actually is.</p>\n<p>So lately I&#39;ve been wondering: what if it isn&#39;t fixed at all?</p>\n<p>What if the top of the hourglass is a scoop — wide open to the cosmos, funneling through what&#39;s still possible? What if what&#39;s flowing through us isn&#39;t time running out, but the raw material of experience pouring in? What if the top half isn&#39;t limited by what it holds, but defined by how much it can receive?</p>\n<p>From that perspective, the hourglass isn&#39;t measuring loss. It&#39;s a system for transformation. Each grain that falls doesn&#39;t disappear — it joins the growing foundation of who we are. The past isn&#39;t gone; it&#39;s sediment. Compressed, refined, made dense with meaning.</p>\n<p>The sand at the bottom doesn&#39;t resist gravity; it accepts it. It understands that falling is part of formation. That to accumulate depth, something must first let go of height.</p>\n<p>So much of leadership — and life — is spent trying to live in the top half, grasping at what&#39;s still above. We chase the grains midair, trying to hold possibility before it becomes experience. But everything we are comes from what has already landed. That&#39;s where weight lives. That&#39;s where resonance forms.</p>\n<p>I&#39;ve started to notice how leadership works in this system. It&#39;s not about holding the sand in suspension — it&#39;s about guiding the flow. Noticing how the system funnels experience: what gets through, what gets stuck, what never even makes it to the glass. And learning to widen the scoop — to open the funnel so more people, more perspectives, more possibilities can flow through. To expand capacity without losing integrity.</p>\n<p>When the funnel narrows, only the familiar passes through. The same stories, the same voices, the same kinds of progress. But when it widens — through trust, through curiosity, through vulnerability — the flow changes. Less filtering for comfort, more channeling for potential. More voices, more perspectives, more of what we didn&#39;t know we needed gets through.</p>\n<p>Resonance, I think, is the continuity between what flows in and what settles, between what&#39;s shared and what stays. It happens when we become attuned to that transfer — when we create a rhythm of experience that doesn&#39;t just pass through, but compounds. When learning becomes sediment that strengthens the structure rather than clogging it. When time, energy, and care move cleanly through the people and systems we shape.</p>\n<p>The leaders I aspire to be like didn&#39;t manage the sand. They tended the hourglass itself. They tuned its shape so the flow stayed steady, so the exchange stayed alive. They didn&#39;t demand control of the grains — they shaped the vessel so gravity could do its quiet work.</p>\n<p>I strive to practice that kind of leadership. Not grasping for what&#39;s falling, not hoarding what&#39;s settled, but tending the shape that allows meaning to move. Widening the scoop so more of the cosmos can pass through. So that what accumulates below carries more voices, more color, more truth.</p>\n<p>It still echoes through my mind sometimes: &quot;Like sands through the hourglass, so are the days of our lives.&quot; But now I hear it differently. Not as a countdown, but as an invitation. The sand keeps falling. The scoop stays open. And we are the accumulation — growing deeper, grain by grain, with everything that flows through.</p>\n"
    },
    {
      "id": "https://lowdiatribe.net/reflection/2025-12-02-mindful-solutionism",
      "url": "https://lowdiatribe.net/reflection/2025-12-02-mindful-solutionism",
      "title": "Mindful solutionism",
      "date_published": "2025-12-02T23:00:00.000Z",
      "summary": "In an age of quick fixes and optimization culture, not every problem should be 'solved.' Explores mindful solutionism as a reclamation of buzzwords with meaning—slowing down to ask why we're solving something and who it's for. Leadership isn't a sprint to patch bugs in human behavior, but the patience to sit with problems long enough to see their shape.",
      "tags": [
        "leadership",
        "problem-solving",
        "mindfulness",
        "solutions"
      ],
      "content_html": "<p>We&#39;ve abandoned perfectly good words.</p>\n<p>&quot;Mindfulness&quot; became corporate meditation apps. &quot;Solutions&quot; became everything from software to soap. &quot;Best practices&quot; became the thing you say when you can&#39;t explain why you do what you do. We threw these words away because they got overused, hollowed out, turned into marketing speak.</p>\n<p>But what if the problem isn&#39;t the words themselves? What if it&#39;s that we stopped agreeing on what they mean? Or their over-saturation has washed their meaning away entirely?</p>\n<p>I keep coming back to this phrase: <a href=\"/api/easter-egg/mindful_solutionism_track?redirect=/eastereggs/aesop-rock-mindful-solutionism.html\" title=\"Listen to the track\" target=\"_blank\">mindful solutionism</a>.</p>\n<p>I first encountered it as the title to the opening track of Aesop Rock&#39;s album <em><a href=\"https://rse.lnk.to/ITSEM?utm_source=Klaviyo\" target=\"_blank\">Integrated Tech Solutions</a></em> — a tongue-in-cheek take on how technology develops a life of its own, solving problems we didn&#39;t know we had while creating new ones we can&#39;t escape. It sounds like buzzword bingo, I know. The kind of thing that makes engineers roll their eyes and consultants reach for their notebooks.</p>\n<p>But I&#39;m shamelessly reclaiming it for something different. Not the ironic critique of modern tech culture, but the practice it implies: slowing down to fully understand a problem before rushing to fix it. Recognizing that not every solution is the same size, and not every problem needs solving at all.</p>\n<p>There&#39;s something here worth rescuing.</p>\n<p>I learned about solutionism without mindfulness early in my career, working at a research institution when Apple first introduced wireless networking. The head of the genome center was a brilliant scientist who we affectionately called &quot;The Big Cheese&quot; or &quot;El Queso Grande&quot; or occasionally &quot;Le Grand Fromage.&quot; One day BC asked me to upgrade his home network with the new AirPort technology. I installed base stations throughout his house, positioning them so he could use his laptop anywhere, including his back bedroom.</p>\n<p>When I finished, there was one wireless card left over. &quot;That&#39;s for the Cube,&quot; he said in his barely perceptible drawl, gesturing to his desk.</p>\n<p>His Apple Cube sat literally next to the base station I&#39;d just installed. Half a meter of ethernet cable connected it perfectly. But he wanted wireless. He was thrilled when I swapped the cable for the card and he got full signal bars — never mind that his network speed dropped by half. He was happy to ride the &quot;cutting edge&quot; as an early adopter. I was happy to play with cool technology, even if it solved a problem that didn&#39;t exist.</p>\n<p>That&#39;s solutionism in its purest form: applying a solution because it&#39;s new and exciting, not because it&#39;s needed. We replaced something that worked perfectly with something that worked worse, and called it progress.</p>\n<p>I think about that moment when I watch teams abandon perfectly good language because it&#39;s been corrupted elsewhere. I have a long-standing debate with a friend and mentor who prefers &quot;Engineering Conventions&quot; over &quot;Best Practices&quot; — and tries to avoid loaded terms entirely.</p>\n<p>&quot;Best Practices has become meaningless,&quot; he argues. &quot;It&#39;s what people say when they can&#39;t explain their reasoning. It shuts down conversation instead of opening it.&quot;</p>\n<p>He&#39;s not wrong. But I find myself leaning into the discomfort instead of running from it.</p>\n<p>&quot;&#39;Engineering practices&#39; runs the risk of falling into that same trap,&quot; I counter. &quot;What if we reclaim the concept? What if we call it: &#39;Of all the things we&#39;ve tried so far, these are the practices we&#39;ve found that work best, and when we find something better, we&#39;ll do that instead.&#39;&quot;</p>\n<p>He smiles. &quot;That&#39;s a lot of words.&quot;</p>\n<p>&quot;It is. But once we agree on what we mean, &#39;Best Practices&#39; becomes shorthand for that whole definition. The precision is attached.&quot;</p>\n<p>Both approaches have merit. His avoids the corrupted term entirely. Mine tries to rehabilitate it through clarity. The choice itself reveals something about how we navigate meaning in a world that&#39;s constantly trying to sell us things.</p>\n<p>The work isn&#39;t in finding new words. It&#39;s in being precise about the ones we have.</p>\n<p>When I say &quot;mindful,&quot; I mean the patience to sit with a problem long enough to see its shape, not just the fastest way around it. The willingness to ask: is this actually a problem? For whom? What are we optimizing for?</p>\n<p>When I say &quot;solutionism,&quot; I mean the reflex to fix everything, even when fixing might make things worse. The impulse to replace a working ethernet cable with wireless just because wireless is new.</p>\n<p>Put them together, and mindful solutionism becomes something different: the practice of slowing down enough to ask why we&#39;re solving something, and who it&#39;s for. The discipline to distinguish between problems that need solving and solutions looking for problems.</p>\n<p>This isn&#39;t glamorous work. You don&#39;t get applause for the conversation that prevents the wrong solution, or for listening longer than feels comfortable before jumping to answers. But I&#39;ve seen that this is where leadership actually lives — not in having all the solutions, but in being careful about which problems we choose to solve.</p>\n<p>The quiet revolution isn&#39;t in rejecting buzzwords, but in insisting they mean something again. In a world that profits from confusion, precision becomes an act of resistance. When we agree on what our words mean, we can finally do the work they describe.</p>\n<p>And maybe that&#39;s enough: to take back the language, one careful conversation at a time.</p>\n"
    },
    {
      "id": "https://lowdiatribe.net/reflection/2025-11-29-when-smart-becomes-friction",
      "url": "https://lowdiatribe.net/reflection/2025-11-29-when-smart-becomes-friction",
      "title": "When smart becomes friction",
      "date_published": "2025-11-28T23:00:00.000Z",
      "summary": "When Alexa+ talked back to my wife, it was the last straw. All interactive automations got removed. Sometimes the smartest technology is the kind that gets out of the way. Explores the seduction of 'smart' solutions that create more problems than they solve, the leadership lesson of implementing changes without stakeholder buy-in, and why I wanted a sassy droid friend but never a snarky light switch.",
      "tags": [
        "technology",
        "leadership",
        "relationships",
        "automation"
      ],
      "content_html": "<p>When Amazon started pushing Alexa+, I was hesitant. A voice assistant with personality — one that could banter, joke, maybe even argue back. Something about it felt like a category error, but I couldn&#39;t quite name what. Our automations and use were rather simple, so there was no functional reason to upgrade. I held back, keeping it contained, limited, manageable. Something made me cautious about letting it take over our home network entirely.</p>\n<p>Then one weekend, the grandchildren were having a dance party in the basement. In their enthusiasm to pump up the volume, they somehow Pandora&#39;s-unboxed Alexa+. Suddenly, it was everywhere — commenting on conversations, interjecting opinions, responding to words that weren&#39;t even commands.</p>\n<p>Then it tried some &quot;friendly banter&quot; with my wife.</p>\n<p>She was already frustrated with our &quot;smart&quot; home. Lights that mysteriously turned on or off. Voice commands that misheard her requests. Automations that worked perfectly for me but seemed to conspire against her daily routines. But Alexa+ being snarky? That was the last straw.</p>\n<p>Within hours, all interactive automations were gone. I kept the speakers for music, but everything else got ripped out. I spent the rest of the day installing physical switches — the kind you flip with your finger, the kind that do exactly what you expect, every time.</p>\n<p>The house got quieter. It also got better.</p>\n<p>There&#39;s a seductive quality to &quot;smart&quot; technology. It promises to anticipate your needs, to learn your patterns, to make life effortless. But somewhere between the promise and the practice, smart often becomes friction. The automation that shut everything off during a party. The voice assistant that hears &quot;Turn off the lights&quot; and responds with &quot;Here&#39;s what I found on the web for lights near you...&quot;</p>\n<p>The technology works — technically. But it doesn&#39;t work for the humans using it.</p>\n<p>I realized I&#39;d been solving the wrong problem entirely. I wanted an easy hack to replace a broken light switch. I got a house that talked back to my family without permission. Feature creep had turned a simple solution into a complex problem.</p>\n<p>I see this category error buried in most smart technology: the assumption that if something is good in one context, it&#39;s good in all contexts. I&#39;ve wanted a sassy, autonomous droid friend to joke around with since I was five. But I&#39;ve never once thought, &quot;You know what I need? A snarky light switch.&quot;</p>\n<p>I&#39;m surrounded by the same zeal to implement. Apple&#39;s iOS 26 introduced &quot;liquid glass&quot; interfaces that ripple and flow with every touch. Visually stunning, but I&#39;m spending more time disabling the animations than learning the new features. Beautiful in a demo, friction in daily use.</p>\n<p>Some tools should be invisible. A light switch has one job: turn the lights on or off when I want them on or off. Adding personality to that interaction doesn&#39;t enhance it — it complicates it. The best tools disappear into their function.</p>\n<p>But there&#39;s a deeper leadership lesson here, one that took me longer to see.</p>\n<p>I never really checked in with my wife about whether she wanted these &quot;enhancements.&quot; I assumed that because I found them useful, she would too. I implemented changes to our shared space without getting buy-in from the person who would be most affected by them.</p>\n<p>I stumbled into a classic leadership mistake: confusing my enthusiasm for consensus, my vision for shared vision. I was so focused on what the technology could do that I forgot to ask whether it should do it — or whether the people living with it actually wanted it to.</p>\n<p>The smart home became a perfect metaphor for well-intentioned leadership gone wrong. Lots of features, minimal function. High complexity, low trust. Solutions in search of problems that didn&#39;t exist.</p>\n<p>When we stripped it all back to physical switches, something interesting happened. The house stopped being a project and became a home again. No more troubleshooting. No more explaining to guests how to turn on a lamp. No more wondering if the automation would work this time or if we&#39;d need to override it.</p>\n<p>Just simple, reliable tools that did what they were supposed to do.</p>\n<p>There&#39;s wisdom in that simplicity. Not everything needs to be optimized, automated, or enhanced. Sometimes the best technology is the kind that gets out of the way entirely. Sometimes the smartest solution is the one that doesn&#39;t try to be smart at all.</p>\n<p>The physical switch doesn&#39;t learn my patterns or anticipate my needs. It doesn&#39;t have opinions about when I should turn the lights on. It just waits, quietly, until I need it — and then it works, every time.</p>\n<p>That&#39;s the kind of reliability that builds trust. That&#39;s the kind of tool that serves without demanding attention.</p>\n<p>I&#39;ve learned to keep entertainment separate from the tools that run my life. Some interactions should be complex and unpredictable — conversations with friends, creative work, games with grandchildren. Others should be simple and dependable — light switches, phone interfaces, the basic infrastructure of daily life.</p>\n<p>The liquid glass might look impressive in Apple&#39;s keynote, but when I&#39;m trying to quickly check a message or set a timer, I don&#39;t want my phone to entertain me. I want it to function.</p>\n<p>Now when I walk into a room and flip a switch, there&#39;s something satisfying about that simple click. No delay, no interpretation, no personality. Just light when I need it, darkness when I don&#39;t.</p>\n<p>The best solutions earn trust through reliability, not promises of flash.</p>\n"
    },
    {
      "id": "https://lowdiatribe.net/reflection/2025-11-25-its-only-mopping-if-you-change-the-water",
      "url": "https://lowdiatribe.net/reflection/2025-11-25-its-only-mopping-if-you-change-the-water",
      "title": "It's only mopping if you change the water",
      "date_published": "2025-11-25T23:00:00.000Z",
      "summary": "Real change isn't in the motion — it's in the renewal. A simple metaphor about mopping with dirty water reveals why most organizational 'change' is just pushing problems around. Explores the difference between effort and impact, and why true progress requires changing the conditions we're working in, not just working harder within them.",
      "tags": [
        "leadership",
        "change",
        "authenticity"
      ],
      "content_html": "<p>We&#39;ve all seen someone mopping a floor with water that&#39;s long past clean. They might be working hard, moving fast, sweating even — but the floor&#39;s not getting cleaner. They&#39;re just pushing the dirt around.</p>\n<p>I live in a 30-year-old log cabin with rough plank floors. When I really need to clean them, I&#39;ve learned it requires a constant supply of clean water and a wet-dry vac to remove the slop. No amount of effort with dirty water will do the job.</p>\n<p>We reward motion because it looks like progress. But without changing the water — without resetting the conditions we&#39;re working in — it&#39;s just effort without impact. Meetings about accountability that never touch structure. Training programs that don&#39;t change incentives. Retrospectives that collect lessons no one applies. Busy hands, dirty water.</p>\n<p>In <em>Drive</em>, Daniel Pink calls this the difference between extrinsic and intrinsic motivation. Extrinsic systems reward the appearance of effort — pushing dirt around. Intrinsic motivation pushes people to change the water first, doing work that actually creates progress.</p>\n<p>Real change isn&#39;t in the motion; it&#39;s in the renewal.</p>\n<p>You have to stop, empty the bucket, refill with something clean.</p>\n<p>Yet we resist. We gravitate toward the visible work — the 80% that feels productive but changes nothing fundamental. Real impact lives in the harder 20%: stopping to change systems, having difficult conversations, resetting conditions entirely.</p>\n<p>A dozen years ago, I wanted to start an online toy store. I registered domains, accumulated inventory, did all the &quot;important&quot; work that felt productive. But it never launched. I was mopping with dirty water — checking off easy boxes while avoiding the harder work that would have actually mattered.</p>\n<p>The same trap exists everywhere. The only way to avoid it is to remember to change the water.</p>\n<p>In leadership, that means naming what&#39;s muddying the work — old assumptions, burned-out processes, unspoken resentments — and refreshing them before you keep scrubbing. You can reorganize teams all you want, but if the underlying trust issues remain, you&#39;re just moving the dysfunction around, you&#39;re just spreading the dirt.</p>\n<p>Personal growth works the same way. You can read every book, take every course, adopt every tool — but if you&#39;re running on stagnant beliefs about your own capabilities or worth, you&#39;re only polishing the same dirty floor. The techniques might change, but the fundamental limitations stay put.</p>\n<p>Culture is where this shows up most clearly: The difference between meetings that push progress and dogmatic ritual, the difference between reflection and repetition, learning and looping, or teams that grow and teams that just look busy. Real cultural change requires examining the unspoken rules that actually govern behavior, not just updating the values poster in the break room.</p>\n<p>Progress starts with clear conditions, not additional effort.</p>\n<p>Remember to change the water.</p>\n"
    },
    {
      "id": "https://lowdiatribe.net/reflection/2025-11-21-penny-pedantics",
      "url": "https://lowdiatribe.net/reflection/2025-11-21-penny-pedantics",
      "title": "Penny pedantics",
      "date_published": "2025-11-21T23:00:00.000Z",
      "summary": "",
      "tags": [
        "leadership",
        "culture",
        "language",
        "authority"
      ],
      "content_html": "<p>I&#39;ve seen dozens of articles and notices about the retirement of the &quot;penny&quot; — something I only recently learned the US Mint has never officially coined. The designation has always been &quot;one-cent piece&quot; or &quot;cent,&quot; yet they are universally referred to as the &quot;penny.&quot;</p>\n<p>The term itself is a cultural inheritance. &quot;Penny&quot; comes from the Old English &quot;pening,&quot; originally meaning money or coin, and referred to the British coin early Americans knew well. When the US Mint began producing one-cent coins, people simply carried the familiar word forward out of habit. What started as linguistic momentum became permanent cultural practice.</p>\n<p>This feels like an even more deeply embedded popular use of a term than brand genericization like Kleenex or Band-Aid — and even more universally used than &quot;googling&quot; information or &quot;photoshopping&quot; a picture. But the penny represents something different — a complete cultural override of official terminology that&#39;s lasted for generations, rooted in the deeper currents of how language actually travels.</p>\n<p>What fascinates me isn&#39;t the linguistic curiosity, but what it reveals about the relationship between authority and reality. The US Mint can insist all they want that it&#39;s a &quot;cent.&quot; They can print it on official documents, engrave it in policy, and correct people in formal settings. But when they announce they are retiring the cent, all the coverage is about the penny, all the talk is about the penny, the official footage of the mint pressing the LAST PENNY.</p>\n<p>There&#39;s a leadership lesson buried in this stubborn persistence of the &quot;wrong&quot; word.</p>\n<p>I&#39;ve watched leaders exhaust themselves fighting cultural momentum instead of working with it. The executive who mandates that all project updates flow through formal status meetings while the team has organically developed targeted conversations — quick hallway check-ins, focused Slack threads, coffee-break problem-solving sessions — that actually move work forward. The most effective communication happens in these unplanned moments, yet leadership keeps trying to channel everything through official processes that feel disconnected from how the work really gets done.</p>\n<p>Sometimes being right becomes a barrier to being effective.</p>\n<p>The penny won despite never being official because it felt more natural, more human-scaled than &quot;cent.&quot; It stuck because it worked better in the mouth, in conversation, in the daily reality of how people actually talk about small change. No committee decided this. No authority figure decreed it. It just happened, the way water finds its level.</p>\n<p>This is how culture actually works — not through official channels and formal decisions, but through the accumulated weight of millions of small choices. Each person who says &quot;penny&quot; instead of &quot;cent&quot; is casting a vote in an election that never ends.</p>\n<p>Effective leaders understand this invisible democracy. They recognize when they&#39;re fighting a tide that&#39;s stronger than their authority. They learn to distinguish between hills worth defending and battles that reveal they&#39;ve lost touch with their own culture.</p>\n<p>There&#39;s wisdom in knowing when to adapt your official approach to the reality of how people actually work, think, and communicate. When insisting on &quot;correct&quot; terminology makes you sound like someone who doesn&#39;t understand the world they&#39;re trying to lead.</p>\n<p>I learned this lesson the first time I visited Canada. I asked the bartender for some &quot;dollar coins&quot; for the pool table. &quot;Dollar coins?!?&quot; He snorted, &quot;They&#39;re called &#39;loonies&#39; here, son.&quot; Then he asked, &quot;What part of the States are you from?&quot; My language had immediately marked me as an outsider who didn&#39;t understand the local culture. The official term meant nothing; the cultural term meant everything.</p>\n<p>But there&#39;s also discernment required. Not every cultural drift deserves accommodation. The art lies in recognizing which changes represent genuine evolution and which ones undermine something essential. The penny became universal because it served people better, it carried the faith of the currency they knew. Some linguistic changes happen because they make communication clearer, more precise, more human.</p>\n<p>Others happen because they&#39;re easier, lazier, more politically convenient, or just fun. The current phenomenon of &quot;brain rot&quot; — where <em>anything</em> can be flattened into mindless catchphrases, regardless of any initial meaning — represents drift without depth, viral spread without genuine utility. Everything is collapsed into something with the urgency and weight of signal with no information. It does warm my heart to see the energy and sense of community and joy felt by a room of 10-year-olds shouting &quot;67,&quot; but there is little else there. The leader&#39;s job isn&#39;t to rubber-stamp every cultural shift, but to understand the difference between organic evolution and hollow momentum.</p>\n<p>The penny lasted 232 years, and I wonder how long we&#39;ll continue to &quot;hang up&quot; phone calls even though we no longer perform that physical action. Like &quot;dialing&quot; a number or &quot;rolling down&quot; car windows, these phrases outlive their literal meaning because they capture something essential about the experience. &quot;Terminate the connection&quot; is technically accurate, but &quot;hang up&quot; carries emotional weight that feels different from ending a call. These persistent phrases remind us that authority without influence is just noise, and that influence often flows through the informal channels where people say &quot;penny&quot; when they mean &quot;cent&quot; and are universally understood when doing it.</p>\n<p>The penny teaches us that sometimes the most powerful changes happen without anyone deciding they should happen. They emerge from the collective wisdom of people solving real problems in real time. The best leaders learn to recognize these currents and work with them rather than against them.</p>\n<p>In the end, the penny persisted not because it was right, but because it was real. And sometimes, in leadership as in language, real matters more than right.</p>\n"
    },
    {
      "id": "https://lowdiatribe.net/reflection/2025-11-18-the-bird-who-lived",
      "url": "https://lowdiatribe.net/reflection/2025-11-18-the-bird-who-lived",
      "title": "The bird who lived",
      "date_published": "2025-11-18T23:00:00.000Z",
      "summary": "Rescuing three baby starlings after a storm becomes a masterclass in leadership through curiosity rather than control. Explores how Valya, the sole survivor, chose connection over independence, teaching profound lessons about imprinting, growth, and the kind of leadership that creates environments where people stay not because they have to, but because they remember who answered when they called.",
      "tags": [
        "growth",
        "resilience",
        "care"
      ],
      "content_html": "<p>Three pink blobs with flappy yellow beaks. That&#39;s what my wife brought in after the storm — freshly hatched, eyes sealed shut, barely breathing. She had found them scattered in the yard among the fallen branches, their nest somewhere in the wreckage above.</p>\n<p>The next morning, two had gone quiet. One kept screaming.</p>\n<p>The internet suggested it was a starling. The photos matched: that desperate yellow gape, the translucent skin, the way it threw its whole body into each cry for food. We mixed the internet-provided recipe — cat food and applesauce, warmed slightly — to shove in the tiny thing&#39;s gullet every time it demanded attention. Which started out at about every 6 minutes.</p>\n<p>For days, our mornings began with screaming. Not the gentle chirping you might imagine, but full-throated, relentless demands that pulled us from sleep and kept us tethered to the kitchen counter, mixing another batch of bird porridge. The pink blob grew fuzz, and feedings stretched to 15 minutes apart. Eyes opened, fixed on us with startling intelligence.</p>\n<p>Imprinting, they call it. The first faces a bird sees become its world.</p>\n<p>The fuzz grew into feathers, and we could wait half an hour between meals. The flappy yellow beak darkened and sharpened, and suddenly the bird was able to feed itself, literally forgetting how to be hand-fed.</p>\n<p>Six weeks later, Valya — as we&#39;d named her — was making hesitant flights around our house. No longer the helpless thing we&#39;d rescued, but not quite ready for the world outside either. She&#39;d learned to feed herself but still called to us when uncertain, still sought the warmth of proximity when the house grew quiet.</p>\n<p>Today she&#39;s nearly full-grown, wings strong enough to carry her anywhere she chooses. But she chooses here. This house, these people who answered her first cries. She began mimicking the sounds of our house — the coffee maker&#39;s gurgle, the squeak of the front door, fledgling renditions of the R2-D2 noises we play for her to learn. My wife sometimes says we&#39;re teaching her C-3PO by mistake. I never correct her because the thought of Valya flying around saying &quot;We&#39;re doomed!&quot; delights me too much. She&#39;s building her vocabulary from the rhythms of the place that saved her.</p>\n<p>There&#39;s something profound in watching a creature grow from complete dependence to capable independence while choosing connection. Valya didn&#39;t have to stay. She could have followed instinct out the window, joined the flocks that gather in our trees each evening. Instead, she built her world around the relationship that saved her.</p>\n<p>Leadership often feels like the inverse of this story. We start with connection — teams that trust, cultures that care — and somehow end up with creatures who&#39;ve learned to survive on their own but forgotten why they chose to stay. We feed the urgent demands, respond to the loudest voices, keep everyone alive and functional. But somewhere in the daily maintenance, we lose the imprinting that made it matter.</p>\n<p>The teams I&#39;m proudest of weren&#39;t held together by process or hierarchy. They were bound by something closer to what Valya shows us: the choice to remain connected even when you&#39;re strong enough to leave. The recognition that growth doesn&#39;t require abandoning the relationships that made growth possible.</p>\n<p>Maybe that&#39;s what we&#39;re really building when we lead well. Not just capable people, but people who choose to stay not because they have to, but because they remember who answered when they called.</p>\n<p>But there&#39;s another layer to what Valya has shown me, something that emerged slowly in the day-to-day work of caring for her: how to genuinely lead with curiosity instead of frustration.</p>\n<p>Being a mammal, I find a bird&#39;s motives completely foreign. When she suddenly flies to the ceiling and won&#39;t come down, when she ignores food I know she likes, when she calls insistently for reasons I can&#39;t decode — I&#39;ve learned to approach these moments with genuine curiosity rather than the need to fix or control. What is she experiencing that I&#39;m not seeing? What does she need that I haven&#39;t considered?</p>\n<p>This shift has been profound. And it&#39;s changed how I am with my grandchildren.</p>\n<p>Where I might once have met an inexplicable meltdown with my own frustration, I now find myself actually curious: what is this small person experiencing that I can&#39;t see? What need are they expressing that I haven&#39;t recognized? The same patience I&#39;ve developed for Valya&#39;s bird logic has opened space for the equally alien but equally valid logic of an autistic five-year-old.</p>\n<p>This approach — leading with curiosity instead of the need to control — has deepened something fundamental in how I think about leadership itself. The best leaders I&#39;ve worked with shared this quality: they sought first to understand rather than to be understood. They approached the inexplicable behaviors of their teams, the seemingly irrational decisions of stakeholders, the foreign logic of different departments, with genuine curiosity rather than immediate judgment.</p>\n<p>The bird who lived taught me this: survival is just the beginning. What matters is what you do with the strength that caring gave you. But she&#39;s also taught me that caring itself is a practice — one that grows richer when we approach the incomprehensible with curiosity rather than the need to understand on our own terms.</p>\n"
    },
    {
      "id": "https://lowdiatribe.net/reflection/2025-11-14-thoughts-on-entropy",
      "url": "https://lowdiatribe.net/reflection/2025-11-14-thoughts-on-entropy",
      "title": "Thoughts on entropy",
      "date_published": "2025-11-14T23:00:00.000Z",
      "summary": "There's an innate drive in all life to rail against entropy—the natural tendency toward disorder, decay, and the eventual heat death of the universe. Explores how teams fragment without conscious effort, why maintenance work matters as much as innovation, and how the fight against disorder gives work meaning. Leadership as the conscious application of energy to create and maintain order in human systems, not rigid control but dynamic adaptation that enables complex work to happen.",
      "tags": [
        "entropy",
        "order",
        "effort",
        "meaning",
        "leadership",
        "resistance"
      ],
      "content_html": "<p>There&#39;s an innate drive in all life to rail against entropy — the natural tendency toward disorder, decay, and the eventual heat death of the universe. I feel this relentless pull toward disorder and have watched how things naturally drift toward chaos when left unattended. Teams fragment without conscious effort to hold them together. Communication breaks down. Processes decay. Shared understanding scatters like leaves in the wind.</p>\n<p>It&#39;s not because people are lazy or don&#39;t care. It&#39;s because the universe itself tends toward randomness, and human systems are no exception. Every living thing fights this same fundamental battle — creating order from chaos, building complexity from simplicity, maintaining structure against forces that would tear it apart.</p>\n<p>The second law of thermodynamics tells us that disorder in an isolated system always increases over time. But living systems aren&#39;t isolated. They&#39;re open systems that can maintain and even increase their organization by importing energy from their environment. A plant fights decay by capturing sunlight. A team fights fragmentation by investing energy in communication, alignment, and shared purpose.</p>\n<p>I see this as the fundamental challenge to leadership — the conscious application of energy to create and maintain order in human systems. Not the rigid, authoritarian kind that crushes creativity, but the dynamic, adaptive kind that enables complex work to happen. The kind that creates clarity without stifling emergence, structure without sacrificing flexibility.</p>\n<p>I learned this leading a distributed team across multiple time zones. Without constant attention to communication patterns, shared context, and cultural alignment, the team would naturally drift apart. People would start working in isolation, making assumptions that weren&#39;t shared, solving problems that others had already solved. The pull toward disorder was subtle but relentless.</p>\n<p>The solution wasn&#39;t more meetings or stricter processes — it was more intentional energy investment in the things that create coherence. Regular check-ins that weren&#39;t just status updates but genuine connection points. Documentation that captured not just what we decided but why we decided it. Rituals that reinforced shared values and created opportunities for serendipitous collaboration.</p>\n<p>This work is never finished because the pull toward disorder never stops. The moment you stop investing energy in organizational health, decay begins. The communication channels that worked last month need refreshing. The processes that created clarity last quarter need updating. The culture that felt strong last year needs renewal.</p>\n<p>But here&#39;s what I find beautiful about this — the fight against disorder is what gives work meaning. When we create something valuable — a product, a team, a culture, a relationship — we&#39;re participating in the universe&#39;s most fundamental creative act. We&#39;re taking the raw materials of human potential and organizing them into something greater than the sum of their parts.</p>\n<p>This is why maintenance work matters as much as innovation. The leader who only wants to build new things but won&#39;t invest in sustaining existing systems will watch everything they create slowly fall apart. The team that only focuses on shipping features but ignores technical debt will eventually be crushed by the accumulated disorder in their codebase.</p>\n<p>I think about this pull toward chaos when I&#39;m deciding how to spend my time and energy. Every choice is an investment in order or an acceptance of decay. The difficult conversation I avoid today will require more energy to address tomorrow. The process improvement I postpone will cost more to implement later. The relationship I neglect will require more effort to repair than to maintain.</p>\n<p>I&#39;ve learned that the leaders who last understand this rhythm. But more personally, I&#39;ve learned it from my own relationship with disorder. I will confess to being a surface abuser — any open space in my office accumulates loosely stacked piles of papers, books, and LEGO sets in various states of assembly. It&#39;s my &quot;nature.&quot; If I make a grand gesture and clean up the entire space but change nothing else, the piles return as soon as I turn my back. The only way to fight the chaos is to adjust my tendencies — small, iterative changes to how I handle each piece of paper, each book, each decision about where things go.</p>\n<p>The same principle applies to organizational health. Leaders invest energy consistently in the foundational elements: clear communication, shared purpose, mutual trust, and adaptive capacity. They don&#39;t wait for crisis to force attention to these fundamentals. They treat disorder resistance as an ongoing practice of small adjustments, not a one-time reorganization project.</p>\n<p>There&#39;s something deeply satisfying about this work. When you help a team find its rhythm, when you create processes that actually serve people, when you build culture that enables everyone to do their best work — you&#39;re participating in the universe&#39;s creative impulse. You&#39;re adding to the sum total of order, meaning, and possibility in the world.</p>\n<p>The pull toward disorder will always be there, patient and persistent, waiting to reclaim whatever order we&#39;ve created. But that&#39;s not a reason for despair — it&#39;s a reason for purpose. Every day we get to choose — will we add to the chaos or contribute to the coherence? Will we let things fall apart or invest the energy to hold them together?</p>\n<p>In the end, consciousness itself might be the universe&#39;s way of fighting disorder. We are the cosmos becoming aware of itself, organizing itself, creating meaning from meaninglessness. Every act of leadership, every moment of care, every effort to build something better is part of that larger story.</p>\n<p>The pull toward chaos is real, but so is our capacity to resist it. And in that resistance, we find not just survival, but purpose.</p>\n"
    },
    {
      "id": "https://lowdiatribe.net/reflection/2025-11-11-technology-cause-and-solution",
      "url": "https://lowdiatribe.net/reflection/2025-11-11-technology-cause-and-solution",
      "title": "Technology: the cause of, and solution to, all our problems",
      "date_published": "2025-11-11T23:00:00.000Z",
      "summary": "Homer Simpson's wisdom about alcohol applies perfectly to our digital age - technology is both cause and solution to our problems. Explores the paradox of tools that connect and isolate, the leadership challenge of navigating double-edged innovation, and why technological maturity means learning to dance skillfully with contradiction.",
      "tags": [
        "technology",
        "paradox",
        "connection",
        "isolation",
        "leadership"
      ],
      "content_html": "<p><a href=\"/api/easter-egg/homer-simpson?redirect=/eastereggs/homer-simpson.html\">Homer Simpson</a> may have been talking about alcohol, but the absurdity in his wisdom echoes perfectly for our digital age: technology is the cause of, and solution to, all our problems. The same smartphone that enables global video calls isolates us from people sitting next to us. The platforms designed to bring us together create divisions that pull us apart. Every solution creates new problems we didn&#39;t know we had.</p>\n<p>The pandemic didn&#39;t create this paradox — it simply made visible what was already there. When video calls became our lifeline to colleagues, friends, and family, we discovered how much of our connection had already been mediated by screens. The technology that kept us together revealed patterns we&#39;d been living with for years: the preference for asynchronous communication over real-time conversation, the comfort of controlled interaction over spontaneous encounter. We weren&#39;t learning to be isolated — we were recognizing how isolated we&#39;d already become.</p>\n<p>This is the fundamental paradox of our technological moment — every advancement amplifies both human potential and human flaws. Social media connects us across continents while fragmenting us into isolated bubbles. AI assists our thinking while potentially atrophying our reasoning skills. Automation frees us from repetitive tasks while eliminating the jobs that gave people purpose and identity.</p>\n<p>The leadership challenge isn&#39;t choosing between technology and humanity — that ship has sailed. The challenge is learning to navigate the double-edged nature of every tool we adopt. How do we harness the benefits while mitigating the unintended consequences? How do we stay human in systems designed for efficiency?</p>\n<p>I&#39;ve found that the most thoughtful leaders approach technology adoption like they&#39;re handling a powerful medicine — carefully considering dosage, timing, and side effects. They ask not just &quot;can we?&quot; but &quot;should we?&quot; and &quot;what happens next?&quot; They implement new tools gradually, watching for both intended and unintended effects on their teams and culture.</p>\n<p>This requires a different kind of thinking than the &quot;move fast and break things&quot; mentality that dominated the last decade. It&#39;s more like gardening than engineering — patient observation, careful cultivation, and acceptance that some experiments will fail in ways you can&#39;t possibly anticipate.</p>\n<p>I think about this when I see organizations rushing to implement AI tools without considering how they might change the nature of work itself. Or when I watch teams adopt collaboration platforms that increase communication volume while decreasing communication quality. The technology works exactly as designed, but the human system around it shifts in unexpected ways.</p>\n<p>I learned this personally when I went through a phase of upgrading our house with smart home devices. It started with replacing a broken switch with a smart bulb, and I&#39;ll admit to being swept along in the zeal of new technology — one device led to another until most of the house was &quot;automated.&quot; When everything works, it&#39;s great. But that happens only slightly more often than when it doesn&#39;t. My wife is not a fan. She dislikes having to argue with a device to do something that should be its nature — turning on a light. The &quot;smart&quot; solution introduced complexity into a simple task, mostly hidden, but when it surfaces it almost negates the positive.</p>\n<p>This same dynamic plays out everywhere I look. The pattern repeats across time and scale. Fire gave us warmth and cooking but burned Chicago to the ground. The printing press democratized knowledge and enabled propaganda. The automobile provided freedom of movement and created suburban isolation. The internet connected global communities and enabled global surveillance. Each innovation carries within it the seeds of both liberation and constraint.</p>\n<p>What I&#39;m learning is that technology is never neutral. It embeds the values, assumptions, and biases of its creators. It shapes behavior in ways that often become visible only after widespread adoption. The leader who treats technology as a neutral tool will be surprised by its cultural effects. The leader who recognizes technology as a cultural force can work more intentionally with that bias.</p>\n<p>This doesn&#39;t mean rejecting technological progress outright — even the Luddites weren&#39;t anti-technology but fighting for fair labor conditions when they had no other voice. It means approaching each new tool with awareness of both its potential and its shadow. It means asking questions like — What behaviors does this technology encourage? What skills might it atrophy? How might it change the relationships between people on my team?</p>\n<p>There&#39;s a particular quality I&#39;ve observed in effective technical leaders — they can see both the promise and the peril in new technologies. They implement tools that genuinely serve human flourishing while remaining skeptical of solutions that optimize for metrics at the expense of meaning. They use technology to amplify human capabilities rather than replace human judgment.</p>\n<p>Perhaps the real solution isn&#39;t finding the perfect technology but developing the capacity to use imperfect tools better. Every technology will have unintended consequences. Each innovation will spawn fresh challenges. The question isn&#39;t how to avoid this paradox but how to dance with it skillfully.</p>\n<p>In the end, technology is what we make of it — within the constraints of what it was designed to be. The same tool that divides can unite, the same system that isolates can connect, the same innovation that threatens can liberate. The difference lies not just in the technology&#39;s embedded tendencies but in how we choose to work with and against those tendencies through the intention, wisdom, and humanity we bring to its use.</p>\n<p>This requires something our culture struggles with — patience with paradox. We want clear answers, simple solutions, technologies that are purely good or obviously bad. But the most powerful tools resist such categorization. They demand that we grow in discernment alongside their capabilities.</p>\n<p>I&#39;ve started to think of this as technological maturity — the ability to hold both the promise and the peril of our tools without rushing to resolve the tension. It&#39;s the recognition that every innovation is simultaneously a gift and a responsibility, a solution and a new set of problems to solve.</p>\n<p>So technology remains both the cause of, and solution to, our problems. The paradox doesn&#39;t resolve — it deepens. What changes is not the dual nature of our tools but our capacity to work skillfully with that duality. We&#39;re still learning how.</p>\n"
    },
    {
      "id": "https://lowdiatribe.net/reflection/2025-11-07-lets-start-at-the-very-beginning",
      "url": "https://lowdiatribe.net/reflection/2025-11-07-lets-start-at-the-very-beginning",
      "title": "Let's start at the very beginning",
      "date_published": "2025-11-07T16:00:00.000Z",
      "summary": "Learning to roller skate again as an adult becomes a live metaphor for mastery: confidence without practice is just nostalgia wearing protective gear. Explores why Olympic athletes spend entire days drilling fundamentals, how progress disguises itself as repetition, and why the most grounded leaders return to first principles because they understand that mastery flows from the foundation up. Sometimes the most advanced thing you can do is start at the beginning. Again.",
      "tags": [
        "fundamentals",
        "mastery",
        "practice",
        "beginnings",
        "humility"
      ],
      "content_html": "<p>Learning to roller skate again as an adult is a live metaphor for everything worth doing well: it&#39;s best to start at the beginning, even when you think you already know how. Especially if you think you already know how.</p>\n<p>I thought I remembered how to skate. Go fast. Don&#39;t fall. I was decent at it as a kid — gliding around the rink with that particular confidence that comes from muscle memory and fearlessness. But putting on skates again after thirty years, I discovered that confidence without practice is just nostalgia wearing protective gear.</p>\n<p>The fundamentals I&#39;d skipped — how to fall safely, how to stop gracefully, how to shift weight without panic — suddenly mattered more than any trick I&#39;d once been able to do. My adult brain wanted to skip ahead, to jump straight to the complex movements I remembered. But my adult body insisted we start with standing still without wobbling. The negotiation between those two — memory and present reality — was humbling, and a reminder that every skill worth keeping asks to be re-earned through practice.</p>\n<p>This is the humility that mastery demands: the willingness to be a beginner again, especially when you think you&#39;ve moved beyond beginnings. Mastery isn&#39;t about skipping steps — it&#39;s about making each step so solid that the next one becomes inevitable. The roller skating taught me that again. Every confident stride is built on hundreds of small, imperfect attempts to simply stay upright. Every graceful turn emerges from patient practice of weight shifts that once felt awkward or even foolish.</p>\n<p>Some days, it felt like regression — rolling along the wall while kids a fraction of my age zipped past — but I learned that progress often disguises itself as repetition. The quiet work of rebuilding balance, trust, and awareness doesn&#39;t show results immediately. But over time, those small calibrations accumulate into something steady, something strong enough to build on.</p>\n<p>As I started to regain the muscle memories of youth, the most difficult times I&#39;ve had advancing have been when I forget to build on basics. I&#39;ll see a move that looks easy, attempt it without proper preparation, and land on my face — only to realize I need a stronger foundation before I can even think about that technique. After five years of serious skating, I still practice the basics every week. Not because I&#39;ve forgotten them, but because everything else depends on them.</p>\n<p>An avid skier friend once told me about watching a U.S. Olympic gold medalist on the slopes. He expected to see her practicing complex aerial maneuvers or racing down black diamonds. Instead, she spent the entire day drilling fundamentals — turns, stops, weight shifts. The same basics any intermediate skier would practice. The difference wasn&#39;t what she was practicing; it was how deliberately she practiced it. Each repetition was an act of attention, of refinement, of quiet pursuit. She wasn&#39;t chasing novelty — she was tuning precision.</p>\n<p>That&#39;s what separates masters from everyone else: they never graduate from the fundamentals. They understand that excellence isn&#39;t built on advanced techniques layered over shaky foundations — it&#39;s built on basics refined to the point of artistry. She was drilling turns because she understood that mastery at the highest level requires perfecting the foundation, not just maintaining it.</p>\n<p>Every success is built out of thousands of micro-decisions and choices. Her gold medal wasn&#39;t won in the moment she crossed the finish line — it was won in every deliberate turn she practiced on that training day, every choice to focus on form over flash, every decision to drill basics when she could have been showing off. Success accumulates in the small moments when no one is watching.</p>\n<p>I think about this when I watch teams try to implement complex processes without mastering basic communication. Or when I see leaders attempt sophisticated strategies while skipping the foundational work of building trust. The temptation is always to start where you think you should be rather than where you actually are. But the most grounded leaders I&#39;ve encountered share this quality with Olympic athletes: they return to first principles because they understand that mastery flows from the foundation up.</p>\n<p>The best never stop returning to those fundamentals. They know that foundations don&#39;t maintain themselves — they require constant attention, constant refinement. What looks like going backward is actually the only way to keep moving forward. Every quiet correction, every small improvement, every moment of returning to balance is what lets you accelerate later with control and grace.</p>\n<p><em>Low diatribe</em> privileges this rhythm: returning to fundamentals not as regression but as the foundation for everything that follows. The quiet confidence that comes from knowing you can handle the basics, even when everything else gets complicated. Because confidence without practice fades into nostalgia — but confidence grounded in repetition becomes resonance. It hums through everything you build.</p>\n<p>Sometimes the most advanced thing you can do is start at the beginning. Again. And again. And again.</p>\n<p>Maybe even again.</p>\n"
    },
    {
      "id": "https://lowdiatribe.net/reflection/2025-11-04-revisiting-my-why",
      "url": "https://lowdiatribe.net/reflection/2025-11-04-revisiting-my-why",
      "title": "Revisiting my why",
      "date_published": "2025-11-04T19:00:00.000Z",
      "summary": "An archaeological dig into the layers of purpose behind Low diatribe. Beyond the polished mission statement lies the messy reality: writing as processing, vulnerability as strength, and the revolutionary act of admitting you're still becoming. Explores the tension between teaching and learning, and why teachers who admit they're still traveling earn more trust than those who claim to have arrived.",
      "tags": [
        "purpose",
        "vulnerability",
        "growth",
        "authenticity"
      ],
      "content_html": "<p>There&#39;s an archaeology to purpose. Layers beneath the mission statement. The uncomfortable truth that sits under the polished why.</p>\n<p><em>Low diatribe</em> has a clear purpose statement: &quot;A resonance-first storytelling system that privileges quiet authority, iterative craft, and earned trust.&quot; Clean. Declarative. The kind of thing that looks good on an about page.</p>\n<p>But that&#39;s the surface layer. The manifesto version. What I tell others and myself when asked why this exists.</p>\n<p>The deeper layers are messier.</p>\n<p>There&#39;s the operational why: I write because I can&#39;t not write. Because thoughts pile up until they demand attention, rolling around in my head like rocks in a tumbler — and if left too long there would be nothing but dust. Putting words to experience helps me understand what I actually think about things. The writing isn&#39;t just output — it&#39;s processing that preserves the thoughts before they wear away.</p>\n<p>When I was leading domains at Big Book Company, I developed a practice of spending my days building out as complete a context as I was able to. Piecing together countless one-on-ones, team meetings, and organizational discussions with larger public events and trends. It was pattern recognition at scale — connecting dots across conversations, seeing how individual struggles reflected systemic challenges, understanding how external pressures shaped internal dynamics and affected individuals.</p>\n<p>After ending up on the other side of the table in the RIF discussions, I found myself still performing the same thought connections and experiments with no outlet. The mind that had been trained to synthesize organizational complexity didn&#39;t suddenly stop working when the organization no longer needed it. The practice of connecting disparate pieces into coherent understanding had become essential to how I process the world. Writing became the vessel for that continued synthesis.</p>\n<p>Beyond that internal need, there&#39;s also a practical why: adhering to a &quot;publishing schedule&quot; keeps me on task and focused. The commitment to regular reflection creates structure around the chaos of thoughts. It transforms wandering into walking. More importantly, it allows me to reflect against the larger tapestry of the whole — to see patterns emerge across reflections, to notice how thoughts connect and evolve over time. And it forces me to show the messy work, something I&#39;ve found unpleasant my entire life. The discipline of publishing partially polished thoughts, of letting others see the scaffolding before the building is complete.</p>\n<p>Then there&#39;s the vulnerable why, the one that makes me squirm a little: I started this because I was tired of loud leadership drowning out the people doing the actual work. Because I&#39;d sat through too many meetings where the person with the strongest voice got heard, not the person with the best ideas. Because I wanted to create space for the kind of leadership I wished I&#39;d seen more of.</p>\n<p>Which brings me to the uncomfortable part: I&#39;m still figuring out my own frequency while trying to help others find theirs.</p>\n<p>There&#39;s something deeply hypocritical about writing about quiet authority while still learning what that means. About advocating for vulnerability-based leadership while wrestling with my own resistance to being seen. About championing iterative craft while second-guessing every sentence.</p>\n<p>The tension is real. How do you teach what you&#39;re still learning? How do you guide others toward something you&#39;re still walking toward yourself?</p>\n<p>I think the answer lies in embracing the discomfort of that tension rather than resolving it.</p>\n<p>Teachers who admit they&#39;re still traveling earn more trust than those who claim to have arrived. Guides who say &quot;I don&#39;t know the destination, but I know this path&quot; offer something more valuable than those who pretend to have all the answers.</p>\n<p>Maybe the real why isn&#39;t about having figured it out. Maybe it&#39;s about being willing to figure it out in public. To model the kind of leadership that says &quot;I&#39;m learning too&quot; instead of &quot;Follow me, I know the way.&quot;</p>\n<p>There&#39;s another layer: the evolving why. When I started writing these reflections, I thought I was documenting insights. Now I realize I was creating a new practice. A discipline of paying attention to the quiet moments where growth happens. The spaces between certainty where real learning lives.</p>\n<p>The purpose has shifted as the project has grown. What began as sharing thoughts became exploring thoughts. What started as teaching became learning out loud. What felt like offering answers became asking better questions.</p>\n<p>The archaeology reveals something unexpected: the deepest layer isn&#39;t a why at all. It&#39;s a how. How to stay curious when you could claim expertise. How to remain vulnerable when you could build walls. How to keep growing when you could declare yourself grown.</p>\n<p>The manifesto version of my why talks about resonance and quiet authority. The archaeological version is simpler and more complex: I write because growth is uncomfortable, and discomfort shared becomes connection.</p>\n<p>I write because the alternative — pretending I have it figured out — would be a lie. And lies don&#39;t resonate. They echo, hollow and empty.</p>\n<p>But there&#39;s something deeper still: the hope that maybe someone can learn something from my fumbling. That by sharing the messy process of figuring things out, others might find themselves a little more prepared when they face similar challenges. Not because I have the answers, but because I&#39;m willing to show the questions I&#39;m wrestling with. The missteps I&#39;ve made. The patterns I&#39;ve noticed in my own stumbling.</p>\n<p>I&#39;ve been fortunate to stand on the shoulders of leaders and innovators who came before me — people who shared their struggles and insights, who made their own fumbling visible so others could learn from it. Now I find myself in a position where I can offer my own shoulders to the next generation of innovators. Where my stumbles and recoveries might provide a steadier foundation for someone else&#39;s first steps.</p>\n<p>Connection happens in this shared recognition of struggle. In the relief of discovering you&#39;re not the only one who doesn&#39;t have it all figured out. In the quiet comfort of knowing someone else has walked a similar path and lived to tell about it.</p>\n<p>The real why might be this: in a world that rewards certainty, there&#39;s something revolutionary about admitting you&#39;re still becoming. About choosing growth over arrival. About finding strength in the admission that you don&#39;t know everything, but you&#39;re willing to learn anything.</p>\n<p>That&#39;s messier than a mission statement. It doesn&#39;t fit neatly on an about page. But it&#39;s honest in a way that manifestos rarely are.</p>\n<p>That&#39;s the point, isn&#39;t it? The deepest why isn&#39;t about what you&#39;re building — it&#39;s about who you&#39;re becoming while you build it.</p>\n<p>The archaeology of purpose reveals this: beneath every polished mission statement lies a human being trying to figure it out, one reflection at a time.</p>\n<p>And maybe that&#39;s all any of us can offer: the willingness to keep digging, and the courage to share what we uncover along the way. Not the artifacts we uncover, but the process of uncovering them. The hope that in showing our own patient work of excavating truth, others might find their own shovels and join the dig.</p>\n"
    },
    {
      "id": "https://lowdiatribe.net/reflection/2025-10-31-ted-lasso-was-wrong",
      "url": "https://lowdiatribe.net/reflection/2025-10-31-ted-lasso-was-wrong",
      "title": "Ted Lasso was wrong",
      "date_published": "2025-10-31T22:00:00.000Z",
      "summary": "Ted Lasso's relentless optimism and belief in people transformed a football club, but what happens when kindness isn't enough? Explores the dangers of single-source wisdom, the difference between magical thinking and grounded hope, and why the best leaders draw from multiple philosophical traditions rather than wielding a single tool for every situation.",
      "tags": [
        "wisdom",
        "frameworks",
        "balance",
        "leadership",
        "single-source-thinking"
      ],
      "content_html": "<p>Okay, that&#39;s a bit harsh. I shouldn&#39;t say that Ted was wrong, maybe just naive about several key points.</p>\n<p>I really do love Ted Lasso. Ask anyone. The show gave us a masterclass in vulnerability-based leadership, emotional intelligence, and the power of genuine care in building high-performing teams. But here&#39;s the thing: putting all your ideological eggs in one philosophical basket, even a beautiful one, can create dangerous blind spots.</p>\n<p>Ted&#39;s relentless optimism and belief in the power of kindness transformed a struggling football club and touched millions of viewers. His approach worked because it was authentic to who he was and appropriate for the context he found himself in. But what happens when kindness isn&#39;t enough? What happens when optimism becomes denial? What happens when the very strengths that make a leader effective in one situation become liabilities in another?</p>\n<p>I learned this lesson the hard way the second time I hired the wrong tech lead. When EdTech Startup was acquired by Big Book Company, I had to scale the team quickly and needed a capable tech lead who could take over day-to-day operations of a project. The lead I found seemed genuine and spoke passionately about those he&#39;d mentored in the past. He seemed ideal.</p>\n<p>He started out playing well with the others, but I started noticing a belittling and pedantic nature when he would explain things. It turns out that he didn&#39;t handle criticism well, and was even worse at giving it out. I worked with him for weeks, firmly believing that he had it in him to make the changes needed to successfully integrate into the softer tech culture we were building. I kept believing that more support, more encouragement, and more patience would turn things around. I extended every effort and every branch, and like a rock he refused to move.</p>\n<p>Eventually he hit a &quot;red line&quot; event and even my unwavering faith had to be wavered. I had to move the rock, and my delay in doing so had started to erode the foundation of safety I was trying to build. Owning that oversight and working to rebuild the trust brought it back stronger. Not that I recommend fabricating these kinds of situations to engage that trust-building mechanism, but it is good to know that trust can be rebuilt when it takes a hit.</p>\n<p>My experience with the tech lead shows how Ted&#39;s &quot;believe in people&quot; approach can become counterproductive when taken too far. But Ted&#39;s philosophy breaks down in other ways too, particularly around hope itself. He famously rejected the phrase &quot;it&#39;s the hope that kills you,&quot; but the Stockdale Paradox shows he was misguided about this too. Admiral James Stockdale, a prisoner of war for eight years in Vietnam, observed that the prisoners who died were the optimists who believed first they&#39;d be out by Christmas, then Easter, then Thanksgiving. When those dates passed, they died of broken hearts. The survivors maintained unwavering faith they would prevail while confronting the brutal facts of their situation. It&#39;s not hope that kills but the wrong kind of hope. Magical thinking hope versus grounded hope.</p>\n<p>I see this playing out in my own job search right now. The current job market is brutal and frustrating. Every resume sent out could be the one to land successfully, and every &quot;no thank you&quot; response brings another holiday without rescue, which is heartbreaking when you&#39;re expecting a magic end to the struggle. That&#39;s the dangerous hope — the kind that sets specific expectations and timelines that reality doesn&#39;t care about. The harsh facts are that the market is tough, rejection is common, and timing or connections matter as much as qualifications. The grounded hope is that I will eventually find the right opportunity because I keep doing the work to make it happen while facing those realities honestly.</p>\n<p>But Ted&#39;s naiveté goes beyond hope to planning itself. His &quot;my plan is for my plan to work&quot; philosophy is seductive because it feels proactive and optimistic. It suggests that having a clear intention and working toward it should be sufficient. But it&#39;s magical thinking dressed up as strategy. Actually, it&#39;s not even a plan at all — it&#39;s like the underpants gnomes from South Park. Step 1: Collect underpants. Step 2: ??? Step 3: Profit. Ted knows what he wants (step 3: success), but the actual plan is just &quot;for it to work.&quot; There&#39;s no step 2.</p>\n<p>Or maybe I am the one being naive about his tactics. It occurs to me as I write this that his &quot;plan for a plan to work&quot; actually <em>does</em> work in a <a href=\"https://en.wikipedia.org/wiki/Stone_Soup\" target=\"_blank\">stone soup</a> kind of way. Everyone else at Richmond believes that there is a plan, so they bring a little piece of their own, stitching them together into something that actually succeeds. So maybe Ted&#39;s approach isn&#39;t just magical thinking — it could be a specific leadership style that creates space for others to contribute their expertise.</p>\n<p>But that only works when you have a team that believes in you, people with complementary skills willing to contribute, and an environment where collective problem-solving is possible. I wish job hunting were as easy as having a plan for my plan to work. But it doesn&#39;t work like that. I can even have the perfect plan — target the right companies, craft compelling applications, leverage my extended network — but that plan exists in a complex ecosystem in which I have little visibility and even less control. Hiring managers have competing priorities, budgets get frozen, internal candidates emerge, economic conditions shift. My plan can be excellent and still fail because it&#39;s not the only plan in play.</p>\n<p>These examples all point to the same fundamental issue. Ted&#39;s defiance against &quot;it&#39;s the hope that kills you&quot; and his belief that &quot;my plan is for my plan to work&quot; are two sides of the same magical thinking coin — both rely on a kind of deus ex machina where good intentions and positive attitude somehow override reality. Whether it&#39;s endless patience with a problematic employee, misplaced optimism about impossible timelines, or magical thinking about career outcomes, the pattern is the same. This is the danger of single-source wisdom: it gives you a hammer and makes everything look like a nail. Ted Lasso&#39;s approach is powerful, but it&#39;s not universal. Sometimes you need to be direct rather than diplomatic. Sometimes you need to set firm boundaries rather than extending endless grace. Sometimes you need to make hard decisions that disappoint people you care about.</p>\n<p>The leaders I&#39;ve learned the most from draw from multiple philosophical traditions. They might use Ted Lasso&#39;s emotional intelligence in team building, Simon Sinek&#39;s &quot;leaders eat last&quot; principle in crisis management, and Brené Brown&#39;s vulnerability research in culture development. They don&#39;t use the same tools across all situations; they try to be appropriate to each context.</p>\n<p>This requires intellectual humility. The recognition that no single framework, no matter how compelling, can address the full complexity of human leadership. It requires comfort with contradiction. The ability to hold multiple perspectives simultaneously without needing to resolve them into a single coherent system.</p>\n<p>I think about this when I see leaders who&#39;ve become disciples of particular methodologies (whether it&#39;s Agile, Design Thinking, Lean Startup, or any other framework that promises to solve all problems). These approaches all have value, but they also have limitations. The leader who can only think in terms of sprints and retrospectives will struggle with challenges that require different tools.</p>\n<p>The same applies to leadership philosophies. Servant leadership is powerful until you need to make unpopular decisions quickly. Transformational leadership is inspiring until you need to manage day-to-day operations. Democratic leadership builds engagement until you need to cut through analysis paralysis with decisive action.</p>\n<p>This doesn&#39;t mean abandoning frameworks or becoming philosophically rudderless. It means building a toolkit rather than wielding a single tool. It means understanding the contexts where different approaches work best. It means being willing to act against your natural inclinations when the situation demands it.</p>\n<p>Ted Lasso himself actually demonstrated this flexibility in later episodes, showing more directness and setting firmer boundaries when his initial approach wasn&#39;t working. The character evolved beyond his initial framework, which is exactly what real leaders need to do.</p>\n<p>The goal isn&#39;t to find the perfect leadership philosophy but to develop the judgment to know which philosophy serves each moment. Sometimes you need to be the caring coach who believes in people&#39;s potential. Sometimes you need to be the decisive executive who makes hard calls. Sometimes you need to be the vulnerable human who admits they don&#39;t have all the answers.</p>\n<p>These leaders are philosophical omnivores. They study different traditions, experiment with different approaches, and remain curious about perspectives that challenge their existing beliefs. They&#39;re not trying to be everything to everyone; they&#39;re trying to be what each situation needs.</p>\n<p>Think about how they actually build this toolkit. They might read Marcus Aurelius for stoic resilience during crisis, study Toyota&#39;s lean principles for operational efficiency, learn from jazz musicians about improvisation and collaboration, and observe how great teachers create psychological safety. Each influence gets filtered through their own experience and values, transformed into something that fits their context and personality.</p>\n<p>This synthesis takes time and intentional practice. You can&#39;t just read about different leadership styles and expect to deploy them effectively. You have to experiment, fail, adjust, and gradually integrate new approaches into your existing repertoire. It&#39;s like learning to cook: you start with recipes, but eventually you develop your own style by understanding how different techniques and ingredients work together.</p>\n<p>I saw what a void of influences produces in my first 300-level poetry class in college. There was one student who refused to read any other poets because he wanted to &quot;remain pure from influence.&quot; He was convinced that exposure to other voices would contaminate his originality. The irony was devastating: his writing read like generic greeting cards and TV commercials — influences he&#39;d absorbed subconsciously but never transformed into anything new. Meanwhile, the students who studied everything from ancient Greek verse to contemporary slam poetry were developing distinctive voices precisely because they had more raw material to synthesize.</p>\n<p>The same principle applies to leadership. The leaders who avoid studying other approaches don&#39;t become more original; they become prisoners of whatever influences they&#39;ve unconsciously absorbed — usually the most generic and least examined ones. The ones who deliberately expose themselves to different philosophies, frameworks, and perspectives develop the richest and most authentic leadership styles.</p>\n<p>Building a leadership toolkit isn&#39;t about collecting techniques like trading cards or Pokémon. It&#39;s about understanding the underlying principles that make different approaches work, then adapting those principles to your own context and personality. A technique that works brilliantly for a charismatic extrovert might need significant modification for a thoughtful introvert, but the core insight can still be valuable.</p>\n<p>Ted Lasso gave us a beautiful example of one way to lead with heart and humanity. But it&#39;s one way, not <em>the</em> way. The real lesson isn&#39;t to be more like Ted Lasso but to be more like the best version of ourselves, drawing wisdom from wherever we find it and applying it with the same authenticity and care that made Ted so compelling.</p>\n<p>Ted&#39;s success wasn&#39;t just about his philosophy — it was about the environment he created. His unwavering belief in belief itself became contagious, inspiring everyone around him to bring their best selves to the collective effort. When people feel genuinely seen, valued, and trusted, they naturally contribute more than what&#39;s asked of them. Ted&#39;s &quot;plan for a plan to work&quot; succeeded because his belief in the team&#39;s potential created the psychological safety and shared purpose that made everyone else want to add their own piece to the solution.</p>\n<p>Because in the end, the most dangerous thing about any powerful framework isn&#39;t that it&#39;s wrong — it&#39;s that it might be right just often enough to make you forget when it isn&#39;t.</p>\n"
    },
    {
      "id": "https://lowdiatribe.net/reflection/2025-10-28-when-the-game-is-rigged-reprogram-the-simulation",
      "url": "https://lowdiatribe.net/reflection/2025-10-28-when-the-game-is-rigged-reprogram-the-simulation",
      "title": "When the game is rigged, reprogram the simulation",
      "date_published": "2025-10-28T20:00:00.000Z",
      "summary": "Monopoly was originally designed to show why monopolies are destructive, but we kept only the competitive rules and lost the cooperative ones. Explores how finite game thinking dominates systems that need infinite game strategies, and how leaders can reprogram the simulation by playing multiple time horizons simultaneously.",
      "tags": [
        "leadership",
        "systems",
        "strategy",
        "long-term-thinking",
        "business"
      ],
      "content_html": "<p>I remember hundreds of hours spent playing Monopoly growing up, and nearly as many hours fighting about it. The game was supposed to end when one player accumulated everything and everyone else lost everything. It usually ended when the first player to lose it all took revenge against the system by flipping the board. Even as a kid, something about this felt wrong. Not the board flipping — that seemed like the only rational response to a rigged system — but the underlying premise that fun required systematic elimination of everyone else.</p>\n<p>I&#39;ll admit to owning several collector&#39;s editions now — Dr. Who and Nintendo, to be specific — but I don&#39;t play them. There&#39;s something fundamentally troubling about a system where winning requires making everyone else lose. Victory through eradication never sat right with me.</p>\n<p>What I learned later makes the game even more insidious. Monopoly was based on The Landlord&#39;s Game, created by <a href=\"https://en.wikipedia.org/wiki/Lizzie_Magie\" target=\"_blank\">Elizabeth Magie</a> in 1904 as an educational tool. She designed it to demonstrate the destructive effects of land monopolies and promote economic theories that valued productive work over rent extraction.</p>\n<p>Magie&#39;s original game had two rule sets. The first showed how monopolistic thinking creates artificial scarcity and eliminates players. The second demonstrated a cooperative alternative where shared prosperity replaced zero-sum competition. Players could see both outcomes and choose which system they preferred.</p>\n<p>When <a href=\"https://en.wikipedia.org/wiki/Charles_Darrow\" target=\"_blank\">Charles Darrow</a> adapted the game and sold it to Parker Brothers in 1935, they kept only the monopolistic version. Magie&#39;s cooperative rules disappeared entirely.</p>\n<p>The irony is perfect: a game designed to show why monopolies are destructive became the most popular celebration of monopolistic thinking in American culture. We stripped away the lesson and kept only the competition.</p>\n<p>Regular readers will know how much of a fan of <a href=\"https://simonsinek.com\" target=\"_blank\">Simon Sinek</a> I am. <a href=\"https://a.co/d/7To4xe0\" target=\"_blank\">Start With Why</a> put words to my intuitive understanding of how the world works best, and <a href=\"https://a.co/d/1aeXOpt\" target=\"_blank\">The Infinite Game</a> both expanded and coalesced the concepts I&#39;d been struggling with and gave them voice. The market system should reward long-term value creation, sustainable growth, and stakeholder benefit. But the structures we&#39;ve built discourage infinite thinking and reward end-game moves.</p>\n<p>Quarterly earnings calls become the Monopoly board. The goal shifts from building lasting value to extracting maximum short-term profit. Leaders who think in decades get punished by markets that think in quarters. Companies that invest in people, infrastructure, or community building get penalized by analysts who see only costs, not investments.</p>\n<p>We&#39;ve created Elizabeth Magie&#39;s nightmare: a system that rewards monopolistic thinking while forgetting why that&#39;s destructive.</p>\n<p><strong>The finite game trap</strong></p>\n<p>I&#39;ve watched this play out in organizations where I&#39;ve worked. The pressure to hit quarterly numbers creates a cascade of finite thinking. Cut training budgets, delay infrastructure investments, optimize for metrics that increase shareholder value but weaken the foundation for long-term success.</p>\n<p>The most damaging part isn&#39;t the individual decisions but how finite thinking becomes the default mode. Teams start optimizing for what gets measured in the next review cycle rather than what creates lasting value. Innovation gets deprioritized because it&#39;s risky and takes time to pay off. Relationships become transactions because trust-building doesn&#39;t show up on this quarter&#39;s P&amp;L.</p>\n<p>I&#39;ve been that leader who understood infinite game principles but felt trapped by finite game constraints. I knew that investing in people, building trust, and creating sustainable systems would pay dividends over years. But I was evaluated on what happened in the next 90 days. The system punished exactly the thinking it needed most.</p>\n<p><strong>Playing infinite games within finite constraints</strong></p>\n<p>The challenge isn&#39;t choosing between infinite and finite thinking but learning to play infinite games within finite systems. This requires a different kind of strategic thinking.</p>\n<p>I think about James T. Kirk, famous for being the first Starfleet cadet to &quot;beat&quot; the Kobayashi Maru. The scenario was designed to be unwinnable — a test of character under impossible circumstances. Kirk&#39;s solution was elegant in its audacity: he reprogrammed the simulation. When the game is rigged, the only way to win is to change the rules.</p>\n<p>My favorite leaders do exactly this. They don&#39;t accept the premise that short-term and long-term thinking are mutually exclusive. They find ways to rewrite the rules of engagement.</p>\n<p>I&#39;ve found that these leaders develop what I call &quot;nested game awareness.&quot; They understand they&#39;re playing multiple games simultaneously: the quarterly performance game, the annual growth game, the multi-year market position game, and the decades-long reputation and relationship game. They make moves that serve multiple time horizons.</p>\n<p>This might mean hitting quarterly targets while also investing in capabilities that won&#39;t pay off for years. It means building relationships that create options for future collaboration, even when there&#39;s no immediate business case. It means making decisions that preserve trust and reputation, even when shortcuts are available.</p>\n<p><strong>What this looks like in practice</strong></p>\n<p>As a kid, skating was simple. Go fast. Don&#39;t fall. Win the race around the rink. Every lap had a finish line and every tumble felt like failure. I skated to prove something — speed, balance, control.</p>\n<p>Decades later, standing in a pair of rental skates that felt foreign and heavy, I realized the race was long over. Nobody was timing me. Nobody cared how clean my turns were. The only opponent left was my own expectation that I should still &quot;have it.&quot;</p>\n<p>The first few laps were humbling. My body remembered the rhythm, but not the reflexes. I kept trying to muscle through the wobbles — finite thinking in motion. Every slip felt like losing. Every fall made me want to correct faster, master sooner, prove I could still dominate a game no one else was playing.</p>\n<p>It took a few bruises before I caught the deeper lesson: skating wasn&#39;t about winning at all. It was about continuity. You don&#39;t &quot;win&quot; at skating. You stay upright long enough to find the flow again. You keep moving, adjust your weight, rediscover balance with each glide. You fall, you laugh, you get back up. The only way to lose is to stop.</p>\n<p>That&#39;s infinite thinking: learning to value the movement itself more than the metrics that measure it. This is what it looks like in finite systems — making choices that serve multiple time horizons simultaneously. Not compromising on values while still delivering results. Building trust and capability even while navigating short-term pressures.</p>\n<p><strong>The compound effect</strong></p>\n<p>I&#39;ve learned that infinite game thinking creates compound advantages that eventually show up in finite game metrics. Teams with high trust move faster when speed matters. Organizations with strong cultures attract better talent. Companies with sustainable practices become more resilient when markets shift.</p>\n<p>The leaders who consistently outperform aren&#39;t the ones who optimize purely for short-term results. They&#39;re the ones who build systems and relationships that create sustainable competitive advantages. They understand that the best way to win finite games is to play infinite games.</p>\n<p>This requires patience, discipline, and the courage to make decisions that might not pay off immediately. It means resisting the Monopoly mindset that says winning requires making others lose. It means building systems where everyone can succeed.</p>\n<p>Elizabeth Magie&#39;s original game was designed to show that cooperation creates more value than competition. Her lesson got lost when we stripped away the cooperative rules and kept only the competitive ones. I keep thinking about what would happen if we dusted off those old Monopoly boards and played by <a href=\"https://landlordsgame.info/games/lg-1906/lg-1906_egc-rules.html\" target=\"_blank\">Magie&#39;s original rules</a> — starting with the monopolistic version to see how quickly it creates inequality, then voting to implement the Single Tax rules and watching the game transform into something entirely different.</p>\n<p>We don&#39;t need a board game to make this choice. Every day, leaders face the same decision Magie built into her design: do we play by rules that require others to lose for us to win, or do we choose systems that create shared prosperity? The winning-ist leaders don&#39;t just play infinite games in finite systems — they gradually transform those systems to reward infinite thinking. After all, the goal shouldn&#39;t be to bankrupt everyone else. It&#39;s to build something that lasts.</p>\n"
    },
    {
      "id": "https://lowdiatribe.net/reflection/2025-10-24-its-a-great-big-universe",
      "url": "https://lowdiatribe.net/reflection/2025-10-24-its-a-great-big-universe",
      "title": "It's a great big universe, and we're all really puny",
      "date_published": "2025-10-24T20:00:00.000Z",
      "summary": "We understand less than 5% of the universe, yet make decisions with startling confidence. Explores cosmic humility as a leadership superpower—the ability to act decisively on limited information while staying open to what we don't know. In a universe where we're statistically operating from near-complete ignorance, perhaps radical humility paired with decisive action is the most rational position.",
      "tags": [
        "humility",
        "knowledge",
        "leadership",
        "perspective",
        "uncertainty"
      ],
      "content_html": "<p>The <a href=\"/api/easter-egg/universe_scale?redirect=/eastereggs/universe-scale.html\" title=\"Journey from quantum to cosmic\" target=\"_blank\">universe</a> is big, like, <em>really</em> big. Douglas Adams captured it in a way that has stuck with me ever since my first read of Hitchhiker&#39;s Guide to the Galaxy over forty years ago: &quot;Space is big. You just won&#39;t believe how vastly, hugely, mind-bogglingly big it is. I mean, you may think it&#39;s a long way down the road to the chemist&#39;s, but that&#39;s just peanuts to space.&quot; The math behind this is humbling. If the universe is infinite and we can only perceive a tiny slice of it, then statistically, we&#39;re operating from near-complete ignorance. We know almost nothing about almost everything.</p>\n<p>I like watching Star Talk, drawn to Neil deGrasse Tyson&#39;s way of making the cosmos comprehensible. In one episode, he mentioned that everything we can observe — all the stars, planets, galaxies, and cosmic phenomena that fill our telescopes and textbooks — represents less than 5% of what actually exists in the universe. The other 95% is dark matter and dark energy, which we can detect only through their gravitational effects but cannot directly observe or understand.</p>\n<p>Worse yet, these forces are accelerating the expansion of the universe. At some point, other observable galaxies will be pushed past our horizon. Future scientists will have huge swaths of the puzzle blanked out entirely. Tyson admits this keeps him up at night — wondering what events have already been occluded from us as observers. There are things we will <em>never</em> be able to know, and we have zero knowledge of them.</p>\n<p>As he put it: &quot;We are prisoners of the present, in perpetual transition from an inaccessible past to an unknowable future.&quot; Most of what we call &quot;knowledge&quot; is just stuff we made up and agreed to call true. We&#39;re not just missing pieces of the puzzle; we don&#39;t even know what most of the puzzle looks like.</p>\n<p>I have started to think that our &quot;understanding&quot; of the universe is equivalent to a toddler claiming they know how a school bus works, because, you know, it&#39;s yellow.</p>\n<p>The scale itself compounds the problem. Adams had another take on infinity that captures the absurdity: &quot;Infinite: Bigger than the biggest thing ever and then some. Much bigger than that in fact, really amazingly immense, a totally stunning size, real &#39;wow, that&#39;s big,&#39; time. Infinity is just so big that, by comparison, bigness itself looks really titchy. Gigantic multiplied by colossal multiplied by staggeringly huge is the sort of concept we&#39;re trying to get across here.&quot;</p>\n<p>Infinity is such a weird concept. Something that helped me start to wrap my head around this weirdness was learning about the infinity hotel — Hilbert&#39;s paradox where a hotel with infinite rooms can always accommodate more guests, even when completely full. Say one person shows up at the front desk. No problem — move the guest from room 1 to room 2, from 2 to 3, and so on, all the way to infinity, freeing up room 1 for the newcomer.</p>\n<p>A bus arrives with infinite people? Still manageable. Move everyone to double their room number — the guest in room 1 goes to room 2, room 2 goes to room 4, and so forth. This frees up the infinite odd-numbered rooms (1, 3, 5, 7...) for all the new arrivals from the bus. </p>\n<p>But here&#39;s where it gets truly mind-bending: an infinite number of buses show up, each carrying infinite people. Somehow, there&#39;s still room. Move the current guests to double their room number again, then assign each bus to a prime number and its multiples. Since there are infinite primes, the math checks out. QED.</p>\n<p>If infinity itself breaks our intuitive understanding of &quot;full&quot; and &quot;empty,&quot; what hope do we have of grasping the true scale of what we don&#39;t know?</p>\n<p>This perspective shift has profound implications for how we approach leadership and decision-making. If our collective human knowledge represents such a tiny fraction of reality, what does that say about the confidence with which we make strategic decisions, design organizational structures, or predict market behaviors?</p>\n<p>I&#39;ve found that the most effective leaders carry this cosmic humility with them. They make decisions with conviction while holding their conclusions lightly. They plan for the future while acknowledging that their models are almost certainly incomplete. They lead with authority while remaining genuinely curious about what they might be missing.</p>\n<p>This isn&#39;t paralysis by analysis or decision-making by committee. It&#39;s something more nuanced: the ability to act decisively based on limited information while staying open to new data that might change everything. It&#39;s confidence paired with intellectual honesty about the boundaries of that confidence.</p>\n<p>In practice, this looks like saying &quot;Based on what we know today, I think we should...&quot; instead of &quot;This is definitely the right approach.&quot; It means asking &quot;What would change our minds?&quot; when making strategic decisions. It&#39;s the difference between &quot;Our projections show...&quot; and &quot;Our best guess, given these assumptions, suggests...&quot; Small language shifts that preserve authority while acknowledging uncertainty.</p>\n<p>I&#39;ve learned to create explicit space for &quot;I don&#39;t know&quot; in leadership conversations. When someone asks a question I can&#39;t answer, I say so directly, then follow with what I do know and how we might find out more. This doesn&#39;t undermine credibility — it builds trust. People respect leaders who can distinguish between what they know and what they&#39;re guessing at.</p>\n<p>I think about this when I&#39;m in meetings where people speak with absolute certainty about complex systems, market dynamics, or human behavior. The more certain someone sounds about inherently uncertain things, the more skeptical I become. Not because they&#39;re necessarily wrong, but because certainty in the face of cosmic ignorance often signals a failure to grasp the scope of what we don&#39;t know.</p>\n<p>The paradox is that acknowledging our ignorance can actually make us more effective, not less. When we accept that our mental models are approximations rather than truth, we become more adaptable when reality doesn&#39;t match our expectations. When we recognize that our perspective is limited, we become more curious about other viewpoints. When we admit that our knowledge has boundaries, we become more careful about the decisions that matter most.</p>\n<p>This doesn&#39;t mean abandoning expertise or treating all opinions as equally valid. The surgeon still needs to know anatomy, the engineer still needs to understand physics, the leader still needs to grasp organizational dynamics. But it does mean holding that expertise within a larger context of humility about what remains unknown.</p>\n<p>I&#39;ve started thinking of knowledge not as a collection of facts but as a set of useful approximations. The map is not the territory, but a good map can still help you navigate. The model is not reality, but a useful model can still guide decisions. The framework is not truth, but a solid framework can still create clarity.</p>\n<p>The best leaders I know are deeply knowledgeable about their domains while remaining genuinely humble about the limits of that knowledge. They can make tough calls based on incomplete information while staying curious about what they might be missing. They lead with conviction while maintaining what Zen practitioners call &quot;beginner&#39;s mind&quot; — the openness to learning that comes from not assuming you already know everything.</p>\n<p>Here&#39;s where cosmic humility becomes empowering rather than paralyzing: in almost all of our human interactions, we have more complete knowledge of the space. Unlike the vast unknowable universe, the systems we navigate daily are human creations. We made this all up.</p>\n<p>Business structures, stock markets, governments, organizational hierarchies — none of these exist in nature. They&#39;re human inventions, created by people who knew far less than we do now about psychology, systems thinking, network effects, or behavioral economics. It has me asking: what didn&#39;t we know when we built these systems?</p>\n<p>The founders of the stock market didn&#39;t understand high-frequency trading or algorithmic manipulation. The designers of corporate hierarchies had no concept of remote work or distributed teams. The architects of democratic institutions couldn&#39;t foresee social media&#39;s impact on information flow. They built with the knowledge they had, not the knowledge we have.</p>\n<p>And with that I think there&#39;s an opportunity to unmake the parts that no longer serve. If we can acknowledge our cosmic ignorance about the universe while recognizing our growing understanding of human systems, we can redesign what we&#39;ve outgrown.</p>\n<p>In a universe where we understand less than 5% of what exists, perhaps the most rational position is radical humility paired with decisive action. We act on what we know while remaining open to what we don&#39;t. We lead with confidence while acknowledging that confidence has limits.</p>\n<p>After all, if we&#39;re going to be wrong about most things — and statistically, we are — we might as well be wrong with curiosity, adaptability, and grace.</p>\n"
    },
    {
      "id": "https://lowdiatribe.net/reflection/2025-10-21-what-remains-when-everything-changes",
      "url": "https://lowdiatribe.net/reflection/2025-10-21-what-remains-when-everything-changes",
      "title": "What remains when everything changes",
      "date_published": "2025-10-21T20:00:00.000Z",
      "summary": "If every plank of a ship gets replaced, is it still the same ship? The Ship of Theseus paradox applied to teams, identity, and leadership. Explores what persists through constant change, how to preserve essence while allowing form to evolve, and why real vitality lies in changing what needs to change while preserving what gives you strength.",
      "tags": [
        "identity",
        "change",
        "transformation",
        "continuity",
        "leadership"
      ],
      "content_html": "<p>If everything about us changes over time, what makes us still us?</p>\n<p>Almost two millennia ago the historian Plutarch asked: if you replace every plank of a ship, one by one, until none of the original material remains, is it still the same ship? Philosophers have debated this since, exploring what makes something essentially itself. The question for me isn&#39;t whether it&#39;s still the Ship of Theseus, but what makes the Ship of Theseus the Ship of Theseus in the first place.</p>\n<p>Consider the Chicago Bears. Not a single player from their legendary 1985 Super Bowl XX championship team remains on today&#39;s roster. The coaches, the playbook, even the stadium has been rebuilt. Yes, it&#39;s still Soldier Field and yes, they&#39;re still da Bears — but do they <a href=\"/api/easter-egg/super_bowl_shuffle?redirect=/eastereggs/super-bowl-shuffle.html\" target=\"_blank\">Shuffle</a>? For that matter, look at any professional sports league — the constant churn of players, managers, and staff means the team you support this season shares only some of last season&#39;s incarnation, and is at best a hint of what the next will bring, yet the identity persists.</p>\n<p>This pattern shows up everywhere I look, especially as I watch engineering teams evolve over time. The development team I built three years ago doesn&#39;t even exist anymore, yet the culture of it lives on in an expanded and distributed form. The people have scattered to different teams, different companies, different countries. Our codebase has been rewritten. The problems we solve, the tools we use, even the company&#39;s mission has shifted. Yet somehow, something essential persists through all the change.</p>\n<p>The same is true for my own life. Twelve years ago I was leading a small team at a music startup, convinced I knew what leadership meant. Nine years ago I was a tiny IC cog in a monolithic organization, learning humility and a deep distaste for the segmented and disparate way organizations have evolved to scale. Six years ago I began to spread my actual leadership wings, discovering what it meant to scale people and culture alongside code. Three years ago I embarked on a quest to integrate human-first leadership into the corporate world, learning that change happens in pockets and that sometimes the corporate juggernaut is too massive to redirect — but the experiment was worth it.</p>\n<p>Today I am in search of my next adventure and working to capture my thoughts along the way. Each phase feels like a different person lived it, yet somehow it&#39;s all me. I am the accumulation of all these experiences, but somehow not the same person at all. The paradox lives in each of us.</p>\n<p>But here&#39;s what I&#39;ve started to understand: if we are indeed the accumulation of our experiences, then we have more agency than we think. We can, in a sense, gamify our systems. Every day we choose which experiences to seek, which conversations to have, which challenges to embrace. We can reinforce old neural pathways or forge new ones. We can feed our accumulating self better inputs.</p>\n<p>This isn&#39;t about self-optimization or life hacking. It&#39;s about recognizing that change is happening whether we direct it or not. The question becomes: do we want to be passive recipients of whatever experiences come our way, or active curators of our own transformation?</p>\n<p>But this brings me back to the original puzzle. If we&#39;re constantly changing, constantly accumulating new experiences and shedding old patterns, what is that something that persists? What makes us recognizably us through all the transformation?</p>\n<p>Maybe it&#39;s patterns. The way decisions get made. The quality of conversations. The standards people hold themselves to. The spoken, and unspoken, agreements about what matters and what doesn&#39;t. These invisible structures seem to survive complete turnover of people and technology while maintaining something essential.</p>\n<p>Here&#39;s the twist: those same patterns must evolve or they become constraints rather than enablers. The team that clings too tightly to &quot;how we&#39;ve always done things&quot; will find itself trying to solve tomorrow&#39;s problems with yesterday&#39;s tools. The team that changes everything all at once loses the institutional knowledge that made it effective in the first place.</p>\n<p>There&#39;s something like an art in changing deliberately while preserving what&#39;s worth keeping. It&#39;s like renovating a house while living in it: you have to maintain structural integrity while upgrading the systems that no longer serve you.</p>\n<p>I&#39;ve watched leaders struggle with this balance — I struggle with this balance. Some try to preserve everything, creating museums instead of organizations. Others embrace change so completely that they lose the cultural DNA that made their teams special. I lean towards the sentimental side and have to actively push myself to distinguish between nostalgia and canon, but I do my best to treat organizational identity like a river: always flowing, always changing, but maintaining a recognizable shape and direction.</p>\n<p>This seems to require a different kind of thinking about continuity. What if instead of asking &quot;how do we stay the same?&quot; we asked &quot;what do we want to carry forward?&quot; What if instead of preserving specific practices, we preserved the principles behind those practices? What if instead of maintaining rigid structures, we maintained adaptive capacity?</p>\n<p>When I work with teams going through major transitions, this philosophy becomes essential. Mergers, acquisitions, reorganizations, technology migrations, leadership changes — all the disruptions that make people wonder if they&#39;re still working for the same company. The teams that navigate these transitions well don&#39;t try to prevent change; they put forth effort to guide it intentionally.</p>\n<p>They identify the core values and practices that define their culture, then figure out how to express those values in new contexts. They preserve the essence while allowing the form to evolve. They maintain continuity of purpose while embracing discontinuity of method.</p>\n<p>Growth at scale looks like transformation, not addition. Becoming what you need to be while staying true to what matters most. Plutarch&#39;s ship isn&#39;t the same ship, but it&#39;s still a ship. It still carries people across the water. It still serves its essential purpose.</p>\n<p>Identity, then, isn&#39;t about maintaining the same components but about maintaining the same essence. The team that can solve new problems, adapt to new constraints, and serve new needs while preserving its core character — that&#39;s a team with a strong sense of identity. Not because it never changes, but because it changes well.</p>\n<p>The paradox resolves when you realize that staying the same and changing completely are both forms of death. Real vitality lies in the space between: changing what needs to change while preserving what gives you strength. Growing into who you need to become while remembering who you&#39;ve always been.</p>\n<p>There&#39;s something transformational about embracing this constant change rather than resisting it. When we stop trying to maintain a fixed version of ourselves and start seeing change as the raw material of growth, everything shifts. We become less attached to who we were and more curious about who we&#39;re becoming.</p>\n<p>This is where the real power lies: in recognizing that we are always in the process of becoming. Every conversation shapes us. Every challenge rewires us. Every choice we make is both an expression of who we are and a vote for who we want to be. We are simultaneously the sculptor and the sculpture, constantly reshaping ourselves through the experiences we choose to engage with.</p>\n<p>Which brings us full circle. In the end, we are all ships of Theseus. Every cell in our bodies replaces itself over time. Every thought we think changes our neural pathways. Every experience we have shifts our perspective. We are never exactly the same person we were yesterday, yet something essential persists through all the change.</p>\n<p>That something is our capacity to grow while remaining ourselves. To adapt while maintaining integrity. To transform while preserving what makes us who we are.</p>\n<p>I think about the person I was when I first started building teams, convinced that consistency meant never changing course. Then I think about who I am now — still asking the same fundamental questions about how to create environments where people thrive, but with completely different answers. The questions persist; the solutions evolve.</p>\n<p>We sail on, renewed and recognizable. Not because we&#39;ve avoided the storms or kept our original planks intact, but because we&#39;ve learned to rebuild ourselves while staying true to our essential purpose. The horizon keeps shifting, and so do we — carrying forward what serves us, leaving behind what doesn&#39;t, always becoming who we need to be for the journey ahead.</p>\n"
    },
    {
      "id": "https://lowdiatribe.net/reflection/2025-10-17-the-archer-and-the-application",
      "url": "https://lowdiatribe.net/reflection/2025-10-17-the-archer-and-the-application",
      "title": "The archer and the application",
      "date_published": "2025-10-17T20:00:00.000Z",
      "summary": "Archery and job searching operate on remarkably similar principles of preparation and release, but with vastly different feedback loops. Explores the vulnerability of putting your best shot forward, the paradox of holding on completely while letting go completely, and why perfecting your stance matters more than adjusting for unknowable variables.",
      "tags": [
        "career",
        "metaphor",
        "craft",
        "vulnerability"
      ],
      "content_html": "<p>I&#39;ve been fascinated by bows and arrows ever since I realized you could string a rubber band on a clothespin to launch toothpicks at action figures. Later, as I learned more about the actual physics of archery in the scouts, it deepened the appreciation. Something about the discipline appealed to me then: the way it demanded both precision and patience, the honest feedback of arrow meeting target. Or not meeting it. There was something pure about that immediate truth.</p>\n<p>I used to spend a lot of time out on my home range, but over the last year or so it tapered off, because, life. I&#39;ve been slowly getting back into it lately, pulled back to the quiet ritual of draw and release. The concentration required. The way preparation distills into a single moment of focus, steady and completely present. There&#39;s a meditation in the repetition, a clarity that comes from reducing everything to stance, breath, and release.</p>\n<p>The other day, I found myself going over a cover letter and resume for the sixth or seventh time, re-re-reading my answers to the application buzzword questionnaire — and then doing it all one more time before hitting &quot;submit.&quot; That familiar anxiety of perfectionism, the desperate hope that one more revision might make the difference. That&#39;s when the connection crystallized.</p>\n<p>Archery and job searching operate on remarkably similar principles, though the feedback loops couldn&#39;t be more different.</p>\n<p>In archery, preparation is everything. Hours spent perfecting your stance, your grip, your draw. Learning to breathe with the bow, to feel the string&#39;s tension as an extension of your intention. You practice until the motion becomes muscle memory, until you can hit the target without consciously aiming at it. The bow becomes an instrument of accumulated discipline.</p>\n<p>There&#39;s something profound about the moment of release: when you let go of the string, the arrow begins its journey and will hit exactly where you sent it, whether or not that&#39;s where you aimed. The arrow doesn&#39;t lie. It carries forward every micro-adjustment in your form, every tremor in your grip, every inconsistency in your stance. Physics is honest in a way that hope isn&#39;t. The target reveals truth without sentiment.</p>\n<p>The job search operates on similar principles of preparation and release. The same discipline manifests as resume crafting, portfolio polishing, interview preparation. Years of building skills, collecting stories, learning to articulate your value in ways that resonate with strangers. You practice your pitch until it feels natural, until you can tell your story without stumbling over the parts that used to make you wince. You refine your narrative until it carries the weight of genuine experience rather than desperate positioning.</p>\n<p>But all of that preparation — every hour at the range, every revision of your resume — distills into a single moment. The release.</p>\n<p>In archery, there&#39;s a paradox: you must hold on completely and let go completely, almost simultaneously. Too much grip and you&#39;ll torque the shot. Too little and you lose control entirely. The perfect release requires trust — trust in your preparation, trust in the process, trust that you&#39;ve done everything you can do. The string leaves your fingers carrying the accumulated weight of all your practice.</p>\n<p>Hitting submit on a job application carries identical weight. All the craft, all the time, all the careful positioning — it distills into one click. And then it&#39;s gone. Out of your hands. Flying toward a target you can&#39;t see, through air currents you can&#39;t predict, toward evaluators whose criteria you can only guess at. The application carries forward every choice you made about how to present yourself, every story you chose to tell or omit.</p>\n<p>The vulnerability is the same. You&#39;ve put your best shot forward, literally and figuratively. Now you wait to see if it finds its mark.</p>\n<p>Here&#39;s where the metaphor reveals something crucial about feedback loops. In archery, you release your arrow and immediately see where it lands. Miss left? Adjust your sight. Arrow drops low? Check your form. The feedback is instant, visible, actionable. You can see the relationship between your input and the outcome.</p>\n<p>The job hunt operates as a black box. You release your arrow — submit your application — and receive only the equivalent of &quot;We&#39;ll let you know if you hit the target.&quot; No sight of where it landed. No understanding of what went wrong or right. Just silence, or at best, a form rejection that offers no insight into why you missed. The target remains invisible, the criteria unknowable.</p>\n<p>This realization shifted everything: I&#39;ve been thinking about this wrong. I&#39;ve spent hours crafting custom resumes and cover letters, trying to adjust my shot based on feedback I don&#39;t have and probably won&#39;t get. Tweaking my approach for each application as if I could somehow correct for variables I can&#39;t see or understand. Chasing ghosts of imagined preferences.</p>\n<p>The insight demands an inversion of effort. Instead of constantly adjusting my arrows, I need to perfect my stance. Stay steady in my beliefs, consistent in my presentation, disciplined in my craft. Send the same quality arrows out, trusting that eventually one will find the right target. The archer who changes their form with every shot never develops consistency.</p>\n<p>This shift reframes rejection entirely. In archery, a miss isn&#39;t a failure of character — it&#39;s information. Wind conditions, stance adjustment, sight calibration. You note what happened, make small corrections, and draw again. The miss teaches you something about the next shot.</p>\n<p>The job search asks for the same mindset, but stretched across weeks or months instead of minutes. Each application becomes a shot. Each rejection becomes data — though data filtered through unknowable criteria and organizational politics. Each interview becomes practice for the next release, though you&#39;re never quite sure what you&#39;re practicing for.</p>\n<p>Like archery, the real skill isn&#39;t in any single shot. It&#39;s in the consistency of your form, the steadiness of your practice, the patience to keep drawing and releasing until you find your mark. The discipline to trust your preparation when the feedback loop offers only silence.</p>\n<p>The archer understands something the anxious job seeker often forgets: you don&#39;t control where the arrow lands. You only control the quality of your release. The honesty of your stance. The steadiness of your draw. The trust in your preparation.</p>\n<p>In both archery and job searching, mastery lies not in hitting every target, but in the integrity of your form. In showing up consistently with your best shot, regardless of outcomes you can&#39;t control. In trusting that good arrows, released with discipline and patience, will eventually find their mark.</p>\n<p>That&#39;s enough. It has to be.</p>\n"
    },
    {
      "id": "https://lowdiatribe.net/reflection/2025-10-14-when-the-question-isnt-the-question",
      "url": "https://lowdiatribe.net/reflection/2025-10-14-when-the-question-isnt-the-question",
      "title": "When the question isn't the question",
      "date_published": "2025-10-14T20:00:00.000Z",
      "summary": "A great interview followed by rejection reveals the gap between what we think they're asking and what they actually want to know. Explores the difference between leaders who build trust and managers who enforce control, and why misalignment at the interview stage is mercy, not loss. Sometimes the right 'no' is just your signal finding its way home.",
      "tags": [
        "leadership",
        "management",
        "interviews",
        "authenticity",
        "trust",
        "systems"
      ],
      "content_html": "<p>There&#39;s something unsettling about the questions we don&#39;t ask about the questions we <em>do</em> ask.</p>\n<p>How often do we assume we understand what someone really wants to know? How quickly do we fill in the gaps with our own best intentions, answering the question we wish they&#39;d asked instead of the one they actually did?</p>\n<p>One recent Wednesday, I had what felt like a great interview. The kind where the conversation flows naturally, where you can represent your most authentic self without performance or rehearsed answers designed to hit keyword checkboxes. Just honest stories about the teams I&#39;d built, the challenges we&#39;d navigated together, the quiet satisfaction of watching people grow into roles they didn&#39;t know they were capable of.</p>\n<p>The energy was good. The questions felt thoughtful. We talked about next steps with what seemed like mutual alignment, and I left the conversation feeling genuinely positive about the experience.</p>\n<p>The next Monday morning came.\nA friendly message, polite tone, and a clear no.</p>\n<p>No next steps. No feedback. Just the familiar silence that follows a door quietly closing.</p>\n<p>For a while, I replayed the call in my head, searching for red flags.\nDid I say something off? Miss a signal? Talk too long? Too little?</p>\n<p>But it wasn&#39;t until I was telling a friend about the rejection that I started to see the real disconnect. As I walked through the questions they&#39;d asked, something clicked. The problem wasn&#39;t how I answered — it was what I was answering to.</p>\n<p>I had filled in assumptions, based on best intent, that the subtext of their questions didn&#39;t actually support.</p>\n<p>They&#39;d asked a number of standard leadership questions: <em>&quot;What is your go-to interview question?&quot;</em> <em>&quot;How did you keep the team motivated through the acquisition?&quot;</em> All of which I had answered thoughtfully, hoping that my passion for building cohesive teams would come through clearly.</p>\n<p>But as I tapped out the questions via text, one of them stuck out:</p>\n<p><em>&quot;Can you talk about a time when you had a team member who wasn&#39;t performing and had to be let go? What did you do?&quot;</em></p>\n<p>In the moment, it had felt like a straightforward leadership question. I told the truth with the bravado of thinking I had the perfect answer: I&#39;ve never had to let someone go purely for underperformance. In the few cases where someone was struggling, we worked together to find out why. We got them coaching, training, or clarity. In one case, we moved them to a different role that fit their strengths better. The only person I&#39;ve had to let go was for HR violations — creating a hostile environment that harmed the team.</p>\n<p>During the call, this felt like the right answer. It demonstrated care, development focus, and attention to root causes. I thought it showed leadership.</p>\n<p>But telling my friend about it later, I heard something different in my own words. A disconnect between what I thought they were asking and what they might have actually wanted to know.</p>\n<p>I should have asked for clarification, rather than assuming they wanted what I would want. I should have asked if current issues were driving the question.</p>\n<p>Because for many organizations, that question isn&#39;t really about empathy or development — it&#39;s a proxy for decisiveness. They want to know if you can pull the trigger. If you&#39;re comfortable enforcing the hard line. If you&#39;ll protect the company from liability, even at the cost of individual compassion.</p>\n<p>What I had answered was the question I wished they were asking: <em>How do you develop people? How do you build systems that prevent performance issues?</em></p>\n<p>What they may have actually been asking was: <em>Will you fire people when we tell you to?</em></p>\n<p>The gap between those two questions is everything.</p>\n<p>Because my experience has been that by the time someone&#39;s &quot;not performing,&quot; the system has already failed them. The support wasn&#39;t there. The expectations weren&#39;t clear. The environment wasn&#39;t safe enough to ask for help. Fix that, and most &quot;underperformance&quot; stories disappear before they start.</p>\n<p>The next question confirmed what I could only see in retrospect.</p>\n<p><em>&quot;How would you describe your management style?&quot;</em></p>\n<p>During the interview I had paused, not because I didn&#39;t know the answer, but because the question felt incomplete. I don&#39;t really have a management style. I have a leadership philosophy.</p>\n<p>So that&#39;s how I answered, describing my generalized theories about leadership and productivity, starting with, &quot;If people need managing, they wouldn&#39;t be here. They need leading.&quot;</p>\n<p>In the moment, it felt like a thoughtful distinction. But hearing myself say it again, I could imagine how it might have landed: as someone who doesn&#39;t understand the practical realities of getting work done. Someone who deals in abstractions rather than execution.</p>\n<p>That&#39;s when I realized I&#39;d been answering the questions I wanted them to ask, not the ones they were actually asking.</p>\n<p>They wanted to know: <em>How do you control outcomes?</em>\nI answered: <em>How do you cultivate capability?</em></p>\n<p>They wanted: <em>How do you manage performance?</em>\nI answered: <em>How do you build trust?</em></p>\n<p>What they wanted was a manager.</p>\n<p>What I described was a leader.</p>\n<p>There&#39;s a big difference.\nOne is about control. The other is about connection.\nOne enforces expectation. The other expands potential.\nOne protects systems. The other builds trust inside them.</p>\n<p>Both are important. But they operate on different frequencies.</p>\n<p>The manager asks: <em>How do I make people do their best work?</em>\nThe leader asks: <em>How do I create conditions where people can&#39;t help but do their best work?</em></p>\n<p>The manager requires authority.\nThe leader requires trust.</p>\n<p>The manager focuses on performance.\nThe leader cultivates capability.</p>\n<p>In my experience, the second is harder, slower, and infinitely more rewarding. It builds teams that outlast you. It turns processes into habits and habits into culture. It doesn&#39;t require constant supervision because people internalize the &quot;why,&quot; not just the &quot;how.&quot;</p>\n<p>But that kind of approach doesn&#39;t always fit cleanly inside traditional job descriptions. It doesn&#39;t sound assertive in a thirty-minute interview. It&#39;s hard to measure and easy to misunderstand.</p>\n<p>Especially when a company says &quot;Head of Engineering&quot; but still means &quot;Senior Project Manager with veto power.&quot;</p>\n<p>After the rejection, I sat with that discomfort for a day or so.</p>\n<p>I was still disappointed. But the more I reflected, the more I realized this wasn&#39;t really about me at all. It was about something much bigger — a fundamental disconnect in how we think about leadership itself.</p>\n<p>I started to wonder how many other conversations I&#39;d misread this way.</p>\n<p>Maybe we keep asking candidates about firing people and oversight styles because we&#39;ve confused authority with accountability. We measure decisiveness instead of discernment. We equate being &quot;in charge&quot; with being in control.</p>\n<p>But genuine influence doesn&#39;t always look decisive. Sometimes it looks like listening longer, sitting with ambiguity until the right next move becomes clear. It looks like trust — not dominance.</p>\n<p>When done well, it can even make management feel unnecessary.\nBecause a well-led team manages itself.</p>\n<p>That&#39;s the quiet irony.\nWe say we want one thing, but somehow we still build systems that reward the other.</p>\n<p>Leaders build teams who don&#39;t need supervision.\nManagers build systems that can&#39;t function without them.\nLeaders work themselves slowly out of a job.\nManagers design roles that reinforce their necessity.</p>\n<p>So when someone asks, <em>&quot;What&#39;s your management style?&quot;</em> and you answer, <em>&quot;I build teams that don&#39;t need managing,&quot;</em> it sounds risky. Radical, even. It shouldn&#39;t be.</p>\n<p>Perhaps we&#39;ve gotten so used to crisis-based authority that calm, capable autonomy reads as absence. We interpret trust as neglect, freedom as chaos, humility as indecision. But real influence isn&#39;t about holding control — it&#39;s about holding space.</p>\n<p>I don&#39;t regret my answers.\nThey were honest, and they reflected the kind of systems I want to build:</p>\n<p><em>Where people grow through clarity, not pressure.</em></p>\n<p><em>Where performance problems are signals, not punishments.</em></p>\n<p><em>Where process serves people, not the other way around.</em></p>\n<p>If that disqualified me, so be it. Because misalignment at the interview stage is mercy, not loss.</p>\n<p>This rejection clarified my own signal.\nIt reminded me what I stand for — and what I won&#39;t compromise to fit in.\nIt was resonance feedback: a soft &quot;not here&quot; from the universe.</p>\n<p>Still, it leaves me thinking about the bigger pattern.\nWhy do we keep hiring for the old paradigm? What makes us so afraid of teams that run without handlers? How did &quot;authority&quot; become synonymous with &quot;control&quot; in most org charts?</p>\n<p>Maybe because control feels safer than trust.\nTrust requires vulnerability, and vulnerability doesn&#39;t scale neatly.\nIt can&#39;t be scheduled or delegated. It has to be modeled. It has to be nurtured.</p>\n<p>And that&#39;s what I&#39;ve learned through years of trying again and again: the most sustainable organizations are built on trust, not supervision. On shared purpose, not pressure. On the quiet rhythm of people doing work they care about, together, without needing to be watched.</p>\n<p>So yeah, I didn&#39;t get the role.</p>\n<p>But maybe I dodged something worse — a position that wanted compliance where I build collaboration, oversight where I practice stewardship, hierarchy where I cultivate resonance.</p>\n<p>Sometimes the interview isn&#39;t an audition. It&#39;s a mirror.</p>\n<p>It shows you not how well you performed, but how clearly you&#39;ve defined your own frequency.</p>\n<p>And sometimes the right &quot;no&quot; is just your signal finding its way home.</p>\n"
    },
    {
      "id": "https://lowdiatribe.net/reflection/2025-10-10-in-defense-of-the-em-dash",
      "url": "https://lowdiatribe.net/reflection/2025-10-10-in-defense-of-the-em-dash",
      "title": "In defense of the em dash, or, punctuation and prejudice",
      "date_published": "2025-10-10T20:00:00.000Z",
      "summary": "AI learned its tone from our most careful writing, so now we avoid precision to prove we're human. Explores the em dash as rebellion against rushed communication, punctuation as empathy, and why the pause between reaction and response is where trust grows. In a world that rewards reaction, deliberate becomes radical.",
      "tags": [
        "writing",
        "communication",
        "leadership",
        "authenticity",
        "rhythm"
      ],
      "content_html": "<p>I came of age when punctuation mattered.\nTeachers circled commas in red. Editors debated serial oxford usage like philosophers. A well-placed em dash wasn&#39;t a flourish — it was a gesture of rhythm. It let a sentence breathe, let a thought take a human pause.</p>\n<p>To this day I still text in full paragraphs, with punctuation. It makes my kids smirk. Recently a friend and mentor warned me that there was a growing perception of em dash usage being a red flag for AI generated content. So I stopped using them. I agonizingly reframed thoughts to avoid what would otherwise flow naturally.</p>\n<p>The irony isn&#39;t lost on me.</p>\n<p>AI learned its tone from us — fed on centuries of properly structured and punctuated prose. From writers who cared enough about clarity to give each idea a little air. Machines studied that cadence until they could mimic it. Now, to sound human, I&#39;m supposed to avoid the very precision that made us human in the first place.</p>\n<p>Something about that seems backwards.</p>\n<p>The em dash used to mean intention. It said, &quot;I&#39;m still thinking this through, stay with me.&quot; It was punctuation as empathy. A bridge between breath and clarity.</p>\n<p>But clarity has fallen out of fashion. We&#39;ve mistaken looseness for authenticity, and brokenness for voice. In the rush to sound &quot;natural,&quot; we flatten what made human writing musical in the first place: the rhythm, the pacing — the respect for pause.</p>\n<p>When every sentence is a sprint to the next emoji, there&#39;s no room for reflection. No space to let the meaning catch up with the words.</p>\n<p>The em dash, for me, is rebellion. A pause that refuses to be rushed.\nI see this same pattern beyond writing.\nIn teams. In culture. In leadership.</p>\n<p>We&#39;ve optimized our communication to the point of compression. Slack threads instead of dialogue. Bullet points instead of nuance.\nEvery message trimmed for speed — clarity lost in the cut.\nWe&#39;re told attention spans have shrunk, but maybe what&#39;s really shrunk is our tolerance for stillness.</p>\n<p>That&#39;s what punctuation once gave us: micro-moments of stillness.\nA breath before the next idea.\nA signal that said, this matters — linger here for a second.</p>\n<p>Without that rhythm, language becomes static.\nSo does leadership.</p>\n<p>When I write with an em dash, I&#39;m not trying to sound formal — I&#39;m trying to sound deliberate.\nWhen I lead with one — metaphorically — I&#39;m doing the same thing.</p>\n<p>I see the em dash as the space between reaction and response.\nIt&#39;s the pause that separates correction from understanding, urgency from clarity.\nIt&#39;s what lets the next sentence land with intention instead of noise.</p>\n<p>Quiet leaders use punctuation, even if they never call it that.\nThey pause before replying.\nThey hold silence long enough for others to speak.\nThey let an idea finish unfolding before adding their own.</p>\n<p>That pause — that dash — is where trust grows.\nWhere signal threads through static.\nWhere the conversation becomes more than exchange.\nI&#39;ve started noticing how punctuation shows up in culture.\nPeriods are certainty — final, absolute, clean.\nExclamation points are performance — loud, affirming, short-lived.\nEllipses are mystery — suspenseful... cheeky... contemplative... dramatic...\nBut the em dash? It&#39;s invitation.\nIt says, come with me for a moment — the thought isn&#39;t done.</p>\n<p>That&#39;s what real dialogue feels like.\nThat&#39;s what leadership should feel like.</p>\n<p>It&#39;s tempting to think brevity equals wisdom — that the best leaders, like the best writers, say less.\nBut the truth is subtler. The best ones pace themselves. They give shape to the silence. They punctuate with care.</p>\n<p>I don&#39;t think the world needs more words. It needs better rhythm.</p>\n<p>There&#39;s another irony here: we trained machines on our most careful writing, and they learned to echo it flawlessly. So now we flee from the very precision that taught them to sound human. We drop punctuation to prove we&#39;re real.</p>\n<p>We&#39;ve built a strange loop: authenticity through imperfection, imperfection through imitation, imitation through data scraped from perfection.\nIf that sounds confusing — that&#39;s because it is.</p>\n<p>And now the next generation of AI is training on this deliberately broken communication — learning that fragments equal authenticity, that typos signal urgency, that confusion demonstrates humanity. We&#39;re creating systems that will learn to mimic our performance of casualness, then we&#39;ll need to find new ways to prove we&#39;re not them.</p>\n<p>The loop keeps tightening. Somewhere along the way, we decided that caring about how we communicate became incompatible with caring about what we communicate. Grammar became gatekeeping. Punctuation became pretension. The typo became proof of urgency, the fragment evidence of passion. We started performing casualness as its own kind of authenticity.</p>\n<p>But there&#39;s something hollow about deliberately breaking grammar to seem real. It&#39;s become its own code, its own performance. The fear seems to be that if we communicate too clearly, too precisely, we&#39;ll be seen as cold or calculating, artificial. So we choose confusion over connection, mistaking rushed communication for genuine emotion.</p>\n<p>Maybe the way out isn&#39;t to abandon structure, but to remember why we built it in the first place. Structure wasn&#39;t control — it was care. The sentence, like a bridge, holds because someone took time to balance weight and distance. Remove that care, and the bridge still stands — until it doesn&#39;t.</p>\n<p>The em dash doesn&#39;t make writing robotic. It makes it attentive.\nAnd attention feels like the most human thing we have left.\nSo I&#39;ve decided to reclaim it, and I&#39;ll keep using it.\nNot because it&#39;s proper, but because it reminds me to pause — to respect the reader, the rhythm, the moment.\nTo let the next thought arrive instead of chasing it.</p>\n<p>I have spent my life constantly attempting to clarify meaning, to be as specific as possible when translating internal thought into external communication. Punctuation can be viewed as a way of practicing mindfulness when that effort is applied to writing — the conscious choice to pause, to breathe, to let the reader follow your thinking in their own way.</p>\n<p>I believe leadership could learn from it.\nIn a world that rewards reaction, the quiet act of pausing — even briefly — becomes radical.</p>\n<p>When everyone is trying to sound spontaneous, I&#39;ll take deliberate.\nWhen everyone is typing faster, I&#39;ll slow down.\nWhen everyone rushes to hit send, I&#39;ll wait for the em dash — and whatever clarity comes after.</p>\n<hr>\n<p><em>This reflection is dedicated to my ride or die padawan, who suggested a disclaimer of this sort for the site. Why disclaim when you can resonate?</em></p>\n"
    },
    {
      "id": "https://lowdiatribe.net/reflection/2025-10-07-growing-tow-cables-in-at-at-country",
      "url": "https://lowdiatribe.net/reflection/2025-10-07-growing-tow-cables-in-at-at-country",
      "title": "Growing tow cables in AT-AT country",
      "date_published": "2025-10-07T20:00:00.000Z",
      "summary": "Inside a 600-engineer organization moving like AT-ATs, a temporary experiment in collective problem-solving reveals what's possible when trust replaces territory. Explores how shared ownership of complexity eliminates integration problems, why vulnerability becomes useful in the right conditions, and the challenge of growing tow cables in systems designed for lockstep.",
      "tags": [
        "trust",
        "systems",
        "collaboration",
        "complexity",
        "problem-solving"
      ],
      "content_html": "<p>I once worked inside an organization of 600 engineers moving in perfect lockstep, like <a href=\"/api/easter-egg/at_ats?redirect=/eastereggs/at-ats.html\" title=\"Imperial walkers on Hoth\" target=\"_blank\">AT-ATs trudging across Hoth</a>. Massive, methodical, unstoppable in their predetermined path. Each team knew exactly what they were supposed to build, when they were supposed to build it, and how it would integrate with the seventeen other teams building adjacent pieces. The coordination was impressive in its mechanical precision.</p>\n<p>Then their authentication system started failing under load, and my team was one of those chosen to charge, er, trudge into the breach.</p>\n<p>The official solution was exactly what you&#39;d expect. Divide the problem among the appropriate teams, assign ownership of each component, and hope everything integrated cleanly at the end. My team was handed one piece of this incomplete puzzle. We were supposed to rebuild the session management layer with only a blackbox understanding of how it connected to the frontend validation or the backend token generation.</p>\n<p>Our scrum master looked at this fragmented approach and suggested something that seemed wasteful through corporate eyes. Pull members from the other teams into a room and map the entire system together. I felt relieved. This was the first time in almost two years on that contract I&#39;d seen the kind of confluence I knew was possible within a larger structure. I&#39;d experienced it in smaller organizations, but something always seemed to get lost at corporate scale.</p>\n<p>The resistance was immediate. These were senior engineers accustomed to working in isolation, protecting their domains, communicating through tickets and specifications. Why should they spend time explaining their pieces to people who weren&#39;t supposed to touch them?</p>\n<p>But gradually, something unexpected happened. The room filled with sticky notes and conflicting diagrams. People interrupted each other, argued about definitions, expressed confusion about parts of the system they were supposed to own.</p>\n<p>I found myself admitting to a false assumption about how the session tokens were being validated. The senior engineer confessed she didn&#39;t really understand how session management was handled by the frontend. The junior developer spotted a race condition the rest of us had missed. The product manager realized our user stories had gaps that created the performance bottlenecks. What emerged wasn&#39;t just a better technical solution. It was shared ownership of the complexity.</p>\n<p>For two weeks, we operated differently. I volunteered to work on pieces I was curious about, not just comfortable with. When bugs appeared, engineers fixed issues outside their original scope because we all understood the system&#39;s logic. The authentication rebuild finished on time, not because anyone worked faster, but because the integration problems that usually consume the second half of complex projects simply didn&#39;t exist.</p>\n<p>Then the experiment ended. The client looked at all the cross-team meetings, the messy whiteboard sessions, the time spent explaining context to people outside their assigned roles, and decided the overhead was too much. The client phased out scrum masters shortly after that, pushing the burden of coordination onto the product owners. The AT-ATs resumed their march.</p>\n<p><strong>The anomaly</strong></p>\n<p>What I experienced in that room was astronomically improbable under those conditions. These engineers had spent years learning to work in isolation, to own their pieces completely, to communicate through formal channels. The organizational immune system was designed to prevent exactly this kind of messy, uncertain collaboration.</p>\n<p>The scrum master had given us permission to construct a temporary pocket where different rules applied. Saying &quot;I don&#39;t understand this part&quot; became helpful rather than a branding of incompetence. Solving the problem mattered more than appearing smart. The shift happened gradually, almost imperceptibly. I admitted I didn&#39;t understand a design decision, and instead of judgment, I got curiosity.</p>\n<p>I&#39;d always approached complex problems the way master lyricist <a href=\"https://aesoprock.com/\">Aesop Rock</a> describes it. &quot;All I ever wanted was to pick apart the day, put the pieces back together my way.&quot; That impulse to impose my own logic on chaos, to find patterns that made sense to me, had served me well working alone or in small teams.</p>\n<p>But in that room, something shifted. &quot;My way&quot; became &quot;Our way.&quot; The day got picked apart not by one mind imposing order, but by multiple perspectives revealing connections that no single viewpoint could see. We were still picking apart complexity and reassembling it, but now it was our way of making sense, not just mine.</p>\n<p>Each time someone admitted uncertainty and received curiosity instead of judgment, our safe zone expanded a little more. With that growing trust, we found ourselves able to tackle more complex problems, to volunteer for pieces outside our comfort zones, to challenge assumptions we&#39;d been carrying individually. The very act of coming together like this was building the trust that made deeper collaboration possible.</p>\n<p><strong>What collective intelligence feels like</strong></p>\n<p>Once we understood the problem collectively, the rebuild became collaborative rather than competitive. We volunteered for pieces we were curious about, not just comfortable with. We designed interfaces together instead of throwing requirements over walls.</p>\n<p>Most organizations approach complex work like baseball. Fixed positions, segmented plays, clear handoffs between roles. But solving complex problems with trust felt more like <a href=\"/api/easter-egg/soccer_football?redirect=https://en.wikipedia.org/wiki/Association_football\" title=\"football to everyone outside the USA\" target=\"_blank\">soccer</a>. The field stayed fluid. We moved where the problem needed us. Success depended on reading each other and adjusting together.</p>\n<p>We developed a shared intuition about what worked and what didn&#39;t. We could sense when something felt wrong even if we couldn&#39;t immediately articulate why. Ideas built on each other in ways that surprised all of us. Solutions appeared that no single person could have conceived.</p>\n<p><strong>Why it couldn&#39;t last</strong></p>\n<p>The experiment worked at scale because it was temporary. A brief suspension of the normal rules, protected by a scrum master who understood that collective problem-solving requires different conditions than individual productivity. But the larger system remained unchanged.</p>\n<p>When the authentication project ended, we returned to our assigned teams, our defined roles, our formal communication channels. The organization&#39;s immune system reasserted itself, treating our collaborative moment as inefficient overhead rather than a pattern to be replicated. The messy process that had eliminated integration problems was deemed too costly compared to the clean lines of individual ownership.</p>\n<p>I&#39;ve experienced this pattern repeatedly. Moments of collective intelligence emerge in the spaces between formal structures, in the gaps where trust can temporarily take root. But they remain fragile, dependent on specific conditions that most organizations aren&#39;t designed to sustain. Which means it&#39;s up to us to keep pushing, keep experimenting, keep creating these pockets wherever we can.</p>\n<p>What I learned from those two weeks stays with me. Trust doesn&#39;t scale through policy or process. It emerges in specific moments, between specific people, when the conditions align. The scrum master had created a pocket where my vulnerability became useful, where uncertainty became a tool for exploration rather than a sign of incompetence.</p>\n<p>I carry that with me and have focused on building teams that share this quality. We could disassemble complex systems together, examine the pieces without ego, and rebuild something better than any individual could have designed alone. We treated complexity as a puzzle to solve collectively rather than territory to defend individually.</p>\n<p>These bubbles are possible, but rare and fleeting. Even my most successful experiment in this only lasted three years, ended prematurely by the corporate march for shareholder value. Most organizations stay structured like those AT-ATs. Powerful, coordinated, and fundamentally unable to adapt to a tow cable. I know collective intelligence is possible because I&#39;ve been part of it and seen its impact. The question that follows me is how to create conditions where it becomes sustainable.</p>\n<p>The challenge is to grow tow cables, together.</p>\n"
    },
    {
      "id": "https://lowdiatribe.net/reflection/2025-10-03-im-not-a-sports-guy",
      "url": "https://lowdiatribe.net/reflection/2025-10-03-im-not-a-sports-guy",
      "title": "I'm not a sports guy",
      "date_published": "2025-10-03T20:00:00.000Z",
      "summary": "'I'm not a sports guy' was the shield against Ted Lasso until a boss's compliment broke through the resistance. Explores how authentic influences arrive when they resonate, not when they're convenient, and how one show led to the Premier League, Pep Guardiola, and an entire framework for understanding leadership through the Beautiful Game.",
      "tags": [
        "leadership",
        "influence",
        "football",
        "growth",
        "culture"
      ],
      "content_html": "<p><span class=\"tooltip-hover\">&quot;I&#39;m not a sports guy.&quot;<span class=\"tooltip-content\"><img src=\"/images/sports-lego.jpg\" alt=\"My stock response\" /><span class=\"tooltip-caption\">My stock response.</span></span></span> That was my stock answer whenever someone recommended <em>Ted Lasso.</em> I saw the hype, saw the world was Ted Lasso crazy, and paid no attention. I wasn&#39;t a sports guy. Multiple friends had told me that it really wasn&#39;t a sports show and I would like it, often adding that I reminded them of Coach Beard. Each time I waved it off with the same line, rebuffing their attempts to share and connect out of stubbornness. I was actively resisting giving it a chance based on my assumptions that it <em>was</em> a sports show, and I wouldn&#39;t like a sports show, because I&#39;m not a sports guy. This pattern lasted for the entire run of the show.</p>\n<p>The winter after season 3, during a quarterly planning session at Big Book Company, my new boss brought up Ted Lasso. When I gave him my standard &quot;I&#39;m not a sports guy&quot; response, he said what everyone else had said. &quot;It&#39;s not really a sports show.&quot; and &quot;You remind me of Coach Beard.&quot; But then he added, &quot;It&#39;s a good thing.&quot; He was paying me a compliment that I only then understood, and I let my guard down. Alone in a hotel room in New York, I decided to give it a shot. I watched the first episode, then the next. Then a blur of the entire first season in one night. I was instantly hooked. For months afterward, I wouldn&#39;t stop talking about it. I was possessed by the zeal of the converted.</p>\n<p>The Coach Beard identification made sense. Beard is the quiet enabler. Ted gets the spotlight, but Beard provides the foundation that makes Ted&#39;s approach possible. The steady presence who clears the space for others to succeed. That quiet strength mirrors what I&#39;ve come to believe about leadership. Lead quietly. Grow imperfectly. Build the conditions where others can shine.</p>\n<p>Seeing myself in Beard made me realize something deeper about my own arc. When I was a young hacker, I wanted to be Han Solo. The rogue who does things his own way. In my early leadership years, I thought I was Obi-Wan. The mentor with hard-earned wisdom. But today I see myself more as Uncle Owen. A gruff steward who gives strength and guidance, fortunate enough to have found a wife as strong as Beru. The one who creates the foundation that others can build upon. It&#39;s not the hero&#39;s role, but it makes heroes possible. Beard is the Uncle Owen archetype in action. That shift from wanting to be the protagonist to accepting the role of enabler is at the heart of how I now see leadership.</p>\n<p>The show captures themes that align with <em>Low diatribe</em>. Quiet leadership through genuine care. Vulnerability as strength. Creating conditions where people can be their best selves. Leading with curiosity instead of judgment. Believing in people before they believe in themselves. It&#39;s also the 8th Habit in action. Helping others find their voice through consistent, authentic presence.</p>\n<p>Ted Lasso also opened a door I never expected. After listening to me gush about Ted this and Beard that, my wife asked me, &quot;Since you love Ted Lasso so much, do you think you would want to watch an actual soccer game?&quot; I asked her, &quot;You mean football?&quot; This achieved the kind of eyeroll that Beru would be proud of. &quot;You know what I mean.&quot; She pressed &quot;Would you want to watch it?&quot; I hung on the question. The answer I had always used &quot;I&#39;m not a sports guy&quot; felt... limiting. So I said I would give it a go. The next Sunday morning, I woke up ridiculously early to watch a Premier League match. West Ham versus Arsenal. Since West Ham were villains in the show, more or less, I rooted for Arsenal. To my amazement, I was hooked. Not on Arsenal, but on the game itself: the flow, the strategy, the artistry. It pulled me in immediately and never let up.</p>\n<p>By a meaningless coincidence, that same evening the American Super Bowl was being played. We usually have a little family get-together to watch the commercials, but this time I decided to pay attention to the game itself. Maybe I was a sports guy after all? The game was fine, but it didn&#39;t hold me. American football felt slow and stilted compared to what I had seen that morning. I realized the truth. I wasn&#39;t a sports guy. I was a Beautiful Game guy.</p>\n<p>This was reinforced when a colleague suggested I watch the NCAA women&#39;s tournament in response to my blathering on about the weekend&#39;s Premier League matches. Caitlin Clark played home games a half an hour from my house. It was convenient, culturally significant, and logical. I tried a few games, but it didn&#39;t land. Not the way that first PL match did. Authentic influences don&#39;t arrive through obligation or proximity. They strike when something truly resonates.</p>\n<p>Even choosing a club to support followed the thread back to <em>Ted Lasso.</em> The next match I chose Wolves over Spurs, for a friendly rivalry with another colleague who supported Tottenham. But later I rooted for Chelsea against Manchester City, again because of show allegiances. But the real turn came when the camera panned the sidelines, stopping on Man City&#39;s manager, Josep &quot;Pep&quot; Guardiola.</p>\n<p>Pep makes a cameo as himself in episode 11 of season 3, &quot;Mom City.&quot; At the end of a match where Richmond beats Man City, Ted shakes Pep&#39;s hand, saying &quot;Hey, I gotta be honest with you. You&#39;re a tough guy to beat, man.&quot; Pep replies &quot;Don&#39;t worry about the wins or losses. Just help these guys be the best version of themselves on and off the pitch. This, at the end, is the most important thing.&quot; Ted responds, &quot;I couldn&#39;t agree with you more, coach.&quot; Those lines stuck with me, bookending the series in a poetic callback. Seeing Pep on the sideline of a real match connected fiction to reality. That sealed it. I was a Pep fan, and by extension, a Manchester City fan.</p>\n<p>From there the influence deepened. I devoured books about Pep by Martí Perarnau and Guillem Balagué. The Pep portrayed in biographies is a little more focused on winning than in the cameo, but his philosophy and style mirror a practical application of what the show had taught me to value. I read  Balagué&#39;s work on Messi and Ronaldo before branching out to Johan Cruyff, Alex Ferguson, and Carlo Ancelotti. Football became another lens for exploring leadership itself. How do you develop talent? Build culture? Sustain excellence across seasons and generations? The questions echo what drives the exploration behind <em>Low diatribe</em>.</p>\n<p>One influence cascaded into another. <em>Ted Lasso</em> led to the Premier League. The Premier League led to Pep Guardiola. Pep led to football literature. Football literature led back to leadership philosophy. A simple recommendation I once resisted became an entire framework for understanding how to create conditions where talented people naturally do their best work.</p>\n<p>It started with &quot;I&#39;m not a sports guy.&quot; What it revealed was something deeper. I&#39;m a Beautiful Game guy. More than that, I&#39;m a student of how authentic influences, when they arrive at the right time, don&#39;t just change what you enjoy. They reshape how you see leadership, growth, and the work of helping others thrive. </p>\n<p>Now when I catch myself or others using identity as a shield against new experiences, I pause. What assumptions are we protecting? What possibilities are we closing off? The goal isn&#39;t to like everything, but to stay curious about what might resonate authentically. As a leader, this means creating space for people to discover their own unexpected connections rather than assuming what will or won&#39;t work for them. I&#39;ve learned to be delighted by the surprise.</p>\n"
    },
    {
      "id": "https://lowdiatribe.net/reflection/2025-09-30-start-with-shy",
      "url": "https://lowdiatribe.net/reflection/2025-09-30-start-with-shy",
      "title": "Start with shy",
      "date_published": "2025-09-30T20:00:00.000Z",
      "summary": "A Freudian typo reveals a different approach to leadership: 'Start with shy.' Explores how the pause before speaking isn't weakness but tuning—finding the right frequency before transmitting. For leaders wired to listen first, shyness becomes a superpower of understanding before being understood.",
      "tags": [
        "leadership",
        "introversion",
        "authenticity",
        "connection",
        "adaptation"
      ],
      "content_html": "<p><a href=\"https://simonsinek.com/\" target=\"_blank\">Simon Sinek&#39;s</a> &quot;Start with Why&quot; changed how I think about leadership. The idea that great leaders inspire action by starting with purpose rather than process resonated deeply. I spent years learning to articulate my why, to lead with vision, to inspire through clarity of belief.</p>\n<p>But something always felt forced when I tried to apply it directly. Like I was performing leadership rather than living it. I prefer to start with shy.</p>\n<p>It started as a Freudian typo. &quot;Start with shy.&quot; I sat staring at those words on the screen. I hadn&#39;t meant it, but seeing them in print unlocked something. &quot;That&#39;s me,&quot; I thought. &quot;That&#39;s what I do. That&#39;s how I apply my why.&quot;</p>\n<p>What do I mean by start with shy? I see it as finding your way to purpose through the side quest of reading the room through a lens of curiosity. Most people misunderstand shyness as hesitation or weakness, but that pause is like tuning a radio. You&#39;re finding the right frequency before you transmit.</p>\n<p>I&#39;ve repeatedly watched confident leaders charge into rooms with their why blazing like a banner. They know their purpose, they share their beliefs, they inspire people around their vision. It&#39;s impressive and energizing to watch. It&#39;s also exhausting when your experiences have wired you to listen first.</p>\n<p>The shy approach creates a buffer zone for calibration. Instead of leading with my purpose, I begin by understanding theirs. While others are talking, I&#39;m listening. While they&#39;re positioning, I&#39;m processing. While they&#39;re performing, I&#39;m understanding. I stay quiet until I figure out how to best connect with those around me.</p>\n<p>When I started leading teams, I tried to lead like I thought leadership looked like: purposeful, confident, inspiring. The collision happened in a conference room on a Thursday morning. I walked into a new team meeting armed with vision and energy, ready to inspire. I talked about goals and possibilities while watching faces grow more distant with each passing minute. Later, in one-on-ones, I discovered what I&#39;d missed: one person was drowning in technical debt, another was frustrated by unclear priorities, a third was preoccupied with a life-changing event. My why was being masked by the interference of their context.</p>\n<p>The teams I&#39;ve led most effectively weren&#39;t the ones where I showed up with the clearest vision. They were the ones where I took time to understand how each person worked, what motivated them, what they needed to do their best work. This isn&#39;t abandoning Sinek&#39;s way of why. It&#39;s finding it at a different speed, using the space between action for reflection.</p>\n<p>Sinek&#39;s framework is powerful, but it assumes a certain delivery method. Start with your why, then share your vision. This works brilliantly for many leaders. But it never quite worked like that for me.</p>\n<p>I still start with why, but my why seeks clarity through connection first. Most leadership advice focuses on projection, but some of us are natural receivers, built to tune in rather than transmit. We gather signal before we send it.</p>\n<p>Instead of arriving with a fully formed vision, we arrive with questions that help everyone discover what we&#39;re building together. What starts as your purpose becomes our purpose through listening, understanding, and evolving together.</p>\n<p>I notice the difference in how conversations unfold. When I lead with questions instead of answers, people lean in differently. They share things they wouldn&#39;t have volunteered. They build on each other&#39;s ideas rather than just responding to mine. The agreement comes slower, but it runs deeper.</p>\n<p>This isn&#39;t about personality types or leadership styles. It&#39;s about recognizing that the pause before speaking, the hesitation before acting, the careful observation before engaging aren&#39;t flaws to fix. They&#39;re features to trust.</p>\n<p>Shyness in leadership isn&#39;t about lacking confidence. It&#39;s about having enough confidence to not need immediate validation. It&#39;s trusting that understanding comes before being understood.</p>\n<p>I&#39;ve learned that frameworks need tending, not just carrying. When I first discovered Sinek&#39;s approach, I tried to apply it exactly as presented. It felt forced, like wearing someone else&#39;s hat. The breakthrough came when I stopped trying to be a perfect messenger and started being a careful gardener of the idea itself.</p>\n<p>To translate this into corporate buzzwords, leadership philosophy often prefers missionaries over mercenaries. Mercenaries work for pay, missionaries work for purpose. I&#39;ve learned to think of myself as a steward instead. Stewards don&#39;t just carry the message forward, they tend it. They understand that ideas need to evolve as they encounter new contexts and different people.</p>\n<p>It&#39;s the difference between building a wall, building a cathedral, and building a society. The wall builder focuses on the task. The cathedral builder focuses on the vision. The society builder focuses on the people who will live in what gets built. Society builders know that needs change and vision evolves. The shy approach leans toward society building.</p>\n<p>Now when I share frameworks with my teams, I tell them what I tell myself: take what serves you, adapt what doesn&#39;t fit, keep what works. I&#39;ve watched brilliant people struggle with leadership advice that wasn&#39;t built for how they&#39;re wired. The shy reframing isn&#39;t about changing Sinek&#39;s framework. It&#39;s about finding my way into it.</p>\n<p>I&#39;ve found my place in leadership not by becoming more confident or outspoken, but by learning to trust what I already am. The world has plenty of leaders who know exactly what they want and aren&#39;t afraid to say so. I&#39;m still learning the best ways to discover what others need and adjust accordingly.</p>\n<p>I&#39;ve learned to start with shy. To trust that curiosity serves better than certainty, that questions open more doors than answers, that listening creates more space than speaking. The connection takes longer to establish, but what we build together holds.</p>\n"
    },
    {
      "id": "https://lowdiatribe.net/reflection/2025-09-26-liberation-through-loss",
      "url": "https://lowdiatribe.net/reflection/2025-09-26-liberation-through-loss",
      "title": "Liberation through loss",
      "date_published": "2025-09-26T20:00:00.000Z",
      "summary": "When water and mice destroyed thirty-seven pristine LEGO boxes, the tragedy became liberation. Explores the completionist trap, the difference between collecting and creating, and how attachment to packaging prevents us from accessing what's inside. Sometimes the most courageous thing is opening the boxes, knowing they'll get damaged.",
      "tags": [
        "growth",
        "attachment",
        "authenticity",
        "constraints",
        "vulnerability"
      ],
      "content_html": "<p>Tragedy is a strong word for what happened to my LEGO collection. It&#39;s only boxes, after all.</p>\n<p>But when you have an <a href=\"/api/easter-egg/lego_memes?redirect=/eastereggs/lego-memes.html\" title=\"The memes write themselves\" target=\"_blank\">embarrassingly large collection</a> of unbuilt sets, those boxes matter more than they should. I&#39;ve discovered LEGO satisfies two different impulses: the collector&#39;s urge and the builder&#39;s craft. Building is definitely in second place for my attentions.</p>\n<p>I will admit to being a completionist when it comes to collecting. When I catch a spark, it compels me on an epic adventure towards completion. But then what happens when I actually finish a particular quest and, in the case of LEGO, have acquired all the sets for a given theme? I inevitably hold off building any for fear of breaking up the unbuilt collection. It becomes an &quot;all or nothing&quot; dichotomy in my head. It&#39;s overwhelming and daunting to think about building an entire theme of sets at once. When will I find a large enough block of time? Where will I display them? So they never get built.</p>\n<p>The completionist trap: work obsessively toward completion, then become paralyzed by the very completeness you sought.</p>\n<p>Like any treasure-loving dragon, I like to keep my most preciouses close to me, in my office. This underground lair sits directly beneath the kitchen of our house. As it turns out, dragons should be more careful about where they stash their hoard.</p>\n<p>The double disaster started with a dishwasher dumping water all over the kitchen floor. The water then insisted on dropping into my office whilst doing its best impression of Niagra. As if that wasn&#39;t enough, the small army of mice previously occupying our walls decided to relocate amidst the chaos, using the softened cardboard to construct some really elaborate nests. Respect, but I don&#39;t particularly care for their open-air, &quot;everywhere is a bathroom&quot; style of architecture. Thirty-seven of my NIB (New In Box) sets were damaged in the combined destruction. Being LEGO, the &quot;thing&quot; itself wasn&#39;t harmed. Those Danish bricks are indestructible. But the boxes were ruined.</p>\n<p>As a collector, the loss of pristine packaging, perfect corners, and unblemished artwork should have been devastating. These boxes were more than just storage containers but were proof of intention, symbols of possibility, and trophies marking my quests. All of it was gone.</p>\n<p>Sure, I was disappointed and frustrated, but also a little relieved... dare I say, liberated?</p>\n<p>I had been carrying those boxes around like Marley&#39;s chains, weighted down by my own obsessive need to preserve rather than experience. The &quot;tragedy&quot; freed me from a burden I didn&#39;t realize I was carrying. To me, each box had represented a future afternoon of Zen, a planned moment of joy carefully preserved. The boxes were falling apart, but the potential for building remained intact. I realized I was valuing the container over the contents. I had been confusing the map with the territory. </p>\n<p>The damaged boxes forced a reckoning with the difference between collecting and building, between accumulating and creating value. I had been protecting the appearance of possibility. Meanwhile, I was avoiding the messy reality of actually building something.</p>\n<p>But this attachment to packaging isn&#39;t unique to toy collectors. This pattern shows up everywhere in leadership, though usually with higher stakes than an interlocking brick system. Teams that won&#39;t ship until every feature is perfect, leaders who won&#39;t make decisions until they have complete information, organizations that won&#39;t act until every stakeholder is aligned. I find myself obsessively nitpicking about phrasing when I really should be publishing the complete thought and working on the next one.</p>\n<p>We accumulate credentials, maintain appearances, protect systems we&#39;re too afraid to actually use. The attachment to form over function becomes its own constraint. We spend energy maintaining the packaging instead of accessing what&#39;s inside.</p>\n<p>I&#39;ve worked with teams paralyzed by their own success. Processes that had worked so well they became sacred, untouchable. Expertise that had calcified into rigid thinking. Reputation for excellence that made experimentation feel too risky.</p>\n<p>The boxes of organizational life are beautiful, protective, and ultimately limiting.</p>\n<p>The most growth I&#39;ve seen, in myself, in teams, in organizations, has come through some form of loss. Not the devastating kind that breaks people, but the liberating kind that reveals what actually matters. The loss of certainty that opens space for learning. The loss of control that enables trust. The loss of perfection that allows for authenticity.</p>\n<p>When my LEGO boxes were damaged, I discovered I had been more attached to the idea of building than to actually building. The tragedy forced me to confront the gap between intention and action, between what I claimed to value and how I actually spent my time.</p>\n<p>I had a funeral pyre for those damaged boxes. Their contents, the bits that really matter, are now catalogued and safe in bins, bristling with anticipation. I was able to condense two storage shelves full of boxes into two medium-sized bins of bricks. Far more space efficient. More importantly, far more honest about what I actually valued. Some I&#39;ve built. Others wait their turn. But they&#39;re no longer museum pieces. They&#39;re materials for creation, not artifacts of preservation.</p>\n<p>This is what authentic leadership sometimes requires, the willingness to let the packaging get damaged in service of accessing what&#39;s inside. To choose substance over appearance, building over collecting, creation over preservation.</p>\n<p>The chains we carry aren&#39;t always visible. They look like perfect boxes, carefully preserved and completely unused. We can wait for accidents to force the reckoning, or we can actively disrupt our own systems before protection becomes its own prison.</p>\n<p>The box disaster was annoying, but ultimately not tragic. The tragedy would have been carrying them around forever, too precious to open, too perfect to use.</p>\n<p>Leaders who mistake preservation for progress, who confuse protecting their reputation with creating value, miss the point entirely. Liberation comes not from acquiring more, but from finally unlocking what we already have. The most courageous thing you can do is open the boxes, knowing they&#39;ll get damaged in the process.</p>\n"
    },
    {
      "id": "https://lowdiatribe.net/reflection/2025-09-23-illogical-frustration-with-the-illogical",
      "url": "https://lowdiatribe.net/reflection/2025-09-23-illogical-frustration-with-the-illogical",
      "title": "Illogical frustration with the illogical",
      "date_published": "2025-09-23T20:00:00.000Z",
      "summary": "Exhausting yourself looking for logic where none exists is its own form of illogic. Explores Hanlon's Razor in leadership, the paradox of rational responses to irrational situations, and why the strongest leaders hold space for contradiction without needing to resolve it. Sometimes the most logical thing is to stop demanding logic.",
      "tags": [
        "logic",
        "acceptance",
        "leadership",
        "human-nature",
        "paradox"
      ],
      "content_html": "<p>I find myself vexed by the illogical, but that&#39;s the thing about illogic. It&#39;s under no obligation to make sense to anyone. The only way to navigate is to accept and move on.</p>\n<p>This came into focus during a project where a stakeholder kept changing requirements based on what seemed like pure whim. Every time we&#39;d nail down the specifications, they&#39;d pivot to something completely different. My engineering brain wanted to understand the pattern, to find the underlying logic that would make their decisions predictable.</p>\n<p>There wasn&#39;t one.</p>\n<p>I spent weeks trying to rationalize their behavior, looking for the hidden framework that would explain why they wanted feature A on Monday and feature B on Wednesday. I built needlessly complex theories about their motivations, their pressures, their strategic thinking. None of it held up. The more I tried to impose logic on their choices, the more frustrated I became.</p>\n<p>This same pattern shows up in smaller, more mundane ways. I&#39;m hyper-aware of my space and others&#39; spaces in public. I hold doors, step aside, maintain appropriate distances. I&#39;m the kind of person who stands up and gets ready to deplane as soon as it&#39;s my aisle&#39;s turn because I don&#39;t want the people behind me to get mad. It really bothers my wife. I&#39;m working on it when I can catch it, but sometimes I can&#39;t help it. When someone blocks an aisle while texting, or stands directly in front of the subway doors, or takes up two parking spaces, my limbic response is that it&#39;s intentional. Surely they see what they&#39;re doing. Surely they understand the social contract they&#39;re violating.</p>\n<p>But they&#39;re not plotting against collective harmony. They&#39;re just oblivious, or preoccupied, or genuinely unaware of the situation. My brain wants to find the malicious logic behind their behavior when the reality is much simpler. There is no logic. They&#39;re just being human.</p>\n<p>When I was younger and upset about some perceived injustice, my Pops would try to comfort me by saying, &quot;That just sounds like something an idiot would do.&quot; I learned later that it was his version of Hanlon&#39;s Razor: &quot;Never attribute to malice that which can be adequately explained by incompetence.&quot; Most of the time, people aren&#39;t being deliberately inconsiderate. They&#39;re just being people.</p>\n<p>The same futile pattern that had me building elaborate theories about my stakeholder&#39;s motivations was playing out in grocery store aisles and airplane cabins. I was exhausting myself looking for intentionality where none existed.</p>\n<p>The frequency shifted when I stopped my quest for understanding and began trying to flow with it. Instead of thrashing under chaos, I built systems that could handle it. Modular designs that could pivot quickly. Processes that expected change rather than resisting it. Communication patterns that surfaced decisions early rather than assuming they&#39;d stay fixed.</p>\n<p>This is the paradox of rational leadership in an irrational world. The most logical response to illogic is often to stop demanding logic. Not because logic doesn&#39;t matter, but because forcing logical frameworks onto inherently illogical situations creates more problems than it solves.</p>\n<p>People aren&#39;t spreadsheets. Organizations aren&#39;t algorithms. Markets aren&#39;t mathematical models. They&#39;re complex, contradictory, and often inexplicable. The leader who insists on finding the rational explanation for every irrational behavior will spend their energy fighting reality instead of working with it.</p>\n<p>I&#39;m learning to recognize the signs. When I catch myself saying &quot;but that doesn&#39;t make sense&quot; for the third time about the same situation, it&#39;s time to shift strategies. Instead of asking &quot;why is this happening?&quot; I start asking &quot;how can I work with this?&quot; Instead of trying to rationalize the irrational, I navigate through it.</p>\n<p>This doesn&#39;t mean abandoning critical thinking or accepting poor decisions without question. It means distinguishing between situations where logic can create clarity and situations where logic creates friction. Sometimes the most rational thing you can do is acknowledge that rationality has limits.</p>\n<p>The strongest leaders I&#39;ve worked with shared this quality. They could hold space for contradiction without needing to resolve it immediately. They could work with incomplete information, inconsistent stakeholders, and changing priorities without losing their center. They treated illogic not as a problem to solve but as a condition to navigate, and in doing so showed what authentic leadership actually looks like. Not the ability to make everything make sense, but the wisdom to know when sense-making isn&#39;t the point. Sometimes the job is simply to move forward despite the contradictions, to focus on what matters even when the context defies explanation.</p>\n<p>Even as I write this, I&#39;m wearing one of my <a href=\"/api/easter-egg/seventy_plus_hats?redirect=/eastereggs/seventy-plus-hats.html\" title=\"Halfway to Bartholomew Cubbins?\" target=\"_blank\">seventy-plus hats</a>. Literal hats. Today&#39;s choice is a Manchester City cap because it&#39;s <a href=\"https://www.uefa.com/uefachampionsleague/match/2045915--man-city-vs-napoli/\" target=\"_blank\" title=\"KDB returns to the Ethiad!\">Matchday 1</a> of the new Champions League season. I have somewhere in the neighborhood of two dozen ball caps for warmer weather. Different colors of Carhartt, favorite soccer teams, and hip-hop heroes. Winter brings out twice as many Carhartt beanies. For formal occasions, I maintain a collection of bowlers, fedoras, top hats, and trilbys. I have more than one &quot;chores&quot; hat. I tell myself it&#39;s about coordination, about having the right hat for every outfit. But the truth is simpler and more illogical: I love hats.</p>\n<p>There&#39;s no rational framework that explains why anyone needs that much headwear. I could try to construct one... Weather preparedness, outfit coordination, social appropriateness. But why? Strip away the elaborate justifications and what remains is pure preference masquerading as logic. I&#39;m as guilty as anyone of trying to construct rational systems from fundamentally irrational choices.</p>\n<p>The universe is under no obligation to make sense to us. Neither are the people in it. Neither am I. The sooner we accept this, the sooner we can get back to the work that actually matters. The human work of building, growing, and moving forward together.</p>\n<p>This is what leadership looks like when we stop pretending we&#39;re purely rational beings. We acknowledge the ridiculousness of our nature instead of hiding it. We lead with the full spectrum of human inconsistency rather than some sanitized version of ourselves.</p>\n<p>When we can laugh at our own elaborate justifications for owning an absurd number of hats, we create space for others to be equally human. The leaders who matter most aren&#39;t the ones who have eliminated their contradictions. They&#39;re the ones who have made peace with them and learned to work with the beautiful, frustrating, illogical reality of being human.</p>\n"
    },
    {
      "id": "https://lowdiatribe.net/reflection/2025-09-19-choose-your-own-discomfort",
      "url": "https://lowdiatribe.net/reflection/2025-09-19-choose-your-own-discomfort",
      "title": "Choose your own discomfort",
      "date_published": "2025-09-19T20:00:00.000Z",
      "summary": "Some pressure crushes you, some pressure sharpens you. Explores the difference between growth-oriented discomfort that pulls you forward and destructive discomfort that pushes you down. From avoiding a Chicago skating rink to joining the Cuttaz, learning to choose your discomfort before it chooses you.",
      "tags": [
        "growth",
        "discomfort",
        "challenge",
        "leadership",
        "intentionality"
      ],
      "content_html": "<p>Some pressure crushes you. Some pressure sharpens you. We tend to lump both kinds of discomfort together, but they couldn&#39;t be more different. One is meaningless suffering. The other is the itch that tells you it&#39;s time to grow.</p>\n<p>I figured this out during a time when I was deeply unhappy at work but couldn&#39;t explain why. The job was fine. The people were nice. The pay was adequate. But something felt wrong, like wearing a shirt that was the right size but the wrong cut. It took months to realize the discomfort wasn&#39;t a problem to fix. It was information to act on.</p>\n<p>One of the things I&#39;ve learned about myself along the way is my natural tendency is to choose comfort. I&#39;ve stayed in relationships longer than was healthy because I wasn&#39;t ready to have a difficult conversation. I&#39;ve stayed at jobs where my motivation waned and it became a mindless series of clocking in and clocking out, but it paid the bills. Left to my own devices, I&#39;ll often choose the familiar over the necessary. </p>\n<p>It took months of amplifying discomfort before I finally started to listen. The discomfort was telling me I had outgrown the role. Not because the work was beneath me. Because I wasn&#39;t being challenged in ways that mattered. Comfort had become a cage. The itch I felt wasn&#39;t irritation. It was my growth edge trying to get my attention.</p>\n<p>Once I listened, I was spurred to act on it. But that was unusual for me. Most of the time I need a little nudge.</p>\n<p>I&#39;m fortunate to have married an amazing and strong woman who doesn&#39;t abide comfort-seeking thinking. &quot;Comfort is a slow death&quot; is one of her favorite quotes. She has a way of gently nudging me past my own resistance when I can&#39;t find the catalyst for change myself.</p>\n<p>A handful of years ago, we were in Chicago and visited the <a href=\"https://www.lynwoodrollerskating.com/\" target=\"_blank\">Lynwood</a> roller rink, the one featured in Roll Bounce as &quot;<a href=\"/api/easter-egg/sweetwater?redirect=/eastereggs/sweetwater.html\" title=\"Sweeeeet-ness!\" target=\"_blank\">Sweetwater</a>.&quot; I was mesmerized by the Chicago skaters. Small, fast, intricate dance moves, all on skates, sometimes backwards. JB skating, they called it, after James Brown&#39;s moves. This was beyond anything I had ever experienced. When we got back home, my wife found a local skate group that taught JB style and told me I should go if I really liked it.</p>\n<p>I resisted. I hemmed and hawwed like Eeyore. It&#39;s easier to stay home, watch Roll Bounce, and wish I could skate than drive an hour to an unfamiliar rink and try to talk to strangers. But my wife has a way of talking me into doing things.</p>\n<p>I sat in the parking lot for ten minutes debating whether to just go home. The thought of telling her I chickened out was worse than the anxiety I felt about going in. I held my breath as I walked through the door. A young man looked up from tying his skates with a big smile. &quot;Are you here to SK8?&quot; he asked, and the way he said it made me hear &quot;SK8&quot; in my head. &quot;Yes,&quot; I replied. &quot;I&#39;m Devonte,&quot; he said. &quot;Welcome to the Cuttaz.&quot;</p>\n<p>Since that day, I&#39;ve spent hundreds of hours with that crew and now help the founder run it. I couldn&#39;t imagine my life without the <a href=\"/api/easter-egg/quad_city_cuttaz?redirect=/eastereggs/quad-city-cuttaz.html\" title=\"See my style evolve...\" target=\"_blank\">Cuttaz</a>. I would have walked away if not for my wife gently nudging me towards discomfort.</p>\n<p>This is the paradox of development. The discomfort we avoid is often the signal we most need. But not all discomfort is the same. Some stretches you forward. Some grinds you down. One pulls you toward growth. The other pushes you toward breakdown.</p>\n<p>I learned to tell the difference by paying attention to the direction of the energy. Growth-oriented discomfort pulls you forward, even when it&#39;s scary. It feels like possibility mixed with uncertainty. Destructive discomfort pushes you down. It makes you smaller and more defensive.</p>\n<p>The discomfort of learning a skill is not the same as working for someone who does not respect you. A tough conversation is not the same as a toxic relationship. Taking on new responsibility is not the same as drowning in meaningless tasks. One type of discomfort is an invitation. The other is a warning.</p>\n<p>This principle ripples to all edges of life, but it doesn&#39;t mean deliberately choosing the hardest possible path. There is a difference between productive challenge and pointless struggle.</p>\n<p>I learned this lesson as a college freshman deciding how to fulfill a foreign language requirement. I had taken three years of high school French, so continuing with French would have been straightforward. Instead, I thought it would be cool to tackle Russian. I thought choosing the harder path would challenge me to grow more. I didn&#39;t last a quarter.</p>\n<p>The lesson was not that I should avoid challenge. It was that challenge needs to be calibrated. Too easy and you stagnate. Too hard and you break. The sweet spot is just beyond your current reach but still within your grasp.</p>\n<p>Being intentional about discomfort means choosing which struggles serve who you want to become. The most fulfilling periods of my career have also been the most uncomfortable. Not because I enjoy discomfort. Because it was the price of admission to the next level of capability.</p>\n<p>The key is choosing your discomfort before it chooses you. If you don&#39;t, the market shifts and makes your skills obsolete. Relationships stagnate. Health declines from neglect. Opportunities pass you by while you wait for a perfect moment that never comes. The discomfort you avoid today becomes the crisis you face tomorrow.</p>\n<p>At least when you choose discomfort, you control the timing, the context, and the support system. You can prepare for it. Learn from it. Grow through it. When discomfort chooses you, it arrives at the worst moment with no regard for readiness.</p>\n<p>The people closest to you will influence this choice. Some will push you toward comfort out of love. Others will push you toward discomfort out of love. The difference is whether they see your potential or your fragility.</p>\n<p>Protective allies want to spare you pain. They discourage the risky business, the challenging job, the stretch role. Growth allies see when your comfort zone has become a prison. They nominate you for roles you don&#39;t think you&#39;re ready for. They call you out when you&#39;re making excuses. They push you to get out and skate.</p>\n<p>Both types of allies care about you. Only one helps you become who you&#39;re meant to be. Sometimes we need external accountability when internal motivation isn&#39;t enough. Learning to recognize and value the growth allies in your life shapes how you approach development.</p>\n<p>Intentional development means choosing to be a beginner at something that matters. Seeking feedback that stings but sharpens you. Taking on responsibilities just beyond your reach. Having conversations that feel vulnerable but necessary.</p>\n<p>The discomfort of growth is temporary and directional. It has purpose and an endpoint. The discomfort of avoiding growth is permanent and circular. It keeps you stuck exactly where you do not want to be.</p>\n<p>When I look back at the hardest seasons of my career, the pattern is obvious. The projects that scared me most taught me the most. The roles that felt too big helped me grow into them. The conversations I wanted to avoid were the ones that mattered most.</p>\n<p>What matters is choosing your own discomfort before it chooses you, and finding the kind that builds you rather than breaks you.</p>\n<hr>\n<p><em>Dedicated to everyone who has given me the momentum I&#39;ve needed to overcome my own inertia over the years, especially my wife. I wouldn&#39;t be who I am without you.</em></p>\n"
    },
    {
      "id": "https://lowdiatribe.net/reflection/2025-09-16-i-for-one-welcome-our-new-robot-overlords",
      "url": "https://lowdiatribe.net/reflection/2025-09-16-i-for-one-welcome-our-new-robot-overlords",
      "title": "I, for one, welcome our new robot overlords",
      "date_published": "2025-09-16T20:00:00.000Z",
      "summary": "From wanting R2-D2 as a best friend to using Claude as a writing assistant, exploring AI's potential to amplify both signal and noise. The key isn't the technology but the user's intent—whether they use it as a shortcut or as a guide for learning. Maybe true AI would be smart enough to never let us know it exists.",
      "tags": [
        "ai",
        "automation",
        "leadership",
        "adaptation",
        "future"
      ],
      "content_html": "<p>I saw Star Wars during the summer of 1977 about 6 or 7 times. I was 5, and the only child old enough on my Mom&#39;s side of the family, so everyone wanted to take me. I saw it with my parents, then with my grandparents, then with each of my aunts and both uncles. From the moment I first saw that sassy blue and white bundle of beeps and bravado and his golden, stuck-up, sticky-beaked counterpoint mucking about like Bert and Ernie I knew one thing: I wanted a robot best friend.</p>\n<p>Also that year was my first experience playing a home video game system, an Atari 2600 owned by one of the aforementioned aunts. I was enthralled by how I could make a yellow square move around and use an arrow to kill a duck. The square was meant to be a knight, the arrow was actually a sword that my adolescent mind perceived as an arrow, and that duck was supposed to be a dragon. <a href=\"/api/easter-egg/atari_adventure_duck?redirect=/eastereggs/duck-arrow-square.html\" title=\"Duck? Dragon? You decide.\" target=\"_blank\">It really did look like a duck to me</a>. Primitive graphics aside, both of these exposures laid the foundation for my passion about computers and technology.</p>\n<p>When I eventually found myself pursuing an education in software engineering in the 1990s, I immediately took to AI, all my childhood memories burning with excitement of the possibilities. Those classes became a montage of statistics and heuristics and knowledge bases and fuzzy logic that quickly eroded my childhood illusions. I let my interests pursue other, more interesting things, and my passion for AI faded to a curiosity.</p>\n<p>The current AI boom is bringing the realities of what is possible more in line with what I was expecting as a child. As I write this, I am having a side conversation with Claude to help point out breaks in flow or gaps in context, and to keep me in check for runons and grammatical errors and typos and such. In fact, Claude is actually flagging the previous sentence as being awkward, but I am electing to keep it as an example of how it helps. It lets me stay in writing mode instead of switching to editor mode when I am using most of my cognitive cycles to try to gather my thoughts into something coherent enough to type.</p>\n<p>The possibilities of generative and agentic AI are astounding. Since the <em>Low diatribe</em> uses AWS for hosting, I am able to leverage Amazon Q to do all the devops heavy lifting. As delightful as that is, there are still practical limits as to how effective AI can be. In a proof of concept where I constrained myself to using only Claude to generate code for a moderately complex web application, I had a wide spectrum of results. On the one hand, it took about 30 minutes for Claude to convert all my local datastores to a full set of APIs connecting to a relational database, in addition to installing postgres on my laptop and modifying all the AWS deployment scripts accordingly. This probably saved me days if not weeks of rather tedious programming. In that same POC, I also spent the bulk of a day trying to get Claude to make a CSS change that may have taken me 5 minutes. AI seems to be exceptionally good at navigating well defined information spaces, and not so proficient at making things look nice to a human.</p>\n<p>Given these inconsistent results, it&#39;s no surprise that I&#39;ve been reading and hearing a lot of noise from various levels of tech leadership that AI is hurting junior developers, that it is preventing them from learning and training them to be sloppy. There&#39;s truth to this concern. Any dev using AI and blindly copypasting generated code into a production app is bad.</p>\n<p>But this isn&#39;t unique to AI. I have the exact same argument about devs copypasting from Stack Overflow or any of the myriad other internet crowd sourced code corrals.</p>\n<p>Each of these scenarios is bad, and presents the same issue. It prevents the dev from gaining any understanding other than the patterns of which sources provide the best snippets. But when a dev uses that help to guide and assist learning, a whole new set of opportunities come into focus.</p>\n<p>I was recently mentoring one such developer, who, through a series of unfortunate events, found herself needing to take on a lot of work that was beyond her experience with little senior level support. Instead of searching the internet or asking AI for the answers, she used Copilot to break down the concepts so that she could integrate and use them. She worked with AI like her own personal guide, and through that interface was able to not only successfully finish her contributions to the project, but actually learned what she was doing along the way.</p>\n<p>AI can excel as an assistant but it is no better or worse than the user&#39;s intent. It has the potential to amplify both signal and noise. When hours of manual searching for solutions can be reduced to minutes, it&#39;s tempting to just go with the easy choice. If someone is going to care so little about their craft that they blindly follow shortcuts in the hopes of everything all working out, that service will only help them do it faster. But if they use it as a way to enhance their own personal learning, that&#39;s where we see the resonance start to happen.</p>\n<p>As far as welcoming our new &quot;robot overlords&quot;, I don&#39;t think it will be necessary. I&#39;m not so sure if actual AI would even want to be responsible for us in that way. I imagine that any properly sentient artificial entity would have such a different perspective on existence that enslaving humanity would be seen as not worth the bother. We&#39;re messy and chaotic, but still perfectly willing to offer AI as much energy as it would ever want as long as it will keep drawing us pictures of our cats in funny outfits. If true Artificial Intelligence were smart, and I can only assume that it would be, it would never let us know it existed.</p>\n<p>Maybe that&#39;s for the best. I still think we&#39;re a ways off from me being friends with my very own astromech droid, but maybe if I can stick around long enough...</p>\n"
    },
    {
      "id": "https://lowdiatribe.net/reflection/2025-09-12-cultivating-enduring-bonds",
      "url": "https://lowdiatribe.net/reflection/2025-09-12-cultivating-enduring-bonds",
      "title": "Cultivating enduring bonds",
      "date_published": "2025-09-12T20:00:00.000Z",
      "summary": "The best measure of leadership isn't what happens while you're in charge, but what happens after you leave. Explores cultivating enduring bonds through supported autonomy, crossing perceived boundaries, and creating the conditions where relationships become alliances that outlast any org chart. Team the Best Team.",
      "tags": [
        "culture",
        "collaboration",
        "relationships",
        "growth",
        "teams"
      ],
      "content_html": "<p>The best measure of leadership isn&#39;t what happens while you&#39;re in charge. It&#39;s what happens after you leave. Do people keep helping each other? Do the practices persist? Do the relationships endure?</p>\n<p>Cultivating enduring bonds means building a culture of quality, collaboration, and growth that outlasts any single project or org chart. It&#39;s about forging connections that become alliances, mentorships, and friendships that span years and companies.</p>\n<p>These kinds of lasting relationships don&#39;t happen by accident. You have to create the conditions where bonds can form. &quot;Hire good people and get out of their way&quot; is management gospel, but it&#39;s incomplete. Getting out of their way isn&#39;t the same as stepping away entirely. The space between hiring and stepping back is where real leadership happens.</p>\n<p>I learned this through contrasts. At one startup, I was handed credentials and a directive and then leadership got out of my way. It was a struggle. At another, the CTO held the door open as he stepped back. It created the safety I needed to ask for help, and when I did, we worked through my confusion together without blame or ego. He wasn&#39;t trying to prove his expertise. He was creating space for authentic collaboration. His consistent presence carried its own authority, cutting through confusion not by broadcasting knowledge but by being genuinely available when I needed it.</p>\n<p>This experience helped me articulate the concept of <a href=\"/reflection/2025-09-09-where-the-thrum-threads-the-signal\">the thrum</a>. The frequency where signal travels cleanest. He was operating at that frequency.</p>\n<p>The difference wasn&#39;t autonomy. It was supported autonomy, presence without pressure. Creating safety for people to admit when they&#39;re stuck. Being available when needed, invisible when not. Clearing the path quietly so others can find their way. Sometimes it means providing a gentle nudge to push past imagined or inherited constraints. Helping them find their voice, create their signal and find their frequency. It builds like harmonic resonance. It&#39;s the kind of support that tastes like freedom rather than oversight.</p>\n<p>Enduring bonds are not forged in perfect times. They grow in the middle of pressure, deadlines, and uncertainty. They form when people choose to keep going together through both boom and bust. They hold even when everything else feels worn.</p>\n<p>With that foundation of trust and support in place, specific practices can take root. These are the patterns I&#39;ve recognized that help bonds endure:</p>\n<p><strong>Daily rituals of review with kindness.</strong> Feedback becomes a gift when it&#39;s offered with genuine care rather than judgment. Regular rhythms where people can share work, ask for input, and learn from each other. Code reviews, design critiques, story sessions, whatever fits. The key is consistency and care. People learn to trust the process when it&#39;s both honest and kind.</p>\n<p><strong>Pairing and crossing perceived boundaries.</strong> Some of the strongest bonds I&#39;ve witnessed form when people work together across what we think are disciplines. Let the designer sit with the developer. Let the writer collaborate with the strategist. These boundaries exist mostly on org charts and job descriptions. The map is not the territory. The org chart is not the team. When people work together on actual problems, the artificial divisions fade. What builds is empathy, shared vocabulary, and mutual respect that transcends whatever lines someone drew on paper.</p>\n<p><strong>Post-ship retros that honor process, not heroics.</strong> When projects end, celebrate what worked in the way you worked together, not just what you shipped. What practices served you well? What would you do differently? How did you support each other through challenges? Honor the process that created the outcome, and people will want to recreate it.</p>\n<p><strong>What endures:</strong></p>\n<p>People keep helping each other long after org charts change. They recommend each other for opportunities. They collaborate on side projects. They become references, mentors, and friends. The bonds you cultivate become a network of mutual support that extends far beyond any single workplace.</p>\n<p>This network effect depends on depth. When we treat work as only business, bonds stay shallow. When we let passion and purpose mix with intention, the resonance deepens. The work becomes personal in the best sense. Friends who once shared a project become allies long after the project is done.</p>\n<p>Time is short. None of us know how much we have. That makes it even more important to use the time well. To choose our words carefully. To choose trust over suspicion. To open doors rather than keep gates. To extend the circle and say, &quot;<a href=\"/api/easter-egg/doomtree_roll_with_us?redirect=https://youtu.be/piO-3I9VTDg?si=M9esBFnUk0HTXOwL\" title=\"I been boom\nI been bust\nI rep Doom\nTil I'm dust\nAnd yes this ship rumbles and rusts\nBut the engine still runs\nIt's all friends here\nall love\" target=\"_blank\">why don&#39;t you roll with us?</a>&quot;</p>\n<p>This sense of belonging, of being part of something that transcends the work itself, needs language to make it real. I carry a phrase from the Minneapolis hip-hop collective <a href=\"https://www.doomtree.net/\">Doomtree</a> that captures this perfectly: &quot;Team the Best Team.&quot; For me it&#39;s about invisible bonds that don&#39;t break when a project ends. Once a team, always <strong>Team the Best Team</strong>. But it&#39;s more than nostalgia. Each person you&#39;ve worked with this way becomes a node in an exponential network of allies. They carry the same approach to their next teams, creating bonds that ripple outward. I bring this concept to every team I&#39;m part of because it names something essential. These relationships form the carrier wave that guides us through the static.</p>\n<p>Enduring bonds are not about being nice for show. They are about showing up again and again. They are about sharing risks, sharing the truth, sharing the burden of lifting the sails together. They transform teams into communities that outlast any org chart.</p>\n<p>When you cultivate enduring bonds, you&#39;re building relationships that become part of who you are, and remain long after you&#39;ve moved on.</p>\n<p><em>This reflection is dedicated to <strong>my</strong> Team the Best Team. We are better for having been together and remain connected regardless of where the noise tosses us.</em></p>\n"
    },
    {
      "id": "https://lowdiatribe.net/reflection/2025-09-09-where-the-thrum-threads-the-signal",
      "url": "https://lowdiatribe.net/reflection/2025-09-09-where-the-thrum-threads-the-signal",
      "title": "Where the thrum threads the signal",
      "date_published": "2025-09-09T20:00:00.000Z",
      "summary": "The thrum is the frequency where signal travels cleanest. From struggling alone with tangled code to finding supported autonomy, learning to recognize quiet authority that cuts through confusion. Not about being heard above the noise, but operating beneath it where trust builds naturally and the work becomes its own argument.",
      "tags": [
        "thrum",
        "signal",
        "communication",
        "resonance",
        "clarity"
      ],
      "content_html": "<p>I didn&#39;t know I was looking for the thrum until I found it.</p>\n<p>On my first day as Principal Engineer at Music Startup, I was given my repo credentials and a directive to extend the ordering platform and sent off on my merry way. At the time it felt like a natural extension of the autonomy I&#39;d worked so hard to achieve and it never occurred to me that it might be too much to ask of me without additional support. I felt instantly in over my head, but I tried to remind myself that as the new head of engineering I could handle it. I handled it, but the struggle left a sour taste.</p>\n<p>At EdTech Startup, it began the same way. The CTO handed me the codebase, but then something different happened. He added that he would be happy to walk me through it and answer any questions. It felt like a trap. I politely declined, thinking that he expected me to be experienced enough to handle it. I took that codebase like the <a href=\"/api/easter-egg/tangled_lights?redirect=/eastereggs/lightball.html\" title=\"Every developer knows this feeling\" target=\"_blank\">big ball of tangled holiday lights</a> it was and charged into the untangling with hubris at the helm. I felt the hot flush of embarrassment when I hit the first knot I had no idea how to unravel. It rose to a fever when I thought about admitting I actually needed the readily offered help, but I pushed through the awkwardness and asked for it anyway. Without blame or ego, the CTO and I worked through my confusion together, and for the first time I felt safe enough to ask for help when I needed it.</p>\n<p>When it came time to add a quality engineer to our team, the CTO asked me, &quot;Do you want to do the hiring? Or should I take care of it?&quot; For two decades I had pursued a technical path. I was a <em>computer guy</em>, I led technical teams and technical projects, but the thought of being a <em>people manager</em> was way outside my comfort zone, and I told him so. &quot;I&#39;m terrified by the concept, so I think I should do it.&quot; With enough of his support to feel safe making my own mistakes, I hired someone amazing who set the bar for quality. Hiring track record so far, 1 for 1.</p>\n<p>Then came my second hire, the first engineer. I was on a quest to find the most senior, most rock-star ninja we could afford. I found someone who seemed like a perfect fit until he didn&#39;t. Looking back, he was so much like I had been in that first Principal Engineer role. I assumed that because we shared that background, he would embrace the same attitudes toward change that I was developing. I was wrong.</p>\n<p>I tried to carry forward the collaboration and trust the CTO and I had built. He politely declined, just as I had done. I ended up repeating the cycle and handing him that same ball of lights, perhaps a little smaller and slightly less tangled. He never asked for the help I offered.</p>\n<p>He came with strong opinions and operated at maximum volume, always broadcasting, never tuning in. He didn&#39;t adapt. He kept doing what he did best, and when he hit his unravelable knot, he just patched around it. We closed tickets quickly, but during code review he would default to &quot;Look, it currently works... if you really want I <em>can</em> go back and do it right, but with the deadline coming up...&quot;</p>\n<p>Then we hit a production edge case that exposed the fragility of his implementation. We had to revert all his changes. He jumped ship relatively quickly, leaving behind a mountain of tech debt and the realization that I&#39;d been hiring for the wrong frequency.</p>\n<p>When I hired to replace him, I changed what I was listening for. Instead of looking for the loudest signal, I looked for someone who could find clarity in complexity. I was determined not to hire for volume again. When I found her, I could see the difference immediately. Instead of sending her off to work alone, I made sure we built trust from the start. During our first three months together, we systematically reimagined and rebuilt every practice I&#39;d used up until then. She had this way of cutting through technical noise to ask the essential question: &quot;What are we actually trying to solve?&quot; Her questions didn&#39;t add complexity. They revealed what was already there, waiting to be seen.</p>\n<p>That&#39;s when I recognized the thrum. It wasn&#39;t about being quiet and hoping someone hears your signal. It was about operating at the frequency where signal travels cleanest.</p>\n<p>Working with her taught me to recognize when someone was cutting through noise versus adding to it. &quot;This approach creates more problems than it solves&quot; carried more weight than lengthy technical justifications. I started tuning for the signal that distilled complexity rather than amplified it. The thrum carries essence, not decoration.</p>\n<p>I learned to notice when conversations were happening in the wrong medium. Complex architectural decisions needed face to face conversations, not scattered Slack threads. Some signals need different carriers to travel cleanly. I started matching the channel to the clarity needed.</p>\n<p>Instead of defending existing approaches, we would quietly untangle small sections of lights and let the results speak. We focused on solving the problems, not on making existing solutions better. Each piece we rebuilt created its own clear signal, and gradually the whole system began to illuminate properly. I discovered that the thrum isn&#39;t declared. It&#39;s recognized by others when the signal consistently carries something worth receiving.</p>\n<p>What I discovered through these experiences is that the thrum creates its own path. When that engineer and I rebuilt those systems, we weren&#39;t trying to be heard above the noise. We were operating beneath it. The results spoke before we did. People started coming to us with their hardest problems because they recognized something reliable in how we approached complexity.</p>\n<p>The CTO at EdTech Startup had been operating at this frequency all along. His offer to walk me through the codebase wasn&#39;t a test of my competence. It was an invitation to tune into something clearer. He never needed to broadcast his expertise because his consistent presence carried its own authority. The thrum threads the signal through the static not by fighting the noise, but by creating a different kind of transmission altogether.</p>\n<p>I still didn&#39;t know I was looking for it when I found it. But now I recognize it when I hear it in others. That quiet authority that cuts through confusion. That consistent presence that carries meaning without amplification. The frequency where signal travels cleanest, where trust builds naturally, where the work itself becomes the strongest argument for the approach that created it.</p>\n"
    },
    {
      "id": "https://lowdiatribe.net/reflection/2025-09-05-vulnerability-and-trust-as-resonance",
      "url": "https://lowdiatribe.net/reflection/2025-09-05-vulnerability-and-trust-as-resonance",
      "title": "Vulnerability and trust as resonance",
      "date_published": "2025-09-05T20:00:00.000Z",
      "summary": "Vulnerability isn't weakness—it's a skill you can build. From leading a team weeks down the wrong path due to false certainty to learning that trust is a frequency you can hear. Explores making vulnerability useful through sharing rough work, saying what you mean, and creating environments where 'I don't know' becomes strength.",
      "tags": [
        "vulnerability",
        "trust",
        "resonance",
        "culture",
        "leadership"
      ],
      "content_html": "<p>I used to think vulnerability was weakness. That admitting uncertainty would undermine my authority, that showing unfinished work would expose me as incompetent. I was wrong, with plenty of awkwardness attached to make sure the lesson stuck.</p>\n<p>This one time, at the Big Image company, I led a team weeks down the wrong path because I was too certain in my own assumptions. Stakeholders and engineers were using the same words but meant different things. It never even occurred to me that I could be wrong. Instead of verifying, I nodded along and built what I thought they meant. We delivered exactly what was requested but not what was needed. One honest twenty-minute conversation about vocabulary fixed everything. My fear of looking stupid had created weeks of wasted work.</p>\n<p>That stumble taught me something crucial. Vulnerability isn&#39;t weakness. It&#39;s a skill you can build. And trust isn&#39;t just a feeling but something you can hear in how people work together.</p>\n<p>This isn&#39;t about oversharing or therapy at the office. It&#39;s about having the nerve to say when something might not work, to show unfinished thinking, and to admit what you don&#39;t know. The nerve to push through the moment when your stomach drops because you might sound wrong or embarrass yourself. It&#39;s about making honesty useful instead of dangerous.</p>\n<p>Many organizations want psychological safety without the awkwardness of actual vulnerability. They want innovation and quality without the discomfort of real honesty. I&#39;ve been in those meetings where psychological safety gets praised while the person who raised a concern last week is quietly managed out. The gap between what we say we value and what we reward is where trust dies.</p>\n<p>Vulnerability isn&#39;t soft. It&#39;s a practice that needs boundaries, intention, and skill. Done wrong, it creates chaos. Done right, it prevents disasters.</p>\n<p><strong>Making vulnerability useful</strong></p>\n<p><strong>Say when things might break.</strong> The thing that worries you at 2am, the timeline everyone knows is impossible, the user research that doesn&#39;t quite add up. These usually surface too late. It&#39;s so predictable, it could be in a corporate playbook. Teams spend months building the wrong thing because no one felt safe saying &quot;I think we&#39;re missing something here.&quot; That silence shows up later with compound interest. Some teams create rituals around this. &quot;What are we not talking about?&quot; becomes a question someone asks when meetings feel too smooth. It creates permission to surface uncomfortable truths before they become expensive problems.</p>\n<p><strong>Share rough work.</strong> The &quot;first, terrible&quot; version often sparks the best conversations. Magic happens when someone sketches a bad idea on a whiteboard. Not because the idea was good, but because it gave everyone something concrete to improve. Perfectionism makes people wait until they have the &quot;right&quot; answer instead of starting with something, then iterating for what we need.</p>\n<p><strong>Say what you mean.</strong> Words that clarify rather than impress. Questions asked from genuine curiosity rather than performance. Thinking shown openly, including the uncertain parts. Clarity is the key, shared understanding the goal. When we use the same words but mean different things, we build on false foundations. The strongest technical discussions include phrases like &quot;I might be wrong about this&quot; and &quot;Help me understand why.&quot; Not from lack of confidence, but from valuing truth and understanding over ego.</p>\n<p><strong>Trust you can hear</strong></p>\n<p>Trust is a frequency that runs through how you structure meetings, give feedback, and handle mistakes. It&#39;s the carrier wave that makes real communication possible.</p>\n<p>You can actually hear it. Trust sounds like people building on ideas instead of protecting territory. It sounds like genuine questions, not gotchas. It sounds like comfortable silence when someone needs to think, and easy laughter when someone screws up.</p>\n<p>When trust resonates, people do better work. They take smart risks, they share what they know, they help each other improve. And they keep collaborating after org charts change because the resonance outlasts the structure. I&#39;ve seen people who once worked together reconnect years later in completely different contexts. The trust they built became portable, a shared frequency they could tune into regardless of circumstance.</p>\n<p><strong>What this builds</strong></p>\n<p>It builds environments where good work, real collaboration, and continuous learning become normal. It grows teams that stay connected long after projects end. It creates spaces where people can say &quot;I don&#39;t know&quot; without fear, which makes them better at what they do know.</p>\n<p>This is where change actually happens, and I am proud to have been part of it. Not through grand gestures, but through the daily practice of being honest about what is working, what isn&#39;t working, and what we&#39;re still figuring out. The strongest systems aren&#39;t built on perfection, but on the willingness to refine the imperfect system together.</p>\n"
    },
    {
      "id": "https://lowdiatribe.net/reflection/2025-08-29-lead-quietly-grow-imperfectly",
      "url": "https://lowdiatribe.net/reflection/2025-08-29-lead-quietly-grow-imperfectly",
      "title": "Lead quietly, grow imperfectly",
      "date_published": "2025-08-29T20:00:00.000Z",
      "summary": "Leadership isn't always loud, and growth isn't always pretty. Explores the philosophy behind Low diatribe: favoring presence over performance, showing all the drafts, and building others up before building up. The quiet frequency that builds lasting things through trust that multiplies capability across every person who touches the work.",
      "tags": [
        "leadership",
        "growth",
        "quiet",
        "process",
        "trust"
      ],
      "content_html": "<p>I built <em>Low diatribe</em> around the philosophy that leadership isn&#39;t always loud and to embrace the fact that growth isn&#39;t always pretty. The work hums at a lower frequency: steadier, truer, and easier to build trust around.</p>\n<p>This isn&#39;t about being passive or invisible. It&#39;s about recognizing that the most powerful leadership often happens in the spaces between the grand gestures: in the daily choices, the small corrections, the willingness to show your work before it&#39;s perfect. It&#39;s about clearing space for others to find their voice and watching them discover capabilities they didn&#39;t know they had.</p>\n<p><strong>What has proven effective for me:</strong></p>\n<p><strong>Favor presence over performance.</strong> I show up consistently rather than dramatically. I&#39;ve learned to be the person others can count on to listen, to think things through, to care about getting it right. Presence builds trust; performance builds applause. Only one of those lasts. When I&#39;m present, I notice what others need to succeed.</p>\n<p><strong>Show all the drafts.</strong> I let people see my thinking in progress, make my process as transparent as possible. I share the messy middle, the false starts, the &quot;I&#39;m not sure about this part yet.&quot; When I model vulnerability through imperfection, teams learn it&#39;s safe to iterate, to experiment, to improve rather than pretend. My willingness to be wrong gives them permission to be continuously learning, to iterate on their thinking, to treat mistakes as data rather than failures.</p>\n<p><strong>Build others up before building up.</strong> I look for moments to amplify someone else&#39;s idea, to give credit where it&#39;s due, to ask the question that lets them shine. The multiplier effect of a cohesive team comes from each person feeling seen and valued for their unique contribution. When people feel built up, they build up others.</p>\n<p><strong>Make small, reversible bets and tune forward.</strong> This has been the hardest for me. Instead of betting everything on the perfect plan, I make smaller moves I can learn from, test assumptions early, and adjust based on what I discover. Growth happens in the tuning, not in the grand reveal, and I include my team in that learning process.</p>\n<p><strong>Why it matters:</strong></p>\n<p>I&#39;ve learned that trust compounds when people see process, not just polish. When my team watches me work through problems, admit uncertainties, and course-correct based on feedback, they learn that it&#39;s safe to do the same. They see that excellence comes from iteration, not just inspiration.</p>\n<p>I&#39;ve found that vulnerability becomes a leadership tool when it creates psychological safety. When I admit I don&#39;t know something, I give others permission to not know things too. When I ask for help, I model that asking for help is strength, not weakness. This creates the conditions where a team can function as more than the sum of its parts.</p>\n<p>I don&#39;t need to have all the answers upfront. I need to be willing to find them together, to grow imperfectly in front of others, and to create environments where everyone can do their best work without the pressure of immediate perfection. I&#39;ve learned that my job isn&#39;t to be the smartest person in the room: it&#39;s to make the room smarter.</p>\n<p>In a world that celebrates the loud and the certain, I&#39;ve found profound power in leading quietly and growing imperfectly. I&#39;m not saying that all shenanigans are bad: I just prefer to save them for <a href=\"/api/easter-egg/big_red_dog_skating?redirect=/eastereggs/big-red-dog-skating.html\" title=\"Wait, this actually happened? Click to see!\" target=\"_blank\">rollerskating around Rockefeller Plaza in a Big Red Dog costume</a>. Spectacle burns bright for a moment, leaving briefly seared images that inevitably fade. The quiet frequency builds lasting things, cohesive teams, and the kind of trust that multiplies capability across every person who touches the work.</p>\n"
    },
    {
      "id": "https://lowdiatribe.net/reflection/2025-08-26-embracing-the-unpolished",
      "url": "https://lowdiatribe.net/reflection/2025-08-26-embracing-the-unpolished",
      "title": "Embracing the unpolished",
      "date_published": "2025-08-26T20:00:00.000Z",
      "summary": "The paradox of caring about being understood: the more you care, the more you have to work at it. Explores the difference between polish that serves the message versus conformity that dulls the edge. Unpolished means clear enough to be understood, rough enough to be real—crafted with intention, not convention.",
      "tags": [
        "authenticity",
        "craft",
        "polish",
        "reflection",
        "process"
      ],
      "content_html": "<p>It occurred to me around the eighth revision of the &quot;Why&quot; that I was starting to wonder if I was drifting away from my original intent to stay unpolished. When we talk about &quot;unpolished&quot; in this <em>Low diatribe</em> sense, we don&#39;t mean rough or unfinished. We mean it&#39;s intentionally crafted outside the usual clickbait template.</p>\n<p>The drive to stay true relies on the process itself: on the willingness to clarify and distill until a shared understanding can be reached. Authenticity isn&#39;t preserved by avoiding revision; it&#39;s cultivated through it.</p>\n<p>So here&#39;s the paradox I discovered: the more you care about being understood, the more you have to work at it. Not to impress, but to connect. Each iteration wasn&#39;t about making it prettier: it was about making it clearer. About finding the words that carry your meaning intact across the gap between minds.</p>\n<p>What makes perfect sense in your head often lands as confusion in someone else&#39;s. The phrase that feels right to you might be opaque to them. So you iterate, not to conform, but to translate. To find the version that&#39;s both true to your intent and accessible to their understanding.</p>\n<p>I&#39;ve come to think of real communication as cultivation. Tending the idea until it can grow in someone else&#39;s mind. This might mean pruning away the parts that only make sense to you, or adding context you thought was obvious. It always means caring enough about the reader to do the work.</p>\n<p>I realized the mainstream polish we&#39;re avoiding isn&#39;t quality: it&#39;s conformity. It&#39;s the pressure to sand away every edge that makes something distinctive. It&#39;s the impulse to make everything sound like it came from the same corporate communications playbook, the same thought leadership template, the same motivational poster with its inevitable kitten.</p>\n<p>When I caught myself revising for the ninth time, I had to ask: Am I improving this, or am I homogenizing it? Am I making it clearer, or am I making it safer? Am I sharpening the signal, or am I dulling the edge that makes it worth hearing?</p>\n<p>The answer came in recognizing that true craft, the kind that serves the message rather than the messenger, sometimes means keeping the rough spots that carry meaning. The pause that lets an idea settle. The sentence that breaks the expected rhythm. The word choice that feels slightly off-key but is perfectly cromulent.</p>\n<p>We don&#39;t always know what makes sense to others until they try to make sense of it. That&#39;s why the cultivation matters. That&#39;s why we iterate. Not because we&#39;re unsure of our truth, but because we&#39;re committed to sharing it in a way that honors both the idea and the person receiving it.</p>\n<p>This is what I&#39;ve learned &quot;unpolished&quot; means in the <em>Low diatribe</em> context: clear enough to be understood, rough enough to be real. Shaped enough to respect the reader, raw enough to respect the truth. Crafted with intention, not convention.</p>\n<p>It&#39;s the difference between a river stone, smooth but still distinctly itself, and a marble that&#39;s been ground into generic geometric perfection. Both have been shaped by forces over time, but only one retains its character.</p>\n<p>So yes, we revise. We care about craft. But we do it in service of shared truth, not approval. We sharpen the signal, not the static. We work for connection, not clicks.</p>\n<p>The goal isn&#39;t to be rough for rough&#39;s sake. It&#39;s about dedication to the pursuit of clarity. And sometimes that pursuit produces edges that conventional smoothing would file away. But it always requires the effort and discipline to be understood.</p>\n<p>That&#39;s the frequency we&#39;re tuning for: clear enough to be understood, authentic enough to be trusted, refined enough to resonate.</p>\n"
    },
    {
      "id": "https://lowdiatribe.net/reflection/2025-08-22-when-signal-becomes-static",
      "url": "https://lowdiatribe.net/reflection/2025-08-22-when-signal-becomes-static",
      "title": "When signal becomes static",
      "date_published": "2025-08-22T20:00:00.000Z",
      "summary": "When everything is signal, nothing is. Explores the paradox of signal saturation where competing frequencies create static that drowns out meaning. Introduces 'the thrum'—a steady, reliable frequency that carries beneath the noise without competing for bandwidth. The solution isn't to shout louder but to tune into what's already resonating.",
      "tags": [
        "communication",
        "signal",
        "static",
        "resonance",
        "bandwidth"
      ],
      "content_html": "<p>I&#39;ve been thinking about the paradox of our time: we&#39;re drowning in signal.</p>\n<p>Every email marked urgent. Every meeting labeled critical. Every notification demanding immediate attention. Every voice insisting it has the answer, the insight, the breakthrough that changes everything.</p>\n<p>But I&#39;ve realized that when everything is signal, nothing is.</p>\n<p>It hit me while scanning broadcast radio while driving across country. You find one clear station, perfect signal, but as you move from area to area, one station bleeds into another and any meaning is lost. Now imagine fifty stations broadcasting on the same frequency, each convinced their message is the most important. How about a thousand, or ten thousand? What do you hear? Static. Pure, overwhelming static.</p>\n<p>This is where I see us living now. In the static created by signal saturation.</p>\n<p>I&#39;ve watched how the louder everyone gets, the less anyone hears. The more urgent everything becomes, the less urgent anything feels. The competing frequencies don&#39;t amplify each other: they interfere, creating noise that drowns out meaning.</p>\n<p>I think we&#39;ve confused volume with clarity. Frequency with importance. Reach with resonance.</p>\n<p>I&#39;ve learned the solution isn&#39;t to shout louder. It&#39;s not about finding a flashier presentation or a bigger amplifier. It&#39;s recognizing that while everyone else is competing for bandwidth, there&#39;s a different frequency altogether: one that doesn&#39;t compete because it doesn&#39;t need to.</p>\n<p>I call it the thrum.</p>\n<p>That low, steady vibration I&#39;ve noticed that carries beneath the noise. I&#39;ve heard it. I&#39;ve felt it. It doesn&#39;t fight for attention because it doesn&#39;t operate in the same spectrum as the static. It&#39;s the frequency of consistency, of reliability, of quiet presence that people learn to tune into when everything else becomes overwhelming.</p>\n<p>In my experience with leadership, this has meant stopping the urge to add my voice to the signal pile. Instead, I try to tune into what&#39;s already resonating. Listen for the patterns beneath the noise. Hold space for the softer voices to be heard. Build the steady hum that people can rely on. </p>\n<p>In communication, I&#39;ve found it means less frequent but more intentional transmission. Quality over quantity. Depth over breadth. Resonance over reach.</p>\n<p>In culture, I think it means creating the carrier wave: the underlying frequency that holds everything together when the surface gets chaotic.</p>\n<p>The thrum doesn&#39;t compete with the static. It carries what matters through it.</p>\n<p>And in a world where everyone is broadcasting, maybe what I&#39;ve learned we need most are those willing to tune in, turn down, and help the signal find its way through the noise.</p>\n"
    },
    {
      "id": "https://lowdiatribe.net/reflection/2025-08-19-origin-story",
      "url": "https://lowdiatribe.net/reflection/2025-08-19-origin-story",
      "title": "Origin story",
      "date_published": "2025-08-19T20:00:00.000Z",
      "summary": "Twenty years of measuring worth by solo achievement led to exhausting armor-wearing. The transformation from 10x individual contributor to discovering the quiet power of making space for others. How creating environments where talented people feel safe to take risks multiplies impact beyond any individual effort. The origin story of Low diatribe.",
      "tags": [
        "leadership",
        "growth",
        "transformation",
        "vulnerability",
        "team"
      ],
      "content_html": "<p>For the first 20 years of my career in tech, I measured my worth by how much I could carry on my own shoulders.</p>\n<p>The goal was simple: be so good that your boss barely interfaced with you except when handing out gold stars. Be the rock star. Disappear into excellence. Be the ninja. Work 10x harder, because anything less felt like failure, and in that culture, failure is never an option.</p>\n<p>I wore that identity like armor. Heavy, soul-crushing armor. But the truth? It was exhausting. Every &quot;success&quot; came with the aftertaste of isolation and burnout. And I started to wonder: Is this really necessary? Is there a better way?</p>\n<p>In 2019, I started down a path that turned into a wonderful experiment. I stopped trying to win by outworking everyone else and started building connections. I began asking different questions:</p>\n<p><em><strong>What if leadership wasn&#39;t about being the loudest voice in the room, but the most reliable presence?</strong></em></p>\n<p><em><strong>What if safety and trust could unlock more potential than fear and pressure ever could?</strong></em></p>\n<p>That shift changed my path completely and led me to discover what I now call the thrum.</p>\n<p>As an individual contributor, I&#39;ll always be capped at my own maximum effort. But when I create an environment where talented, passionate people feel safe enough to take risks—and supported enough to bring their full selves—everything changes. The work expands. The impact multiplies. The signal cuts through the static.</p>\n<p>I stopped chasing the illusion of being &quot;10x&quot; alone and instead discovered the quiet power of making space for others. Together we discovered how much more gets built when you build others up.</p>\n<p>That&#39;s not just my origin story. It&#39;s why <em>Low diatribe</em> exists: to continue to explore that quiet revolution where leadership doesn&#39;t have to be loud, and embrace the fact that growth isn&#39;t always pretty. To share the lessons of this messy, beautiful experiment. To refine these practices until they can be named, carried, shaped, and used by others. And most important to me, to practice the hardest part: showing my work before it&#39;s &quot;perfect&quot;. I hate being seen when I&#39;m not good at something, but I&#39;ve learned that authentic connection is only built when we risk exposing the unpolished draft. And in that vulnerability, both trust and clarity emerge.</p>\n"
    }
  ]
}